Bug 13682 - kickstart doesn't initialize the partition table
Summary: kickstart doesn't initialize the partition table
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-07-10 23:59 UTC by Joshua LeVasseur
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-07-17 19:52:16 UTC
Embargoed:


Attachments (Terms of Use)

Description Joshua LeVasseur 2000-07-10 23:59:33 UTC
The kickstart script refuses to initialize the partition table of a new
drive.  It reverts to interactive mode to ask the user whether the
partition table should be initialized.  The kickstart script ignores the
'zerombr yes' command.

Solution:
In anaconda/text.py, the NewtFstab object initialization forces the zeroMbr
parameter to 0 (around source line 207).  It should pass todo.zeroMbr as
the parameter.  Change the line to:
            todo.fstab = NewtFstab(todo.setupFilesystems,
                                       todo.serial, todo.zeroMbr, 0,
                                       todo.intf.waitWindow,
                                       todo.intf.messageWindow)

Comment 1 Brock Organ 2000-07-12 16:04:09 UTC
behavior verified ... thanks for the report!

Comment 2 Michael Fulbright 2000-07-17 19:52:14 UTC
Should be fixed in internal development tree.


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