People are tempted to use the pkgchk -n command to check if there are any errors in the installed packages. This is ok. But it is NOT ok at all to use pkgchk -f to fix things up. The Uw7/OSR6 Release 7.1 Getting Started Guide specifically states,
on p. 65,
'It is typical to see a number of errors when running this command
(pkgchk or pkgchk -n), due to the number of and interaction
between the various packages on your system. You should make a
note of any errors you find, but do not attempt to fix these
errors with pkgchk -f. This command is currently not
supported and may cause your system to fail or not reboot.
There is no current workaround.'
I like to run:
pkgchk -n base 2>&1 > /tmp/pout
Less the pout file and fix what's wrong. Post to comp.unix.unixware.misc (c.u.u.m) with questions if you have troubles.
<mschalit@pacbell.net>
gerberb@zenez.com |