| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
This is one of follow-up commits for commit
358a9a34f496fdd2b032edf12274a146b606d1a4, dealing with upgrade.
|
|
|
|
|
| |
CONFIG_NETIUCV has been disabled in the kernel, so remove support for
these devices during installation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before the device tree is built in the storage code, run through the
DASD devices on the system and format any with a status of
'unformatted'. We have to run dasdfmt on these devices before we can
partition them.
Under RHEL-5, this process was serial and the user had to click Yes for
each unformatted DASD found, which could take a really long time if
you had thousands of DASDs.
The idea now is that if the DASD is seen by anaconda, we want to use it
for installation. The stage 1 device initialization routines as well as
the CMS conf file provided at boot time allow the user to restrict the
range of devices we see during installation. If any of the devices we
see are unformatted, run dasdfmt before building the devicetree.
This process is implemented in a DASD class that works similar to the
iscsi and zfcp classes. That is, devices may need to be started or
brought in to a working state before the anaconda storage code can use
them.
|
|
|
|
|
|
|
|
|
|
| |
Previously, detailedMessageWindow() would just give you a messageWindow
and throw out the longText.
This patch tries to implement something that will let the longText
contain somewhat formatted text and allow users to scroll. That's done
with the ListboxChoiceWindow. Selecting any item in the list box is the
same as selecting button ID 0 on the dialog.
|
|
|
|
|
|
|
|
| |
Create an execWithCallback() function that takes in a callback function
and some data that is always passed to the callback function. Change
execWithPulseProgress() to use execWithCallback(). The idea behind
execWithCallback() is to allow flexibility to creating non-pulse
progress bars or other UI indicators.
|
| |
|
|
|
|
|
|
| |
This leaves the sshd support on the s390 intact and functional (testing
needed), and at the same time add the ability to ssh in and get a terminal
on non-s390 platforms.
|
|
|
|
|
|
|
| |
As discussed on IRC this changes the platform.diskType property
into a platform.diskLabelType method that takes a disk/device type argument
and uses this argument to check for dasd disks and in that cases returns
dasd as diskLabelType.
|
|
|
|
|
| |
Rename platform.diskType to platform.diskLabelType, as diskType is confusing
(we usally use it to refer to is the disk dasd, iscsi, zfcp, etc.).
|
|
|
|
|
|
|
| |
For some reason, gtk cycles backwards through the radio buttons under our
old UI arrangement, which was a table with one column and three rows, and
then an HBox packed into one of the rows with two columns in it. Instead,
just use a 2x3 table.
|
|
|
|
|
|
| |
This patch allows the user to select "Minimal" from the task list and get
just a bare minimum of packages. Note that the first task to have all its
groups selected by default will be the only one selected in the task list.
|
|
|
|
|
|
|
|
|
|
|
| |
Syntax error with kwargs in DASDDevice. Use kwargs.pop() in both
DASDDevice and ZFCPDiskDevice so DASD or zFCP specific kwargs are not
passed to DiskDevice.__init__().
Remove the incorrect name variable setting in ZFCPDiskDevice.
Change 'devices' to 'device' in udev_device_get_zfcp_attribute() so that
zFCP attributes can be read.
|
| |
|
|
|
|
| |
This snuck in as part of another commit when it shouldn't have.
|
| |
|
|
|
|
|
| |
As of now, a udev "add" event on an existing dm device causes the
device node to be removed from the /dev directory, which is bad.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This fixes an inconsistency where /boot could be on various filesystems
during interactive installs, but not during kickstart. What filesystems
are valid is controlled by the Platform module.
|
|
|
|
| |
This seems to be a more future-proof way of doing things.
|
| |
|
|
|
|
|
|
| |
For the rhel6-branch, we now have an x.y.z version number since it was
branched from f12-branch. The bumpver target needs to handle the extra
.z component.
|
| |
|
|
|
|
|
| |
Also rewrite getNextPartitionType for clarity so that bugs like this
will be easier to identify and fix in the future.
|
|
|
|
|
|
| |
We were previously using tests that have diverged from what's going on in
yuminstall.py, so this brings the two backend tests into using the same
concept.
|
|
|
|
|
|
|
|
| |
If fsck fails with a return code indicating errors we can't
automatically fix, give the user a more descriptive error dialog before
exiting. There's not much we can do if the filesystem is beyond
automatic repair, so tell the user to repair the filesystem under rescue
mode or something similar.
|
|
|
|
|
|
|
|
|
| |
Prevents this:
Traceback (most recent call first):
File "/tmp/updates/yuminstall.py", line 214, in callback
self.numpkgs)
TypeError: <lambda>() takes exactly 1 argument (3 given)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Because of 8bc669549ddcc7040a5ba56b8afafa18684bac4e and maybe others,
triggering reipl at the end of anaconda is no longer sufficient to be
hit in all different anaconda install paths. Therefore, move the triggering
right after having configured reipl in sysfs and do all in one place.
Now loader must no longer immediately relay SIGUSR1/2 to init,
since anaconda is not nearly finished with installation,
but only remember the state requested by anaconda. Only right before loader
terminates, it kills init with the remembered state to really reboot/halt.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This has always been broken for s390x since it was introduced in
67a5a0afb3100e7986ce127b3c2684e01c97304e. The fix ensures that both
s390 and s390x do not start a second shell on the console that collides
with init=linuxrc.s390 blocking on console input and potentially
providing a rescue shell after hitting return.
Apparently LOADER_FLAGS_NOUSB has gone meanwhile but nobody noticed
since this code path referencing it was never compiled on s390x.
|
|
|
|
|
|
|
|
|
| |
The support for boot option "nokill" in shutdown by
ade8105a8515afee24220fd0cc1199e30c1c3142 did not adapt the
standalone version of shutdown (#ifdef AS_SHUTDOWN) so doKill
was always 0. Introduce a new command line option "--nokill" and
otherwise default to doKill=1. While we're at it also provide
a command line option "-P" for poweroff.
|
|
|
|
|
|
|
| |
Return kernel parameter information for the DASD. NOTE: This is using
the current rd_DASD parameter in dracut, which is just a copy of the
dasd= kernel parameter. Will change this once dracut gets a better
rd_DASD parameter.
|
|
|
|
|
|
|
| |
Expand the DASDDevice class to hold the device bus ID and flags that are
passed at boot time. Add udev functions to return the bus ID and flag
values for DASD devices. When building the device tree, read the DASD
information and pass that to the DASDDevice object.
|
|
|
|
|
|
|
|
|
| |
Collect CCW bus ID, WWPN, and FCP LUN values for zFCP devices when
building the device tree. Store these in the ZFCPDiskDevice object and
use them to generate the rd_ZFCP= string for dracut.
Expand storage/udev.py with functions to determine if a device is zFCP
and to get arbitrary attribute values.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On s390x, linuxrc.s390 brings up the network completely and
writes an NM compliant /etc/sysconfig/network-scripts/ifcfg-<DEVICE>.
Apparently, loader never hits STEP_IP or writeEnabledNetworkInfo().
The latter would convert LAYER2= and PORTNO= into OPTIONS="".
Since it does not seem to be called, linuxrc.s390 now writes OPTIONS="".
Fixed readIfcfgContents() to not swallow OPTIONS which contains '='.
With this in place, network.py writes a correct ifcfg to /mnt/sysimage.
This patch completes ifcfg production on s390x of the following commits:
25f58fe7c701c453d39d2a9c5c0850eefce07f76
9249e40f42ffbbdcf42cd1caad72e3d622c7a75b
5f0fcf6688d08f83826c2892bb9fc97d6b4d7dd0
81163960a6137d39a5f2082e9f8d9f0a7b2ada57
This patch is intended for both devel and F-12.
|
|
|
|
|
|
| |
Use "device" entries in the config file rather than specifying
configuration parameters in the "multipath" section of the config file.
This gets us more reasonable configuration.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Boot repo parameter doesn't use slashes and we have to handle nfs urls from
both sources the same way in UI.
|
|
|
|
|
|
|
|
|
| |
If the bootLoaderInfo is old-style class, setting of its property drivelist
doesn't work, instead the property is overwritten with attribute and therefore
for example any following calls of updateDriveList have no effect.
AFAIK it doesn't cause problems anywhere at the moment, but I think it should
be fixed it in master.
|
|
|
|
|
| |
Just like we want things to not be mounted and lvm to be not active when
doing liveinstalls, we also want to start with any mdraid arrays deactivated.
|
|
|
|
|
|
|
|
|
|
| |
Our patch for adding support for the swap flag to parted msdos label handling
has been rejected upstream, upstream says we should use
ped_partition_set_system() instead. So do that, as I would like to drop this
patch from our parted package eventually.
This will also cause us to assign the right type to swap partitions in
GPT tables, so this patch should go to F-12 too.
|
| |
|