Re: [MLUG] need info

[Shawn Parker <EMAIL:PROTECTED>]

i think /configs, /users, /system and /programs is all a file system needs.

/configs - all your configuration files for different apps...basically 
/etc. but, to clean up the directory hierarchy, applications should 
create relevant directories under /configs; ie. /apache, /postfix, 
/mysql, etc.

/users - well, it's user directories. including /root. i also think /tmp 
should be a standard in each user directory

/system - anything and everything to do with basic system operation. 
/dev, /lib, /proc, /var, /sbin, etc.

/programs - all the compiled binaries, scripts and executables for programs.

i also think, although i don't know how hard it would be, restrictions 
should be put on where users can create directories. i'm very anal about 
my file systems. i hate it when users create directories all over the 
place. in my opinion, users should only have permission to create 
directories in the "users" space.  the ability to create documents and 
directories in / or any other directory is not needed (except by the 
superuser, and even then used sparingly).

this is one of my biggest problems with windows. users can create 
folders and files on the desktop, in c:\, in Program Files, etc. it's 
annoying. the only place to create, store and manage data should be in 
the respective user folder.

the problem with computers and operating systems in general is they 
aren't restrictive enough. if you limit the space a user can interact 
with, then you avoid simple problems like "where are my word documents, 
again?"

i think all the current file system structures suck. os x is better than 
most from what i hear.


Mike Miller wrote:

> On Tue, 4 Jan 2005, Jason McIntosh wrote:
>
>> A coworker and I were discussing this, and where binaries and other 
>> applications should be stored.  We both agreed, each program should 
>> have it's own directory.  Has anyone seen where gnome puts all it's 
>> libraries?  UGH.  I may like the gnome interface, but where they put 
>> stuff drives me nuts.
>
>
> We need a shell that will use a recursive path for binaries.  In 
> otherwords, you could use the usual /bin /usr/bin and whatever, but 
> the shell would find all binary files within all *subdirectories* of 
> those directories.  That would be nice.
>
>
>>>> Why would you want to use a simple name like "/programs" when you 
>>>> could use "/Program Files"??  ;-)
>>>
>>>
>>> Capital letters and spaces are evil! ;)
>>
>>
>> Perhaps they were evil originally, but not so much anymore.
>
>
> Oh no, they are still evil.  I was only kidding about the hideous 
> "/Program Files" which is a bizarre Microsoft convention.  It is much 
> better not to use spaces, not to use mixed case and not to use a long 
> string.  I'd go with /progs or /bin.
>
> You know, it doesn't have to be a system that can be understood just 
> by looking at the filenames.  You want too mnemonic names, but you 
> want short names.  If it takes a minute to learn them, that's fine, 
> but you will be typing them for the next 50 years, so you want them to 
> be short.
>
>
>> Now, there's an interesting thought, although I'd say what about 
>> creating a distro with everything truly separate and designed the way 
>> we'd like?  Call it MLUG Linux?  The Linux that makes sense?  I know 
>> not everyone likes Mac's on the list, but that's an example of a file 
>> system layout we could look at for examples.  Course, it'd be nice to 
>> get some input from other MLUG'ers out there.  Anyone have any other 
>> thoughts?
>
>
> I'm not sure that renaming root directories will be worth the effort.  
> I doubt it.
>
> On the other hand, a modification to bash so that it will look in 
> subdirectories in the given path seems like a really nice feature.  I 
> would do things like this...
>
> /usr/local/bin/genetics/aspex
> /usr/local/bin/genetics/merlin
> /usr/local/bin/genetics/genehunter
> /usr/local/bin/genetics/solar
> /usr/local/bin/misc/perlseq
> /usr/local/bin/misc/numalign
> /usr/local/bin/mine/check_tcp_logfile
> /usr/local/bin/mine/mail_word_of_the_day
>
> ...so that I could keep some organization in that binary directory.  
> It would help me to find files and it would help me to keep track of 
> which files came from which programs.  As it stands, I have to throw 
> everything into /usr/local/bin or create symlinks.
>
> I think this can be done by changing the way the internal hash table 
> is constructed from the given path.
>
> Mike
> _______________________________________________
> members mailing list
> EMAIL:PROTECTED
> http://mlug.missouri.edu/mailman/listinfo/members
>


-- 
Shawn Parker
Network Administrator
Cumulus Media
Columbia, Missouri - KBXR, KFRU, KOQL, KPLA
Jefferson City, Missouri - KBBM, KJMO, KLIK
573-449-4141 Ext: 331

_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members