Re: [PATCH] "Invalid Entry for Partition Size" when "Fill all available space" selected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Sorry if my mail client made stuff unreadable,  I'm currently fighting with it.
----- "Mark Hamzy" <hamzy@xxxxxxxxxx> wrote:

> The following is from the IBM bugzilla that I am looking at:
> 
> I am testing RHEL5.1 GA. When creating the file system, I use "Fill

Does the same behavior happen in 5.2  is there a bug for 5.3 for this issue?

> all
> available space" to use up all the free space. The problem is that
> when I clear
> out the value for "Size (MB)" and then click ok, anaconda asks me to
> provide a
> value. But this value doesn't make any sense to this option.
> 
> ┌────────┌────────────────────┤ Add Partition
> ├────────────────────┐─────────┐
> │ │ │ │
> │ │ Mount Point:/___________________ │ oint │
> │ /dev/sd│ │ ↑ │
> │ sda1 │ File System type: Allowable Drives: │ ? │
> │ Free │ ext2 ↑ [*] sda ? │ ? │
> │ /dev/sd│ ext3 ? [ ] sdb ↓ │ ? │
> │ sdb1 │ │ ? │
> │ sdb2 │ Size (MB): _______ ( ) Fixed Size: │ ? │
> │ Free │ ( ) Fill maximum size of (MB): 1____ │ ? │
> │ │ (*) Fill all available space: │ ? │
> │ │ │ ? │
> │ │ [ ] Force to be a primary partition │ ↓ │
> │ │ │ │
> │ ┌─│ ┌────┐ ┌────────┐ │ │
> │ │ │ │ OK │ │ Cancel │ │ │
> │ └─│ └────┘ └────────┘ │ │
> │ │ │ │
> │ │ │ │
> └────────└─────────────────────────────────────────────────────────┘
> ────────┘
> 
> 
> ┌────────┌────────────────────┤ Add Partition
> ├────────────────────┐─────────┐
> │ │ │ │
> │ │ Mount Point:/___________________ │ oint │
> │ /dev/sd│ │ ↑ │
> │ sda1 │ File System type: Allowable Drives: │ ? │
> │ Free │ ext2 ┌┤ Invalid Entry for Partition Size ├─┐da ? │ ? │
> │ /dev/sd│ ext3 │ │ b ↓ │ ? │
> │ sdb1 │ │ Must specify a value │ │ ? │
> │ sdb2 │ Size (MB│ │ : │ ? │
> │ Free │ │ ┌────┐ │ : 1____ │ ? │
> │ │ │ │ OK │ │ : │ ? │
> │ │ │ └────┘ │ │ ? │
> │ │ │ │ │ ↓ │
> │ │ │ │ │ │
> │ ┌─│ └─────────────────────────────────────┘ │ │
> │ │ │ │ │
> │ └─│ └────┘ └────────┘ │ │
> │ │ │ │
> │ │ │ │
> └────────└─────────────────────────────────────────────────────────┘
> ────────┘
> 
> I have noticied that this is not a problem in the graphical

be aware that the text mode as we know it is being replaced.  For 5.3 it is recommended to use vnc.

> installation because that entry box keeps getting reset to 1. Rather
> than attempt that same behavior, I just set that value to 1 if there
> was an error in the number when "Fill maximum size" and "Fill all
> available" are selected.
> 
> (See attached file: 41618.Fedora10.patch)
> 
> Mark
> 
> Common Information Model/Web-Based Enterprise Management at
> http://www.openpegasus.org/
> Take a look at the Linux Omni Printer Driver Framework at
> http://omniprint.sourceforge.net/ 
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list@xxxxxxxxxx
> https://www.redhat.com/mailman/listinfo/anaconda-devel-list

Attachment: 41618.Fedora10.patch
Description: Binary data

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux