Bug#276299: netcfg insists on confirming hostname and domainname
On Wed, 2004-10-13 at 17:06, Joey Hess wrote:
> Geert Stappers wrote:
> > The sane defaults come from domain name servers in the network.
> > > Please make it possible to surpress these questions.
> > For those who use "preseed/url=http://goldserver/seeds/ahost.txt"
> > ( "preseed/file=/hd-media/ahost.txt" users can avoid the confirm )
> You can still pass the same parameters to netcfg at the command line if
> you're doing network preseeding (unless you run out of kernel command
> I don't really think this is a bug in netcfg. Prompting for the hostname
> is the correct behavior in general. And I've had no problem stopping it
> from prompting by using preseeding.
I've not used preseeding, so I may be all wet here. nevertheless...
The scenario that has a problem is where you are using preseeding for
everything *but* hostname and domainname. You are getting host and
domain name from DHCP.
There should be some way to tell preseeding that you want it to trust
DHCP and use it for getting what can be gotten -- not to bother the user
unless some critical parameter can't be gotten from DHCP.
The time this is important is when you are cloning a bunch of systems
that you want to be identical in every way *except* hostname, which you
expect to get from DHCP. This is more common than you might imagine in
large commercial installations.
Just my tuppence worth...