From: Ulf Bartelt <ulf@twc.de>
To: linux-lvm@msede.com
Subject: Re: [linux-lvm] SuSE/LVM boot problem
Date: Wed, 03 May 2000 12:05:58 +0200 [thread overview]
Message-ID: <390FFA06.F5EBA4F0@twc.de> (raw)
In-Reply-To: 20000502232221.A20803@gondor.com
Jan Niehusmann wrote:
> I can imagine two ways to make lilo work with lvm:
>
> 1) at install time (when you run /sbin/lilo), lilo maps the logical (lvm)
> locations to physical locations and writes these to the boot block. The boot
> code doesn't need to be changed.
>
> 2) lilo writes logical locations to the boot block (trivial). The boot
> code needs to understand lvm.
While waiting for either 1 or 2 you could use 3:
3) Make /boot and / contiguous and remember not to move them until lvm
has a non-moveable flag. Calculate the physical start and the length in
sectors of /boot and /, fake them into your partition table and use
these "partition aliases" to boot and use these filesystems...
...and don�t forget to give lilo an append="..." line defining the real
geometry of your drive as linux�s geometry guessing will give strange
results with such aliases not starting on cylinder boundaries...
This hack works fine for me since end of november 1999.
Better explanations are at http://www.freenet.de/y.e.t.i./
next prev parent reply other threads:[~2000-05-03 10:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-02 5:20 [linux-lvm] SuSE/LVM boot problem Marco Shaw
2020-11-27 16:17 ` Michael Marxmeier
2000-05-02 18:41 ` dgould
2000-05-02 21:22 ` Jan Niehusmann
2000-05-02 22:18 ` Heinz Mauelshagen
2000-05-03 10:05 ` Ulf Bartelt [this message]
2000-05-31 8:40 ` Andi Kleen
2000-05-03 0:15 ` Marco Shaw
2000-05-03 7:38 Michael Marxmeier
2000-05-03 16:53 ` dgould
2000-05-31 9:01 ` Andi Kleen
2000-05-31 16:13 ` Christoph Hellwig
2000-05-31 16:18 ` Andi Kleen
2000-05-31 18:25 ` Michael Marxmeier
2000-06-01 12:15 ` Ulf Bartelt
2000-06-01 9:01 ` David Gould
2000-05-03 18:09 Andreas Dilger
2000-05-03 21:01 ` Eric M. Hopper
2000-05-03 23:50 Andreas Dilger
2000-05-04 2:28 ` dgould
2000-05-04 5:21 ` Michael Loftis
2000-05-04 2:38 ` Eric M. Hopper
2000-05-04 12:18 Shaw, Marco
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=390FFA06.F5EBA4F0@twc.de \
--to=ulf@twc.de \
--cc=linux-lvm@msede.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;
as well as URLs for NNTP newsgroup(s).