Linked by Thom Holwerda on Mon 30th Jan 2012 20:39 UTC
General Unix Finally something really interesting to talk about. If you've used UNIX or any of its derivatives, you've probably wondered why there's /bin, /sbin, /usr/bin, /usr/sbin in the file system. You may even have a rationalisation for the existence of each and every one of these directories. The thing is, though - all these rationalisations were thought up after these directories were created. As it turns out, the real reasoning is pretty damn straightforward.
Thread beginning with comment 505231
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: About time...
by tuaris on Tue 31st Jan 2012 01:25 UTC in reply to "About time..."
Member since:

While I approve of Fedora 17's idea, I still think that GoboLinux still has the best idea thus far. Why make things cryptic and messy on purpose? in GoboLinux you know the programs are stored in /Programs

Reply Parent Score: 2

RE[2]: About time...
by Alfman on Tue 31st Jan 2012 03:34 in reply to "RE: About time..."
Alfman Member since:


Thank you so much for the pointer to GoboLinux, it's a great concept!! In my own distro I faced many similar challenges when I tried to modernize the legacy paths since so many applications hard code them.

I found using symbolic links worked, but that's very unclean when the namespace is cluttered with both the old and new paths. I see that GoboLinux solves this with a new kernel feature called GoboHide, which provides an element of backwards compatibility while cleaning directory listings.

Reply Parent Score: 4

RE[3]: About time...
by bogomipz on Tue 31st Jan 2012 20:33 in reply to "RE[2]: About time..."
bogomipz Member since:

Personally, I think K&R made a mistake when they decided that names starting with a dot should be hidden. It would have been much more flexible to have the hidden flag as an attribute you could set on any file or folder. GoboHide would then not be necessary.

Reply Parent Score: 2