From: Mike Shaver <shaver@netscape.com>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: root-be-0.03.tar.gz
Date: Wed, 21 Jan 1998 19:38:31 +0000 [thread overview]
Message-ID: <34C64EB7.1FA95A9C@netscape.com> (raw)
In-Reply-To: Pine.LNX.3.95.980121135323.22712E-100000@lager.engsoc.carleton.ca
Alex deVries wrote:
> I can already see some things that should go into 0.04..
It would be nice if there was a really minimal root-be with just enough
to get a network configured and then start pulling stuff down via RPM.
That was my goal with the Linux-installer, although we could have two
versions, too.
> Some things to work on:
> - get a more modern version of vmlinux with efs for both scache'd and
> non-scache'd machines
I _must_ start working on EFS again. I assume I've missed the 2.2
freeze, but I could still help a lot of people by getting off my a** and
finishing it. My apologies to those who are waiting on it.
> - make Linux-installer-0.1c with root-be-0.03.tar.gz (with Mike's
> permission)
Sold!
Note that you'll have to make a cpio of it, because that's all the
installer understands. Also, if you talk to Alan about how to fix the
installer to do devices correctly, things will get a little simpler.
> - document all this (damn, I wish I had another SCSI disk to practice
> installs)
I have one, and the work Indy survived the layoffs (woohoo!), so I'll be
back to work on that stuff shortly (cross your fingers =) ).
Mike
--
509756.92 504401.08
next prev parent reply other threads:[~1998-01-21 19:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-21 18:59 root-be-0.03.tar.gz Alex deVries
1998-01-21 19:38 ` Mike Shaver [this message]
1998-01-21 20:26 ` root-be-0.03.tar.gz Alan Cox
1998-01-21 20:26 ` root-be-0.03.tar.gz Alan Cox
1998-01-22 6:04 ` root-be-0.03.tar.gz Alex deVries
1998-01-22 6:11 ` root-be-0.03.tar.gz Mike Shaver
1998-01-22 12:04 ` root-be-0.03.tar.gz Oliver Frommel
1998-01-22 18:18 ` root-be-0.03.tar.gz William J. Earl
1998-01-23 3:57 ` root-be-0.03.tar.gz ralf
1998-01-23 17:43 ` root-be-0.03.tar.gz William J. Earl
1998-01-23 22:24 ` root-be-0.03.tar.gz Thomas Bogendoerfer
1998-01-24 13:16 ` root-be-0.03.tar.gz ralf
1998-01-25 11:47 ` root-be-0.03.tar.gz Thomas Bogendoerfer
1998-01-22 10:29 ` root-be-0.03.tar.gz Alan Cox
1998-01-22 10:29 ` root-be-0.03.tar.gz Alan Cox
1998-01-22 20:39 ` root-be-0.03.tar.gz Alistair Lambie
1998-01-22 21:37 ` root-be-0.03.tar.gz William J. Earl
1998-01-22 22:18 ` root-be-0.03.tar.gz Alistair Lambie
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=34C64EB7.1FA95A9C@netscape.com \
--to=shaver@netscape.com \
--cc=adevries@engsoc.carleton.ca \
--cc=linux@cthulhu.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