This file lies by saying 200-255 are reserved for local use, thus
implying that they aren't used for the rest of the system. Fix the lies: 253 is used by mfs (bad MFS for not registering it). 254 is a magic cookie inside of the dev code in at least one place. 255 is -1 which is magic in a different way in the dev code. So, that means that 200-252 are reserved for local users. A grep for 252 didn't turn anything up, so I'm assuming it and lower are safe. And I thought I was being smart by allocating our local major numbers from 254 on down. This caused very very odd problems that were hard to track down: close not being called, sync failing at reboot, etc.
This commit is contained in:
parent
6ea6805f8c
commit
03c16f958a
|
@ -165,5 +165,8 @@ chrdev name comments
|
|||
146 twe 3ware Escalade ATA RAID (controller)
|
||||
147 twed 3ware Escalade ATA RAID (drives)
|
||||
148 agp AGP <dfr>
|
||||
200 ?? entries from 200-255 are reserved for local use
|
||||
255 ?? entries from 200-255 are reserved for local use
|
||||
200 ?? entries from 200-252 are reserved for local use
|
||||
252 ?? entries from 200-252 are reserved for local use
|
||||
253 mfs Used by MFS
|
||||
254 internal Used internally by the kernel
|
||||
255 bad choice -1 is 255 which has magic meanings internally
|
||||
|
|
Loading…
Reference in New Issue