All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Larger dev_t and major/minor split
Date: Thu, 20 Mar 2003 14:09:02 -0800	[thread overview]
Message-ID: <20030320220901.GR2835@ca-server1.us.oracle.com> (raw)
In-Reply-To: <b5dckh$lv1$1@cesium.transmeta.com>

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 / ;-(

Joel

-- 

"Nothing is wrong with California that a rise in the ocean level
 wouldn't cure."
        - Ross MacDonald

Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127

  reply	other threads:[~2003-03-20 21:58 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 [this message]
2003-03-20 23:06   ` H. Peter Anvin
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=20030320220901.GR2835@ca-server1.us.oracle.com \
    --to=joel.becker@oracle.com \
    --cc=hpa@zytor.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 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.