From: Mike Shaver <shaver@neon.ingenia.ca>
To: alan@lxorguk.ukuu.org.uk (Alan Cox)
Cc: miguel@nuclecu.unam.mx, ariel@sgi.com, linux@cthulhu.engr.sgi.com
Subject: Re: boot linux - wish
Date: Sat, 16 Aug 1997 10:15:48 -0400 (EDT) [thread overview]
Message-ID: <199708161415.KAA31361@neon.ingenia.ca> (raw)
In-Reply-To: <m0wzheO-0005FiC@lightning.swansea.linux.org.uk> from Alan Cox at "Aug 16, 97 01:08:12 pm"
Thus spake Alan Cox:
> > If I stick all the RH stuff in an initrd and then they do FTP install,
> > then they should be able to use it via boot /vmlinux or boot -f
> > bootp()..., no?
>
> 2.1.4x blows up with an initrd - hopefully fixed in 2.1.50/soon but that
> means the SGI one will corrupt and explode atm
I thought Ijust saw something from Bill Hawes cross the list that
addressed that, actually. Regardless, they've got at least a week to
get 2.1.x playing nicely with initrds before I'll get a chance to use
it on the Indy. The initrd stuff is the trivial part, and should
operate identically to having it mounted via NFS-root.
Thanks for the warning, though.
Mike
--
#> Mike Shaver (shaver@ingenia.com) Ingenia Communications Corporation
#> Chief System Architect -- will tame sendmail(8) for food
#>
#> "You are a very perverse individual, and I think I'd like to get to
#> know you better." --- eric@reference.com
WARNING: multiple messages have this Message-ID (diff)
From: Mike Shaver <shaver@neon.ingenia.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: miguel@nuclecu.unam.mx, ariel@sgi.com, linux@cthulhu.engr.sgi.com
Subject: Re: boot linux - wish
Date: Sat, 16 Aug 1997 10:15:48 -0400 (EDT) [thread overview]
Message-ID: <199708161415.KAA31361@neon.ingenia.ca> (raw)
Message-ID: <19970816141548.4W-PdNRWcKIRBIgoq3KOp0XYjWlhaPUTdq-jQku50fU@z> (raw)
In-Reply-To: <m0wzheO-0005FiC@lightning.swansea.linux.org.uk> from Alan Cox at "Aug 16, 97 01:08:12 pm"
Thus spake Alan Cox:
> > If I stick all the RH stuff in an initrd and then they do FTP install,
> > then they should be able to use it via boot /vmlinux or boot -f
> > bootp()..., no?
>
> 2.1.4x blows up with an initrd - hopefully fixed in 2.1.50/soon but that
> means the SGI one will corrupt and explode atm
I thought Ijust saw something from Bill Hawes cross the list that
addressed that, actually. Regardless, they've got at least a week to
get 2.1.x playing nicely with initrds before I'll get a chance to use
it on the Indy. The initrd stuff is the trivial part, and should
operate identically to having it mounted via NFS-root.
Thanks for the warning, though.
Mike
--
#> Mike Shaver (shaver@ingenia.com) Ingenia Communications Corporation
#> Chief System Architect -- will tame sendmail(8) for food
#>
#> "You are a very perverse individual, and I think I'd like to get to
#> know you better." --- eric@reference.com
next prev parent reply other threads:[~1997-08-16 14:23 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-15 20:17 boot linux - wish Ariel Faigon
1997-08-15 20:17 ` Ariel Faigon
1997-08-15 20:23 ` Mike Shaver
1997-08-15 21:47 ` Miguel de Icaza
1997-08-15 22:03 ` Alex deVries
1997-08-16 1:05 ` Mike Shaver
1997-08-16 1:05 ` Mike Shaver
1997-08-16 12:08 ` Alan Cox
1997-08-16 12:08 ` Alan Cox
1997-08-16 14:15 ` Mike Shaver [this message]
1997-08-16 14:15 ` Mike Shaver
1997-08-16 20:33 ` Ralf Baechle
1997-08-16 20:33 ` Ralf Baechle
1997-08-15 20:38 ` Alex deVries
1997-08-15 20:53 ` Mike Shaver
1997-08-15 20:53 ` Mike Shaver
1997-08-15 20:59 ` Alex deVries
1997-08-19 10:38 ` Oliver Frommel
1997-08-15 21:46 ` Miguel de Icaza
1997-08-16 5:08 ` Eric Kimminau
1997-08-16 6:18 ` Ralf Baechle
1997-08-16 6:18 ` Ralf Baechle
1997-08-16 20:25 ` Miguel de Icaza
1997-08-16 21:54 ` Vincent Renardias
1997-08-16 22:07 ` Ralf Baechle
1997-08-16 22:07 ` Ralf Baechle
1997-08-17 12:33 ` Alan Cox
1997-08-17 12:33 ` Alan Cox
1997-08-18 4:25 ` Kernel with working initrd? Alex deVries
1997-08-19 1:37 ` Current problems Alex deVries
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=199708161415.KAA31361@neon.ingenia.ca \
--to=shaver@neon.ingenia.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ariel@sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=miguel@nuclecu.unam.mx \
/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