[CentOS] turning off udev for eth0
Denniston, Todd A CIV NAVSURFWARCENDIV Crane
todd.denniston at navy.milWed Jan 4 14:22:27 UTC 2012
- Previous message: [CentOS] turning off udev for eth0
- Next message: [CentOS] turning off udev for eth0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of Les Mikesell > Sent: Tuesday, January 03, 2012 22:24 > To: CentOS mailing list > Subject: Re: [CentOS] turning off udev for eth0 > > On Tue, Jan 3, 2012 at 5:13 PM, Peter Larsen > <plarsen at famlarsen.homelinux.com> wrote: > > > >> Is there no way to alter udev's behaviour? Is udev even > >> needed on a server system using virtual hardware? > >> Altering the rules file not a big deal in itself but it > >> adds needless busywork when setting up a new guest. <SNIP> > > It's a very common problem. Another way is to have a %post script in KS > > or after initial startup as a VM, that fixes the file based on what the > > VM properties are. > > It happens in real hardware too if you move a disk to a different > chassis, clone a drive, restore a backup to similar hardware, etc. > > Where is the best documentation on what triggers the rules to be > rewritten, how the bios location works, etc.? I gave up on tricking UDEV, it was easier to work with the system with my clones. `system-config-network-cmd -e` yields a text file that, you can have either a firstboot script or the booting sysadm, `system-config-network-cmd -i -c -f file.txt` will pull back in and reconfigure the system after ifdown'ing eth0. For good measure I also blanked (and restorecon'd) resolv.conf and hosts prior to pulling in the file. Good luck.
- Previous message: [CentOS] turning off udev for eth0
- Next message: [CentOS] turning off udev for eth0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list