| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Errors bring returned is a simple mismatch or invalid chars, which we
can't allow. Raised items are actual quality issues which the user
could use anyway.
|
|
|
|
|
|
| |
This moves it to a more central spot so that it can be used by both the
gui and the text spoke, or any other thing that wants to validate
passwords.
|
|
|
|
|
|
| |
There may be cases when we don't get exit code. Especially in those
nonstandard cases we should honor the 'nokill' flag and don't reboot
the machine.
|
|
|
|
|
| |
This will only help if the disks and/or their free regions are very
small.
|
|
|
|
|
|
| |
They won't show up in /etc/fstab and they don't have mountpoints, so
it really doesn't matter if they exist or not. We want to include
them in the new root regardless.
|
|
|
|
|
| |
This was only triggered if none of the partitions being allocated
were growable, which has become a very rare case.
|
| |
|
|
|
|
|
| |
There is no guarantee of growth, so be sure to start with a size
that can hold the specified formatting.
|
|
|
|
|
|
|
| |
If we skip accounting for any requests, the set's data will no longer
match the state of its devices. We need to know how much every device
has grown. This bug was leading to severely overgrown sets in some
cases.
|
|
|
|
|
| |
It already gets called from _do_refresh and multiple calls to
save_right_side are both wasteful and potentially dangerous.
|
| |
|
| |
|
|
|
|
|
|
| |
The parted list should be pretty much in sync, but this way saves
some trouble with resolving the parted partition paths to devices
in the devicetree.
|
|
|
|
|
| |
This also uses Storage.recursiveRemove to remove dependent devices
before trying to remove the partition.
|
| |
|
|
|
|
|
| |
This is used to prevent combinations of features that do not
reduce to a valid raid level.
|
| |
|
| |
|
|
|
|
|
| |
ValueError makes exception handling difficult since you can't know
if the error is something expected as opposed to a programming error.
|
| |
|
|
|
|
|
|
| |
If we are given invalid X layouts (not supported), we have to remove them
from the list. If none are left in the list, we should act like if there
was none specified at all and add our defaults.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to set VConsole keymap and X layouts separately. We may
get them all from kickstart, but if not, we have to convert the
given one to the missing one and save the configuration. If X11
configuration is written before the server is started, it is
loaded. This way we can get rid of using XklWrapper in main anaconda
script.
Also we need to write one more configuration file. And it's better
to try to write all configuration files ignoring errors and in case
some error(s) appeared, raise exception at the end of the procedure.
Resolves: rhbz#853877
Resolves: rhbz#856362
Resolves: rhbz#859867
|
| |
|
| |
|
|
|
|
|
| |
We should indicate where does this file come from. Moreover, without this
comment vim doesn't turn on the syntax highlighting automatically.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Wifi connections have separate ifcfg files, not specified by the
device name.
Signed-off-by: Vratislav Podzimek <vpodzime@redhat.com>
|
|
|
|
|
|
|
|
| |
Using libnm-glib from a separate thread results in a hang, probably
because libnm-glib has to do some "loops magic" for its internal use
of DBus.
Signed-off-by: Vratislav Podzimek <vpodzime@redhat.com>
|
|
|
|
| |
"b" means bits, which is definitely not what we want to display.
|
|
|
|
|
|
|
|
| |
With the addition of Cinnamon and MATE and some others, there's now entirely
too much stuff in the environment window to fit without scrolling. Plus, I
guess smaller screens always needed to scroll. Without a scroll bar, GTK
puts this window in a really bizarre place. See the screenshot attached to
the bug.
|
| |
|
|
|
|
|
|
| |
Catch some common errors that are not practical to prevent via the
UI and show an error message instead of attempting to carry out the
request.
|
| |
|
|
|
|
|
|
| |
/boot can be on btrfs, lvm, or md. This should be handled in the ui.
Related: rhbz#864131
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Resolves: rhbz#862667
Resolves: rhbz#960994
|
|
|
|
|
|
|
|
| |
BTRFS and RAID are not always in the device type combo, so we
can't count on using direct index access to the combo.
Resolves: rhbz#862667
Resolves: rhbz#860994
|
| |
|
|
|
|
|
|
|
|
| |
reIPL used to be ran via dispatch, and would trigger either a reboot or
a shut down. Now we'll run it as part of the s390 bootloader install.
The message warning users to reipl themselves is somewhat lost here,
something for another day perhaps. This at least gets the system
working right.
|
| |
|
| |
|
|
|
|
|
|
| |
This keeps the ugly hack going, but it keeps us from crashing on the
s390 case where anaconda gets launched twice (once to prompt for ssh,
once inside tmux to do the actual install).
|
|
|
|
|
|
| |
If anaconda is launched /inside/ tmux, the TMUX variable will be
present. This is the anaconda we want to attach to, so don't prompt for
ssh here.
|
|
|
|
|
|
|
|
|
| |
When installing on s390x, we just want to run pure anaconda on the tty.
This will either detect s390x and print out ssh details for the user to
ssh in to continue the install (and get tmux), or if a kickstart was
provided and the RUNKS option was used it will just blast through the
kickstart in cmdline mode. Tmux doesn't work in x3270, the terminal for
s390x, so we have to avoid using it.
|
|
|
|
|
| |
This is useful as the install user's shell, rather than having anaconda
direct as that shell.
|
|
|
|
|
|
|
|
|
| |
Break out the setup of ARM-OMAP systems, as they need to have a vfat partition
at the start of the disk in order for the SOC to load the initial boot code.
This also sets the weight for the '/' partition to ensure it is the last
partition on the image.
Signed-off-by: Brian C. Lane <bcl@brianlane.com>
|
|
|
|
|
|
| |
This likely hits every single kickstart install. Because we run execute
over and over again, we're eventually going to hit a situation where
storage just breaks.
|