| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
We remove the partitions at the end of clearpart function when we
traverse the clearpart list and "Destroy" each partition.
|
| |
|
| |
|
|
|
|
| |
We are scheduling the actions we need. This is just noise now.
|
| |
|
|
|
|
|
| |
There's no sense raising a traceback if the user just chose the same size
as the filesystem already is.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This seems pretty harmless to me, and raising an error causes problems when
dealing with bind mounts.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Resizing existing filesystems on PartitionDevice objects now works
properly. I have resized ext3 and ntfs on existing partitions and
autopart takes over after that.
LVM resizing is not done yet, but this patch takes care of the major
case: resizing existing Windows installations.
|
|
|
|
|
|
| |
Without the call to busyCursorPop(), we get the watch mouse pointer
for the rest of the install. waitWindow sets it up, which is called
when 'Finding storage devices...' is displayed.
|
| |
|
|
|
|
| |
Not sure how this worked yesterday, but order is important
|
|
|
|
| |
This reverts commit 8683176aef29562f6e7505a7727b79f94e1c8a8c.
|
|
|
|
|
|
|
| |
(1) When there's more than one system to choose from, display the name of the
device, its release string, and the label if it exists.
(2) Return the right type when the user makes a selection from the combo box.
|
|
|
|
|
| |
(1) We need to use the device's name instead of its path for clearPartDisks.
(2) We need to set doAutoPart since text mode is autopart only.
|
|
|
|
|
|
|
|
|
| |
In RHEL-5 we use _rnetdev for network based /, and various pieces
of the RHEL-5 initscripts key of on this to do special things. So I thought
it would be good to do the same in Fedora. Testing has revealed that
Fedora's mount command cannot handle this options on things go boom,
so use plain _netdev for / just like we do with other network based fs, and
as we've been doing in previous Fedora releases.
|
|
|
|
|
|
|
|
|
| |
booty was using its own code to find out wether to pass in
UUID=.... or /dev/.... as root= option, leading to inconsistencies
between fstab (/dev/mapper/Volgroup-lv_root) and grub.conf (UUID=...)
Harmless, but confusing. This patch fixes this by removing the no longer
needed getRootDevName method from booty and instead using device.fstabSpec
|
| |
|
| |
|
|
|
|
| |
Also correct some references to self.origrequest.
|
| |
|
|
|
|
|
|
| |
This could use expansion in the future, perhaps removing the disk
that caused the problem as a Skip option, or something like that.
For now, if we can't read your disks, stop.
|
|
|
|
|
|
| |
Be more defensive about what we get back from the _isys module. Do
not assume we get an error string. If it's empty, place None in the
tuple.
|
| |
|
|
|
|
|
| |
We don't need these commands in both locations, /sbin will be
sufficient.
|
|
|
|
|
| |
If NULL is given as the last parameter to doPwMount(), do not try
to dereference it.
|
|
|
|
|
|
|
|
| |
Hitting this periodically on my test systems. The disk may or may
not be capable of the ped_disk_commit_to_dev() call yet. The disk
is busy. I don't want to use a Timer thread since we're using
PyGTK and we'll get in to all sorts of problems if threads are
brought it. The poor man's try loop has been working for me today.
|
|
|
|
|
|
| |
Also, don't require that partitions be bootable in advance of being
identified as the boot device. We will set the boot device's boot
flag explicity elsewhere.
|
| |
|
| |
|
|
|
|
|
| |
The storage layer keeps track of uuids for filesystems, so we need
to update it if we change the uuid
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
|
|
|
|
| |
/dev/live is an absolute symlink right now, so strip off /dev if we
need to
|
|
|
|
|
|
| |
isys.umount() defaults to removing directories. Maybe we should change
that, but it has implications for a fair number of callers. So let's just
not remove the mountpoints for now
|