Linux LVM users
 help / color / mirror / Atom feed
From: Luca Berra <bluca@comedia.it>
To: Christophe Saout <christophe@saout.de>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] booting a dm+lvm2 kernel
Date: Thu Jan  1 17:40:01 2004	[thread overview]
Message-ID: <20040101233902.GG21031@percy.comedia.it> (raw)
In-Reply-To: <1072998611.5199.21.camel@leto.cs.pocnet.net>

On Fri, Jan 02, 2004 at 12:10:11AM +0100, Christophe Saout wrote:
>I thought you were talking about the lvmcreate_initrd script that came
i actually never used lvmcreate_initrd that came with LVM1,

>Yes, I've seen redhat doing this. I personally prefer being able to
>override it at the command line though. Having something hardcoded in
>the initrd sounds strange to me.
i agree with your concern, i'll try to get it from the command line

>I have attached the script. I parse /proc/cmdline, try to remove root=
>using a shell function and if it actually removed something I know that
>the rest has to be a device name. :)
uhm, you should be wary of the case when a root= is in lilo.conf and
luser wants to override it from cmdline. you stop a t the first
occurrence.

>Wasn't ash the one from busybox?
no busybox is a dietlibc compiled shell that already has most command
compiled in, so a single executable, and smaller than glibc.

>With udev I just created /dev/console and some others. Doing everything
>from the script seems unnecessary.
i have to, because of tmpfs dev

>> My initrd detects if the root VG is on a md (softraid) device and
>> starts it before trying to activate the VG.
>Doesn't the kernel start them automatically? You mean, if it isn't
>activated in the kernel? Probably a good idea.
I strongly believe that raid autodetection should be done in user space,
possibly with mdadm. There is a big advantage in being able to control
what gets activated and when, besides distribution kernels use modular
scsi drive modules, so probably autodetection won't work anyway.
I also don't have the faintest idea if the kernel deals with stacked
raid devices

>Yes, that's also possible. But I don't really like it being readonly
>because, as you say, mounting something on /etc or /dev is unnecessary.
>What's the problem with ext2? The wasted memory?
wasted memory and disk space, being able to fit kernel+initrd on a
single floppy is a good reason

>I would love making the initrd an initramfs. But that doesn't currently
i think initramfs is not mature yet.
L.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

  reply	other threads:[~2004-01-01 17:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-01 10:58 [linux-lvm] booting a dm+lvm2 kernel Kjartan Reynir Hauksson
2004-01-01 12:49 ` Luca Berra
2004-01-01 15:42   ` Christophe Saout
2004-01-01 16:47     ` Luca Berra
2004-01-02  8:30       ` Christophe Saout
2004-01-01 17:40         ` Luca Berra [this message]
2004-01-01 17:50           ` Christophe Saout
2004-01-01 17:05   ` [linux-lvm] LVM2 on boot partition Branko
  -- strict thread matches above, loose matches on Subject: below --
2004-01-03 11:34 [linux-lvm] booting a dm+lvm2 kernel Kjartan Reynir Hauksson
2004-01-05  7:32 ` Luca Berra
2004-01-02 18:02 Kjartan Reynir Hauksson
2004-01-03  4:30 ` Luca Berra
2004-01-02 16:54 Kjartan Reynir Hauksson
2004-01-02 17:34 ` Luca Berra
2004-01-02 13:40 Kjartan Reynir Hauksson
2004-01-02 14:12 ` Luca Berra
2004-01-02 14:24   ` Bill Rugolsky Jr.
2004-01-02 16:11     ` Luca Berra
2004-01-02 13:03 Kjartan Reynir Hauksson
2004-01-02 13:15 ` Luca Berra
2004-01-02 11:37 Kjartan Reynir Hauksson
2004-01-02 12:07 ` Luca Berra
2004-01-02  9:12 Kjartan Reynir Hauksson
2004-01-02 10:58 ` Luca Berra
2003-12-31 18:46 Kjartan Reynir Hauksson
2004-01-01  5:11 ` Luca Berra
2003-12-30 21:21 Kjartan Reynir Hauksson
2003-12-31  3:35 ` Luca Berra

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=20040101233902.GG21031@percy.comedia.it \
    --to=bluca@comedia.it \
    --cc=christophe@saout.de \
    --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