| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
Timestamp/tag format changed.
|
| |
| |
| |
| |
| | |
Also use short form of format type names. The long form is for
the user interface only.
|
| | |
|
| |
| |
| |
| |
| |
| | |
MD_DEVNAME is never set for existing md arrays. Some metadata versions
will have MD_NAME, but not all. All md arrays have MD_METADATA while
component devices do not, making it perfect for differentiating them.
|
| | |
|
| | |
|
|/
|
|
|
| |
Some methods have been added to other intfs but not to RescueInterface;
they must be added there as well.
|
|
|
|
|
| |
Most anything that anaconda calls should be in a Requires: to make sure it
gets pulled into the tree.
|
| |
|
|
|
|
|
|
|
|
|
| |
We have to use BASEARCH, because during the build the ARCH is set to ppc
and the BUILDARCH is ppc64 so we couldn't find the file.
RPMUtils map the BASEARCH correctly to ppc. So we will find the file.
It also works correctly for i686 -> i386 and x86_64 -> x86_64.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
(1) The filtered model is no longer the top-level so anywhere we want to call
refilter, we need to dig down and get the child, which happens to be the
filtered model.
(2) Similarly, we can only call get_text on the child of a ComboBoxEntry because
that's the entry part.
(3) Populate all search drop-downs when the containing hbox is realized, not
some complicated setup where each individual item is selected.
|
| |
|
| |
|
|
|
|
|
|
| |
Since we're stuffing more things into this column than just WWIDS (paths on
iscsi and s390 stuff soon, at least) the column header needs to be changed
to match.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Given a partition layout like this:
partition startsector endsector
/boot 2048 1026047
PV 1026048 xxxxxxxxxx
Then when we call getFreeRegions() parted gives us a free region with a
geometry starting at sector 63 and ending at sector 2047, which we then try to
align to our 2048 grain, which fails for the starting sector. When we fail to
align, this means that the free region is too small to create an aligned
partition in there, and we should just skip it.
|
|
|
|
|
|
|
| |
Some of the values which are returned by udev are strings,
which contain more values for the same key.
The string format is "val1 key=val2 key=val3 ...".
This fix makes sure we split this string into a list of values.
|
|
|
|
|
| |
This method is what calls kickstart.selectPackages, so not running it means the
%packages section of the kickstart file will never be applied.
|
|
|
|
| |
This is a leftover from having our own udev db reading code.
|
|
|
|
|
| |
Some udev properties which should be a string were
wrongly converted to a list of words.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our partitioning code was assuming that having a partition from
sector 0 - 512 means the partition stops at sector 512, iow that
it goes from sector 0 till 511, but that is not how parted geometries
work, the range includes the end sector. So 0 - 512 will get you
a 513 sectors partition.
This patch adds an endAligment property to disklabel which can be used
to properly align end sectors (which must be aligned to the disklabel's
alignment with the offset decreased by 1), patches partitioning.py to
use this to align end sectors and fixes up end sector calculations in
partitioning.py to be start + length - 1.
On DASD's (s390), the wrong end sector was causing a traceback (#560586),
as DASD's disklabels need partitions to be cylinder aligned, and the wrong
end sector violated this.
|
|
|
|
|
| |
When doing custom partitioning, and adding an mdraid array, and a pre-existing
array has a minor > 32, we will back trace, this patch fixes this.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were relying on the ctypes behavior to default to int as return type for
all functions. But most of the functions in question are not returning int's
but pointers, which are 64 bit on s390x (and ppc64 and x86_64).
Due to the fact that we were getting virtual addresses below 4G + the C
calling conventions on x86_64 making it not matter when passing in an 32 bit
int instead of a 64 bit one, as long as the 32 bit one represent the correct
number, we got away with this on x86_64 (unfortunately really).
This patch very likely also fixes #560035.
Note I also threw in a traceback fix in the same codepath, baseudev assumes
that devices always have a DEVLINKS property, which is not true for for
example network devices.
|
| |
|
| |
|
|
|
|
|
|
| |
Doing this allows use of map and filter, which seems more natural than the
iterator dance. This patch also fixes a problem drilling down to the base
store through all the various models.
|
|
|
|
|
| |
For some reason, doing it the other way around allows you to click on column
headers but there is no sorting that happens.
|
|
|
|
|
|
|
| |
For the common home/laptop use case, the user likely only has one disk. If
that's the case and they pick the Basic filtering UI (indicating they don't
want to add fcoe/iscsi/whatever disks), then there's no point in showing
these UI components.
|
|
|
|
|
| |
This is sometimes useful, like when we won't know until the screen is being
populated whether or not we actually want to display it.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The recent base_udev.py changes to switch over to
global_udev.enumerate_devices(), move the removing of the /sys prefix to
udev_get_device(). But in various places in the devicetree we call
udev_get_device() (through udev_get_block_device) to get information from
parents which are not yet in the tree (ie when we scan a partition
before its disk).
All these calls are broken now, as all those pass in a path without /sys
at the front and the new udev_get_device() wants it with /sys in front.
This patch makes udev_enumerate_devices() return paths without the /sys
prefix, and reverses the changes to udev_get_device() to expect a full path,
so that we use sysfs paths without /sys in front consistently everywhere.
|
|
|
|
|
| |
Do not list the directories in sys, but use the libudev's
enumerate_devices function to get the sysfs paths.
|
|
|
|
| |
Same problem that was present in linuxrc.s390.
|
|
|
|
|
|
| |
This brings iBFT (iscsi) / EDD (FCoE) / /tmp/zfcp.cfg (zfcp) auto discovered
drives only. So that they show up in the filter UI and can be selected for
the installation (tested with iBFT).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) When populating the store make left / right visible depend on if the
disk is listed in clearPartDisks or not
2) Don't extend clearPartDisks when moving to the next screen, but set it
so that drives which were moved to the left get removed from it.
3) The bootdisk is part of cleardisks, don't put it in
clearPartDisks twice
4) Update the bootloader drivelist, putting the select drive on the front,
don't override it. Even if we just want to mount a disk it should still
count in our bios drive order, so that grub gets a correct map
(Note even before this fix this was already effectively being done
by bootloader.py which overrides the drivelist as set by clearpart_gui)
Note this patch only fixes back/forth issues with the UI code, there is
still a problem in the underlying logic code, where after having
autopartitioned once, subsequent attemps will fail with no free space found.
I've filed this as bug 559233.
|
| |
|
|
|
|
| |
request.disks should be request.req_disks
|
|
|
|
|
|
|
|
| |
Note this patch also removes the following line (in the middle of the EDD
block):
handleSegv = _isys.handleSegv
This is intentional, as that line was present in isys.py twice.
|
|
|
|
|
|
|
|
| |
Replace all usage of the isys C EDD code with the new storage
python EDD code. Note that this moves the sorting of partition.req_disks
from devices.py to paritioning.py, because sorting now needs access
to the storage object, this also has the added advantange that now we
always allocatePartitions in sorted drive order, even in interactive mode.
|
|
|
|
|
|
|
|
|
|
| |
There are various issues with the EDD C-code, mostly that it is way
too complicated for what it does. This patch re-implements it in
python, and adds a compareDrives substitute to the storage class.
Note that the compareDrives substitute is a copy and paste job of the
isys code (using the new storage edd_dict). The isys code will be removed
in a separate patch.
|
|
|
|
|
| |
This file is required to make sure NFS works when it attempts to fall back
to protocol v3. The mount command looks for it when mounting as v4 fails.
|