Hi Mark, it seems this requirement is captured by following enhancement:
5556 AI must provide way to switch of populating hostname from DHCP server As far as implementation is concerned, the plan is to take advantage of SMF Enhanced Profiles for those kind of post-install configuration tasks. Might it be what you are looking for ? Thanks ! Jan On 04/18/09 02:11, Mark S. Wedel wrote: > By default, if using automated install, the hostname (/etc/nodename) of the > system is set to opensolaris. This is not good in our lab environment - > having a large number of machines which just say 'opensolaris' when logging > in is sure to cause confusion. > > I notice that with bug 5554, the hostname can be specified in the manifest > file. This works, but now requires that there be hundreds of distinct > manifest files (one for each host) to set the hostname. The rest of the > values in the manifest file are more generic and could apply for a large > number of hosts. Having one manifest per machine becomes a maintenance > headache. > > Ideal case is that hostname is whatever dhcp reports (dhcpinfo -i e1000g0 > hostname for example). I can certainly see many cases where that might not > be desirable (the DHCP address really is dynamic or DHCP does not provide > useful hostnames) > > Ideal solution would be same way to configure it - maybe something like: > propval name='use_dhcp_hostname' ' value='true' > > Which if set, uses dhcpinfo to get hostname, if not, falls back to hostname > propval and then opensolaris. > > Any plans to add such functionality? Is there a way to do this right now?
