From: Heinz Mauelshagen <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM, lilo and MBR?
Date: Tue, 27 Mar 2001 12:28:36 -0600 [thread overview]
Message-ID: <20010327122836.B12883@sistina.com> (raw)
In-Reply-To: <200103271811.f2RIBS005020@webber.adilger.int>; from adilger@turbolinux.com on Tue, Mar 27, 2001 at 11:11:28AM -0700
On Tue, Mar 27, 2001 at 11:11:28AM -0700, Andreas Dilger wrote:
> Urs Thuermann wrote:
> > Patrick Caulfield <caulfield@sistina.com> writes:
> > > 2. IIRC, someone had a patch for lilo to load the kernel and initrd
> > > image from a LV. Where can I get it? And will it go into the
> > > standard lilo package?
> >
> > Andreas will be along in a moment !
>
> Yes, patch for LILO has already been sent to LVM mailing lists a
> couple of times. I found a copy at:
>
> http://marc.theaimsgroup.com/?l=linux-lvm&m=98451699131728&w=4
>
> I have not yet submitted it to the LILO maintainer, because if you try
> to run it on older LVM kernel code (i.e. what's in the official 2.4.2
> kernel), it will immediately crash your system. The Sistina folks have
> told me they will submit an LVM kernel patch with the fix...
>
Which is already history now.
Linus has it since 10 days or something...
Regards,
Heinz -- The LVM guy --
> > > Don't run LILO on /dev/sda if it's a PV because it will destroy
> > > it. You should partition the disk into /dev/sda1 (that way
> > > the PV will start further in and leave space for LILO)
> >
> > Hm, I hoped I could get rid of the broken partitioning scheme of the
> > PC and C/H/S addressing used in the partition table.
>
> But then again, your MBR has the same problems, so why worry? Even so,
> you only need the partition table on the boot disk, so no big deal.
>
> > Are there objections to change LVM so that the VGDA is placed at some
> > fixed offset (say 1 sector or 1 block (1K)) from the beginning of the
> > PV? This is how many file systems also use block devices to avoid
> > conflicts with MBR, boot sectors and so on.
>
> Yes, because it will break every LVM setup around. Too bad it wasn't
> in the original design, but it is too late to change.
>
> Cgeers, Andreas
> --
> Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
> \ would they cancel out, leaving him still hungry?"
> http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Bartningstr. 12
64289 Darmstadt
Germany
Mauelshagen@Sistina.com +49 6151 7103 86
FAX 7103 96
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2001-03-27 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 9:34 [linux-lvm] LVM, lilo and MBR? Urs Thuermann
2001-03-27 10:01 ` Patrick Caulfield
2001-03-27 13:43 ` Urs Thuermann
2001-03-27 14:14 ` Patrick Caulfield
2001-03-27 18:11 ` Andreas Dilger
2001-03-27 18:28 ` Heinz Mauelshagen [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=20010327122836.B12883@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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).