All of lore.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Emmanuel Colbus <ecolbus@manux.info>, linux-kernel@vger.kernel.org
Subject: Re: [RFC][5/11][MANUX] Kernel compatibility : major/minor numbers
Date: Tue, 15 Apr 2014 11:02:51 -0400	[thread overview]
Message-ID: <534D4A1B.30002@gmail.com> (raw)
In-Reply-To: <534D3762.4010905@manux.info>

On 2014-04-15 09:42, Emmanuel Colbus wrote:
> Now, back to the filesystem...
> 
> In order to associate devices to their files, the Linux kernel uses
> their major and minor numbers. However, mine doesn't; instead, I've
> attributed myself a single group of values (major=0, minor=0, for both
> character-mode and block-mode special files), with the meaning (for the
> userspace) "you cannot identify the content of this file based on its
> major and minor numbers".
> 
> As for my kernel, there is a syscall to associate such files with their
> proper peripherals (asper(2)), after which it internally identifies them
> using their inode and partition numbers; as for userspace, it has no
> choice but to use their names, as usual.
> 
> Do you have any objection to my taking of these values?
> 

According to Documentation/devices.txt:
	0		Unnamed devices (e.g. non-device mounts)
			0 = reserved as null device number

Based on this, I would say that you are probably better off using one of
the local use numbers (60-63 and 250-254 are reserved for local and
experimental use)


  reply	other threads:[~2014-04-15 15:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 13:42 [RFC][5/11][MANUX] Kernel compatibility : major/minor numbers Emmanuel Colbus
2014-04-15 15:02 ` Austin S Hemmelgarn [this message]
2014-04-15 17:39   ` Emmanuel Colbus
2014-04-15 15:06 ` One Thousand Gnomes
2014-04-15 15:32   ` Emmanuel Colbus
2014-04-15 15:40     ` One Thousand Gnomes
2014-04-15 20:19     ` Theodore Ts'o
2014-04-15 20:58       ` Emmanuel Colbus

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=534D4A1B.30002@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=ecolbus@manux.info \
    --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.