| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Remove unused code from isys.
|
|
|
|
| |
These functions are no longer called from anywhere inside anaconda.
|
|
|
|
|
|
| |
Remove the dasd.c file from the isys source tree. The only function
that was still used was getDasdPorts() and it is only called by Python
code, so we can move that functionality in to Python.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove unnecessary semi colons in various places
- textw/upgrade_text.py: add a few missing imports
- Fix various missplaced doc strings
- Fix several double imports
- Fix AnacondaKSScript.run: Module 'os' has no 'exists' member
- users.py: Remove double definition of Users.setRootPassword
- yuminstall.py: correct typo reop -> repo
- yuminstall.py: _run: anaconda -> self.anaconda
|
| |
|
|
|
|
|
|
| |
A crash occurs after the IPv6 GUI has been enabled when we chose to configure
the network device manually. When the crash is fixed the screen still does not
appear. This patch fixes both the problems.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In stage 2, the nfs options given in repo= boot parameter were malparsed, in UI
they were ignored.
Note that now the options can get to stage 2 only via method=/repo= boot
parameter. Ks nfs option --opts works only when its url specifies stage2 (i.e.
ends with images/install.img). In cases when method (--repo parameter for
anaconda python script) is inferred from stage2, nfs options of stage2
"nfs:..." url aren't passed to stage 2.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a read from a block device (like USB key) or a cdrom (USB cdrom) fails, sleep
a bit to give the device some time to initialize. Return status of the mount
command is checked so waiting occurs only if there is a reasonable chance that
the device might eventually come online. This required extending our existing
mounting methods to report the correct mount error code.
I tested that
* the installer still runs
* reading the kickstart from a usb works
* starting the installer with no USB key inserted but a command line argument pointing to a USB drive will trigger the waiting cycle and that when the key is inserted while waiting the kickstart is eventually found on the key.
|
|
|
|
|
| |
We have glib for other things, so we can use it for option parsing and
dump another library dependency.
|
|
|
|
|
|
| |
Somehow a debug printf of mine from developing:
"Fix EDD BIOS disk order detection in general and make it work with dmraid"
patch ended up in getting committed, this patch removes it.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Remove the ANACONDAVERSION environment variable and embed the version
number at build time. The isys.getAnacondaVersion() function returns
the version number to Python code. If need be, it can be extended to
libisys.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most sysfs path handling code expects / uses sysfs path's without the
/sys prefix (as udev does internally). There were 4 functions which were
exceptions to this:
udev_enumerate_devices
udev_enumerate_block_devices
udev_get_device
udev_get_block_device
These expected resp. returned sysfs path's with /sys prefix. This
inconsistency causes the backtrace in bug 516168. Rather then applying a
simple fix for this, this patch makes the sysfs path usage consistent
everywhere, to avoid issues like this in the future.
This patch adjust the above 4 functions and all callers.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We need to use dbus and udev now, instead of the HAL interface. In
the future, we need to adapt code from storage/udev.py to be less tied
to block devices, since network devices use this same interface now.
|
|
|
|
| |
Adjust memory requirements.
|
| |
|
|
|
|
|
|
|
|
| |
libisys and loader lacked handling for the LAYER2 and PORTNO settings
present on s390x systems.
Also include the fix for #468755 to write layer2=1 rather than layer=2
to the ifcfg-DEVICE file.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Only read in 63 bytes, to make sure we preserve any trailing NULs for
end of string.
|
| |
|
|
|
|
|
|
|
| |
This appears to be the source of the problem, and fixes the issue
in brief testing. It is completely baffling to me why this would only
manifest now; it's not like this code has changed since it was
added.
|
|
|
|
|
|
|
|
|
|
| |
Remove minihal.py and use NetworkManager to get a list of device names
and their hardware addresses. Still have to talk to hal via D-Bus to
build a description string, but the hal path is given to us by
NetworkManager, so we are sure we are only building a list of interfaces
that NetworkManager knows about and can communicate with.
Also rewrite command-stubs/list-harddrives to not use minihal.
|
|
|
|
|
|
|
| |
This patch makes resetFileContext return the context (a string)
on success, and None on failure. This fixes the "set SELinux
context for newly mounted ..." log messages to actually show
the context set.
|
|
|
|
|
|
| |
In kickstartNetworkUp(), call is_nm_connected() to see if we are in
NM_STATE_CONNECTED. If we are in any other state, prompt for network
configuration and start NetworkManager.
|
|
|
|
|
| |
Call the umount(8) command when unmounting filesystems through isys so
that /etc/mtab is updated.
|
|
|
|
|
|
| |
Turn doPwMount() in to a mount command wrapper. We're already calling
mount(8) and capturing error messages so we can pass them back up to our
Python code, so the same for unmounting filesystems.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our C-code isys EDD BIOS disk order detection is broken in 2 ways atm:
1) It tries to open "sda" instead of "/dev/sda"
2) It tries to open floppies and when it fails, it aborts further device
scanning
Besides that it didn't work with dmraid setups due to the following issues:
3) The C-code will not identify a device by the mbr signature from the
EDD BIOS info, if multiple devices match the signature, however
if we have a fakeraid mirror for example we will have 3 matching devices
both the 2 raw disks and the device mapper device.
4) The python code was using /dev/mapper/longName names where as the
C-code uses /dev/dm-#
5) The python code was calling the C-code (which builds a cache) before it
setup the dmraid sets, so those were not known to the C-code
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit 5a0189827c1c6db21ecbfd01f00ee1f5edbb7a77.
gcc-4.4.0-0.31 in rawhide fixes the problem we were seeing.
|