Bernd Schemmer wrote:
Hi,
>>pkg -R /mnt fix
Been there; done that. Now the python scripts work again!
But I'm curious about the output of the pkg commands (see attachment)
I first did a pkg -R /mnt verify (log file pkg_verify.log), then a pkg
-r /mnt fix (log file pkg_fix.log) and then a pkg -r /mnt verify again
(log file pkg_verify1.log)
The errors in the logfile pkg_verfiy.log about invalid owner for files
and directories (xtrnaw7 instead of root) in the directory
/usr/share/local are "okay" - these directories are also in my package
so it's clear that I changed them by accident.
But the errors like this error message
pkg:/SUNWPython ERROR
hardlink: usr/bin/isapython2.4
Path and Target (usr/lib/isaexec) inodes not the same
link: usr/bin/python
target=//bin/amd64/python
link: usr/bin/python2.4
target=//bin/amd64/python2.4
I do not understand -- I did not change neither /usr/bin/isapython2.4
nor /usr/lib/isaexec. I did copy /usr/bin/ps (which should be a hardlink
to /usr/lib/isaexec) but copying that file shouldn't change anyhting I
think.
In addition, the pkg verfiy after the pkg fix still shows some errors
about invalid groups for directories -- shouldn't these errors also be
fixed by pkg fix?
Should I worry about those errors and do a pkg fix again?
Unfortunately, there are (ironically) still a few bugs in pkg fix and
verify; especially with links. I can't say with certainty whether you
should run pkg fix again or not or whether these are a real issue.
Cheers,
--
Shawn Walker
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
