| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Various parts of anaconda either call these methods or expect them to return
certain values (so, not NotImplementedError) and it's just easier to have them
return default values than create new implementations.
|
| |
|
| |
|
|
|
|
| |
Or really, any devices we can't actually use.
|
|
|
|
|
| |
/ is always mounted for us anyway, and since we're using rsync it's just a
simple matter of copying from that directory to our destination.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This prevents trying to mount the device a second time. If it's already
mounted, and is a valid source of repodata, use it from the path it's
already mounted on. Otherwise go ahead and mount the selected optical
drive where we want it.
|
|
|
|
|
| |
The full device is more useful than just the path. Callers can get the
path if they want it.
|
|
|
|
| |
This will return a list of places a particular device might be mounted.
|
| |
|
|
|
|
|
| |
We're unsetting method there too, we need to unset the install_device so
that we don't try and mount it later.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Nothing uses a method/repo of 'cdrom://<dev>:<path>' anymore, and
nothing passes a method like '@/tmp/filename', so this code is all
useless.
|
|
|
|
|
| |
A bunch of these comments don't apply anymore - update them so they
reflect reality
|
|
|
|
| |
Systemd handles the tricky bits of logging for us now. Yay!
|
| |
|
|
|
|
|
|
| |
- We can add dhcp activation in networkInitialize in thread later
- Also fixing merge (newui->master) of
https://lists.fedorahosted.org/pipermail/anaconda-patches/2012-June/000023.html
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ksdata.network.hostname which is new property (there is a related kickstart
patch) obtaining the hostname from network commands (ksdata.network.network
list of NetworkData objects). The goal is to use this data instead
of getting actual hostname of installer (getHostname function)
notes:
- ksdata.network.hostname value will be initalized in networkInitialize
(following patch)
- getHostname (actual hostname of system) is still used in dracutSetupArgs,
we need to get ksdata passed somehow from bootloader.py:set_boot_args()
- Hostname of installer environment is still set in kickstart. We used to
do it because of mdadm member naming (640743) but this is not needed
anymore - mdadm actually doesn't use it. If it starts to again, or
does it in some special conditions, we can pass ksdata.network.hostname
(as we do for default vg names) using --homehost option.
We might need to set the hostname for some installed package though,
so I am keeping it.
- We should think about where to set hostname in GUI. This should happen
before writing storage (needed for vg, mdmember names), or we can drop
default naming based on hostname.
|
| |
|
|
|
|
| |
See udev's 828136.
|
|
|
|
| |
Instead of creating the file in installer and copying it to system.
|
|
|
|
|
|
|
| |
ksdata are updated in NetworkSpoke.apply from ifcfg files.
At the end of installation we need to modify ifcfg files
(network configuration) for devices used by storage and to
set ONBOOT defaults. So update also ksdata.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Do locking inside release since it gets called from outside of
YumPayload.
|
| |
|
|
|
|
|
|
| |
This way if the user starts with one of those methods and doesn't change
anything before hitting back, we won't waste time trying to redownload
everything.
|
|
|
|
|
| |
This reverts commit d82ee4a818be9db7b65282fad7de3c8bf872a6f3.
There is a better way to do this.
|
|
|
|
|
|
|
|
| |
This recovers some logic from yuminstall.py, only use /run/install/repo
if there is metadata there.
This is related to bug 851274 , but only fixes part of it. It gets
booting from boot.iso working again, but leaves booting from DVD broken.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This spoke sets the root password, or if left blank disables the root
login. Some level of validation is done and the user is trapped until
they get it right or press back twice on a weak password.
capslock monitoring is not enabled currently, but there is some stub
code commented out that deals with it.
|
|
|
|
|
|
|
|
|
| |
This updates what attributes get written out to the traceback file for the
newui. In particular, it avoids writing out all the yum stuff that makes the
traceback file grow over 2 MB and take nearly a minute to pickle.
It's entirely possible this is either skipping too much or writing out too
much still, but we can work on that over time.
|
| |
|
| |
|
| |
|
|
|
|
| |
This prevents a traceback from happening when handling tracebacks.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
the splitsep function was buggy before, but it was fixed in dracut 019
so we don't need these workarounds anymore.
See upstream dracut commit f7cadaa843498c4b986f8a030fab39002ad108b6.
Related: 844c0c156ed2f27920257d86690f3017727f398e
Related: 700e985082b03abcbd3009de81885b8fbf72818b
|
|
|
|
|
|
|
|
|
| |
We updated the anaconda dracut module to work with "newer" dracut; all
the features/changes that would actually cause compatibility problems
are present in dracut 019 and later.
(The systemd changes are in dracut 020 but existing anaconda-dracut code
is still backward-compatible with 019)
|