| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
IT IS ACCOMPLISHED.
|
| |
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Also, rip out all the username/password stuff too. That's not needed for
nfs.
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
