How about having it store the inodes in /dev on the underlying filesystem?
(Or is it too hard to make the system permit mounts over non-empty
directories...) Also, does devfs actually create all those inodes when it
initializes? Why not just generate listings, etc. on the fly? The tables are
always there in memory. No need to create an effective duplicate.
Taral
-
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.altern.org/andrebalsa/doc/lkml-faq.html