Bug 9916 - network --bootproto static does not work
Summary: network --bootproto static does not work
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
(Show other bugs)
Version: 6.2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-03-02 10:18 UTC by Pawel Salek
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-03-02 18:12:50 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Pawel Salek 2000-03-02 10:18:13 UTC
I have tried Kickstart with network --bootproto static option but it still
sends the BOOTP requests which obviously fail.
The Kickstart-HOWTO file recommends using network --static but it doesn't
work neither.

I have also a suggestion: it would be nice if Kickstart would ask for the
IP number if the static configuration was requested but no IP number was

Comment 1 Jay Turner 2000-03-02 11:51:59 UTC
Were was the kickstart file located?  On the boot diskette or on the network?
What command line did you pass?

Comment 2 Pawel Salek 2000-03-02 14:55:59 UTC
I did some more tests and I admit network --bootproto static works after all and
I withdraw this part (stupid me, have forgotten to pass the ks=floppy
parameter). My comments about the documentation inconsistency remain valid.

Anyway, the installation fails at xconfig:
line 271, in write file xf86config.py
line 387, in mouseSection
AttributeError: 'None' object has no attribute info.

Relevant parts of my kickstart file are following:
mouse generic3ps/2
xconfig --server SVGA --monitor "IBM 6549 G94 & G96"

Am I doing a silly mistake?

Comment 3 Jay Turner 2000-03-02 18:12:59 UTC
Both of these issues are resolved in later builds of the installer. Will be
fixed in the next release.

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