From: Andreas Dilger <adilger@turbolinux.com>
To: Andi Kleen <ak@suse.de>
Cc: Linux LVM mailing list <linux-lvm@msede.com>, isdfa@visi.com
Subject: Re: [linux-lvm] LVM support for LILO
Date: Thu, 7 Sep 2000 17:44:03 -0600 (MDT) [thread overview]
Message-ID: <200009072344.RAA21636@lynx.turbolabs.com> (raw)
In-Reply-To: <20000908004640.A24191@gruyere.muc.suse.de> from "Andi Kleen" at Sep 08, 2000 12:46:40 AM
Andi Kleen, you write:
> I hacked lilo, but I never tested them really because I didn't have a spare
> HD to experiment with the changed PV format at that time (I noticed the
> problem with the PV format only after I did that work :-() You can have
> the untested patches if you want. From visual inspection the translated
> blocks looked ok.
Yes, please send me a copy...
> A full solution requires more work, e.g. at least a LV flag so that
> LVM can urge the user to rerun lilo after a *move. Support in lilo for LVs
> spread over multiple devices would also be nice (I just cheated by requiring
> it all on a single device)
Yes, this was discussed a bit in the past, but like all things Linux, it
is better to have something now instead of later. However, I don't even
know if it would be possible to boot from multiple devices, since I think
this may even be a BIOS thing to load the blocks, otherwise we would never
be restricted to BIOS devices for boot...
> It just does not make much sense then, because with a DOS partition table
> you can as well have a partition based /boot
It's still not good to have a partition-based /boot, because you can't
migrate it, enlarge it, etc (carefully, mind you). There are still some
limitations for LVM based /boot, but if you have /dev/hda1 that is all
in LVM, you are free to manage it any way you want. The partition table
is only a few kB... You can make all your other disks full LVM disks
and save a few more kB, if you are TOTALLY SURE you will never want to
boot from any of them...
Cheers, Andreas
next prev parent reply other threads:[~2000-09-07 23:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-07 18:25 [linux-lvm] LVM support for LILO Andreas Dilger
2000-09-07 21:43 ` Andi Kleen
2000-09-07 22:39 ` Andreas Dilger
2000-09-07 22:46 ` Andi Kleen
2000-09-07 23:44 ` Andreas Dilger [this message]
2000-09-08 14:25 ` Andi Kleen
2000-09-08 0:11 ` Heinz J. Mauelshagen
2000-09-07 22:14 ` Andi Kleen
2000-09-07 23:00 ` Andi Kleen
2000-09-08 0:02 ` Heinz J. Mauelshagen
2000-09-07 23:29 ` Andreas Dilger
2000-09-08 13:02 ` Heinz J. Mauelshagen
2000-09-08 13:47 ` Luca Berra
2000-09-08 19:09 ` Heinz J. Mauelshagen
2000-09-08 14:03 ` Michael J Kellen
2001-02-27 0:30 ` Ralph Jennings
-- strict thread matches above, loose matches on Subject: below --
2000-09-08 19:39 Andreas Dilger
2000-09-08 19:50 Andreas Dilger
2000-09-09 7:44 ` Luca Berra
2000-09-09 10:07 ` Christoph Hellwig
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=200009072344.RAA21636@lynx.turbolabs.com \
--to=adilger@turbolinux.com \
--cc=ak@suse.de \
--cc=isdfa@visi.com \
--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).