Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 3772 - Several kickstart problems
Several kickstart problems
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
Depends On:
  Show dependency treegraph
Reported: 1999-06-28 03:17 EDT by jalar
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-10 16:11:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description jalar 1999-06-28 03:17:15 EDT
1) My partition table was damaged during my first try.
   Apparently 'zerombr no' is to blame for this. The
   install goes through without it (after I had manually
   fixed the partition table, of course)

2) 'device ethernet ne --opts "io=0x220, irq=9"' results
   in autoprobing (?) for a ne card at 0x300 and
failing. 	   Then manual configuration kicks in (which is
   because the ks install then continues)

3) 'mouse whatever' doesnt work until I give
   '--device ttyS0' (does cua0 even exist?). This also
   kicks you out of the ks install.

4) 'xconfig' leaves the machine at blank screen. Pressing
   alt-F1 returns you to the install

5) 'rootpw --iscrypted xxxx' reencrypts the password. I
   thought this was fixed?

6) Perhaps add to the H.3.22 section of the install manual
   (%post section in a ks install) that

	'If you intend to do anything useful, note that
	the root-filesystem-to-be (/ of the install) is
	located at /mnt, for example use

	    rpm -i --root=/mnt xxxxxxxx'
Comment 1 jalar 1999-06-28 03:20:59 EDT
Oh, and I _am_ using the 29-May-1999 images.
Comment 2 Jay Turner 1999-06-28 08:15:59 EDT
This issue has been forwarded to a developer for further action.
Comment 3 bdraco 1999-07-03 19:57:59 EDT
setting the mouse to none in the ks.cfg also produces the same
Comment 4 patrick 1999-07-06 14:44:59 EDT
I've run into this and ended up having to have a mouse connected to
the machine during install (a pain in the ass because I do multiple
simultaneous installs).  I've been looking through the RH5.2
Installation manual, and it says to use something like:

mouse --kickstart genericps/2

I have yet to try it with the --kickstart option though.
Comment 5 Bill Nottingham 1999-07-15 13:51:59 EDT
rootpw --iscrypted requires replacing the install2 binary
on the install image. You can either force a supplementary
disc, or copy the install2 binary on the errata supp.img
(or in the Raw Hide install image, IIRC) to the install image.
Comment 6 panu.matilainen 1999-08-31 10:00:59 EDT
The --iscrypted thingy can also be worked around in the post-section:
sed 's&root:[^:]*:&root:'$ROOTPW':&' < /etc/shadow > /tmp/shadow
mv /tmp/shadow /etc/shadow
chmod 0400 /etc/shadow
Comment 7 Jay Turner 2000-02-10 16:10:59 EST
These issues are resolved in the latest installer available in beta.

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