From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Newbie question
Date: Mon, 16 Jul 2001 13:34:17 +0200 [thread overview]
Message-ID: <20010716133417.F11625@sistina.com> (raw)
In-Reply-To: <20010713200112.A11175@colombina.comedia.it>; from bluca@comedia.it on Fri, Jul 13, 2001 at 08:01:13PM +0200
On Fri, Jul 13, 2001 at 08:01:13PM +0200, Luca Berra wrote:
> On Fri, Jul 13, 2001 at 01:12:00PM +0200, Heinz J. Mauelshagen wrote:
> > > Another question is the boot stuff, what is better? compile LVM as a module
> > > and use inird or compile the kernel with built-in LVM support?
> >
> > It doesn't make a difference if you go for the module or the build in driver,
> > you need to have an initrd today anyway to activate your VGs at boot time.
> >
> > We are working on boot time recognition of VGs in the driver which will vanish
> > the initrd. That will be in a post 1.0 version of the Linux LVM.
>
> is this still worthwile since i read Linus in thinking of a new way
> to handle initrd (appending a tar file to a kernel image and populating
> a ramfs with it) and moving many _init code that now bloats kernel
> to userspace.
Yes, we do move the functions to read metadata into the LVM kernel code
because we need them in the cluster case anyway.
>
> Regards,
> L.
>
> --
> Luca Berra -- bluca@comedia.it
> Communication Media & Services S.r.l.
> /"\
> \ / ASCII RIBBON CAMPAIGN
> X AGAINST HTML MAIL
> / \
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
--
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2001-07-16 11:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-11 18:33 [linux-lvm] syslogd reports: kernel: lvm -- lvm_chr_ioctl: unknown command 4004fe0a Theo
2001-07-12 8:46 ` Joe Thornber
2001-07-12 14:53 ` [linux-lvm] Newbie question Leandro Lucarella
2001-07-13 11:12 ` Heinz J. Mauelshagen
2001-07-13 15:33 ` Re[2]: " Leandro Lucarella
2001-07-13 16:41 ` Vincent Bernat
2001-07-16 11:31 ` Heinz J. Mauelshagen
2001-07-16 11:33 ` Heinz J. Mauelshagen
2001-07-16 15:08 ` Steven Lembark
2001-07-16 23:36 ` Luca Berra
2001-07-17 8:31 ` josv
2001-07-17 11:39 ` Heinz J. Mauelshagen
2001-07-17 19:58 ` Luca Berra
2001-07-18 15:25 ` Heinz J. Mauelshagen
2001-07-13 18:01 ` Luca Berra
2001-07-16 11:34 ` Heinz J. Mauelshagen [this message]
2001-07-12 19:07 ` [linux-lvm] syslogd reports: kernel: lvm -- lvm_chr_ioctl: unknown command 4004fe0a Johann
-- strict thread matches above, loose matches on Subject: below --
2002-06-25 14:53 [linux-lvm] newbie question shri krishnan
2002-06-26 5:41 ` Heinz J . Mauelshagen
2001-02-02 15:08 JAmes
2001-02-02 15:49 ` Eric M. Hopper
2001-02-02 16:09 ` James
2001-02-04 4:29 ` David Gould
2001-02-02 20:56 ` Andreas Dilger
2001-02-03 8:22 ` James
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=20010716133417.F11625@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