I did quite exactly that but in the normal boot environment, but since you insisted that I should do all this in maintenance mode I ran 'beadm destroy <new-BE>', added '-s', booted the original image in maintenance mode and executed exactly the same commands you just listed. But still, there are unfixed errors (although they are fewer now).
The faulty packages are now: pkg://opensolarisdev/library/python-2/pyopenssl-26 pkg://opensolarisdev/library/desktop/gtk2 pkg://opensolarisdev/library/SUNWcs pkg://opensolarisdev/library/system/boot/real-mode pkg://opensolarisdev/library/system/library pkg://opensolarisdev/library/gnome/preferences/control-center I even retried the pkg fix process in the prior BE in maintenance med, without success > Robin Axelsson wrote: > > > The pkg fix was not successful at all even though > it said so, it didn't > > "fix" anything, the same errors remain. > > > > I don't understand how I can use 'pkg fix' when > booting the BE in > > single-user as you suggest. When I do that it will > only say: > > > > pkg: Requested "fix" operation would affect files > that cannot be modified in live image. > > Please retry this operation on an alternate boot > environment. > > Right. This is where you'd say > > beadm create new-be > beadm mount new-be /mnt > pkg -R /mnt fix ... > beadm unmount new-be > beadm activate new-be > reboot > > This creates a clone of the current BE, which is > compatible with the > current pkg(5) bits, and won't have the problem of > having to modify files > in use. > > Danek > _______________________________________________ > install-discuss mailing list > install-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/install-d > iscuss > -- This message posted from opensolaris.org
