From owner-linux-origin@oss.sgi.com Wed Jan 3 11:27:27 2001 Received: by oss.sgi.com id ; Wed, 3 Jan 2001 11:27:08 -0800 Received: from brutus.conectiva.com.br ([200.250.58.146]:27388 "EHLO dhcp046.distro.conectiva") by oss.sgi.com with ESMTP id ; Wed, 3 Jan 2001 11:26:56 -0800 Received: (ralf@lappi) by bacchus.dhis.org id ; Wed, 3 Jan 2001 17:18:18 -0200 Date: Wed, 3 Jan 2001 17:18:16 -0200 From: Ralf Baechle To: John Hawkes Cc: linux-origin@oss.sgi.com Subject: Re: any news about posix0? Message-ID: <20010103171816.A4511@bacchus.dhis.org> References: <012001c075b2$cbd164a0$6401a8c0@marin1.sfba.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <012001c075b2$cbd164a0$6401a8c0@marin1.sfba.home.com>; from hawkes@engr.sgi.com on Wed, Jan 03, 2001 at 10:27:14AM -0800 X-Accept-Language: de,en,fr Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing On Wed, Jan 03, 2001 at 10:27:14AM -0800, John Hawkes wrote: > Have you seen a response to your email about the broken hardware in > posix0? I know I'm interested in getting that system to work. No email response but posix0 has shown other flaws in the past. Currently they seem to be gone but it's probably only a question of time until they return again. I suspect in parts it might be a thermal problem. I had powered off posix0 over xmas. On the 26th it took 5 1/2 hours of repeated power cycling and reseting before I the error messages went away. A few days before that I had firmware error messages regarding one of the SCSI HBA's (self test failed). IRIX was booting though but I wasn't able to access /dev/sdd from either IRIX or Linux. And in August one of the bays (bottom right when standing in front of the machine) didn't get powered up. Pretty fishy system ... Anyway, there is now a more or less well running Redhat 7.0 installation on /dev/sde1. You need to use a fairly recent test11 kernel; older kernels have bugs in their 32-bit compatibility code which doesn't properly work for glibc 2.2 in older versions. Ralf From owner-linux-origin@oss.sgi.com Mon Jan 15 21:06:08 2001 Received: by oss.sgi.com id ; Mon, 15 Jan 2001 21:05:49 -0800 Received: from brutus.conectiva.com.br ([200.250.58.146]:46844 "EHLO dhcp046.distro.conectiva") by oss.sgi.com with ESMTP id ; Mon, 15 Jan 2001 21:05:25 -0800 Received: (ralf@lappi.waldorf-gmbh.de) by bacchus.dhis.org id ; Tue, 16 Jan 2001 03:04:36 -0200 Date: Tue, 16 Jan 2001 03:04:36 -0200 From: Ralf Baechle To: linux-origin@oss.sgi.com Subject: mips32 program Message-ID: <20010116030435.C908@bacchus.dhis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Accept-Language: de,en,fr Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing Probably nobody noticed so far; posix0's mips64 installation has a small utility named mips32 which makes uname -m return mips, not mips64 for it's subprocesses. This is required for many programs whicha are based on autoconf; a returned value of mips64 would make them guess they're running on a mips64-unknown-linux-gnu system - which would confuse the build process hopelessly. So for buildin apps it may be a good idea to login and do this: exec mips32 $SHELL The tool is derived by sed'ing the sparc32 package; for more information see mips32(1). Ralf