All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <lvm@interlinx.bc.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Migrating to an LVM system (boot/root) disk
Date: Sun, 3 Jun 2001 03:22:25 -0700	[thread overview]
Message-ID: <20010603032225.K21442@linux.interlinx.bc.ca> (raw)
In-Reply-To: <NBBBKLKHMJHIJLHOGAOJCEALIPAA.steve.wray@the.net.nz>; from steve.wray@the.net.nz on Sun, Jun 03, 2001 at 05:02:41PM +1200

On Sun, Jun 03, 2001 at 05:02:41PM +1200, Steve Wray wrote:
> 1. In the LFS howto, I saw a warning to the effect of: NEVER run lilo
> from a chrooted environment. You can destroy your MBR making
> your system bootable only from floppy... Dunno if it applied here.

If you do not tell it which disk to write the MBR to, yes, that would
be true.

> 2. Having a /boot on LVM *is* possible, BUT you will need to boot
> from floppy.

No you don't.  There are several in depth discussions in the archive
about doing this including a posting (several times in fact) of a
patch to Lilo to help it locate the kernel and initrd on an LVM /boot.
Please see the archives for details.

> 3. to get over your night horrors, make a boot disk

disks!  My initrd is 1.3MB alone!

> that includes the LVM
> tools. A good starting point is miniroot. I posted a URL to it on this
> list a little while ago. I don't have it to hand but it'll be in the
> archive!

Yeah, I realize that making boot diskettes is what I have to do, but
the "automated" mkbootdisk that some distros ship as well as the
various root/boot kits out there sure are not going to inclue the LMV
tools.  Having to manually craft the pair is a pain.  :-)

Perhaps just like LVM has a nice little script for creating the
initrd, they can ship with a nice little script for creating root/boot
diskettes.

Of course a lot of this headache goes away if the kernel had the
"auto-detection" code like it does for MDs.

b.

-- 
Brian J. Murrell

  reply	other threads:[~2001-06-03 10:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-03  2:16 [linux-lvm] Migrating to an LVM system (boot/root) disk Brian J. Murrell
2001-06-03  5:02 ` Steve Wray
2001-06-03 10:22   ` Brian J. Murrell [this message]
2001-06-03 10:59     ` Steve Wray
2001-06-03 18:27       ` Michael Tokarev
2001-06-03 21:12         ` Steve Wray
2001-06-03 23:11           ` Michael Tokarev
2001-06-04 17:34             ` Andreas Dilger
2001-06-04 18:59               ` Michael Tokarev
2001-06-04 21:03                 ` Steve Wray
2001-06-04 22:15               ` AJ Lewis
2001-06-04 23:15                 ` Michael Tokarev
2001-06-04 23:28                   ` Luca Berra
2001-06-05 16:57                     ` AJ Lewis
2001-06-05 17:55                   ` Andreas Dilger
2001-06-05 18:08                     ` Luca Berra
2001-06-04  3:40 ` Andreas Dilger
2001-06-04  6:04   ` Brian J. Murrell
2001-06-04 17:37     ` Andreas Dilger

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=20010603032225.K21442@linux.interlinx.bc.ca \
    --to=lvm@interlinx.bc.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.