From: Joel Becker <Joel.Becker@oracle.com>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Andries.Brouwer@cwi.nl, akpm@digeo.com,
andrey@eccentric.mae.cornell.edu, linux-kernel@vger.kernel.org,
torvalds@transmeta.com
Subject: Re: major/minor split
Date: Thu, 20 Mar 2003 14:03:13 -0800 [thread overview]
Message-ID: <20030320220313.GQ2835@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20030320214740.GP2835@ca-server1.us.oracle.com>
On Thu, Mar 20, 2003 at 01:47:41PM -0800, Joel Becker wrote:
> Actually, no. mknod(8), ls(1), and friends still assume struct
> stat with u16.
It's been pointed out to me that this isn't clear. What I mean
is that mknod(8), ls(1), and other programs assume dev_t mappings that
are usually based upon the MAJOR() macro and friends. This means that
any modification of the dev_t arrangement may require source fixes and
may not, depending on how smart MAJOR() is, but will absolutely require
a new compile of the software to pick up the new MAJOR() macro.
Peter is right, we only want to do this once.
Joel
--
"There are some experiences in life which should not be demanded
twice from any man, and one of them is listening to the Brahms Requiem."
- George Bernard Shaw
Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2003-03-20 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 21:40 major/minor split Andries.Brouwer
2003-03-20 21:00 ` Roman Zippel
2003-03-20 21:47 ` Joel Becker
2003-03-20 22:03 ` Joel Becker [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-20 22:24 Andries.Brouwer
2003-03-20 23:23 ` Roman Zippel
2003-03-21 0:04 ` H. Peter Anvin
2003-03-20 23:52 ` H. Peter Anvin
2003-03-21 7:35 Andries.Brouwer
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=20030320220313.GQ2835@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@digeo.com \
--cc=andrey@eccentric.mae.cornell.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zippel@linux-m68k.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.