Gary Thomas wrote:
Gary Thomas wrote:
Jerry Vonau wrote:
Gary Thomas wrote:
Jerry Vonau wrote:
Gary Thomas wrote:
Running a system built with anaconda-11.4.0.40 (and friends), the
kickstart commands seem to be ignored when run from liveinst.
  # liveinst --text ks=/tmp/ks.cfg
     or
  # liveinst --text ksdev=eth0 ks=nfs:192.168.1.101:/tmp/ks.cfg

Am I doing something wrong?


Jeremy said that the ks file needs to be local at this point, stage1 grabs the ks file, but there is no stage1 with a cd install.

I really want to get this working so I can do [scripted] installs
from a livecd image.

Thanks


Is the network up at this point? If not.....

A work-around would be to script the grabbing of the ks file yourself and copying it /tmp. Use wget for a http/ftp source or maybe mount the nfs server and copy over the ks file.

Then use something like this:
liveinst --text ks=/tmp/ks.cfg

Precisely what I already did (see the first example above)

Just so I'm clear here, you burned the iso with this file in /tmp?

No, I downloaded the kickstart file into /tmp after the livecd was
booted, but before I called liveinst.

Looking through /usr/sbin/anaconda I see:
op.add_option("--kickstart", dest="ksfile")
but no --ks= so I don't think anaconda is using the ks file.

Perhaps "liveinst --text --kickstart=/tmp/ks.cfg" would do the trick here. That is setup in the livecd ks file, which would need to be edited:

if strstr "\`cat /proc/cmdline\`" liveinst ; then
   /usr/sbin/liveinst --kickstart=\$ks
fi

if strstr "\`cat /proc/cmdline\`" textinst ; then
   /usr/sbin/liveinst --text --kickstart=\$ks
fi

Hoping I'm on the right track,

Thanks - I'll look more closely at how these options are passed around.

I tried every option I could find, even trying to run anaconda in a more
"normal" mode, but it always ignores my kickstart file.  I even put an
incorrect file name <non-existent> and indeed nothing changed, hence my
assertion that the kickstart file (ks=XXX) is ignored completely.

What am I missing?  How can I get this to work?

Thanks

Mind if I have a look at your ks file that you used for the livecd creation?

Well, liveinst takes the place of stage1, and is just a wrapper, have a look:

# eventually, we might want to allow a more "normal" install path
ANACONDA="/usr/sbin/anaconda --method=livecd://$LIVE_BLOCK --lang $LANG"

if [ ! -e /selinux/load ]; then
    ANACONDA="$ANACONDA --noselinux"
fi

if [ -x /usr/bin/hal-lock -a -e /var/lock/subsys/haldaemon ]; then
    /usr/bin/hal-lock --interface org.freedesktop.Hal.Device.Storage \
 --exclusive --run "$ANACONDA $*"
else
    $ANACONDA $*
fi



As a test let the livecd boot, (don't pass liveinst at the boot prompt), try editing the liveinst file, adding in your kickstart stuff:
ANACONDA="/usr/sbin/anaconda --method=livecd://$LIVE_BLOCK \
--lang $LANG --kickstart=/tmp/ks.cfg"
save and then call liveinst.

Just trying to narrow down where the ks variable is not being passed.

Jerry




--
Fedora-livecd-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-livecd-list

Reply via email to