public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Larger dev_t and major/minor split
Date: Thu, 20 Mar 2003 15:06:31 -0800	[thread overview]
Message-ID: <3E7A4977.5090700@zytor.com> (raw)
In-Reply-To: <20030320220901.GR2835@ca-server1.us.oracle.com>

Joel Becker wrote:
> On Thu, Mar 20, 2003 at 01:42:41PM -0800, H. Peter Anvin wrote:
> 
>>b) In order to support NFSv2 and other filesystems which only support
>>   a 32-bit dev_t, I suggest we stay within a (12,20)-bit range for as
> 
> 
> 	Hmm, I guess that means dropping ext2/3 for / ;-(
> 

Last I checked, all traditional (inode-based) Unix filesystems,
including ext2/3 used block pointers for dev_t.  There are plenty of
block pointers; 60 bytes worth.

	-hpa


  reply	other threads:[~2003-03-20 22:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 21:42 Larger dev_t and major/minor split H. Peter Anvin
2003-03-20 22:09 ` Joel Becker
2003-03-20 23:06   ` H. Peter Anvin [this message]
2003-03-20 23:49     ` Joel Becker
2003-03-21  0:02       ` H. Peter Anvin
2003-03-20 22:47 ` Greg KH

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=3E7A4977.5090700@zytor.com \
    --to=hpa@zytor.com \
    --cc=Joel.Becker@oracle.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox