Bug 7980 - kickstart: clearpart --all/linux
Summary: kickstart: clearpart --all/linux
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.1
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Jay Turner
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-12-24 03:38 UTC by Vilius Puidokas
Modified: 2015-01-07 23:40 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2000-02-18 19:41:15 UTC


Attachments (Terms of Use)

Description Vilius Puidokas 1999-12-24 03:38:15 UTC
just got a chance to learn in a hard way the fact that:

'clearpart --all' affects not only all partitions, but also all _drives_.

There's nothing mentioned about multidisk stuff in kickstart. Also one
can't specify on which drive should be exact partition built, so one can
make a very *bad* assumption that "kickstart doesn't touch any other
drives."

let's put at least into documentation, that ks DOES touch other disk drives
(hdb, sdb, sdc...), even if you can't do partitioning on them.

suggestion - what about a possibility to give some kindof mix of these
three tables:
  fstab (where to mount),
  fdisk (what to mount, maybe even let playing with cylinders?)
  and our ks table (--size, --grow, --maxsize..)

also: looks like wiping out partition table is not done very clean (touches
fs data?), at least i failed to restore my 6 ext2 fs :'(
[well, had not much time for that]

Comment 1 Erik Troan 2000-02-18 19:41:59 UTC
this is documented in our manual

Comment 2 Vilius Puidokas 2000-02-18 21:03:59 UTC
ok, i'll be short this time. But just to keep docs (and RH) accurate:
http://www.redhat.com/support/manuals/RHL-6.1-Manual/ref-guide/s1-kickstart-file.html
(also hardcopy of manual on my desk) contains:

-To clear all partitions from a disk, this line would do the trick:
- clearpart --all

should sound like:
+To clear all partitions from all disks, this line would do the trick:
+ clearpart --all

p.s. if it shouldn't touch other disks then it's a bug.


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