>They don't have by default, but we still might want to apply
>SVr4 packages to the booted install environment - please see below.


>[3] Finished DC build and booted resulting AI ISO image - it contains 
>lock files:
>
>$ ls -la /var/sadm/install/
>total 18
>drwxr-xr-x   4 root     bin          512 Nov  6 01:08 .
>drwxr-xr-x   8 root     sys          512 Nov  6 00:54 ..
>-rw-r--r--   1 root     root           0 Nov  6 00:47 .door
>lrwxrwxrwx   1 root     root          36 Nov  6 00:58 .lockfile -> 
>/mnt/misc/var/sadm/install/.lockfile
>lrwxrwxrwx   1 root     root          36 Nov  6 00:58 .pkg.lock -> 
>/mnt/misc/var/sadm/install/.pkg.lock
>lrwxrwxrwx   1 root     root          43 Nov  6 00:58 .pkg.lock.client 
>-> /mnt/misc/var/sadm/install/.pkg.lock.client
>drwxr-xr-x   2 root     bin          512 Nov  6 01:08 admin
>lrwxrwxrwx   1 root     root          35 Nov  6 00:58 contents -> 
>/mnt/misc/var/sadm/install/contents
>lrwxrwxrwx   1 root     root          43 Nov  6 00:58 gz-only-packages 
>-> /mnt/misc/var/sadm/install/gz-only-packages
>dr-xr-xr-x   2 root     bin          512 Nov  6 00:47 logs
>
>However, those are just symbolic links to the read-only area:

So /var/sadm/install is readable but /tmp/misc is not readable?


># mount -p
>...
>/tmp/solarismisc.zlib - /mnt/misc hsfs - no 
>ro,nosuid,noglobal,maplcase,rr,traildot
>...
>
>This leads to the situation when pkgserv SMF service goes
>sometimes to the maintenance mode during boot, but not always.
>
>If I remove those 'dot' files from DC proto area and they don't end up
in the final ISO imageimage, pkgserv is allowed to manipulate them,
>since /var/sadm/install/ directory is writable:


So who creates the symbolic links?  I think we should not put the symbolic
links there.



>Assuming that we still would like to support installation of SVr4 packages
>during the installation process into running installation environment as 
>well
>as on target (e.g. in order to deliver missing third party device driver
>which is in SVr4 format), can we still go with pkgserv SMF service disabled
>in the installation environment or is there any reason why it should be
>enabled ?

No reason for the LiveCD & AI-install; these are really "throw away"
environments.  You will need to have a readable /var/sadm/install 
directory if you want to install packages, though.

Casper


Reply via email to