Bug 450131 - Can't run system-config-network-cmd in kickstart
Summary: Can't run system-config-network-cmd in kickstart
Keywords:
Status: CLOSED DUPLICATE of bug 451756
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-network
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Harald Hoyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-06-05 14:42 UTC by Chris Adams
Modified: 2008-11-28 15:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-28 15:30:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Chris Adams 2008-06-05 14:42:08 UTC
I have kickstart files that run system-config-network-cmd in %post to configured
the installed networking.  That no longer works with Fedora 9, because s-c-n-cmd
apparently tries to talk to hal via dbus.  I can start the messagebus service in
the kickstart %post, but since hal is already running (in the anaconda root), I
can't start it in the chroot %post for the kickstart script to use.

Is there any way around this?  What is the recommended way to configure static
network interfaces in a kickstart?

Comment 1 Jiri Moskovcak 2008-11-28 15:30:26 UTC

*** This bug has been marked as a duplicate of bug 451756 ***


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