Talk:Build an Official ISO
- Note: Maybe obvious, generate checksums for final ISO's : --Stephdl (talk) 13:29, 3 January 2015 (CET)
it seems that anaconda does the job and create the checksum and the sha1 automatically
==> in fact this is handled by the build_iso script Unnilennium (talk) 16:23, 17 July 2016 (CEST)
- Each installer and ISO needs to built on the corresponding version (cos5 for sme8 and cos6 for sme9).
- This can be misleading. The build box can be the same, eg COS6 x64 for all ISOs, it is only the mock image that needs to match the ISO, and this is magically handled by the mock configs
For clarification read http://bugs.contribs.org/show_bug.cgi?id=7675#c37
'The corresponding version' refers to either a cos5 install or a cos5 mock env. Building packages does require the same 'corresponding version' You can't easily build sme8 packages on a cos6 box. But with mock you can because you can create a small chroot of cos5 to build the packages. We use the same trick to build the ISO. The ISO mock creates a minimal cos5 with the correct packages to build the ISO.
- Note I needed to edit mock cfg file to include /build in the chroot due to my local setup.
- These are the changes that I made as I do not have the nfs mounts on my local machine. I replaced
config_opts['plugin_conf']['mount_opts']['dirs'].append(('storage:/export/build', '/build', 'nfs', 'defaults,noatime,nodiratime,nosuid'))
config_opts['plugin_conf']['mount_opts']['dirs'].append(('storage:/mirrors', '/mirrors', 'nfs', 'defaults,noatime,nodiratime,nosuid'))
- with
config_opts['plugin_conf']['bind_mount_opts']['dirs'].append(('/build', '/build' ))
Also note http://bugs.contribs.org/show_bug.cgi?id=7675#c61
- There is also an update to /usr/lib/python2.6/site-packages/mockbuild/mounts.py that needs to happen so loop devices get mounted correctly. Check /var/lib/mock/smeserver-VERSION-ARCH/result/root.log after mock -r smeserver-VERSION-ARCH-iso --init (eg mock -r smeserver-8-i386-iso --init). The mounting of the /dev/loopX should pass (return code 0). If it fails (return code 32) then the patch below is needed on your build host.
@@ -83,6 +83,9 @@
decorate(traceLog())
def mount(self):
+ if not os.path.isdir(self.srcpath) and not os.path.isfile(self.srcpath):
+ mockbuild.util.touch(self.bindpath)
+
if not self.mounted:
cmd = ['/bin/mount', '-n',
'--bind', self.srcpath, self.bindpath ]
- For SME Server 8 check that anaconda-runtime was installed in the mock instance. For SME 8 the anaconda-runtime needs to be installed, check /usr/lib/anaconda-runtime/mk-images* exists in the mock instance after the mock --init. (check /var/lib/mock/smeserver-8-i386/root/usr/lib/anaconda-runtime)
If it does not then run the following, assuming i386 ARCH.
mock -r smeserver-8-i386-iso --cwd /build/smeserver/stage/8 --chroot /usr/bin/yum install anaconda-runtime
If you have error for lack of privileges, noticed for sme9 --Stephdl (talk) 15:29, 31 December 2014 (CET)
mock -r smeserver-8-i386-iso --cwd /build/smeserver/stage/8 --chroot '/usr/bin/sudo /usr/bin/yum install anaconda-runtime'
You can find logs of the related scripts build_ISO and build_installer
/build/smeserver/stage/8/build_ISO.i386
&
/build/smeserver/stage/8/build_installer.i386
- for sme9 modify /build/smeserver/stage/bin/build_installer --Stephdl (talk) 13:53, 31 December 2014 (CET)
L100
/build/smeserver/repo/testing/$distrel/smeextras/$distarch/ \
in
/build/smeserver/repo/$distrel/smeextras/$distarch/ \
I noticed that the Iso gets a 'beta' tag with warnings during the install process. How remove the the beta tag, add --final in the build_installer
# add --final when we have final product
PYTHONPATH=/usr/lib/anaconda/ sudo /usr/lib/anaconda-runtime/buildinstall \
--product "$distname" \
--version "${distvers/[^0-9.]*/}" \
--release "$distname" \
--brand "centos" \
--final \
--bugurl http://bugs.contribs.org/ \
--output $(pwd)/$distarch/ \
/build/smeserver/repo/$distrel/smeextras/$distarch/ \
$(pwd)/$distarch/
/bin/sed -i -e "s|packagedir =.*|packagedir = Packages|" $(pwd)/$distarch/.treeinfo
I forget the solution to the beta-nag. Either I modified the build script on the buildsys. Or I modified anaconda on the buildsys.
SME10 preparation and build_installer
first for reference
- original Red hat doc forc customisation
- how to customize centos 7
http://serverfault.com/questions/517908/how-to-create-a-custom-iso-image-in-centos
https://github.com/joyent/mi-centos-7
Foreword
Red Hat suggest to create a product.img (https://access.redhat.com/documentation/en/red-hat-enterprise-linux/7/anaconda-customization-guide/2-working-with-iso-images#sect-product-img) and to put it in the folder images at the root of the CD, however, Centos did not use this way, but rather edited directly the anaconda image inside the live image.
Also, we might want to patch Anaconda at least to handle the degraded raid 1
Hence I feel we will have to do the same to hide all Centos branding.Unnilennium (talk) 17:20, 17 July 2016 (CEST)
how to steps (WIP)
- first extract the content of Live image, and the image of Anaconda inside
cd /build/smeserver/stage/10.0.alpha1/x86_64/LiveOS/ mkdir squashfs sudo mount -r -o loop squashfs.img squashfs mkdir mysquash cp -ar squashfs mysquash sudo umount squashfs rmdir squashfs mkdir rootfs sudo mount -r -o loop mysquashfs/LiveOS/rootfs.img rootfs mkdir myrootfs cp -ar rootfs myrootfs umount rootfs rmdir rootfs
- then we have to modify what we want like usual
WORK IN PROGRESS:
- /usr/share/anaconda/pixmaps/ content (logo, side bar, top bar, etc.)
- /usr/share/anaconda/pixmaps/rnotes/en/ content (Banners for the installation progress screen)
- /usr/share/anaconda/anaconda-gtk.css (gui stylesheet)
- /run/install/product/pyanaconda/installclasses/ (for changing the product name)
- addons, we do not need for now /usr/share/anaconda/addons/
- we might want to patch anaconda and copy files where necessary (later stage)
- finally rebuild images
cd myrootfs find . | cpio -c -o | gzip -9cv > ../rootfs.img cd ../.. mv rootfs.img mysquashfs/LiveOS/ cd mysquashfs find . | cpio -c -o | gzip -9cv > ../squashfs.img