This patch against kboot-10 contains a detailed description of the kboot_sl system loader add-on. The documentation is written with lyx and comes with a Makefile that creates a pdf-file if lyx and pdflatex are installed. It can be found in a new and extra doc directory below the kboot-10 main directory. Note that this is the main and reference documentation of the system loader! best regards Michael vvv the patch starts below vvv diff -Nuar kboot-10/doc/description.lyx kboot-10_patch1_doc/doc/description.lyx --- kboot-10/doc/description.lyx 1970-01-01 01:00:00.000000000 +0100 +++ kboot-10_patch1_doc/doc/description.lyx 2006-06-21 14:58:30.000000000 +0200 @@ -0,0 +1,3695 @@ +#LyX 1.4.1 created this file. For more info see http://www.lyx.org/ +\lyxformat 245 +\begin_document +\begin_header +\textclass article +\begin_preamble +\usepackage{a4wide} +\usepackage[pdftex]{hyperref} +\end_preamble +\language english +\inputencoding auto +\fontscheme pslatex +\graphics default +\paperfontsize default +\spacing single +\papersize default +\use_geometry false +\use_amsmath 1 +\cite_engine basic +\use_bibtopic false +\paperorientation portrait +\secnumdepth 3 +\tocdepth 3 +\paragraph_separation skip +\defskip medskip +\quotes_language english +\papercolumns 1 +\papersides 1 +\paperpagestyle default +\tracking_changes false +\output_changes true +\end_header + +\begin_body + +\begin_layout Title + +\family typewriter +kboot_sl +\family default + Linux System Loader Description +\end_layout + +\begin_layout Author +Michael Löhr and Swen Schillig +\end_layout + +\begin_layout Date +$Id: specs.lyx,v 1.21 2006/06/21 11:41:27 loehr Exp $ +\end_layout + +\begin_layout Standard + +\newpage + +\begin_inset LatexCommand \tableofcontents{} + +\end_inset + + +\newpage + +\end_layout + +\begin_layout Standard +\begin_inset ERT +status collapsed + +\begin_layout Standard + + +\backslash +sloppy +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Section +Overview +\end_layout + +\begin_layout Standard +This document describes the installation and configuration of the system + loader. + All features and options of the system loader configuration are explained + in detail. + In addition, the usage of the user interface is outlined and example configurat +ions are provided in the appendix. +\end_layout + +\begin_layout Section +Description +\end_layout + +\begin_layout Standard +As an extension of the +\family typewriter +kboot +\family default + project by Werner Almesberger ( +\begin_inset LatexCommand \htmlurl[kboot homepage]{http://kboot.sourceforge.net/} + +\end_inset + +) the system loader runs in a minimal Linux environment started by a platform + specific first stage boot loader. + At the start a configuration file is read, the setup is performed according + to the configuration data and finally the boot selection menu is displayed. + Based on the users selection, a boot configuration is loaded and the system + is reinitialized via the +\family typewriter +kexec +\family default + system call. + As the result the minimal Linux system is replaced by the system selected + in the boot configuration. +\end_layout + +\begin_layout Standard +Up to this level of description +\family typewriter +kboot +\family default + and +\family typewriter +kboot_sl +\family default +, as the system loader extension will be called in the following text, offer + similar functionality. + From a more detailed view +\family typewriter +kboot_sl +\family default + has been optimized for a different goal than the original +\family typewriter +kboot +\family default + environment. + The original +\family typewriter +kboot +\family default + tries to provide a compact and minimal Linux boot system that will be built + and customized for the target machine and application. + +\family typewriter +kboot_sl +\family default + tries to offer a more generic and feature rich Linux boot environment that + can be provided in a ready to use form, e.g. + as a rpm-package but gives up the goal to provide a very small boot environment. +\begin_inset Foot +status collapsed + +\begin_layout Standard +Dennis Merbach was so friendly to host our collected Linux system loader + patches at +\begin_inset LatexCommand \htmlurl{http://www.merbach.net/kboot_sl/} + +\end_inset + +. + Future additions and extensions may also appear on this site. +\end_layout + +\end_inset + + +\end_layout + +\begin_layout Standard + +\family typewriter +kboot_sl +\family default + can be seen in the following ways: +\end_layout + +\begin_layout Enumerate + +\emph on +As a comfortable boot loader for systems that offer only a frugal first + stage boot loader: +\end_layout + +\begin_deeper +\begin_layout Standard +From this point of view +\family typewriter +kboot_sl +\family default + solves the problem that some boot loaders have to be reinitialized whenever + a component of the boot configuration changes. + Examples for this type of boot loaders are +\family typewriter +lilo +\family default + on the i386 platform or +\family typewriter +zipl +\family default + on the s390 platform. + With +\family typewriter +kboot_sl +\family default + these boot loaders will be initialized only once to start +\family typewriter +kboot_sl +\family default +. + Any further changes to the boot configuration will be handled dynamically + by +\family typewriter +kboot_sl +\family default +. + A potentially uncomfortable boot menu like in the case of the +\family typewriter +zipl +\family default + boot loader is replaced by the more convenient boot selection menu of +\family typewriter +kboot_sl +\family default +. +\end_layout + +\end_deeper +\begin_layout Enumerate + +\emph on +As a boot loader that can be controlled from remote via the network: +\end_layout + +\begin_deeper +\begin_layout Standard +Usual boot managers offer their boot seletion menu on the local console + of the system to be booted. + Therefore it is necessary to walk to the machine or to connect with a special + terminal software if anything different than the default configuration + has to be booted. + With +\family typewriter +kboot_sl +\family default + a standard ssh interface allows remote connections while a system is still + in its boot phase. +\end_layout + +\end_deeper +\begin_layout Enumerate + +\emph on +As a boot loader that supports boot configurations to be centralized and + managed on the network: +\end_layout + +\begin_deeper +\begin_layout Standard +Typical boot loaders have to be configured locally on the system to be booted. + If kernel parameters or the kernel itself have to be changed on several + systems an administrator has to login to all systems in order to change + the settings or install the kernel. + +\family typewriter +kboot_sl +\family default +'s ability to access remote files through a network connection together + with a mechanism that can handle system specific configurations is the + basis to consolidate the boot configuration for several systems. + Boot parameters, kernels, ramdisks, etc. + can be provided by a centralized boot server. + Especially in virtualization or cluster environments with many similar + systems this allows to manage and change boot configurations very efficiently. + The approach helps also to distribute new kernel versions with important + bug fixes fast and keeps all systems booting from the same boot server + in a consistent state. +\end_layout + +\end_deeper +\begin_layout Enumerate + +\emph on +As a rescue system that is always available in the boot sequence: +\end_layout + +\begin_deeper +\begin_layout Standard +If the boot of a Linux system fails, a Linux rescue system that allows to + fix the problem is quite useful. + On a system that uses +\family typewriter +kboot_sl +\family default + as its boot manager there is already a rescue system installed. + From the shell environment of +\family typewriter +kboot_sl +\family default + the problem that prevents the system from booting can be analyzed and fixed. + As soon as the problem is solved the system can be booted into normal operation + again. + Special tools and requirements for a customized rescue system can be easily + integrated into the +\family typewriter +kboot_sl +\family default + ramdisk via the +\family typewriter +kboot_admin +\family default + tool. +\end_layout + +\end_deeper +\begin_layout Section +Building system loader executables +\end_layout + +\begin_layout Standard +In most cases the end user of the system loader +\family typewriter +kboot_sl +\family default + will use prebuilt components and has therefore no need to build the system + loader from scratch. + If it is necessary to rebuild the system loader components there are three + possibilities. +\end_layout + +\begin_layout Subsection +The +\family typewriter +kboot +\family default + Build Environment +\end_layout + +\begin_layout Standard +The system loader is an extension to +\family typewriter +kboot +\family default + and therefore integrated into the +\family typewriter +kboot +\family default + build environment. + As a result the execution of the +\family typewriter +make +\family default + command downloads and compiles all components required by +\family typewriter +kboot +\family default + and the system loader extension. + Finally, +\family typewriter +make +\family default + creates a system loader kernel and a ramdisk. + This ramdisk contains the kboot base environment and all system loader + add-ons, which are detailed out further down in this document. + Additional information about the build environment can be found in the + original +\family typewriter +kboot +\family default + documentation by Werner Almesberger. +\end_layout + +\begin_layout Subsection +RPM Package Build +\end_layout + +\begin_layout Standard +This build option is only available on RPM based Linux distributions. + Executing +\family typewriter +make redhat-rpm +\family default + in the +\family typewriter +kboot +\family default + top level directory will first execute +\family typewriter +make +\family default + in the +\family typewriter +kboot +\family default + build environment and finally create source and binary RPM packages of + the system loader. + +\end_layout + +\begin_layout Subsection +System Loader Standalone Build +\end_layout + +\begin_layout Standard +It is possible to build the system loader as a stand-alone application without + the +\family typewriter +kboot +\family default + kernel and ramdisk environment. + Executing +\family typewriter +make install +\family default + in the sub-directory +\family typewriter +kboot/ui +\family default + is creating a stand-alone version of the system loader. + This version can be used for debugging or to initiate a fast menu controlled + reboot of the system. + To ensure that the system loader will find all its components the environmant + variable +\family typewriter +KBOOT_PATH +\family default + has to be set similar to the following example: +\end_layout + +\begin_layout LyX-Code + +\size scriptsize +export KBOOT_PATH=/root/systemloader/kboot/ui/usr/kboot +\end_layout + +\begin_layout LyX-Code + +\size scriptsize +/root/systemloader/kboot/ui/usr/kboot/kboot -u linemode file:///boot/kboot.conf + +\end_layout + +\begin_layout Section +Installation +\end_layout + +\begin_layout Standard +There are two ways to install the system loader, automatically via a RPM-package + (on supported systems only) or manually by copying the system loader kernel + and ramdisk to the +\family typewriter +/boot +\family default + directory. + In both cases the system loader is not activated automatically. +\end_layout + +\begin_layout Standard +Instead of using the kernel provided with the +\family typewriter +kboot +\family default + package it is also possible to use any other kernel available on the system. + However, the kernel must be at least version 2.6.13 and the kexec system + call has to be supported. + In the simplest scenario all required drivers (e.g. + disk or network drivers) are compiled into the kernel. + For more flexibility the +\family typewriter +kboot_admin +\family default + tool (see section +\begin_inset LatexCommand \ref{sec:The-kboot_admin-Tool} + +\end_inset + +) allows to create and modify customized system loader ramdisks with module + support. + Kernels and ramdisks are different for 31/32-bit and 64-bit systems and + must not be mixed. +\end_layout + +\begin_layout Standard +To enable the system loader it has to be configured as a boot entry of the + first stage boot loader. + On Intel +\family typewriter +lilo +\family default + or +\family typewriter +grub +\family default + can be used, on s390/System z the system loader can be booted from the + reader or use +\family typewriter +zipl +\family default + as the first stage loader. + Any minimal first stage loader is sufficient because the system loader + will handle the boot selection menu and user interaction. +\end_layout + +\begin_layout Standard +Before the system loader can be used, an appropriate configuration file + has to be created. + A detailed description of all elements of the system loader configuration + file is given in section +\begin_inset LatexCommand \ref{sec:Elements-of-the} + +\end_inset + +. + Example configuration files can be found in sections +\begin_inset LatexCommand \ref{i386conf} + +\end_inset + + and +\begin_inset LatexCommand \ref{sub:kboot.conf-for-s390} + +\end_inset + +. + When the system loader configuration file is available the system loader + kernel and initrd can be booted via the first stage boot loader. + Sections +\begin_inset LatexCommand \ref{sub:menu.lst-for-grub} + +\end_inset + + and +\begin_inset LatexCommand \ref{sub:zipl.conf} + +\end_inset + + show example configurations for +\family typewriter +grub +\family default + and +\family typewriter +zipl +\family default +. +\end_layout + +\begin_layout Standard + +\family typewriter +kboot_sl +\family default + will be started if the kernel command line contains the additional parameter + +\family typewriter +kboot +\family default + that specifies the location of the configuration file. + Otherwise the Werner Almesberger variant of the +\family typewriter +kboot +\family default + environment will be started without the system loader extension. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +kboot=dasd://(0.0.5c5e,1)/boot/kboot.conf +\end_layout + +\begin_layout Section +Boot Methods +\end_layout + +\begin_layout Standard +Depending on the hardware platform and the available disk types the system + loader supports several boot methods. + On the i386 and s390 platform the system can be booted from a kernel image + file. + An initial ramdisk and a kernel command line or parmfile can be specified + together with this kernel file. + On the s390 platform +\family typewriter +*.ins +\family default + files or the boot map information written by +\family typewriter +zipl +\family default + can be used in addition. +\end_layout + +\begin_layout Standard +In any case the location of kernel, ramdisk, parmfile, insfile or boot map + will be defined as an URI. + Which URI scheme has to be used depends on the system platform and available + disk. + The +\family typewriter +block +\family default + URI is typically used on the i386 platform. + The +\family typewriter +dasd +\family default + and +\family typewriter +zfcp +\family default + URI schemes are specific for the s390 platform. + On every platform the +\family typewriter +ftp +\family default + , +\family typewriter +http +\family default + and +\family typewriter +scp +\family default + URI schemes can be used to boot from the network. +\end_layout + +\begin_layout Standard +All boot methods and URI schemes will be described in detail in the following + chapter. +\end_layout + +\begin_layout Section +Elements of the Config File +\end_layout + +\begin_layout Standard +\begin_inset LatexCommand \label{sec:Elements-of-the} + +\end_inset + +The config file for +\family typewriter +kboot_sl +\family default + consists of some global definitions which are followed by one or more boot + entries. + External files are always referenced by an URI. + A detailed description of supported URIs will be given in section +\begin_inset LatexCommand \ref{sub:URIs} + +\end_inset + +. +\end_layout + +\begin_layout Subsection +Global Definitions +\end_layout + +\begin_layout Standard +Preceding the boot entries the system loader configuration file contains + a number of definitions that are valid for the whole configuration file. +\end_layout + +\begin_layout Subsubsection +Comments +\end_layout + +\begin_layout Standard +Comments are allowed in the global definitions part of the configuration + file and in the boot entries. + A comment starts with +\family typewriter +# +\family default + and ends at the end of the line. + Tabs or spaces in front of the # are possible but comments at the end of + a line that contains a definition are not allowed. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +# this is a comment +\end_layout + +\begin_layout LyX-Code + # this is also a comment +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + # this is not allowed! +\end_layout + +\begin_layout Subsubsection + +\family typewriter +default +\begin_inset LatexCommand \label{sub:default} + +\end_inset + + +\end_layout + +\begin_layout Standard +The +\family typewriter +default +\family default + statement references the boot entry that will be selected automatically + after the timeout. + Valid references are the label of a boot entry or a number. + Implicit numbering of the boot entries starts with 0. + If the default statement is not used, entry number 0 will be used as the + default. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +default linux2 +\end_layout + +\begin_layout LyX-Code +default 1 +\end_layout + +\begin_layout Subsubsection + +\family typewriter +timeout +\end_layout + +\begin_layout Standard +The +\family typewriter +timeout +\family default + statement specifies the time in seconds until the default boot entry will + be started automatically. + If the statement is not used or the timeout is set to 0 no timeout will + occur. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +timeout 15 +\end_layout + +\begin_layout Subsubsection + +\family typewriter +password +\begin_inset LatexCommand \label{sub:password} + +\end_inset + + +\end_layout + +\begin_layout Standard +The +\family typewriter +password +\family default + statement defines the password that has to be entered if a locked boot + entry (see section +\begin_inset LatexCommand \ref{sub:lock} + +\end_inset + +) has been selected. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +password topsecret +\end_layout + +\begin_layout Subsubsection + +\family typewriter +userinterface +\end_layout + +\begin_layout Standard +The +\family typewriter +userinterface +\family default + statement specifies which userinterface module should be started to display + the boot selection menu. + For every userinterface command a userinterface process will be started. + This allows to start several instances of the same userinterface module + listening on different input devices or ports. + Additional options may be specified depending on the user interface module. + Currently +\family typewriter +linemode +\family default + and ssh are available as user interface modules. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code +userinterface [MODULE_OPTIONS] +\end_layout + +\begin_layout Subsubsection + +\family typewriter +userinterface linemode +\end_layout + +\begin_layout Standard +For the linemode interface it is required to specify the device on which + the boot selection menu will be displayed. + Typical values for the device parameter are +\family typewriter +/dev/console +\family default + , +\family typewriter +/dev/tty +\family default + or +\family typewriter +/dev/tty1 +\family default + . +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code +userinterface linemode +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +userinterface linemode /dev/tty1 +\end_layout + +\begin_layout Subsubsection + +\family typewriter +userinterface ssh +\end_layout + +\begin_layout Standard +The +\family typewriter +userinterface ssh +\family default + statement will start a process that is listening for incoming ssh connections + in the background. + For every incoming connection that is successfully established a new user + interface instance will be started. + The type of interface to be started has to be specified as the first module + option. + Currently only linemode can be specified here but for the future additional + user interface types (e.g. + ncurses) may become available. + Additional module options may be used to specify the port on which the + ssh connection can be established and to load RSA or DSS keys from a location + defined by an URI scheme. +\end_layout + +\begin_layout Standard +Connecting to the system loader via ssh will require a userid and password. + During the creation of the system loader ramdisk a user kboot with password + kboot will be created automatically. + The tool +\family typewriter +kboot_admin +\family default + allows to change the password on an existing ramdisk. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code + +\size scriptsize +userinterface ssh [port=] [rsa_key=] + [dss_key=] +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +userinterface ssh linemode port=2222 +\end_layout + +\begin_layout Subsubsection + +\family typewriter +include +\end_layout + +\begin_layout Standard +The +\family typewriter +include +\family default + statement can be used anywhere in the system loader configuration file. + The content of the file referenced by the URI will be included at the position + of the +\family typewriter +include +\family default + statement. + Nested includes are allowed but limited to twenty levels. + +\family typewriter +include +\family default + statements that appear inside an inactive system section will not be applied. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code +include URI +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +include dasd://(0.0.5c5e,1)/boot/extra_menu.conf +\end_layout + +\begin_layout Subsection +Setup Commands +\end_layout + +\begin_layout Standard +This group of commands allows to setup additional devices in the minimal + Linux environment of the system loader. + It is possible to load additional kernel modules, to specify network settings + and to enable devices that are not enabled automatically. + Each +\family typewriter +setup +\family default + command is executed immediately. + As parameters are identified by keywords they are not required to appear + in any particular order. + An additional short form allows to use +\family typewriter +setup +\family default + commands on the kernel command line. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code +setup { } +\end_layout + +\begin_layout Subsubsection + +\family typewriter +setup module +\end_layout + +\begin_layout Standard +The +\family typewriter +setup module +\family default + command allows to load additional kernel modules. + Module dependencies are resolved automatically. + The module to be loaded has to be present on the system loader ramdisk. + Modules can be added to an existing ramdisk via the kboot_admin tool. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code +setup module { +\end_layout + +\begin_layout LyX-Code + name +\end_layout + +\begin_layout LyX-Code + param +\end_layout + +\begin_layout LyX-Code + kernelversion +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Standard +Short form: +\end_layout + +\begin_layout LyX-Code +mod([,[,]] +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +setup module { +\end_layout + +\begin_layout LyX-Code + name qeth +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Subsubsection + +\family typewriter +setup network +\end_layout + +\begin_layout Standard +The +\family typewriter +setup network +\family default + command allows to specify network settings and to initialize a network + device with these settings. + Static setup and dhcp are supported. + Parameters for static network setup can also be used in dhcp mode and are + used as fallback if dhcp fails. + A correct network setup is required to use network based URI schemes like + ftp, http and scp. + A +\family typewriter +setup module +\family default + command may be required to load the network device driver before the +\family typewriter +setup network +\family default + command can be executed successfully. + The +\family typewriter +kboot_admin +\family default + tool can be used to copy the required driver modules into the ramdisk of + the system loader. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code +setup network { +\end_layout + +\begin_layout LyX-Code + interface +\end_layout + +\begin_layout LyX-Code + mode +\end_layout + +\begin_layout LyX-Code + address
+\end_layout + +\begin_layout LyX-Code + mask +\end_layout + +\begin_layout LyX-Code + gateway +\end_layout + +\begin_layout LyX-Code + nameserver +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Standard +Short form: +\end_layout + +\begin_layout LyX-Code +static([,
[,[,[,]]]] +\end_layout + +\begin_layout LyX-Code + dhcp([,
[,[,[,]]]] +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +setup network { +\end_layout + +\begin_layout LyX-Code + interface eth0 +\end_layout + +\begin_layout LyX-Code + mode dhcp +\end_layout + +\begin_layout LyX-Code + address 9.155.23.65 +\end_layout + +\begin_layout LyX-Code + mask 255.255.255.128 +\end_layout + +\begin_layout LyX-Code + gateway 9.155.23.1 +\end_layout + +\begin_layout LyX-Code + nameserver 9.64.163.21 +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Subsubsection + +\family typewriter +setup qeth +\end_layout + +\begin_layout Standard +On the s390 platform the +\family typewriter +setup qeth +\family default + command can be used to enable a qeth ethernet device with the given busids. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code +setup qeth { +\end_layout + +\begin_layout LyX-Code + busid +\end_layout + +\begin_layout LyX-Code + busid +\end_layout + +\begin_layout LyX-Code + busid +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Standard +Short form: +\end_layout + +\begin_layout LyX-Code +qeth(,,) +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +setup qeth { +\end_layout + +\begin_layout LyX-Code + busid 0.0.f5de +\end_layout + +\begin_layout LyX-Code + busid 0.0.f5df +\end_layout + +\begin_layout LyX-Code + busid 0.0.f5e0 +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Subsubsection + +\family typewriter +setup dasd +\end_layout + +\begin_layout Standard +On the s390 platform the +\family typewriter +setup dasd +\family default + command can be used to enable a dasd disk device with the given busid. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code +setup dasd { +\end_layout + +\begin_layout LyX-Code + busid +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Standard +Short form: +\end_layout + +\begin_layout LyX-Code +dasd() +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +setup dasd { +\end_layout + +\begin_layout LyX-Code + busid 0.0.5c60 +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Subsubsection + +\family typewriter +setup zfcp +\end_layout + +\begin_layout Standard +On the s390 platform the +\family typewriter +setup zfcp +\family default + command can be used to enable a zfcp disk device. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code +setup zfcp { +\end_layout + +\begin_layout LyX-Code + busid +\end_layout + +\begin_layout LyX-Code + wwpn +\end_layout + +\begin_layout LyX-Code + lun +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Standard +Short form: +\end_layout + +\begin_layout LyX-Code +zfcp(,,) +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +setup zfcp { +\end_layout + +\begin_layout LyX-Code + busid 0.0.54ae +\end_layout + +\begin_layout LyX-Code + wwpn 0x5005076300cb93cb +\end_layout + +\begin_layout LyX-Code + lun 0x512e000000000000 +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Subsection +System Dependent Sections +\end_layout + +\begin_layout Standard +Based on the network capabilities of the system loader it is possible to + provide kernels, ramdisks and kernel parameters on a centralized bootserver. + System dependent sections in the system loader configuration file provide + a mechanism that is especially useful for shared system loader configuration + files. + A system dependent section starts with a test, that determines if the configura +tion part is active on a specific system. + Depending on the result of this test the following section is used or ignored. + The identification of the system can be done via the MAC address of a network + adapter, the UUID of the system, the name of the virtual machine or the + name of the logical partition of the host system. + A system dependent section is active if at least one of the system identifiers + matches. + If a system identifier is not available on the specific system it will + never match. + System dependent sections can be nested in order to specify settings that + are common to a number of systems and to be able to change only some details + for the specific system. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code +system { +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Standard +Examples: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +system mac(00:10:C6:DE:12:6C) +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + uuid(C7CCA781-2DD5-11C6-93BC-AD439DC0988B) +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +{ +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + root block://(/dev/hda5,ext3)/boot/ +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +} +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +system not(vmguest(linux41)) { +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + include ftp://kboot:kboot@53v15g41.ibm.com/boot/standard_entries.conf +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +} +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +system vmguest(linux40,g53lp15) +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + vmguest(linux41,g53lp15) +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +{ +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + setup network { +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + mode static +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + vmguest(linux40) { +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + address 9.152.26.120 +\end_layout + +\begin_layout LyX-Code + } +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + vmguest(linux41) { +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + address 9.152.26.121 +\end_layout + +\begin_layout LyX-Code + } +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + mask 255.255.252.0 +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + gateway 9.152.24.1 +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + nameserver 9.152.120.241 +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + interface eth0 +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + } +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +} +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout Subsubsection + +\family typewriter +mac +\end_layout + +\begin_layout Standard +The mac systemidentifier can be used on nearly every system that has a network + adapter. + The mac statement matches if the system has a network adapter with this + mac address. + It may be necessary to load a kernel module and to enable the network device + before the MAC of the system can be determined. + Therefore it is not the preferred method to identify a system via its mac. + Nevertheless it is the only available method for older machines on the + i386 platform. +\end_layout + +\begin_layout Subsubsection + +\family typewriter +uuid +\end_layout + +\begin_layout Standard +On the i386 platform recent BIOS versions provide a UUID that allows to + identify the specific system unambiguously. + The +\family typewriter +uuid +\family default + command matches when the given UUID matches the UUID of the system. + If available this is the preferred method to identify a specific system + on the i386 platform. +\end_layout + +\begin_layout Subsubsection + +\family typewriter +lpar +\end_layout + +\begin_layout Standard +The concept of logical partitions allows to split the hardware of a computer + system into several independent parts. + Each part or logical partition can boot its own operating system. + The +\family typewriter +lpar +\family default + system identifier allows to identify the logical partition on which the + system loader configuration file is currently used and matches when the + given name matches the name of the current logical partition. + In the system loader it is implemented for the s390 platform. + In the future it could be extended to other platforms that offer logical + partitions. +\end_layout + +\begin_layout Subsubsection + +\family typewriter +vmguest +\end_layout + +\begin_layout Standard +The concept of virtual machines is an approach that allows to run several + instances of operating systems under the control of a virtualization software. + The +\family typewriter +vmguest +\family default + system identifier allows to identify the virtual machine on which a system + loader configuration file is currently used. + It matches when the given name matches the name of the virtual machine. + An extended form allows to specify the name of a logical partition in addition + and matches when the name of the virtual machine and the name of the logical + partition are identical to the given parameter values. + The +\family typewriter +vmguest +\family default + system identifier is implemented for VM on the the s390 platform. + In the future it could be extended to other environments that offer virtual + machines. +\end_layout + +\begin_layout Subsection +Boot Entry Definitions +\end_layout + +\begin_layout Standard +The global definitions are followed by a section of boot entries which describe + the available boot configurations. + A boot entry starts with the line +\end_layout + +\begin_layout LyX-Code +boot_entry { +\end_layout + +\begin_layout Standard +and ends with a closing bracket +\end_layout + +\begin_layout LyX-Code +} +\end_layout + +\begin_layout Standard +Every boot entry must contain exactly one statement that triggers a boot + action. + These boot action statements are +\family typewriter +kernel +\family default +, +\family typewriter +insfile +\family default +, +\family typewriter +bootmap +\family default +, +\family typewriter +halt +\family default +, +\family typewriter +reboot +\family default + and +\family typewriter +shell +\family default +. + Other statements can be used optionally. + Some of them will specify labels or variables to improve the handling of + the configuration file, some will influence the behaviour of the boot menu + and some will pass additional information to the booted system. + All possible statements inside the boot entry are described in the following + sections. +\end_layout + +\begin_layout Subsubsection + +\family typewriter +title +\end_layout + +\begin_layout Standard +The +\family typewriter +title +\family default + statement defines a text that will be displayed in the boot selection menu + and should give some meaningful description of the boot configuration. + This statement is mandatory for all boot entries. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +title Debian GNU/Linux, latest kernel +\end_layout + +\begin_layout Subsubsection + +\family typewriter +label +\end_layout + +\begin_layout Standard +The +\family typewriter +label +\family default + statement allows to assign a symbolic label to a boot entry. + This label can be used in the default statement to reference the default + boot entry (see section +\begin_inset LatexCommand \ref{sub:default} + +\end_inset + +). + If no label definition is present the boot entry can still be referenced + numerically by its position in the configuration file. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +label linux3 +\end_layout + +\begin_layout Subsubsection + +\family typewriter +root +\end_layout + +\begin_layout Standard +The +\family typewriter +root +\family default + statement defines an URI path prefix and will be prepended to all URIs +\begin_inset Foot +status collapsed + +\begin_layout Standard +The root definition will not be applied to +\family typewriter +bootmap +\family default + URIs because a path definition makes no sense for a structure that is not + part of any filesystem. +\end_layout + +\end_inset + + specified in the same boot entry. + Typically it is used to specify a common path for kernel, initrd and parmfile. + Note that the path prefix and the rest of the URI will be concatenated + as they are specified. + There is no automatic insertion of a +\family typewriter +'/' +\family default + character and no syntax checking. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +root dasd://(0.0.5c5e,1)/boot/ +\end_layout + +\begin_layout Subsubsection + +\family typewriter +kernel +\end_layout + +\begin_layout Standard +The +\family typewriter +kernel +\family default + statement specifies the kernel file that will be booted if this boot entry + is selected. + All supported URI formats are allowed to specify the location of the kernel + file. + If a root statement is given in the same boot entry, it will be prepended + to the specified kernel path. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +kernel vmlinuz +\end_layout + +\begin_layout Subsubsection + +\family typewriter +initrd +\end_layout + +\begin_layout Standard +The +\family typewriter +initrd +\family default + statement specifies the initial ramdisk that will be used if this boot + entry is selected. + All supported URI formats are allowed to specify the location of the ramdisk + file. + If a root statement is given in the same boot entry, it will be prepended + to the specified ramdisk path. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +initrd initrd.img +\end_layout + +\begin_layout Subsubsection + +\family typewriter +cmdline +\end_layout + +\begin_layout Standard +The cmdline statement specifies the kernel commandline that is used to start + the kernel if this boot entry is selected. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +cmdline ro root=/dev/ram0 ramdisk_size=100000 +\end_layout + +\begin_layout Subsubsection + +\family typewriter +parmfile +\end_layout + +\begin_layout Standard +As an alternative to the cmdline statement the +\family typewriter +parmfile +\family default + statement can be used to specify the file that will be used as the kernel + command line if this boot entry is selected. + All supported URI formats are allowed to specify the location of the parmfile. + If a root statement is given in the same boot entry, it will be prepended + to the specified parmfile path. + If parmfile and cmdline are specified at the same time they will be concatenate +d as +\family typewriter +parmfile +\family default ++ +\family typewriter + ' ' +\family default ++ +\family typewriter + cmdline +\family default + . +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +parmfile parmfile.txt +\end_layout + +\begin_layout Subsubsection + +\family typewriter +lock +\begin_inset LatexCommand \label{sub:lock} + +\end_inset + + +\end_layout + +\begin_layout Standard +The +\family typewriter +lock +\family default + command allows to have password protected boot entries. + If a locked boot entry is selected the user has to enter the password specified + in the +\family typewriter +password +\family default + statement (see section +\begin_inset LatexCommand \ref{sub:password} + +\end_inset + +) to execute this boot selection entry. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +lock +\end_layout + +\begin_layout Subsubsection + +\family typewriter +pause +\end_layout + +\begin_layout Standard +The +\family typewriter +pause +\family default + statement displays a message and waits for user input before the boot entry + will be started. + This can be used to ask the user to prepare the system for booting (e.g. + by inserting a boot CD to the CD drive). +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +pause Please insert your boot floppy! +\end_layout + +\begin_layout Subsubsection + +\family typewriter +insfile +\end_layout + +\begin_layout Standard +The +\family typewriter +insfile +\family default + statement can be used as an alternative method to specify a boot configuration. + An +\family typewriter +\size scriptsize +*.ins +\family default +\size default + file contains the definitions of a kernel, initial ramdisk and parmfile, + therefore it makes no sense to specify these components . + The +\family typewriter +insfile +\family default + statement is only available on the s390 platform and is provided with several + Linux distributions for this platform. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +insfile dasd://(0.0.5c5e,1)/usr/local/insfile_test/redhat/generic.ins +\end_layout + +\begin_layout Subsubsection + +\family typewriter +bootmap +\begin_inset LatexCommand \label{sub:bootmap} + +\end_inset + + +\end_layout + +\begin_layout Standard +The +\family typewriter +bootmap +\family default + command can be used as an alternative method to specify a boot configuration. + It is only available on the s390 platform and boots the system using the + boot information from the boot map of the specified disk. + This boot information is written by the tool +\family typewriter +zipl +\family default +. + Only bootmaps in the format created by +\family typewriter +zipl +\family default + version 1.2 or newer are supported. + The bootmap command uses a modified URI format that is described in section + +\begin_inset LatexCommand \ref{sub:dasd-URI-for} + +\end_inset + + and +\begin_inset LatexCommand \ref{sub:zfcp-URI-for} + +\end_inset + +. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code +bootmap dasd://(0.0.5e2a,0) +\end_layout + +\begin_layout Subsubsection + +\family typewriter +halt +\end_layout + +\begin_layout Standard +The +\family typewriter +halt +\family default + statement can be used instead of a real boot selection. + It will halt the Linux environment of the system loader. +\end_layout + +\begin_layout Subsubsection + +\family typewriter +reboot +\end_layout + +\begin_layout Standard +The +\family typewriter +reboot +\family default + statement can be used instead of a real boot selection. + This statement will reboot the system. + If a first stage bootloader is installed the system will be restarted via + this bootloader. +\end_layout + +\begin_layout Subsubsection + +\family typewriter +shell +\family default + +\begin_inset LatexCommand \label{sub:shell} + +\end_inset + + +\end_layout + +\begin_layout Standard +The +\family typewriter +shell +\family default + statement can be used instead of a real boot selection. + If the resulting boot entry is selected, the user will get a shell prompt. + Leaving the shell prompt via exit will redisplay the boot selection menu. +\end_layout + +\begin_layout Subsection +URI Definitions +\end_layout + +\begin_layout Standard +\begin_inset LatexCommand \label{sub:URIs} + +\end_inset + +URIs provide a generic mechanism to describe the location of files. + They are used by the system loader to locate boot and configuration files. + The following sections describe the supported URI schemes in detail. +\end_layout + +\begin_layout Subsubsection + +\family typewriter +block +\end_layout + +\begin_layout Standard +The +\family typewriter +block +\family default + URI can be used to reference a file on any block device containing a supported + filesystem. + This is the typical method to access the boot files on the i386 platform + and on other non s390 platforms. + If no filesystem type is specified, the filesystem type will be autodetected. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +block://([,])/ +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +block://(/dev/hda5,ext3)/boot/vmlinuz +\end_layout + +\begin_layout Subsubsection + +\family typewriter +ftp +\family default + +\begin_inset LatexCommand \label{sub:URI_ftp} + +\end_inset + + +\end_layout + +\begin_layout Standard +The +\family typewriter +ftp +\family default + URI can be used to reference a file on a ftp-server. + This URI type is available on all platforms but requires a network connection. + If the remote server requires a UID and a password, it has to be provided + the usual way (see the example below). + In case the UID contains the +\begin_inset Quotes eld +\end_inset + +@ +\begin_inset Quotes erd +\end_inset + + , as it happens in e-mail addresses, it has to be replaced with +\begin_inset Quotes eld +\end_inset + +%40 +\begin_inset Quotes erd +\end_inset + + to avoid any misunderstanding with the separator between the UID:PW combination + and the host-name. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +ftp://[UID[:PW]@]hostname[:PORT]/ +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +ftp://my_name%40ibm.com:my_secret@ftp.server.com/boot/vmlinuz +\end_layout + +\begin_layout Subsubsection + +\family typewriter +http +\family default + +\begin_inset LatexCommand \label{sub:URI_http} + +\end_inset + + +\end_layout + +\begin_layout Standard +The +\family typewriter +http +\family default + URI can be used to reference a file on a http-server. + This URI type is available on all platforms but requires a network connection. + If the remote server requires a UID and a password, it has to be provided + like for the +\begin_inset LatexCommand \ref{sub:URI_ftp} + +\end_inset + +ftp URI (see example below). + In case the UID contains the +\begin_inset Quotes eld +\end_inset + +@ +\begin_inset Quotes erd +\end_inset + + , as it happens in e-mail addresses, it has to be replaced with +\begin_inset Quotes eld +\end_inset + +%40 +\begin_inset Quotes erd +\end_inset + + to avoid any misunderstanding with the separator between the UID:PW combination + and the host-name. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +http://[UID[:PW]@]hostname[:PORT]/ +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +http://my_name%40ibm.com:my_secret@http.server.com/boot/vmlinuz +\end_layout + +\begin_layout Subsubsection + +\family typewriter +scp +\end_layout + +\begin_layout Standard +The +\family typewriter +scp +\family default + URI can be used to reference a file on a server which is accessible via + the SSH protocol. + As with the +\begin_inset LatexCommand \ref{sub:URI_ftp} + +\end_inset + + ftp- and the +\begin_inset LatexCommand \ref{sub:URI_http} + +\end_inset + + http-URI the scp-URI is available on all platforms but requires a network + connection. + The encoding of a UID and a password is identical to the above described + protocols (see example below). + In case the UID contains the +\begin_inset Quotes eld +\end_inset + +@ +\begin_inset Quotes erd +\end_inset + + , as it happens in e-mail addresses, it has to be replaced with +\begin_inset Quotes eld +\end_inset + +%40 +\begin_inset Quotes erd +\end_inset + + to avoid any misunderstanding with the separator between the UID:PW combination + and the host-name. + Beside the UID:PW combination, encoded in the URI, the public key authenticatio +n is supported as well. + Therefor the local public key has to be part of the servers +\family typewriter +authorized_keys +\family default +file and the public key authentication has to be enabled on the server. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +scp://[UID[:PW]@]hostname[:PORT]/ +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +scp://my_name%40ibm.com:my_secret@ssh.server.com/boot/vmlinuz +\end_layout + +\begin_layout Subsubsection + +\family typewriter +file +\end_layout + +\begin_layout Standard +The +\family typewriter +file +\family default + URI can be used to reference files on an already mounted filesystem. + This type of URI is available on all platforms. + In an unmodified system loader boot environment it can only be used to + reference files on the initial ramdisk. + If the system loader is running as a program on an already booted Linux + system it can be used instead of the other URIs. +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +file:///boot/vmlinuz +\end_layout + +\begin_layout Subsubsection + +\family typewriter +dasd +\end_layout + +\begin_layout Standard +The +\family typewriter +dasd +\family default + URI can be used to reference files on zSeries ESCON/FICON attached storage. + This type of URI is only available on the s390 platform. + If no filesystem type is specified, the filesystem type will be autodetected. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +dasd://(,[[,]])/ +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +dasd://(0.0.5c5e,1)/usr/local/insfile_test/SuSE/suse.ins +\end_layout + +\begin_layout Subsubsection + +\family typewriter +zfcp +\end_layout + +\begin_layout Standard +The zfcp URI can be used to reference files on s390 (zSeries) FCP attached + storage. + This type of URI is only available on the s390 platform. + If no filesystem type is specified, the filesystem type will be autodetected. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +zfcp://(,,,[[,]])/ +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +zfcp://(0.0.54e0,0x5005076303000104,0x4011400500000000,1)/boot/initrd.img +\end_layout + +\begin_layout Subsubsection + +\family typewriter +dasd +\family default + URI for the bootmap command +\begin_inset LatexCommand \label{sub:dasd-URI-for} + +\end_inset + + +\end_layout + +\begin_layout Standard +Because the bootmap information is not stored inside a file system the bootmap + command (see section +\begin_inset LatexCommand \ref{sub:bootmap} + +\end_inset + +) uses a reduced form of the dasd URI. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +dasd://([,]) +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +dasd://(0.0.5e89,1) +\end_layout + +\begin_layout Subsubsection + +\family typewriter +zfcp +\family default + URI for the bootmap command +\begin_inset LatexCommand \label{sub:zfcp-URI-for} + +\end_inset + + +\end_layout + +\begin_layout Standard +Because the bootmap information is not stored inside a file system the bootmap + command (see section +\begin_inset LatexCommand \ref{sub:bootmap} + +\end_inset + +) uses a reduced form of the zfcp URI. +\end_layout + +\begin_layout Standard +Syntax: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +zfcp://(,,[,]) +\end_layout + +\begin_layout Standard +Example: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +zfcp://(0.0.04ae,0x500507630e01fca2,0x4010404500000000,2) +\end_layout + +\begin_layout Section +Using the Command Line Interface +\end_layout + +\begin_layout Standard +The command line interface is the basic user interface of the system loader. + It is designed to run on all platforms and without any special requirements + regarding the capabilities of the user interface device. + Therefore it will be usable on line mode interfaces like the 3270 terminal + on the s390 platform or via a serial line on typical open systems platforms. +\end_layout + +\begin_layout Standard +The command line interface displays the title information from all boot + entries found in the system loader configuration file. + The default entry is marked by an arrow symbol +\family typewriter +-> +\family default +, locked entries are displayed in brackets +\family typewriter +[] +\family default +. +\end_layout + +\begin_layout LyX-Code +kboot user interface is starting. + +\end_layout + +\begin_layout LyX-Code +Configuration file source: file:///boot/boot_menu.config +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code +Welcome to kboot! +\end_layout + +\begin_layout LyX-Code +The following boot options are available: +\end_layout + +\begin_layout LyX-Code +-> 1 latest kernel from DASD +\end_layout + +\begin_layout LyX-Code + 2 latest kernel from EVMS (matching system) +\end_layout + +\begin_layout LyX-Code + 3 rescue kernel from DASD +\end_layout + +\begin_layout LyX-Code + 4 kboot (development version) +\end_layout + +\begin_layout LyX-Code + 5 Linux 2.6.13-14.x from FCP disk +\end_layout + +\begin_layout LyX-Code + 6 System Reboot +\end_layout + +\begin_layout LyX-Code + 7 System Halt +\end_layout + +\begin_layout LyX-Code + 8 start a shell! +\end_layout + +\begin_layout LyX-Code + d Display boot parameters of the selected entry +\end_layout + +\begin_layout LyX-Code + m Modify and boot selected entry +\end_layout + +\begin_layout LyX-Code + i Enter boot parameters interactively +\end_layout + +\begin_layout LyX-Code +Please enter your selection: +\end_layout + +\begin_layout Standard +The selection of a specific entry is done by entering its number. + If the menu is not completely visible it can be redisplayed by entering + an empty input. + If a timeout occurs while one or more user interfaces are waiting for input, + all user interfaces will be terminated and the default entry will be executed. + If a timeout is defined it will be displayed by the user interface. + In addition to the selection of predefined menu entries the user interface + allows to display existing boot entries, to modify them or to enter new + entries from scratch. +\end_layout + +\begin_layout Standard +Entering the boot entry number with prefix +\family typewriter +d +\family default + will display the associated boot entry like shown in the following example. + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +d2 +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +*** BOOT ENTRY PRINTOUT *** +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +title latest kernel from EVMS (matching system) +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +label evms +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +root block://(/dev/evms/evmsvol)/boot/ +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +kernel vmlinuz +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +cmdline dasd=5c60-5c61 root=/dev/dasda1 ro noinitrd selinux=0 +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +action KERNEL_BOOT +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +*** Press RETURN to continue *** +\end_layout + +\begin_layout Standard +With prefix +\family typewriter +m +\family default + the boot entry will first be displayed completely and will then be offered + line by line to allow the input of modified lines. + Empty user input will leave the respective line unchanged. + The modified boot entry will be displayed again and can be booted finally. +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +m2 +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +*** BOOT ENTRY PRINTOUT *** +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +title latest kernel from EVMS (matching system) +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +label evms +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +root block://(/dev/evms/evmsvol)/boot/ +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +kernel vmlinuz +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +cmdline dasd=5c60-5c61 root=/dev/dasda1 ro noinitrd selinux=0 +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +action KERNEL_BOOT +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +*** Please enter the new values for each line *** +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +*** or hit ENTER to leave it unchanged. + *** +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +root +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +kernel vmlinuz.rescue +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +initrd +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +cmdline +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +parmfile +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +*** BOOT ENTRY PRINTOUT *** +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +root block://(/dev/evms/evmsvol)/boot/ +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +kernel vmlinuz.rescue +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +cmdline dasd=5c60-5c61 root=/dev/dasda1 ro noinitrd selinux=0 +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +action KERNEL_BOOT +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +*** Press 'B' to boot this entry or any other key to cancel *** +\end_layout + +\begin_layout Standard +The +\family typewriter +i +\family default + command allows to enter a boot entry interactively from scratch in cases + where no similar entry is already present in the boot selection menu. +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +i +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +*** Please enter the values for manual boot*** +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +ACTION => 1->KERNEL_BOOT 2->INSFILE_BOOT 3->BOOTMAP_BOOT +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +action 1 +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +root block://(/dev/evms/evmsvol)/boot/ +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +kernel vmlinuz.rescue +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +initrd +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +cmdline dasd=5c60-5c61 root=/dev/dasda1 ro noinitrd selinux=0 +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +parmfile +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +*** BOOT ENTRY PRINTOUT *** +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +root block://(/dev/evms/evmsvol)/boot/ +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +kernel vmlinuz.rescue +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +cmdline dasd=5c60-5c61 root=/dev/dasda1 ro noinitrd selinux=0 +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +action KERNEL_BOOT +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +*** Press 'B' to boot this entry or any other key to cancel *** +\end_layout + +\begin_layout Section +The +\family typewriter +kboot_admin +\family default + Tool +\begin_inset LatexCommand \label{sec:The-kboot_admin-Tool} + +\end_inset + + +\end_layout + +\begin_layout Standard +The administration tool was created to modify a ramfs to suite all environment + and user requirements while running the minimal system contained within + the ramfs. + The functionality includes the support to add any executable, library or + module to the ramfs. + In addition all dependencies are detected and resolved by adding those + files to the ramfs as well. +\end_layout + +\begin_layout Standard +E.g. + if an added executable is dynamically linked and has therefor certain library + dependencies, this will be detected and the required libraries will be + copied to the ramfs. + +\end_layout + +\begin_layout Standard +The same applies for library (e.g. + library_a requires library_b) and module (mod_a requires mod_b) dependencies. + If modules are added to the ramfs the required modules.dep file is generated + in the appropriate location. +\end_layout + +\begin_layout Standard +The second field of application is to merge two ramfs files into one. + This might be the case if a special utility ramfs exists and the extra + features of this ramfs should be added to the default initial ramfs of + a distribution (e.g.: merge the kboot ramfs with SuSEs initrd). + The resulting ramfs contains all files from both sources whereas the content + of the master ramfs, usually the distribution ramfs, takes precedence. +\end_layout + +\begin_layout Standard +In addition the tool can be used to change the super-users password within + the ramfs. + This functionality is primarily used when the ramfs is supporting remote-access + while running the minimal system. +\end_layout + +\begin_layout Standard +The individual settings of the admin tool are configured through a configuration + file which can be specified by the '-c ' command-line parameter. + The default is /etc/kboot_admin.conf. +\end_layout + +\begin_layout Standard +On first program initiation the configuration file is created automatically + with default values for all settings. +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +GZIP /usr/bin/gzip +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +FIND /usr/bin/find +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +CPIO /usr/bin/cpio +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +CUT /usr/bin/cut +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +RSYNC /usr/bin/rsync +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +GET_K_VERS /sbin/get_kernel_version +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +MASTER_RAMFS /boot/initrd +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +KBOOT_RAMFS /boot/kboot-root-glibc.cpio.gz +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +IMAGE_RAMFS /boot/initrd-kboot.cpio.gz +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +TEMP_DIR /tmp/KBOOT +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +############### the module dependent part ################## +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +KERNEL /boot/vmlinuz +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +MODULE e100 +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +MODULE reiserfs +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +############### executables and libraries ################## +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +EXEC uname +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +EXEC losetup +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +EXEC ldd +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +LIBRARY /lib/libpam_misc.so.0 +\end_layout + +\begin_layout Standard +These settings have to be modified manually to map the local requirements. +\end_layout + +\begin_layout Standard +In addition the admin tool supports the following options and commands. +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +Commands: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + merge join content from -s and -m to -o +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + passwd change password for super-user ID in -m +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + add add executables, libraries and/or modules to the ramfs +\end_layout + +\begin_layout LyX-Code + +\size footnotesize +Options: +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + -h|--help this help text +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + -v|--version print version information +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + -c|--config configuration file name (default /etc/kboot_admin.conf) +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + -m|--master master ramfs superseding other ramfs' content. +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + -s|--secondary second ramfs which is merged with the master ramfs. +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + -o|--output file name for the resulting ramfs image +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + -k|--kernel kernel file name +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + -l|--lib add DLL(s) to ramfs (full qualified path) +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + -m|--module add module(s) to ramfs (e.g. + qeth ) +\end_layout + +\begin_layout LyX-Code + +\size footnotesize + -x|--executable add executable to ramfs (e.g. + losetup) +\end_layout + +\begin_layout Standard +Notice: if one or more of the command-line switches +\family typewriter + -l, -m, -x +\family default +are used, none of the configured file values are used for libraries, modules + and executables. + This means that either the configuration file or the command line is used + to reference the files which are to be added to the ramfs. +\end_layout + +\begin_layout Standard +To describe the admin tool's functionality best, verify the following examples: +\end_layout + +\begin_layout Enumerate +merge two ramfs files into one and use all the settings provided by the + configuration file test.conf . +\end_layout + +\begin_deeper +\begin_layout LyX-Code + +\size footnotesize +admin_tool merge +\end_layout + +\end_deeper +\begin_layout Enumerate +add the executables ldd and /home/frank/my_exec to the ramfs /boot/my_initrd + and store the resulting ramfs in the default file. + +\end_layout + +\begin_deeper +\begin_layout LyX-Code + +\size footnotesize +admin_tool -m /boot/my_initrd -x ldd,/home/frank/my_exec add +\end_layout + +\end_deeper +\begin_layout Enumerate +add all executables, libraries and modules specified in the configuration + file /home/frank/my.conf and store the resulting ramfs in /home/frank/my_initrd.n +ew . +\end_layout + +\begin_deeper +\begin_layout LyX-Code + +\size footnotesize +admin_tool -f /home/frank/my.conf -o /home/frank/my_initrd.new add +\end_layout + +\end_deeper +\begin_layout Enumerate +change the super-users password in the ramfs /boot/my_initrd and store the + resulting ramfs in the same file. +\end_layout + +\begin_deeper +\begin_layout LyX-Code + +\size footnotesize +admin_tool -m /boot/my_initrd -o /boot/my_initrd passwd +\end_layout + +\end_deeper +\begin_layout Section +Using Online Documentation +\end_layout + +\begin_layout Standard +Man pages are available for the +\family typewriter +kboot +\family default + executable and for the system loader configuration file +\family typewriter +kboot.conf +\family default +. + These man pages are meant as a short overview and refer to this specification + and to the system loader design document for a detailed description of + this software. +\end_layout + +\begin_layout Section +Extending the System Loader +\end_layout + +\begin_layout Standard +The system loader is designed to be extensible. + The extension can be done without changing the code of the existing components. + User provided loader modules can provide support for additional URI schemes + (e.g. + nfs, smb). + Additional user interface modules can provide more comfortable user interfaces + (e.g. + graphical or web-based). + +\end_layout + +\begin_layout Section +\start_of_appendix +Examples +\end_layout + +\begin_layout Subsection + +\family typewriter +menu.lst +\family default + to Start the System Loader via +\family typewriter +grub +\end_layout + +\begin_layout Standard +This example shows how the system loader can be booted on the i386 platform + using grub as the first stage boot loader. + Relevant for the system loader is the +\family typewriter +kboot= +\family default + parameter in the kernel command line which references the system loader + configuration file. + Without this parameter the unmodified kboot variant as provided by Werner + Almesberger will be started. + The +\family typewriter +quiet +\family default + parameter minimizes the screen output while the system loader environment + is started. +\end_layout + +\begin_layout Standard + +\size scriptsize +\begin_inset LatexCommand \label{sub:menu.lst-for-grub} + +\end_inset + + +\begin_inset Include \verbatiminput{menu.lst} +preview false + +\end_inset + + +\end_layout + +\begin_layout Subsection +Simple +\family typewriter +kboot.conf +\family default + for i386 +\end_layout + +\begin_layout Standard +The following example shows a simple system loader configuration for the + i386 platform. + Two userinterface instances are started to listen on two different devices + simultaneously. +\end_layout + +\begin_layout LyX-Code + +\size scriptsize +\begin_inset LatexCommand \label{i386conf} + +\end_inset + + +\begin_inset Include \verbatiminput{kboot_i386.conf} +preview false + +\end_inset + + +\end_layout + +\begin_layout Subsection +An Example Using Advanced Configuration Features +\end_layout + +\begin_layout Standard +The following example shows how the same system loader configuration files + can be used on two different systems. + The platform for the examples is s390 which gets the boot configuration + of the first stage boot loader in the file zipl.conf. + Both systems share the same configuration files. +\end_layout + +\begin_layout Subsubsection +zipl.conf on System 1 +\begin_inset LatexCommand \label{sub:zipl.conf} + +\end_inset + + +\end_layout + +\begin_layout Standard +System 1 is a virtual machine called +\family typewriter +linux41 +\family default +. + The configuration for the first stage bootloader +\family typewriter +zipl +\family default + references a file +\family typewriter +parmfile_linux41.kboot +\family default + which contains the kernel commandline that is used to boot the initial + system loader linux environment. +\end_layout + +\begin_layout LyX-Code + +\size scriptsize +\begin_inset Include \verbatiminput{zipl1.conf} +preview false + +\end_inset + + +\end_layout + +\begin_layout Standard +The kernel command line in +\family typewriter +parmfile_linux41.kboot +\family default + contains the parameter +\family typewriter +quiet +\family default + to suppress unnecessary messages while the system loader is booted. + The second parameter references the system loader configuration file +\family typewriter +kboot.conf +\family default + (shown in +\begin_inset LatexCommand \vref{sub:System-Loader-Configuration} + +\end_inset + +) on a disk of the virtual machine. + Note that on the i386 platform usually the +\family typewriter +block +\family default + URI scheme would be used instead of the +\family typewriter +dasd +\family default + URI scheme. +\end_layout + +\begin_layout LyX-Code + +\size scriptsize +\begin_inset Include \verbatiminput{parmfile_linux41.kboot} +preview false + +\end_inset + + +\end_layout + +\begin_layout Subsubsection +zipl.conf on System 2 +\end_layout + +\begin_layout Standard +System 2 is another virtual machine called +\family typewriter +linux40 +\family default +. + This machine has a kernel and the initial ramdisk of the system loader + installed locally but gets the boot configuration via the network from + system 1. + The initial setup of the network interface is done via the +\family typewriter +kset= +\family default + parameter on the kernel commandline. + The +\family typewriter +kboot= +\family default + parameter references the boot configuration via ftp. +\end_layout + +\begin_layout LyX-Code + +\size scriptsize +\begin_inset Include \verbatiminput{zipl2.conf} +preview false + +\end_inset + + +\end_layout + +\begin_layout Subsubsection +System Loader Configuration Used by Both Systems +\begin_inset LatexCommand \label{sub:System-Loader-Configuration} + +\end_inset + + +\begin_inset LatexCommand \label{sub:kboot.conf-for-s390} + +\end_inset + + +\end_layout + +\begin_layout Standard +The following system loader configuration is used by both systems and shows + various examples for system dependent definitions, device setup and included + configuration parts and how these capabilities can be combined. + +\end_layout + +\begin_layout LyX-Code + +\size scriptsize +\begin_inset Include \verbatiminput{kboot.conf} +preview false + +\end_inset + + +\end_layout + +\begin_layout Standard +To show the include mechanism the definition of the generic boot entries + +\family typewriter +reboot +\family default +, +\family typewriter +halt +\family default + and +\family typewriter +shell +\family default + is done via the following include file: +\end_layout + +\begin_layout LyX-Code + +\size scriptsize +\begin_inset Include \verbatiminput{standard_entries.conf} +preview false + +\end_inset + + +\end_layout + +\begin_layout LyX-Code + +\end_layout + +\end_body +\end_document diff -Nuar kboot-10/doc/kboot.conf kboot-10_patch1_doc/doc/kboot.conf --- kboot-10/doc/kboot.conf 1970-01-01 01:00:00.000000000 +0100 +++ kboot-10_patch1_doc/doc/kboot.conf 2006-06-13 15:09:42.000000000 +0200 @@ -0,0 +1,139 @@ +# +# My first system loader config file +# + +default linux1 +timeout 600 + +# +# define userinterfaces to be started +# 1. start a linemode ui on /dev/console +# 2. start a second linemode interface for incoming ssh connections +# + +userinterface linemode /dev/console +userinterface ssh linemode + +# +# device setup +# + +# enable two fcp devices on the vmguest named 'linux40' + +system vmguest(linux40) { + + setup zfcp { + busid 0.0.54ae + wwpn 0x5005076300cb93cb + lun 0x512e000000000000 + } + + setup zfcp { + busid 0.0.54ae + wwpn 0x5005076300cb93cb + lun 0x512f000000000000 + } +} + +# load the qeth kernel module and enable a qeth device +# on the vmguest 'linux41' on lpar 'g53lp15' + +system vmguest(linux41,g53lp15) { + + setup module { + name qeth + } + + setup qeth { + busid 0.0.f5de + busid 0.0.f5df + busid 0.0.f5e0 + } +} + +# +# network setup 'linux41' only +# setup for other systems is done via the kernel command line +# + +system vmguest(linux41,g53lp15) { + + setup network { + mode static + address 9.152.26.121 + mask 255.255.252.0 + gateway 9.152.24.1 + nameserver 9.152.120.241 + interface eth0 + } +} + +# +# here we have the entries for the boot menu +# + +boot_entry { + title latest kernel from DASD + label linux1 + + system vmguest(linux41) { + root dasd://(0.0.5c60,1)/home/kboot/boot/s390/ + } + + system not(vmguest(linux41)) { + root ftp://kboot:kboot@53v15g41.boeblingen.de.ibm.com/home/kboot/boot/s390/ + } + + kernel vmlinuz + + system vmguest(linux40) { + cmdline dasd=5c5e-5c5f root=/dev/dasda1 ro noinitrd selinux=0 + } + + system vmguest(linux41) { + cmdline dasd=5c60-5c61 root=/dev/dasda1 ro noinitrd selinux=0 + } +} + +system vmguest(linux40) { + + boot_entry { + title latest kernel from EVMS + label evms + + root block://(/dev/evms/evmsvol)/boot/ + kernel vmlinuz + cmdline dasd=5c5e-5c5f root=/dev/dasda1 ro noinitrd selinux=0 + } +} + +boot_entry { + title rescue kernel from DASD + label rescue + + system vmguest(linux41) { + root dasd://(0.0.5c60,1)/home/kboot/boot/s390/ + } + + system not(vmguest(linux41)) { + root ftp://kboot:kboot@53v15g41.boeblingen.de.ibm.com/home/kboot/boot/s390/ + } + + kernel vmlinuz.rescue + + system vmguest(linux40) { + cmdline dasd=5c5e-5c5f root=/dev/dasda1 ro noinitrd selinux=0 + } + + system vmguest(linux41) { + cmdline dasd=5c60-5c61 root=/dev/dasda1 ro noinitrd selinux=0 + } +} + +system vmguest(linux41) { + include dasd://(0.0.5c60,1)/home/kboot/boot/s390/standard_entries.conf +} + +system not(vmguest(linux41)) { + include ftp://kboot:kboot@53v15g41.boeblingen.de.ibm.com/home/kboot/boot/s390/standard_entries.conf +} diff -Nuar kboot-10/doc/kboot_i386.conf kboot-10_patch1_doc/doc/kboot_i386.conf --- kboot-10/doc/kboot_i386.conf 1970-01-01 01:00:00.000000000 +0100 +++ kboot-10_patch1_doc/doc/kboot_i386.conf 2006-02-08 15:49:11.000000000 +0100 @@ -0,0 +1,65 @@ +# +# This is a sample config file for kilo +# + +default linux1 +timeout 0 +password secret + +userinterface linemode /dev/tty1 +userinterface linemode /dev/tty + +boot_entry { + title Debian GNU/Linux, latest kernel + label linux1 + + root block://(/dev/hda5,ext3)/boot/ + kernel vmlinuz + initrd initrd.img + cmdline root=/dev/hda5 ro ramdisk_size=100000 lang=de apm=power-off nomce lapic vga=normal +} + +boot_entry { + title Debian GNU/Linux, rescue kernel + label linux2 + + root block://(/dev/hda5,ext3)/boot/ + kernel vmlinuz-2.6.11-kanotix-7 + initrd initrd.img-2.6.11-kanotix-7 + cmdline root=/dev/hda5 ro ramdisk_size=100000 lang=de apm=power-off nomce vga=0x317 +} + +boot_entry { + title Debian GNU/Linux, rescue kernel (locked) + label linux3 + + lock + root block://(/dev/hda5,ext3)/boot/ + kernel vmlinuz-2.6.11-kanotix-7 + initrd initrd.img-2.6.11-kanotix-7 + cmdline root=/dev/hda5 ro ramdisk_size=100000 lang=de apm=power-off nomce vga=0x317 +} + +boot_entry { + title kboot environment + label kboot + + root block://(/dev/hda5,ext3)/boot/ + kernel vmlinuz + initrd kboot-root-glibc.cpio.gz + cmdline root=/dev/hda5 ro ramdisk_size=100000 lang=de apm=power-off nomce lapic vga=normal + +} + +boot_entry { + title System Reboot + label reboot + + reboot +} + +boot_entry { + title System Halt + + halt +} diff -Nuar kboot-10/doc/Makefile kboot-10_patch1_doc/doc/Makefile --- kboot-10/doc/Makefile 1970-01-01 01:00:00.000000000 +0100 +++ kboot-10_patch1_doc/doc/Makefile 2006-06-21 15:01:16.000000000 +0200 @@ -0,0 +1,13 @@ +# +# Makefile for the system loader PDF description +# + +all: description.pdf + +description.pdf: description.tex + pdflatex description.tex # aller guten Dinge sind drei! + pdflatex description.tex + pdflatex description.tex + +description.tex: description.lyx + lyx-qt -e latex description.lyx diff -Nuar kboot-10/doc/menu.lst kboot-10_patch1_doc/doc/menu.lst --- kboot-10/doc/menu.lst 1970-01-01 01:00:00.000000000 +0100 +++ kboot-10_patch1_doc/doc/menu.lst 2006-06-14 11:28:59.000000000 +0200 @@ -0,0 +1,25 @@ +## default num +# Set the default entry to the entry number NUM. Numbering starts from 0, and +# the entry number 0 is the default if the command is not used. +default 1 + +## timeout sec +# Set a timeout, in SEC seconds, before automatically booting the default entry +# (normally the first entry defined). +timeout 5 + +# Pretty colours +color cyan/blue white/blue +gfxmenu (hd0,4)/boot/message + +title Debian GNU/Linux, kernel +root (hd0,4) +kernel /boot/vmlinuz root=/dev/hda5 ro +initrd /boot/initrd.img +boot + +title kboot system loader environment +root (hd0,4) +kernel /boot/vmlinuz ro quiet root=/dev/ram0 kboot=block://(/dev/hda5,ext3)/boot/boot_menu.config +initrd /boot/kboot-root-glibc.cpio.gz +boot diff -Nuar kboot-10/doc/parmfile_linux41.kboot kboot-10_patch1_doc/doc/parmfile_linux41.kboot --- kboot-10/doc/parmfile_linux41.kboot 1970-01-01 01:00:00.000000000 +0100 +++ kboot-10_patch1_doc/doc/parmfile_linux41.kboot 2006-06-12 16:54:28.000000000 +0200 @@ -0,0 +1 @@ +quiet kboot=dasd://(0.0.5c60,1)/home/kboot/boot/s390/kboot.conf diff -Nuar kboot-10/doc/standard_entries.conf kboot-10_patch1_doc/doc/standard_entries.conf --- kboot-10/doc/standard_entries.conf 1970-01-01 01:00:00.000000000 +0100 +++ kboot-10_patch1_doc/doc/standard_entries.conf 2006-06-13 15:09:42.000000000 +0200 @@ -0,0 +1,20 @@ + +boot_entry { + title System Reboot + label reboot + + reboot +} + +boot_entry { + title System Halt + + halt +} + +boot_entry { + title start a shell! + + shell +} + diff -Nuar kboot-10/doc/zipl1.conf kboot-10_patch1_doc/doc/zipl1.conf --- kboot-10/doc/zipl1.conf 1970-01-01 01:00:00.000000000 +0100 +++ kboot-10_patch1_doc/doc/zipl1.conf 2006-06-12 16:54:28.000000000 +0200 @@ -0,0 +1,8 @@ +# This is an expample zipl.conf file +[defaultboot] +default = kboot +[kboot] +target = "/home/kboot/boot" +image = "/home/kboot/boot/s390/vmlinuz" +ramdisk = "/home/kboot/boot/s390/initrd_sl2" +parmfile = "/home/kboot/boot/s390/parmfile_linux41.kboot" diff -Nuar kboot-10/doc/zipl2.conf kboot-10_patch1_doc/doc/zipl2.conf --- kboot-10/doc/zipl2.conf 1970-01-01 01:00:00.000000000 +0100 +++ kboot-10_patch1_doc/doc/zipl2.conf 2006-06-12 16:54:28.000000000 +0200 @@ -0,0 +1,10 @@ +# This is an expample zipl.conf file +[defaultboot] +default = kboot +[kboot] +target = "/boot" +image = "/boot/vmlinuz-2.6.16.18" +ramdisk = "/boot/initrd_sl2" +parameters = "quiet + kset=mod(qeth),qeth(0.0.f5db,0.0.f5dc,0.0.f5dd),static(eth0,9.152.26.120,255.255.252.0,9.152.24.1,9.152.120.241) + kboot=ftp://kboot:kboot@53v15g41.boeblingen.de.ibm.com/home/kboot/boot/s390/kboot.conf" Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Kboot-general mailing list Kboot-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kboot-general