Here's my suggestion for a solution.
Once I work through a bunch of net driver problems, I want to release a
snapshot block device driver (freezes a blkdev in time). For this, I
needed a block major. After hearing about the device number freeze, I
was wondering if this solution works:
Register block device using existing API, and obtain a dynamically
assigned major number. Export a tiny ramfs which lists all device
nodes. Mounted on /dev/snap, /dev/snap/0 would be the first blkdev for
snap's dynamically assigned major. (Al Viro said he has skeleton code
to create such an fs, IIRC)
This solution
(a) keeps from grot-ing up /proc even more [I had considered
proc_mknod() until viro talked me out of it]
(b) does not require centrally assigned majors and minors.
(c) does not require devfs. most distros ship without it afaik, and
switching to it is not an overnight process, and requires devfsd to be
useful in the real world.
-- Jeff Garzik | Game called on account of naked chick Building 1024 | MandrakeSoft | - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/