In message <[EMAIL PROTECTED]>, Takanori Watanabe writes: >In message <[EMAIL PROTECTED]>, Poul-Henning Kamp wrote: > >>DEVFS: > >> 3. major/minors will be dynamically assigned. > >So we will need file to list node id list in printf(9) format, >instead of /sys/conf/majors.
I am not sure about this... [1] >And more better if we generate device name #define or array of >string from the file. This will help us implementing loading >module when an user process attempt to open some nodes that >owned by unloaded modules. and even less about this... [2] That said, just because I don't like it doesn't mean that people should try to prototype it and see if I'm wrong... Poul-Henning [1] A major part of the drive behind DEVFS is to avoiding the need to register device drivers in a magic, global file. I will agree that it is an predictable outcome that one day two drivers will both try to be /dev/foo but he, they get to haggle that one out for themselves. [2] I simply cannot see us kldload'ing stuff in response to ls -l /dev/watchthis (This is a trick answer: The point is that at VOP_LOOKUP time where the device cloning runs, you don't know for what operation the VOP_LOOKUP is called: stat, open, remove, rename... (Well, some of them you do, but not the interesting ones). -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message