From: Christoph Hellwig <hch@ns.caldera.de>
To: Luca Berra <bluca@comedia.it>, Linux-LVM@sistina.com
Subject: Re: [linux-lvm] devfs
Date: Thu, 14 Dec 2000 16:53:22 +0100 [thread overview]
Message-ID: <20001214165322.A22656@caldera.de> (raw)
In-Reply-To: <20001214164152.A1886@colombina.comedia.it>; from bluca@comedia.it on Thu, Dec 14, 2000 at 04:41:53PM +0100
On Thu, Dec 14, 2000 at 04:41:53PM +0100, Luca Berra wrote:
> On Wed, Dec 13, 2000 at 09:17:41PM +0100, Russell Coker wrote:
> > It appears that devfs is not supported in LVM at this time (but I can't be
> > certain because I haven't got it going properly yet). What are the plans for
> > devfs support?
>
> this is not exact, there is some devfs support in lvm 0.9, or
> 0.8 in kernels >= 2.4.0-test8, but it does not work!!!
>
> i had to patch the lvm tools so they don't remove the /dev/<vgname> directory
>
> also from my brief testing it seems that devfs tries to create the
> /dev/vg/group node when activating the vg (while this should be done
> during vgscan), but does not create the lv defice files.
Right - you have to apply _two_ patches for the userlevel.
I had a system running devfs and LVM for a while but than switched back
to traditional /dev for other reasons.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
next prev parent reply other threads:[~2000-12-14 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 20:17 [linux-lvm] devfs Russell Coker
2000-12-14 15:41 ` Luca Berra
2000-12-14 15:53 ` Christoph Hellwig [this message]
2000-12-18 3:36 ` Matthew O'Keefe
-- strict thread matches above, loose matches on Subject: below --
2000-01-05 17:33 James Pattinson
2000-01-05 22:34 ` Heinz Mauelshagen
2000-01-05 23:03 ` James Pattinson
2000-01-05 23:30 ` James Pattinson
2000-01-06 23:24 ` Jos Visser
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=20001214165322.A22656@caldera.de \
--to=hch@ns.caldera.de \
--cc=Linux-LVM@sistina.com \
--cc=bluca@comedia.it \
/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