Bug 240546 - Kickstart command zerocmd documented incorrectly
Kickstart command zerocmd documented incorrectly
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
6
All Linux
low Severity low
: ---
: ---
Assigned To: Anaconda Maintenance Team
: Documentation, EasyFix
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-05-18 08:39 EDT by Lubomir Kundrak
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-05-18 10:27:45 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 Lubomir Kundrak 2007-05-18 08:39:10 EDT
Description of problem:

/usr/share/doc/anaconda-11.1.1.3/kickstart-docs.txt claims that:

   zerombr (optional)

       If zerombr is specified, and yes is its sole argument, any invalid
       partition tables found on disks are initialized. This will destroy
       all of the contents of disks with invalid partition tables. This
       command should be in the following format:

       zerombr yes                                                 

       No other format is effective.

Which is purely wrong. The current version of anaconda complains that
zerombr command no longer takes any options. Thus "zerombr yes" should
be replaced with "zerombr". Is there any difference between it and
"clearpart --initlabel"?
Comment 1 Chris Lumens 2007-05-18 10:27:45 EDT
This is fixed in the devel tree.

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