Bug 12769

Summary: mkkickstart b0rken with PS/2 mice.
Product: [Retired] Red Hat Linux Reporter: Daniel Stone <tamriel86>
Component: mkkickstartAssignee: Matt Wilson <msw>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1   
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-06-20 23:56:27 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 Daniel Stone 2000-06-20 23:56:26 UTC 
This morning, I tried to create a KickStart disk with "mkkickstart" and it 
was all fine and dandy. Until I actually wanted to use the KickStart disk 
to install a new machine. I have a PS/2 mouse attached to the machine I 
ran mkkickstart off (and, indeed all the systems around here), and 
mkkickstart wrote "mouse ps/2" to the config file. All is good and well - 
or so it seems. RH objects to this and throws up an error about it not 
being a valid type. So I went to the file referenced and looked up the 
types for mouseToMouse - the struct/function it was b0rking on, and lo and 
behold, "ps/2" wasn't a valid mouse type there - it's either "genericps/2" 
(generic 2-button PS/2 mouse) or "generic3ps/2" (generic 3-button PS/2 
mouse). Not enough for me to set my hair on fire and run screaming out of 
the room, but reasonably annoying.

Regards,
Daniel Stone
(daniel.org/tamriel86)
Comment 1 Nalin Dahyabhai 2000-07-21 18:21:53 UTC 
This appears to be fixed in Raw Hide (ftp://ftp.redhat.com/rawhide/i386/).  With
MOUSETYPE set to "ps/2", mkkickstart prints "mouse genericps/2".  Please
reopen this bug if you find that this is not the case.