|
Description
|
currently when zoneadmd sets up zone mounts during zone boot, in ensures that
all zone mount points are directories. this is unnecessarily strict since
for lofs mounts the mount point can be a file as well. zoneadmd should
take this into account and permit this type of behavior.
while working on this bug i notices a few more interesting behaviors in zoneadmd
- if the user specifies a non-absolute mount path in the zone configuration
then zoneadmd will core dump on an assert() in valid_mount_path().
- if a user specifies a non-canonical path in the zone configuration that
zone should fail to boot, and it will fail to boot if that path exists.
but if that path doesn't exist then the first time they try to boot the
zone the path will be created and the zone will successfully boot, but
the next time they try to boot the zone (or if they reboot the zone) the
zone will fail to boot and complain that the mount path is non-canonical.
- normaly if a mount path doesn't exist within a zone, then zoneadmd will
create it (this holds true for zonecfg ipd mounts, zonecfg fs mounts,
platform.xml global mounts, and other assorted mounts), but certain other
mounts (platform.xml non-global mounts and other assorted mount) don't
get created if they don't exist and instead the zone fails to boot. This
seems really inconsistent. zoneadmd should always create any point points
that it needs.
|