| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It's up to firstboot to set up the first user as the admin. Or, the user
can go through with a kickstart install.
This requires an updated version of pykickstart that understands the rootpw
command doesn't need a password argument if it's just going to lock the
account.
|
| | |
|
| |
| |
| |
| |
| | |
It is used only in the text mode and it should be possible to replace
it with calling 'loadkeys' command in the new text mode.
|
| |
| |
| |
| |
| |
| |
| | |
The only thing we were using from the system-config-keyboard was the
activate method that basically just calls loadkeys command. This can
be easily replaced with our own method using data from ksdata.keyboard
allowing us to remove anaconda.keyboard object.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Brian C. Lane <bcl@redhat.com>
|
| |
| |
| |
| | |
Signed-off-by: Brian C. Lane <bcl@redhat.com>
|
| |
| |
| |
| |
| |
| |
| | |
Use case is to create images using livemedia-creator where we wont be
running on the target platform.
Signed-off-by: Brian C. Lane <bcl@redhat.com>
|
| |
| |
| |
| |
| |
| | |
kernel to install.
Signed-off-by: Brian C. Lane <bcl@redhat.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
proper class
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\| |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Otherwise, it won't start and thus anaconda won't start. The other way to
fix this would be to add stuff to lorax to move the file into place, but I
don't want to make lorax changes.
|
| | |
|
| | |
|
| |
| |
| |
| | |
This was built by gptsync, which is no longer with us.
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
Makefile.am
anaconda
data/systemd/anaconda.target
pyanaconda/bootloader.py
pyanaconda/constants.py
pyanaconda/iutil.py
pyanaconda/kickstart.py
pyanaconda/network.py
pyanaconda/vnc.py
scripts/makeupdates
|
| | |
| | |
| | |
| | |
| | |
| | | |
Make "readfile" more clear about its intent (read one line, discard
errors). Rename it to "readsysfile" just so nobody gets confused about
what it's for.
|
| | |
| | |
| | |
| | | |
Emit logging messages when 'rd.debug' or 'rd.info' are passed.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Having a shell on tty2 or hvc1 is convenient.. if you have tty2 or hvc1.
But not everyone does - think s390, or POWER, or remote virt guests.
Instead, let's run anaconda inside a tmux session, with windows
pre-configured with a shell, anaconda.log, program.log, and storage.log.
We set this up by using two services: anaconda.service, and
anaconda-tmux@.service.
anaconda.service starts anaconda (and starts watching the logs) inside a
detached tmux session, on screen 1. It also starts a shell on screen 2,
and 'tail -F' on anaconda.log, storage.log, and program.log on screens
3, 4, and 5.
anaconda-tmux@.service will be instantiated on the default console
(tty1, hvc0, ttyS0, whatever) and connect to the running tmux session,
which will show screen 1 - and thus the text UI (if any) appears.
Exiting tmux just restarts anaconda-tmux@.service, which reconnects to
the existing session, so you can't accidentally kill the installer by
leaving tmux.
|
| | |
| | |
| | |
| | |
| | | |
Print a couple of messages as anaconda starts up so the user isn't
confused about what's happening after the screen goes dark.
|
| | |
| | |
| | |
| | |
| | | |
Commit c8c14c9 deleted these two files, but they got resurrected in some
merge somehow. Delete them again, since we don't need them.
|
| | |
| | |
| | |
| | | |
This is related to commit 43715e5db831893edcfc2b289a1e575b0ba19403
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Dracut debug shell gives users root like access, without a password.
This is not a good thing if the admin has decided that the system should
have a password protected boot loader. So for boot loaders that support
password protection, we should also add the rd.shell=0 flag to the boot
arguments to prevent the user from gaining root level access.
|
| | |
| | |
| | |
| | |
| | | |
We're not supporting the boot mode that requires gptsync so don't ship
the software any more.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Resolves: rhbz#836307
|
| | |
| | |
| | |
| | |
| | |
| | | |
When F12 (the global default continue hotkey) is pressed the button
value is None. But we still want to process the details when this
happens. The use of bool here makes it a little easier to read.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
snack/newt returns None for a button if F12 is pressed which is a global
default. There can be passphrase data in the box when this happens and
we should read it. The only time we should ignore anything in the box
is if the user has explicitely pressed the cancel button. If the
passphrase box is empty but the user pressed F12 we still handle that
correctly as an implicit cancel.
|
| | |
| | |
| | |
| | |
| | |
| | | |
/etc/zipl.conf is written by anaconda when we install the boot loader.
Because we mess with it, we have to reset the selinux context on it
before rebooting.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If a kickstart pre/post fails we read the logfile and add it to the
anaconda log. This doesn't work well for device nodes like /dev/console
so skip reading the log it isn't a regular file.
Resolves: rhbz#835563
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Forced reboot just kills processes without shutting units/services
down. In case of NetworkManager.service this terminating of NM is racing
with that of dhclient. If dhclient dies first, NM brings down respective
connection which - if used by NFS mounted in dracut (e.g. for repo=nfs:
repo=nfsiso: installs) - causes hang when systemd umounts filesystems.
Resolves: rhbz#818581
|
| | |
| | |
| | |
| | |
| | | |
If zipl doesn't succeed, the install won't reboot when finished. This
is not an acceptable situation.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
execWithCapture normally doesn't care about non-zero exits in called
processes. In some cases (most?) this is preferred. In few cases we do
actually care about the success or failure of the execution. "fatal"
provides a boolean that will allow callers to decide if they care or
not.
An OSError is raised because there is already code to catch that in the
except section.
Related: rhbz#730023
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Device formats have both a type and mountType property. The mountType
property has a fallback of reading the _type attribute, if _mountType
isn't set. But when we're migrating filesystems, the _mountType will
have already been set, so just modifying _type won't effect any code
looking at mountType. This can lead to the wrong data being written out
to say /etc/fstab.
|