Description of problem:
The fact that an install is happening via jump drve, CD/DVD, or floppy is
irrelevant to whether the network should be brought up or not.
The only meaningful test for whether the network should be brought up or not is,
"Do I know how?" If you do, then do it. And if not, don't. Period.
Second-guessing whether the user's %post is going to try to do a "yum update" or
"wget" (etc) is pointless.
Version-Release number of selected component (if applicable):
Build an installer DVD w/ "ifconfig -a ; netstat -n -r" in the %post section.
Steps to Reproduce:
1. Build an installer DVD, with "network --device eth0 --onboot yes --bootproto
dhcp" in it, and "ifconfig -a" in the %post section.
2. Boot off it.
3. Check vty3 for output.
eth0 (or whatever) will not be "up" nor will it have an IP address, etc.
The environment for the %post scripts should be whatever the environment of the
rest of the install was (regarding mounts, network interfaces, modules, etc)
plus as much of the state that the eventual target machine should have (which is
already partly the case anyway, right? all partitions are formatted and mounted
by the time %post runs... so why not the network as well?).
Created attachment 129095 [details]
In-house script to create cups printers
A more concrete example of why this needs to be done is the following. I have a
simple script (attached) which I like to call from %post processing when doing
unattended local (re)images. The script looks something like:
which creates a bunch of printers using CUPS. The only problem is that the CUPS
daemon listens on localhost:631 ... which isn't available unless:
gets done. So at the VERY least, lo needs to be up, running, and configured...
even if no other interfaces are.
Committed a potential fix. I will test it next time we build a new anaconda so
the debug procedure for something on a CD is slightly less complicated.
I just tried a PXE/NFS install from rawhide (20070111) and the loopback
interface was not brought up.
Do the real interfaces at least get brought up?
Found where we're not bringing up loopback and fixed it. This should be better
in the next build of anaconda, then. Back to MODIFIED.