From owner-linux-origin@oss.sgi.com Sat Dec 2 05:25:01 2000 Received: by oss.sgi.com id ; Sat, 2 Dec 2000 05:24:41 -0800 Received: from u-240-21.karlsruhe.ipdial.viaginterkom.de ([62.180.21.240]:15626 "EHLO u-240-21.karlsruhe.ipdial.viaginterkom.de") by oss.sgi.com with ESMTP id ; Sat, 2 Dec 2000 05:24:27 -0800 Received: (ralf@lappi) by bacchus.dhis.org id ; Sat, 2 Dec 2000 14:24:12 +0100 Date: Sat, 2 Dec 2000 14:24:12 +0100 From: Ralf Baechle To: linux-origin@oss.sgi.com Subject: Tools upgrade on dbear Message-ID: <20001202142412.A30939@bacchus.dhis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Accept-Language: de,en,fr Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing I've upgraded the binutils for mips64 on dbear to binutils-mips64-linux- 2.9.5-2. There was some strange problem with installing the rpm on that machine which prevented an earlier update. After some fiddling the problem has now disolved into nothing so we'll never find what was causing it. Ralf From owner-linux-origin@oss.sgi.com Tue Dec 5 16:15:48 2000 Received: by oss.sgi.com id ; Tue, 5 Dec 2000 16:15:39 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:38740 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Tue, 5 Dec 2000 16:15:13 -0800 Received: from madurai.engr.sgi.com (madurai.engr.sgi.com [163.154.5.75]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id QAA23210 for ; Tue, 5 Dec 2000 16:15:12 -0800 (PST) mail_from (ananth@sgi.com) Received: from sgi.com (mango.engr.sgi.com [163.154.5.76]) by madurai.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id QAA04460 for ; Tue, 5 Dec 2000 16:10:05 -0800 (PST) Message-ID: <3A2D84A8.1BF555F1@sgi.com> Date: Tue, 05 Dec 2000 16:13:28 -0800 From: Rajagopal Ananthanarayanan X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.16-4SGI_20smp i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-origin@oss.sgi.com Subject: memmove issues Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing In porting XFS to mips64 I ran into a problem where if memmove is called with zero length, the code gets into a bogus loop. Ideally, memmove with zero length should be a no-op ... Is it possible to fix this in MIPS64 so we don't have to work-around this problem in XFS? Also, memset & memcpy should also behave similarly --- if called with zero length then it should be a no-op. thanks, -- -------------------------------------------------------------------------- Rajagopal Ananthanarayanan ("ananth") Member Technical Staff, SGI. -------------------------------------------------------------------------- From owner-linux-origin@oss.sgi.com Tue Dec 5 17:03:38 2000 Received: by oss.sgi.com id ; Tue, 5 Dec 2000 17:03:29 -0800 Received: from u-222-10.karlsruhe.ipdial.viaginterkom.de ([62.180.10.222]:25604 "EHLO u-222-10.karlsruhe.ipdial.viaginterkom.de") by oss.sgi.com with ESMTP id ; Tue, 5 Dec 2000 17:03:27 -0800 Received: (ralf@lappi) by bacchus.dhis.org id ; Wed, 6 Dec 2000 02:03:07 +0100 Date: Wed, 6 Dec 2000 02:03:07 +0100 From: Ralf Baechle To: Rajagopal Ananthanarayanan Cc: linux-origin@oss.sgi.com Subject: Re: memmove issues Message-ID: <20001206020307.D1235@bacchus.dhis.org> References: <3A2D84A8.1BF555F1@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A2D84A8.1BF555F1@sgi.com>; from ananth@sgi.com on Tue, Dec 05, 2000 at 04:13:28PM -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 Tue, Dec 05, 2000 at 04:13:28PM -0800, Rajagopal Ananthanarayanan wrote: > In porting XFS to mips64 I ran into a problem where if memmove is called > with zero length, the code gets into a bogus loop. Ideally, memmove with > zero length should be a no-op ... > > Is it possible to fix this in MIPS64 so we don't have to work-around this > problem in XFS? > > Also, memset & memcpy should also behave similarly --- if called with zero > length then it should be a no-op. memcpy, memmove and __copy_{to,from}_user are all unified in one fat routine, so fixing one will fix all of them. The bug fix is critical because via copy_{to,from}_user functions that can be turned into an exploitable DoS attack. 32-bit kernel is also affected. memset & clear_user should already handles the zero length problem correctly. Ralf From owner-linux-origin@oss.sgi.com Wed Dec 6 12:26:53 2000 Received: by oss.sgi.com id ; Wed, 6 Dec 2000 12:26:43 -0800 Received: from pneumatic-tube.sgi.com ([204.94.214.22]:50795 "EHLO pneumatic-tube.sgi.com") by oss.sgi.com with ESMTP id ; Wed, 6 Dec 2000 12:26:38 -0800 Received: from madurai.engr.sgi.com (madurai.engr.sgi.com [163.154.5.75]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA09351 for ; Wed, 6 Dec 2000 12:34:47 -0800 (PST) mail_from (ananth@sgi.com) Received: from sgi.com (mango.engr.sgi.com [163.154.5.76]) by madurai.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA05573 for ; Wed, 6 Dec 2000 12:21:35 -0800 (PST) Message-ID: <3A2EA099.2EA8365D@sgi.com> Date: Wed, 06 Dec 2000 12:24:57 -0800 From: Rajagopal Ananthanarayanan X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.16-4SGI_20smp i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-origin@oss.sgi.com Subject: glibc-devel/statvfs etc. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing For a number of reasons it'll be great if there is a port of more recent glibc-devel for MIPS64. Currently, on a couple of the machines here we have only glibc-devel version 2.0.6 ... particulary I need access to statvfs.h. There are other issues like basic types, such as __int32_t, not defined. So, is there a newer version of glibc-devel for MIPS64? -------------------------------------------------------------------------- Rajagopal Ananthanarayanan ("ananth") Member Technical Staff, SGI. -------------------------------------------------------------------------- From owner-linux-origin@oss.sgi.com Wed Dec 6 15:26:54 2000 Received: by oss.sgi.com id ; Wed, 6 Dec 2000 15:26:34 -0800 Received: from u-84-10.karlsruhe.ipdial.viaginterkom.de ([62.180.10.84]:20228 "EHLO u-84-10.karlsruhe.ipdial.viaginterkom.de") by oss.sgi.com with ESMTP id ; Wed, 6 Dec 2000 15:26:13 -0800 Received: (ralf@lappi) by bacchus.dhis.org id ; Thu, 7 Dec 2000 00:25:44 +0100 Date: Thu, 7 Dec 2000 00:25:44 +0100 From: Ralf Baechle To: Rajagopal Ananthanarayanan Cc: linux-origin@oss.sgi.com Subject: Re: glibc-devel/statvfs etc. Message-ID: <20001207002544.B952@bacchus.dhis.org> References: <3A2EA099.2EA8365D@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A2EA099.2EA8365D@sgi.com>; from ananth@sgi.com on Wed, Dec 06, 2000 at 12:24:57PM -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, Dec 06, 2000 at 12:24:57PM -0800, Rajagopal Ananthanarayanan wrote: > For a number of reasons it'll be great if > there is a port of more recent glibc-devel > for MIPS64. Currently, on a couple of the > machines here we have only glibc-devel > version 2.0.6 ... particulary I need access > to statvfs.h. There are other issues like > basic types, such as __int32_t, not defined. > > So, is there a newer version of glibc-devel for MIPS64? I have a 80% port of Redhat 7.0 which is based on a fairly recent glibc. It's running mostly solid for me and that also inludes things such as threading and binary compatibility with glibc 2.0. I'm uploading the glibc 2.1.95 now to oss.sgi.com:/pub/linux/mips/glibc/; the rest of the distribution will follow in about two days. Not earlier for bandwidth reasons, I'm on a 28k8 bps diet ;-) Note, you will also need rpm4 to install these rpms. rpm3 will not install rpm4 packages, therefore you need to untar the rpm4 binary tarballs first, then use it to install the rpm4 package properly, then glibc. Note it's still only a 32-bit library. The kernel is designed to be able to run a 64-bit userland but we currently don't have the necessary support for that in gas and glibc, just to mention the most important packages that cannot yet support a 64-bit userland.. Ralf From owner-linux-origin@oss.sgi.com Wed Dec 6 15:51:24 2000 Received: by oss.sgi.com id ; Wed, 6 Dec 2000 15:51:15 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:34824 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Wed, 6 Dec 2000 15:50:54 -0800 Received: from sydney.sydney.sgi.com (sydney.sydney.sgi.com [134.14.48.2]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id PAA00778; Wed, 6 Dec 2000 15:50:51 -0800 (PST) mail_from (kaos@ocs.com.au) Received: from kao2.melbourne.sgi.com by sydney.sydney.sgi.com via ESMTP (950413.SGI.8.6.12/930416.SGI) id KAA19284; Thu, 7 Dec 2000 10:49:33 +1100 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Ralf Baechle cc: Rajagopal Ananthanarayanan , linux-origin@oss.sgi.com Subject: Re: glibc-devel/statvfs etc. In-reply-to: Your message of "Thu, 07 Dec 2000 00:25:44 BST." <20001207002544.B952@bacchus.dhis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 07 Dec 2000 10:49:33 +1100 Message-ID: <1478.976146573@kao2.melbourne.sgi.com> Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing On Thu, 7 Dec 2000 00:25:44 +0100, Ralf Baechle wrote: >Note, you will also need rpm4 to install these rpms. rpm3 will not install >rpm4 packages rpm 3.0.5 will handle rpm v4 packages while still using the rpm v3 database format. From owner-linux-origin@oss.sgi.com Wed Dec 6 15:59:24 2000 Received: by oss.sgi.com id ; Wed, 6 Dec 2000 15:59:05 -0800 Received: from u-84-10.karlsruhe.ipdial.viaginterkom.de ([62.180.10.84]:21764 "EHLO u-84-10.karlsruhe.ipdial.viaginterkom.de") by oss.sgi.com with ESMTP id ; Wed, 6 Dec 2000 15:58:59 -0800 Received: (ralf@lappi) by bacchus.dhis.org id ; Thu, 7 Dec 2000 00:58:38 +0100 Date: Thu, 7 Dec 2000 00:58:38 +0100 From: Ralf Baechle To: Keith Owens Cc: Rajagopal Ananthanarayanan , linux-origin@oss.sgi.com Subject: Re: glibc-devel/statvfs etc. Message-ID: <20001207005838.E952@bacchus.dhis.org> References: <20001207002544.B952@bacchus.dhis.org> <1478.976146573@kao2.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <1478.976146573@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Thu, Dec 07, 2000 at 10:49:33AM +1100 X-Accept-Language: de,en,fr Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing On Thu, Dec 07, 2000 at 10:49:33AM +1100, Keith Owens wrote: > Ralf Baechle wrote: > >Note, you will also need rpm4 to install these rpms. rpm3 will not install > >rpm4 packages > > rpm 3.0.5 will handle rpm v4 packages while still using the rpm v3 > database format. Surprise - we don't have a rpm 3.0.5 port. Making one would be easy, a mostly formal exercise but ... Ralf From owner-linux-origin@oss.sgi.com Wed Dec 6 16:02:34 2000 Received: by oss.sgi.com id ; Wed, 6 Dec 2000 16:02:25 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:6158 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Wed, 6 Dec 2000 16:02:15 -0800 Received: from madurai.engr.sgi.com (madurai.engr.sgi.com [163.154.5.75]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id QAA03782 for ; Wed, 6 Dec 2000 16:02:14 -0800 (PST) mail_from (ananth@sgi.com) Received: from sgi.com (mango.engr.sgi.com [163.154.5.76]) by madurai.engr.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id PAA05707 for ; Wed, 6 Dec 2000 15:55:57 -0800 (PST) Message-ID: <3A2ED2D6.35D0554A@sgi.com> Date: Wed, 06 Dec 2000 15:59:18 -0800 From: Rajagopal Ananthanarayanan X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.16-4SGI_20smp i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-origin@oss.sgi.com Subject: Re: glibc-devel/statvfs etc. References: <3A2EA099.2EA8365D@sgi.com> <20001207002544.B952@bacchus.dhis.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing Ralf Baechle wrote: > > I have a 80% port of Redhat 7.0 which is based on a fairly recent glibc. > It's running mostly solid for me and that also inludes things such as > threading and binary compatibility with glibc 2.0. I'm uploading the > glibc 2.1.95 now to oss.sgi.com:/pub/linux/mips/glibc/; the rest of the > distribution will follow in about two days. Not earlier for bandwidth > reasons, I'm on a 28k8 bps diet ;-) That's great! Few questions: By 80% do you mean that there are some obscure packages are not available? Does glibc 2.1.95 also contain glibc-devel? Can one upgrade only glibc (and glibc-devel) on one of our origins which has Hard Hat 5.1? > > Note, you will also need rpm4 to install these rpms. rpm3 will not install > rpm4 packages, therefore you need to untar the rpm4 binary tarballs first, > then use it to install the rpm4 package properly, then glibc. > > Note it's still only a 32-bit library. The kernel is designed to be able > to run a 64-bit userland but we currently don't have the necessary support > for that in gas and glibc, just to mention the most important packages > that cannot yet support a 64-bit userland.. I'm compiling the xfs cmds (user utilities) in 32-bit mode so that's ok. -------------------------------------------------------------------------- Rajagopal Ananthanarayanan ("ananth") Member Technical Staff, SGI. -------------------------------------------------------------------------- From owner-linux-origin@oss.sgi.com Wed Dec 6 16:24:24 2000 Received: by oss.sgi.com id ; Wed, 6 Dec 2000 16:24:05 -0800 Received: from u-84-10.karlsruhe.ipdial.viaginterkom.de ([62.180.10.84]:33284 "EHLO u-84-10.karlsruhe.ipdial.viaginterkom.de") by oss.sgi.com with ESMTP id ; Wed, 6 Dec 2000 16:23:40 -0800 Received: (ralf@lappi) by bacchus.dhis.org id ; Thu, 7 Dec 2000 01:23:21 +0100 Date: Thu, 7 Dec 2000 01:23:21 +0100 From: Ralf Baechle To: Rajagopal Ananthanarayanan Cc: linux-origin@oss.sgi.com Subject: Re: glibc-devel/statvfs etc. Message-ID: <20001207012321.B1993@bacchus.dhis.org> References: <3A2EA099.2EA8365D@sgi.com> <20001207002544.B952@bacchus.dhis.org> <3A2ED2D6.35D0554A@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3A2ED2D6.35D0554A@sgi.com>; from ananth@sgi.com on Wed, Dec 06, 2000 at 03:59:18PM -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, Dec 06, 2000 at 03:59:18PM -0800, Rajagopal Ananthanarayanan wrote: > > I have a 80% port of Redhat 7.0 which is based on a fairly recent glibc. > > It's running mostly solid for me and that also inludes things such as > > threading and binary compatibility with glibc 2.0. I'm uploading the > > glibc 2.1.95 now to oss.sgi.com:/pub/linux/mips/glibc/; the rest of the > > distribution will follow in about two days. Not earlier for bandwidth > > reasons, I'm on a 28k8 bps diet ;-) > > That's great! Few questions: By 80% do you mean that there are some obscure > packages are not available? Does glibc 2.1.95 also contain glibc-devel? > Can one upgrade only glibc (and glibc-devel) on one of our origins > which has Hard Hat 5.1? In theory it should work. Still a backup sounds like an excellent idea :-) - make a backup - install rpm - run rpm --rebuilddb - install glibc, then all the other packages. Most of the other 20% are stuff like KDE packages which rely on an older compiler package which I haven't yet ported. With a compat-egcs package porting KDE and apps also should work. A few more a plagued by compiler bugs of egcs-current, most important parts of Kerberos 5. Postgresql and mysql would need some minor porting work. It's a relativly important compiler bug in gcc-current which preferably hits C++ but also some plain C programs, so if there is anybody who's interested in fixing that one ... Btw, I've kept my Origin 200 up and running for weeks and compile packages. It's fairly close to reach the lower levels of workhorse qualities. Ralf From owner-linux-origin@oss.sgi.com Tue Dec 26 06:08:59 2000 Received: by oss.sgi.com id ; Tue, 26 Dec 2000 06:08:39 -0800 Received: from brutus.conectiva.com.br ([200.250.58.146]:55800 "EHLO dhcp046.distro.conectiva") by oss.sgi.com with ESMTP id ; Tue, 26 Dec 2000 06:08:15 -0800 Received: (ralf@lappi) by bacchus.dhis.org id ; Tue, 26 Dec 2000 12:00:30 -0200 Date: Tue, 26 Dec 2000 12:00:30 -0200 From: Ralf Baechle To: linux-origin@oss.sgi.com Subject: posix0 hw trouble Message-ID: <20001226120029.B894@bacchus.dhis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Accept-Language: de,en,fr Sender: owner-linux-origin@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-origin-outgoing Xmas hacking. Posix0 continues to gives me hardware trouble. Error message of the day: [...] ***Warning: router 99e50 is not connected on any port ***Warning: router 99e50 is not connected on any port ***Warning: router 99e50 is not connected on any port ***Warning: router 99e50 is not connected on any port ***Warning: router 99e50 is not connected on any port ***Warning: router 99e50 is not connected on any port ***Warning: router 99e50 is not connected on any port ***Warning: router 99e50 is not connected on any port ***Warning: router 9a7bb is not connected on any port ***Warning: router 9a7bb is not connected on any port ***Warning: router 9a7bb is not connected on any port ***Warning: router 9a7bb is not connected on any port ***Warning: router 9a7bb is not connected on any port ***Warning: router 9a7bb is not connected on any port ***Warning: router 9a7bb is not connected on any port ***Warning: router 9a7bb is not connected on any port [...] alias_bridge0 edge add err 1 Could not setup node master_bridge. Path aliases like bootp() may not work [...] That's printed by the firmware after resetting box ... Ralf