Bug 240546

Summary: Kickstart command zerocmd documented incorrectly
Product: [Fedora] Fedora Reporter: Lubomir Kundrak <lkundrak>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 6Keywords: Documentation, EasyFix
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-05-18 14:27:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Lubomir Kundrak 2007-05-18 12:39:10 UTC
Description of problem:

/usr/share/doc/anaconda- 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 14:27:45 UTC
This is fixed in the devel tree.