[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libc5 / libc6
On Sun, 11 Oct 1998, Stanislav Malyshev a.k.a Frodo wrote:
> Well, I just had to say that you should look for /usr/doc/glibc...
/usr/doc/glibc only lists changes from standards...
> > PS: WHEN TINKERING WITH LIBRARIES KEEP A BOOT / ROOT DISKETTE HANDY AND
> > MAKE A LOG OF YOUR CHANGES. NOTICE THE CAPITALS. NOTHING WORKS WITHOUT
> > LIBRARIES ON AN ELF SYSTEM, NOT EVEN INIT.
>
> It is not bad to have also a kit of static utilities, like ln, cp, mv, or
> even statically linked shell, if one goes to play with libraries.
Let's start with having a statically linked INIT, LOGIN, GETTY and all
that yes ? The static utils are about as useful as a shoe for a wooden
foot without. See below:
plp4:~# ldd $(which init)
libc.so.5 => /lib/libc.so.5.3.12
plp4:~# ldd $(which bash)
libtermcap.so.2 => /lib/libtermcap.so.2.0.8
libc.so.5 => /lib/libc.so.5.3.12
plp4:~# ldd $(which login)
libc.so.5 => /lib/libc.so.5.3.12
plp4:~# ldd $(which stty)
libc.so.5 => /lib/libc.so.5.3.12
there is almost NOTHING that is not linked against libc on an ELF system.
Peter