SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Okay, forgive my ignorance, but I'm a bit confused. Why is it that Linux seems to have both a /usr/local and a usr/share? I'm assuming /share is so programs can share libraries and whatnot such as GTK, but isn't that what /usr/lib should be for?
Is there a way to get rid of the /share placement and just have all the non-essential programs installed into usr/local?
I've always thought /opt was a bit of a redundancy, as well. I'd say the filesystem layout is up for a bit of revision, but I don't think the traditionalists in our community would go for that. I guess it's good to have lots of options, but I think there should be some consolidation.
Well, if there IS no real point, then I'd like to begin working on a way to get my Slack install filesystem trimmed down some. Having all non-essential programs in /usr/local would be SO much better. And you're right, I forgot all about /usr/opt.
Well, the problem is that in order to get a custom filesystem layout, you'll need to either compile all your own programs, or use binary packages that only install to /usr/local or /usr...
Many, such as kde and gnome do use share and opt.
It's quite doable, and there are a few different tree layouts out there, some distros use customs jobs. I've thought about it myself, but I'm not so irked by the redundancy that I'll take action
Well, it bugs me. Plus, actually, it's not very conducive to helping newbies out, either. I don't want to lose that great feeling Slackware has from doing custom configs and whatnot, but there's a purpose to that (configurability and power). Redundant filepaths aren't really conducive to learning or customization, except for learning the paths themselves, heh.
If I get annoyed enough to seek resolution, I'll let you know what I find.