Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: linux@yon.engr.sgi.com, davem@caip.rutgers.edu (David)
Subject: Re: Hello world!
Date: Thu, 13 Mar 1997 16:18:06 -0800 (PST)	[thread overview]
Message-ID: <199703140018.QAA20671@yon.engr.sgi.com> (raw)
In-Reply-To: <9703141124.ZM7712@windy.wellington.sgi.com> from "Alistair Lambie" at Mar 14, 97 11:24:41 am

:
:On Mar 14, 10:32am, Mike Shaver wrote:
:> Subject: Hello world!
:> Looks like I'm getting an Indy when I get back to Ottawa next week, so
:> I'd like to hear from others (hello?) as to what kind of work we're
:> looking at in the short term.
:>

The goals are:
	0) Complete the merge with mainstream Linux
	   (David left at 2.0.11 or so) which I assume
	   Ralf has already done or doing.

	1) Get the Indy to boot linux from a _local_ disk
	   Ralf and Miguel were looking into SILO here.

	2) Get gcc to work native of Linux/Indy

As Alistair said, David already got the WD SCSI driver to work
and he was booting to multiuser and even running GNU emacs
on his Linux Indy.  But this was done using:

	1) Cross builds (gcc-cross was running on IRIX 6.2
	   and producing Linux ELF-32 binaries).

	2) Booting was never local. It was always using the
	   ARC prom bootp command.

	3) The target Linux/Indy filesystems were NFS mounted.

Basically we need to mkfs.ext2(8) on the local Indy (as IRIX
supports XFS and EFS both of which are proprietary, Sigh)
It would be best to have a seprate disk (rather than a
partition which may disappear in case of human error)
Get SILO to work, get the latest gcc to work native
and we can start working on userland.

Asking David some questions might be a good idea too.
I'm not sure he is currently on the list, I'll ask
him if he's interested to join.

:>
:> I understand that we're looking to get a source repository out on the
:> 'net, which would be a good start.  What are people planning to start
:> with first?  (I suppose talking to disks is a priority... =) )
:>

Larry and I are working on setting up linux.sgi.com outside the
SGI firewall. My intention is to set up tcpwrappers so that only
the developers (Ralf, Miguel, Mike) and SGI people could login
and give you complete control of the machine. At which point
you can install ssh or whatever and start sharing sources.

The "official" initial post-David merged source tree should
come from Ralf.

-- 
Peace, Ariel

WARNING: multiple messages have this Message-ID (diff)
From: ariel@yon.engr.sgi.com (Ariel Faigon)
To: linux@yon.engr.sgi.com, David <davem@caip.rutgers.edu>
Subject: Re: Hello world!
Date: Thu, 13 Mar 1997 16:18:06 -0800 (PST)	[thread overview]
Message-ID: <199703140018.QAA20671@yon.engr.sgi.com> (raw)
Message-ID: <19970314001806.H-N1OPsMrZrO6Ymx2XAOQ0ec6VIsKIQMJARNphFL4EM@z> (raw)
In-Reply-To: <9703141124.ZM7712@windy.wellington.sgi.com> from "Alistair Lambie" at Mar 14, 97 11:24:41 am

:
:On Mar 14, 10:32am, Mike Shaver wrote:
:> Subject: Hello world!
:> Looks like I'm getting an Indy when I get back to Ottawa next week, so
:> I'd like to hear from others (hello?) as to what kind of work we're
:> looking at in the short term.
:>

The goals are:
	0) Complete the merge with mainstream Linux
	   (David left at 2.0.11 or so) which I assume
	   Ralf has already done or doing.

	1) Get the Indy to boot linux from a _local_ disk
	   Ralf and Miguel were looking into SILO here.

	2) Get gcc to work native of Linux/Indy

As Alistair said, David already got the WD SCSI driver to work
and he was booting to multiuser and even running GNU emacs
on his Linux Indy.  But this was done using:

	1) Cross builds (gcc-cross was running on IRIX 6.2
	   and producing Linux ELF-32 binaries).

	2) Booting was never local. It was always using the
	   ARC prom bootp command.

	3) The target Linux/Indy filesystems were NFS mounted.

Basically we need to mkfs.ext2(8) on the local Indy (as IRIX
supports XFS and EFS both of which are proprietary, Sigh)
It would be best to have a seprate disk (rather than a
partition which may disappear in case of human error)
Get SILO to work, get the latest gcc to work native
and we can start working on userland.

Asking David some questions might be a good idea too.
I'm not sure he is currently on the list, I'll ask
him if he's interested to join.

:>
:> I understand that we're looking to get a source repository out on the
:> 'net, which would be a good start.  What are people planning to start
:> with first?  (I suppose talking to disks is a priority... =) )
:>

Larry and I are working on setting up linux.sgi.com outside the
SGI firewall. My intention is to set up tcpwrappers so that only
the developers (Ralf, Miguel, Mike) and SGI people could login
and give you complete control of the machine. At which point
you can install ssh or whatever and start sharing sources.

The "official" initial post-David merged source tree should
come from Ralf.

-- 
Peace, Ariel

  reply	other threads:[~1997-03-14  0:21 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-03-13 22:10 Hello world! Mike Shaver
     [not found] ` <shaver@neon.ingenia.ca>
1997-03-14 11:24   ` Alistair Lambie
1997-03-14  0:18     ` Ariel Faigon [this message]
1997-03-14  0:18       ` Ariel Faigon
1997-03-14  8:45       ` David S. Miller
1997-05-27 19:45   ` strace/truss equiv? Christopher W. Carlson
1997-05-28 18:56   ` Dynapenguin! Seth Morabito
1997-05-28 19:10     ` Dynapenguin! Mike Shaver
1997-05-28 19:10       ` Dynapenguin! Mike Shaver
1997-07-18 19:00   ` Pointers on how to get started richard offer
1997-07-21  7:10     ` Martin Knoblauch
1997-08-15 21:17   ` Power Series? richard offer
  -- strict thread matches above, loose matches on Subject: below --
1997-05-22 19:13 small world Mike Shaver
1997-05-25  3:21 ` Ralf Baechle
1997-05-25  3:21   ` Ralf Baechle
     [not found]   ` <ralf@mailhost.uni-koblenz.de>
1997-05-27  3:01     ` Christopher W. Carlson
1997-05-27 21:07     ` strace/truss equiv? Seth Morabito
1997-05-26  7:48 ` small world Martin Knoblauch
1997-05-27 19:19 strace/truss equiv? Mike Shaver
1997-05-27 19:37 ` Luc Chouinard
1997-05-27 19:42 ` John E. Schimmel
1997-05-27 19:42   ` John E. Schimmel
1997-05-27 20:01   ` Mike Shaver
1997-05-27 20:01     ` Mike Shaver
1997-05-27 19:48 ` Ariel Faigon
1997-05-27 19:48   ` Ariel Faigon
1997-05-27 20:37 ` Ralf Baechle
1997-05-27 20:37   ` Ralf Baechle
1997-05-27 20:50   ` Mike Shaver
1997-05-27 20:50     ` Mike Shaver
1997-05-27 20:58     ` Ralf Baechle
1997-05-27 20:58       ` Ralf Baechle
1997-05-28 18:37 Dynapenguin! Mike Shaver
1997-07-18 16:54 Pointers on how to get started Emmanuel Mogenet
1997-07-18 17:32 ` Ariel Faigon
1997-07-18 17:32   ` Ariel Faigon
1997-07-18 17:32 ` Alex deVries
1997-07-18 18:13   ` Mike Shaver
1997-07-18 18:13     ` Mike Shaver
1997-07-18 18:43     ` Alex deVries
1997-07-18 18:46       ` Mike Shaver
1997-07-18 18:46         ` Mike Shaver
1997-07-18 20:45   ` Alan Cox
1997-07-18 20:45     ` Alan Cox
1997-07-21  3:36   ` Miguel de Icaza
1997-08-15 20:20 Power Series? Mike Shaver
1997-08-15 20:20 ` Mike Shaver
1997-08-15 20:36 ` Steve Rikli
1997-08-15 20:36   ` Steve Rikli
1997-08-15 20:47   ` Alex deVries
1997-08-15 20:54   ` Mike Shaver
1997-08-15 20:54     ` Mike Shaver
1997-08-16  0:51 ` David Kennedy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199703140018.QAA20671@yon.engr.sgi.com \
    --to=ariel@yon.engr.sgi.com \
    --cc=ariel@cthulhu.engr.sgi.com \
    --cc=davem@caip.rutgers.edu \
    --cc=linux@yon.engr.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox