Bug 9916

Summary:	network --bootproto static does not work
Product:	[Retired] Red Hat Linux	Reporter:	Pawel Salek <pawsa>
Component:	installer	Assignee:	Michael Fulbright <msf>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-03-02 18:12:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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
specified.

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.