On 06/29/10 03:00 PM, [email protected] wrote:
Hi,
I am using the automated installer from build 137 to install the latest
development builds. We had a couple of questions related to the
networking aspect of the install.
Note that you must boot from an AI boot service that is the same build
as the build you are installing (this doesn't mean the server has to be
running the same build, though normally later builds on servers are
preferred to older); any other configuration is subject to unexplained
failures (and your first question below could potentially be a result of
mismatches).
1. On certain systems, after installation, none of the network
interfaces are enabled, while the interfaces are enabled on some other
machines. What is causing the network configuration to be dissimilar for
different hardware?
Network auto-configuration is handled by the NWAM functionality,
nwam-discuss might be better able to sort out your issues here.
2. Is it possible to provide the domain name, NIS settings etc as part
of an install service?
Not at this time. Additional nameservice configuration will be
available in future builds.
3.Using sys-unconfig we were able to configure network, but it was
necessary to redirect the console
to ttya because the splashimage took over the graphics console so you
don't see any output there. Is this a bug?
sys-unconfig & sysidtool are unaware of the graphical boot and are
planned for replacement with updated tools that will be able to cope.
However, you should be able to merely press any key early during
graphical boot to switch to text.
Dave
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
