Known devreg problems (and possible solutions)
---------------------

Possible race problems in user space:
	Reading /proc/devreg and opening the chosen device is not an
	atomic	action. There is no way to ensure that the chosen device still 
	exists.

	Possible solutions:
	- add a ioctl that returns the DeviceID to all registered devices
	so the user-app can know whether it got the right device. I hate
	it.

	- add a system call open-by-deviceid. I dont know what to think
	about it, this could replace the way dynamic devices are accessed
	and maybe even replace devfs, but it would also give up the Unix
	everything-is-a-file notion. Unrealistic.

	- when Linux gets support for file meta-information / multiple
	streams for files the list entry could be added to a devfs
	file as a second stream. Clean solution, would also remove
	the need for /proc/devreg. (Doing this as a ioctl is not a good 
	idea because then you cannot browse devices that are already open)

	- keeping it as it is, because it is highly unlikely that a user
	manages it to remove or even replace a device between the access
	to /prov/devreg and the device file. Currently implemented.