Thanks Robert,
I want to be clear. I have no problem with the "installed" system. I
don't even have NetworkManager installed.
My problem in during the automated installation process (which is called
kickstart). anaconda (the installer) allows one to automated the process
of installing (very useful when you are installing many systems).
During the automated installation process, one has the ability to run a
%post script to further customise the installed image. In my case when
running this automated install, the /etc/resolv.conf changes at some
point during the install and as a result all my post installation
scripts (that are run during the automated install) fail and the
"installed" system is not configured properly.
Ahmed
On Fri, 2011-04-08 at 13:20 -0500, Robert E. Blair wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I installed a server with the "workstation" configuration and simply
> "rpm -e'ed" NetworkManager. The result was just fine. The old network
> configuration layer is still underneath - the gui is gone though - but
> who used that.
>
> Nico Kadel-Garcia wrote:
> | On Wed, Apr 6, 2011 at 2:50 AM, Ahmed El Zein
> <[log in to unmask]> wrote:
> |
> |> I am looking at the logs and the only network related log that coincides
> |> with the resolv.conf file changing is:
> |> <29> Arp 6 06:40:49 NetworkManager[542]: ifcfg-rh:
> |> updating /etc/sysconfig/network-scripts/ifcfg-eth0
> |>
> |> at that point /etc/sysconfig/network-scripts/ifcfg-eth0 changes and gets
> |> an NM_CONTROLLED="yes" added to it and the /etc/resolv.conf file is
> |> replaced with the single lined one.
> |
> | NetworkManager, frankly, has no use on a typical server. Its dynamic
> | manipulations of network configuration are unpredictable, unintuitive,
> | and far more suited to a laptop or traveling desktop in an environment
> | where upstream DHCP is reliably configured. It is a complex and
> | powerful tool that *STILL* has no way to configure pair-bonding,
> | 'bridged' connections for KVM supporting hosts, or DHCP client
> | configuration with client identifiers except to use a text editor and
> | turn off NetworkManager by one means or another. It's one of the
> | upstream vendors least useful development efforts.
> |
> | Unfortunately, we're now pretty much stuck with it, due to all the
> | recent system dependencies on it. Ripping it out by the roots became
> | infeasible with Scientific :Linux 6. Fortunately, pre-configuring
> | 'NM_CONTROLLED=no' is a new capability, and doing so early in the
> | kickstart '%post' scripts seems to be very helpful in preventing such
> | issues. In syntax:
> |
> | grep -q ^NM_CONTROLLED= [filename] || \
> | echo 'NM_CONTROLLED=no' >> [filename]
> | sed -i 's/NM_CONTROLLED=.*/NM_CONTROLLED=no/g' [filename]
> |
> | Deducing the files to do this to is a bit more awkward, since you
> | don't want to touch '.bak' files or '~' files, but there are functions
> | to do that already available in the /etc/sysconfig/network-scripts/
> | utiliti4es. Do you need help with that?
>
> - --
> Robert E. Blair, Room C221, Building 360
> Argonne National Laboratory (High Energy Physics Division)
> 9700 South Cass Avenue, Argonne, IL 60439, USA
> Phone: (630)-252-7545 FAX: (630)-252-5782
> GnuPG Public Key: http://www.hep.anl.gov/reb/key.asc
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
>
> iD4DBQFNn1IAOMIGC6x7/XQRArHQAKC3ou2RC19qeg401vU4Lz6ocwJ8ngCXaeqz
> z1yTtl8N+iMCiieNaNT1pw==
> =cauz
> -----END PGP SIGNATURE-----
--
Ahmed H. El Zein
Data Services Specialist
ANU Supercomputer Facility
Room 315, Leonard Huxley Building (#56), Mills Road
The Australian National University
Canberra ACT 0200 Australia
T: +61 2 6125 0539
F: +61 2 6125 8199
M: +61 4 4913 5073
W: http://anusf.anu.edu.au/
CRICOS Provider #00120C
--------------------------------------------
|
