Messages in this thread |  | | | Date | Thu, 17 May 2001 11:33:30 +0200 | | From | Guest section DW <> | | Subject | Re: LANANA: To Pending Device Number Registrants |
| |
On Wed, May 16, 2001 at 09:35:09PM -0400, Jeff Garzik wrote:
> To inject a bit of concrete into this discussion, I note that block > devices with dynamically assigned don't work with CONFIG_DEVFS and > devfs=only. Block devices -require- majors currently, due to those > !@#!@# arrays. However, devfs_register_blkdev always returns zero when > devfs=only, even if its a block device and a dynamic major is requested.
Jeff, this is a non-issue. These arrays you talk about are removed in a simple edit session - I did it a handful of times - there is no problem there whatsoever.
What you are talking about is kernel-internal. We are free to do whatever we like inside the kernel, and we have full information. The only question is how to transmit device identity across the kernel space/user space boundary.
Andries
[And my solution is to use cookies - 64-bit opaque numbers that carry no information, and are generated at random by the kernel, but with the properties: (i) things that have a device number today keep this number, (ii) the random generation is such that whenever possible chances are good that after a reboot the same device will have the same number.] - 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/
|  |