| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| | |
|
|/ |
|
|
|
|
| |
Whole-disk formats are recognized but cannot be edited in any way.
|
| |
|
|
|
|
|
|
|
| |
For some reason, gtk cycles backwards through the radio buttons under our
old UI arrangement, which was a table with one column and three rows, and
then an HBox packed into one of the rows with two columns in it. Instead,
just use a 2x3 table.
|
| |
|
| |
|
|
|
|
| |
Addition to patch 4fff93ac8e3b3187af5f50d17a065fafc610a5df.
|
|
|
|
|
| |
Fix lookup of LUKS device for partitions to not traceback on failure
and allow reformat w/ encryption for all device types.
|
|
|
|
|
|
| |
Don't set exists or migrate flags in a widget callback -- they will be
set when the user clicks "OK". Likewise, don't try to preserve exists or
size attributes when user has chosen to reformat the device.
|
| |
|
| |
|
|
|
|
|
|
|
| |
The use of a unique id frees us from having to worry about parted renaming
partitions whenever we remove one. It will also provide a mechanism with
which we can more reliably track protected partitions, currently
problematic for the same reason.
|
| |
|
| |
|
|
|
|
| |
...but only they are reformatting the device.
|
| |
|
|
|
|
|
|
|
|
| |
When carrying over the format's attributes we do not consider the
possiblility that the partition is encrypted, in which case we want to
preserve the attributes of the LUKSDevice's - not the PartitionDevice's -
format. This was causing a traceback whenever a user tried to edit a
preexisting encrypted partition.
|
|
|
|
|
|
| |
Currently if you create a new partition from the UI and then later
decide to change the size using edit partition, the size does not
get changed. This patch fixes this.
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
There's no sense raising a traceback if the user just chose the same size
as the filesystem already is.
|
|
|
|
|
|
| |
Pass format to new partition (request) so that it doesn't have
to create DeviceFormat instance which tracebacks with:
http://fpaste.org/paste/6475
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
This is analogous to the earlier fix for lvs.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
- Always return a list from run().
- Handle the case of removing encryption from a device.
- Schedule format create actions to go with device create actions.
- Save mountpoint setting even when not formatting/creating.
- pass format instance to createFSTypeMenu
- create preexist options even for unknown formats
|
|
|
|
|
| |
We don't have this function anymore, but I don't know if we need
to be calling anything else.
|
|
|
|
|
| |
Misc syntax fixes for the new storage code. Generated these while
trying to do a 'Create custom layout' install.
|
| |
|
| |
|
|
|
|
|
|
| |
The old pyparted had CHS values as properties directly on the
PedDevice. The new pyparted API gives a 3-tuple for the CHS
values via the biosGeometry and hardwareGeometry properties.
|
|
|
|
|
| |
The property name for Device objects on a Disk or Geometry is
'device', not 'dev'.
|
|
|
|
|
| |
The parted.Device object now offers functions to translate
between cylinders and sectors.
|
| |
|
| |
|
|
|
|
| |
* po/sk.po: Typo fix.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Basic rules are the same for partitions, LVs, RAID devices:
- Existing LUKS headers can only be removed if the device is being formatted.
- You can create a new filesystem on the device and retain the preexisting
LUKS header.
- You can add a LUKS header to a non-encrypted preexisting device only if
creating a new filesystem on the device.
- We prompt for passphrase only for non-preexisting LUKS headers, meaning
those that existed when we read the disk layout initially. We do not support
adding or changing passphrases for preexisting encrypted devices.
|
|
|
|
|
|
|
| |
Shorten 'Red Hat Author(s)' to just 'Author(s)'. Perhaps eventually
we'll get an AUTHORS file and will just remove author names from the
individual files. Also fixed a type in scripts/dumphdrlist.py where
Author was listed twice.
|
| |
|
| |
|
|
|
|
| |
track of the request being resizable rather than just the filesystem
|
|
|
|
| |
This simplifies the edit partition dialog and adds resizing support
|
|
|
|
|
|
| |
The class LUKSDevice, in cryptodev.py, handles the details of creation and management of the encrypted devices. RequestSpec and Device classes contain an optional LUKSDevice instance describing the device's encryption setup.
There is no support for pre-existing encrypted devices and kickstart support is not present at this point.
|
| |
|