zlacker

[return to "Understanding the linux filesystem (/etc, /var, /bin, /opt etc.)"]
1. hendry+A4[view] [source] 2013-06-26 03:36:03
>>alexho+(OP)
I prefer the simpler filesystem proposal from http://sta.li/filesystem

The FHS has been poorly done for years. For e.g. where is the canonical place for a Web vhost root? /srv/www? /srv/web? /var/www?

◧◩
2. gizmo6+i7[view] [source] 2013-06-26 04:28:57
>>hendry+A4
That looks like a really cool idea.

One thing I don't like about its filesystem is its insistence that all binaries go into /bin. As a user, I greatly appreciate the concept of having some sort of /local directory to distinguish between files (or just executable in this case) which the end user installed and which are part of the distribution. If you abandon the idea that /bin has no subdirecories, then I could see /bin/local as a viable alternative (although I think I would still prefer a /local folder where that had /local/bin, /local/etc ...).

◧◩◪
3. ahomes+Ep1[view] [source] 2013-06-26 21:23:31
>>gizmo6+i7
I really dislike the idea of /usr/local. Users should install everything through the package manager, otherwise stuff just collects in /usr/local and there's no easy way to remove it (if 3 different users install 5 different programs in /usr/local, how do you remove one of those programs?).

Also, one thing I think is needed right now is an easy way for users to install programs in $HOME, only for themselves (not system-wide) and without root access. On most distros (AFAIK), you can only do "sudo apt-get install PKG" (or something similar) which installs the package system-wide for everyone, or you can go through the whole configure&&make fun to install a program in your home directory. I'd like to see something like $HOME/bin and $HOME/lib where users can auto-install binaries that only they use.

[go to top]