Sebastien Roy wrote:
Furthermore, just turning off one service that apparently isn't
directly linked to GDM should not block GDM from running... at least
NOT without some clear warning of what is happening or about to
happen.
This much isn't related to NWAM, but I agree that there's something
amiss here. The indirect dependencies between network/physical (default
or nwam, it doesn't matter) and graphical-login/gdm should be looked at,
as there's indeed no obvious logical relationship between a graphical
login screen and networking configuration. Perhaps a bug should be
filed.
Taking a quick look, many services individually specify requirements on
network/loopback and network/physical, rather than milestone/network,
and even the latter declares network/physical as required rather than
optional. Personally, I would have expected network-aware apps to rely
upon milestone/network, and leave the milestone to declare
network/physical as an optional dependency (although this is probably a
simplistic view of the world).
My guess is this:
fmri svc:/application/graphical-login/gdm:default
dependency require_all/none svc:/system/filesystem/local (online)
fmri svc:/system/filesystem/local:default
dependency require_all/none svc:/system/filesystem/minimal (online)
svc:/network/physical (multiple)
The comment in /var/svc/manifest/system/filesystem/local-fs.xml for this
dependency seems to implicate iSCSI as the reason for this:
<!--
With the introduction of iSCSI Boot, local filesystem
needs basic network setup (DHCP/IP and so on) to mount
-->
Hope that helps,
Brian
--
Brian Ruthven Sun Microsystems UK
Solaris Revenue Product Engineering Tel: +44 (0)1252 422 312
Sparc House, Guillemont Park, Camberley, GU17 9QG
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
