modprobe.conf?
Kevin J. Cummings
cummings at kjchome.homeip.net
Fri May 28 03:06:25 UTC 2010
On 05/27/2010 10:54 PM, Andre Robatino wrote:
>
> I did a local F13 install from the DVD (not enabling any external repos), then
> used NetworkManager to set eth0 to connect automatically (right-clicking on the
> NetworkManager applet, Edit Connections..., etc.) At this point, I still had no
> /etc/modprobe.conf file. It was only after using s-c-n to change my network
> settings that the file appeared. The bug seems 100% reproducible by any type of
> network editing with s-c-n.
>
> If you install again, see if you can match up the time on the file with
> something in /var/log/yum.log, or if it happens after all packages are installed.
Got me to thinking. So I looked at my F13 test system, and sure enough,
I had an empty /etc/modprobe.conf file. I can't remember if I ran
system-config-network or not on May 9th at 23:04, but I *do* remember
disabling NetworkManager and re-enabling the network service at some
point. (I got sick and tired of not being able to login to the system
remotely unless I was also logged in at the console! Stupid idea!)
I'm going to delete it and then reboot the system (its a kernel behind
anyways....) and see if the file returns.
--
Kevin J. Cummings
kjchome at rcn.com
cummings at kjchome.homeip.net
cummings at kjc386.framingham.ma.us
Registered Linux User #1232 (http://counter.li.org)
More information about the users
mailing list