summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorManuel Traut <manut@mecka.net>2013-01-30 15:54:51 +0100
committerManuel Traut <manut@mecka.net>2013-01-30 15:54:51 +0100
commitcbc5342614b26482a9336ed35693d0a3cd42276c (patch)
treeffb1988d90eef8b2eee79bea2baed9ef71a3b5a1
parentad59b25e403b9dd9fbee29f44fd01f8655fa6479 (diff)
updte elbe-devel pres
Signed-off-by: Manuel Traut <manut@mecka.net>
-rw-r--r--distribution/elbe-devel/pres_elbe-devel_en.tex266
1 files changed, 261 insertions, 5 deletions
diff --git a/distribution/elbe-devel/pres_elbe-devel_en.tex b/distribution/elbe-devel/pres_elbe-devel_en.tex
index 44e29bb..7e3977c 100644
--- a/distribution/elbe-devel/pres_elbe-devel_en.tex
+++ b/distribution/elbe-devel/pres_elbe-devel_en.tex
@@ -162,42 +162,298 @@ ${n.et.text}
\begin{frame}
\frametitle{preseeding}
+Preseeding provides a way to set answers to questions asked during the
+installation process, without having to manually enter the answers while
+the installation is running.
\end{frame}
+\begin{frame}
+\frametitle{preseeding}
+Many pre-seeding rules are generated from the XML file with mako:
+./elbepack/mako/commmon.cfg.mako
+\end{frame}
+
+\begin{frame}[fragile]
+\frametitle{preseeding}
+Project specific preseeding rules can be added to the xml file.
+These rules are then included by ./elbepack/mako/custom-preseed.cfg.mako
+\end{frame}
+
+
\subsection{Makefile (pre-install)}
\begin{frame}
\frametitle{initrd.gz modification}
+\begin{itemize}
+\item a directory tmp-tree is created
+\item all files and scripts needed inside the installer
+ are copied to the tmp-tree
+\item ungzip the original initrd.gz
+\item use cpio to append all files of tmp-tree to the unzipped initrd image
+\item gzip the new initrd image and remove the tmp-tree
+\end{itemize}
\end{frame}
\begin{frame}
\frametitle{create buildenv.img}
+\begin{itemize}
+\item qemu-img is used to create a buildenv.img file. This file will be used as
+harddisk of the emulated virtual machine.
+\item The debian-installer will install a full featured debian on this image.
+\item After the debian-installer was active, this image can be used as a virtual
+build-environment.
+\item The target rootfilesystem is normally just a subset of this image.
+\end{itemize}
\end{frame}
-\begin{frame}
+\begin{frame}[fragile]
\frametitle{start emulator}
+\begin{itemize}
+\item the cmdline to start the emulator depends on several specifications made
+in the XML file:
+\begin{lstlisting}
+..
+ ${prj.text("buildimage/interpreter")} \
+ -M ${prj.text("buildimage/machine")} \
+ -drive file=buildenv.img,if=${hd_type},bus=1,unit=0 \
+% if prj.has("mirror/cdrom"):
+ -drive file=${prj.text("mirror/cdrom")},if=${cdrom_type},media=cdrom,bus=1,unit=1 \
+% endif
+ -kernel vmlinuz \
+ -initrd initrd-preseeded.gz \
+ -append 'root=/dev/${hd_name} debconf_priority=critical console=${prj.text("buildimage/console")} DEBIAN_FRONTEND=newt' \
+ -no-reboot \
+ -net nic,vlan=1,model=${prj.text("buildimage/NIC/model")},macaddr="${prj.text('buildimage/NIC/MAC')}" \
+ -net user,vlan=1 \
+ -m $(MEMSIZE) \
+ -usb && reset
+..
+\end{lstlisting}
+\end{itemize}
\end{frame}
\subsection{debian-installer in emulator}
\begin{frame}
-\frametitle{preseeding}
+\frametitle{an ordinary debian installation}
+runs inside the virtual machine:
+\begin{itemize}
+\item the buildenv.img will be partitionated and formated
+\item the root partition will be mounted at /target of the debian-installer rfs
+\item a minimal rootfilesystem will be installed to /target
+\item a chroot /target will be executed
+\item all packages will be installed and configured
+\item the /target chroot will be left
+\item the hook d-i preseed/late\_command string /post-inst.sh will be executed
+\end{itemize}
\end{frame}
+
\begin{frame}
-\frametitle{post install}
-cp-scipts-into-buildenv.sh
-changeroot-into-buildenv.sh
+\frametitle{post-inst.sh}
+\begin{description}
+\item [cp-scipts-into-buildenv.sh] copy all (generated) scripts
+
+from the initrd (/)
+
+to the buildenv.img (/target/opt/elbe)
+
+\item [changeroot-into-buildenv.sh] chroot into /target again,
+
+trigger target (/opt/elbe/create-target-rfs.sh)
+
+and cdrom (/opt/elbe/mkcdrom.sh) generation.
+\end{description}
\end{frame}
\begin{frame}
\frametitle{target generation}
+\begin{itemize}
+\item generate file and pkg lists
+\item create /target tree
+\item call dump.py to
+\begin{itemize}
+ \item validate packages / write logfile
+ \item add fullpkgs list to source.xml
+ \item add content of /etc/apt/sources.list to source.xml
+ \item add content of /etc/apt/preferences to source.xml
+ \item modify /target tree with finetuning.sh
+\end{itemize}
+\item generate licence information file
+\item call part-target.sh to copy /target tree to (different) images
+\item (optional) generate cpio images and tarballs
+\end{itemize}
+\end{frame}
+
+
+\begin{frame}[fragile]
+\frametitle{create /target tree}
+\begin{itemize}
+\item depending on the elbe mode, a filelist is generated. e.g. in normal mode:
+\begin{lstlisting}
+ls -A1 / | \
+ grep -v target | grep -v proc | grep -v sys | \
+ xargs find >> /opt/elbe/filelist
+\end{lstlisting}
+\item then all files specified to be stored on the target rfs are copied:
+\begin{lstlisting}
+rsync -a --files-from=/opt/elbe/filelist / /target
+\end{lstlisting}
+\end{itemize}
+\end{frame}
+
+
+\begin{frame}[fragile]
+\frametitle{dump.py - check if all req. packages are installed}
+\begin{itemize}
+\item add lines about missing packages to validation.txt:
+\begin{lstlisting}
+ for name in [p.et.text for p in pkgs] + [kinitrd]:
+
+ if not name in cache:
+ elog.printo( "- package %s does not exist" % name )
+ errors += 1
+ continue
+
+ cp = cache[name]
+
+ if not cp.installed and name != kinitrd:
+ elog.printo( "- package %s is not installed" % name )
+ errors += 1
+ continue
+\end{lstlisting}
+\end{itemize}
+\end{frame}
+
+
+\begin{frame}[fragile]
+\frametitle{dump.py - check version of packages used}
+(only done if a fullpkgs tag was specified in the xml file)
+\begin{itemize}
+\item add lines about packages with wrong version to validation.txt:
+\begin{lstlisting}
+ for p in fullpkgs:
+ name = p.et.text
+ ver = p.et.get('version')
+ md5 = p.et.get('md5')
+ pindex[name] = p
+ ...
+ if cpi.version != ver:
+ elog.printo("pack %s v%s != installed v%s" % (name, ver, cpi.version))
+ errors += 1
+ continue
+
+ if cpi.md5 != md5:
+ elog.printo("pack %s md5 %s != installed md5 %s" % (name, md5, cpi.md5) )
+ errors += 1
+ ...
+\end{lstlisting}
+\item there is also a check for packages that are installed but wasn't specified to be installed
+\end{itemize}
+\end{frame}
+
+
+\begin{frame}[fragile]
+\frametitle{dump.py - write fullpkglist to source.xml}
+\begin{itemize}
+\item all used packages are mentioned in this list (including version and md5sum):
+\begin{lstlisting}
+ paktree = xml.ensure_child( 'fullpkgs' )
+ paktree.clear()
+ pkgs = []
+ for p in cache:
+ if p.is_installed:
+ pkgs.append( (p.name, p.installed.version, p.is_auto_installed, p.installed.md5))
+ ...
+ for p in pkgs:
+ append_pkg_elem( paktree, p[0], p[1], p[2], p[3] )
+\end{lstlisting}
+\end{itemize}
+\end{frame}
+
+
+\begin{frame}
+\frametitle{dump.py - modify /target tree with finetuning.sh}
+\begin{itemize}
+\item the script is executed while cwd is /target.
+
+ So files can be copied
+
+ from the debian rfs to the target rfs
+
+ by e.g. 'cp /etc/passwd etc/'
+
+\item the output of the finetuning.sh commands is appended to elbe-report.txt
+\end{itemize}
+\end{frame}
+
+
+\begin{frame}
+\frametitle{dump.py - filelist generation}
+elbe-report.txt includes a filelist that indicates each file in the target rfs
+and its origin
+\begin{itemize}
+\item a time stamp is recorded before and after finetuning. Files that show up
+ with a modification time in that period show up as modified/created by
+ finetuning.sh
+\end{itemize}
+\end{frame}
+
+
+\begin{frame}[fragile]
+\frametitle{generate licence information file}
+all licence informations that are stored in /usr/share/* are collected in one file:
+\begin{lstlisting}
+find /usr/share/doc -name copyright -exec \
+ /opt/elbe/print_licence.sh {} \; >> /opt/elbe/licence.txt
+\end{lstlisting}
\end{frame}
+
+\begin{frame}[fragile]
+\frametitle{call part-target.sh to copy /target tree to (different) images}
+currently only UBI image support is functional.
+
+HD images are under development. They will be created by using python bindings
+of libparted and loopback mounts.
+\end{frame}
+
+
+\begin{frame}[fragile]
+\frametitle{build ubifs images}
+\begin{itemize}
+\item mkfs.ubifs -r is used to generate a ubifs image from a subdirectory
+\item the name of the images is defined by the label in the fstab tag.
+\item the image defined first in the fstab is created first
+\item the files copied to an image are moved temporarily away from /target:
+\begin{lstlisting}
+ /mountA/mountB # mountA shouldn't include files like mountB/test
+\end{lstlisting}
+\item /target is restored as all images were created
+\end{itemize}
+\end{frame}
+
+
+\begin{frame}[fragile]
+\frametitle{(optional) generate cpio images and tarballs}
+\begin{lstlisting}
+% if xml.has("target/package/tar"):
+tar cf /opt/elbe/target.tar -C /target .
+% endif
+
+% if xml.has("target/package/cpio"):
+cd /target
+find . -print | cpio -ov -H newc >/opt/elbe/target.cpio
+% endif
+\end{lstlisting}
+\end{frame}
+
+
\begin{frame}
\frametitle{cdrom generation}
\end{frame}
+
\subsection{Makefile (post-install)}
\begin{frame}