Hi,

    I did my first successful install of Debian 2.0 from a Cheapbytes
cd. It wasnt quite as slick as I would have liked it to be, but I did
get it working.

    I did have some problems initially with confiuring 'dip' to work.
(The ppp install script crashed with an error. Unfortunately, I didnt
record the error, so I'm not complaining). I initially thought, that
maybe there was some problem with the new binary version of 'dip' that
came with debian, since I was using the same chat script that worked
with my RedHat installation and 'dip' was failing to onnect to my ISP.
So, I thought that I would get the 'dip' sources and build it on my
system.

    There were some problems with the Makefile searching for  the
2.7.2.1 gcc-lib include directory instead of 2.7.2.3, but I got around
that. The show-stopper, however was that the Makefile couldnt find the
socketio.h include. I eventually traced this include down to the
libc5-altdev_5.4.38-1.1.deb package in the oldlibs directory on the
debian cd.

    I am vaguely aware that this release of debian changed from using
libc5 to libc6. I dont really know what that means. My question is this
: will I screw up anything if I install any of the older libraries? A
related question is : how come the socketio.h include is not present
with the newer libraries.

    (Oh, I did get 'dip' to work. Turns out there was a bug in my chat
script which was not serious with the older version of 'dip' present in
my RedHat distribution. However, the newer version of 'dip' that came
with Hamm took a more serious view of this bug. However, I would still
like an answer to my questions.)

    Also, I downloaded communicator 4.05 and tried to install it. Part
of the install process required using a program (that comes in the
communicator tarball) called 'vreg'. I am unable to execute this. It
says that it requires libc.so.5. Sure enough, I dont have libc.so.5, but
I do have a symbolic link of libc.so.6. Is this problem only a matter of
defining a sybolic link of libc.so.5 to the same library as pointed to
by libc.so.6, or do I have to build communicator from the sources on my
machine? Incidentally, the communicator program itself complain about
the absence of libXt.so.6. Where do I get this from?

Thanks,
Kenneth

Reply via email to