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

[William Park]

I think we're speaking past each other.  Historical convention has
accumulated a lot of baggage.  What you're typing only makes sense
in the ecosystem it's intended to be used.  If you're supposed to
care which library you're supposed to link with, then what you typed
is inadequate and vague.

Also, you're making selective argument.  For example, 'named' is
DNS server, and 'bind' is its package name.  Another, 'httpd' is
web server, and 'apache' is the package name.  In these and other
cases, you have to know their names and where they are coming from.
I'm merely saying that, if we had to care from the beginning, then
a lot of headache could be avoided.

-- 

William



----- Original Message -----
> From: Lennart Sorensen <lsorense-1wCw9BSqJbv44Nm34jS7GywD8/FfD2ys at public.gmane.org>
> To: tlug-lxSQFCZeNF4 at public.gmane.org
> Cc: 
> Sent: Tuesday, February 7, 2012 2:21:32 PM
> Subject: Re: [TLUG]: Understanding the bin, sbin, usr/bin , usr/sbin split
> 
> On Tue, Feb 07, 2012 at 10:11:43AM -0800, William Park wrote:
>>  Hmm... don't you have to know where the library is coming from?
>>  I mean, libc.so from GNU C and libc.so from busybox are awefully
>>  different.
> 
> No you don't.  When compiling you really just need:
> 
> cc -o putput input.c -lpthread
> 
> Doesn't matter which libc as long as the compiler was originally
> configured for a given target.  My makefile certainly doesn't care if
> it is glibc, eglibc or uclibc or even klibc.
> 
> -- 
> 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
> 
--
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