: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.