Bug 69066 - Disk Druid overlaps boxes in partition layout graph
Summary: Disk Druid overlaps boxes in partition layout graph
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 9
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-17 17:52 UTC by pete peterson
Modified: 2008-01-17 17:49 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:49:15 UTC
Embargoed:


Attachments (Terms of Use)

Description pete peterson 2002-07-17 17:52:30 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.7 [en] (X11; U; SunOS 5.8 sun4u)

Description of problem:
The line of boxes showing the partition layout overlaps, so some of the
boxes are unreadable.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. have disk partitioned as in "additional information"
2. select partitioning with disk druid
3.  observe confusing disk layout picture
	

Additional info:

Disc was 40 mb maxtor -- partition layout was (approx)
/dev/hda1  1..261	       fat16
/dev/hda2   262..268      Linux
/dev/hda3   269..1543    Extended
/dev/hda4   1544..2563   Linux
/dev/hda5    269..523      fat16
/dev/hda6    524..589      linux swap
/dev/hda7    590..1543     linux
(unpartitioned space 1544..4982)

This is a minor problem, but it's important not to confuse beginners trying
to use disk druid

Comment 1 Michael Fulbright 2002-07-18 17:14:03 UTC
Are you saying some of the partitions are graphed so small (because they are
small partitions) that the label is not visiable inside it?

Beginners are going to be confused by partitioning no matter what you do...

Comment 2 Michael Fulbright 2002-08-13 16:07:12 UTC
Closing due to inactivity - please reopen if you have additional information
regarding this issue report.

Comment 3 Red Hat Bugzilla 2006-02-21 18:49:15 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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