All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: kaih@khms.westfalen.de, linux-kernel@vger.kernel.org
Subject: Re: On re-working the major/minor system
Date: Sun, 9 Dec 2001 21:37:27 GMT	[thread overview]
Message-ID: <UTC200112092137.VAA252458.aeb@cwi.nl> (raw)

    From: kaih@khms.westfalen.de (Kai Henningsen)

    > The C library, and the POSIX standard, etc, etc.

    I think you'll find that there is *NOTHING* in either the C standard,  
    POSIX, or the Austin future-{POSIX,UNIX} standard that knows about major  
    or minor numbers.

The Austin draft turned into POSIX 1003.1-2001 yesterday or so.

There is not much, but a few traces can be found.
For example, the pax archive format uses 8-byte devmajor and devminor fields.

(But to reassure others: no, this standard does not specify
major and minor in ls output, but just says
"If the file is a character special or block special file, the size of
 the file may be replaced with implementation-defined information
 associated with the device in question.")

Andries



             reply	other threads:[~2001-12-09 21:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-09 21:37 Andries.Brouwer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-08 17:55 On re-working the major/minor system Andries.Brouwer
2001-12-07 10:56 Linux/Pro -- clusters Martin Dalecki
2001-12-07 12:08 ` Alan Cox
2001-12-07 20:51   ` On re-working the major/minor system Erik Andersen
2001-12-07 21:21     ` H. Peter Anvin
2001-12-07 21:55       ` Erik Andersen
2001-12-07 22:04         ` H. Peter Anvin
2001-12-07 23:07           ` Erik Andersen
2001-12-07 23:12             ` H. Peter Anvin
2001-12-08 11:42               ` Alan Cox
2001-12-08 20:37                 ` H. Peter Anvin
2001-12-09 12:06         ` Kai Henningsen
2001-12-09 21:57           ` H. Peter Anvin
2001-12-11 20:45             ` Kai Henningsen

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=UTC200112092137.VAA252458.aeb@cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=kaih@khms.westfalen.de \
    --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.