0004416: check for running in a zone

Notes
(0008109) bonivart (developer) 2010-07-13 10:49	This may be a good idea but we need to check for sparse zones since those are the problem with regards to writing to /usr.

(0009128) bonivart (developer) 2011-06-21 17:06	This is how it looks when installing a CAS package in a sparse zone (with read-only /usr): => Installing CSWcas-usergroup-1.44,REV=2011.05.02 (4/55) ... Please see /opt/csw/share/doc/cas_usergroup/license for license information. ERROR: attribute verification of </usr/sadm/install/scripts/i.cswusergroup> failed pathname does not exist ERROR: attribute verification of </usr/sadm/install/scripts/r.cswusergroup> failed pathname does not exist ERROR: attribute verification of </usr/sadm/install/scripts/i.cswusergroup> failed pathname does not exist ERROR: attribute verification of </usr/sadm/install/scripts/r.cswusergroup> failed pathname does not exist Installation of <CSWcas-usergroup> partially failed. Exiting pkgutil due to pkgadd error: 2 root@atvp1uascm021:~# The read-only status of /usr can be checked with mount and a useful message could be printed to help the user, something like: "You need to install the cas* packages in the global zone first". This should be added to all cas packages (now that they are separate).

Relationships

OpenCSW Bug Tracker