Colin, shouldn't d-i just reprocessed the netcfg directive from the
network-retrieved preseed file? Intuitively, you would expect d-i to do
the right thing and apply the netcfg configuration defined in your
preseed file, wherever it is retrieved from. The fact that netcfg
directive are not being processed when the preseed file is retrieved
from the network is inconsistent.
The Debian manual describe a hackish work-around for that:
"""
Although preseeding the network configuration is normally not possible when
using network preseeding (using “preseed/url”), you can use the following hack
to work around that, for example if you'd like to set a static address for the
network interface. The hack is to force the network configuration to run again
after the preconfiguration file has been loaded by creating a “preseed/run”
script containing the following commands:
killall.sh; netcfg
"""
So, I wonder: can we make d-i re-run netcfg automatically after it
fetched it's preseed file specified by preseed/url, so that the netcfg
directive are applied as it would normally be expected?
Thanks.
--
description of preseeding netcfg settings and when to use preseed file and when
to use kernel command line settings not clear enough
https://bugs.launchpad.net/bugs/262330
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
