| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
We may not have formatcb in all cases, don't assume it exists.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Separate the logic from the actual constructing of the gtk stuff is very
helpful when trying to debug, develop these files. This commit doesn't
actually change any behavior in the file.
|
|
|
|
|
| |
Mainly lines running for more that 80 characters. The use of tabs
instead of spaces and spaces after the line has ended.
|
|
|
|
|
|
|
|
|
| |
When re-editing a new device, the fstype combo was not getting set to
the current format type because of confusion caused by the use of
format name in some places and format type in others.
The only thing we use the name attribute for is displaying in the
fstype combo. For everything else we use the type attribute.
|
|
|
|
|
| |
This at least gets to the partitioning screen; didn't finish an install, but it's
closer
|
|
|
|
| |
Missed this one in my initial cciss prep patch.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This hopefully fixes cciss (will test once an anaconda with this in
has hit rawhide, so I can use rhts to test). This is the second version of
this patch, this time it also does the / -> ! translation for sysfs names.
|
| |
|
| |
|
|
|
|
|
|
| |
When performing a custom partitioning layout, make the Format check mark
column work correctly depending on what you enter in the Edit Partition
dialog box. Also register and cancel storage actions as necessary.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
The format checkbox enables the combo box listing filesystems.
Likewise, the migrate checkbox enables the combo box listing filesystems
you can migrate to. The two choices are mutually exclusive. We only
want one combo box active at a time. Without this patch, box combo
boxes would become active if either checkbox was checked.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The 'Shrink current system' dialog had some bounds checking problems.
Users could enter a size that was too small or too large.
Renamed the function and related controls to use 'shrink' instead of
'resize' in the name to better reflect what the code does.
Use the format's size to set the bounds rather than the partition's.
Since we are shrinking here, we only want to let users select a size
smaller than the current format size.
A size smaller than the minimum will automatically be set to the correct
minimum. Likewise, a size larger than the maximum will automatically be
set to the correct maximum.
|
| |
|
|
|
|
|
|
| |
Check the resizable property as well as targetSize not being zero
(indicates no new targetSize has been set) and finally compare
targetSize to currentSize.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
There's no sense raising a traceback if the user just chose the same size
as the filesystem already is.
|
|
|
|
| |
Also correct some references to self.origrequest.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* storage/__init__.py (createSuggestedVGName): Take into account the new
lvm black list.
* storage/devicelibs/lvm.py (blacklistVG): New function, add a VG to a
the black list.
* storage/devicelibs/lvm.py (vgreduce): introduces a new argument to the
function. rm means use the lvm --removemissing option.
* storage/devices.py (LVMVolumeGroupDevice.complete): New function to
evaluate if VG is consistent.
* storage/devices.py (LVMLogicalVolumeDevice.complete): Likewise for
LVs.
* storage/devicetree.py (_handleInconsistencies): New function intended to
catch all unwanted behavior from the system before continuing.
* storage/devicetree.py (questionReinitILVM): New function intended
to ask the user what to do in case we find inconsistent LVM metadata.
|
|
|
|
|
|
| |
Pass format to new partition (request) so that it doesn't have
to create DeviceFormat instance which tracebacks with:
http://fpaste.org/paste/6475
|
|
|
|
|
|
|
|
|
|
| |
I opted to maintain the lv information in a simple dict which we
convert to a temporary vg/lv instance set when we need to. There
is no trampling on objects, and the code is just simpler. The big
difference is that we have to go through and figure out what all
was done at the very end, right before returning to the partition
gui. So far, it is considerably more stable than the previous
implementation was.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
If the user elects not to provide a passphrase or key, do not create
a LUKSDevice. We will just keep the backing device with its luks
format. This saves us the trouble of checking whether we have the
ability to set up each LUKSDevice since we only have LUKSDevice
instances for those we can set up.
|
|
|
|
|
|
|
| |
Previously we just passed in the device on which we would be
creating the filesystem, but that doesn't make it easy to know
if we initially plan to format the device or if the device is
encrypted.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Re-editing new partitions was generating a new request instead of
modifying the original request.
We were also trying to pass in a format to the ActionDestroyFormat
constructor, which is wrong -- they all take a device argument.
Lastly, the conditional for showing the "new" filesystem options
was wrong, which was causing both it and the "preexist" fs options
to get added to the dialog on new request re-edits.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
In the 'Shrink current system' dialog box, create an action to
resize the format and separate one to resize the device. These
are registered in the Storage object when the function returns.
Catch exceptions from the actions and display error messages
for the user if necessary.
|
| |
|
|
|
|
| |
This is analogous to the earlier fix for lvs.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The bug manifests itself in edit raid ui dialog of existing raid
array.
* storage/devices.py: For existing partitions use parents to get
number of total devices in array, for new partitions use value
from device instance which is initialized when the instance is
created
* iw.raid_dialog_gui.py: Initialize number of total devices when
creating raid array in UI.
|
|
|
|
| |
Also (probably harmless) typo corrected.
|