From: Flavio Bruno Leitner <fbl@conectiva.com.br>
To: Valdis.Kletnieks@vt.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel/initrd and rootfs over LVM
Date: Thu, 23 Oct 2003 14:52:39 -0300 [thread overview]
Message-ID: <20031023175239.GF21031@conectiva.com.br> (raw)
In-Reply-To: <200310231556.h9NFuGqm007878@turing-police.cc.vt.edu>
On Thu, Oct 23, 2003 at 11:56:16AM -0400, Valdis.Kletnieks@vt.edu wrote:
> What I ended up doing to get that working back in the 2.5.4x days was to have
> my initrd's linuxrc do a 'lvm vgscan' to get the volume group online, and then
> an 'lvdisplay' - this of course wedged up after it since there wasn't a proper
> root=, but it revealed the numbers I needed.
It's an option, but I was thinking if there is no way to
name_to_dev_t() handle this case, so all rootfs devices
will uses the same syntax.
> As far as I can tell, if you're using the device-mapper in 2.6, you'll want
> MAJOR=, and then the MINOR= seems to be stable across 2.4/2.6/lvm1/lvm2 (So if
> you're building the system under 2.4 and have LVM running there, you can get
> the minor number from lvdisplay there, and use it with major=254 to get your
> 2.6 up and running. For lilo, I ended up using this:
>
> root=65029
> # magic number is major=254 * 256 + minor=5
It works too. It's just hard to upgrade many machines when you
already have root=/dev/vg../lv.. at grub config.
--
Flávio Bruno Leitner <fbl@conectiva.com.br>
[ E74B 0BD0 5E05 C385 239E 531C BC17 D670 7FF0 A9E0 ]
prev parent reply other threads:[~2003-10-23 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 16:44 kernel/initrd and rootfs over LVM Flavio Bruno Leitner
2003-10-23 15:56 ` Valdis.Kletnieks
2003-10-23 17:52 ` Flavio Bruno Leitner [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=20031023175239.GF21031@conectiva.com.br \
--to=fbl@conectiva.com.br \
--cc=Valdis.Kletnieks@vt.edu \
--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;
as well as URLs for NNTP newsgroup(s).