> When upgrading to newer kernels there is a necessity for upgrading
> libraries such as libc. The Livingston software was written for Linux
> 1.2.13 with libraries which were current at the time 1.2.13 was current.
> It is not unusual at all to have binaries written for earlier systems to
> operate erraticly when trying to run on a more up to date system.
Bootup: Sat Oct 26 20:29:42 1996 Load average: 0.03 0.04 0.00 3/64 19228
user : 2d 17:28:33.72 1.4% page in : 220668741 disk 1: 2140307r 5619362w
nice : 0:00:00.00 0.0% page out: 90432678 disk 2: 14448568r64486651w
system: 8d 11:20:11.41 4.3% swap in : 1293093 disk 3: 3400857r 1296946w
idle : 185d 11:52:28.94 94.3% swap out: 12984
uptime: 196d 16:41:14.05 context : 1142120932
That's a system running a 2.0.2x kernel...but it's totally a.out...even
the kernel was compiled a.out. Newer libs are recommended, but not
absolutely required. In addition, I have numerous systems running 2.0.x
kernels that have been upgraded to ELF compatibility, but are still
primarily a.out systems. Application software (like PM Console) should not
really care what kernel version you have. In fact, I'd say Livingston might
be better off continuing to build a.out tools as there are actually places
still running 1.2.13 and all a.out software.
------------------------------------------------------------------
Jon Lewis <jlewis@fdt.net> | Unsolicited commercial e-mail will
Network Administrator | be proof-read for $199/hr.
________Finger jlewis@inorganic5.fdt.net for PGP public key_______