Understanding the bin, sbin, usr/bin , usr/sbin split

Lennart Sorensen lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org
Tue Feb 7 16:26:39 UTC 2012


On Tue, Feb 07, 2012 at 11:18:12AM -0500, Christopher Browne wrote:
> It's a solution to certain, particularly simplistic, problems.
> 
> Those problems are fairly frequently occurring, notably with
> non-Unix-like application monoliths such as office suits and web
> browsers.  Indeed, those classes of applications tend to be
> sufficiently grandly bloated that I have the suspicion that it might
> be reasonable to statically link in the bloated library sets that they
> require.  It's not obvious that this would worsen space consumption or
> anything else too terribly materially, as they're already exceeding
> grandiose.
> 
> Embrace the "non-Unix-itude", I say...

So if a libssl bug is found and you update libssl to fix it, firefox is
still broken.  That's a great idea.

> Notice that if this set of (cr)applications got spun off in this
> fashion, it would make the attendant bloat that much more visible to
> everyone, and not have packagers holding their noses, trying to force
> these apps into the other procrustean beds.  There wouldn't need to be
> a "Firefox for Ubuntu" and "Firefox for Debian" and "Firefox for Red
> Hat" anymore :-).

Well fortunately I have iceweasel from Debian already, so I don't need
firefox'x own crazy idea of how to distribute software.

-- 
Len Sorensen
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wiki/Mailing_lists





More information about the Legacy mailing list