| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
| |
The rules use shell glob syntax, not regular expressions.
|
|
|
|
|
|
|
|
|
|
| |
New udev rules for DM stuff use 'MAJOR' and 'MINOR' instead of 'DM_MAJOR'
and 'DM_MINOR', so we need devicelibs.dm.device_is_multipath() to check
for them instead. For now, this code will work with either variety.
This also makes devicelibs.dm.device_is_multipath() take the whole info
blob and do what it needs with it, rather than splitting it up in the
calling function.
|
|
|
|
|
|
| |
For devices created using an external utility we can display a
pulsing progressWindow. For devices created using a python module
we display a waitWindow.
|
|
|
|
|
|
| |
If we are using an external utility to create the format we can use
iutil.execWithPulseProgress. For formats we create using a python
module we can only put up a waitWindow.
|
| |
|
|
|
|
|
|
| |
There's some broken hueristic in mkswap that leads it to sometimes
mistake a logical volume for a disk and hence refuse to format it,
citing something about bootblocks. Nonsense.
|
| |
|
|
|
|
| |
Also includes mentioning the fact when a step is direct.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The BOOT flag of a partition indicates that it can be used to boot the OS
from. Surely this is no longer true after we've formatted it. Note that
we will set the BOOT flag on /boot later on.
|
|
|
|
|
|
|
|
|
|
|
| |
In F-10 and before we did not set the boot flag for /boot on msdos labels,
this could lead to issues when asked to install grub into a partition,
or with certain BIOS's which won't boot from a disk when there are no
active partitions on the disk. However our new behavior of always setting
the boot flag for /boot is wrong for msdos labels too, and is causing various
issues, see (amongst others) bug 533658, 530894 and:
http://forums.fedoraforum.org/showthread.php?t=231421
http://forums.fedoraforum.org/showthread.php?t=2348
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
First, there's nothing you can do. We don't allow changing the package set
or resizing partitions on upgrade, so you can't hope to recover. Second,
trying to go back is bringing up a tricky bug.
On preupgrade, all the steps before this one are in skipSteps. So dispatcher
tries to find the step to go back to, discovers there isn't one, and decides
to move "back" to the first step that wasn't skipped. To no one's surprise,
that's the same step we were on. However it's not an interactive step, so
setScreen tracebacks.
|
| |
|
| |
|
|
|
|
|
| |
This makes sure the keyboard both defaults to the right setting and is
correctly set in /etc/sysconfig/keyboard post-install.
|
|
|
|
|
|
|
| |
We're not guaranteed to have the _infofs program on every platform, so we
need to make sure the filesystem is supported before making an attempt. For
now this is only showing up on NTFS volumes on ppc, but it's possible to
come up in other places.
|
| |
|
|
|
|
|
|
|
| |
This hasn't worked since the switch to python-meh, though it's looked like
it has worked. Before, dumpState would cause an exception because it hadn't
been adapted to python-meh. This exception would then get written out as
/tmp/anaconda-tb-*, which made dumpState look like it worked.
|
| |
|
|
|
|
|
|
|
| |
In RHEL, we want the old bootloader timeout behavior, so people see
output on the teletype and have time to frob some switches on the
front panel. But for those of us in modern environments, we don't want
to do that, so this patch uses installclass to choose which one you get.
|
|
|
|
|
|
|
| |
If we don't have libwrap.so, sshd won't start. Previously this was
/sometimes/ pulled in by tcp-wrappers .
Also re-sort the list a little better.
|
|
|
|
|
| |
Some package %post scripts depend on usbfs, so mount it before installing
packages.
|
|
|
|
|
|
| |
We are currently using the fs/mounpoint with the smallest amount of
freespace when install.img needs to be transferred to the harddisk. Use the
fs with the largest amount of freespace instead.
|
| |
|
|
|
|
|
|
| |
Now you can use globs or non-device node names to specify disks in the
arguments to these commands, which should be a big help to large storage
configurations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is handy for large configurations so you can specify:
clearpart --drives=sda?
Instead of:
clearpart --drives=sdaa,sdab,sdac,sdad,sdae,sdaf,...
All shell globs are supported here, and all the DEVLINKS are checked against
the glob. This means you can use /dev/disk/by-path paths without knowing
the whole big thing.
|
|
|
|
|
|
|
| |
This allows specifying by anything that could be in DEVLINKS, which includes
stuff like UUID a second way, physical device path on the system, serial
number, and perhaps other methods depending on what kinds of devices are
installed. The next step is making this work throughout kickstart.
|
| |
|
|
|
|
| |
This is a migration of the patch 22e2548cbb41a0c32fa3a0a2e67e67bbf3109155 from rhel5-branch, BZ#493052.
|
| |
|
|
|
|
|
|
|
|
|
| |
terminates program in OOM scenarios.
This is to avoid having to copy-paste the asprintf-log-abort if branch
all the time. This commit also modifies existing asprintf() calls to
use the new macro in places where the change wouldn't modify program's
semantics.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Recent trees have been giving errors when we get to the stage2 download
point, such as this one:
Unable to retrieve http://download.fedoraproject.org/pub/fedora/linux/development/x86_64/os//images/install.img.
libcurl needs to be initialized inside urlinstTransfer() so it has the
latest network state for the system. The above error is caused by old
DNS settings. libcurl won't automatically do a res_init(), so we need
to set up a new curl instance and use that.
Since this patch moves curl usage to be exclusively within
urlinstTransfer(), move 'curl' to that function as well and remove it
from loaderData.
Add curl cleanup calls at the end of urlinstTransfer().
|
|
|
|
|
| |
We have glib for other things, so we can use it for option parsing and
dump another library dependency.
|
|
|
|
|
| |
Use g_file_get_contents() and g_strsplit() to read in .buildstamp data and
split it up. Remove static buffers.
|
| |
|
| |
|
|
|
|
| |
This message can be ignored in kickstart by using %packages --ignoremissing.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When updating device.map during upgrade of grub, I missed case when driveorder
changes between install and upgrade (e.g. when driveorder different from that
detected during upgrade had been specified when isntalling) in my previous
patch. To fix it, I generate device.map in similar way as when installing (only
updating it with some devices that we can know about only from updated
device.map - e.g. chainloaded devices). This brought me to another
consolidation of the code (started in previous grub installation patches):
* remove updateGrub, use writeGrub with upgrade flag instead
* move code from writeGrub into separate methods
writeGrubConf (called only for grub (re)install)
writeSysconfig (called both for grub (re)install and upgrade)
writeDeviceMap (called both for grub (re)install and upgrade)
* remove old writeSysconfig and updateDeviceMap that were called
only from upgradeGrub, use new writeSysconfig and writeDeviceMap
with upgrade flag instead.
|
|
|
|
|
| |
Also rewrote the baseudev.py to use the bindings instead of parsing
the udev db file
|
| |
|