<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
This describes basically how to do kickstart Lime Image install:
<a class="moz-txt-link-freetext"
href="http://fedoraproject.org/wiki/Anaconda/Kickstart/KickstartingFedoraLiveInstallation">http://fedoraproject.org/wiki/Anaconda/Kickstart/KickstartingFedoraLiveInstallation</a><br>
<br>
If you stick with network-only for locations of the install image,
this also works for Fedora 20. However, for the full capability of
network or USB Flash Drive for the location of the image, the Fedora
21 is needed.<br>
<br>
Optionally, I have an updates.img available for anaconda-20.25.16-1
here: <a class="moz-txt-link-freetext" href="http://czarc.org/fedora/updates/">http://czarc.org/fedora/updates/</a><br>
<br>
As described here:
<a class="moz-txt-link-freetext" href="http://fedoraproject.org/wiki/Anaconda/Kickstart#liveimg">http://fedoraproject.org/wiki/Anaconda/Kickstart#liveimg</a><br>
<blockquote type="cite">
<p><code>liveimg --url=<url> [--proxy=<proxyurl>]
[--checksum=<sha256>] [--noverifyssl]</code>
</p>
<dl>
<dd> Install a disk image instead of packages. The image can be
the squashfs.img from a Live iso, or any filesystem mountable
by the install media (eg. ext4). Anaconda expects the image to
contain utilities it needs to complete the system install so
the best way to create one is to use livemedia-creator to make
the disk image. If the image contains /LiveOS/*.img (this is
how squashfs.img is structured) the first *img file inside
LiveOS will be mounted and used to install the target system.
As of Anaconda 21.29 the URL may point to a tarfile of the
root filesystem. The file must end in .tar, .tbz, .tgz, .txz,
.tar.bz2, tar.gz, tar.xz
</dd>
</dl>
</blockquote>
You can also kickstart install with liveimg pointing to a tarball as
or anaconda-21.29 ... well, sort-of. It basically works but there
are a couple of problems.<br>
<br>
1. The initramfs file for the rescue kernel is not created when
doing a tarball install. The problem along with a patch to fix it
has been bz'ed: <a class="moz-txt-link-freetext" href="https://bugzilla.redhat.com/show_bug.cgi?id=1170589">https://bugzilla.redhat.com/show_bug.cgi?id=1170589</a>
and the patch has also been submitted to anaconda-patches. Since it
is unlikely that this update will make it into Fedora 21, I have
created an updates.img for anaconda-21.48.21-1 which is available
here: <a class="moz-txt-link-freetext" href="http://czarc.org/fedora/updates/">http://czarc.org/fedora/updates/</a> (the README.txt is the output
of git-log showing what updates are applied).<br>
<br>
2. Using the updates.img, you do a kickstart liveimg<i> </i>install
of a tarball. Everything is good ... sorry, no. I am not sure if
this is a bug but installation using a tarball needs a full-system
SELinux relabel. Fortunately, this is easy to handle by adding the
following to your kickstart file:<br>
<blockquote type="cite"><big><tt>%post</tt><tt><br>
</tt><tt>/usr/bin/touch /.autorelabel</tt><tt><br>
</tt><tt>%end</tt></big></blockquote>
<br>
Enjoy, Gene<br>
</body>
</html>