From owner-linux@cthulhu.engr.sgi.com Sat Jun 1 19:12:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA15566; Sat, 1 Jun 1996 19:12:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id CAA12384 for linux-list; Sun, 2 Jun 1996 02:12:04 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id TAA12379 for ; Sat, 1 Jun 1996 19:12:02 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id TAA15557; Sat, 1 Jun 1996 19:12:02 -0700 Date: Sat, 1 Jun 1996 19:12:02 -0700 Message-Id: <199606020212.TAA15557@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: progress, finally... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ok, I have a complete compilation environment that seems to work quite well. All the tools are GNU, I have gcc/ld/as/etc. setups which can create either big or little endian kernels in either ELF or ECOFF format. The target format is that used by the existing Linux/MIPS people. These tools have been linking kernels for two days, I finally got a big endian kernel that sash would eat and it went fine until it tried to look for DECstation devices as that is one of the only machine types the existing Linux/MIPS kernels support (splat!). ;-) For now I'm going to hack the ARC prom code and the SCSI driver in parallel and see how far I can get it booting, more to come. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 1 20:36:29 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA20653; Sat, 1 Jun 1996 20:36:29 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA22246 for linux-list; Sun, 2 Jun 1996 03:36:25 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA22241 for ; Sat, 1 Jun 1996 20:36:23 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA24950; Sat, 1 Jun 1996 20:35:48 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606020335.UAA24950@yon.engr.sgi.com> Subject: Re: progress, finally... To: dm@neteng.engr.sgi.com (David S. Miller) Date: Sat, 1 Jun 1996 20:35:47 -0700 (PDT) Cc: linux@cthulhu.engr.sgi.com In-Reply-To: <199606020212.TAA15557@neteng.engr.sgi.com> from "David S. Miller" at Jun 1, 96 07:12:02 pm Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1048 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David, This is very impressive progress. Thanks for the update! I understand you have the prom pointers. A few that _may_ be relevant are in: http://info.engr.sgi.com/~ariel/linux/port.html This doc was put together in a rush, any suggestions, requests for additions etc. would be welcome. > > >Ok, I have a complete compilation environment that seems to work quite >well. > >All the tools are GNU, I have gcc/ld/as/etc. setups which can create >either big or little endian kernels in either ELF or ECOFF format. >The target format is that used by the existing Linux/MIPS people. > >These tools have been linking kernels for two days, I finally got a >big endian kernel that sash would eat and it went fine until it tried >to look for DECstation devices as that is one of the only machine >types the existing Linux/MIPS kernels support (splat!). ;-) > >For now I'm going to hack the ARC prom code and the SCSI driver in >parallel and see how far I can get it booting, more to come. > >Later, >David S. Miller >dm@sgi.com > -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Sat Jun 1 20:47:02 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA02822; Sat, 1 Jun 1996 20:47:02 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA22797 for linux-list; Sun, 2 Jun 1996 03:46:56 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA22786 for ; Sat, 1 Jun 1996 20:46:54 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA02817; Sat, 1 Jun 1996 20:46:54 -0700 Date: Sat, 1 Jun 1996 20:46:54 -0700 Message-Id: <199606020346.UAA02817@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: question Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I understand what all the IP?? things are, but what is the IO4? Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sun Jun 2 15:44:21 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA09646; Sun, 2 Jun 1996 15:44:20 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA15124 for linux-list; Sun, 2 Jun 1996 22:44:17 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA15118 for ; Sun, 2 Jun 1996 15:44:15 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id PAA08072; Sun, 2 Jun 1996 15:44:15 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id PAA29455; Sun, 2 Jun 1996 15:44:13 -0700 Date: Sun, 2 Jun 1996 15:44:13 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606022244.PAA29455@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com Subject: Re: question In-Reply-To: <199606020346.UAA02817@neteng.engr.sgi.com> References: <199606020346.UAA02817@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > I understand what all the IP?? things are, but what is the IO4? IO4 is part of the I/O system on Challenge L and XL ("Everest", "IP19") systems. From owner-linux@cthulhu.engr.sgi.com Mon Jun 3 11:09:11 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA06419; Mon, 3 Jun 1996 11:09:11 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA27254 for linux-list; Mon, 3 Jun 1996 17:12:28 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA27240 for ; Mon, 3 Jun 1996 10:12:26 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) for <@ares.esd.sgi.com:linux@engr.sgi.com> id KAA13259; Mon, 3 Jun 1996 10:12:22 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id KAA17639; Mon, 3 Jun 1996 10:12:20 -0700 Date: Mon, 3 Jun 1996 10:12:20 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606031712.KAA17639@fir.esd.sgi.com> To: linux@cthulhu.engr.sgi.com Subject: mtc0/eret hazard for the R4600, R4700, and R5000 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk We recently noticed an error in the CP0 hazard table for the above processors. Specifically, the eret row in the table in Appendix F is incorrect. There must be two instructions between an mtc0 which changes a register read by eret and an eret, not just one. This is not normally a problem, but it does mean that one must keep the mtc0 which restores $epc far enough away from the eret. From owner-linux@cthulhu.engr.sgi.com Mon Jun 3 11:35:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA07273; Mon, 3 Jun 1996 11:35:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA04395 for linux-list; Mon, 3 Jun 1996 17:46:31 GMT Received: from heaven.newport.sgi.com (heaven.newport.sgi.com [169.238.102.134]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04385 for ; Mon, 3 Jun 1996 10:46:29 -0700 Received: by heaven.newport.sgi.com (940816.SGI.8.6.9/940406.SGI) id KAA06440; Mon, 3 Jun 1996 10:46:27 -0700 From: "Christopher W. Carlson" Message-Id: <9606031046.ZM6438@heaven.newport.sgi.com> Date: Mon, 3 Jun 1996 10:46:26 -0700 In-Reply-To: "David S. Miller" "question" (Jun 1, 8:46pm) References: <199606020346.UAA02817@neteng.engr.sgi.com> X-Mailer: Z-Mail-SGI (3.2S.2 10apr95 MediaMail) To: "David S. Miller" , linux@cthulhu.engr.sgi.com Subject: Re: question Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Jun 1, 8:46pm, David S. Miller wrote: > Subject: question > > I understand what all the IP?? things are, but what is the IO4? > > Later, > David S. Miller > dm@sgi.com >-- End of excerpt from David S. Miller David, For future reference, you might want to check out http://www.asd.sgi.com/bbon/, which is the SGI Big Book Of Names - definitions for all of our acronyms. -- Chris Carlson +------------------------------------------------------+ | Also, carlson@sgi.com | | Work: (714) 756-5976 SGI vmail: x5-8095 | | FAX: (714) 833-9503 | +------------------------------------------------------+ From owner-linux@cthulhu.engr.sgi.com Mon Jun 3 18:03:50 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA21285; Mon, 3 Jun 1996 18:03:49 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA24937 for linux-list; Tue, 4 Jun 1996 01:02:55 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA24926 for ; Mon, 3 Jun 1996 18:02:54 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA21209; Mon, 3 Jun 1996 18:02:54 -0700 Date: Mon, 3 Jun 1996 18:02:54 -0700 Message-Id: <199606040102.SAA21209@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: more progress Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I have my ARCS firmware library code in the kernel to the point where it can do console I/O. Right now the kernel loads from sash and prints the SGI ARCS library version and revision numbers then spins in an endless loop so that it cannot cause any more trouble. ;-) I plan on continuing the ARCS library support code, specifically the code to probe for the physical memory layout of the machine which the rest of the kernel startup code needs anyway, then the device tree manipulation and probing mechanisms as well. Next I will look into getting the kgdb code functioning. And after that I will most likely try to get the generic kernel init'ing such that all the generic data structures and non-device code are setup and the kernel attempts to mount root (which it will not be able to). ;) In parallel I will begin to write the HPC? support, specifically the dma interface code. I will as well be looking into the drivers for scsi, ethernet and graphics console at the same time, coding what I can. Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 3 20:15:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA25344; Mon, 3 Jun 1996 20:15:16 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA14786 for linux-list; Tue, 4 Jun 1996 03:14:30 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA14781 for ; Mon, 3 Jun 1996 20:14:27 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA25310; Mon, 3 Jun 1996 20:14:26 -0700 Date: Mon, 3 Jun 1996 20:14:26 -0700 Message-Id: <199606040314.UAA25310@neteng.engr.sgi.com> From: "David S. Miller" To: carlson@heaven.newport.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <9606031046.ZM6438@heaven.newport.sgi.com> (carlson@heaven.newport.sgi.com) Subject: Re: question Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: "Christopher W. Carlson" Date: Mon, 3 Jun 1996 10:46:26 -0700 For future reference, you might want to check out http://www.asd.sgi.com/bbon/, which is the SGI Big Book Of Names - definitions for all of our acronyms. Thanks. Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 3 22:04:34 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA28837; Mon, 3 Jun 1996 22:04:34 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA24795 for linux-list; Tue, 4 Jun 1996 05:03:56 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA24790 for ; Mon, 3 Jun 1996 22:03:54 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA28754; Mon, 3 Jun 1996 22:03:54 -0700 Date: Mon, 3 Jun 1996 22:03:54 -0700 Message-Id: <199606040503.WAA28754@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: CVS commit mailing list? Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk If anyone wants to keep close track of my progress I could point the CVS commit messages at a generic mailing list so that everyone on this who wants to could see them. Would someone like to set this up? Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 00:47:20 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA09919; Tue, 4 Jun 1996 00:47:20 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA09731 for linux-list; Tue, 4 Jun 1996 07:47:11 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA09726 for ; Tue, 4 Jun 1996 00:47:10 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA28057 for linux@engr; Tue, 4 Jun 1996 00:46:32 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606040746.AAA28057@yon.engr.sgi.com> Subject: Re: CVS commit mailing list? To: linux@cthulhu.engr.sgi.com Date: Tue, 4 Jun 1996 00:46:32 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 853 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk If anyone on the linux@engr list is _not_ interested in these CVS commit auto reports, let me know and I'll ask majordomo-owner to create a separate: linux-progress@engr majordomo list. Until we see objections/too-much-traffic, I think Dave can go ahead and auto-mail the reports to linux@engr Personally, I think I'll find these interesting. Anyone? > >I wouldn't mind if you just pointed it at linux@engr (i.e., this list). >Anyone else? > >--lm >--- >Larry McVoy lm@sgi.com http://reality.sgi.com/lm (415) 933-1804 >Copyright 1996, all rights reserved. Microsoft Network is prohibited from >redistributing this work in any form, in whole or in part without license. >License to distribute this work is available to Microsoft at $500. >Transmission without permission constitutes an agreement to these terms. > -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 04:55:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA14358; Tue, 4 Jun 1996 04:55:16 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id LAA26107 for linux-list; Tue, 4 Jun 1996 11:55:02 GMT Received: from beyond.clubfed.sgi.com (beyond.clubfed.sgi.com [169.238.1.2]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA26101; Tue, 4 Jun 1996 04:54:58 -0700 Received: from trinbago.clubfed.sgi.com by beyond.clubfed.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/911001.SGI) id HAA21084; Tue, 4 Jun 1996 07:47:03 -0400 Received: by trinbago.clubfed.sgi.com (940816.SGI.8.6.9/940406.SGI.AUTO) id IAA03426; Tue, 4 Jun 1996 08:16:06 -0400 From: "Kwesi Ames" Message-Id: <9606040815.ZM3424@trinbago.clubfed.sgi.com> Date: Tue, 4 Jun 1996 08:15:54 -0400 In-Reply-To: ariel@yon.engr.sgi.com (Ariel Faigon) "Re: CVS commit mailing list?" (Jun 4, 12:46am) References: <199606040746.AAA28057@yon.engr.sgi.com> X-Face: +g~UQT+z9(^"0C`fv,%E,C6_Oe)WXTlrohR/DaIIi.M1K4Q.Lov?w.b5_9)7ttP:DT)a})( Q*I&N#UNe$Tnxu^U!'P8-AbGqCG,y;#j4iO;rkEr`^$o7DmAqm5?uU8@'w88/iSrC-{4,a423@pN,7x&P7n=2@Y8{ X-Mailer: Z-Mail-SGI (3.2S.1 10apr95 MediaMail) To: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com Subject: Re: CVS commit mailing list? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk [snip] > > Until we see objections/too-much-traffic, I think Dave can > go ahead and auto-mail the reports to linux@engr > > Personally, I think I'll find these interesting. I too find them interesting. -Kwesi > > Anyone? > > > > >I wouldn't mind if you just pointed it at linux@engr (i.e., this list). > >Anyone else? > > [chomp] -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kwesi O. Ames Systems Engineering Support Silicon Graphics Inc. koa@sgi.com "I was one in a MILLON" corp voicemail (800) 326-1020 ext. 5-8713 phone (301) 572-3255 fax (301) 572-3280 http://reality.sgi.com/koa ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 09:18:26 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA22705; Tue, 4 Jun 1996 09:18:26 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA20279 for linux-list; Tue, 4 Jun 1996 16:18:17 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA20273; Tue, 4 Jun 1996 09:18:15 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id JAA15037; Tue, 4 Jun 1996 09:18:14 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id JAA15088; Tue, 4 Jun 1996 09:18:04 -0700 Date: Tue, 4 Jun 1996 09:18:04 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606041618.JAA15088@fir.esd.sgi.com> To: ariel@cthulhu.engr.sgi.com Cc: linux@cthulhu.engr.sgi.com Subject: Re: CVS commit mailing list? In-Reply-To: <199606040746.AAA28057@yon.engr.sgi.com> References: <199606040746.AAA28057@yon.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ariel Faigon writes: > > If anyone on the linux@engr list is _not_ interested in these > CVS commit auto reports, let me know and I'll ask majordomo-owner > to create a separate: > > linux-progress@engr > > majordomo list. > > Until we see objections/too-much-traffic, I think Dave can > go ahead and auto-mail the reports to linux@engr > > Personally, I think I'll find these interesting. ... I am interested too, but I would rather have two lists, just as we normally do for regular development (sgi.bugs.xxx for bug reports and checkins about xxx, sgi.engr.xxx for general discussion about xxx). Why don't you set up linux-progress as a clone of linux to start, and people who tire of the reports can unsubscribe from the linux-progress. Having a separate list will also make a little easier to search the archives later on. From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 10:07:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA01316; Tue, 4 Jun 1996 10:07:30 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA17723 for linux-list; Tue, 4 Jun 1996 15:52:04 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id IAA17716 for ; Tue, 4 Jun 1996 08:52:03 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id IAA13771; Tue, 4 Jun 1996 08:52:02 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id IAA14993; Tue, 4 Jun 1996 08:51:52 -0700 Date: Tue, 4 Jun 1996 08:51:52 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606041551.IAA14993@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com, mani@fir.esd.sgi.com Subject: Re: more progress In-Reply-To: <199606040102.SAA21209@neteng.engr.sgi.com> References: <199606040102.SAA21209@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: ... > Next I will look into getting the kgdb code functioning. And after > that I will most likely try to get the generic kernel init'ing such > that all the generic data structures and non-device code are setup and > the kernel attempts to mount root (which it will not be able to). ;) ... Please check with Mani Varadarajan (mani@esd.sgi.com) about kgdb. He has used it with the DMS Moosehead system simulator, although in that case the simulator acts as the target system monitor, instead of having a program resident in memory with the kernel. I don't know if he had to fix anything for the MIPS architecture; if he did, that might save you some startup time. From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 11:30:01 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA04250; Tue, 4 Jun 1996 11:30:01 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA28851 for linux-list; Tue, 4 Jun 1996 17:17:26 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA28835; Tue, 4 Jun 1996 10:17:22 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA28670; Tue, 4 Jun 1996 10:16:42 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606041716.KAA28670@yon.engr.sgi.com> Subject: Re: CVS commit mailing list? To: wje@fir.esd.sgi.com (William J. Earl) Date: Tue, 4 Jun 1996 10:16:42 -0700 (PDT) Cc: ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com In-Reply-To: <199606041618.JAA15088@fir.esd.sgi.com> from "William J. Earl" at Jun 4, 96 09:18:04 am Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1077 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk OK, I requested linux-progress to be created on majordomo@engr. I guess it'll take some time till someone gets time to set this up, I'll let you know when it is ready. > >Ariel Faigon writes: > > > > If anyone on the linux@engr list is _not_ interested in these > > CVS commit auto reports, let me know and I'll ask majordomo-owner > > to create a separate: > > > > linux-progress@engr > > > > majordomo list. > > > > Until we see objections/too-much-traffic, I think Dave can > > go ahead and auto-mail the reports to linux@engr > > > > Personally, I think I'll find these interesting. >... > > I am interested too, but I would rather have two lists, just as >we normally do for regular development (sgi.bugs.xxx for bug reports and >checkins about xxx, sgi.engr.xxx for general discussion about xxx). >Why don't you set up linux-progress as a clone of linux to start, and >people who tire of the reports can unsubscribe from the linux-progress. >Having a separate list will also make a little easier to search the >archives later on. > -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Jun 4 23:42:45 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA10325; Tue, 4 Jun 1996 23:42:44 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id GAA01954 for linux-list; Wed, 5 Jun 1996 06:42:05 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA01947; Tue, 4 Jun 1996 23:42:04 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA10272; Tue, 4 Jun 1996 23:42:00 -0700 Date: Tue, 4 Jun 1996 23:42:00 -0700 Message-Id: <199606050642.XAA10272@neteng.engr.sgi.com> From: "David S. Miller" To: ariel@cthulhu.engr.sgi.com CC: wje@fir.esd.sgi.com, ariel@cthulhu.engr.sgi.com, linux@cthulhu.engr.sgi.com In-reply-to: <199606041716.KAA28670@yon.engr.sgi.com> (ariel@yon) Subject: Re: CVS commit mailing list? Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: ariel@yon (Ariel Faigon) Date: Tue, 4 Jun 1996 10:16:42 -0700 (PDT) OK, I requested linux-progress to be created on majordomo@engr. I guess it'll take some time till someone gets time to set this up, I'll let you know when it is ready. When you tell me it is up I will point the CVS commit mails at it, thanks Ariel. Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 00:00:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA11072; Wed, 5 Jun 1996 00:00:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id GAA03336 for linux-list; Wed, 5 Jun 1996 06:59:38 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id XAA03324 for ; Tue, 4 Jun 1996 23:59:37 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA11058; Tue, 4 Jun 1996 23:59:36 -0700 Date: Tue, 4 Jun 1996 23:59:36 -0700 Message-Id: <199606050659.XAA11058@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: [ariel@yon: linux-progress is allive] Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk ------- Start of forwarded message ------- From: ariel@yon (Ariel Faigon) Subject: linux-progress is allive To: dm@yon (David S. Miller) Date: Tue, 4 Jun 1996 23:53:38 -0700 (PDT) Reply-To: ariel@engr.sgi.com Organization: Silicon Graphics Inc. MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 545 David, could you forward this to 'linux' Majordomo@engr doesn't seem to like me, it keeps bouncing back when I mail this to linux... - ----- Forwarded message from owner-linux@cthulhu ----- The linux-progress list is now set up. My list descriptions somehow evaporated, but this is not important. Feel free to subscribe. To: majordomo@engr.sgi.com subscribe linux-progress David: you may point your CVS commit automailer to it: linux-progress@engr.sgi.com - -- Peace, Ariel - ----- End of forwarded message from owner-linux@cthulhu ----- ------- End of forwarded message ------- From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 00:12:53 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA11479; Wed, 5 Jun 1996 00:12:52 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA05405 for linux-list; Wed, 5 Jun 1996 07:12:18 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA05400 for ; Wed, 5 Jun 1996 00:12:16 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA11472; Wed, 5 Jun 1996 00:12:16 -0700 Date: Wed, 5 Jun 1996 00:12:16 -0700 Message-Id: <199606050712.AAA11472@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: netbooting Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk How much pain is involved in netbooting a kernel from an INDY? Can I just setup a /tftpboot area with the appropriate files and setup a place to place the kernels for the bootloader to find and it'll work? If so, can someone tell me what the necessary magic is that needs to be done? This would speed up my development tremendously ;) Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 00:34:07 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA12214; Wed, 5 Jun 1996 00:34:06 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA08448 for linux-list; Wed, 5 Jun 1996 07:33:37 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA08443 for ; Wed, 5 Jun 1996 00:33:35 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA12209; Wed, 5 Jun 1996 00:33:35 -0700 Date: Wed, 5 Jun 1996 00:33:35 -0700 Message-Id: <199606050733.AAA12209@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: confuscious say... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk "Young grasshopper be very very careful when poking MC memory controller registers you may hose machine to irrecoverable state..." Indeed, even the power switch was useless hehehe... Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 13:49:12 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA03571; Wed, 5 Jun 1996 13:49:12 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA23460 for linux-list; Wed, 5 Jun 1996 18:42:37 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA23448 for ; Wed, 5 Jun 1996 11:42:35 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id LAA18157; Wed, 5 Jun 1996 11:35:29 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id LAA11745; Wed, 5 Jun 1996 11:35:26 -0700 Date: Wed, 5 Jun 1996 11:35:26 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606051835.LAA11745@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com Subject: Re: netbooting In-Reply-To: <199606050712.AAA11472@neteng.engr.sgi.com> References: <199606050712.AAA11472@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > How much pain is involved in netbooting a kernel from an INDY? Can I > just setup a /tftpboot area with the appropriate files and setup a > place to place the kernels for the bootloader to find and it'll work? > If so, can someone tell me what the necessary magic is that needs to > be done? It is easy. On your host system, either put the kernel you want to boot in /usr/local/boot/., or, in /etc/inetd.conf on your host system, add a "-f" to the end of the line and "killall -HUP inetd" (to get inetd to re-read /etc/inetd.conf). Then, on the target system, first set the "netaddr" PROM environment variable. It should be set to the IP address (dotted notation) of the target system. Check it with the "printenv" PROM command. Set it with setenv -p netaddr 1.2.3.4 (replacing "1.2.3.4" with the IP address of the target system). Then, do boot -f bootp()hostsystem:xyx where "hostsystem" is the name of the host system and "xyz" is the name of the kernel you want to boot. If you add "-f" to the bootp line, you can use a full path name on the target system in place of "xyz". Any additional words on the command line are passed to the booted program as a UNIX-style argument list, and the environment variable list is passed as well. That is, on entry, the program will see argc in $a0, argv in $a1, and environ in $a2. On an Indy, the booted kernel (or other program) must be in MIPS ECOFF format. On Moosehead, the kernel must be in ELF format. The "-coff" option to the IRIX ld will cause it to create an ECOFF binary instead of an ELF binary in the final link, even if all the input binaries are in ELF format. If you want to boot an ELF kernel on Indy, you have to boot an indirect loader. You can use the IRIX sash. Put sash in the volume header on the Indy, or in a bootp-able place on the host system. Then do boot -f bootp()hostsystem:sash or boot -f sash and then, in either case boot -f bootp()hostsystem:xyx where the last command is to the sash prompt, not the PROM prompt. sash knows how to load both ELF and ECOFF. On an Indy, the PROM would like you to link the kernel at or above 0x88002000, with the highest address in the linked binary being below 0x88400000 (4 MB). From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 16:40:50 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA10985; Wed, 5 Jun 1996 16:40:49 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA12222 for linux-list; Wed, 5 Jun 1996 23:40:45 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA12213 for ; Wed, 5 Jun 1996 16:40:44 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA09961; Wed, 5 Jun 1996 16:38:09 -0700 Date: Wed, 5 Jun 1996 16:38:09 -0700 Message-Id: <199606052338.QAA09961@neteng.engr.sgi.com> From: "David S. Miller" To: wje@fir.esd.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <199606051835.LAA11745@fir.esd.sgi.com> (wje@fir.esd.sgi.com) Subject: Re: netbooting Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Wed, 5 Jun 1996 11:35:26 -0700 From: wje@fir.esd.sgi.com (William J. Earl) On an Indy, the booted kernel (or other program) must be in MIPS ECOFF format. Know whats strange, I can netboot big endian elf kernels from the ARCS command line monitor with zero problems on my target INDY. ;-) Later, David S. Miller dm@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 16:56:54 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA15545; Wed, 5 Jun 1996 16:56:53 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA15640 for linux-list; Wed, 5 Jun 1996 23:56:43 GMT Received: from titian (titian.engr.sgi.com [192.102.117.31]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA15634; Wed, 5 Jun 1996 16:56:40 -0700 Received: from localhost by titian via SMTP (950413.SGI.8.6.12/940406.SGI.AUTO) id QAA12520; Wed, 5 Jun 1996 16:56:40 -0700 Message-Id: <199606052356.QAA12520@titian> To: "David S. Miller" cc: wje@fir.esd.sgi.com, linux@cthulhu.engr.sgi.com Subject: Re: netbooting In-reply-to: Your message of "Wed, 05 Jun 1996 16:38:09 PDT." <199606052338.QAA09961@neteng.engr.sgi.com> Date: Wed, 05 Jun 1996 16:56:39 -0700 From: Mike McDonald Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk >Date: Wed, 5 Jun 1996 16:38:09 -0700 >From: "David S. Miller" >To: wje@fir.esd.sgi.com >Subject: Re: netbooting > > Date: Wed, 5 Jun 1996 11:35:26 -0700 > From: wje@fir.esd.sgi.com (William J. Earl) > > On an Indy, the booted kernel (or other program) must be > in MIPS ECOFF format. > >Know whats strange, I can netboot big endian elf kernels from the ARCS >command line monitor with zero problems on my target INDY. ;-) > >Later, >David S. Miller >dm@engr.sgi.com My understanding was that sash had to be COFF due to the proms but that the newer versions of sash understood both COFF and ELF kernels. Something like that anyway. Mike McDonald mikemac@engr.sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 5 17:28:25 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA18391; Wed, 5 Jun 1996 17:28:25 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA23246 for linux-list; Thu, 6 Jun 1996 00:27:19 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA23223 for ; Wed, 5 Jun 1996 17:27:14 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id RAA03914; Wed, 5 Jun 1996 17:27:05 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id RAA12455; Wed, 5 Jun 1996 17:26:22 -0700 Date: Wed, 5 Jun 1996 17:26:22 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606060026.RAA12455@fir.esd.sgi.com> To: Mike McDonald Cc: "David S. Miller" , linux@cthulhu.engr.sgi.com Subject: Re: netbooting In-Reply-To: <199606052356.QAA12520@titian> References: <199606052338.QAA09961@neteng.engr.sgi.com> <199606052356.QAA12520@titian> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Mike McDonald writes: > > >Date: Wed, 5 Jun 1996 16:38:09 -0700 > >From: "David S. Miller" > >To: wje@fir.esd.sgi.com > >Subject: Re: netbooting > > > > Date: Wed, 5 Jun 1996 11:35:26 -0700 > > From: wje@fir.esd.sgi.com (William J. Earl) > > > > On an Indy, the booted kernel (or other program) must be > > in MIPS ECOFF format. > > > >Know whats strange, I can netboot big endian elf kernels from the ARCS > >command line monitor with zero problems on my target INDY. ;-) > > > >Later, > >David S. Miller > >dm@engr.sgi.com > > My understanding was that sash had to be COFF due to the proms but > that the newer versions of sash understood both COFF and ELF kernels. > Something like that anyway. Yes, that is correct. If David is leaving off the "-f", it is possible that the PROM is booting sash first, and letting sash boot the kernel. On the other hand, David's Indy does have the latest Indy PROM, so it is possible that the PROM developer dropped in ELF support. We can't assume it is available on an Indy, so we let sash do the work. I checked on the PROM source, and the recent PROMs, such as what David has, do indeed boot ELF binaries directly. That is, both ELF and ECOFF are turned on in the recent Indy PROMs. From owner-linux@cthulhu.engr.sgi.com Sat Jun 8 02:09:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA07026; Sat, 8 Jun 1996 02:09:17 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id JAA28985 for linux-list; Sat, 8 Jun 1996 09:09:10 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id CAA28980 for ; Sat, 8 Jun 1996 02:09:08 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id CAA07021; Sat, 8 Jun 1996 02:09:08 -0700 Date: Sat, 8 Jun 1996 02:09:08 -0700 Message-Id: <199606080909.CAA07021@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: wheee... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I finally got interrupts working... more to come Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 8 04:23:48 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA07867; Sat, 8 Jun 1996 04:23:48 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id LAA03208 for linux-list; Sat, 8 Jun 1996 11:23:34 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA03203 for ; Sat, 8 Jun 1996 04:23:33 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id EAA07860; Sat, 8 Jun 1996 04:23:33 -0700 Date: Sat, 8 Jun 1996 04:23:33 -0700 Message-Id: <199606081123.EAA07860@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: Are you satisfied now Mr. McVoy? ;-) Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Calibrating delay loop.. ok - 91.96 BogoMIPS Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 8 05:19:57 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id FAA08549; Sat, 8 Jun 1996 05:19:57 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id MAA04756 for linux-list; Sat, 8 Jun 1996 12:19:44 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id FAA04751 for ; Sat, 8 Jun 1996 05:19:43 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA08535; Sat, 8 Jun 1996 05:19:46 -0700 Date: Sat, 8 Jun 1996 05:19:46 -0700 Message-Id: <199606081219.FAA08535@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: well it is about time... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk This port is going like a funeral procession, I apologize. Ok, quick report: 1) Interrupts work, with a little more coding it will handle the setup and registering of all interrupts and handlers on the INDY for whatever driver requests them. 2) Timers work, I am using the r4k counter/compare register timer mechanism because of the bug in the i8254 Intel timer chips on certain INDY's. The calibration of the compare offsets needs some work but the working framework is there and needs a little tweaking, basically my algorithm is: a) setup i8254 counter 0 and counter 2 such that the period of counter 0 is the desired HZ value b) poll counter 0 waiting for a value of 1 c) quickly set CP0_COUNTER to zero d) poll counter 0 for value of 1 e) quickly read CP0_COUNTER value This seems to approximate the value I want in it's current form pretty well. I have to add some fuzz factors into it and possibly write the calibration code in assembly to get the accuracy I want/need. 3) The kernel boots decently far. It init's all of memory management, sets up the buffer cache, sets up the inode table, inits the networking stack, prints the linux banner and is about to fork off the init kernel thread. At this point my task list looks like: 1) Clean up and finish all the krufty code I wrote tonight ;-) 2) Write console/keyboard/mouse/serial drivers as these will need to be done anyways. 3) Do some verification on what works at that point. 4) Look into getting kgdb working. 5) Write ethernet/scsi drivers. 6) (fingers crossed) shell prompt... we hope... As far as I'm concerned I am severely behind schedule. I will try to get the pace going more quickly soon, I promise. Sorry. God, I'm so slow, two weeks to get the thing to half boot, sheesh! Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 8 11:23:39 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA12624; Sat, 8 Jun 1996 11:23:39 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA20038 for linux-list; Sat, 8 Jun 1996 18:23:29 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA20033 for ; Sat, 8 Jun 1996 11:23:28 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id LAA01539; Sat, 8 Jun 1996 11:22:46 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606081822.LAA01539@yon.engr.sgi.com> Subject: Re: Are you satisfied now Mr. McVoy? ;-) To: dm@neteng.engr.sgi.com (David S. Miller) Date: Sat, 8 Jun 1996 11:22:46 -0700 (PDT) Cc: linux@cthulhu.engr.sgi.com In-Reply-To: <199606081123.EAA07860@neteng.engr.sgi.com> from "David S. Miller" at Jun 8, 96 04:23:33 am Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 688 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > > >Calibrating delay loop.. ok - 91.96 BogoMIPS > Will a Triton CPU (R5000) make this better ? :-) For those who are not familiar with bogomips, my Pentium-100 at home does 39.94 bogomips. And the best number I've seen for a desktop is almost 300 bogomips for an Alpha 21064 overclocked to 300MHz. The 91.96 number for a 150MHz Indy sounds pretty good. Still, I would like to know, David: What clock factor are you using? The DEC Alphas do one clock pre instruction, so their factor is 1, why is the Indy at less than two-thirds of its clock rate? Fr more details: http://sunsite.unc.edu/linux/HOWTO/mini/BogoMips It would be nice to send them the new data... -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 09:56:40 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA25215; Mon, 10 Jun 1996 09:56:40 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA15622 for linux-list; Mon, 10 Jun 1996 16:56:35 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA15615 for ; Mon, 10 Jun 1996 09:56:34 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id JAA22016; Mon, 10 Jun 1996 09:56:33 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id JAA28660; Mon, 10 Jun 1996 09:56:22 -0700 Date: Mon, 10 Jun 1996 09:56:22 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606101656.JAA28660@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com Subject: Re: Are you satisfied now Mr. McVoy? ;-) In-Reply-To: <199606081123.EAA07860@neteng.engr.sgi.com> References: <199606081123.EAA07860@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > Calibrating delay loop.. ok - 91.96 BogoMIPS I assume this is on the target system, which should be a 133 MHZ R4600SC. From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 10:00:04 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA25259; Mon, 10 Jun 1996 10:00:04 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA16313 for linux-list; Mon, 10 Jun 1996 17:00:00 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA16307 for ; Mon, 10 Jun 1996 09:59:59 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id JAA22242; Mon, 10 Jun 1996 09:59:58 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id JAA28671; Mon, 10 Jun 1996 09:59:47 -0700 Date: Mon, 10 Jun 1996 09:59:47 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606101659.JAA28671@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com Subject: Re: well it is about time... In-Reply-To: <199606081219.FAA08535@neteng.engr.sgi.com> References: <199606081219.FAA08535@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > This port is going like a funeral procession, I apologize. Not at all--nice work. Considering some of the messy stuff you have to deal with, it is going quite well. .. > 2) Timers work, I am using the r4k counter/compare register timer > mechanism because of the bug in the i8254 Intel timer chips > on certain INDY's. The calibration of the compare offsets > needs some work but the working framework is there and needs > a little tweaking, basically my algorithm is: > > a) setup i8254 counter 0 and counter 2 such that the period > of counter 0 is the desired HZ value > b) poll counter 0 waiting for a value of 1 > c) quickly set CP0_COUNTER to zero > d) poll counter 0 for value of 1 > e) quickly read CP0_COUNTER value > > This seems to approximate the value I want in it's current form > pretty well. I have to add some fuzz factors into it and possibly > write the calibration code in assembly to get the accuracy I > want/need. When it is time to do R4000 support, I can show you how to work around the R4000 count/compare bug. (This does not apply to other processors, such as the R4600, R5000, or R10000.) From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 10:02:23 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA25357; Mon, 10 Jun 1996 10:02:23 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA16773 for linux-list; Mon, 10 Jun 1996 17:02:15 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA16758 for ; Mon, 10 Jun 1996 10:02:14 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id JAA25237; Mon, 10 Jun 1996 09:59:38 -0700 Date: Mon, 10 Jun 1996 09:59:38 -0700 Message-Id: <199606101659.JAA25237@neteng.engr.sgi.com> From: "David S. Miller" To: wje@fir.esd.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <199606101656.JAA28660@fir.esd.sgi.com> (wje@fir.esd.sgi.com) Subject: Re: Are you satisfied now Mr. McVoy? ;-) Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Mon, 10 Jun 1996 09:56:22 -0700 From: wje@fir.esd.sgi.com (William J. Earl) David S. Miller writes: > Calibrating delay loop.. ok - 91.96 BogoMIPS I assume this is on the target system, which should be a 133 MHZ R4600SC. Yes, but beware my r4k compare register calibration still needs some work, this value could be off a bit... Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 10:03:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA25452; Mon, 10 Jun 1996 10:03:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA16904 for linux-list; Mon, 10 Jun 1996 17:03:05 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA16889; Mon, 10 Jun 1996 10:03:04 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id KAA22379; Mon, 10 Jun 1996 10:03:01 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id KAA28690; Mon, 10 Jun 1996 10:02:50 -0700 Date: Mon, 10 Jun 1996 10:02:50 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606101702.KAA28690@fir.esd.sgi.com> To: ariel@cthulhu.engr.sgi.com Cc: dm@neteng.engr.sgi.com (David S. Miller), linux@cthulhu.engr.sgi.com Subject: Re: Are you satisfied now Mr. McVoy? ;-) In-Reply-To: <199606081822.LAA01539@yon.engr.sgi.com> References: <199606081123.EAA07860@neteng.engr.sgi.com> <199606081822.LAA01539@yon.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ariel Faigon writes: > > > > > >Calibrating delay loop.. ok - 91.96 BogoMIPS > > > Will a Triton CPU (R5000) make this better ? :-) An R5000 should scale with clock rate, relative to the 133 MHZ R4600 David is using. The 180 MHZ R5000 would then be 124.46. > For those who are not familiar with bogomips, my Pentium-100 > at home does 39.94 bogomips. And the best number I've seen > for a desktop is almost 300 bogomips for an Alpha 21064 > overclocked to 300MHz. The 91.96 number for a 150MHz Indy > sounds pretty good. I think the 150 MHZ R4400 is in David's host machine, with the 133 MHZ R4600 in his target machine, so the 91.96 should be for the latter. From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 10:16:08 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA25944; Mon, 10 Jun 1996 10:16:08 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA19095 for linux-list; Mon, 10 Jun 1996 17:16:00 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA19090 for ; Mon, 10 Jun 1996 10:15:59 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA25937; Mon, 10 Jun 1996 10:15:59 -0700 Date: Mon, 10 Jun 1996 10:15:59 -0700 Message-Id: <199606101715.KAA25937@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: oh btw... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk (for those not following the CVS commit mailing list...) I got the Linux graphics console working on the NEWPORT tonight, seems to work decently well... you guys make some strange graphics hardware... ;-) Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 10 17:13:53 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA11152; Mon, 10 Jun 1996 17:13:53 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA10445 for linux-list; Tue, 11 Jun 1996 00:13:41 GMT Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA10419 for ; Mon, 10 Jun 1996 17:13:38 -0700 Received: by soyuz.wellington.sgi.com (951211.SGI.8.6.12.PATCH1042/940406.SGI) for linux@cthulhu.engr.sgi.com id MAA03444; Tue, 11 Jun 1996 12:13:36 +1200 From: alambie@wellington.sgi.com (Alistair Lambie) Message-Id: <199606110013.MAA03444@soyuz.wellington.sgi.com> Subject: Is this a silly idea? To: linux@cthulhu.engr.sgi.com Date: Tue, 11 Jun 1996 12:13:36 +1200 (NZT) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 835 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Folks, I guess a lot of people will have both Linux and that other operating system on there machines for various reasons. One thing that I know I would find useful is to be able to have a filesystem that could be accessed from whichever OS you had loaded (eg. for putting mail and other common things on). I'm not sure what the best way to attack this would be, but my guess is that we need to put the common filesystem in Irix, as I would pick that it would be difficult to get the buyin to port one of our filesystems to Linux. Several questions: 1. Is this sensible (or is there already a way of doing this)? 2. If it is sensible, what should we do (type of fs etc)? 3. Does anyone know how easy this is (I'm not sure whether I'm brave enough!)? Just a thought.... Alistair PS - I get 61.64 Bogomips on a 100MHz R4600PC From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 10:36:25 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA05933; Tue, 11 Jun 1996 10:36:25 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA11086 for linux-list; Tue, 11 Jun 1996 17:36:18 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA11075 for ; Tue, 11 Jun 1996 10:36:17 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA05924; Tue, 11 Jun 1996 10:36:16 -0700 Date: Tue, 11 Jun 1996 10:36:16 -0700 Message-Id: <199606111736.KAA05924@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: my CVS tree Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I want to have my CVS tree moved into a place which is backed up often and is stable + globally accessible with ease by others. And after seeing my home directory get spammed not two days after I get here, neteng is currently _not_ the place as of now, I feel more confident having it stay on my workstation as it does indeed right now. It would be a shame to lose all the work I have done, so I'd like to take care of this soon. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 10:39:01 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA05960; Tue, 11 Jun 1996 10:39:01 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA11605 for linux-list; Tue, 11 Jun 1996 17:38:57 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA11600 for ; Tue, 11 Jun 1996 10:38:56 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA05955; Tue, 11 Jun 1996 10:38:50 -0700 Date: Tue, 11 Jun 1996 10:38:50 -0700 Message-Id: <199606111738.KAA05955@neteng.engr.sgi.com> From: "David S. Miller" To: alambie@wellington.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <199606110013.MAA03444@soyuz.wellington.sgi.com> (alambie@wellington.sgi.com) Subject: Re: Is this a silly idea? Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: alambie@wellington.sgi.com (Alistair Lambie) Date: Tue, 11 Jun 1996 12:13:36 +1200 (NZT) I'm not sure what the best way to attack this would be, but my guess is that we need to put the common filesystem in Irix, as I would pick that it would be difficult to get the buyin to port one of our filesystems to Linux. I planned on hacking xfs _and_ efs implementations into Linux. Several questions: 1. Is this sensible (or is there already a way of doing this)? 2. If it is sensible, what should we do (type of fs etc)? 3. Does anyone know how easy this is (I'm not sure whether I'm brave enough!)? Also, I wouldn't mind seeing an ext2 implementation in IRIX, I could probably hack up an initial read-only kernel module implementation in a very short amount of time. This is all only a matter of someone sitting behind the screen and whacking away at the code for 2 or 3 days, nothing more. I'd rather concentrate on getting bootstrapped at this point, but after that I'll probably hack on something like xfs/efs or whatever. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 10:48:11 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA06125; Tue, 11 Jun 1996 10:48:11 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA13132 for linux-list; Tue, 11 Jun 1996 17:48:01 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA13124 for ; Tue, 11 Jun 1996 10:47:59 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id KAA06117; Tue, 11 Jun 1996 10:47:59 -0700 Message-Id: <199606111747.KAA06117@neteng.engr.sgi.com> To: linux@neteng.engr.sgi.com Cc: jmy@neteng.engr.sgi.com From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) Subject: Re: Is this a silly idea? Date: Tue, 11 Jun 1996 10:47:59 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : I planned on hacking xfs _and_ efs implementations into Linux. We will shoot that plan in the head right away. EFS is dead technology and XFS is family jewels. If we start putting XFS into Linux, there will be hell to pay. Besides, XFS is 45K lines of code (probably more now) and it is really non trivial. Porting that to Linux would take quite a while. I would like to have an XFS port eventually, but we need to figure out a way to keep it SGI source. Last I checked, there was noise that doing stuff as a loadable module was not enough. Any news on that? I think porting ext2fs to IRIX is a much better idea. : Also, I wouldn't mind seeing an ext2 implementation in IRIX, I could : probably hack up an initial read-only kernel module implementation in : a very short amount of time. Please. I have some file system notes somewhere that talk about the data structures needed to do this. James is a good resource, he did cachefs. He's a busy, but nice, guy and he sits near you. --lm From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 11:45:46 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA07237; Tue, 11 Jun 1996 11:45:46 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA23150 for linux-list; Tue, 11 Jun 1996 18:45:37 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA23138 for ; Tue, 11 Jun 1996 11:45:36 -0700 Received: from storm.engr.sgi.com (storm.engr.sgi.com [192.26.79.92]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA07226 for ; Tue, 11 Jun 1996 11:45:35 -0700 Received: by storm.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux@neteng id LAA25628; Tue, 11 Jun 1996 11:44:13 -0700 From: "Donna Yobs" Message-Id: <9606111144.ZM25626@storm.engr.sgi.com> Date: Tue, 11 Jun 1996 11:44:12 -0700 In-Reply-To: lm@gate1-neteng (Larry McVoy) "Re: Is this a silly idea?" (Jun 11, 10:47am) References: <199606111747.KAA06117@neteng.engr.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: linux@neteng.engr.sgi.com Subject: Re: Is this a silly idea? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk lm is right, we don't want to let the xfs source out; but if we could do just the loadable modules it would show an advantage of mips technology on linux (or is that counter culture, sigh). -d -- ------------------------------------------------------------------------- Donna Derby Yobs Silicon Graphics - NSD yobs@engr.sgi.com Product Marketing From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 12:48:07 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id MAA08750; Tue, 11 Jun 1996 12:48:07 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id TAA03375 for linux-list; Tue, 11 Jun 1996 19:48:02 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id MAA03370 for ; Tue, 11 Jun 1996 12:48:01 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id MAA08744; Tue, 11 Jun 1996 12:48:00 -0700 Message-Id: <199606111948.MAA08744@neteng.engr.sgi.com> To: "Donna Yobs" From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: linux@neteng.engr.sgi.com Subject: Re: Is this a silly idea? Date: Tue, 11 Jun 1996 12:48:00 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : lm is right, we don't want to let the xfs source out; : but if we could do just the loadable modules it would : show an advantage of mips technology on linux (or is : that counter culture, sigh). We will need to do this eventually. From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 15:35:21 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA14658; Tue, 11 Jun 1996 15:35:21 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA28354 for linux-list; Tue, 11 Jun 1996 22:35:15 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA28349 for ; Tue, 11 Jun 1996 15:35:13 -0700 Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA14655 for ; Tue, 11 Jun 1996 15:35:13 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA06140; Tue, 11 Jun 1996 15:34:31 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606112234.PAA06140@yon.engr.sgi.com> Subject: Re: Is this a silly idea? To: yobs@storm.engr.sgi.com (Donna Yobs) Date: Tue, 11 Jun 1996 15:34:30 -0700 (PDT) Cc: linux@neteng.engr.sgi.com In-Reply-To: <9606111144.ZM25626@storm.engr.sgi.com> from "Donna Yobs" at Jun 11, 96 11:44:12 am Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 861 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > >lm is right, we don't want to let the xfs source out; >but if we could do just the loadable modules it would >show an advantage of mips technology on linux (or is >that counter culture, sigh). > Donna, I think this is a good realistic compromise that can be accepted both by SGI and the Linux community. On the way to "world domination now" (as Linus puts it), Linux enthusiasts must learn how to realistically compromise here and there. Think of it: a much more significant "compromise" is to support the Windows API via WINE etc. rather than trying to force the Unix APIs upon the rest of the software-developers-world and lose. With clever compromises that the commercial world can accept and by keeping the vast majority of the value under the GPL, Linux will gradually get where Linus (and some of the rest of us :-) want it to be. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 15:55:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA15626; Tue, 11 Jun 1996 15:55:16 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA00759 for linux-list; Tue, 11 Jun 1996 22:55:12 GMT Received: from storm.engr.sgi.com (storm.engr.sgi.com [192.26.79.92]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA00750 for ; Tue, 11 Jun 1996 15:55:10 -0700 Received: by storm.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) for linux id PAA26486; Tue, 11 Jun 1996 15:53:48 -0700 Date: Tue, 11 Jun 1996 15:53:48 -0700 From: yobs@storm.engr.sgi.com (Donna Yobs) Message-Id: <199606112253.PAA26486@storm.engr.sgi.com> To: linux@storm.engr.sgi.com Subject: nt... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hate to muddy the waters, but a customer has asked about getting some basic tools onto NT so that we can interop better. Hoping someone in this group may have some insight, I'm including the email. Let me know if you have any ideas. I'm trying to iron out a list of what we should do to have a better PC friendly view of the world, without going to NT. thanks -- included text -- The type of NT tools that I would be looking for is as follows: Our company writes glue to tie many of the entertainment type applications together. We have translaters, display tools, programs that scan disk directories and verify that all the frames of a shot are present, etc. For example, we have a small program that sircheck (for Solitair Image Recorder Check) that opens each frame of a shot and reads the header to make sure that all the frames are of the same resolution. If you have been doing a shot at video res and rerender at 2k resolution, It is possible that all of the frames are present, but that one of them is still the old version. The most common mistake is to copy frames 1-99 and then 101-199 skipping frame 100. Customers now have NT workstations -- whether for 3Dstudio, lightwave, Softimage, or whatever. We are being asked for the ability to execute sircheck from an NT workstation so that the files can be verified by the animator before he turns the tape over to the guy who will be shooting the shot on an SGI workstation. This utility is part of what makes our film recorder package more attractive than the competition. Failure to respond to this kind of request would make our company appear less responsive in a business that borders on the edge of custom consultation. We have been exclusively SGI based since 1984, and have very little NT experience. Most of our utilities have some kind of GL or OpenGL based GUI. I am looking for any help to run this kind of program on NT. There is no high performance graphics involved. Nor do I wish to redesign the interface to match NT style. I think I can do some of what I want with the software GL emulator that was presented for Windows 95. I need some no cost software like that GL package. In addition, I need low level stuff like what is in the developers toolbox. Readers and writers and low level chunks. For example, we need the ability to read SGI .rgb format files on NT. The net abounds with utilities for Unix type things on NT, such as tar. I spoke with the toolbox janitors about collecting these type of utilities and seeing which ones support the IRIX versions. For example, finding or adapting a public domain NT tar package such that it will easily recognize and handle the default SGI tar block sizes and byte order. Our customers are artists and animators, not computer programmers. They need the ability to read tapes, translate files, and in general, go back and forth between tools and packages without typing a 60 character command line. They need more than an NFS mounted partition shared between the SGI and NT. What good is an NFS mounted partition if you can't read the file format? The developers toolbox is a wouderful, useful, and esential effort. It contains much public stuff cleansed for use with SGI machines. I believe that if the effort is expanded to include tools for NT that would enable SGI machines to better fit into a mixed environment, our ability to sell SGI into these accounts would be greatly enhanced. Right now, I am under a lot of pressure to port our whole film recorder to NT. This would be a big project, and one I am not wild about. If I can not make it easier for SGI's and NT to co-exist, we will have to give it serious thought. I hope this answers some of your questions. I see that my sticky keyboard has played havok with my spelling. I can not seem to find a decent mail package that can work between my PC and the SGI mailhost that we have at RFX. Another example of problems working with NT and SGI. It is agravating not being able to spellcheck or to edit. Ray Feeney ------------------------------------------------------------------------- Donna Derby Yobs Silicon Graphics - NSD yobs@engr.sgi.com Product Marketing http://storm.engr From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 17:04:42 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA17294; Tue, 11 Jun 1996 17:04:42 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA12447 for linux-list; Wed, 12 Jun 1996 00:04:31 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id RAA12442 for ; Tue, 11 Jun 1996 17:04:30 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA17283; Tue, 11 Jun 1996 17:04:30 -0700 Date: Tue, 11 Jun 1996 17:04:30 -0700 Message-Id: <199606120004.RAA17283@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: I fixed the r4ktimer code... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Calibrating delay loop.. ok - 138.04 BogoMIPS Much better ;-) Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 18:11:20 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA21562; Tue, 11 Jun 1996 18:11:20 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA24805 for linux-list; Wed, 12 Jun 1996 01:11:12 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA24799 for ; Tue, 11 Jun 1996 18:11:10 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id SAA09358; Tue, 11 Jun 1996 18:11:09 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id SAA08986; Tue, 11 Jun 1996 18:11:05 -0700 Date: Tue, 11 Jun 1996 18:11:05 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606120111.SAA08986@fir.esd.sgi.com> To: "David S. Miller" Cc: linux@cthulhu.engr.sgi.com Subject: Re: I fixed the r4ktimer code... In-Reply-To: <199606120004.RAA17283@neteng.engr.sgi.com> References: <199606120004.RAA17283@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > Calibrating delay loop.. ok - 138.04 BogoMIPS > > Much better ;-) Yes, except that it should really be 133.33 on the 133 MHZ R4600SC. I don't have any idea where the 4% error would be coming from, unless there is something wrong with the external timer. One way of checking the timer might be to measure a tick of the Dallas clock/calendar chip. I believe the one we use in Indy counts 0.01 second units, so noticing the $count change over, say, a 0.5 second interval, as measured by the Dallas part, would be a way of validating the timer configuration. From owner-linux@cthulhu.engr.sgi.com Tue Jun 11 18:22:26 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA21879; Tue, 11 Jun 1996 18:22:26 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA26908 for linux-list; Wed, 12 Jun 1996 01:22:21 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA26898 for ; Tue, 11 Jun 1996 18:22:20 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAB21833; Tue, 11 Jun 1996 18:19:45 -0700 Date: Tue, 11 Jun 1996 18:19:45 -0700 Message-Id: <199606120119.SAB21833@neteng.engr.sgi.com> From: "David S. Miller" To: wje@fir.esd.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <199606120111.SAA08986@fir.esd.sgi.com> (wje@fir.esd.sgi.com) Subject: Re: I fixed the r4ktimer code... Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Tue, 11 Jun 1996 18:11:05 -0700 From: wje@fir.esd.sgi.com (William J. Earl) David S. Miller writes: > > Calibrating delay loop.. ok - 138.04 BogoMIPS > > Much better ;-) Yes, except that it should really be 133.33 on the 133 MHZ R4600SC. I don't have any idea where the 4% error would be coming from, unless there is something wrong with the external timer. One way of checking the timer might be to measure a tick of the Dallas clock/calendar chip. I believe the one we use in Indy counts 0.01 second units, so noticing the $count change over, say, a 0.5 second interval, as measured by the Dallas part, would be a way of validating the timer configuration. Peculiar... but I believe if you look at the calibrate_delay() function I sent you earlier you will see that the way it performs the calculation implies a certain error fuzz all in the name of efficiency (some time back calibrate_delay() was much more accurate but took 3 or 4 seconds to run at boot time, ugh, the lesser of two evils) The new way I calculate the r4k compare register offset is that I set the rate generation of the Intel counter at 1HZ. I then make 4 samples of how far the r4k counter goes every time the Intel counter makes a full 1 HZ iteration. I then average these 4 samples and multiply by HZ (which == 100 for the Mips port of Linux) to find the final r4k offset value that I use. Anyways, BogoMIPS is by definition "bogus" ;-) It is only used by the kernel to do quick microsecond delays in various places of the kernel. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 12 16:14:43 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA01877; Wed, 12 Jun 1996 16:14:42 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA21396 for linux-list; Wed, 12 Jun 1996 23:14:37 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA21388 for ; Wed, 12 Jun 1996 16:14:36 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA01857; Wed, 12 Jun 1996 16:14:35 -0700 Date: Wed, 12 Jun 1996 16:14:35 -0700 Message-Id: <199606122314.QAA01857@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: off topic question Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk What is a good program under IRIX for creating figures and slides? Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Wed Jun 12 16:23:55 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA01964; Wed, 12 Jun 1996 16:23:55 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA23238 for linux-list; Wed, 12 Jun 1996 23:23:51 GMT Received: from beyond.clubfed.sgi.com (beyond.clubfed.sgi.com [169.238.1.2]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA23215 for ; Wed, 12 Jun 1996 16:23:47 -0700 Received: from trinbago.clubfed.sgi.com by beyond.clubfed.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/911001.SGI) id TAA01662; Wed, 12 Jun 1996 19:22:12 -0400 Received: by trinbago.clubfed.sgi.com (940816.SGI.8.6.9/940406.SGI.AUTO) id TAA01821; Wed, 12 Jun 1996 19:44:59 -0400 From: "Kwesi Ames" Message-Id: <9606121944.ZM1819@trinbago.clubfed.sgi.com> Date: Wed, 12 Jun 1996 19:44:50 -0400 In-Reply-To: "David S. Miller" "off topic question" (Jun 12, 4:14pm) References: <199606122314.QAA01857@neteng.engr.sgi.com> X-Face: +g~UQT+z9(^"0C`fv,%E,C6_Oe)WXTlrohR/DaIIi.M1K4Q.Lov?w.b5_9)7ttP:DT)a})( Q*I&N#UNe$Tnxu^U!'P8-AbGqCG,y;#j4iO;rkEr`^$o7DmAqm5?uU8@'w88/iSrC-{4,a423@pN,7x&P7n=2@Y8{ X-Mailer: Z-Mail-SGI (3.2S.1 10apr95 MediaMail) To: "David S. Miller" , linux@cthulhu.engr.sgi.com Subject: Re: off topic question Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Jun 12, 4:14pm, David S. Miller wrote: > Subject: off topic question > > What is a good program under IRIX for creating figures and slides? > > Later, > David S. Miller > dm@sgi.com >-- End of excerpt from David S. Miller You mean other than Showcase?? Kwesi -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kwesi O. Ames Systems Engineering Support Silicon Graphics Inc. koa@sgi.com "I was one in a MILLON" corp voicemail (800) 326-1020 ext. 5-8713 phone (301) 572-3255 fax (301) 572-3280 http://reality.sgi.com/koa ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-linux@cthulhu.engr.sgi.com Wed Jun 12 16:27:35 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA02031; Wed, 12 Jun 1996 16:27:34 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA23886 for linux-list; Wed, 12 Jun 1996 23:27:31 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA23881 for ; Wed, 12 Jun 1996 16:27:29 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA02023; Wed, 12 Jun 1996 16:27:27 -0700 Date: Wed, 12 Jun 1996 16:27:27 -0700 Message-Id: <199606122327.QAA02023@neteng.engr.sgi.com> From: "David S. Miller" To: koa@trinbago.clubfed.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <9606121944.ZM1819@trinbago.clubfed.sgi.com> (koa@trinbago.clubfed.sgi.com) Subject: Re: off topic question Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: "Kwesi Ames" Date: Wed, 12 Jun 1996 19:44:50 -0400 You mean other than Showcase?? Thank you... I didn't know about showcase. ;) Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sun Jun 16 18:44:09 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA19168; Sun, 16 Jun 1996 18:44:09 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA24443 for linux-list; Mon, 17 Jun 1996 01:43:41 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA24438 for ; Sun, 16 Jun 1996 18:43:40 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA19157; Sun, 16 Jun 1996 18:43:39 -0700 Date: Sun, 16 Jun 1996 18:43:39 -0700 Message-Id: <199606170143.SAA19157@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: SHELLL PROMPT!!! Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk And some other userland utilities work as well... wheee... Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 17 13:51:15 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA16944; Mon, 17 Jun 1996 13:51:15 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA24316 for linux-list; Mon, 17 Jun 1996 20:51:09 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA24309 for ; Mon, 17 Jun 1996 13:51:08 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id NAA16930; Mon, 17 Jun 1996 13:51:07 -0700 Date: Mon, 17 Jun 1996 13:51:07 -0700 Message-Id: <199606172051.NAA16930@neteng.engr.sgi.com> From: "David S. Miller" To: linux@neteng.engr.sgi.com Subject: strace project Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I'm just curious how strace support for IRIX 6.2 is coming along? It would be _extremely_ useful and make me _extremely_ happy to have so that I can write all of the IRIX system call compatability code when I return from my talks in the U.K. on Thursday. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 17 13:58:13 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA17123; Mon, 17 Jun 1996 13:58:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA26260 for linux-list; Mon, 17 Jun 1996 20:58:06 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA26244 for ; Mon, 17 Jun 1996 13:58:04 -0700 Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id NAA17113 for ; Mon, 17 Jun 1996 13:58:04 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id NAA12238; Mon, 17 Jun 1996 13:58:03 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id NAA10393; Mon, 17 Jun 1996 13:58:02 -0700 Date: Mon, 17 Jun 1996 13:58:02 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606172058.NAA10393@fir.esd.sgi.com> To: dm@sgi.com Cc: linux@neteng.engr.sgi.com Subject: Re: strace project In-Reply-To: <199606172051.NAA16930@neteng.engr.sgi.com> References: <199606172051.NAA16930@neteng.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk David S. Miller writes: > > I'm just curious how strace support for IRIX 6.2 is coming along? > > It would be _extremely_ useful and make me _extremely_ happy to have > so that I can write all of the IRIX system call compatability code > when I return from my talks in the U.K. on Thursday. If by strace you mean tracing system call arguments and results, try using par(1). (It does not help if you want to decode argument structures, however.) Here is a sample: par -s -SS date Mon Jun 17 13:56:39 PDT 1996 0mS was sent signal SIGUSR1 0mS END-pause() errno = 4 (Interrupted system call) 0mS received signal SIGUSR1 0mS sigreturn(0x7fff2a00) OK 1mS execve(/usr/bsd/date, 0x7fff2ea8, 0x7fff2eb0) errno = 2 (No such file or directory) 1mS execve(/usr/new/date, 0x7fff2ea8, 0x7fff2eb0) errno = 2 (No such file or directory) 1mS execve(/usr/people/wje/abi-bin/date, 0x7fff2ea8, 0x7fff2eb0) errno = 2 (No such file or directory) 2mS execve(/usr/people/wje/irix-bin/date, 0x7fff2ea8, 0x7fff2eb0) errno = 2 (No such file or directory) 2mS execve(/usr/bin/date, 0x7fff2ea8, 0x7fff2eb0) OK 74mS open(/lib/rld, O_RDONLY, 04) = 3 74mS read(3, <7f 45 4c 46 01 02 01 00 00 00 00 00 00 00 00 00>..., 52) = 52 74mS lseek(3, 52, SEEK_SET) = 52 74mS read(3, <70 00 00 00 00 00 00 a0 0f b6 00 a0 0f b6 00 a0>..., 96) = 96 74mS elfmap(3, 0x7fff21bc, 2) = 0xfb60000 75mS close(3) OK 76mS getpagesize() = 4096 77mS getpid() = 10390 ppid=10389 78mS syssgi(SGI_TOSSTSAVE) OK 78mS getpagesize() = 4096 78mS brk(0x10002000) OK 80mS time() = 835044999 80mS ioctl(1, TCGETA, 0x7fff2cd8) = 0 81mS write(1, "Mon Jun 17 13:56:39 PDT 1996\n", 29) = 29 81mS prctl(PR_GETNSHARE) = 0 81mS exit(0) exit : 1 times read : 2 times write : 1 times open : 1 times close : 1 times time : 1 times brk : 1 times lseek : 1 times getpid : 1 times syssgi : 2 times ioctl : 1 times sysmp : 2 times execve : 5 times sigreturn : 1 times prctl : 1 times From owner-linux@cthulhu.engr.sgi.com Mon Jun 17 14:20:50 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA17642; Mon, 17 Jun 1996 14:20:50 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id VAA01426 for linux-list; Mon, 17 Jun 1996 21:20:44 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id OAA01414 for ; Mon, 17 Jun 1996 14:20:41 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id OAA17636; Mon, 17 Jun 1996 14:20:40 -0700 Date: Mon, 17 Jun 1996 14:20:40 -0700 Message-Id: <199606172120.OAA17636@neteng.engr.sgi.com> From: "David S. Miller" To: linux@neteng.engr.sgi.com Subject: native Linux/MIPS binaries Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I'm going to be away giving talks in the U.K. until Thursday afternoon. With that in mind I'm going to show people how they can begin to become acquainted with the work that is already done, and how to setup a cross-compilation environment both for the kernel and for userland binaries. If you want to checkout and build your own SGILinux kernels, Larry and myself have set things up so that this is possible on neteng. Just ask Larry to put you into group 'hackers' on neteng and you'll be able to check out a CVS kernel source tree. Step 1: Get added to group 'hackers' on neteng. Step 2: Make sure the following are close to the beginning of your PATH: /usr/local/gnu-cross-seb/bin These are the cross gcc/binutils utilities necessary to build a SGI Linux kernel. /hosts/neteng/usr/people/dm/install/bin These are miscellaneous GNU utilities such as CVS, GNU make, and GNU awk, which are required for the build process. Step 3: Set CVSROOT environment variable to /hosts/tanya/cvs and checkout your very own kernel. $ export CVSROOT=/hosts/tanya/cvs $ mkdir src $ cd src $ cvs checkout linux If you've had a tree for a while, or see some updates on linux-progress you would like integrated into your tree do this. $ cd src $ cvs update linux If you want to make changes to the source, and feel overly free to, specify the file to be 'committed' back into the CVS repository like this. $ cd src/linux/drivers/net $ cvs commit -m "My cool checkin message." sgiseeq.c sgiseeq.h CVS has a lot of other powerful features such as revision diffs, automatic commit conflict detection etc. Step 4: Configure and build. $ cd linux $ make oldconfig $ make dep; make clean $ make vmlinux Or if you like parallel builds (neteng can build Linux kernels in around 2 1/2 minutes flat) replace the last command with. $ make -j Step 5: If you want, boot the thing. $ cp vmlinux /usr/local/boot Go into the ARCS boot monitor prompt on the other machine and say something like >> bootp()server:vmlinux And it should at least do something interesting ;-) For userland, unfortunately, I can only point you at where the current Linux/MIPS information is located. I will be doing some detective work on native userland binaries myself when I return, but people can check it out for now if they would like to. The current main distribution site is: ftp.fnet.fr:/linux-mips/ The current library the other MIPS are using as a basis cannot be obtained from the above site, it is a pre-test release of GNU libc, you can obtain snapshots of these prereleases from: alpha.gnu.ai.mit.edu:/roland/ These are developer snapshots, so don't be surprised if it doesn't work without applying a hammer to the code/makefiles. ;-) I believe that the cross-development tools provided on ftp.fnet.fr can be used to compile the GNU libc and subsequently the userlevel binaries linked with GNU libc. The Linux/MIPS web site hasn't been talking to me lately, seems like a configuration on their end, but for reference it is: http://www.fnet.fr/linux-mips/ The documation provided there can be found at the Linux/MIPS ftp site as well I believe. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 17 15:28:36 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA23455; Mon, 17 Jun 1996 15:28:36 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA20651 for linux-list; Mon, 17 Jun 1996 22:27:38 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA20641 for ; Mon, 17 Jun 1996 15:27:37 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id PAA23297; Mon, 17 Jun 1996 15:27:36 -0700 Message-Id: <199606172227.PAA23297@neteng.engr.sgi.com> To: wje@fir.esd.sgi.com (William J. Earl) From: lm@gate1-neteng.engr.sgi.com (Larry McVoy) cc: linux@neteng.engr.sgi.com Subject: Re: strace project Date: Mon, 17 Jun 1996 15:27:36 -0700 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk : If by strace you mean tracing system call arguments and results, : try using par(1). (It does not help if you want to decode argument structures, : however.) Here is a sample: He needs to decode args. The idea was that strace groks most of the ioctls in most OS's. If we ever want to run little endian binaries on a big endian kernel (which would be kinda cool) we need the arg decode. David wanted it for something else too. --lm From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 09:41:56 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA03622; Tue, 18 Jun 1996 09:41:55 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA17045 for linux-list; Tue, 18 Jun 1996 16:41:49 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id JAA17026 for ; Tue, 18 Jun 1996 09:41:48 -0700 Received: from localhost (lm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via SMTP id JAA03609; Tue, 18 Jun 1996 09:41:47 -0700 Message-Id: <199606181641.JAA03609@neteng.engr.sgi.com> To: linux@neteng.engr.sgi.com Cc: olson@neteng.engr.sgi.com Subject: anyone know if this is true? Date: Tue, 18 Jun 1996 09:41:47 -0700 From: Larry McVoy Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk If it isn't true, can someone send mail to Tiemann and tell him the facts. Sounds like we're getting bad press. ------- Forwarded Message Date: Tue, 18 Jun 1996 05:22:52 -0700 From: Michael Tiemann To: lm@sgi.com Subject: [comp.sys.sgi.apps] gcc part II Is this not fixed in 6.2? I upgraded my machine at home yesterday, and it looked suspiciously like SGI was providing headers and libraries as part of the std 6.2 release. From: jon@vcnet.com (Jon Rust) Subject: gcc part II Newsgroups: comp.sys.sgi.apps Date: Mon, 17 Jun 1996 22:25:34 -0700 Organization: IAVC Path: cygnus.com!kithrup.com!news.Stanford.EDU!agate!howland.reston.ans.net !newsfeed.internetmci.com!in1.uu.net!news.vcnet.com!jon.vc.net!user Lines: 21 Message-ID: NNTP-Posting-Host: jon.vc.net X-Newsreader: Yet Another NewsWatcher 2.2.0b4 Before I fly off the handle, I wanna make sure this is true. You can't build ***anything*** unless you fork over a huge wad of cash to SGI for their compiler and dev enviro? **If** this is true, it's horseshit. No wonder SGI is so far down the food chain in the land of UNIX. Buying SGI could be one of the biggest mistakes I've made since openning my business over 15 months ago. I wonder if my 30 days are up. Maybe I can ship it back. I only wish I'd bought [insert any other UNIX platform here]. If it's not true, could someone plz point me in the right direction to get gcc working so I can compile BIND, RADIUS, wuftpd, etc... pissed off with no build capability, jon -------------------------------------------------------- Jon Rust Internet Access of Ventura County jon@vc.net http://www.vc.net 805.383.3500 I know that gcc is not yet 6.2-friendly, but that's much more easily fixed than the library/header problem. Michael ------- End of Forwarded Message From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 10:11:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04781; Tue, 18 Jun 1996 10:11:30 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA24241 for linux-list; Tue, 18 Jun 1996 17:11:26 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA24232; Tue, 18 Jun 1996 10:11:24 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA14821; Tue, 18 Jun 1996 10:10:31 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606181710.KAA14821@yon.engr.sgi.com> Subject: Re: anyone know if this is true? To: lm@neteng.engr.sgi.com (Larry McVoy) Date: Tue, 18 Jun 1996 10:10:31 -0700 (PDT) Cc: linux@cthulhu.engr.sgi.com, gcc@corp.sgi.com, tiemann@cygnus.com In-Reply-To: <199606181641.JAA03609@neteng.engr.sgi.com> from "Larry McVoy" at Jun 18, 96 09:41:47 am Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2672 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Sadly, it *is* true. I guess many more 6.2 pissed off customers are waiting down the pipeline. We can solve it by getting David Miller's development environment packaged as freeware, (it includes a GNU linker that works) and put it (really quick) outside the firewall for whoever is interested. 1) Someone with a couple of days of time needs to take this and just do it. I was planning on it, but I need another week or so to start. 2) I'm afraid we'll need to add crt[1n].o as binaries as these are *not* shipped with the headers and libraries of 6.2 Any comments, objections from anyone (especially for step 2) ? > >If it isn't true, can someone send mail to Tiemann and tell him the >facts. Sounds like we're getting bad press. > >------- Forwarded Message > >Date: Tue, 18 Jun 1996 05:22:52 -0700 >From: Michael Tiemann >To: lm@sgi.com >Subject: [comp.sys.sgi.apps] gcc part II > >Is this not fixed in 6.2? I upgraded my machine at home yesterday, and >it looked suspiciously like SGI was providing headers and libraries as >part of the std 6.2 release. > > From: jon@vcnet.com (Jon Rust) > Subject: gcc part II > Newsgroups: comp.sys.sgi.apps > Date: Mon, 17 Jun 1996 22:25:34 -0700 > Organization: IAVC > Path: cygnus.com!kithrup.com!news.Stanford.EDU!agate!howland.reston.ans.net >!newsfeed.internetmci.com!in1.uu.net!news.vcnet.com!jon.vc.net!user >Lines: 21 >Message-ID: >NNTP-Posting-Host: jon.vc.net >X-Newsreader: Yet Another NewsWatcher 2.2.0b4 > > Before I fly off the handle, I wanna make sure this is true. > > You can't build ***anything*** unless you fork over a huge wad of cash to > SGI for their compiler and dev enviro? > > **If** this is true, it's horseshit. No wonder SGI is so far down the food > chain in the land of UNIX. Buying SGI could be one of the biggest mistakes > I've made since openning my business over 15 months ago. I wonder if my 30 > days are up. Maybe I can ship it back. I only wish I'd bought [insert any > other UNIX platform here]. > > If it's not true, could someone plz point me in the right direction to get > gcc working so I can compile BIND, RADIUS, wuftpd, etc... > > pissed off with no build capability, > jon > > -------------------------------------------------------- > Jon Rust > Internet Access of Ventura County > jon@vc.net http://www.vc.net 805.383.3500 > >I know that gcc is not yet 6.2-friendly, but that's much more easily >fixed than the library/header problem. > >Michael > >------- End of Forwarded Message > -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 10:11:55 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04792; Tue, 18 Jun 1996 10:11:54 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA24347 for linux-list; Tue, 18 Jun 1996 17:11:51 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA24341 for ; Tue, 18 Jun 1996 10:11:49 -0700 Received: from anchor.engr.sgi.com (anchor.engr.sgi.com [192.102.117.8]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04788; Tue, 18 Jun 1996 10:11:49 -0700 Received: (from olson@localhost) by anchor.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA13973; Tue, 18 Jun 1996 10:11:49 -0700 Date: Tue, 18 Jun 1996 10:11:49 -0700 From: olson@anchor.engr.sgi.com (Dave Olson) Message-Id: <199606181711.KAA13973@anchor.engr.sgi.com> To: linux@neteng.engr.sgi.com, Larry McVoy Subject: Re: anyone know if this is true? Cc: olson@neteng.engr.sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk It's not true. All he has to do is install eoe.hdrs and compiler_eoe.hdrs. That's just the *BASE* header files. Dave Olson, Silicon Graphics Guru and busybody at large http://reality.sgi.com/olson olson@sgi.com From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 10:16:14 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04903; Tue, 18 Jun 1996 10:16:13 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA25475 for linux-list; Tue, 18 Jun 1996 17:16:09 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA25469 for ; Tue, 18 Jun 1996 10:16:08 -0700 Received: from storm.engr.sgi.com (storm.engr.sgi.com [192.26.79.92]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA04897; Tue, 18 Jun 1996 10:16:07 -0700 Received: by storm.engr.sgi.com (950413.SGI.8.6.12/940406.SGI.AUTO) id KAA11458; Tue, 18 Jun 1996 10:14:37 -0700 From: "Donna Yobs" Message-Id: <9606181014.ZM11456@storm.engr.sgi.com> Date: Tue, 18 Jun 1996 10:14:37 -0700 In-Reply-To: Larry McVoy "anyone know if this is true?" (Jun 18, 9:41am) References: <199606181641.JAA03609@neteng.engr.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Larry McVoy , linux@neteng.engr.sgi.com Subject: Re: anyone know if this is true? Cc: olson@neteng.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk You do get the basics with eoe: versions long eoe.hdr.lib shows what hdrs are on basic irix versions long eoe.hdr.lib|wc 283 1415 17711 both are default: eoe.hdr.lib [d] compiler_eoe.hdr.lib [d] -- ------------------------------------------------------------------------- Donna Derby Yobs Silicon Graphics - NSD yobs@engr.sgi.com Product Marketing From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 10:22:18 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA05141; Tue, 18 Jun 1996 10:22:18 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA27398 for linux-list; Tue, 18 Jun 1996 17:22:13 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA27374 for ; Tue, 18 Jun 1996 10:22:10 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id KAA14883; Tue, 18 Jun 1996 10:21:17 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606181721.KAA14883@yon.engr.sgi.com> Subject: Re: anyone know if this is true? To: olson@anchor.engr.sgi.com (Dave Olson) Date: Tue, 18 Jun 1996 10:21:17 -0700 (PDT) Cc: linux@cthulhu.engr.sgi.com In-Reply-To: <199606181711.KAA13973@anchor.engr.sgi.com> from "Dave Olson" at Jun 18, 96 10:11:49 am Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 869 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk > >It's not true. All he has to do is install eoe.hdrs and compiler_eoe.hdrs. > Dave, I'm afraid you're misinformed. The problem is real. Customers cannot build anything on 6.2 even if the install the above subsystems, unless they buy our IDO. I said it many times, to be able to build anything on 6.2 they still miss a linker (the GNU linker is not supported in any official GNU or Cygnus releases on any SGI and we don't include /usr/lib/crt[1n].o with our headers and libraries) David Miller has a heavily patched working GNU linker that creates Linux elf-32 binaries. He told me that it should be easy to make it produce native IRIX binaries. As for the crt[1n].o files I really hope they are not a problem to give away. >That's just the *BASE* header files. > This is correct. From the point of view of the original complaint Is not enough. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 10:35:29 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA05281; Tue, 18 Jun 1996 10:35:28 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id RAA01291 for linux-list; Tue, 18 Jun 1996 17:35:24 GMT Received: from sgi.sgi.com (sgi.engr.sgi.com [192.26.80.37]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id KAA01275; Tue, 18 Jun 1996 10:35:23 -0700 Received: from cygnus.com (cygnus.com [140.174.1.1]) by sgi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA02315; Tue, 18 Jun 1996 10:35:20 -0700 Received: from localhost.cygnus.com (axon.cygnus.com [140.174.1.116]) by cygnus.com (8.6.12/8.6.9) with ESMTP id KAA22547; Tue, 18 Jun 1996 10:35:19 -0700 Message-Id: <199606181735.KAA22547@cygnus.com> To: ariel@cthulhu.engr.sgi.com cc: lm@neteng.engr.sgi.com (Larry McVoy), linux@cthulhu.engr.sgi.com, gcc@corp.sgi.com, tiemann@cygnus.com Subject: Re: anyone know if this is true? In-reply-to: Your message of "Tue, 18 Jun 1996 10:10:31 PDT." <199606181710.KAA14821@yon.engr.sgi.com> Date: Tue, 18 Jun 1996 10:35:19 -0700 From: Michael Tiemann Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Hey Ariel, good to hear from you! It sounds to me like (1) SGI intended to make GCC a viable freeware option for Irix 6.2, (2) the support in 6.2 is not quite right, due to slight technical problems. If I understand this correctly, then I think it won't be too hard to fix the PR-related issues, and I'll be happy to chime in our support for the intended solution (whatever it may be). If SGI isn't committing to supplying a reasonable foundation to GNU (w/o ProDev or IDO), then that's another story. Michael From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 11:39:51 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA08153; Tue, 18 Jun 1996 11:39:50 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA13620 for linux-list; Tue, 18 Jun 1996 18:39:45 GMT Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA13610; Tue, 18 Jun 1996 11:39:43 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id LAA07982; Tue, 18 Jun 1996 11:39:41 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id LAA09663; Tue, 18 Jun 1996 11:39:40 -0700 Date: Tue, 18 Jun 1996 11:39:40 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606181839.LAA09663@fir.esd.sgi.com> To: ariel@cthulhu.engr.sgi.com Cc: olson@anchor.engr.sgi.com (Dave Olson), linux@cthulhu.engr.sgi.com Subject: Re: anyone know if this is true? In-Reply-To: <199606181721.KAA14883@yon.engr.sgi.com> References: <199606181711.KAA13973@anchor.engr.sgi.com> <199606181721.KAA14883@yon.engr.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Ariel Faigon writes: > > > >It's not true. All he has to do is install eoe.hdrs and compiler_eoe.hdrs. > > > Dave, I'm afraid you're misinformed. The problem is real. > Customers cannot build anything on 6.2 even if the install the above > subsystems, unless they buy our IDO. > > I said it many times, to be able to build anything on 6.2 > they still miss a linker (the GNU linker is not supported in > any official GNU or Cygnus releases on any SGI and we don't include > /usr/lib/crt[1n].o with our headers and libraries) Those files are included only in dev.sw.lib, not in irix.sw.irix_lib. I agree that they should be in the latter. ld is shipped in compiler_eoe.sw.lboot, but it is located under /usr/cpu/sysgen/root/usr/bin/. From owner-linux@cthulhu.engr.sgi.com Tue Jun 18 16:25:00 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA18230; Tue, 18 Jun 1996 16:25:00 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id XAA02396 for linux-list; Tue, 18 Jun 1996 23:24:54 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id QAA02391 for ; Tue, 18 Jun 1996 16:24:52 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id QAA15589; Tue, 18 Jun 1996 16:23:57 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606182323.QAA15589@yon.engr.sgi.com> Subject: gcc solution looks plausible (was: anyone know if this is true?) To: olson@anchor.engr.sgi.com (Dave Olson) Date: Tue, 18 Jun 1996 16:23:56 -0700 (PDT) Cc: gcc@corp.sgi.com, linux@cthulhu.engr.sgi.com In-Reply-To: <199606182106.OAA15730@anchor.engr.sgi.com> from "Dave Olson" at Jun 18, 96 02:06:24 pm Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 973 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk [I'm Ccing gcc@corp and linux@engr, some more people may be happy to hear this] Dave Olson wrote to me about 'ld': > >The one in /var/sysgen/root is the same one that driverwrap invokes. > >There are two ld's, the one in usr/lib, and the one in usr/bin. They >are different. There is a one to one match between /usr/bin/ld and >/var/sysgen/root/usr/bin/ld, and similarly for /usr/lib/ld and >/var/sysgen/root/ld > >(assuming a 32 bit system) > Thanks! that's encouraging. I assume this means that I should install two symlinks: /usr/freeware/bin/ld -> /var/sysgen/root/usr/bin/ld /usr/freeware/lib/gcc-lib/mips-sgi-irixX.Y/2.7.2/ld -> /var/sysgen/root/ld Or something close to this. This plus building gcc -with-gnu-as, using -32 -old_ld in the specs file and Bean's permission to package crt[1n].o should solve all the problems I'm aware of and make many customers happy. That was very helpful. Looks like a solution is close. Thanks again. -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Thu Jun 20 04:03:17 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA27017; Thu, 20 Jun 1996 04:03:16 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id LAA24827 for linux-list; Thu, 20 Jun 1996 11:03:06 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA24816 for ; Thu, 20 Jun 1996 04:03:05 -0700 Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id EAA27014 for ; Thu, 20 Jun 1996 04:03:02 -0700 Received: by soyuz.wellington.sgi.com (951211.SGI.8.6.12.PATCH1042/940406.SGI) for linux@neteng.engr.sgi.com id XAA02623; Thu, 20 Jun 1996 23:02:59 +1200 From: alambie@wellington.sgi.com (Alistair Lambie) Message-Id: <199606201102.XAA02623@soyuz.wellington.sgi.com> Subject: Kernel doesn't work on 200MHz Indy To: linux@neteng.engr.sgi.com Date: Thu, 20 Jun 1996 23:02:58 +1200 (NZT) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Content-Length: 694 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Just incase anyone is interested: I was able to boot Davids kernel on my Indy when I only had a 100MHz R4600PC, but know I've upgraded to a 200MHz R4400SC it dies! Looks like something to do with the memory controller... Here goes a bit of what comes out: Bad pmd in pte_alloc_kernel: 00000000 Double fault caused by invalid entries in pgd: Double fault address : ffffffffe4000000 c0_epc : ffffffff88093ebc Of course there was heaps more, but I couldn't get cut and paste to work :-) I haven't had time to have a look at what's going on yet. Cheers, Alistair PS - It only gives a BogoMIPS reading of 103.63, which is around what I got when it was a 100MHz chip. From owner-linux@cthulhu.engr.sgi.com Thu Jun 20 11:12:30 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA01257; Thu, 20 Jun 1996 11:12:29 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA16912 for linux-list; Thu, 20 Jun 1996 18:12:23 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA16875 for ; Thu, 20 Jun 1996 11:12:20 -0700 Received: from ares.esd.sgi.com (fddi-ares.engr.sgi.com [192.26.80.60]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id LAA01241 for ; Thu, 20 Jun 1996 11:12:19 -0700 Received: from fir.esd.sgi.com by ares.esd.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/950213.SGI.AUTOCF) id LAA24562; Thu, 20 Jun 1996 11:12:19 -0700 Received: by fir.esd.sgi.com (940816.SGI.8.6.9/920502.SGI.AUTO) id LAA24532; Thu, 20 Jun 1996 11:12:17 -0700 Date: Thu, 20 Jun 1996 11:12:17 -0700 From: wje@fir.esd.sgi.com (William J. Earl) Message-Id: <199606201812.LAA24532@fir.esd.sgi.com> To: alambie@wellington.sgi.com (Alistair Lambie) Cc: linux@neteng.engr.sgi.com Subject: Re: Kernel doesn't work on 200MHz Indy In-Reply-To: <199606201102.XAA02623@soyuz.wellington.sgi.com> References: <199606201102.XAA02623@soyuz.wellington.sgi.com> Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Alistair Lambie writes: > Just incase anyone is interested: > > I was able to boot Davids kernel on my Indy when I only had a 100MHz R4600PC, > but know I've upgraded to a 200MHz R4400SC it dies! Looks like something > to do with the memory controller... There is no way the kernel could work on an R4000 or R4400 without changes to the cache routines, as well as the addition of certain workarounds for processor errata. Stick to R4600 and R5000 processors for the time being. I asked David to start with the R4600, because the workarounds for the errata are far simpler, and because it and the R5000 are the volume processors for Indy. It will not be all that hard to add R4000 and R4400 support, but there are several messy workarounds to implement, so it is more interesting to get a complete system working on an R4600 or R5000. ... > PS - It only gives a BogoMIPS reading of 103.63, which is around what I got > when it was a 100MHz chip. That is to be expected. BogoMIPS is essentiall 2 times the number of times one can execute a loop like this: la a0,0x7FFFFFFF 1: bltz a0,1b addu a0,-1 On an R3000, R4600, or R5000, the branch executes in two cycles (counting one for the branch delay slot), so BogoMIPS equals the processor clock rate. On an R4000 or R4400, the branch executes in four cycles (counting one for the branch delay slot), so BogoMIPS equals one half the processor clock rate. There appears to be a small error in the current logic for calibrating the processor clock rate, which accounts for the BogoMIPS being 103.63 instead of 100.00. From owner-linux@cthulhu.engr.sgi.com Fri Jun 21 00:49:05 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA06976; Fri, 21 Jun 1996 00:49:05 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA27055 for linux-list; Fri, 21 Jun 1996 07:49:00 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA27050 for ; Fri, 21 Jun 1996 00:48:58 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA06968; Fri, 21 Jun 1996 00:48:58 -0700 Date: Fri, 21 Jun 1996 00:48:58 -0700 Message-Id: <199606210748.AAA06968@neteng.engr.sgi.com> From: "David S. Miller" To: wje@fir.esd.sgi.com CC: alambie@wellington.sgi.com, linux@neteng.engr.sgi.com In-reply-to: <199606201812.LAA24532@fir.esd.sgi.com> (wje@fir.esd.sgi.com) Subject: Re: Kernel doesn't work on 200MHz Indy Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Date: Thu, 20 Jun 1996 11:12:17 -0700 From: wje@fir.esd.sgi.com (William J. Earl) There is no way the kernel could work on an R4000 or R4400 without changes to the cache routines, as well as the addition of certain workarounds for processor errata. Stick to R4600 and R5000 processors for the time being. I asked David to start with the R4600, because the workarounds for the errata are far simpler, and because it and the R5000 are the volume processors for Indy. It will not be all that hard to add R4000 and R4400 support, but there are several messy workarounds to implement, so it is more interesting to get a complete system working on an R4600 or R5000. Heh, I go the the UK and people are trying my kernel out all over the place. This is good. I will work on the issues necessary for R4[40]00 processor support certainly. Take note that I worked to get a shell prompt on my target machine "by all means necessary" as quickly as possible so that I could have an early proof of concept to show everyone. With this there are some hard coded items in the tree that need to be attended to, but I should be able to get it all to work. One notable thing is that machines not equipped with NEWPORT graphics cards, and instead possess an INDY with the older EXPRESS graphics card, will not be able to get things working until I get the serial console up or I write a driver for the EXPRESS. Both will happen in due time. As you can see I am back from the UK, and will try to get back on track this weekend. Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 22 20:19:58 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA13640; Sat, 22 Jun 1996 20:19:58 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id DAA22390 for linux-list; Sun, 23 Jun 1996 03:19:17 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id UAA22384 for ; Sat, 22 Jun 1996 20:19:15 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id UAA13617; Sat, 22 Jun 1996 20:19:15 -0700 Date: Sat, 22 Jun 1996 20:19:15 -0700 Message-Id: <199606230319.UAA13617@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: what I am up to... Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk I've just checked in last night an initial serial driver for the INDY. Since this machine (as do some other SGI's) have the Zilog85C30 on board, I just took my Sparc driver and hacked it a little. Currently it works well as the console, and some initial tests with KGDB show that it is ok for the KGDB packets as well. KGDB needs some work on the host end of things before I can use it very much. I'm cleaning up the source tree. The end result will hopefully be a single kernel which can work flawlessly on any Mips CPU variant. I know what need to be done for this to work. In the end the goal is to be able to fire up the same Linux kernel on _any_ SGI piece of hardware and it just works, just like the Sparc kernel does. More to come... Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 24 05:25:27 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id FAA18489; Mon, 24 Jun 1996 05:25:26 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id MAA04132 for linux-list; Mon, 24 Jun 1996 12:25:19 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id FAA04127 for ; Mon, 24 Jun 1996 05:25:18 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA18480; Mon, 24 Jun 1996 05:25:17 -0700 Date: Mon, 24 Jun 1996 05:25:17 -0700 Message-Id: <199606241225.FAA18480@neteng.engr.sgi.com> From: "David S. Miller" To: linux@cthulhu.engr.sgi.com Subject: R4k taglo/taghi hardware bugs^H^H^H^Hfeatures? Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Are there any known problems with the taglo/taghi registers showing what they should after "indexed load tag secondary" cache instructions? Whatever is in both registers before the cache instruction, is still in there afterwards... I've also tried the primary-data and primary-instruction variants of the cache operations and still same results. I don't know, but it is so nice how the primary cache sizes are stored in well defined config registers in CP0, yet the secondary cache needs to be sized by complete magic and diagnostic mechanisms. The CPU knows the size of the secondary cache lines, why so difficult to put the secondary cache total size somewhere similar? (for those of you playing at home, yes I know the R5k Triton does this in the CP0 config register, but all other R4k variants do not) I've been up all night trying to figure out what (isn't) happening... Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Mon Jun 24 15:44:56 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA13863; Mon, 24 Jun 1996 15:44:56 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA29789 for linux-list; Mon, 24 Jun 1996 22:44:50 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA29784 for ; Mon, 24 Jun 1996 15:44:49 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id PAA24773 for linux; Mon, 24 Jun 1996 15:43:51 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606242243.PAA24773@yon.engr.sgi.com> Subject: External Linux/MIPS list To: linux@yon.engr.sgi.com Date: Mon, 24 Jun 1996 15:43:51 -0700 (PDT) Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2698 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk In order to prevent confidential data leaks (like random mentions of Speedracer or Lego), and in order to build critical-mass support to the Linux port outside SGI. I have created a separate linux mailing list for non-SGI interested parties. It seems that there is a lot of interest outside SGI from people who may be important assets for the Linux/MIPS effort in the future. People who sell Linux CDROMs, talented developers, etc. I enclose the welcome message for your reference. if you feel you know someone nice outside who you think should be on this list (and they agree) just subscribe them by mailing to: external-majordomo@postofc.corp.sgi.com with body: subscribe linuxmips their@email.address Once we have enough people on that list, I will send a short summary of the current status to them. Please: 1) Don't mix between linux@engr (our internal list) and linuxmips@corp (free for all) [The list-names are different on purpose.] 2) Feel free to Cc linuxmips@corp on any message that doesn't contain SGI confidential data. -- Peace, Ariel ----- Forwarded message from MAILMAN@palladium.corp.sgi.com ----- >From owner-linuxmips-outgoing@palladium.corp.sgi.com Mon Jun 24 15:25:28 1996 Date: Mon, 24 Jun 1996 15:26:21 -0700 Message-Id: <199606242226.PAA11036@palladium.corp.sgi.com> To: linuxmips@palladium.corp.sgi.com Subject: Welcome to linuxmips From: MAILMAN@palladium.corp.sgi.com Sender: owner-linuxmips@palladium.corp.sgi.com Precedence: bulk Reply-To: MAILMAN@palladium.corp.sgi.com Welcome to the linuxmips mailing list! To unsubscribe from this list send email to: external-majordomo@postofc.corp.sgi.com with the following line in the _body_ of the message: unsubscribe linuxmips _your_email_address_here_ To post a message to this mailing list use this address: linuxmips@postofc.corp.sgi.com Here's some general information for the linuxmips mailing list: Welcome to the linuxmips mailing list ! linuxmips@corp.sgi.com linuxmips will be used to update interested parties not affiliated with SGI on the status of the ongoing Linux/MIPS port within SGI. Thanks to the Linux/MIPS effort going on in Germany (thanks guys!) and to David Miller's summer's internship at SGI we expect Linux soon to be running on many SGI platforms and be able to run IRIX binaries. We intend to release the port under the GPL as a part of mainstream Linux and hope that other Linux/MIPS enthusiasts will join the effort once the first step is done and released to the net. Feel free to tell your friends about this list. -- Ariel (ariel@sgi.com) ----- End of forwarded message from MAILMAN@palladium.corp.sgi.com ----- From owner-linux@cthulhu.engr.sgi.com Mon Jun 24 18:35:45 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA18378; Mon, 24 Jun 1996 18:35:45 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA00738 for linux-list; Tue, 25 Jun 1996 01:35:40 GMT Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA00723 for ; Mon, 24 Jun 1996 18:35:37 -0700 Received: from windy.wellington.sgi.com by soyuz.wellington.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/940406.SGI) for id NAA03612; Tue, 25 Jun 1996 13:35:34 +1200 Received: (alambie@localhost) by windy.wellington.sgi.com (950413.SGI.8.6.12/8.6.9) id NAA02028 for linux@engr; Tue, 25 Jun 1996 13:35:33 +1200 From: "Alistair Lambie" Message-Id: <9606251335.ZM2026@windy.wellington.sgi.com> Date: Tue, 25 Jun 1996 13:35:33 +0000 X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: linux@cthulhu.engr.sgi.com Subject: Userland binaries Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Being miles away in New Zealand it is kind of hard to know who is doing what! I have been playing around with cross compiling userland binaries. But before I get carried away here are some questions: 1. Is anyone already doing this? 2. Should we set up a repository so we don't all spend our time doing the same thing? 3. I have used the the cross compiler from ftp.fnet.fr. The libc I have used is the gnu one that has just appeared on ftp.fnet.fr in the last week. Are these the right ones to be using (they only allow static linking)? 4. If several people are doing this maybe we should coordinate the effort so we don't all do the same packages. That should be enough questions for this week :-) Cheers, Alistair -- Alistair Lambie alambie@wellington.sgi.com Silicon Graphics New Zealand SGI Voicemail: 56791 Level 5, Walsh Wrightson Tower, Ph: +64-4-802 1455 94-96 Dixon St, Wellington, NZ Fax: +64-4-802 1459 From owner-linux@cthulhu.engr.sgi.com Tue Jun 25 06:44:36 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id GAA06332; Tue, 25 Jun 1996 06:44:35 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id NAA20004 for linux-list; Tue, 25 Jun 1996 13:44:31 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id GAA19995 for ; Tue, 25 Jun 1996 06:44:29 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id GAA06325; Tue, 25 Jun 1996 06:44:15 -0700 Date: Tue, 25 Jun 1996 06:44:15 -0700 Message-Id: <199606251344.GAA06325@neteng.engr.sgi.com> From: "David S. Miller" To: alambie@wellington.sgi.com CC: linux@cthulhu.engr.sgi.com In-reply-to: <9606251335.ZM2026@windy.wellington.sgi.com> (alambie@wellington.sgi.com) Subject: Re: Userland binaries Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: "Alistair Lambie" Date: Tue, 25 Jun 1996 13:35:33 +0000 Being miles away in New Zealand it is kind of hard to know who is doing what! I wasn't far from there last week ;-) (for those who do not know I gave two talks in Manchester England last week) I have been playing around with cross compiling userland binaries. But before I get carried away here are some questions: 1. Is anyone already doing this? Not that I know of. 2. Should we set up a repository so we don't all spend our time doing the same thing? Good idea. 3. I have used the the cross compiler from ftp.fnet.fr. The libc I have used is the gnu one that has just appeared on ftp.fnet.fr in the last week. Are these the right ones to be using (they only allow static linking)? This should be correct. That libc snapshot probably only does static binaries, the developers have initial 'hello world' type shared binaries working from what I hear so expect some more about this soon. I'll update the list on any progress on shared libraries I hear about myself. 4. If several people are doing this maybe we should coordinate the effort so we don't all do the same packages. Another good idea. ;-) Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Thu Jun 27 15:47:52 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA06305; Thu, 27 Jun 1996 15:47:51 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA13235 for linux-list; Thu, 27 Jun 1996 22:47:46 GMT Received: from soyuz.wellington.sgi.com (soyuz.wellington.sgi.com [155.11.228.1]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id PAA13222 for ; Thu, 27 Jun 1996 15:47:42 -0700 Received: from windy.wellington.sgi.com by soyuz.wellington.sgi.com via ESMTP (951211.SGI.8.6.12.PATCH1042/940406.SGI) id KAA02245; Fri, 28 Jun 1996 10:47:44 +1200 Received: (alambie@localhost) by windy.wellington.sgi.com (950413.SGI.8.6.12/8.6.9) id KAA04678; Fri, 28 Jun 1996 10:47:43 +1200 From: "Alistair Lambie" Message-Id: <9606281047.ZM4676@windy.wellington.sgi.com> Date: Fri, 28 Jun 1996 10:47:42 +0000 In-Reply-To: "David S. Miller" "Re: Userland binaries" (Jun 26, 1:44am) References: <199606251344.GAA06325@neteng.engr.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: dm@sgi.com, alambie@wellington.sgi.com Subject: Re: Userland binaries Cc: linux@cthulhu.engr.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk On Jun 26, 1:44am, David S. Miller wrote: > Subject: Re: Userland binaries > From: "Alistair Lambie" > Date: Tue, 25 Jun 1996 13:35:33 +0000 > > Being miles away in New Zealand it is kind of hard to know who is > doing what! > > I wasn't far from there last week ;-) (for those who do not know I > gave two talks in Manchester England last week) > Yeah...only another 24 hours flying and you too could have been here. > I have been playing around with cross compiling userland binaries. > But before I get carried away here are some questions: > > 1. Is anyone already doing this? > > Not that I know of. > Judging by the resounding silence I guess you are correct! > 2. Should we set up a repository so we don't all spend our time > doing the same > thing? > > Good idea. > Can someone point me at a place (I could host here, but it seems crazy for everyone to try suck everything up a 64k pipe...of course this assumes that people are actually interested!!). > 4. If several people are doing this maybe we should coordinate the > effort so > we don't all do the same packages. > > Another good idea. ;-) So far I've done sh-utils and file-utils. Next I'm planning on SYSVinit and whatever packages have getty/login/security. Then some more shells and an editor. I guess after that the next thing might be some of the networking stuff. I'm using the RedHat SRPMS for this, and applying their patches unless they are platform specific. Does anyone have any wild objections to this? Also, what format would people prefer for packages...just tar.gz or RPM? (guess this also raises the point that I need to do some binaries to deal with however we package things!) Cheers, Alistair -- Alistair Lambie alambie@wellington.sgi.com Silicon Graphics New Zealand SGI Voicemail: 56791 Level 5, Walsh Wrightson Tower, Ph: +64-4-802 1455 94-96 Dixon St, Wellington, NZ Fax: +64-4-802 1459 From owner-linux@cthulhu.engr.sgi.com Sat Jun 29 00:07:58 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA17310; Sat, 29 Jun 1996 00:07:58 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA04533 for linux-list; Sat, 29 Jun 1996 07:07:54 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id AAA04526 for ; Sat, 29 Jun 1996 00:07:52 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id AAA17304; Sat, 29 Jun 1996 00:07:52 -0700 Date: Sat, 29 Jun 1996 00:07:52 -0700 Message-Id: <199606290707.AAA17304@neteng.engr.sgi.com> From: "David S. Miller" To: linux@neteng.engr.sgi.com Subject: NIS rarpd entries Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk When I'm booting my test box I have to run a bogus hacked up copy of rarpd because the NIS maps in my domain don't have an ethers entry for stacey.engr What is a better way of dealing with this? Later, David S. Miller dm@sgi.com From owner-linux@cthulhu.engr.sgi.com Sat Jun 29 18:27:31 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA26278; Sat, 29 Jun 1996 18:27:31 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id BAA04482 for linux-list; Sun, 30 Jun 1996 01:27:26 GMT Received: from yon.engr.sgi.com (yon.engr.sgi.com [150.166.61.32]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA04477 for ; Sat, 29 Jun 1996 18:27:24 -0700 Received: (from ariel@localhost) by yon.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id SAA01788; Sat, 29 Jun 1996 18:26:23 -0700 From: ariel@yon.engr.sgi.com (Ariel Faigon) Message-Id: <199606300126.SAA01788@yon.engr.sgi.com> Subject: NIS rarpd entries (fwd) To: dpinto@yon.engr.sgi.com (Demetrio Pinto) Date: Sat, 29 Jun 1996 18:26:23 -0700 (PDT) Cc: linux@cthulhu.engr.sgi.com Reply-To: ariel@cthulhu.engr.sgi.com Organization: Silicon Graphics Inc. X-Mailer: ELM [version 2.4 PL24 ME5a] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 814 Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk Demetrio, Will it be possible to add an ethers entry for stacey.engr to our ypmaps ? Thanks! If yes, David, could you send Demetrio the ethernet address ? ----- Forwarded message from David S. Miller ----- >From owner-linux@cthulhu Sat Jun 29 00:07:01 1996 Date: Sat, 29 Jun 1996 00:07:52 -0700 Message-Id: <199606290707.AAA17304@neteng.engr.sgi.com> From: "David S. Miller" To: linux@neteng Subject: NIS rarpd entries Reply-to: dm@sgi.com Sender: owner-linux@cthulhu Precedence: bulk When I'm booting my test box I have to run a bogus hacked up copy of rarpd because the NIS maps in my domain don't have an ethers entry for stacey.engr What is a better way of dealing with this? Later, David S. Miller dm@sgi.com ----- End of forwarded message from David S. Miller ----- -- Peace, Ariel From owner-linux@cthulhu.engr.sgi.com Sat Jun 29 22:39:46 1996 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA16738; Sat, 29 Jun 1996 22:39:46 -0700 Return-Path: Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id FAA23565 for linux-list; Sun, 30 Jun 1996 05:39:41 GMT Received: from neteng.engr.sgi.com (neteng.engr.sgi.com [192.26.80.10]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id WAA23560; Sat, 29 Jun 1996 22:39:39 -0700 Received: (from dm@localhost) by neteng.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id WAA16730; Sat, 29 Jun 1996 22:39:38 -0700 Date: Sat, 29 Jun 1996 22:39:38 -0700 Message-Id: <199606300539.WAA16730@neteng.engr.sgi.com> From: "David S. Miller" To: ariel@cthulhu.engr.sgi.com CC: dpinto@yon.engr.sgi.com, linux@cthulhu.engr.sgi.com In-reply-to: <199606300126.SAA01788@yon.engr.sgi.com> (ariel@yon) Subject: Re: NIS rarpd entries (fwd) Reply-to: dm@sgi.com Sender: owner-linux@cthulhu.engr.sgi.com Precedence: bulk From: ariel@yon (Ariel Faigon) Date: Sat, 29 Jun 1996 18:26:23 -0700 (PDT) Will it be possible to add an ethers entry for stacey.engr to our ypmaps ? Thanks! If yes, David, could you send Demetrio the ethernet address ? 8:0:69:8:8a:18 stacey.engr.sgi.com Later, David S. Miller dm@sgi.com