| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The main problem here is that get_partition_by_name() has been
removed from partedUtils.py. The functionality is now provided
by the getPartitionByPath() method on a parted.Disk object. The
old function in partedUtils would iterate over the PedDisk
collection and each partition manually, whereas now we have to
call getPartitionByPath() for each parted.Disk we have.
request.drive has been used inconsistently throughout the existing
storage code and only started to show up when I was moving things
from anaconda to pyparted. What this patch does is ensure that
request.drive on RequestSpec objects is always a list or None.
There are a few other changes in the storage code to handle the
request.drive variable always being a list, but I think it should
be pretty straightforward.
|
| | |
|
| |
|
|
| |
bootDev.device.getName() instead of bootDev.getName()
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Removed the parted.getPartitionByName() function. There is now
a method on parted.Disk called getPartitionByPath() which provides
the same functionality, but only works on a single Disk.
|
| |
|
|
|
|
|
| |
Rather than calling disk.nextPartition() over and over, we can
get a hash table of all partitions on a disk via disk.partitions.
Iterate over the values() of this hash (the keys correspond to
the partition number).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Iterate over partitions with a for loop over
disk.partitions.values() rather than calling next_partition()
2) Call getFlag() rather than get_flag()
3) Call setFlag() to enable a flag, call unsetFlag() to disable
a flag.
4) Reference the active property rather than calling the
is_active() method.
And other fixes.
|
| | |
|
| |
|
|
| |
Now provided by pyparted as parted.getPartitionByName()
|
| |
|
|
| |
Now provided by parted.Partition.getDeviceNodeName()
|
| |
|
|
| |
This function is just a pass-through for isys.readFSType().
|
| |
|
|
|
|
| |
This patch also makes selecting /boot as mountpoint
to automatically select ext3 (in place of ext4)
in filesystem combo.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that btrfs is in mainline, let's let anaconda play with
it too ;) We still need btrfs.ko in the kernel, and btrfs
support in e2fsprogs. I've got the latter patch submitted
upstream, and it's in rawhide now.
Note that the below is 100% totally untested and may even have
typos, my track record with python is not too good, sorry. :)
So review would be appreciated....
Updated to address Radek's review, as well as adding the requisite
witty (commandline-space-eating) boot option...
(And stopped trying to use parted fs identification -- katzj)
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
|
| |
|
|
| |
ext4 should be safe enough to allow people to select it without a magic flag
|
| |
|
|
|
| |
Based on a patch by Tom Callaway <tcallawa@redhat.com>, this adds supporting
for using ntfs-3g (and thus fuse) to mount filesystems.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
As previously discussed we do want to allow installing the bootloader on the
MBR in the raid 1 case (which until some time ago we did not allow) (#217176),
but we do not want to change our current default of installing to the partition
(which gives us the mirror redundancy, due to special handling in booty).
This patch effectively reverts commit 48d582347492493c87b2b368394fd8e7342688bc,
which removed the raid1 case special handling, and then adds mbr support to the
raid special case in fsset.py, and add some special case handling to
bootloader.py to not default to the mbr in this case.
|
| |
|
|
|
|
|
|
| |
The main reason for this is that having swap files still mounted means that
/mnt/sysimage cannot be unmounted in migrateFilesystems, which leads to a
traceback on upgrades. Once we've unmounted all the swap devices, we then
need to go back and turnOnSwap again afterwards. mountFilesystems doesn't do
that for us.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Try to name volume groups as vg_HOSTNAME and logical volumes as
lv_MOUNTPOINT, if we can. Swap partitions will be lv_swapNN where
NN is a unique number in the instance where more than one swap
partition in use. The / partition will get the name lv_root.
Fall back on the old naming system (VolGroupNN for volume groups
and LogVolNN for logical volumes) for people doing custom setup
or where the hostname is localhost.
For swap partition naming, tack on an NN designation when there
are more than 1 swap partitions requested. If only one is
requested, it will be "lv_swap".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch removes a special case when /boot (or / without a separate /boot)
is on mdraid. For some reason we only allow installing grub to the mdX device
then instead of allowing both the mbr of the 1st disk and the device holding
/boot.
I've searched through the anaconda history and this special handling of
mdraid /boot has been there since before Feb. 2002, it was inherited from
before booty was introduced and it does not seem to make sense. Either we
cannot have /boot on mdraid at all (in all cases except for raid1) or we can
have /boot on mdraid (in case of raid1) and then it does not matter if the
bootstrap of grub starts on the mbr or on the first sector of a partition.
This fixes 217176
|
| |
|
|
|
|
|
| |
Since LVs appear as device paths in fstab (most other stuff as
UUID=) we needed to add some smarts to readFstab so it can
locate the backing device and create a useful Device instance
with which we can mount the rootfs.
|
| | |
|
| | |
|
| |
|
|
| |
Fix various syntax errors caught by PyChecker
|
| | |
|
| | |
|
| |
|
|
|
| |
Add modules for sd/mmc subsystem and support the block device name where we
need to do munging given the 'p' separator
|
| | |
|
| |
|
|
|
| |
This is as safe as using a UUID since the device path is based on
the LUKS UUID, not a device node.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
since they might be started before there are any LVs. (this fixes dmraid.)
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
We had been hard-coding various args to mke2fs to try to get
what we wanted, but newer mke2fs supports "-t $TYPE" which
is much simpler, and harder to get wrong.
I must admit to not actually testing this patch, though.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
* po/sk.po: Typo fix.
|
| | |
|
