From: Robert Love <rml@tech9.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mknod64(1)
Date: 18 Apr 2003 17:31:04 -0400 [thread overview]
Message-ID: <1050701464.745.52.camel@localhost> (raw)
In-Reply-To: <b7pqf5$kqv$1@cesium.transmeta.com>
On Fri, 2003-04-18 at 17:24, H. Peter Anvin wrote:
> Well, actually, once glibc is updated to call SYS_mknod64 and have the
> right MAJOR() and MINOR() macros, it shouldn't require any changes to
> mknod(1).
Agreed. Assuming mknod(1) is dev_t-clean, this is obsolete as soon as
glibc is updated for 64-bit dev_t. Until then, this is available and
easy and works.
> What would probably be useful for mknod(1), if it doesn't already, is
> to allow the major/minor to be specified in any of the standard bases,
> i.e. using strtoul(...,...,0).
mknod(1) does not, I think. Actually, maybe it does... it uses some
coreutils wrapper.
But my mknod64(1) certainly does :)
Hex, decimal, and binary should all work.
Robert Love
next prev parent reply other threads:[~2003-04-18 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 21:13 mknod64(1) Robert Love
2003-04-18 21:24 ` mknod64(1) H. Peter Anvin
2003-04-18 21:31 ` Robert Love [this message]
2003-04-19 15:45 ` mknod64(1) Andreas Schwab
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=1050701464.745.52.camel@localhost \
--to=rml@tech9.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox