Bug 15116 - anaconda wants to write unchanged partition tables to disk unnecessarily
Summary: anaconda wants to write unchanged partition tables to disk unnecessarily
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
(Show other bugs)
Version: 7.0
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-02 13:24 UTC by Telsa Gwynne
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-17 16:17:51 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Telsa Gwynne 2000-08-02 13:24:15 UTC 
Cyrix MediaGX with 32Mb of RAM and a very large
HD which I have partitioned to triple-boot between different
flavours of Linux.. 

Decided to install pinstripe over the top of the last beta
to replace it. Used disk druid, selected the partitions to
use for /boot and / - it already spotted the swap. I changed
nothing from its previous set up. hda3 was still /boot and
hda9 was still /. 

Next screen: "you have not much memory in your machine.
I want to turn on swap. "[Think bubble: 32Mbs? Fair enough...]
"To do that, I need to write the partition table to disk. Is that okay?"
[Think bubble: huh?]

Why? Why does it need to rewrite the partition table? It
hasn't changed...

I thought I had put this into bugzilla before but I can't
find it. Sorry.
Comment 1 Michael Fulbright 2000-08-17 16:17:47 UTC 
It should not cause problems since the partition table is the same.
Note You need to log in before you can comment on or make changes to this bug.