> And now the kernel source maintenance problem: how to impose unique
> numbers to kernel messages with the least labor?
That could be at least partly solved by stating that all such numbers
will use the following rules:
1. The number allocated will fit within an unsigned 16-bit integer.
2. Where the message relates to a device that appears as a node in
/dev that has a STATIC major number, the number will consist of
100 times the major number for that device plus the message number
within the appropriate driver.
3. Where the message relates to part of the /proc filesystem that
is not directly related to a device driver, the number will
consist of 25600 plus the appropriate message number.
That has essentially either allocated or reserved message numbers from
0 to 25699, but leaves 25700 through 65535 available for allocation
elsewhere...
Best wishes from Riley.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu