From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: mknod64(1)
Date: 18 Apr 2003 14:24:53 -0700 [thread overview]
Message-ID: <b7pqf5$kqv$1@cesium.transmeta.com> (raw)
In-Reply-To: 1050700383.745.48.camel@localhost
Followup to: <1050700383.745.48.camel@localhost>
By author: Robert Love <rml@tech9.net>
In newsgroup: linux.dev.kernel
>
> So I wrote a mknod64(1) tool, so we can play with 64-bit device
> numbers. It is available at:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/rml/mknod64
>
> for testing. And that is really its whole purpose because I see no
> reason why the mknod in coreutils will not eventually support
> mknod64(2).
>
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).
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).
I belive HP/UX (which have had 32-bit minors for a long time) actually
had ls -l display hexadecimal minors. I am not advocating that,
however, it probably would break too many scripts.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-04-18 21:13 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 ` H. Peter Anvin [this message]
2003-04-18 21:31 ` mknod64(1) Robert Love
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='b7pqf5$kqv$1@cesium.transmeta.com' \
--to=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