Talking from the SysAdmin point of view, procfs is one of the truly
cool things which separates Linux from the others. I'd rather tune
/proc/sys stuff than use sysctl or Solaris' funky /etc/system and
ndd crap. It's the next best thing to "point and click" without going
over to the dark side.
Sure /system is a better name (extra typing becaue we can't have
/sys/sys can we??).
And while you all are at it, why not take a look at some of the naming
conventions that BeOS makes too. I'm _not_ being sarcastic.
Example1: Excellent devfs layout.
Example 2: BeOS root directory is a ramfs off of which the
other drives/filesystems are mounted. (I haven't thought
this one out too much but I could image that it would make
some things easier.)
Example 3: Kernel Modules are in the directory:
/boot/beos/system/add-ons/kernel
Perhaps we could have directories something like:
/boot/kernel
/boot/grub
/boot/lilo
/dev using devfs !
/etc
/home
/system/config/sys
/net
/system/modules/kernelversion/ (modules in devfs similar tree)
/system/info (for cpuinfo, ioports, meminfo, filesystems, etc.)
/sbin (or even in /system/bin ???)
/tmp
/usr
/var
Example 3: BeOS moves /usr/local stuff to more of a per user
configuration where each user has a $HOME/config directory.
Of course, we would put things like .Xdefaults, kde, gnome, etc.
directories here which vary according to user while still keeping
/usr/local for all users.
My ~/config contains things like "find ~/config -type d | hand edit some"
config/add-ons/media/decoders
config/add-ons/media/encoders
config/add-ons/media/extractors
config/add-ons/media/writers
config/add-ons/net_server
config/be/Applications
config/be/Demos
config/be/Preferences
config/bin
config/boot (Things my personal boot/login preferences)
config/doc
config/doc/postgresql
config/doc/postgresql/html
config/documentation
config/etc
config/fonts
config/include
config/include/openssl
config/include/postgresql
config/include/postgresql/lib
config/include/postgresql/libpq
config/lib
config/lib/perl5
config/lib/perl5/5.00503
config/lib/perl5/site_perl
config/lib/perl5/site_perl/5.005/BePC-beos
config/man
config/man/man1
config/servers
config/settings
config/settings/beos_mime
config/settings/beos_mime/application
config/settings/beos_mime/audio
config/settings/beos_mime/image
config/settings/beos_mime/message
config/settings/beos_mime/text
config/settings/beos_mime/video
config/share
config/share/postgresql
config/ssl
config/ssl/certs
config/ssl/lib
config/ssl/man
config/ssl/man/man1
Of course, on heavily user subscribed systems, some sort of
NT like COW technique might be nesc. if too many file duplications
occur in the ~/config directories. Having a good /usr/local would
prevent much of this growth, at least in theory. As would strict
quotas. :-)
Just some thoughts.
-- timothy.covell@ashavan.org. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/