I'm trying to build a new ramdisk that uses glibc 2.2.2. My approach was to
take a working ramdisk and to replace the libraries and links in the lib
directory with the new ones.
However when Linux is booting up from this ramdisk I'm told that
libutil.so.1 doesn't exist. In fact it does and is a symbolic link to the
actual library file. I've removed and recreated this link 3 or 4 times and
am pretty sure it is correct.
Is there something obvious about symbolic links that could be causing this
problem.
Here is the output around the failure point:
--------------
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 72K
init: errKernel panic: Attempted to kill init!
or while loading shared libraries: libutil.so.1: cannot load shared object
file: No such file or directory
---------------
and the output for the ramdisk that works from the same point:
----------------
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 72K
INIT: version 2.74 booting
INIT: Entering runlevel: 3
Starting system logger: syslogd
Starting INET services: inetd
Starting pcmcia Starting PCMCIA services: cardmgr.
Linux login:
-----------------
All straws gratefully clutched.
jon
_______________________________________________
http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm
Please visit the above address for information on this list.
