Jan Damborsky wrote: ... > I see - thank you for clarifying this. > Looking at Alok's preliminary webrev, it is going to introduce > new 'net' instance of svc:/system/filesystem/root SMF service > which will be enabled in case there is a boot from network > detected - it contains all network related stuff necessary > to establish working AI environment. > > I am thinking if that might be the viable place to absorb > this fix, as it deals with network configuration. Assuming > that the fix would be decomposed into functions for better > readability, following logic would be added to that new 'net' > SMF instance: > > . /lib/svc/share/net_fs_include.sh > > INIT_NET_STRATEGY=`determine_network_boot_strategy()` > > if [ "$INIT_NET_STRATEGY" != "dhcp" -a "$INIT_NET_STRATEGY" != "manual" > ] ; then > # network strategy not determined, report failure and abort > exit $SMF_EXIT_ERR_FATAL > fi > > configure_network($INIT_NET_STRATEGY) > # process return code > > [...] > > if [ "$INIT_NET_STRATEGY" == "manual" ] ; then > configure_dns() > # process return code > fi > > > Do you think it might be suitable place for those modifications > or might it be better to consider different approach ? >
I tend to think that this really should be in something like the network/physical service, although the code to set up resolv.conf in the general cases appears in network/service (note that script is also invoked in other contexts such as NWAM to do that work). Have you looked at that as an option? Dave
