Bug 1139176 - kickstarts network command not know --biosdevname option
Summary: kickstarts network command not know --biosdevname option
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora Documentation
Classification: Fedora
Component: install-guide
Version: devel
Hardware: i686
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Bokoc
QA Contact: Fedora Docs QA
URL:
Whiteboard:
Depends On: 1135692
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-08 10:11 UTC by Martin Kolman
Modified: 2014-12-16 17:11 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1135692
Environment:
Last Closed: 2014-12-16 17:11:44 UTC
Embargoed:


Attachments (Terms of Use)

Description Martin Kolman 2014-09-08 10:11:08 UTC
+++ This bug was initially created as a clone of Bug #1135692 +++

Description of problem:
starting F20 i386 installation from kickstart file which contain network command
as:
network --onboot=yes --noipv6 --bootproto=dhcp --biosdevname=0 --hostname=mypc

ends with anaconda error:

anaconda 20.25.15-1 for Fedora 20 started.
The following problem occured on line 35 of the kickstart file:

no such option: --biosdevname


Expected results:
option should be accepted. Perhaps should be created (template?) udev config rules file in /etc/udev/rules.d/ also.

--- Additional comment from bcl on 2014-09-03 03:15:05 CEST ---

--biosdevname is no a valid option.

--- Additional comment from Frantisek Hanzlik on 2014-09-06 12:34:43 CEST ---

Then is bug in Fedora 20 Installation Guide, where is (chapter 15.4. Kickstart Options) this parameter mentioned.

Comment 1 Petr Bokoc 2014-10-20 14:52:27 UTC
Option has been removed.

The change will appear in the Fedora 21 Installation Guide once it comes out.

Comment 2 Petr Bokoc 2014-12-16 17:11:44 UTC
F21 guide has been released, and --biosdevname= is no more. http://docs.fedoraproject.org/en-US/Fedora/21/html/Installation_Guide/sect-kickstart-commands-network.html


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