| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
IT IS ACCOMPLISHED.
|
| |
|
|
| |
e.g. network --ipv6=2001:aaaa::1/48
|
| |
|
|
|
|
| |
See also 88eaea1d9e3811e08e56174f93d9362e95494e77.
Resolves: rhbz#734967
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
We ended up with netDev_set == 1 and netDev == NULL in the case
which resulted in SIGSEGV later. The patch sets netDev to value
of --device option which leads to asking in UI as in other similar
cases.
Resolves: rhbz#697432
|
| |
|
|
|
| |
These decisions will now be made in anaconda proper. There's no need to
involve three separate processes in the discussion.
|
| |
|
|
| |
Related: rhbz#683953
|
| | |
|
| | |
|
| |
|
|
|
| |
Also remove noksdevice handling. It doesn't work anymore,
I wonder if it ever have worked or even been used.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
For non-network installs it restores rhel 5 behaviour that
was changed in master by commit 9767cb5fce174e8fcf28d06ad6f48384129a7cd4
(which would activate the device in any case).
Now new --activate option can be used if bringing up the device
in non-network install is desired.
Port from rhel6-branch.
Related: rhbz#638131
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Port from rhel6-branch.
Resolves: rhbz#668395
No matter whether it has the new --activate flag set.
For network installs restores common rhel 5 and master behaviour.
For non-network installs it restores master's behaviour
which is to activate the device. Rhel 5 behaviour (don't
bring the device up for non-network installs) will be
restored by following patch.
|
| |
|
|
|
|
|
|
|
| |
Port from rhel6-branch.
Resolves: rhbz#638131
Sets DEFROUTE=no in ifcfg file. Use case: one NIC used to fetch
packages, another for iSCSI. Using the option we can prevent the latter
to grab default route.
|
| |
|
|
|
| |
Port from rhel6-branch
Resolves: rhbz#638131
|
| |
|
|
|
| |
Port from rhel6-branch.
Resolves: rhbz#638131
|
| |
|
|
|
| |
Port from rhel6-branch.
Resolves: rhbz#638131
|
| |
|
|
|
| |
I think that rebooting is accomplished by not specifying halt or reboot,
so don't specify either of those.
|
| |
|
|
|
| |
This should fix all problems described in the above bug. All the decisions
about suggesting VNC are handled within anaconda proper.
|
| |
|
|
|
|
| |
pykickstart ensures that if "updates" is given, url is set to "floppy".
Otherwise, you've either provided a URL or skipped the command entirely.
In the last case, url is "".
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Lots of people rely on the fact that a %pre script can generate a file that will
later be %included. Proper kickstart processing involves first making a pass over
the file looking for any %pre scripts, ignoring all %include lines. Then another
pass is made that handles all the %includes, which will pick up and that were
generated.
With the pykickstart integration, I made it so reboot and other loader-handled
kickstart commands can be in a %include file. However, this also made a missing
%include a fatal error, which breaks the %pre-generated include trick.
This fix makes it so any %includes that do exist will be processed in loader, but
missing ones will not be a fatal error. It will only be much later during
anaconda proper that a missing include will cause an error.
|
| |
|
|
|
| |
Since the loader is doing this now, we can just call it once there, then pass
the preprocessed file location into anaconda via the --kickstart parameter.
|
| |
|
|
|
|
|
| |
Since we're just running every command handling function and letting the
function decide whether it need to do anything, there's no need for the
command names and special structure. Instead, just keep an array of
function pointers to iterate.
|
| | |
|
| |
|
|
|
| |
Running the commands will now require operating on PyObjects, and I don't
want to expose that outside of kickstart.c.
|
| | |
|
| |
|
|
|
|
|
| |
This involves converting runKickstart to setting up the pykickstart interface
and then walking through every entry in ksTable to call the setupData
function. A later patch will change these functions to make sure there's
something for them to do before running.
|
| |
|
|
|
|
| |
Doing this lets me get rid of the special purpose kickstart parser in
kickstart.c that doesn't understand %ksappend or %include and must certainly
follow different quoting rules.
|
| | |
|
| |
|
|
|
|
|
| |
This is required so the source layout and package layout have a similar enough
structure to make our test setup work. Without this move, you can't run
"make check" or checkbot without getting error messages about no such module
pyanaconda.booty.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Where people come up with these use cases is beyond me. Here we go:
1) Prepare an ext2/3/4 volume on the hard disk and drop the install DVD
iso as well as images/install.img on there.
2) Drop a kickstart file on this volume called ks.cfg. Make sure it:
a) Has *no* 'network' lines
b) Uses 'harddrive --partition=DEVICE --dir=/PATH'
c) Contains a valid 'vnc' line
2) Copy vmlinuz and initrd.img to the /boot directory for the system.
3) Edit boot loader configuration to boot the installer kernel+ramdisk.
4) Reboot system, choose installer and pass:
ks=hd:DEVICE:ks.cfg
Without this patch, the network is never configured during loader
because both the install media and kickstart file are provided locally.
However, we do need to bring up the network for vnc, so look for a vnc
line in the kickstart file and make sure the network is brought up.
|
| |
|
|
|
|
| |
This is in preparation to use logging from imount.c. We don't want a dependency
of isys on loader, instead move logging code into isys and change loader sources
to use the log.h header in isys.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If a read from a block device (like USB key) or a cdrom (USB cdrom) fails, sleep
a bit to give the device some time to initialize. Return status of the mount
command is checked so waiting occurs only if there is a reasonable chance that
the device might eventually come online. This required extending our existing
mounting methods to report the correct mount error code.
I tested that
* the installer still runs
* reading the kickstart from a usb works
* starting the installer with no USB key inserted but a command line argument pointing to a USB drive will trigger the waiting cycle and that when the key is inserted while waiting the kickstart is eventually found on the key.
|
| |
|
|
|
| |
We have glib for other things, so we can use it for option parsing and
dump another library dependency.
|
| |
|
|
|
| |
Use glib's data structures and string functions in modules.c since we
already have glib. Add in some safety checks as well.
|
| | |
|
| |
|
|
|
| |
Also, rip out all the username/password stuff too. That's not needed for
nfs.
|
| | |
|
| |
|
|
| |
so we can correctly free it (#483818)
|
| |
|
|
|
|
| |
This test causes it not to reboot if you don't specify anything about
rebooting in kickstart or on the command line. It also treats /all/
installs with "nokill" specified as "halt" installs.
|
| | |
|
| |
|
|
|
| |
Fix two missing things. I dropped the { in the git patch and needed
to remove the now-unused iface_t in main.
|
| |
|
|
|
|
|
| |
If the user passes ks=hd: or another non-remote kickstart location,
do not bring up networking during installation. However, if they
pass the 'vnc' parameter, make sure we do bring up networking early
because we can't let them configure it by the time we get to stage2.
|
| | |
|
| | |
|
| |
|
|
| |
config problem (found looking at #75614)
|