Bug 130332 - Firstboot can't set up network because of missing /etc/modules.conf file
Summary: Firstboot can't set up network because of missing /etc/modules.conf file
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: 2
Hardware: noarch
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-08-19 08:24 UTC by Mogens Kjaer
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-07-06 21:40:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mogens Kjaer 2004-08-19 08:24:37 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
I use kickstart to set up multiple FC2 machines.

The machines are set up initially with DHCP, and I want to
specify the correct static IP address during the firstboot
session.

I've set

firstboot --reconfig

in the kickstart file.

However, when firstboot starts, I get an error in
/usr/share/firstboot/modules/networking.py because the file
/etc/modules.conf is missing.

Shouldn't this be changed into /etc/modprobe.conf ?


Version-Release number of selected component (if applicable):
firstboot-1.3.14-1.noarch.rpm

How reproducible:
Always

Steps to Reproduce:
1. kickstart install
2. reboot
3. firstboot crach
    

Additional info:

Comment 1 Mogens Kjaer 2004-08-19 13:24:01 UTC
I've solved the problem by adding these three lines
to the %post section of the kickstart file:

cp /usr/share/firstboot/modules/networking.py
/usr/share/firstboot/modules/networking.py.old
sed 's/modules.conf/modprobe.conf/'
</usr/share/firstboot/modules/networking.py.old
>/usr/share/firstboot/modules/networking.py
rm /usr/share/firstboot/modules/networking.py.old

Comment 2 Matthew Miller 2005-04-26 15:36:56 UTC
Fedora Core 2 is now maintained by the Fedora Legacy project for
security updates only. If this problem is a security issue, please
reopen and reassign to the Fedora Legacy product. If it is not a
security issue and hasn't been resolved in the current FC3 updates or
in the FC4 test release, reopen and change the version to match.


Note You need to log in before you can comment on or make changes to this bug.