On Mon, Feb 24, 2014 at 9:12 AM, Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
>
> This patch uses the 0/0 device number, but the actual number doesn't matter
> as long as it doesn't conflict with a real device.
Side note: I think 0/0 is the right choice, for a very specific
reason: it is already documented as being special. No other
combination has that.
We've had "major number 0" documented as being for unnamed devices,
and minor 0 is "reserved as null device number", which is just bad
documentation (it's *not* /dev/null, it doesn't exist). You cannot
register a character device with mijor/minor 0 in Linux, for example.
(The block layer similarly considers MKDEV(0,0) to be an unallocated device)
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
