New subject: [Bug 1139176] kickstarts network command not know --biosdevname option

8 Sep 2014


      https://bugzilla.redhat.com/show_bug.cgi?id=1139176
Bug ID: 1139176
           Summary: kickstarts network command not know --biosdevname
                    option
           Product: Fedora Documentation
           Version: devel
         Component: install-guide
          Assignee: pbokoc@redhat.com
          Reporter: mkolman@redhat.com
        QA Contact: docs-qa@lists.fedoraproject.org
                CC: anaconda-maint-list@redhat.com,
                    extras-qa@fedoraproject.org, franta@hanzlici.cz,
                    g.kaviyarasu@hotmail.com, jonathan@jonmasters.org,
                    pbokoc@redhat.com, vanmeeuwen+fedora@kolabsys.com,
                    zach@oglesby.co
        Depends On: 1135692
+++ 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@redhat.com 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.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1135692
[Bug 1135692] kickstarts network command not know --biosdevname option
-- 
You are receiving this mail because:
You are the QA Contact for the bug.

[Bug 1139176] New: kickstarts network command not know --biosdevname option