Newbie on the anaconda team
- Fedora 12
- squid proxy to cache packages
- lighttpd to serve up updates.img
- tftpd to serve up pxe boot images
- mock + pungi for building
yum install mock
- Edit the
/etc/mock/site-defaults.cfgfile to bind your working directories inside the mock root. This keeps mock from wiping those directories on --init
config_opts['plugin_conf']['bind_mount_enable'] = True config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/home/user/projs/anaconda', '/root/anaconda' )) config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/local/repo', '/repo' )) config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/local/pungi', '/pungi' ))
- Edit the
/etc/mock/file for the distribution or copy it to a new name and edit
proxy=http://proxy.home:3128to the main section.
- comment out mirrorlist entries
- Open up the mirror list url(s) in a browser and pick a mirror, use the same one for base and updates
baseurl=<mirror url>in each section instead of mirrorlist
- Do this for each section with a mirrorlist
- Setup the initial mock environment, replace the fedora-13-i386 with the mock file edited above
mock -r fedora-13-i386 --init
mock -r fedora-13-i386 --no-clean --install pungi
Now you have a mock chroot environment setup that will use the proxy cache for packages.
Building boot images
Use the compose and pungi.ks files below, place them into /root/ in the mock to be built. Replace REPO_URL_HERE with the same repo you selected for the mock's yum.conf file.
# un-comment the applicable repo repo --name=fedora --baseurl=REPO_URL_HERE --proxy=http://proxy.home:3128 # Very small install footprint %packages @base kernel syslinux nomtools anaconda %end
#!/bin/bash echo "*** Running pungi --force --nosource --nodebuginfo --nosplitmedia -G -C -B -c /root/pungi.ks --ver=13" pungi --cachedir=/pungi/cache --force --nosource --nodebuginfo --nosplitmedia -G -C -B -c /root/pungi.ks --ver=13 echo "*** Done."
chmod a+x compose
mock -r fedora-13-i386 --chroot "/root/compose"
Change the --ver to match whichever release you are building for
Anaconda includes the ability to update itself by passing
updates=http://path/to/update.img to the kernel at boot time. This allows you to use the same boot media and test changes to stage2 of the installer.
- This assumes a working mock chroot (ie. I built boot images with this one first)
- You need a git repo of Anaconda, I branch for the build so I don't clutter up master with build by-products.
git clone git://git.fedorahosted.org/anaconda.git
cd anaconda; git checkout -b build-updates
- bind the anaconda directory to the mock being used by editing
/etc/mock/site-defaults.cfgas described above.
- NOTE: DO NOT use
mount -o bindto mount directories inside the mock. They will be obliterated the next time --init is run.
- NOTE: DO NOT use
- Install the development tools group
mock -r fedora-13-i386 --install @development-tools
- enter the chroot
mock -v -r fedora-13-i386 --shell
- grab a copy of the current anaconda*src.rpm from someplace and install the dependencies with:
- now build anaconda
- copy the updates.img over to the updates directory and optionally rename it
cp /var/lib/mock/fedora-13-i386/root/root/anaconda/updates.img /home/tftpboot/images/updates/
You can skip installing development tools and anaconda deps for subsequent iterations.
updates=http://proxy.home/updates/updates.img to the kernel parameters when booting the install media.
NOTE: By running yum inside the chroot you may mess up the rpmdb version, this depends on how close your host system is to the target system. So YMMV
Build with a test anaconda.rpm
NOTE: This doesn't actually seem to work when the released anaconda version matches that in the branch. buildinstall isn't letting the local repo override the one in the repo
Normally when a punji build is done it pulls anaconda from the repo/proxy cache. Instead you want it to use your new build (ie. when doing stage1 development which cannot be updated by updates= being passed to the kernel)
- make sure mock is mounting your anaconda directory as described above. Again, do not use
mount -o bindto do it.
mock -v -r fedora-13-i386-proxy --shell
- Removed the cached files. Otherwise it pull pull from there and not update to the latest
rm -rf /13
rm -rf /pungi/cache/local
rpmbuild -ts --nodeps anaconda...tar.gz
rpmbuild --rebuild /builddir/build/SRPMS/anaconda...src.rpm
cp /builddir/build/RPMS/anaconda...rpm /repo
repo --name=local --baseurl=file:///repo/
mock -v -r fedora-13-i386 --chroot "/root/compose"
rsync -avc /var/lib/mock/fedora-13-i386/root/13/i386/os/images/ /home/tftpboot/images/fedora/13/i386/
Boot with the pxe image and see what happens.
NOTE: The removal of the local repo cache is needed because yum gets confused by its presence.
Update boot.iso with new anaconda rpm
After you have a working boot.iso you can easily update it with the files from the new anaconda rpm you built above. Use the [| upd_bootiso] script to do this:
upd_bootiso boot.iso anaconda-13.35-1.fc13.i686.rpm
This will extract the files from initrd.img and install.img on the boot.iso, update the files and then re-build the boot.iso
This is considerably faster than using mock + pungi to compose a whole new iso from scratch.
Note, this script currently only works with x86 due to the fact that I borrowed part of it from the
mk-images.x86 script and haven't built on other architectures yet.