From: Dan Kegel <dank@kegel.com>
To: Andrew McGregor <andrew@indranet.co.nz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: FAQ: how to boot with root=LABEL=/
Date: Sat, 28 Dec 2002 22:11:53 -0800 [thread overview]
Message-ID: <3E0E9229.6070404@kegel.com> (raw)
In-Reply-To: <57400000.1041112349@localhost.localdomain>
I'll just pass the device for now, but I appreciate the
explanation, and maybe it'll help the next fellow who runs into this.
- Dan
Andrew McGregor wrote:
> You need to build an initrd for that to work. That is actually handled
> by the scripts in the initrd, so without those...
>
> One workaround to get the ramdisk without having to use modules goes
> like this:
>
> Do a make modules_install anyway. That sets up the directory layout in
> /lib/modules, without which mkinitrd fails. Remove any modules that get
> installed (2.4 makefiles will probably build and install modules even if
> CONFIG_MODULES is not set).
>
> Then build the kernel and do a make install, and the /sbin/installkernel
> script will do the right thing.
>
> Not tested, but given my understanding of how RH8 boots, should work.
>
> Or else just pass the device.
>
> Andrew
>
> --On Saturday, December 28, 2002 11:12:13 -0800 Dan Kegel
> <dank@kegel.com> wrote:
>
>> I'm trying to configure a minimal 2.4.17 to boot
>> on my redhat 8 box. No modules, no sound, nothing fancy at all.
>>
>> One problem I'm having is it only works if I boot with root=/dev/hda9
>> instead of red hat's usual root=LABEL=/
>> I thought I had configured in the proper partition support.
>>
>> Can anyone point out what's missing from my .config (or from 2.4.17)
>> to allow booting with root=LABEL=/ ?
--
Dan Kegel
Linux User #78045
http://www.kegel.com
prev parent reply other threads:[~2002-12-29 5:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 19:12 FAQ: how to boot with root=LABEL=/ Dan Kegel
2002-12-28 21:49 ` Andreas Dilger
2002-12-28 21:52 ` Andrew McGregor
2002-12-29 6:11 ` Dan Kegel [this message]
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=3E0E9229.6070404@kegel.com \
--to=dank@kegel.com \
--cc=andrew@indranet.co.nz \
--cc=linux-kernel@vger.kernel.org \
/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