Technical article 104923

Accessing libcrypt.a causes tar to fail after booting from my boot/root floppies

OpenServer 5.0.0

Written · Last revised

Problem

When using the tar(C) command after booting from my emergency root and boot floppies, this error occurs:

dynamic linker: tar: cannot open /usr/lib/libcrypt.so

Why is the tar(C) command failing and how do I prevent similar failures in the future?

Cause

When creating the boot and root emergency floppy disks for your installation, the file "/usr/lib/libcrypt.so" was not copied to the root floppy diskette.

Solution

There are two solutions for this issue: a temporary, quick solution for the existing root floppy diskette (step 1), and a long-term solution for any future root diskettes you may make (step 2).

1. After creating the root floppy diskette, mount the root floppy to the /mnt directory:

# mount /dev/fd0 /mnt

(The above assumes you are using the first floppy drive.)

After mounting the root floppy, copy the crypt library to the appropriate directory on the root floppy:

# cp /usr/lib/libcrypt.so /mnt/usr/lib

When the file has been copied, unmount the root floppy from the mountpoint:

# umount /mnt

2. To prevent this error from occurring in all future versions of your boot/root emergency floppy diskettes, edit this file:

# vi /usr/lib/mkdev/fd

Locate the lines that looks similar to this:

# The following is a list of core utils that
# must be placed on the
# root floppy filesystem.
core_utils="
./usr/lib/libc.so.1
./usr/lib/libsocket.so.1
./usr/lib/librpcsvc.so
.
.
.

Add this line after the librpcsvc.so entry:

./usr/lib/libcrypt.so

And save the new fd script, exiting the editor.

Future versions of the root floppy you create will no longer generate the described error when accessing the tar(C) utility.

From the Xinuos technical article database, record 104923. Reproduced with permission. The original is at www.sco.com/ta/104923, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.