From: Peter Samuelson <peter@cadcamlab.org>
To: Christoph Hellwig <hch@caldera.de>
Cc: lvm-devel@sistina.com, linux-kernel@vger.kernel.org
Subject: Re: [lvm-devel] *** ANNOUNCEMENT *** LVM 0.9.1 beta5 available at www.sistina.com
Date: Wed, 21 Feb 2001 22:12:25 -0600 [thread overview]
Message-ID: <20010221221225.B21010@cadcamlab.org> (raw)
In-Reply-To: <20010221180035.N25927@athlon.random> <200102211718.SAA25997@ns.caldera.de>
In-Reply-To: <200102211718.SAA25997@ns.caldera.de>; from hch@caldera.de on Wed, Feb 21, 2001 at 06:18:24PM +0100
[Christoph Hellwig]
> It would be really good to have something devfs-like just for LVM in
> setups that don't use LVM, so we could avoid mounting root read/write
^^^devfs?
> for device-creation.
For most people, read/write access to /dev is rarely needed -- how
often do you create new VGs or LVs? How often do you run MAKEDEV or
vgscan? Sometimes you need to change tty inodes but that's what
/dev/pts is for.
If you do need read-write access to /dev but not /, put it on a
separate filesystem. Leave just a skeletal /dev in your root
filesystem, enough to bootstrap.
Peter
next prev parent reply other threads:[~2001-02-22 4:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010220224907.D21281@srv.sistina.com>
2001-02-20 22:42 ` Andrea Arcangeli
2001-02-21 0:31 ` Andreas Dilger
2001-02-21 1:12 ` Andrea Arcangeli
2001-02-21 3:49 ` Richard Gooch
2001-02-21 17:00 ` Andrea Arcangeli
2001-02-21 17:18 ` Christoph Hellwig
2001-02-22 4:12 ` Peter Samuelson [this message]
2001-02-22 9:46 ` Christoph Hellwig
2001-02-22 10:52 ` Peter Samuelson
2001-02-22 11:53 ` Christoph Hellwig
2001-02-21 17:03 ` Richard Gooch
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=20010221221225.B21010@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=hch@caldera.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lvm-devel@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
all inboxes | Powered by JetHome®