Bug 3641 - kickstart fails if partitions are not specified
kickstart fails if partitions are not specified
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
6.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Matt Wilson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-06-22 14:31 EDT by Joshua Buysse
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-09-19 19:06:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joshua Buysse 1999-06-22 14:31:51 EDT
I'm attempting to use kickstart to partially automate the
install process -- having the system ask about network and X
configuration, since the machines I need to install are not
especially similar.  I'm mainly using kickstart to provide a
way to automate package specification and a post-install
customization.

The problem that I'm running into is that the installer does
not ask about partitioning if none is specified in the
kickstart file.  I've got a wide variety of machines.

Another minor annoyance (I would just customize the
kickstart file for each machine with a script otherwise) is
that the 'part' keyword does not allow you to specify a disk
to place the partition on.  On the machines that have
multiple disks, I want control over the swap partitions,
etc.
Comment 1 Joshua Buysse 1999-06-23 16:28:59 EDT
A good solution in my mind for a future version of the installer would
be a '--ask' option for any of the kickstart keywords, so you could
specifically state 'network --ask' or 'part --ask'.
Comment 2 Jay Turner 2000-02-10 16:03:59 EST
Added to a list of feature requests for future releases.
Comment 3 Michael Fulbright 2000-09-19 19:05:57 EDT
Should be fixed in the Pinstripe beta release.

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