From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Shawn Jin <shawnxjin@gmail.com>
Cc: Tomasz Chmielewski <mangoo@wpkg.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Force a usb drive to be /dev/sda?
Date: Fri, 13 Jun 2008 23:54:52 +0200 [thread overview]
Message-ID: <4852ECAC.9060106@s5r6.in-berlin.de> (raw)
In-Reply-To: <c3d0340b0806131329n604b11bcv5dce0985580516fc@mail.gmail.com>
Shawn Jin wrote:
>>> The bootloader I'm using is LILO. So I have to specify the boot device
>>> and the root device in lilo.conf. For example, boot=/dev/sda,
>>> root=/dev/sda1. I'm not sure how mounting filesystem by UUID or by
>>> label can help. A little bit elaboration will be more helpful.
>> Ah I forgot that... Looks like this requires an initrd too, though without
>> special scripts of your own.
>
> Forgive my slowness to understand your suggestion. The kernel I built
> has all the sata drivers, usb drivers, and scsi layer built in. So
> during the kernel bootup before the root is mounted, all drives (sata
> and usb) are scanned and detected. How does an initrd plus mounting
> the root filesystem by UUID or label help here? Or how can I set the
> "root" in the lilo.conf?
I haven't used lilo for a while, nor initrd, hence I can't give you a
detailed recipe. You specify the initrd as device with root filesystem
to the boot manager. In the initrd you have e.g. an fstab by which you
mount the later root filesystem based on the filesystem ID. Then the
initrd chroots to that fs.
> If an initrd is used, I would rather go with option 3. That is, build
> SATA drivers as loadable modules and load them in the initrd. Then
> before initrd loads sata drivers, there is only one usb drive as
> /dev/sda.
In that case you don't need an initrd at all.
> Also I'm lost by this comment: "though without special scripts of your
> own". Could you explain it in another way? Were you saying that I need
> my own special scripts to mount the root filesystem by UUID or label?
> I think this is quite obvious since I need to build an initrd, which
> is always customized. :-P
A little bit more would be necessary if the initrd had to pick up device
IDs. If you just use the initrd to load some modules and to mount the
subsequent root fs, it won't really look different from most distributor
initrds AFAICS.
--
Stefan Richter
-=====-==--- -==- -==-=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-06-13 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 8:35 Force a usb drive to be /dev/sda? Tomasz Chmielewski
2008-06-12 11:11 ` Stefan Richter
2008-06-13 5:32 ` Shawn Jin
2008-06-13 6:35 ` Stefan Richter
2008-06-13 20:29 ` Shawn Jin
2008-06-13 21:54 ` Stefan Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-12 6:05 Shawn Jin
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=4852ECAC.9060106@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.org \
--cc=shawnxjin@gmail.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