Darren J Moffat wrote:
> On 12/05/2010 17:01, Sebastien Roy wrote:
>> The svc:/network/install service will support configuring one IPv4
>> interface and/or one IPv6 interface and, optionally, a default route
>> reachable by these interfaces. The service will define two property
>> groups, one for an IPv4 interface and one for an IPv6 interface. The
>> service will use its properties and ipadm(1M) to configure the network
>> interfaces. And similarly, the service will use its properties and
>> route(1M) to define a default route.
>
> Why is this limited to a single address for v4 and v6 ?
>
> Can multiple instances of network/install be created in a profile and be
> activated by the installer to create hosts with multiple IP addresses ?
> As is I believe possible today with jumpstart ?
>
>
> For the DNS configuration why are the resolv.conf "options", "sortlist"
> directives not supported for configuration in svc:/network/dns/install ?
There seem to be quite a few issues in the same area:
- Where are NIS and LDAP? Or are they not needed by this part of
the installation process?
- How does routing configuration work? Are "default routes" the only
thing that's ever needed?
- What about datalink configuration?
- What about systems that need to have IPMP or other IP-level bits
such as tunnels or IPsec?
I think what might be missing here are the boundaries of this case. I'm
a little queasy with the idea of assuming that the only interfaces that
matter are available-at-boot Ethernet drivers with simple IP
configuration and not much else, but perhaps it makes sense in some
particular (limited?) context.
Is there some case that describes what the "Solaris Next" installer can
and can't do over a network?
--
James Carlson 42.703N 71.076W <[email protected]>
_______________________________________________
opensolaris-arc mailing list
[email protected]
