All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Monnier" <monnier+lists/linux/lvm/news/@tequila.cs.yale.edu>
To: lists-linux-lvm@moderators.isc.org
Subject: [linux-lvm] Re: root filesystem in lvm
Date: 02 Jun 1999 06:43:23 -0400	[thread overview]
Message-ID: <5l3e0adgs4.fsf@tequila.cs.yale.edu> (raw)


A while ago, Michael Marxmeier (mike@msede.com) mentioned:
> However it should be possible to use LILO. As far as i understand 
> LILO uses partition relative block numbers to load the kernel image. 
> We just need to make sure that they are relative to the dos style 
> partition.

How would LILO deal with a kernel image spread over several physical
partitions (or even disks) (in case you not only want a root fs on LVM but
a striped/mirrored/trucmuched one) ?

> If included statically in the kernel the lvm driver could
> execute the equivalent of a vgchange -ay and we should be able to
> mount the root file system.

That would be really neat.  The initrd workaround is just that: a workaround.

> However this will lead to some kernel bloat as some of the code which
> currently resides un user space in lvmlib and vgchange must also be 
> present in the kernel.

- how hard would it be ?
- source code bloat:  hopefully, the exact same source code can be shared
  between the kernel and the liblvm/vgchange (I deeply hate code duplication)
- kernel bloat:  how bad would it be ?
  how much of that extra code could be put in __INITFUNC (so that the bloat
  only impacts the on-disk kernel image, but not the in-memory one) ?
  Let's also not forget that the kernel bloat should be measured between
  'linux+lvm+initrd' and 'linux+lvm+lvmroot'.


	Stefan

             reply	other threads:[~1999-06-02 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-02 10:43 Stefan Monnier [this message]
1999-06-02 12:22 ` [linux-lvm] Re: root filesystem in lvm Luca Berra
  -- strict thread matches above, loose matches on Subject: below --
1999-06-02 10:43 Stefan Monnier
1999-06-08 13:52 ` Ulrik De Bie

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=5l3e0adgs4.fsf@tequila.cs.yale.edu \
    --to=monnier+lists/linux/lvm/news/@tequila.cs.yale.edu \
    --cc=lists-linux-lvm@moderators.isc.org \
    /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.