All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: linux-kernel@vger.kernel.org
Cc: Andries.Brouwer@cwi.nl, akpm@digeo.com
Subject: mknod64(1)
Date: 18 Apr 2003 17:13:03 -0400	[thread overview]
Message-ID: <1050700383.745.48.camel@localhost> (raw)

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).

But for now this version works and supports the 64-bit dev_t with a
32:32 split.  It is also identical in functionality to mknod(1), except
it does not support an initial mode other than the default (i.e., no
--mode option).

Installation is simple but RPM packages are also available.

Usage is the same as mknod, except you may specify a 32-bit value for
the major and the minor device number.

This currently requires 2.5.67-mm4, but I suspect the 64-bit dev_t work
will eventually make its way into Linus's tree.

Note that most utilities cannot see the 64-bit device numbers, i.e.
ls(1) only displays 8-bits of each.  You can do a homemade stat64() or
just trust the code.

With the above kernel and this utility, you can play with 64-bit device
numbers.  Enjoy.

	Robert Love



             reply	other threads:[~2003-04-18 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18 21:13 Robert Love [this message]
2003-04-18 21:24 ` mknod64(1) H. Peter Anvin
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=1050700383.745.48.camel@localhost \
    --to=rml@tech9.net \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=akpm@digeo.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.