Jesse Keating wrote:
On Mon, 2008-05-05 at 13:46 -0400, Marcus Leech wrote:
If "networking" needs to be explicitly turned on in this release
(after
Anaconda has been told to configure a
static interface, etc), then it fails to follow the principles of
least astonishment, IMNSHO.
It does not. The NetworkManager service will bring up the connections
that have been configured, including those during anaconda install. IF
it is not bringing them up at all that is a bug we need to fix. If it
is bringing them up too late that's also something to look at.
Yes, I started out using Network Manager (that's how Anaconda configured
everything).
But NetworkManager didn't run correctly due to SELinux issues. So I
went down the
"no NetworkManager" path.
I will try turning Network Manager back on, now that I've got a
fully-updated F9 image, and
see whether it reliably brings up eth0 on reboot.
--
Marcus Leech Mail: Dept 1A12, M/S: 04352P16
Security Standards Advisor Phone: (ESN) 393-9145 +1 613 763 9145
Strategic Standards
Nortel Networks mleech@xxxxxxxxxx
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
