Linked by Thom Holwerda on Thu 3rd Nov 2005 20:03 UTC, submitted by tup
Linux "I was impressed by the way GoboLinux handled. This distribution clearly has a well-defined identity of its own, and the authors' philosophy shows in every detail of the system. The system is fast, without a grain of bloat in it." GoboLinux' most defining feature is its filesystem layout, which does not follow the Free Standards Group's Filesystem Hierarchy Standard, but is more like OSX' layout.
Thread beginning with comment 55353
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: meh
by on Thu 3rd Nov 2005 23:51 UTC in reply to "RE: meh"

Member since:

It's a wonder I haven't already; it's happened before.

Off the top of my head:
1) the giant mess of links
2) the old fs layout is still present along with the new (either pick one or the other, not both!)
3) old fs layout is required for some tasks (as far as I can tell, there is no /dev equivalent in the new layout)

-bytecoder

Reply Parent Bookmark Score: 0

RE[3]: meh
by hobgoblin on Fri 4th Nov 2005 00:09 in reply to "RE[2]: meh"
hobgoblin Member since:
2005-07-06

1) well there are inventigations into alternatives. like say unionfs. still, using ls -l helps in figuring out those links.

2) hey, even os x have that old fs layout there. only that os x hides it on the file manager level, while gobo have to use a kernel module to do so. this to enable it to play nice with all the diffrent file managers out there.

3) the dev tree us mounted under /system and symlinked to the / iirc...

Reply Parent Bookmark Score: 1

RE[3]: meh
by Mohjive on Fri 4th Nov 2005 19:57 in reply to "RE[2]: meh"
Mohjive Member since:
2005-11-04

1) There is no mess of links. Executables all have links in /System/Links/Executables, libs in /System/Links/Libraries,... you get the point. There's an exception and that is that settings are linked in /System/Settings.
2) There is not a chance that a small dist like that would have the possibility to patch every program that has hard coded paths in it. I do not even think that a larger dist would have that possibility. The old one is hidden from the user and is never used; it's only there for compability reasons
3) /System/Kernel/Devices, there's an equivalent for everything.

Reply Parent Bookmark Score: 1

RE[3]: meh
by renox on Fri 4th Nov 2005 23:33 in reply to "RE[2]: meh"
renox Member since:
2005-07-06

Mmm, personally I don't mod down on the content of the post (it's your opinion wether I agree or not is irrelevant) but on the form: if it's insulting, then I mod down.

Now on your post about the giant mess of links, either you get a mess of:
a) directories with very long PATH, LD_LIBRARY_PATH, etc.
b) files within directories: with everything in a few select location, which is the current 'normal Linux way'.
c) links as in Gobo Linux way.

So either way it's a mess, which is 'normal': there are many, many applications so somehow they must be organised..
I think that c) is better than b) for applications, for shared libraries, I don't know how they're handled on Gobo and it's always the hard part..

Reply Parent Bookmark Score: 1