| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
The only time anyone really used it was to migrate from ext2->ext3.
It is dead weight.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Without vconsole.keymap on kernel command line, dracut/plymouth
uses 'us' as keymap in LUKS password prompt.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Note that this means the resulting kickstart file will be less-than-complete,
which is not what we want but is apparently what users want. Any bugs filed
regarding this will be closed WONTFIX.
|
| |
|
| |
|
|
|
|
|
| |
createLuserConf needs to be called before the first use of User().
Also cleaned up some whitespace.
|
|
|
|
|
| |
- Splits doInstall to doInstall and doConfiguration
- Updates text and gui mode to use doConfiguration
|
|
|
|
|
|
|
|
| |
For yum payloads we write storage config before installing the payload
so %post scripts have access to the configuration files if needed. For
live installs, we have to write the config after installing the payload
since installing the payload would overwrite parts of the storage
configuration (notably /etc/fstab).
|
|
|
|
|
|
| |
libuser checks the LIBUSER_CONF environmental variable and uses the
temporary config file it points to, but in order for this to work it
must be set before User() is run.
|
| |
|
|
|
|
| |
Resolves: rhbz#853308
|
|
|
|
|
| |
We now use ksdata and execute methods for storing and writing
configuration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Short story:
Ifcfg files are (still) copied from installer environment instead of
generating from ksdata[1].
Details:
Ifcfg files can be created during installation
- in dracut: based on boot options and kickstart
- in anaconda: missing default ifcfg files[2]
- in GUI using nm-c-e
Going through ksdata here (update ksdata in spoke.apply and write ifcfg
files from ksdata at the end of install - writeNetworkConf in doInstall [3])
- which is what we would generally do for other spokes - is not necessary,
and has some caveats:
We'd need to update ks network command to mirror all configuration doable
in ifcfg files with nm-c-e (plus wireless credentials stored in keys-<device>
files, routing stored in yet another network-scripts files) and keep
up with every update of nm-c-e options instead of letting nm-c-e just
write the configuration for us. Also NM can update ifcfg files on its
own after they are written - another opprotunity for missync.
[1] Beside ifcfg files we also copy /etc/sysconfig/network-scripts/keys-<device>
files. We might want to copy also routing files created in nm-c-e.
[2] this should go to dracut IMO.
[3] such would be the chain:
- dracut writes ifcfg files
- NM can update ifcfg when activating device
(does anaconda need to update ksdata ?)
- anaconda can write missing default ifcfg files
- nm-c-e can modify ifcfg files (GUI configuration)
- anaconda stores ifcfg to ksdata (spoke.apply)
- anaconda dumps ksdata to ifcfg on /mnt/sysimage (doInstall)
- anaconda modifies configuration for storage devices,
and to set ONBOOT default - currently this can't precede the previous
step because we are changing NM_CONTROLLED which is not mirrored
in ksdata, so we need also to sync ksdata in this step
|
|
|
|
|
|
|
| |
We now use ksdata to store data and execute() methods of kickstart
commands to set the installed system up. In order to not place all
the code to kickstart.py, timezone.py module gathering all timezone
related code was created.
|
| |
|
|
|
|
|
|
| |
lokkit is going to be going away, all it did was edit the selinux config
file, so do that ourselves with SimpleConfigFile. Also add selinux
kickstart execute method
|
|
|
|
|
| |
This means you get the whatever-support group installed if you have the
whatever language selected during installation.
|
| |
|
| |
|
|
|
|
|
|
| |
Note that this does not yet handle the fact that we want to skip firstboot
on most kickstart installs (unless the user specifies otherwise). We need
a place to load those defaults, which will be a separate patch.
|
|
|
|
| |
We need to run these before the progress hub so we can catch errors.
|
|
|
|
|
|
|
|
| |
Clean up mountImage and opticalInstallMedia to match their new surroundings.
Allow a path to a specific image file to be specified to mountImage.
Don't automatically mount optical media we detect in opticalInstallMedia.
|
|
|
|
|
| |
We need to write a config file to the /etc/X11/xorg.conf.d/ defining
the layouts selected in the installation.
|
| |
|
| |
|
|
|
|
|
| |
Certain portions of the install are now implemented as kickstart scripts,
so they need to start being run.
|
|
|
|
|
|
|
| |
Includes implementation of Payload.kernelVersionList property and
Payload.dracutSetupArgs method, along with reworked writeBootLoader.
I have renamed writeBootloader to writeBootLoader as well.
|
|
|
|
|
| |
Adds a property to Storage to list packages required for storage,
platform, and bootloader.
|
|
|
|
|
|
|
|
| |
Those appear to have a lot of information still in them that may not be
present either in pykickstart or elsewhere in anaconda. Those still won't
be called, but I'm not yet comfortable removing them entirely.
Also, use pykickstart to do the writeKS stuff now.
|
|
|
|
|
|
|
|
|
|
|
| |
We have to switch yum over from the configuration-time installroot to
the install-time installroot. This, of course, is not as simple as
changing an attribute of the YumBase instance. Instead, it requires
that we create a new instance of YumBase with the new configuration.
Instead of calling updateBaseRepo again to start from scratch and try
to establish an install-time repo set like we do during configuration,
write out the configuration we want for install time based on what
was configured and then tell the install-time YumBase to use it.
|
|
|
|
| |
This is only tested with a sane http repo.
|
|
|
|
|
|
|
|
|
|
|
| |
In the new UI users configure software selection and repos before
the new root filesystem exists on ROOT_PATH. This means we need to
do the configuration with a yum installroot outside of ROOT_PATH.
Of course, we need to switch to the new/actual root before we
install packages.
I am planning to smooth this out such that it will not require a
full run through updateBaseRepo or a storage instance.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the previous code, I could never get the UI to be redrawn to reflect the
changes, even though the changes appeared to have taken effect.
This new code instead uses a message queue for communication between the thread
doing all the hard work and the main thread that handles GTK stuff. The storage
code will shove messages into that queue when it does something like create a
filesystem, and the main thread watches in the idle loop for messages.
I've also provided yet another context manager to make all this code simpler.
|
|
There's nothing particularly clever about this. It just calls the ksdata
execute methods linearly, makes partitions, and installs packages. Error
handling is not yet in good shape and neither is progress reporting.
However, an autopart setup will actually make partitions.
|