> I may regret getting into this, but here goes.
You and me both. :)
> -- Do dynamic major allocation in the usual way.
> -- Report the allocation (and other stuff) via /proc.
> -- The startup script run by init uses the information in /proc
> to create the appropriate inodes.
>
> Now this may seem, er... hacky, but I actually think it achieves the
> rather sensible aims of devfs without the pain. The string lookup
> mechanisms are now just part of normal filesystem operation, and it's
> completely dynamic so pretty well future proofed.
>
> It's not the right choice for the more important drivers in the
> kernel, but for purely modular drivers (those which really do need to
> be in kernel space), I think it makes a wad of sense. What do the
> other protagonists feel?
Well, couple things, for one, what about those 'more important
drivers'? My biggest problem w/ linux these days is the scsi device
stuff. If this could be fixed w/ shell scripts and reading info out
of /proc, then that may work. But then, what about USB, PCMCIA, and
other dynamic pieces? Do you have modprobe or whatnot create and
delete the nodes? Do you just create the nodes w/ the assumption that
they'll be used?
Just some thoughts.
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/