public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Andreas Dilger <adilger@turbolinux.com>,
	Linux LVM Development list <lvm-devel@sistina.com>,
	Linux kernel development list <linux-kernel@vger.kernel.org>,
	Heinz Mauelshagen <mauelshagen@sistina.com>
Subject: Re: [lvm-devel] *** ANNOUNCEMENT *** LVM 0.9.1 beta5 available at www.sistina.com
Date: Wed, 21 Feb 2001 18:00:35 +0100	[thread overview]
Message-ID: <20010221180035.N25927@athlon.random> (raw)
In-Reply-To: <20010220234219.B2023@athlon.random> <200102210031.f1L0VQU15564@webber.adilger.net> <20010221021252.A932@athlon.random> <200102210349.f1L3nHE03110@mobilix.atnf.CSIRO.AU>
In-Reply-To: <200102210349.f1L3nHE03110@mobilix.atnf.CSIRO.AU>; from rgooch@ras.ucalgary.ca on Wed, Feb 21, 2001 at 02:49:17PM +1100

On Wed, Feb 21, 2001 at 02:49:17PM +1100, Richard Gooch wrote:
> You definately can mknod(2) on devfs. [..]

So then why don't we simply create the VG ourself with the right minor number
and use it as we do without devfs? We'll still have a global 256 VG limit this
way but that's not a minor issue.

Andrea

  reply	other threads:[~2001-02-21 16:59 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 ` [lvm-devel] *** ANNOUNCEMENT *** LVM 0.9.1 beta5 available at www.sistina.com 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 [this message]
2001-02-21 17:03           ` Richard Gooch
2001-02-21 17:18           ` Christoph Hellwig
2001-02-22  4:12             ` Peter Samuelson
2001-02-22  9:46               ` Christoph Hellwig
2001-02-22 10:52                 ` Peter Samuelson
2001-02-22 11:53                   ` Christoph Hellwig

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=20010221180035.N25927@athlon.random \
    --to=andrea@suse.de \
    --cc=adilger@turbolinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvm-devel@sistina.com \
    --cc=mauelshagen@sistina.com \
    --cc=rgooch@ras.ucalgary.ca \
    /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