summaryrefslogtreecommitdiffstats
path: root/pyanaconda/install.py
Commit message (Collapse)AuthorAgeFilesLines
* Remove the storage module and replace it with blivet.David Lehman2013-01-281-1/+1
|
* Remove filesystem migration code.David Lehman2013-01-281-2/+1
| | | | | The only time anyone really used it was to migrate from ext2->ext3. It is dead weight.
* Prepare structures to save spoke completenes for firstboot and GIEMartin Sivak2013-01-111-1/+2
|
* Split ksdata execute and setup methods for addonsMartin Sivak2012-12-171-1/+4
|
* Add support for KS %addon section and the API+code to use itMartin Sivak2012-12-171-1/+4
|
* Add keyboard dracut setup args (#875567)Vratislav Podzimek2012-12-131-1/+1
| | | | | Without vconsole.keymap on kernel command line, dracut/plymouth uses 'us' as keymap in LUKS password prompt.
* Unify writeNetworkConf with other modules (rename, put in ks.execute)Radek Vykydal2012-12-051-2/+1
|
* don't write network settings on image installBrian C. Lane2012-12-031-2/+3
|
* Execute xconfig data (#874868)Jesse Keating2012-11-131-0/+1
|
* Blank out passphrases from /root/anaconda-ks.cfg (#868519).Chris Lumens2012-10-301-0/+6
| | | | | | 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.
* update to use firewalld (#815540)Brian C. Lane2012-10-171-1/+2
|
* Minimum we have to do with HW clockVratislav Podzimek2012-10-121-3/+8
|
* fix libuser setup (#855481)Brian C. Lane2012-09-271-5/+4
| | | | | createLuserConf needs to be called before the first use of User(). Also cleaned up some whitespace.
* Make progress hub spokes possible and move the root password thereMartin Sivak2012-09-131-28/+39
| | | | | - Splits doInstall to doInstall and doConfiguration - Updates text and gui mode to use doConfiguration
* Write storage configs after payload install for live installs. (#856836)David Lehman2012-09-121-0/+6
| | | | | | | | 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).
* fix root password setup (#855481)Brian C. Lane2012-09-091-2/+2
| | | | | | 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.
* Mark ksdata.*.execute invocations as another stepVratislav Podzimek2012-09-061-19/+21
|
* Don't depend on storage or instClass in EFIGRUBPeter Jones2012-09-051-1/+1
| | | | Resolves: rhbz#853308
* Remove anaconda.instLanguage object and language moduleVratislav Podzimek2012-09-041-0/+1
| | | | | We now use ksdata and execute methods for storing and writing configuration.
* networking: write configuration in doInstallRadek Vykydal2012-08-271-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Use ksdata.timezone and timezone module instead of anaconda.timezoneVratislav Podzimek2012-08-221-0/+1
| | | | | | | 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.
* Force authconfig to be installed on the target system (#848803).Chris Lumens2012-08-161-1/+6
|
* replace lokkit for selinux settings (#815540)Brian C. Lane2012-08-091-0/+1
| | | | | | 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
* Select language-specific groups as part of doInstall.Chris Lumens2012-08-021-1/+1
| | | | | This means you get the whatever-support group installed if you have the whatever language selected during installation.
* Update the authconfig command to work.Chris Lumens2012-07-241-0/+1
|
* Update the group, rootpw, and user commands to be called from doInstall.Chris Lumens2012-07-181-0/+8
|
* Hook up the kickstart firstboot command so it actually does something.Chris Lumens2012-07-171-0/+1
| | | | | | 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.
* Run clearpart, autopart, bootloader from the storage spoke.David Lehman2012-06-201-6/+0
| | | | We need to run these before the progress hub so we can catch errors.
* Add support for cdrom and harddrive methods, including switching.David Lehman2012-06-061-0/+1
| | | | | | | | 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.
* Enable setting up multiple layouts on the installed systemVratislav Podzimek2012-06-011-0/+1
| | | | | We need to write a config file to the /etc/X11/xorg.conf.d/ defining the layouts selected in the installation.
* Use pyanaconda.errors for error handling in storage.David Lehman2012-05-111-2/+1
|
* Move service enabling/disabling into an execute method.Chris Lumens2012-05-091-1/+6
|
* Run kickstart %post scripts at the end of installation.Chris Lumens2012-05-081-0/+3
| | | | | Certain portions of the install are now implemented as kickstart scripts, so they need to start being run.
* Enable bootloader install.David Lehman2012-05-031-2/+13
| | | | | | | Includes implementation of Payload.kernelVersionList property and Payload.dracutSetupArgs method, along with reworked writeBootLoader. I have renamed writeBootloader to writeBootLoader as well.
* Pass packages to select for storage, &c to payload.preInstall.David Lehman2012-05-031-1/+1
| | | | | Adds a property to Storage to list packages required for storage, platform, and bootloader.
* Remove all the writeKS methods except in network and storage.Chris Lumens2012-04-241-0/+16
| | | | | | | | 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.
* Generate an installer yum config for package install.David Lehman2012-04-191-1/+1
| | | | | | | | | | | 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.
* Enable package installation.David Lehman2012-04-191-0/+1
| | | | This is only tested with a sane http repo.
* Use a yum cache dir outside the install root.David Lehman2012-04-191-1/+1
| | | | | | | | | | | 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.
* Run clearpart prior to partitioning (you get CLEARPART_TYPE_LINUX).David Lehman2012-04-191-0/+1
|
* Add some convenience methods to hide the details of the queue implementation.Chris Lumens2012-04-191-2/+2
|
* Redo the progress bar code so it actually works.Chris Lumens2012-04-161-2/+4
| | | | | | | | | | | | 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.
* Add a top-level function that does the hard work of installation.Chris Lumens2012-04-091-0/+51
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.