Re: [patch-2.3.47] /proc/driver/microcode -> /dev/cpu/microcode

From: Theodore Y. Ts'o (tytso@MIT.EDU)
Date: Tue Feb 29 2000 - 16:07:44 EST


   Date: Mon, 28 Feb 2000 16:09:54 +0000 (GMT)
   From: Riley Williams <rhw@MemAlpha.cx>

> If programs simply access these files as /devfs/foo, then
> someone who doesn't want to use devfs as their /dev
> directory can simply mount devfs in /devfs, and be done
> with it. Folks who believe in the /devfs relgiion can
> mount /devfs over /dev, and then put a symlink in so that
> /devfs points /dev.

   Alternatively, they can mount /devfs as /devfs and put a symlink
   in with /dev -> /devfs unless I'm mistaken?

No, because in this scenario this is someone who wants /dev to be a real
directory with real device inodes, and not use /devfs for their devices.
Hence, /dev has to be a real directory and not a symlink to /devfs.
However, if we start moving synthetic files from /proc to devfs, and
programs are accessing them via /dev/kitchensink, then we will need to
put lots of symlinks from /dev/* to /devfs.

                                                - Ted

-
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/



This archive was generated by hypermail 2b29 : Tue Feb 29 2000 - 21:00:23 EST