All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Root on LV
Date: Mon, 10 Sep 2001 13:31:17 +0200	[thread overview]
Message-ID: <20010910133117.I31313@sistina.com> (raw)
In-Reply-To: <20010906161011.B10735@gatekeeper.osp.nl>; from josv@osp.nl on Thu, Sep 06, 2001 at 04:10:11PM +0200

On Thu, Sep 06, 2001 at 04:10:11PM +0200, josv@osp.nl wrote:
> vgscan and vgchange -a y *ARE* quite essential.
> It is currently *not* possible to perform these two essential
> commands in the kernel.
> 
> AFAIK that is...

That's true. We will have in kernel LVM metadata read support in a
post 1.0 version of LVM which will avoid to run userspace tools to activate
choosen VGs at all.

Regards,
Heinz    -- The LVM Guy --

> 
> ++Jos
> 
> And thus it came to pass that dobos_s@IBCnet.hu wrote:
> (on Thu, Sep 06, 2001 at 04:03:49PM +0200 to be exact)
> 
> > Hi!
> > 
> > I cannot understand something.
> > My kernel has no modules.
> > Why should I create an ext2 partition for holding an initrd which is not
> > doing any essential things except vgscan and vgchange -ay ?
> > Why cant these things built into the kernel?
> > 
> > Maybe I didnt understand something...
> > 
> > 
> > Please CC to me, because I am not member on list...
> > 
> > Thanks
> > 
> > 
> > Dobos Sandor
> > IBCnet Hungary Ltd.
> > 
> > 
> > 
> > 
> > 
> > _______________________________________________
> > 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
> 
> -- 
> Klingon coding rule #12: "Specifications are for the weak and timid!"
> 
> _______________________________________________
> 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

*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-09-10 11:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06 14:03 [linux-lvm] Root on LV dobos_s
2001-09-06 14:10 ` josv
2001-09-10 11:31   ` Heinz J . Mauelshagen [this message]
2001-09-06 14:42 ` svetljo
2001-09-06 15:37   ` Andreas Dilger
2001-09-06 16:35     ` svetljo
2001-09-06 17:52       ` Luca Berra
2001-09-10 11:29     ` Heinz J . Mauelshagen
2001-09-06 16:53 ` lembark
  -- strict thread matches above, loose matches on Subject: below --
2001-09-17 14:26 Steve Pratt
2001-09-18 17:23 ` lembark
2001-09-19 18:54 Steve Pratt
2001-09-19 19:43 ` lembark
2001-09-20  5:15 ` Adrian Phillips

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=20010910133117.I31313@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 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.