Subject: Re: why /bin and /sbin static
To: Charles M. Hannum <email@example.com>
From: None <firstname.lastname@example.org>
Date: 03/19/2001 20:12:30
> On Mon, Mar 19, 2001 at 08:24:39AM +0100, email@example.com wrote:
> > i still cant understand why such simple program like df for example needs
> > OVER 100kB of library code. good written accounting software fits in few
> > hundreds kB!
> Bad example. B-)
> -r-xr-sr-x 1 root operator 70884 Jan 22 19:35 /bin/df
on what arch?
> The problem with things like ls(1) is more complex. Once you start
> dealing with user names, you have to pull in all of DB, which is huge,
> plus the rest of nsswitch stuff, which BTW includes YP and RPC, and the
> message catalog system, and...
> This stuff should be in separate, dynamically loaded, libraries. You
> use getpwman(3), it loads libnsswitch_db.so, which loads libdb.so, and
> goes from there. Or loads libnsswitch_yp.so, and that pulls in
> librpc.so. None of this crap should be in libc in the first place.
> It's insane.
no. dividing libraries is inefficient with shared libs. it takes more
one big libc for all would be better ...