Mailinglist Archive: yast-commit (396 mails)

< Previous Next >
[yast-commit] r65274 - in /trunk/autoinstallation/doc: ./ images/src/ misc/ xml/
Author: ug
Date: Mon Aug 8 14:12:13 2011
New Revision: 65274

URL: http://svn.opensuse.org/viewcvs/yast?rev=65274&view=rev
Log:
changed to file structure of the documentation

Added:
trunk/autoinstallation/doc/images/src/
trunk/autoinstallation/doc/images/src/EPS (with props)
trunk/autoinstallation/doc/images/src/PNG (with props)
trunk/autoinstallation/doc/images/src/WEB (with props)
trunk/autoinstallation/doc/xml/
trunk/autoinstallation/doc/xml/ASKSection.xml
trunk/autoinstallation/doc/xml/BootMedia.xml
trunk/autoinstallation/doc/xml/BootloaderSection.xml
trunk/autoinstallation/doc/xml/CreateProfile.xml
trunk/autoinstallation/doc/xml/CreateProfileDetails.xml
trunk/autoinstallation/doc/xml/FilesSection.xml
trunk/autoinstallation/doc/xml/GeneralSection.xml
trunk/autoinstallation/doc/xml/Installation.xml
trunk/autoinstallation/doc/xml/Introduction.xml
trunk/autoinstallation/doc/xml/KDumpSection.xml
trunk/autoinstallation/doc/xml/LDAPSection.xml
trunk/autoinstallation/doc/xml/MailSection.xml
trunk/autoinstallation/doc/xml/Makefile
trunk/autoinstallation/doc/xml/Makefile.am
trunk/autoinstallation/doc/xml/Makefile.in
trunk/autoinstallation/doc/xml/NFSSection.xml
trunk/autoinstallation/doc/xml/NISSection.xml
trunk/autoinstallation/doc/xml/NTPSection.xml
trunk/autoinstallation/doc/xml/NetworkInstallation.xml
trunk/autoinstallation/doc/xml/NetworkSection.xml
trunk/autoinstallation/doc/xml/PartitioningSection.xml
trunk/autoinstallation/doc/xml/PrinterSection.xml
trunk/autoinstallation/doc/xml/Profile.xml
trunk/autoinstallation/doc/xml/ReportSection.xml
trunk/autoinstallation/doc/xml/RulesAndClasses.xml
trunk/autoinstallation/doc/xml/RunlevelSection.xml
trunk/autoinstallation/doc/xml/ScriptsSection.xml
trunk/autoinstallation/doc/xml/SecuritySection.xml
trunk/autoinstallation/doc/xml/SoftwareSection.xml
trunk/autoinstallation/doc/xml/SoundSection.xml
trunk/autoinstallation/doc/xml/SysconfigSection.xml
trunk/autoinstallation/doc/xml/UsersSection.xml
trunk/autoinstallation/doc/xml/X11Section.xml
trunk/autoinstallation/doc/xml/advanced.xml
trunk/autoinstallation/doc/xml/appendix-rules.xml
trunk/autoinstallation/doc/xml/appendix2.xml
trunk/autoinstallation/doc/xml/autoyast.xml
trunk/autoinstallation/doc/xml/bin (with props)
trunk/autoinstallation/doc/xml/catalog.xml
trunk/autoinstallation/doc/xml/creating_autoyast2_modules.xml
trunk/autoinstallation/doc/xml/entities (with props)
trunk/autoinstallation/doc/xml/examples (with props)
trunk/autoinstallation/doc/xml/images (with props)
trunk/autoinstallation/doc/xml/linuxrc.xml
trunk/autoinstallation/doc/xml/multiplesource.xml
trunk/autoinstallation/doc/xml/purpose.xml
trunk/autoinstallation/doc/xml/web (with props)
Removed:
trunk/autoinstallation/doc/ASKSection.xml
trunk/autoinstallation/doc/BootMedia.xml
trunk/autoinstallation/doc/BootloaderSection.xml
trunk/autoinstallation/doc/CreateProfile.xml
trunk/autoinstallation/doc/CreateProfileDetails.xml
trunk/autoinstallation/doc/FilesSection.xml
trunk/autoinstallation/doc/GeneralSection.xml
trunk/autoinstallation/doc/Installation.xml
trunk/autoinstallation/doc/Introduction.xml
trunk/autoinstallation/doc/KDumpSection.xml
trunk/autoinstallation/doc/LDAPSection.xml
trunk/autoinstallation/doc/MailSection.xml
trunk/autoinstallation/doc/NFSSection.xml
trunk/autoinstallation/doc/NISSection.xml
trunk/autoinstallation/doc/NTPSection.xml
trunk/autoinstallation/doc/NetworkInstallation.xml
trunk/autoinstallation/doc/NetworkSection.xml
trunk/autoinstallation/doc/PartitioningSection.xml
trunk/autoinstallation/doc/PrinterSection.xml
trunk/autoinstallation/doc/Profile.xml
trunk/autoinstallation/doc/ReportSection.xml
trunk/autoinstallation/doc/RulesAndClasses.xml
trunk/autoinstallation/doc/RunlevelSection.xml
trunk/autoinstallation/doc/ScriptsSection.xml
trunk/autoinstallation/doc/SecuritySection.xml
trunk/autoinstallation/doc/SoftwareSection.xml
trunk/autoinstallation/doc/SoundSection.xml
trunk/autoinstallation/doc/SysconfigSection.xml
trunk/autoinstallation/doc/UsersSection.xml
trunk/autoinstallation/doc/X11Section.xml
trunk/autoinstallation/doc/advanced.xml
trunk/autoinstallation/doc/appendix-rules.xml
trunk/autoinstallation/doc/appendix2.xml
trunk/autoinstallation/doc/autoyast.xml
trunk/autoinstallation/doc/autoyast2-8.1.txt
trunk/autoinstallation/doc/catalog.xml
trunk/autoinstallation/doc/creating_autoyast2_modules.xml
trunk/autoinstallation/doc/linuxrc.xml
trunk/autoinstallation/doc/misc/
trunk/autoinstallation/doc/multiplesource.xml
trunk/autoinstallation/doc/purpose.xml
Modified:
trunk/autoinstallation/doc/Makefile.am

Modified: trunk/autoinstallation/doc/Makefile.am
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/Makefile.am?rev=65274&r1=65273&r2=65274&view=diff
==============================================================================
--- trunk/autoinstallation/doc/Makefile.am (original)
+++ trunk/autoinstallation/doc/Makefile.am Mon Aug 8 14:12:13 2011
@@ -4,133 +4,7 @@
# $Id$
#

-SUBDIRS = autodocs images entities bin components examples xsl
+SUBDIRS = xml autodocs images entities bin components examples xsl
htmldir = $(docdir)/html

-xml_file = autoyast.xml
-xml_files = $(wildcard *.xml)
-
-
-EXTRA_DIST = $(xml_files) $(wildcard *.xsl) web/default.css
-
-CLEANFILES = .html.sum profile.dtd.xml elements \
- elements.xml elements.ent profile.dtd.xml examples.ent\
- components.ent .ps.sum autoyast.out autoyast.pdf autoyast.fo \
- images.ent
-
-STYLESHEET_CSS = default.css
-
-html_DATA = $(wildcard html/*.html) \
- html/index.html \
- html/yast2docs.css \
- html/default.css
-
-#doc_DATA = autoyast.pdf
-
-components: components.ent
- bin/components.sh noref > components.ent
-
-examples: examples.ent
- bin/examples.sh > examples.ent
-
-html/index.html: autoyast.xml
- XML_CATALOG_FILES=@XML_CATALOG@ \
- time -p @XSLTPROC@ --xinclude \
- -stringparam chunk.fast '1' \
- --stringparam html.stylesheet $(STYLESHEET_CSS) \
- @STYLESHEET_HTML@ autoyast.xml
- XML_CATALOG_FILES=@XML_CATALOG@ \
- time -p @XSLTPROC@ --xinclude \
- -stringparam base.dir 'html/devel/' \
- -stringparam chunk.fast '1' \
- --stringparam html.stylesheet $(STYLESHEET_CSS) \
- @STYLESHEET_HTML@ creating_autoyast2_modules.xml
- cd html/devel; \
- ln -s ../default.css ./default.css; \
- ln -s ../images ./images
- cd ../..
-
-html/index.html: autoyast.xml
- XML_CATALOG_FILES=@XML_CATALOG@ \
- @XSLTPROC@ --xinclude @STYLESHEET_HTML@ \
- $<
-
-#autoyast.fo: autoyast.xml
-# XML_CATALOG_FILES=@XML_CATALOG@ \
-# @XSLTPROC@ @XSLTPROC_FLAGS@ --xinclude \
-# -o $@ @STYLESHEET_PDF@ $<
-
-#autoyast.fo: autoyast.xml
-# saxon -o autoyast.fo autoyast.xml @STYLESHEET_PDF@
-
-#autoyast.pdf: autoyast.fo
-# fop -q $< $@
-
-autoyast.xml: images.ent examples components
-
-html/yast2docs.css: html/index.html
- cp @STYLESHEET_CSS@ html
- cp -a $(ydatadir)/docbook/images html
-
-html/default.css: html/index.html webimages
- cp web/default.css html
-
-images.ent:
- @make -r -C images/WEB -f makefile.ent ima
-
-: images.ent chunks webimages
-
-
-webimages:
- mkdir -p html/img
- cp -a images/WEB/*png html/img
-
-
-.PHONY: images examples.ent components.ent
-
-images: images/EPS/* images/PNG/*
- @if ! [ -e "img" ]; then \
- mkdir -p img; \
- fi
- @if ! [ -e "img/Makefile" ]; then \
- ln -s ../images/makefile.images img/Makefile; \
- fi
-
- @echo "generating PNG files for all outputs...";
- @if [ "$(IMAGES)" = "all" ]; then \
- rm -f img/*.{png,pdf}; \
- fi;
-
- @for j in `bin/findImages.sh` ; do \
- if [ -e "images/EPS/$$j" ]; then \
- source="images/EPS/$$j"; eps="1";\
- elif [ -e "images/PNG/$$j" ]; then \
- source="images/PNG/$$j"; eps="0"; \
- fi; \
- dest=`echo "img/$$j" | sed -e "s|_|-|g;s|.eps||g;s|.png||g;"`; \
- if [ -e "$$source" ]; then \
- if [ ! -f $$dest".png" ] || [ $$dest".png" -ot $$source
]; then \
- if [ $$eps == "1" ]; then \
- echo " converting $$source ->
$$dest'.pdf'"; \
- bin/epstopdf12 -o=$$dest".pdf"
$$source; \
- echo " converting $$source ->
$$dest'.png'"; \
- convert $$source $$dest".png"; \
- else \
- echo " linking $$source ->
$$dest'.png'"; \
- convert -depth 8 $$source $$dest".png";
\
- fi; \
- fi; \
- fi; \
- done
- @make -r -C img ima
-
-
-install-data-local:
- install -d -m 755 $(DESTDIR)$(htmldir)
- cp -a $(srcdir)/html/images $(DESTDIR)$(htmldir)
- cp -a $(srcdir)/html/img $(DESTDIR)$(htmldir)
- cp -a $(srcdir)/html/devel $(DESTDIR)$(htmldir)
-
-clean-local:
- rm -rf html


Added: trunk/autoinstallation/doc/images/src/EPS
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/images/src/EPS?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/images/src/EPS (added)
+++ trunk/autoinstallation/doc/images/src/EPS Mon Aug 8 14:12:13 2011
@@ -0,0 +1 @@
+link ../EPS
\ No newline at end of file

Added: trunk/autoinstallation/doc/images/src/PNG
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/images/src/PNG?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/images/src/PNG (added)
+++ trunk/autoinstallation/doc/images/src/PNG Mon Aug 8 14:12:13 2011
@@ -0,0 +1 @@
+link ../PNG
\ No newline at end of file

Added: trunk/autoinstallation/doc/images/src/WEB
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/images/src/WEB?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/images/src/WEB (added)
+++ trunk/autoinstallation/doc/images/src/WEB Mon Aug 8 14:12:13 2011
@@ -0,0 +1 @@
+link ../WEB
\ No newline at end of file

Added: trunk/autoinstallation/doc/xml/ASKSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/ASKSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/ASKSection.xml (added)
+++ trunk/autoinstallation/doc/xml/ASKSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,453 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+ <section id="CreateProfile.Ask">
+ <title>
+ Ask the user for values during installation
+ </title>
+
+ <para>
+ This feature is only available since SUSE Linux 10.1 and SLES10.
+ </para>
+ <para>
+ You have the option to let the user decide the values of specific
+ parts of the profile during the installation. If you use that feature,
+ a popup will come up during the installation and will ask the user to
+ enter a specific part of the profile. So if you want a full auto
installation
+ but you want the user to set the password of the local account, you
can do
+ this via the <emphasis>ask</emphasis> directive in the profile.
+ </para>
+ <para>
+ The following elements must be between the &lt;ask-list
config:type="list"&gt;&lt;ask&gt; ... &lt;/ask&gt;&lt;/ask-list&gt; tags in the
&lt;general&gt; section.
+ </para>
+ <para>
+ <table frame='top'>
+ <title>XML representation</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>question</entry>
+ <entry>The question you want to ask the user.
+ <para><screen>&lt;question&gt;Enter the LDAP
server&lt;/question&gt;</screen></para></entry>
+ <entry>The default value is the path to the element (the path
often looks strange, so I recommend to enter a question)</entry>
+ </row>
+ <row>
+ <entry>default</entry>
+ <entry>you can set a pre-selection for the user. A textentry
will be filled out with this value,
+ a checkbox will be "true" or "false" and a selection
will have this default "value" pre-selected.
+
<para><screen>&lt;default&gt;dc=suse,dc=de&lt;/default&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>help</entry>
+ <entry>An optional helptext that is shown on the left side of
the question.
+ <para><screen>&lt;help&gt;Enter the LDAP server
address.&lt;/help&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>title</entry>
+ <entry>An optional title that is shown above the questions.
+ <para><screen>&lt;title&gt;LDAP
server&lt;/title&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>type</entry>
+ <entry>the type of the element you want to change. Possible
values are "symbol","boolean","string" and "integer".
+ The filesystem in
+ the partition section is a symbol, while the
"encrypted" element in the user configuration is a boolean.
+ You can see the type of that element if you look in
your profile at the config:type="...." attribute.
+ Since openSUSE 11.2 and SLES11-SP2 you can use
"static_text" as type too. A static_text is just a text that
+ does not require any user input and can be used to show
information if it's not wanted in the help text.
+
<para><screen>&lt;type&gt;symbol&lt;/type&gt;</screen></para></entry>
+ <entry>optional. The defaul is string. If type is "symbol" you
must provide the selection element too (see below)</entry>
+ </row>
+ <row>
+ <entry>password</entry>
+ <entry>if this boolean is set to "true", a password dialog
pops up instead of a simple text entry. Setting this
+ to "true" makes only sense if "type" is string.
+ <para><screen>&lt;password
config:type="boolean"&gt;true&lt;/password&gt;</screen></para></entry>
+ <entry>optional. The default is "false"</entry>
+ </row>
+ <row>
+ <entry>path (deprecated since openSUSE 11.0 - use
pathlist)</entry>
+ <entry>The path to the element in the profile. It's a comma
seperated list of elements that describes the
+ path to the element you want to change. For example,
the ldap server element can be found in the profile
+ in the &lt;ldap&gt;&lt;ldap_server&gt; section. So if
you want to change that value, you have to set the
+ path to "ldap,ldap_server". If you want to change the
password of the first user in the profile, you have to
+ set the path to "users,0,user_password". The "0"
indicates the first user in the &lt;users config:type="list"&gt;
+ list of users in the profile.
+
<para><screen>&lt;path&gt;networking,dns,hostname&lt;/path&gt;</screen></para></entry>
+ <entry>this information is optional but you should at least
provie <emphasis>path</emphasis> or <emphasis>file</emphasis></entry>
+ </row>
+ <row>
+ <entry>pathlist (available since openSUSE 11.0 and replaces
<emphasis>path</emphasis>)</entry>
+ <entry>a list of <emphasis>path</emphasis> elements (see above)
+ <para><screen>&lt;pathlist
config:type="list"&gt;&lt;path&gt;networking,dns,hostname&lt;/path&gt;&lt;path&gt;...&lt;/path&gt;</screen></para></entry>
+ <entry>this information is optional but you should at least
provie <emphasis>path</emphasis> or <emphasis>file</emphasis></entry>
+ </row>
+ <row>
+ <entry>file (available since SLES10 SP1 and SL 10.2)</entry>
+ <entry>you can store the answer to a question in a file, to
use it in one of your scripts later. If you ask during stage=inital and you
want to use the answer in stage2, then you have to copy the answer-file in a
chroot script that is running as chrooted=false. Do it like this "cp
/tmp/my_answer /mnt/tmp/". The reason for that is, that /tmp in stage1 is just
in the RAM disk and will get lost after the reboot but the installed system is
already mounted at /mnt/
+
<para><screen>&lt;file&gt;/tmp/answer_hostname&lt;/file&gt;</screen></para></entry>
+ <entry>this information is optional but you should at least
provie <emphasis>path</emphasis> or <emphasis>file</emphasis></entry>
+ </row>
+ <row>
+ <entry>password</entry>
+ <entry>if this boolean is set to "true", a password dialog
pops up instead of a simple text entry. Setting this
+ to "true" makes only sense if "type" is string.
+ <para><screen>&lt;password
config:type="boolean"&gt;true&lt;/password&gt;</screen></para></entry>
+ <entry>optional. The default is "false"</entry>
+ </row>
+ <row>
+ <entry>stage</entry>
+ <entry>stage configures the installation stage where the
question pops up. You can set this value to "cont" or
+ "initial". "initial" means the popup comes up very
early in the installation, short after the pre-script
+ has run. "cont" means, that the dialog with the
question comes after the first reboot, when the system
+ boots for the very first time. Questions you answer
during the "inital" stage, will write their answer
+ into the profile on the harddisk. You should know that
if you enter cleartext passwords during "initial".
+ Of course it does not make sense to ask for a
filesystem to use in the "cont" phase. The harddisk is already
+ partitioned at that stage and the question will have no
effect.
+
<para><screen>&lt;stage&gt;cont&lt;/stage&gt;</screen></para></entry>
+ <entry>optional. The default is "initial"</entry>
+ </row>
+ <row>
+ <entry>selection</entry>
+ <entry>the selection element contains a list of &lt;entry&gt;
elements. Each entry represents a possible option
+ for the user to choose. So the user can't enter a value
in a textfield, but he can choose from a list
+ of values.
+ <para><screen>
+&lt;selection config:type="list"&gt;
+ &lt;entry&gt;
+ &lt;value&gt;
+ reiser
+ &lt;/value&gt;
+ &lt;label&gt;
+ Reiser Filesystem
+ &lt;/label&gt;
+ &lt;/entry&gt;
+ &lt;entry&gt;
+ &lt;value&gt;
+ ext3
+ &lt;/value&gt;
+ &lt;label&gt;
+ Extended3 Filesystem
+ &lt;/label&gt;
+ &lt;/entry&gt;
+&lt;/selection&gt;</screen></para></entry>
+ <entry>optional for type=string, not possible for type=boolean
and a must have for type=symbol</entry>
+ </row>
+ <row>
+ <entry>dialog (available since SL 10.3 and SLES10 SP2)</entry>
+ <entry>Since OpenSUSE 10.3 you can have more than one question
per dialog. To make that possible you have
+ to specifiy the dialog-id with an integer. All questions with
the same dialog-id are on the same dialog.
+ The dialogs are sorted by the id too.
+ <para><screen>&lt;dialog
config:type="integer"&gt;3&lt;/dialog&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>element (available since SL 10.3 and SLES10 SP2)</entry>
+ <entry>Since OpenSUSE 10.3 you can have more than one question
per dialog. To make that possible you have
+ to specifiy the element-id with an integer. The questions on a
dialog are sorted by the id.
+ <para><screen>&lt;element
config:type="integer"&gt;1&lt;/element&gt;</screen></para></entry>
+ <entry>optional (see dialog></entry>
+ </row>
+ <row>
+ <entry>frametitle (available since SL 10.3 and SLES10
SP2)</entry>
+ <entry>Since OpenSUSE 10.3 you can have more than one question
per dialog. Each question on a dialog has
+ a frame that can have a frametitle. A small caption for each
question if you want so. Since openSUSE 11.3 you can put multiple elements into
one frame. They have to have the same frametitle then.
+ <para><screen>&lt;frametitle&gt;User
data&lt;/frametitle&gt;</screen></para></entry>
+ <entry>optional (default is no frametitle)</entry>
+ </row>
+ <row>
+ <entry>script (available since SL 10.3 not in SLES10
SP1)</entry>
+ <entry>with 10.3 you can run scripts after a question has been
answered (see the table below for detailed instructions about scripts)
+
<para><screen>&lt;script&gt;...&lt;/script&gt;</screen></para></entry>
+ <entry>optional (default is no script)</entry>
+ </row>
+ <row>
+ <entry>ok_label (available since openSUSE 11.2 / SLES11
SP2</entry>
+ <entry>You can change the Label on the "Ok" button. The last
element that specifies the label for a dialog wins.
+
<para><screen>&lt;ok_label&gt;Finish&lt;/ok_label&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>back_label (available since openSUSE 11.2 / SLES11
SP2</entry>
+ <entry>You can change the Label on the "Back" button. The last
element that specifies the label for a dialog wins.
+ <para><screen>&lt;back_label&gt;change
values&lt;/back_label&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>timeout (available since openSUSE 11.2 /
SLES11-SP2</entry>
+ <entry>You can specify an integer here that is used as timeout
in seconds. If the user does not answer the question before the timeout, the
default value is taken as answer. When the user touches/changes any widget in
the dialog, the timeout is turned off and the dialog has to be confirmed by the
ok-button.
+ <para><screen>&lt;timeout
config:type="integer"&gt;30&lt;/timeout&gt;</screen></para></entry>
+ <entry>optional. A missing value is interpreted as 0 which
means that there is no timeout</entry>
+ </row>
+ <row>
+ <entry>default_value_script (available since openSUSE 11.2 /
SLES11-SP2)</entry>
+ <entry>you can run scripts to set the default value for a
question(see the table below for detailed instructions about default value
scripts). It's useful if you can "calculate" a useful default value, especially
in combination with the "timeout" option.
+
<para><screen>&lt;default_value_script&gt;...&lt;/default_value_script&gt;</screen></para></entry>
+ <entry>optional (default is no script)</entry>
+ </row>
+ </tbody>
+ </tgroup>
+
+ </table>
+ </para>
+
+ <para>
+ The following elements must be between the &lt;ask-list
config:type="list"&gt;&lt;ask&gt;&lt;default_value_script&gt;...&lt;/default_value_script&gt;...&lt;/ask&gt;&lt;/ask-list&gt;
tags in the &lt;general&gt; section. It's available since 11.2 and SLES11-SP2
+ </para>
+ <para>
+ <table frame='top'>
+ <title>XML representation</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>source</entry>
+ <entry>the source code of the script. Whatever you echo to
STDOUT will be used as default value for the ask-dialog. If your script has an
exit code other than 0, the normal default element is used. Take care you echo
with "echo -n" to suppress the '\n' and that you echo reasonable values and not
"okay" for a boolean
+
<para><screen>&lt;source&gt;...&lt;/source&gt;</screen></para></entry>
+ <entry>this value is required. Otherwise nothing would be
executed</entry>
+ </row>
+ <row>
+ <entry>interpreter</entry>
+ <entry>the interpreter to use
+
<para><screen>&lt;interpreter&gt;perl&lt;/interpreter&gt;</screen></para></entry>
+ <entry>default is shell (you can set "/bin/myinterpreter" as
value too)</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+
+
+ <para>
+ The following elements must be between the &lt;ask-list
config:type="list"&gt;&lt;ask&gt;&lt;script&gt;...&lt;/script&gt;...&lt;/ask&gt;&lt;/ask-list&gt;
tags in the &lt;general&gt; section. It's available since 10.3 (not SLES10
SP1).
+ </para>
+ <para>
+ <table frame='top'>
+ <title>XML representation</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>filename</entry>
+ <entry>the filename of the script
+
<para><screen>&lt;filename&gt;my_ask_script.sh&lt;/filename&gt;</screen></para></entry>
+ <entry>default is ask_script.sh</entry>
+ </row>
+ <row>
+ <entry>source</entry>
+ <entry>the source code of the script. Together with
"rerun_on_error" on you check the value that was entered for sanity (since 11.0
only). Your script can create a file "/tmp/next_dialog" with a dialog id in it.
That's the next dialog autoyast will raise then. A value of -1 terminates the
ask sequence. If that file is not created, autoyast will run the dialogs in a
normal order (since 11.0 only)
+
<para><screen>&lt;source&gt;...&lt;/source&gt;</screen></para></entry>
+ <entry>this value is required. Otherwise nothing would be
executed</entry>
+ </row>
+ <row>
+ <entry>environment</entry>
+ <entry>a boolean that passes the "value" of the answer to the
question as an environment variable to the script. The variable is named "VAL".
+ <para><screen>&lt;environment
config:type="boolean"&gt;true&lt;/environment&gt;</screen></para></entry>
+ <entry>optional (default is "false").</entry>
+ </row>
+ <row>
+ <entry>feedback</entry>
+ <entry>a boolean that turns on feedback for the script
execution. That means that STDOUT will be shown in a popup box that must be
confirmed after the script execution.
+ <para><screen>&lt;feedback
config:type="boolean"&gt;true&lt;/feedback&gt;</screen></para></entry>
+ <entry>optional (default is "false").</entry>
+ </row>
+ <row>
+ <entry>debug</entry>
+ <entry>a boolean that turns on debugging for the script
execution
+ <para><screen>&lt;debug
config:type="boolean"&gt;true&lt;/debug&gt;</screen></para></entry>
+ <entry>optional (default is "true"). This value needs feedback
to be turned on too.</entry>
+ </row>
+ <row>
+ <entry>rerun_on_error (available since openSUSE 11.0)</entry>
+ <entry>a boolean that keeps the dialog open until the script
has an exit code of 0 (zero). So you can parse and check the answers the user
gave in the script and popup an error with the "feedback" option.
+ <para><screen>&lt;rerun_on_error
config:type="boolean"&gt;true&lt;/rerun_on_error&gt;</screen></para></entry>
+ <entry>optional (default is "false"). This value should be
used together with the feedback option.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+
+ </table>
+ </para>
+ <para>
+ Below you can see an example of the usage of the "ask" feature.
+ </para>
+ <para>
+ <screen>
+&lt;general&gt;
+ &lt;ask-list config:type=&quot;list&quot;&gt;
+ &lt;ask&gt;
+ &lt;!-- deprecated since openSUSE 11.0; use pathlist instead
+ &lt;path&gt;ldap,ldap_server&lt;/path&gt;
+ --&gt;
+ &lt;pathlist config:type="list"&gt;
+ &lt;path&gt;ldap,ldap_server&lt;/path&gt;
+ &lt;/pathlist&gt;
+ &lt;stage&gt;cont&lt;/stage&gt;
+ &lt;help&gt;choose your server depending on your
department&lt;/help&gt;
+ &lt;selection config:type=&quot;list&quot;&gt;
+ &lt;entry&gt;
+ &lt;value&gt;ldap1.mydom.de&lt;/value&gt;
+ &lt;label&gt;LDAP for development&lt;/label&gt;
+ &lt;/entry&gt;
+ &lt;entry&gt;
+ &lt;value&gt;ldap2.mydom.de&lt;/value&gt;
+ &lt;label&gt;LDAP for sales&lt;/label&gt;
+ &lt;/entry&gt;
+ &lt;/selection&gt;
+ &lt;default&gt;ldap2.mydom.de&lt;/default&gt;
+ &lt;default_value_script&gt;
+ &lt;source&gt; &lt;![CDATA[
+echo -n &quot;ldap1.mydom.de&quot;
+]]&gt;
+ &lt;/source&gt;
+ &lt;/default_value_script&gt;
+ &lt;/ask&gt;
+ &lt;ask&gt;
+ &lt;!-- deprecated since openSUSE 11.0; use pathlist instead
+ &lt;path&gt;networking,dns,hostname&lt;/path&gt;
+ --&gt;
+ &lt;pathlist config:type="list"&gt;
+ &lt;path&gt;networking,dns,hostname&lt;/path&gt;
+ &lt;/pathlist&gt;
+ &lt;question&gt;Enter Hostname&lt;/question&gt;
+ &lt;stage&gt;initial&lt;/stage&gt;
+ &lt;default&gt;enter your hostname here&lt;/default&gt;
+ &lt;/ask&gt;
+ &lt;ask&gt;
+ &lt;!-- deprecated since openSUSE 11.0; use pathlist instead
+ &lt;path&gt;partitioning,0,partitions,0,filesystem&lt;/path&gt;
+ --&gt;
+ &lt;pathlist config:type="list"&gt;
+ &lt;path&gt;partitioning,0,partitions,0,filesystem&lt;/path&gt;
+ &lt;/pathlist&gt;
+ &lt;question&gt;Filesystem&lt;/question&gt;
+ &lt;type&gt;symbol&lt;/type&gt;
+ &lt;selection config:type=&quot;list&quot;&gt;
+ &lt;entry&gt;
+ &lt;value
config:type=&quot;symbol&quot;&gt;reiser&lt;/value&gt;
+ &lt;label&gt;default Filesystem
(recommended)&lt;/label&gt;
+ &lt;/entry&gt;
+ &lt;entry&gt;
+ &lt;value
config:type=&quot;symbol&quot;&gt;ext3&lt;/value&gt;
+ &lt;label&gt;Fallback Filesystem&lt;/label&gt;
+ &lt;/entry&gt;
+ &lt;/selection&gt;
+
+ &lt;/ask&gt;
+ &lt;/ask-list&gt;
+ ...
+&lt;/general&gt;
+</screen>
+</para>
+<para>
+The following example is a nice way to choose between autoyast profiles.
Autoyast will read the "modified.xml" file again after the ask-dialogs are
done. So we can fetch a complete new profile.
+</para>
+<para>
+<screen>
+ &lt;ask&gt;
+ &lt;selection config:type=&quot;list&quot;&gt;
+ &lt;entry&gt;
+ &lt;value&gt;part1.xml&lt;/value&gt;
+ &lt;label&gt;Simple partitioning&lt;/label&gt;
+ &lt;/entry&gt;
+ &lt;entry&gt;
+ &lt;value&gt;part2.xml&lt;/value&gt;
+ &lt;label&gt;encrypted /tmp&lt;/label&gt;
+ &lt;/entry&gt;
+ &lt;entry&gt;
+ &lt;value&gt;part3.xml&lt;/value&gt;
+ &lt;label&gt;LVM&lt;/label&gt;
+ &lt;/entry&gt;
+ &lt;/selection&gt;
+ &lt;title&gt;XML Profile&lt;/title&gt;
+ &lt;question&gt;Choose a profile&lt;/question&gt;
+ &lt;stage&gt;initial&lt;/stage&gt;
+ &lt;default&gt;part1.xml&lt;/default&gt;
+ &lt;script&gt;
+ &lt;filename&gt;fetch.sh&lt;/filename&gt;
+ &lt;environment
config:type=&quot;boolean&quot;&gt;true&lt;/environment&gt;
+ &lt;source&gt;&lt;![CDATA[
+wget http://10.10.0.162/$VAL -O /tmp/profile/modified.xml 2&gt;/dev/null
+]]&gt;
+ &lt;/source&gt;
+ &lt;debug config:type=&quot;boolean&quot;&gt;false&lt;/debug&gt;
+ &lt;feedback
config:type=&quot;boolean&quot;&gt;false&lt;/feedback&gt;
+ &lt;/script&gt;
+ &lt;/ask&gt;
+</screen>
+<para>
+Since openSUSE 11.0 you can verify the answer of a question with a script like
this:
+</para>
+<para>
+<screen>
+ &lt;ask&gt;
+ &lt;script&gt;
+ &lt;filename&gt;my.sh&lt;/filename&gt;
+ &lt;rerun_on_error
config:type=&quot;boolean&quot;&gt;true&lt;/rerun_on_error&gt;
+ &lt;environment
config:type=&quot;boolean&quot;&gt;true&lt;/environment&gt;
+ &lt;source&gt;&lt;![CDATA[
+if [ &quot;$VAL&quot; = &quot;myhost&quot; ]; then
+ echo &quot;Illegal Hostname!&quot;;
+ exit 1;
+fi
+exit 0
+]]&gt;
+ &lt;/source&gt;
+ &lt;debug config:type=&quot;boolean&quot;&gt;false&lt;/debug&gt;
+ &lt;feedback
config:type=&quot;boolean&quot;&gt;true&lt;/feedback&gt;
+ &lt;/script&gt;
+ &lt;dialog config:type=&quot;integer&quot;&gt;0&lt;/dialog&gt;
+ &lt;element config:type=&quot;integer&quot;&gt;0&lt;/element&gt;
+ &lt;!-- deprecated since openSUSE 11.0; use pathlist instead
+ &lt;path&gt;networking,dns,hostname&lt;/path&gt;
+ --&gt;
+ &lt;pathlist config:type="list"&gt;
+ &lt;path&gt;networking,dns,hostname&lt;/path&gt;
+ &lt;/pathlist&gt;
+ &lt;question&gt;Enter Hostname&lt;/question&gt;
+ &lt;default&gt;enter your hostname here&lt;/default&gt;
+ &lt;/ask&gt;
+</screen>
+</para>
+</para>
+
+
+ </section>
+

Added: trunk/autoinstallation/doc/xml/BootMedia.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/BootMedia.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/BootMedia.xml (added)
+++ trunk/autoinstallation/doc/xml/BootMedia.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,57 @@
+ <section id="choosingbootmedia">
+ <title>Choosing the right Boot Medium</title>
+ <para>
+ There are different methods for booting the client. The computer can
boot from
+ its network interface card (NIC) to receive the boot images via
&dhcp; /TFTP
+ or a suitable kernel as well as an initrd image are loaded from a
+ floppy or a boot-able CD-ROM.
+ </para>
+ <section id="bootfromfloppy">
+ <title>
+ Booting from a floppy
+ </title>
+ <para>
+ For testing/rescue purposes or because the NIC does not have a PROM
or PXE
+ you can build a boot floppy to use with &autoyast2;. Using a floppy
+ to initiate an auto-install process is limited due to the size of
the
+ data a floppy can hold. However, it is still possible to use
+ floppies when auto-installing a single, disconnected machine.
+ </para>
+ <para>
+ Floppies can be used to store the control file, especially when
using
+ the original &company-suse; CD-ROMs for a single, disconnected
machine. Using the
+ kernel command line, you can specify the location of the control
+ file on the floppy. (See <quote><link linkend='BootFromFloppy'
+ endterm="BootFromFloppy.title"></link></quote>)
+ </para>
+ <para>
+ Even without specifying any command line options, it is still
possible to initiate the
+ auto-install process by placing a control file on a floppy with a
+ special, pre-defined file name. (<filename>autoinst.xml</filename>)
&yast2; will check for
+ <filename>autoinst.xml</filename> upon startup and if it was found
it
+ will switch from interactive to automated installation.
+ </para>
+ </section>
+
+ <section id="bootfromcd">
+ <title>Booting from CD-ROM</title>
+ <para>
+ You can use the original &company-suse; CD-ROMs in combination
with other
+ media, i.e. with a floppy to hold the control file or in combination
+ with network where the control file can be located.
+ </para>
+ <para>
+ It is also possible to create customized CD-ROMs to hold only the
+ package you need in addition to the control file which also can be
+ saved on the CD-ROM. This method requires creation of CD-ROMs
+ every time you wish to change the configuration though.
+ </para>
+ </section>
+ </section>
+
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast2.xml" "chapter" "section")
+ End:
+ -->
\ No newline at end of file

Added: trunk/autoinstallation/doc/xml/BootloaderSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/BootloaderSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/BootloaderSection.xml (added)
+++ trunk/autoinstallation/doc/xml/BootloaderSection.xml Mon Aug 8 14:12:13
2011
@@ -0,0 +1,572 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+<section id="CreateProfile.Bootloader">
+ <title>The Boot loader</title>
+ <para>This documentation is for yast2-bootloader and is is valid for SLE11
and openSUSE 11.0+. For older versions please use the documentation that comes
with your distribution in /usr/share/doc/packages/autoyast2/</para>
+ <para>
+ General scope of autoyast profile only bootloader part.
+ <screen>
+&lt;bootloader&gt;
+ &lt;device_map config:type=&quot;list&quot;&gt;
+ - info about order of devices in device.map
+ &lt;/device_map&gt;
+ &lt;global&gt;
+ - info about configuration of installation (installation settings for GRUB
and generic boot code)
+ &lt;/global&gt;
+ &lt;initrd_modules config:type=&quot;list&quot;&gt;
+ - list of initrd modules
+ &lt;/initrd_modules&gt;
+ &lt;loader_type&gt;grub&lt;/loader_type&gt; - type of bootloader
+ &lt;sections config:type=&quot;list&quot;&gt;
+ - bootloader sections in menu.lst
+ &lt;/sections&gt;
+ &lt;/bootloader&gt;
+</screen>
+</para>
+ <section><title>Device map</title>
+<para>
+You can define devices and their order in device.map but it is not necessary.
yast2-bootloader checks the devices during the installation and proposes a
device.map by itself. It can happen that the order of the devices is wrong or
you have defined a different order than it is in the BIOS (please take care
about changes there. it can leads to unbootable system).
+</para>
+<screen>
+&lt;device_map config:type=&quot;list&quot;&gt;
+ &lt;device_map_entry&gt;
+ &lt;firmware&gt;hd0&lt;/firmware&gt; &lt;!-- order of devices in target
map --&gt;
+ &lt;linux&gt;/dev/disk/by-id/ata-ST3500418AS_6VM23FX0&lt;/linux&gt;
&lt;!-- name of device (disk) --&gt;
+ &lt;/device_map_entry&gt;
+&lt;/device_map&gt;
+</screen>
+ </section>
+ <section><title>Globals</title>
+ <para>
+ This is an important part where you can define where to install GRUB and
also how the boot process will work. It is not necessary to define this part as
mentioned before, yast2-bootloader proposes a configuration by itself and so
this is optional. Usually the AutoYaST profile includes only this part and all
other parts are added automatically during installation by yast2-bootloader.
Unless you have some special needs, you don't have to specify the bootloader
config in the XML file.
+<screen>
+ &lt;global&gt;
+ &lt;activate&gt;true&lt;/activate&gt;
+ &lt;default&gt;openSUSE 11.2 - 2.6.31.5-0.1&lt;/default&gt;
+ &lt;gfxmenu&gt;(hd0,1)/boot/message&lt;/gfxmenu&gt;
+ &lt;lines_cache_id&gt;4&lt;/lines_cache_id&gt;
+ &lt;timeout config:type=&quot;integer&quot;&gt;10&lt;/timeout&gt;
+ &lt;/global&gt;
+</screen>
+ </para>
+<para>
+ <table frame='top'>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>activate</entry>
+ <entry>
+ <para>set boot flag on boot partition. The boot partition can be "/"
if there is no separate /boot partition. If the boot partition is on logical
partition, the boot flag is set to the extended partition.
+ </para>
+ <para><screen>&lt;activate&gt;true&lt;/activate&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>default</entry>
+ <entry>
+ <para>
+ name(title) of the default boot section from menu.lst
+ </para>
+ <para><screen>&lt;default&gt;openSUSE 11.2 -
2.6.31.5-0.1&lt;/default&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>gfxmenu</entry>
+ <entry>
+ <para>
+ path to the graphical boot menu (/boot/message). 'none' means
don't use graphical boot menu
+ </para>
+
<para><screen>&lt;gfxmenu&gt;(hd0,1)/boot/message&lt;/gfxmenu&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>timeout</entry>
+ <entry>
+ <para>
+ timeout in seconds for automatic booting the default boot section
from menu.lst
+ </para>
+ <para><screen>&lt;timeout
config:type="integer"&gt;10&lt;/timeout&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>generic_mbr</entry>
+ <entry>
+ <para>
+ write generic boot code to MBR. (It is ignored if boot_mbr is set
to true)
+ </para>
+
<para><screen>&lt;generic_mbr&gt;false&lt;/generic_mbr&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>boot_mbr</entry>
+ <entry>
+ <para>
+ write GRUB to MBR of the first disk in the order (device.map
include order of disks)
+ </para>
+ <para><screen>&lt;boot_mbr&gt;false&lt;/boot_mbr&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>boot_boot</entry>
+ <entry>
+ <para>
+ write GRUB to separate /boot partition (if separate /boot
partition missing GRUB will be written to "/")
+ </para>
+ <para><screen>&lt;boot_boot&gt;false&lt;/boot_boot&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>boot_root</entry>
+ <entry>
+ <para>
+ write GRUB to "/" partition
+ </para>
+ <para><screen>&lt;boot_root&gt;false&lt;/boot_root&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>boot_extended</entry>
+ <entry>
+ <para>
+write GRUB to the extended partition (it is important if you want to use a
generic boot code and the "boot" partition is logical) NOTE: if the boot
partition is logical it should use boot_mbr (write GRUB to MBR) instead of
generic_mbr.
+ </para>
+
<para><screen>&lt;boot_extended&gt;false&lt;/boot_extended&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>boot_custom</entry>
+ <entry>
+ <para>
+ write GRUB to custom device.
+ </para>
+
<para><screen>&lt;boot_custom&gt;/dev/sda3&lt;/boot_custom&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>trusted_grub</entry>
+ <entry>
+ <para>
+ use trusted GRUB instead of the classical GRUB (gfxmenu is deleted
automatically if this option is true) please doesn't use trusted GRUB if your
hardware doesn't support it.
+ </para>
+
<para><screen>&lt;trusted_grub&gt;false&lt;/trusted_grub&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>lines_cache_id</entry>
+ <entry>
+ <para>
+ internal option which means cache id for perl-Bootloader. Please
don't use it or change it in a cloned XML file.
+ </para>
+ <para><screen></screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ </tbody>
+ </tgroup>
+</table>
+</para>
+ </section>
+ <section><title>Initrd modules </title>
+<para>
+ This is a list of initrd modules. It is not necessary to add this part it
should be added automatically. Please don't modify it if you are not sure what
the initrd modules are.
+</para>
+ </section>
+ <section><title>Loader Type</title>
+ <para>
+ This part defines the type of the bootloader. It could be grub, lilo,
ppc or elilo.
+ </para>
+ <screen>
+&lt;loader_type&gt;grub&lt;/loader_type&gt;
+ </screen>
+ </section>
+ <section><title>Sections</title>
+ <para>
+This includes the configuration of the boot sections in the menu.lst. This
part is added by yast2-bootloader during installation automatically. It is good
to know that yast2-bootloader deletes boot sections with no valid kernel and
initrd path. It also deletes such boot sections.
+ </para>
+<screen>
+ &lt;sections config:type=&quot;list&quot;&gt;
+ &lt;section&gt;
+ &lt;append&gt;resume=/dev/disk/by-id/raid-sil_ajacccbhejai-part2
splash=silent quiet showotps&lt;/append&gt;
+ &lt;image&gt;(hd0,0)/vmlinuz-2.6.31-10-default&lt;/image&gt;
+ &lt;initial&gt;1&lt;/initial&gt;
+ &lt;initrd&gt;(hd0,0)/initrd-2.6.31-10-default&lt;/initrd&gt;
+ &lt;lines_cache_id&gt;0&lt;/lines_cache_id&gt;
+ &lt;name&gt;openSUSE 11.2 Milestone 8 - 2.6.31-10 (default)&lt;/name&gt;
+ &lt;original_name&gt;linux&lt;/original_name&gt;
+ &lt;root&gt;/dev/mapper/sil_ajacccbhejai_part3&lt;/root&gt;
+ &lt;type&gt;image&lt;/type&gt;
+ &lt;vgamode&gt;0x31a&lt;/vgamode&gt;
+ &lt;/section&gt;
+ &lt;section&gt;
+ &lt;append&gt;resume=/dev/disk/by-id/raid-sil_ajacccbhejai-part2
splash=silent quiet showopts&lt;/append&gt;
+ &lt;image&gt;(hd0,0)/vmlinuz-2.6.31-10-xen&lt;/image&gt;
+ &lt;initrd&gt;(hd0,0)/initrd-2.6.31-10-xen&lt;/initrd&gt;
+ &lt;lines_cache_id&gt;2&lt;/lines_cache_id&gt;
+ &lt;name&gt;Xen -- openSUSE 11.2 Milestone 8 - 2.6.31-10&lt;/name&gt;
+ &lt;nounzip&gt;0&lt;/nounzip&gt;
+ &lt;original_name&gt;xen&lt;/original_name&gt;
+ &lt;root&gt;/dev/mapper/sil_ajacccbhejai_part3&lt;/root&gt;
+ &lt;type&gt;xen&lt;/type&gt;
+ &lt;vgamode&gt;0x31a&lt;/vgamode&gt;
+ &lt;xen&gt;(hd0,0)/xen.gz&lt;/xen&gt;
+ &lt;xen_append&gt;&lt;/xen_append&gt;
+ &lt;/section&gt;
+ &lt;section&gt;
+ &lt;blockoffset&gt;1&lt;/blockoffset&gt;
+ &lt;chainloader&gt;/dev/fd0&lt;/chainloader&gt;
+ &lt;lines_cache_id&gt;3&lt;/lines_cache_id&gt;
+ &lt;name&gt;Floppy&lt;/name&gt;
+ &lt;noverifyroot&gt;true&lt;/noverifyroot&gt;
+ &lt;original_name&gt;floppy&lt;/original_name&gt;
+ &lt;type&gt;other&lt;/type&gt;
+ &lt;/section&gt;
+ &lt;/sections&gt;
+</screen>
+</section>
+ <section><title>Options</title>
+ <para>
+the options depend on the <emphasis>type</emphasis>.
+ </para>
+ <section><title>Options for section type: image and xen</title>
+ <table frame='top'>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>append</entry>
+ <entry>
+ <para>
+ list of kernel args but without(!) vga= and root=
+ </para>
+ <para><screen>&lt;append&gt;splash=silent quiet
showopts&lt;/append&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>image</entry>
+ <entry>
+ <para>
+ path to the kernel
+ </para>
+
<para><screen>&lt;image&gt;(hd0,0)/vmlinuz-2.6.31-10&lt;/image&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>initrd</entry>
+ <entry>
+ <para>
+ path to the initrd
+ </para>
+
<para><screen>&lt;initrd&gt;(hd0,0)/my-initrd&lt;/initrd&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>lines_cache_id</entry>
+ <entry>
+ <para>
+ internal option which means cache id for perl-Bootloader. Please
don't use it or change it in a cloned XML file.
+ </para>
+ <para><screen></screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>name</entry>
+ <entry>
+ <para>
+ name of section
+ </para>
+ <para><screen>&lt;name&gt;Productive
System&lt;/name&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>original_name</entry>
+ <entry>
+ <para>
+ internal name of section parsed by YaST from a comment in the
config file. There are some rules for names and original_name helps to
determine if boot section is linux or failsafe and for chainloader it helps to
determine if it is windows or other linux/floppy etc. Please use simple
original_name: linux, xen, windows, floppy etc.
+ </para>
+
<para><screen>&lt;original_name&gt;linux&lt;/original_name&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>root</entry>
+ <entry>
+ <para>
+ location of the root partition ("/")
+ </para>
+
<para><screen>&lt;root&gt;/dev/mapper/sil_ajacccbhejai_part3&lt;/root&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>type</entry>
+ <entry>
+ <para>
+ type of section it could (image/xen/other/menu)
+ </para>
+ <para><screen>&lt;type&gt;xen&lt;/type&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>vgamode</entry>
+ <entry>
+ <para>
+ kernel arg for vga (vga=)
+ </para>
+ <para><screen>&lt;vgamode&gt;0x31a&lt;/vgamode&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>xen</entry>
+ <entry>
+ <para>
+ path to xen.gz
+ </para>
+ <para><screen>&lt;xen&gt;(hd0,0)/xen.gz&lt;/xen&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>xen_append</entry>
+ <entry>
+ <para>
+ kernel args for XEN
+ </para>
+ <para><screen>&lt;xen_append&gt;&lt;/xen_append&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ </tbody>
+ </tgroup>
+</table>
+ </section>
+ <section><title>Options for section type: other (chainloader)</title>
+ <table frame='top'>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>lines_cache_id</entry>
+ <entry>
+ <para>
+ internal option which means cache id for perl-Bootloader. Please
don't use it or change it in a cloned XML file.
+ </para>
+ <para><screen></screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>name</entry>
+ <entry>
+ <para>
+ name or title of section
+ </para>
+ <para><screen>&lt;name&gt;Floppy&lt;/name&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>original_name</entry>
+ <entry>
+ <para>
+ internal name of section parsed by YaST from a comment in the
config file. There are some rules for names and original_name helps to
determine if boot section is linux or failsafe and for chainloader it helps to
determine if it is windows or other linux/floppy etc. Please use simple
original_name: linux, xen, windows, floppy etc.
+ </para>
+
<para><screen>&lt;original_name&gt;linux&lt;/original_name&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>type</entry>
+ <entry>
+ <para>
+ type of section it could (image/xen/other/menu)
+ </para>
+ <para><screen>&lt;type&gt;other&lt;/type&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>blockoffset</entry>
+ <entry>
+ <para>
+ offset in chainloader (used only in grub)
+ </para>
+ <para><screen>&lt;blockoffset&gt;1&lt;/blockoffset&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>chainloader</entry>
+ <entry>
+ <para>
+ partition part for chainloader (so chainloader+blockoffset get
final chainloader item in grub)
+ </para>
+
<para><screen>&lt;chainloader&gt;/dev/fd0&lt;/chainloader&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>noverifyroot</entry>
+ <entry>
+ <para>
+ with/without checking root
+ </para>
+
<para><screen>&lt;noverifyroot&gt;true&lt;/noverifyroot&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>remap</entry>
+ <entry>
+ <para>
+ it is special for windows and it means remapping disk which makes
the second disk the first e.g. map (hd0) (hd1) map (hd1) (hd0)
+ </para>
+ <para><screen>&lt;remap&gt;false&lt;/remap&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>makeactive</entry>
+ <entry>
+ <para>
+ add the makeactive argument for chainloader section
+ </para>
+
<para><screen>&lt;makeactive&gt;false&lt;/makeactive&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ </tbody>
+ </tgroup>
+</table>
+</section>
+ <section><title>Options for section type: menu (configfile)</title>
+ <table frame='top'>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>lines_cache_id</entry>
+ <entry>
+ <para>
+ internal option which means cache id for perl-Bootloader. Please
don't use it or change it in a cloned XML file.
+ </para>
+ <para><screen></screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>name</entry>
+ <entry>
+ <para>
+ name or title of section
+ </para>
+ <para><screen>&lt;name&gt;Floppy&lt;/name&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>original_name</entry>
+ <entry>
+ <para>
+ internal name of section parsed by YaST from a comment in the
config file. There are some rules for names and original_name helps to
determine if boot section is linux or failsafe and for chainloader it helps to
determine if it is windows or other linux/floppy etc. Please use simple
original_name: linux, xen, windows, floppy etc.
+ </para>
+
<para><screen>&lt;original_name&gt;linux&lt;/original_name&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>type</entry>
+ <entry>
+ <para>
+ type of section it could (image/xen/other/menu)
+ </para>
+ <para><screen>&lt;type&gt;other&lt;/type&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>configfile</entry>
+ <entry>
+ <para>
+ path to menu.lst config file
+ </para>
+ <para><screen>&lt;configfile&gt;1&lt;/configfile&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>root</entry>
+ <entry>
+ <para>
+ device name for loading menu.lst from other installation of linux
+ </para>
+ <para><screen>&lt;root&gt;/dev/sda1&lt;/root&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ </tbody>
+ </tgroup>
+</table>
+</section>
+</section>
+</section>
+

Added: trunk/autoinstallation/doc/xml/CreateProfile.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/CreateProfile.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/CreateProfile.xml (added)
+++ trunk/autoinstallation/doc/xml/CreateProfile.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,168 @@
+
+ <chapter id="CreateProfile">
+ <title >Creating A Control File</title>
+
+ <section id="Autoinstallation.collectInfo">
+ <title>Collect information</title>
+ <para>
+ In order to create the control file, first you need to collect
+ information about the systems your are going to
+ install. This includes among other things hardware data and network
+ information. Make sure you know the following about the machines you
want to install:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>Hard disk types and sizes</para>
+ </listitem>
+ <listitem>
+ <para>Graphic interface and attached monitor if any</para>
+ </listitem>
+ <listitem>
+ <para>Network interface and MAC address if known (i.e. when using
&dhcp;)</para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ With these parameters you are ready to go and create a profile of your
systems
+ to control the auto-installation process.
+ </para>
+ </section>
+ <section id="CreateProfile.CMS">
+ <title>
+ Using the Configuration Management System
+ </title>
+ <para>
+ In order to create the control file for one or more computers, a
configuration
+ interface based on &yast2; is provided. This system depends on existing
modules
+ which are usually used to configure a computer in regular operation mode,
+ i.e. after &company-suse; Linux is installed.
+ </para>
+ <para>
+ The configuration management system lets you create control files easily
and
+ additionally it lets you manage a repository of configurations for use
+ in a networked environment and with multiple clients.
+ </para>
+ <figure>
+ <title>Configuration System</title>
+ <mediaobject>&autoyast2-maindialog;</mediaobject>
+ </figure>
+
+ <section>
+ <title>Creating a new Profile</title>
+ <para>
+ With some exceptions, almost all resources of the control file can
+ be configured using the configuration management system. The system
+ offers flexibility and configuration of some resources is
+ identical to this available in the &yast2; Control Center. In
+ addition to the existing and familiar modules new
+ interfaces were created for special and complex configurations,
+ for example for partitioning, general options and software.
+ </para>
+ <para>
+ Furthermore, using the &cms; guarantees that the resulting control file
is
+ valid and insures that it can be used directly to start automated
installation.
+ </para>
+ <para>
+ Make sure the configuration system is installed (package
+ <emphasis>autoyast2</emphasis>) and call it using the <emphasis>YaST2
+ Control Center</emphasis> or call it directly as root with the
+ following command (make sure the <emphasis>DISPLAY</emphasis> variable
is set correctly to
+ start the graphical user interface instead of the text based one):
+ </para>
+ <screen>
+/sbin/yast2 autoyast
+ </screen>
+
+ </section>
+
+
+ </section>
+
+ <section id="CreateProfile.Manual">
+ <title>Creating/Editing a Control File Manually</title>
+ <para>
+ If you edit the control file manually, make sure it has a valid syntax.
To
+ check the syntax, use some tools already available
+ on the distribution. For example to verify that the file is well
+ formed, use the utility <command>xmllint</command> available with the
+ <emphasis>libxml2</emphasis> package:
+ </para>
+ <screen>
+xmllint &lt;control file&gt;
+ </screen>
+ <para>
+ If the control file is not well formed, i.e. if a tag is not closed,
+ <command>xmllint</command> will report about the errors.
+ </para>
+ <para>
+ Before going on with the auto-installation, please fix any errors
+ resulting from such checks. The auto-installation process can't be
+ started with an invalid and non-well formed control file.
+ </para>
+
+ <para>
+ You can use any XML editor available on your system or use your
+ favorite text editor with XML support (i.e. Emacs, Vim). However, it is
not quite
+ optimal to create the control file manually for large number of machines
+ and it should only be seen as an interface between the auto-installation
+ engine and the Configuration Management System (<abbrev>CMS</abbrev>).

+ </para>
+
+ <figure id="kxmleditor">
+ <title id="kxmleditor.title" >Editing the control file with
<command>kxmledit</command></title>
+ <mediaobject>&kxmleditor;</mediaobject>
+ </figure>
+
+ </section>
+
+ <section id="CreateProfile.XSLT">
+ <title>Creating a Profile (control file) via Script with XSLT</title>
+ <para>
+ For the case you have a template and just want to change a few things
via script or command line,
+ you can use a XSLT processor like <emphasis>sablot</emphasis> for this.
Lets say you have an autoyast profile
+ and you want to fillout the hostname via script for any reason (maybe
because you have to do it
+ so often, you want to script it)
+ </para>
+ <para>
+ First you have to create an XSL file
+ </para>
+ <example>
+ <title>Example file for replacing hostname/domain by script</title>
+ <screen><xi:include href="examples/example.add_hostname.xsl"
parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+ <para>
+ As you can see, this file expects the "hostname" and the "domain" as
parameters from the user.
+ <screen>&lt;xsl:param name="hostname"/&gt;
+&lt;xsl:param name="domain"/&gt;</screen>
+ There will be a "copy" of those parameters in the "dns" section of the
control file. That means,
+ if there already is a domain element in the dns section, you'll get a
second one (no good).
+ </para>
+ <para>
+ If you want to create a new autoyast profile now from the template plus
the XSL file, run the following command:
+ <screen>sabcmd add_hostname.xsl \$hostname=myHost \$domain=my.domain
template.xml</screen>
+ You'll get a filled out autoyast profile then on STDOUT.
+ </para>
+ <para>
+ If you have multiple XSL files you want to apply to a template, do it
like this
+ <screen>
+ sabcmd add_hd_vg.xsl \$device=/dev/sda \$partition=p2 \$vg=system \
+ | sabcmd add_harddisk.xsl \$device=/dev/system \$lvm=true \
+ | sabcmd ....
+ | sabcmd add_hostname.xsl \$hostname=myHost \$domain=my.domain
+ </screen>
+ So you just pipe the output of each sabcmd to the next sabcmd.
+ </para>
+ <para>
+ For more information aout XSLT, go to the official webpage <ulink
url="http://www.w3.org/TR/xslt";>www.w3.org/TR/xslt</ulink>
+ </para>
+ </section>
+
+ </chapter>
+
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast.xml" "book" "chapter")
+ End:
+ -->

Added: trunk/autoinstallation/doc/xml/CreateProfileDetails.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/CreateProfileDetails.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/CreateProfileDetails.xml (added)
+++ trunk/autoinstallation/doc/xml/CreateProfileDetails.xml Mon Aug 8 14:12:13
2011
@@ -0,0 +1,74 @@
+ <chapter id="configuration">
+ <title>Configuration and Installation Options</title>
+ <para>
+ This chapter introduces important parts of a control file for
+ standard purposes. To have an idea about the other options available,
+ use the configuration management system.
+ </para>
+ <para>
+ Note that for some of the configuration options to work, additional
+ packages have to be installed, depending on the software selection you
+ have configured. If you choose to install <emphasis>Minimal</emphasis>
+ then some packages might be missing and those have to be added to the
+ individual package selection.
+ </para>
+ <para>
+ YaST will install packages required by YaST modules in the second phase
+ of the installation and before the post-installation phase of AutoYaST
+ has started, however if the YaST modules are not available in the
+ system, this will not happen. For example, no security settings will be
+ configured if <emphasis>yast2-security</emphasis> is not installed.
+ </para>
+
+ <xi:include href="GeneralSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="ReportSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="BootloaderSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="PartitioningSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="SoftwareSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="RunlevelSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="NetworkSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="NISSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="LDAPSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="NFSSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="NTPSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="MailSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="SecuritySection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="X11Section.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="UsersSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="ScriptsSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="SysconfigSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="FilesSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="ASKSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="KDumpSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ <section id="CreateProfile.Hardware">
+ <title>
+ Miscellaneous hardware and system components
+ </title>
+
+ <para>
+ In addition to the core component configuration, like network
+ authentication and security, &autoyast;2 offers a wide range of
+ hardware and system configuration which is available by default on
+ any system installed manually and in an interactive way. For
+ example, it is possible to configure printers, sound devices, TV
+ cards and any other hardware components which have a module within YaST2.
+ </para>
+ <para>
+ Any new configuration options that will be added to &yast2; will be
+ automatically available as an auto-installation resource.
+ </para>
+
+
+
+ <xi:include href="PrinterSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ <xi:include href="SoundSection.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </section>
+
+ </chapter>
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast.xml" "book" "chaper")
+ End:
+ -->

Added: trunk/autoinstallation/doc/xml/FilesSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/FilesSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/FilesSection.xml (added)
+++ trunk/autoinstallation/doc/xml/FilesSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,59 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+ <section id="createprofile.completeconf">
+ <title>Adding complete configurations</title>
+ <para>
+ For many applications and services you might have prepared a
+ configuration file which should be copied in a complete form to some
+ location in the installed system. This is for example if you are
+ installing a web server and have a <emphasis>ready to go</emphasis>
+ server configuration file (<filename>httpd.conf</filename>).
+ </para>
+ <para>
+ Using this resource, you can embed the file into the control file by
+ specifying the final path on the installed system. &yast2; will copy this
+ file to the specified location.
+ </para>
+ <para>
+ This feature requires the autoyast2 package to be installed. If the
package is
+ missing, AutoYaST will silently ignore the <emphasis>files</emphasis>
section.
+ Since openSUSE 11.1 and SLES11 AutoYaST will install the package on it's
own if
+ it's missing.
+ </para>
+ <para>
+ Since openSUSE 11.1 and SLES11 you can specify a
<emphasis>file_location</emphasis>
+ where the file should be retrieved from, like an HTTP server for
example. That would
+ look like this
<emphasis>&lt;file_location&gt;http://my.server.site/issue&lt;/file_location&gt;</emphasis>
+ </para>
+ <para>
+ Since openSUSE 11.2 (not SLES11) you can create directories by
specifying a file_path that ends with a slash.
+ </para>
+ &example.files;
+
+ <para>
+ A more advanced example is shown below. This configuration will create
+ a file using the content supplied in <emphasis>file_contents</emphasis>
+ and will change the permissions and ownership of the file. After the
+ file has been copied to the system, a script is executed which can be
+ used to manipulate the file and prepare it for the environment of the
client.
+ </para>
+ &example.filesadv;
+ </section>
+

Added: trunk/autoinstallation/doc/xml/GeneralSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/GeneralSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/GeneralSection.xml (added)
+++ trunk/autoinstallation/doc/xml/GeneralSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,215 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+
+ <section id="CreateProfile.General">
+ <title id="CreateProfile.General.title">
+ General Options
+ </title>
+
+ <para>
+ General
+ options include all the settings related to the installation process and
+ the environment of the installed system.
+ </para>
+ <example>
+ <title>General Options</title>
+ <para>
+ The mode section configures the behavior of AutoYaST when it comes to
confirmation and rebooting. The following has to be in the
&lt;general&gt;&lt;mode&gt; section
+ </para>
+ <para>
+ By default, the auto-installation process has to be confirmed by the
+ user. The confirmation should be disabled if a fully unattended
+ installation is desired. This option is used to view and change the
+ settings on a target system before anything is committed and can be
+ used for debugging. It is set to <emphasis>true</emphasis> by default
+ to avoid recursive installs when the system schedules a reboot after
+ initial system setup.
+ </para>
+ <para>
+ With <emphasis>halt</emphasis> you make autoyast to turn off the machine
+ after all packages have been installed. So instead of the reboot into
+ stage two, the machine is turned off. The bootloader is alreay installed
+ and all your chroot scripts have run.
+ </para>
+ <para>
+ <emphasis>final_halt</emphasis> and <emphasis>final_reboot</emphasis> are
new
+ with openSUSE 11.0 and SLES11. You can reboot or halt the machine,
+ when everything with installation and configuration is done, with that.
+ </para>
+ <para>
+ openSUSE 11.0 uses the kexec feature and does not reboot anymore between
stage1 and stage2. With
+ the <emphasis>forceboot</emphasis> option you can force the reboot in
case you need it for some
+ reason. true will reboot, false will not reboot and a missing
<emphasis>forceboot</emphasis> option
+ uses the products default.
+ </para>
+ <para>
+ <table frame='top'>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>confirm</entry>
+ <entry>if this boolean is set to "true" the installation stops at
the confirmation screen (also called proposal screen) and has to be confirmed
with the "install"-button.
+ <para><screen>&lt;confirm
config:type="boolean"&gt;true&lt;/confirm&gt;</screen></para>
+ </entry>
+ <entry>optional. The default is true</entry>
+ </row>
+ <row>
+ <entry>halt</entry>
+ <entry>shut down the machine after the first stage. So if you turn
it on again, the machine boots and the second stage of the autoinstallation
starts
+ <para><screen>&lt;halt
config:type="boolean"&gt;true&lt;/halt&gt;</screen></para>
+ </entry>
+ <entry>optional. The default is false</entry>
+ </row>
+ <row>
+ <entry>second_stage</entry>
+ <entry>this boolean configures if AutoYaST will run in the second
stage too (after the partitioning, software and bootloader installation of the
first stage). If you set this to false, a normal manual installation happens in
the second stage.
+ <para><screen>&lt;second_stage
config:type="boolean"&gt;true&lt;/second_stage&gt;</screen></para>
+ </entry>
+ <entry>optional. The default is true</entry>
+ </row>
+ <row>
+ <entry>final_reboot</entry>
+ <entry>if you set this to true, the machine will reboot at the
very end of the installation (when everything is installed and configured at
the end of the second stage)
+ <para><screen>&lt;final_reboot
config:type="boolean"&gt;true&lt;/final_reboot&gt;</screen></para>
+ </entry>
+ <entry>optional. The default is false. It makes no sense to set
this <emphasis>and</emphasis> final_halt to true. This options is available
since openSUSE 11.0 and SLES11</entry>
+ </row>
+ <row>
+ <entry>final_halt</entry>
+ <entry>if you set this to true, the machine will shutdown at the
very end of the installation (when everything is installed and configured at
the end of the second stage)
+ <para><screen>&lt;final_halt
config:type="boolean"&gt;true&lt;/final_halt&gt;</screen></para>
+ </entry>
+ <entry>optional. The default is false. It makes no sense to set
this <emphasis>and</emphasis> final_reboot to true. This options is available
since openSUSE 11.0 and SLES11</entry>
+ </row>
+ <row>
+ <entry>forceboot</entry>
+ <entry>Some openSUSE releases use kexec to avoid the reboot after
the first stage. They immediately boot into the installed system. You can force
a reboot with this
+ <para><screen>&lt;forceboot
config:type="boolean"&gt;true&lt;/forceboot&gt;</screen></para>
+ </entry>
+ <entry>optional. The default is false.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+
+
+<screen>
+ <xi:include href="examples/example.generalOptions.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+
+
+ <para>
+ AutoYaST in openSUSE 11.1 allows you to configure the proposal screen
with the &lt;proposals config:type="list"&gt;
+ option in the profile. All proposals that are listed in that section are
shown in the proposal screen if you set the
+ <emphasis>confirm</emphasis> option to true.
+ </para>
+ <para>
+ This is the list of proposals for openSUSE 11.1 are (you can find that
in the control.xml on the installation source too):
+ <itemizedlist>
+ <listitem>
+ <para>
+ partitions_proposal
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ bootloader_proposal
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ country_simple_proposal
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ timezone_proposal
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ users_proposal
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ hwinfo_proposal
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ mouse_proposal
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ software_proposal
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ runlevel_proposal
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ deploying_proposal
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ The wait section was invented with openSUSE 11.1 and SLES11. You can
let AutoYaST sleep before and after each module during the second stage.
+ You can run scripts and/or you can pass a value (in seconds) for
AutoYaST to sleep. In the example above AutoYaST will sleep for 15 seconds
(10+5) before
+ the network configuration happens and 10 seconds (3+7) after the
network configuration is done. The scripts in the example don't really make a
lot of sense
+ because you could pass that value as "time" value too but I think you
get how scripts in the wait section work now.
+ </para>
+ <note>
+ <title>Change starting from SUSE Linux 10.1/SLES10</title>
+ <para>
+ The <emphasis>language</emphasis>, <emphasis>keyboard</emphasis> and
+ <emphasis>clock</emphasis> properties in the <emphasis>general</emphasis>
+ resource were moved to the root (<emphasis>profile</emphasis>)
element of
+ the autoyast profile. So don't use them in the general section anymore.
+ </para>
+ <para>
+ Since now you can use the <emphasis>second_stage</emphasis> property,
which
+ can turn off autoyast after the first reboot. So the complete second
stage is
+ a manual installation (default is true, which means that autoyast is
doing a
+ complete installation). Since openSUSE 11.0 you can set the boolean
<emphasis>final_reboot</emphasis>
+ and <emphasis>final_halt</emphasis> to reboot/turn off the machine at
the end of stage two.
+ </para>
+ <para>
+ For the signature-handling, please read the
<emphasis>Software</emphasis> chapter
+ of this documentation.
+ </para>
+ </note>
+ </section>
+

Added: trunk/autoinstallation/doc/xml/Installation.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Installation.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/Installation.xml (added)
+++ trunk/autoinstallation/doc/xml/Installation.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,786 @@
+
+<chapter id="Invoking">
+ <title>The Auto-Installation Process</title>
+ <section id="Installation.process">
+
+ <title>
+ Introduction
+ </title>
+ <para>
+ After the system has booted and the control file has been retrieved,
+ &yast2; performs configuration of the system according to the information
+ provided in the control file. All the configuration is summarized in a
window that is shown by
+ default and should be deactivated if a full automatic installation is
+ needed.
+ </para>
+ <para>
+ When &yast2; has reached the point where the summary of the
configuration is shown,
+ &yast2; has only probed hardware and prepared the system for
+ auto-installation, thus, nothing has been changed in the system yet, so
+ that in case of any error, the process still can be aborted.
+ </para>
+
+ <para>
+ A system should be automatically installable without the need to have
+ any graphic adaptor or monitor. Having a monitor attached to the
+ client machine is nevertheless recommended to follow the process and
+ to get feedback in case of any errors. Choosing between the Qt and the
+ Ncurses interfaces is possible. For headless
+ clients, system messages can be monitored using the serial console.
+ </para>
+ <section id="Installation.Interface.X11">
+ <title>
+ X11 Interface
+ </title>
+ <para>
+ This is the default interface while auto-installing. No special
+ variables are required to activate it.
+ </para>
+ </section>
+ <section id="Installation.Interface.SerialConsole">
+ <title>
+ Serial console
+ </title>
+ <para>
+ You can start installing a system using the serial console by adding
+ the keyword console (i.e. console=ttyS0) to the command line of the
+ kernel. This will start linuxrc in console mode and later in the
+ process, &yast2; also is started in serial console mode.
+ </para>
+ </section>
+ <section id="Installation.Interface.Ncurses">
+ <title>
+ Text based YaST2-Installation
+ </title>
+ <para>
+ This option can also be activated on the command line. This will start
+ YaST2 in <emphasis>Ncurses</emphasis> mode. To start &yast2; in text
+ mode, add <emphasis>textmode=1</emphasis> on the command line.
+ </para>
+ <para>
+ Starting &yast2; in text mode is recommended when installing a client
+ with less than 64 MB or when X11 is not being configured at all,
+ especially on headless machines.
+ </para>
+ </section>
+ </section>
+
+ <section id="bootmedium">
+ <title>Choosing the right Boot Medium</title>
+ <para>
+ There are different methods for booting the client. The computer can
boot from
+ its network interface card (NIC) to receive the boot images via &dhcp;
/TFTP
+ or a suitable kernel as well as an initrd image are loaded from a
+ floppy or a boot-able CD-ROM.
+ </para>
+ <section>
+ <title>
+ Booting from a floppy
+ </title>
+ <para>
+ For testing/rescue purposes or because the NIC does not have a PROM or
PXE
+ you can build a boot floppy to use with &autoyast2;. Using a floppy
+ to initiate an auto-install process is limited due to the size of the
+ data a floppy can hold. However, it is still possible to use
+ floppies when auto-installing a single, disconnected machine.
+ </para>
+ <para>
+ Floppies can be used to store the control file, especially when using
+ the original &company-suse; CD-ROMs for a single, disconnected
machine. Using the
+ kernel command line, you can specify the location of the control
+ file on the floppy.
+ </para>
+ <para>
+ Even without specifying any command line options, it is still possible
to initiate the
+ auto-install process by placing a control file on a floppy with a
+ special, pre-defined file name. (<filename>autoinst.xml</filename>)
&yast2; will check for
+ <filename>autoinst.xml</filename> upon startup and if it was found it
+ will switch from interactive to automated installation.
+ </para>
+ </section>
+
+ <section>
+ <title>Booting from CD-ROM</title>
+ <para>
+ You can use the original &company-suse; CD-ROMs in combination with
other
+ media, i.e. with a floppy to hold the control file or in combination
+ with network where the control file can be located.
+ </para>
+ <para>
+ It is also possible to create customized CD-ROMs to hold only the
+ package you need in addition to the control file which also can be
+ saved on the CD-ROM. This method requires creation of CD-ROMs
+ every time you wish to change the configuration though.
+ </para>
+ </section>
+
+ <section>
+ <title>Booting via PXE over the network</title>
+ <para>
+ Booting via PXE requires a DHCP and a TFTP server in your network. The
computer
+ will boot then without a physical media like a boot floppy or CDROM.
+ </para>
+ <para>
+ Here is a small example of a "/srv/tftp/pxelinux.cfg/default" file:
+ <screen>
+default SLES9
+
+# install SLES9
+label SLES9
+ kernel linux_sles9
+ append initrd=initrd_sles9 vga=0x0314 install=.... autoyast=...
language=de_DE
+
+# boot harddisc
+label hd·
+ LOCALBOOT 0
+ </screen>
+ </para>
+ <para>
+ It's recommended to add the vga=... parameter with a valid value for
graphical
+ installations, to trigger an installation with the frame buffer device
instead
+ of the vesa driver or ncurses mode.
+ </para>
+ <para>
+ Here is as a small example my "/etc/dhcp.conf" file:
+ <screen>
+option domain-name-servers 192.168.66.1;
+default-lease-time 600;
+max-lease-time 7200;
+ddns-update-style none; ddns-updates off;
+log-facility local7;
+option grub-menufile code 150 = text;
+option grub-menufile "(nd)/menu.lst";·
+subnet 192.168.66.0 netmask 255.255.255.0 {
+ range 192.168.66.100 192.168.66.200;
+ # PXE related stuff ...
+ #
+ # "next-server" defines the tftp server which will·
+ # serve the pxelinux image to the PXE clients.
+ next-server 192.168.66.1;
+ allow booting;
+ allow bootp;
+ option routers 192.168.66.1; # default gateway
+
+ #
+ # "filename" specifies the pxelinux image on the tftp server·
+ # which will be served to the PXE clients.
+ # The configured tftp server on 192.168.100.1 runs in a·
+ # "change-root jail" to /srv/tftpboot
+ filename "pxelinux.0";
+}
+ </screen>
+ </para>
+ <para>
+ A problem you might run into if you do installation via PXE is, that
the
+ installation will run into an endless loop, because after the first
reboot,
+ the machine is doing PXE boot again and will restart the installation
instead
+ of booting from harddisc for the second stage of the installation.
+ </para>
+ <para>
+ This problem can be solved in different ways. One way is to use a http
server
+ to provide the autoyast profile and instead of a static profile, a CGI
script
+ on the webserver is run that provides the profile and then changes the
TFTP server
+ configuration then for this special host, so that the next PXE boot
from that
+ machine will be from harddisc by default.
+ </para>
+ <para>
+ Another way is to use autoyast to upload a new PXE boot configuration
for that host.
+ That is done via autoyast profile like this:
+ <screen>
+ <![CDATA[
+ <pxe>
+ <pxe_localboot config:type="boolean">true</pxe_localboot>
+ <pxelinux-config>
+DEFAULT linux
+ LABEL linux
+ localboot 0
+
+
+ </pxelinux-config>
+ <tftp-server>192.168.66.1</tftp-server>
+ <pxelinux-dir>/pxelinux.cfg</pxelinux-dir>
+ <filename>__MAC__</filename> <!-- since openSUSE 11.2, not SLES11 -->
+ </pxe>
+]]>
+ </screen>
+ This will upload a new configuration for the actual machine to the tftp
server short
+ before the first reboot happens. In most installations the TFTP daemon
runs as user
+ "nobody". You have to make sure that that user has write permissions to
the "pxelinux.cfg"
+ directory if you use that mechanism.
+ So if your machine got the IP address "192.168.66.195" a file
"C0A842C3" will
+ be uploaded and if the machine reboots and will get the same IP address
+ via DHCP again, the new configuration will be used that has the
harddisc as
+ a default boot media.
+ </para>
+ <para>
+ Of course this requires that the machine will get the same IP address
again after the
+ reboot and if you want to do another autoinstallation for that machine,
you have to
+ remove the file from the TFTP server.
+ </para>
+ <para>
+ Since openSUSE 11.2 (not SLES11) you can configure the filename too
that will be uploaded.
+ If you use the "magic" __MAC__ filename, the filename will be the mac
address of your machine like this "01-08-00-27-79-49-ee".
+ A missing filename creates the IP address filename like in the past.
+ </para>
+ </section>
+ </section>
+
+ <section id="invoking_autoinst">
+ <title id="invoking_autoinst.title">
+ Invoking the Auto-Installation process
+ </title>
+
+ <section>
+ <title>Command line Options</title>
+ <para>
+ Adding the command line variable <emphasis>autoyast</emphasis> will make
+ <emphasis>linuxrc</emphasis> start in automated mode.
+ <command>Linuxrc</command> searches for a configuration file, which
+ should be distinguished from the main control file in the following
+ places:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>In the root directory of the initial ram-disk used for booting
+ the system up</para>
+ </listitem>
+ <listitem>
+ <para>In the root directory of the floppy</para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ The configuration file used by <command>linuxrc</command> can have the
+ following keywords (for a detailed description of how linuxrc works and
+ other keywords, see <quote><link linkend='appendix.linuxrc'
+ endterm="appendix.linuxrc.title"></link></quote> ):
+ </para>
+
+ <table frame='top'>
+ <title>Keywords for <command>linuxrc</command></title>
+ <tgroup cols='2'>
+ <thead>
+ <row>
+ <entry>Keyword</entry>
+ <entry>Value</entry>
+ </row>
+ </thead>
+
+
+ <tbody>
+
+ <row><entry>netdevice</entry><entry>Which network device to use for
+ network setup (Device used for &bootp; / &dhcp;
requests)</entry></row>
+ <row><entry>server</entry><entry>Which server to contact for source
directory (NFS Server)</entry></row>
+ <row><entry>serverdir</entry><entry>Directory on NFS Server
</entry></row>
+ <row><entry>hostip</entry><entry>When empty, client sends &bootp;
request, otherwise client is configured with entered IP
configuration.</entry></row>
+ <row><entry>netmask</entry><entry>Netmask</entry></row>
+ <row><entry>gateway</entry><entry>Gateway</entry></row>
+ <row><entry>nameserver</entry><entry>Nameserver</entry></row>
+ <row><entry>insmod</entry><entry>Kernel modules to
load.</entry></row>
+ <row>
+ <entry>autoyast</entry>
+ <entry>Location of the the control file to be used for the
+ automatic installation, i.e
+
<emphasis>autoyast=http://192.168.2.1/profiles/</emphasis></entry>
+
+ </row>
+ <row>
+ <entry>install</entry>
+ <entry>Location of the installation directory, i.e.
<emphasis>install=nfs://192.168.2.1/CDs/</emphasis> </entry>
+ </row>
+ <row>
+ <entry>instmode</entry>
+ <entry>Installation mode, i.e. nfs, http etc. (Not needed if
+ <emphasis>install</emphasis> is set)</entry>
+ </row>
+ <row>
+ <entry>y2confirm</entry>
+ <entry>even with &lt;confirm&gt;no&lt;/confirm&gt; in the
profile, the confirm proposal comes up.
+ This is available since SUSE Linux 10.1 / SLES10
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+
+
+ <para>
+ These variables and keywords will bring the system up to the point
+ where &yast2; can take over with the main control file. Currently, the
+ source medium is
+ automatically discovered, which in some cases makes it possible to
+ initiate the auto-install process without giving any instructions to
+ linuxrc.
+ </para>
+
+ <para>
+ The traditional <command>linuxrc</command> configuration file
+ (<filename>info</filename>) has the function of
+ giving the client enough information about the installation server and
+ the location of the sources. In most cases this file is not needed; it
is however
+ needed in special network environments where &dhcp; / &bootp; are not
+ used or when special kernel modules have to be loaded.
+ </para>
+ <para>
+ All linuxrc keywords
+ can be passed to <command>linuxrc</command> using the kernel command
+ line. The command line can for example also be set when creating
network boot-able
+ images or it can be passed to the kernel using a specially configured
+ &dhcp; server in combination with Etherboot or &pxe;.
+ </para>
+ <para>
+ The format of the special command line variable
+ <emphasis>autoyast</emphasis> can be used as described in table
<quote><link
+ linkend="commandLineAutoYaST"
endterm="commandLineAutoYaST.title"></link></quote>
+ </para>
+
+ <table frame='top' id="commandLineAutoYaST">
+ <title id="commandLineAutoYaST.title">Command line variables for
AutoYaST</title>
+ <tgroup cols='2'>
+ <thead>
+ <row>
+ <entry>
+ Command line variable
+ </entry><entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row><entry>autoyast=default</entry><entry>Default
auto-installation option </entry></row>
+ <row><entry>autoyast=file://&lt;path&gt;</entry><entry>Looks for
+ control file in specified path (relative to source root
+ directory, i.e. <emphasis>file:///autoinst.xml</emphasis> if in
+ the top directory of a CD-ROM and you did an installation from
CD)</entry></row>
+
+ <row>
+ <entry>
+
autoyast=device://&lt;device&gt;/&lt;file&gt;</entry><entry>Looks
+ for control file on a storage device. (only device name needed
+ without full path, i.e. /dev/sda1 is wrong, instead use sda1).
+ Since openSUSE 11.2 (not SLES11) you can leave out the device to
trigger
+ AutoYaST's search routine over all devices. (autoyast=device:///my.xml)
+ </entry>
+ </row>
+
+
+ <row>
+ <entry>autoyast=floppy://&lt;path&gt;</entry>
+ <entry>Looks for control file in the floppy (Useful when booting
+ from CD). Since SLES10 SP1 and later the fallback is looking on
USB devices too</entry>
+ </row>
+ <row>
+ <entry>autoyast=nfs://&lt;server&gt;/&lt;path&gt;</entry>
+ <entry>Looks for control file on &lt;server&gt; </entry>
+ </row>
+ <row>
+
<entry>autoyast=http://[user:password@]&lt;server&gt;/&lt;path&gt;</entry>
+ <entry>Retrieves the control file from a web server using the
HTTP protocol.</entry>
+ </row>
+ <row>
+
<entry>autoyast=https://[user:password@]&lt;server&gt;/&lt;path&gt;</entry>
+ <entry>Retrieves the control file from a web server using HTTPS
(encrypted connection) protocol (possible since SL 10.1 and SLES10</entry>
+ </row>
+ <row>
+ <entry>autoyast=tftp://&lt;server&gt;/&lt;path&gt;</entry>
+ <entry>Retrieve the control file with TFTP</entry>
+ </row>
+ <row>
+
<entry>autoyast=ftp://[user:password@]&lt;server&gt;/&lt;path&gt;</entry>
+ <entry>Retrieve the control file with FTP</entry>
+ </row>
+ <row>
+ <entry>autoyast=usb://&lt;path&gt; (since SLES10 SP1)</entry>
+ <entry>Retrieve the control file from USB devices (autoyast will
search on all USB devices it can find)</entry>
+ </row>
+ <row>
+ <entry>autoyast=relurl://&lt;path&gt; (since openSUSE
11.0)</entry>
+ <entry>Retrieve the control file from the installation source
(install=....)</entry>
+ </row>
+ <row>
+ <entry>autoyast=slp (since openSUSE 11.2, not SLES 11)</entry>
+ <entry>Query the location of the profile from an SLP server
(service:autoyast:...). Since openSUSE 11.3 you can add a "description="
attribute so you can "translate" the URL into something more readable</entry>
+ </row>
+ <row>
+ <entry>autoyast=cifs://&lt;server&gt;/&lt;path&gt; (since
openSUSE 11.2, not SLES 11)</entry>
+ <entry>Looks for control file on &lt;server&gt; with CIFS</entry>
+ </row>
+ <row>
+ <entry>autoyast=label://&lt;label&gt;/&lt;path&gt; (since
openSUSE 11.3, not SLES 11)</entry>
+ <entry>Looks for control file on a device that has the
label</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>
+ Several scenarios for auto-installation are possible using different
+ types of infrastructure and source media. The simplest way is by using
+ the source media from the &company-suse; Box. In that case you have
+ either a DVD with all &company-suse; packages or a set of CD-ROMs. To
initiate the
+ auto-installation process however, the auto-installation command line
+ variable should be entered at system boot-up and the control file should
+ be accessible to YaST2. The following list of scenarios explains how
+ the control file can be supplied and the setup needed for the
+ auto-installation process to be successful.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Using &company-suse; original CD-ROMs from &company-suse; Linux
box:
+ </para>
+ <para>
+ To use the original CD-ROMs, you need a media with the control
+ file, the control file can reside on the following locations:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ <emphasis>Floppy</emphasis>: Control file accessible via the
+ <emphasis>autoyast=floppy</emphasis> option. &yast2; also
searches
+ upon startup for a file named
+ <filename>autoinst.xml</filename>. If such a file is found,
YaST2
+ will switch into auto-installation mode even if no special
+ command line variables were supplied. (See <quote><link
+ linkend="autoinstall.singlesystem"
+ endterm="autoinstall.singlesystem.title"></link></quote> )
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Network</emphasis>: Control file accessible via the
+ <emphasis>autoyast=nfs://..</emphasis>,
+ <emphasis>autoyast=ftp://..</emphasis>
+ <emphasis>autoyast=http://..</emphasis> or
+ <emphasis>autoyast=tftp://..</emphasis> options.
+ </para>
+ </listitem>
+
+ </orderedlist>
+ </listitem>
+ <listitem>
+ <para>
+ Using 'self-made' CD-ROMs:
+ </para>
+ <para>
+ In this case, you can include the control file on the CD-ROM
+ for easy access (using the <emphasis>autoyast=file://</emphasis>
+ option) or use one of the above mentioned methods used with the
+ original &company-suse; CD-ROMs.
+ </para>
+ <para>
+ Using CD-ROMs for autoinstallation, it is required to instruct the
+ installer to use the CD-ROM for installation and not try to find
+ the installation files on the network. This can be accomplished by
+ adding the <emphasis>instmode=cd</emphasis> option to the kernel
+ command line (this can be done by adding the option to the
+ isolinux.cfg file on the CD).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Using NFS and Floppy, Network or CD-ROM for system boot-up.
+ </para>
+ <para>
+ This option is the most important one due to the fact that
+ installations of PC farms are normally done using NFS servers and
other
+ network services like &bootp; / &dhcp; . The control file can
reside in
+ the following places:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ <emphasis>Floppy/CD-ROM</emphasis>: Control file accessible via
the
+ <emphasis>autoyast=file://..</emphasis> option.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Network</emphasis>: Control file accessible via the
+ <emphasis>autoyast=http://..</emphasis>,
+ <emphasis>autoyast=ftp://..</emphasis>,
+ <emphasis>autoyast=nfs://..</emphasis> or
+ <emphasis>autoyast=tftp://..</emphasis> options.
+ </para>
+ </listitem>
+
+ </orderedlist>
+ </listitem>
+
+ </itemizedlist>
+
+ <note>
+ <title>Disabling network and DHCP</title>
+ <para>To disable network during installations where network is not
+ needed or not available, for example when auto-installing from
+ CD-ROMs use the linuxrc option <emphasis>netsetup</emphasis> to
+ set network configuration behavior. To disable network setup use
+ <emphasis>netsetup=0</emphasis> </para>
+ </note>
+
+
+ <para>
+ If <emphasis>autoyast=default</emphasis> is defined, &yast2; will look
+ for a file named <filename>autoinst.xml</filename> in
+ the following three places:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>
+ The root directory of the floppy disk.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The root directory of the installation medium.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The root directory of the initial ram disk used to boot the system.
+ </para>
+ </listitem>
+ </orderedlist>
+
+ <para>
+ With all autoyast invocation options, excluding
+ <emphasis>default</emphasis>, it is possible to specify the location of
+ the control file in the following ways:
+ </para>
+
+ <orderedlist numeration="arabic">
+ <listitem>
+ <para>
+ Specify the exact location of the control file:
+ <screen>
+autoyast=http://192.168.1.1/control-files/client01.xml
+ </screen>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Specify a directory where several control files are located
+ </para>
+ <screen>
+autoyast=http://192.168.1.1/control-files/
+ </screen>
+ <para>
+ In this case the relevant control file is retrieved using the hex
digit
+ representation of the IP as described below.
+ </para>
+ </listitem>
+ </orderedlist>
+ <para>
+ If only the path prefix variable is defined, &yast2; will fetch the
+ control file from the specified location in the following way:
+ </para>
+ <orderedlist numeration="arabic">
+ <listitem>
+ <para>
+ First, it will search for the control file using its own IP address
in
+ upper case hexadecimal, e.g. <emphasis>192.0.2.91 ->
C000025B</emphasis>.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ If that file is not found, it will remove one hex digit and try
+ again. This action is repeated till the file with the correct name
+ is found. Ultimately, it will try looking for a file with the MAC
+ address of the clients as the file name (mac should have the
+ following syntax: <emphasis>0080C8F6484C</emphasis>) and if not
found a file named
+ <filename>default</filename> (in lower
+ case).
+ </para>
+ </listitem>
+ </orderedlist>
+
+ <para>
+ As an example, for 192.0.2.91, the HTTP client will try:
+ </para>
+ <literallayout>
+C000025B
+C000025
+C00002
+C0000
+C000
+C00
+C0
+C
+0080C8F6484C
+default
+ </literallayout>
+ <para>
+ in that order.
+ </para>
+ <para>
+ To determine the hex representation of the IP address of the client,
+ use the utility called <command>/usr/sbin/gethostip</command> available
+ with the <emphasis>syslinux</emphasis> package.
+ </para>
+ <example>
+ <title>Determine HEX code for an IP address</title>
+ <screen>
+# /usr/sbin/gethostip 10.10.0.1
+10.10.0.1 10.10.0.1 0A0A0001
+ </screen>
+ </example>
+
+
+
+ </section>
+
+ <section id="autoinstall.singlesystem">
+ <title id="autoinstall.singlesystem.title">
+ Auto-installing a Single System
+ </title>
+ <para>
+ The easiest way to auto-install a system without any network connection
+ is by using the standard CD-ROMs that come in the &company-suse;
Linux box. Using the
+ CD-ROMs in combination with a floppy disk lets you getting started
with
+ &autoyast2; very fast and without spending much time configuring
+ installation server and network environments.
+ </para>
+
+
+ <para>
+ Create the control file and
+ name it <filename>autoinst.xml</filename>. Copy the file
+ <filename>autoinst.xml</filename> to a floppy by either mounting the
+ floppy or by using the <emphasis>mtools</emphasis>.
+ </para>
+ <screen>
+mcopy autoinst.xml a:
+ </screen>
+
+ </section>
+
+
+ <section>
+ <title>Combining linuxrc <emphasis>info</emphasis> file with &yast2;
control file</title>
+ <para>
+ If you choose to pass information to <emphasis>linuxrc</emphasis> using
+ the <emphasis>info</emphasis> file, it is possible to integrate the
+ keywords in the XML control file. In the case the file has to be
+ accessible to linuxrc and has to be named <emphasis>info</emphasis>.
+ </para>
+ <para>
+ Linuxrc will look for a string (<emphasis>start_linuxrc_conf</emphasis>
+ in the control file which represents the
+ beginning of the file. If it is found, it will parse the content
starting
+ from that string and will finish when the string
+ <emphasis>end_linuxrc_conf</emphasis> is found. The options are stored
in
+ the control file in the following way:
+ </para>
+ <example>
+ <title>
+ Linxurc options in the control file
+ </title>
+ <screen>
+ <![CDATA[
+....
+ <install>
+....
+ <init>
+ <info_file>
+<![CDATA[
+#
+# Don't remove the following line:
+# start_linuxrc_conf
+#
+install: nfs://192.168.1.1/CDs/full-i386
+textmode: 1
+autoyast: file:///info
+
+# end_linuxrc_conf
+# Do not remove the above comment
+#
+]]]><![CDATA[]>
+
+ </info_file>
+ </init>
+......
+ </install>
+....
+]]>
+ </screen>
+ </example>
+ <para>
+ Note that the autoyast keyword must point to the same file, i.e. if it
+ is on a floppy, then the protocol <emphasis>floppy</emphasis> has to be
+ used. In other cases where the <emphasis>info</emphasis> file is stored
+ in the initial ram-disk, the <emphasis>file</emphasis> option has to be
used.
+ </para>
+ </section>
+ </section>
+ <section id="System_Configuration">
+ <title id="System_Configuration.title">
+ System Configuration
+ </title>
+ <para>
+ The system configuration during auto-installation can be seen as the
+ most important part of the whole process. Customizing a system to your
+ environment needs is what makes an auto-installation system attractive,
+ not the installation part.
+ </para>
+ <para>
+ As you have seen in the previous chapters, almost anything can be
+ configured automatically on the target system. In addition to the
+ pre-defined directives, you can always use post-scripts to change other
+ things in the system. Additionally you can change any system variables
and
+ if required, copy complete configuration files into the target system.
+ </para>
+ <section>
+ <title>
+ Post-Install and System Configuration
+ </title>
+ <para>
+ The Post-Installation and the System Configuration are initiated
directly after the last
+ package is installed in the target system and is continued after the
+ system has booted for the first time.
+ </para>
+ <para>
+ Before the system is booted for the first time, &yast2; writes all data
+ collected during installation into the system and finally it writes the
+ boot loader in the specified location. In addition to these regular
+ tasks, which are also done when performing a regular installation, YaST2
+ executes the <emphasis>chroot-scripts</emphasis> as specified in the
+ control file. Note that these scripts are executed while the system is
+ still not mounted.
+ </para>
+ <para>
+ If a different kernel than the default is installed, a hard reboot will
+ be required. A hard reboot can also be forced during auto-installation,
+ independent of the installed kernel. This can be accomplished using the
+ <emphasis>reboot</emphasis> property of the
+ <emphasis>general</emphasis> resource. (See <link
+ linkend="CreateProfile.General">General Options</link>)
+ </para>
+ </section>
+ <section>
+ <title>System Customization</title>
+ <para>
+ Most of the system customization is done in the second stage of the
+ installation. &yast2; provides most of the important resources needed to
+ bring up a system to a usable , general state. However, you may have
+ other requirements for the installed system. If the required
+ customizations can't be done using &yast2; resources, then the
+ post-install scripts can be used to accomplish this task.
+ </para>
+ <para>
+ You can define an unlimited number of custom scripts in the control
+ file either by editing the control file or by using the configuration
+ system.
+ </para>
+ </section>
+ </section>
+
+ </chapter>
+
+
+
+
+
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast.xml" "book" "chapter")
+ End:
+ -->

Added: trunk/autoinstallation/doc/xml/Introduction.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Introduction.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/Introduction.xml (added)
+++ trunk/autoinstallation/doc/xml/Introduction.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,161 @@
+ <chapter id="introduction">
+ <title>Introduction</title>
+
+ <para>
+ &autoyast2; is a system for installing one or more SuSE Linux systems
+ automatically and without user intervention. &autoyast2; installations
+ are performed using an autoyast profile with installation and
configuration
+ data. That profile can be created using the configuration insterface
+ of &autoyast2; and can be provided to &yast2; during installation in
+ different ways.
+ </para>
+
+ <section id="avail">
+ <title>Availability</title>
+ <para>
+ &autoyast2; is available with recent &company-suse; products starting
+ from <emphasis>SuSE Linux 8.0</emphasis> and business products starting
from
+ <emphasis>SLES 8</emphasis>.
+ </para>
+ <para>Products prior to SuSE Linux 8.0 and business products based
+ on <emphasis>SLES 7</emphasis> have an auto-installation
+ system based on <emphasis>YaST1</emphasis>. A configuration management
+ system is provided by <emphasis>ALICE</emphasis> for these products.
+ </para>
+ <note>
+ <title>Updated documentation</title>
+ <para>Updated documentation can always be found at the following URL:
+ <ulink
url="http://www.suse.com/~ug";>http://www.suse.com/~ug</ulink></para>
+ </note>
+ </section>
+
+
+ <section id="motiv">
+ <title>Motivation</title>
+ <para>
+ The <ulink url="http://www.linuxjournal.com/";>Linux Journal</ulink>, in
+ an article in <ulink
+
url="http://www.linuxjournal.com/categories.php?op=newindex&amp;catid=178";>issue
78</ulink> writes:
+ </para>
+ <para>
+ <quote>
+ A standard Linux installation asks many questions about what to
+ install, what hardware to configure, how to configure the network
+ interface, etc. Answering these questions once is informative and
maybe
+ even fun. But imagine a system engineer who has to set up a new Linux
+ network with a large number of machines. Now, the same issues need to
+ be addressed and the same questions answered repeatedly. This makes
the
+ task very inefficient, not to mention a source of irritation and
+ boredom. Hence, a need arises to automate this parameter and option
+ selection.</quote>
+ </para>
+ <para>
+ <quote>The thought of simply copying the hard disks naturally crosses
one's
+ mind. This can be done quickly, and all the necessary functions and
+ software will be copied without option selection. However, the fact is
+ that simple copying of hard disks causes the individual computers to
+ become too similar. This, in turn, creates an altogether new mission
of
+ having to reconfigure the individual settings on each PC. For example,
+ IP addresses for each machine will have to be reset. If this is not
+ done properly, strange and inexplicable behavior results.</quote>
+ </para>
+
+ <para>
+ Regular installation of SuSE Linux is semi-automated by default. The
user is
+ requested to select the necessary information at the beginning of the
+ installation (In most cases language only), &yast2; then generates a
+ proposal for the underlying system depending on different factors and
+ system paramters. In
+ most cases, and especially for new systems, such a proposal can be
+ used to install the system and provides a usable installation.
+ </para>
+ <para>
+ The steps following the proposal are fully automated and the user is
only
+ prompted at the end of the installation to configure hardware and
network services.
+ </para>
+ <para>
+ &autoyast2; can be used where no user intervention is required or
+ where customization is required. Using an autoyast profile, &yast2;
+ prepares the system for a custom installation and avoids any
+ interaction with the user, unless specified in the file
+ controling the installation.
+ </para>
+ <para>
+ &autoyast2; is not an automated GUI system. This means that in most
+ cases many screen will be skipped, i.e. you will never see the language
+ selection interface. &autoyast2; will simply pass the language
+ parameter to the sub-system without displaying any language related
+ interface.
+ </para>
+
+ </section>
+
+ <section id="overviewandconcept">
+ <title>Overview and Concept</title>
+ <para>
+ Using &autoyast2;, multiple systems sharing the same environment and
+ similar but not necesserily identical hardware performing similar
+ tasks can easily be installed in parallel and in a short time. A
+ configuration file (referred to as "autoyast profile") is created using
+ existing configuration resources. The profile file can be easily
+ tailored for any specific environment.
+ </para>
+
+
+ <para>
+ Unlike autoinstallation systems available with older &company-suse;
+ releases, &autoyast2; is fully integrated and provides various options
for
+ installing and configuring a system. The main advantage over older
+ systems and other auto-installation systems is the possibility to
configure a
+ computer by using existing modules and avoiding using custom scripts
which
+ are normally executed at the end of the installation.
+ </para>
+
+ <para>
+ This document will guide you through the three steps of
auto-installation:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Preparation: All relevant information about the target system are
+ collected and turned into the appropriate directives of the profile.
+ The profile file is transferred onto the target system where
+ its directives will be parsed and transformed to &yast2; conforming
+ data. </para>
+ </listitem>
+ <listitem>
+ <para>
+ Installation: follows the instructions given in the profile and
+ installs the base system.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Configuration: &yast2; in addition to user-defined post-install
+ scripts complete the system configuration
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ The complete and detailed process is illustrated in the following
figure:
+ </para>
+
+ <?anas-pagebreak?>
+ <figure id="process">
+ <title id="process.title">Auto-installation process</title>
+ <mediaobject>&autoyast-oview;</mediaobject>
+ </figure>
+ </section>
+
+
+ </chapter>
+
+
+
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast.xml" "book" "book")
+ End:
+ -->
+

Added: trunk/autoinstallation/doc/xml/KDumpSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/KDumpSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/KDumpSection.xml (added)
+++ trunk/autoinstallation/doc/xml/KDumpSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,576 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+ <!-- {{{ Kdump -->
+
+ <section id="CreateProfile.kdump">
+ <title>
+ Kernel dumps
+ </title>
+
+ <note>
+ This feature is only available since SLES 11 (not openSUSE 11.1). It is
not available
+ on the <emphasis>zSeries</emphasis> (<emphasis>s390x</emphasis>)
architecture!
+ </note>
+
+ <para>
+ With kdump the system is able to create crashdump files if the whole
system (i.e., the
+ kernel) crashes. That crash dump files contain the memory contents while
the system crashed.
+ Such core files can be analyzed later by the support or a (kernel)
developer to find the
+ reason why the system crashed. It's mostly useful for servers where you
cannot
+ easily reproduce such crashes on another system and where it's important
that the
+ problem gets fixed.
+ </para>
+
+ <para>
+ The only downside of enabling kdump is that this costs you between
64&nbsp;MiB and
+ 128&nbsp;MiB of System RAM (on "normal" sized systems) that needs to be
reserved to
+ be used by kdump in the case the system crashes and the dump needs to be
generated.
+ </para>
+
+ <para>This section only describes how to setup kdump with &autoyast;. It
does not describe
+ how kdump works in general and also does not describe each small detail.
Refer to
+ the kdump(7) manual page which is in the package named
<emphasis>kdump</emphasis> or to
+ the <ulink url="http://en.opensuse.org/Kdump";>openSUSE Kdump
documentation</ulink>.
+ </para>
+
+ <para>
+ At first, let's present an overall example for the kdump configuration:
+ </para>
+
+ &example.kdump;
+
+ <!-- {{{ Memory Reservation -->
+ <section id="CreateProfile.kdump.reservation">
+ <title>Memory Reservation</title>
+
+ <para>
+ As already mentioned above, it's necessary to reserve some memory at
bootup for
+ kdump. Because that memory must be reserved very early during the boot
process,
+ the configuration is done via a kernel command line parameter called
+ <literal>crashkernel</literal>. That memory will be used to load a
second kernel
+ in that memory that will be executed without rebooting if the first
kernel
+ crashes. That kernel also has a special initrd which contains all
programs
+ that are necessary to save the dump to network or disk, send the
notification
+ email and finally reboot.
+ </para>
+
+ <para>
+ You can enable or disable that the <literal>crashkernel</literal>
parameter is
+ written for the default boot kernel with the
<literal>add_crash_kernel</literal>
+ tag and you can specify the value of the
<literal>crashkernel</literal> parameter
+ using the <literal>crash_kernel</literal> tag.
+ </para>
+
+ <para>
+ For the memory reservation there are two things to specify: The
<emphasis>amount</emphasis>
+ of reserved memory (such as <literal>64M</literal> to reserve
64&nbsp;MiB of memory from
+ the RAM) and the <emphasis>offset</emphasis>. The syntax is
+ <literal>crashkernel=AMOUNT@OFFSET</literal>. Luckily the kernel is
able to auto-detect the
+ right offset for you nowadays (with the exception of the Xen
hypervisor where you have to
+ specify <emphasis>16M</emphasis> as offset), so you don't have to
worry about that too much.
+ You can just specify
<literal>&lt;crash_kernel&gt;crashkernel=64M&lt;/crash_kernel&gt;</literal>
+ and the right thing will happen.
+ </para>
+
+ <para>
+ For the <emphasis>amount</emphasis> of memory, following values are
recommended:
+ </para>
+
+ <para>
+ <table frame="top">
+ <title>Recommended values for the reserved memory amount</title>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>Platform</entry>
+ <entry>Recommended values</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ i386 and x86-64
+ </entry>
+ <entry>
+ <literal>64M</literal> for small machines (about 2&nbsp;GiB
of RAM, 4 cores)
+ and <literal>128M</literal> for larger machines
+ </entry>
+ </row>
+ </tbody>
+ <tbody>
+ <row>
+ <entry>
+ PPC64
+ </entry>
+ <entry>
+ <literal>128M</literal> for small machines
+ and <literal>256M</literal> for larger machines
+ </entry>
+ </row>
+ </tbody>
+ <tbody>
+ <row>
+ <entry>
+ IA64
+ </entry>
+ <entry>
+ <literal>256M</literal> for small machines,
+ <literal>512M</literal> for medium machines and
+ <literal>1G</literal> and more for really large machines
+ (mostly SGI Altix systems)
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+
+ <para>
+ To make things even more complicated, there's a so-called
<emphasis>extended
+ command line syntax</emphasis> where you can specify the amount of
reserved
+ memory dependent of the System RAM. That is good if you share one
&autoyast;
+ profile for multiple installations or when you often remove or install
memory
+ on one machine. The syntax is:
+ </para>
+
+ <para>
+
<screen>BEGIN_RANGE_1-END_RANGE_1:AMOUNT_1,BEGIN_RANGE_2-END_RANGE_2:AMOUNT_2@OFFSET</screen>
+ </para>
+
+ <para>
+ In that syntax <literal>BEGIN_RANGE_1</literal> is the start of the
first
+ memory range (for example: <literal>0M</literal>) and
<literal>END_RANGE_1</literal>
+ is the end of the first memory range (and can be empty in case
"infinity" should
+ be assumed) and so on. So for example
+ <literal>256M-2G:64M,2G-:128M</literal> means to reserve 64&nbsp;MiB
of crashkernel
+ memory when the system has between 256&nbsp;MiB and 2&nbsp;GiB RAM and
to reserve
+ 128&nbsp;MiB of crashkernel memory when the system has above
2&nbsp;GiB RAM.
+ </para>
+
+ <para>
+ The following table contains the settings that are necessary for the
+ memory reservation:
+ </para>
+
+ <para>
+ <table frame='top'>
+ <title>XML representation of the memory reservation settings</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>add_crash_kernel</entry>
+ <entry>If the memory should be reserved, that basically
enables or disables kdump.
+ <para><screen>&lt;add_crash_kernel
config:type="boolean"&gt;true&lt;/add_crash_kernel&gt;</screen></para></entry>
+ <entry>required</entry>
+ </row>
+ <row>
+ <entry>crash_kernel</entry>
+ <entry>The syntax of the crashkernel command line as discussed
above.
+
<para><screen>&lt;crash_kernel&gt;256M:64M&lt;/crash_kernel&gt;</screen></para></entry>
+ <entry>required</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ </section>
+ <!-- }}} -->
+
+ <!-- {{{ Dump Saving -->
+ <section id="CreateProfile.kdump.saving">
+ <title>
+ Dump Saving
+ </title>
+
+ <!-- {{{ Target -->
+ <section id="CreateProfile.kdump.saving.target">
+ <title>
+ Target
+ </title>
+
+ <para>
+ The element <literal>KDUMP_SAVEDIR</literal> holds an URL to where
the dump
+ is saved. Following methods are possible:
+ </para>
+
+ <itemizedlist mark='opencircle'>
+ <listitem>
+ <para>
+ <literal>file</literal> to save to the local disk
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>ftp</literal> to save to an FTP server (without
encryption)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>sftp</literal> to save to an SSH2 SFTP server
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>nfs</literal> to save to a NFS location and
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <literal>cifs</literal> to save the dump to a CIFS/SMP export
from Samba or Microsoft Windows.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ For details see the kdump(5) manual page. Two examples are:
+ <literal>file:///var/crash</literal> (which is the default location
+ according to FHS) and
<literal>ftp://user:password@host:port/incoming/dumps</literal>.
+ Below that directory, a directory name that contains a time stamp
will be created
+ in which the dumps are saved.
+ </para>
+
+ <para>
+ When the dump is saved to the local disk,
<literal>KDUMP_KEEP_OLD_DUMPS</literal>
+ can be used to delete old dumps automatically. This setting takes a
number that
+ specifies how much old dumps should be kept. If the partition has
less than
+ <literal>KDUMP_FREE_DISK_SIZE</literal> megabytes free disk space
after saving the
+ dump, the dump is not copied at all.
+ </para>
+
+ <para>
+ If you would not like only to save the dump but also the whole
kernel and
+ (if installed) the debug information of the kernel to that directory
to have
+ everything you need (except all kernel modules and the debugging
information
+ of all kernel modules) to analyze the dump in one directory, you can
set
+ <literal>KDUMP_COPY_KERNEL</literal> to <literal>true</literal>.
+ </para>
+ </section>
+ <!-- }}} -->
+ <!-- {{{ Filtering and Compression -->
+ <section id="CreateProfile.kdump.saving.compression">
+ <title>
+ Filtering and Compression
+ </title>
+
+ <para>
+ The size of kernel dumps is uncompressed and unfiltered as large as
your system has RAM.
+ To get smaller files (for example, to send it to support), you can
compress the whole
+ dump file afterwards. However, the drawback is that the dump has to
be uncompressed
+ afterwards before opening, so the disk space needs to be there in
any case.
+ </para>
+
+ <para>
+ To use page compression which compresses every page and allows
dynamic decompression
+ with the crash(8) debugging tool, set
<literal>KDUMP_DUMPFORMAT</literal> to
+ <literal>compressed</literal> (which is actually the default).
+ </para>
+
+ <para>
+ To filter the dump, you have to set the
<literal>KDUMP_DUMPLEVEL</literal>. Then not all
+ memory is saved to disk but only memory that does not fulfill some
criteria. I.e. you
+ may want to leave out pages that are completely filled by zeroes as
they don't
+ contain any useful information. 0 produces a full dump and 31 is the
smallest dump.
+ The manual page kdump(5) and makedumpfile(8) contain a table that
lists for
+ each value which pages will be saved.
+ </para>
+
+ </section>
+ <!-- }}} -->
+ <!-- {{{ Table -->
+ <section id="CreateProfile.kdump.saving.summary">
+ <title>
+ Summary
+ </title>
+ <para>
+ <table frame='top'>
+ <title>XML representation of the dump target settings</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>KDUMP_SAVEDIR</entry>
+ <entry>An URL that specifies the target to which the dump
and related files will be saved.
+
<para><screen>&lt;KDUMP_SAVEDRIR&gt;file:///var/crash/&lt;/KDUMP_SAVEDIR&gt;</screen></para></entry>
+ <entry>required</entry>
+ </row>
+ <row>
+ <entry>KDUMP_COPY_KERNEL</entry>
+ <entry>If not only the dump itself should be saved to
<literal>KDUMP_SAVEDIR</literal> but
+ also the kernel and its debugging information (if
installed).
+
<para><screen>&lt;KDUMP_COPY_KERNEL&gt;false&lt;/KDUMP_COPY_KERNEL&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>KDUMP_FREE_DISK_SIZE</entry>
+ <entry>
+ The number of megabytes that should always be free after
saving the dump. If that
+ space would be below that value, the dump will not be
copied.
+
<para><screen>&lt;KDUMP_FREE_DISK_SIZE&gt;64&lt;/KDUMP_FREE_DISK_SIZE&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>KDUMP_KEEP_OLD_DUMPS</entry>
+ <entry>
+ The number of dumps that are kept (i.e., not deleted) if
<literal>KDUMP_SAVEDIR</literal>
+ points to a local directory. Specify 0 if you don't want
to delete dumps at all and
+ specify -1 if all dumps (except the one that is just
saved) should be deleted.
+
<para><screen>&lt;KDUMP_KEEP_OLD_DUMPS&gt;4&lt;/KDUMP_KEEP_OLD_DUMPS&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ </section>
+ <!-- }}} -->
+
+ </section>
+ <!-- }}} -->
+ <!-- {{{ Email Notification -->
+ <section id="CreateProfile.kdump.notification">
+ <title>
+ Email Notification
+ </title>
+
+ <para>
+ It's useful to get notified via email that a machine has crashed and a
dump has been
+ saved. That way you can for example setup a dump server in a company
and trigger
+ some actions by that email automatically like calling the
administrator from home
+ to check if everything runs again.
+ </para>
+
+ <para>
+ Because the dump is saved in a special initrd environment, we cannot
use a local
+ mail server just to send that notification email. However, it's better
to send
+ that email in the initrd just because it's more likely that we have a
working network
+ connection here (which we need in the netdump case to save the dump
away anyway)
+ compared that the server comes up again and everything is working.
+ </para>
+
+ <para>You have to provide at least exactly one address in
+ <literal>KDUMP_NOTIFICATION_TO</literal> and zero, one or more
addresses
+ in <literal>KDUMP_NOTIFICATION_CC</literal>. Please note that you can
only
+ specify the address here, not a real name or some other fancy stuff.
+ </para>
+
+ <para>
+ To actually send the email, we need
<literal>KDUMP_SMTP_SERVER</literal> and
+ (if the server needs authentication)
<literal>KDUMP_SMTP_USER</literal> and
+ <literal>KDUMP_SMTP_PASSWORD</literal>. Please note that TSL or SSL
are not supported.
+ That may be added in future.
+ </para>
+
+ <para>
+ <!-- {{{ Table: XML representation of the email notification settings
-->
+ <table frame='top'>
+ <title>XML representation of the email notification settings</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>KDUMP_NOTIFICATION_TO</entry>
+ <entry>Exactly one email address (and only an address) to
which the mail
+ should be sent. Additional recipients can be specified in
+ <literal>KDUMP_NOTIFICATION_CC</literal>.
+
<para><screen>&lt;KDUMP_NOTIFICATION_TO&gt;bwalle@xxxxxxx&lt;/KDUMP_NOTIFICATION_TO&gt;</screen></para></entry>
+ <entry>optional (email notification is disabled if
empty)</entry>
+ </row>
+ <row>
+ <entry>KDUMP_NOTIFICATION_CC</entry>
+ <entry>Zero, one or more recipients that are in the Cc line of
the notification mail.
+ <para><screen>&lt;KDUMP_NOTIFICATION_CC&gt;spam@xxxxxxx
devnull@xxxxxxx&lt;/KDUMP_NOTIFICATION_CC&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>KDUMP_SMTP_SERVER</entry>
+ <entry>
+ Host name of the SMTP server that will be used for the mail
delivery. Please note
+ that the SMTP authentication is supported (see
<literal>KDUMP_SMTP_USER</literal>
+ and <literal>KDUMP_SMTP_PASSWORD</literal>) but TSL and SSL
are <emphasis>not</emphasis>
+ supported.
+
<para><screen>&lt;KDUMP_SMTP_SERVER&gt;email.suse.de&lt;/KDUMP_SMTP_SERVER&gt;</screen></para></entry>
+ <entry>optional (email notification is disabled if
empty)</entry>
+ </row>
+ <row>
+ <entry>KDUMP_SMTP_USER</entry>
+ <entry>
+ User name that is used together with
<literal>KDUMP_SMTP_PASSWORD</literal>
+ for SMTP authentication.
+
<para><screen>&lt;KDUMP_SMTP_USER&gt;bwalle&lt;/KDUMP_SMTP_USER&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>KDUMP_SMTP_PASSWORD</entry>
+ <entry>
+ Password that is used together with
<literal>KDUMP_SMTP_USER</literal>
+ for SMTP authentication.
+
<para><screen>&lt;KDUMP_SMTP_PASSWORD&gt;geheim&lt;/KDUMP_SMTP_PASSWORD&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <!-- }}} -->
+ </para>
+ </section>
+ <!-- }}} -->
+ <!-- {{{ Kdump kernel settings -->
+ <section id="CreateProfile.kdump.kernel">
+ <title>
+ Kdump kernel settings
+ </title>
+
+ <para>
+ As already mentioned, a special kernel is booted to save the dump.
+ If you don't want to use the auto-detection mechanism to find out
which kernel
+ is used (see the kdump(5) manual page that describes the algorithm
which
+ is used to find the kernel), you can specify the version of a custom
kernel
+ in <literal>KDUMP_KERNELVER</literal>. If you set that to
+ <literal>foo</literal>, then the kernel located in
+ <filename>/boot/vmlinuz-foo</filename> or
<filename>/boot/vmlinux-foo</filename>
+ (in that order on platforms that have a <filename>vmlinuz</filename>
file)
+ will be used.
+ </para>
+
+ <para>
+ You can even specify the command line which will be used to boot the
kdump kernel.
+ Normally the boot command line is used minus some settings that hurt
in the
+ kdump case (like the <literal>crashkernel</literal> parameter itself)
plus
+ some settings that are needed in the kdump case (see the manual page
kdump(5)).
+ If you just want some additional parameters like a overwritten console
setting
+ then use <literal>KDUMP_COMMANDLINE_APPEND</literal>. If you know what
you're doing
+ and you want to specify the whole command line, set
<literal>KDUMP_COMMANDLINE</literal>.
+ </para>
+
+ <para>
+ <!-- {{{ Table: XML representation of the kernel settings -->
+ <table frame='top'>
+ <title>XML representation of the kernel settings</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>KDUMP_KERNELVER</entry>
+ <entry>Version string for the kernel that will be used for
kdump. Leave it
+ empty to use the auto-detection mechanism (strongly
recommended).
+
<para><screen>&lt;KDUMP_KERNELVER&gt;2.6.27-default&lt;/KDUMP_KERNELVER&gt;</screen></para></entry>
+ <entry>optional (auto-detection if empty)</entry>
+ </row>
+ <row>
+ <entry>KDUMP_COMMANDLINE_APPEND</entry>
+ <entry>Additional command line parameters for the kdump kernel.
+
<para><screen>&lt;KDUMP_COMMANDLINE_APPEND&gt;console=ttyS0,57600&lt;/KDUMP_COMMANDLINE_APPEND&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>KDUMP_COMMANDLINE</entry>
+ <entry>
+ Overwrite the automatically generated kdump command line.
Use with care.
+ Normally <literal>KDUMP_COMMANDLINE_APPEND</literal> is the
setting you're
+ looking for.
+ <para><screen>&lt;KDUMP_COMMANDLINE_APPEND&gt;root=/dev/sda5
maxcpus=1 irqpoll&lt;/KDUMP_COMMANDLINE&gt;</screen></para></entry>
+ <entry>optional (email notification is disabled if
empty)</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <!-- }}} -->
+ </para>
+ </section>
+ <!-- }}} -->
+ <!-- {{{ Expert settings -->
+ <section id="CreateProfile.kdump.expert">
+ <title>
+ Expert settings
+ </title>
+
+ <para>
+ <!-- {{{ Table: XML representation of the expert settings -->
+ <table frame='top'>
+ <title>XML representation of the expert settings</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>KDUMP_IMMEDIATE_REBOOT</entry>
+ <entry><literal>true</literal> if the system should be
rebooted automatically
+ after the dump has been saved, <literal>false</literal>
otherwise. The default
+ is to reboot the system automatically.
+
<para><screen>&lt;KDUMP_IMMEDIATE_REBOOT&gt;true&lt;/KDUMP_IMMEDIATE_REBOOT&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>KDUMP_VERBOSE</entry>
+ <entry>Bitmask that specifies how to verbose the kdump process
should be.
+ Read kdump(5) for details.
+
<para><screen>&lt;KDUMP_VERBOSE&gt;3&lt;/KDUMP_VERBOSE&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>KEXEC_OPTIONS</entry>
+ <entry>Additional options that are passed to
<application>kexec</application>
+ when loading the kdump kernel. Normally empty.
+
<para><screen>&lt;KEXEC_OPTIONS&gt;--noio&lt;/KEXEC_OPTIONS&gt;</screen></para></entry>
+ <entry>optional</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <!-- }}} -->
+ </para>
+
+ </section>
+ <!-- }}} -->
+
+ </section>
+ <!-- }}} -->
+
+

Added: trunk/autoinstallation/doc/xml/LDAPSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/LDAPSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/LDAPSection.xml (added)
+++ trunk/autoinstallation/doc/xml/LDAPSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,35 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+ <section id="Configuration.Network.LDAP">
+ <title>
+ &ldap; client
+ </title>
+ <para>
+ The installed machine can be set up as an
+ <emphasis>> &ldap; client</emphasis> to authenticate users with an
+ OpenLDAP; server. Required data are the name of the search base (base
DN, e.g, dc=mydomain,dc=com)
+ and the IP address of the &ldap; server (e.g., 10.20.0.2).
+ </para>
+ <para>
+ If &ldap; is activated, <emphasis>NSS</emphasis> and
<emphasis>PAM</emphasis>
+ will be configured accordingly to use &ldap; for user authentication.
+ </para>
+ &example.ldapclient;
+ </section>
+

Added: trunk/autoinstallation/doc/xml/MailSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/MailSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/MailSection.xml (added)
+++ trunk/autoinstallation/doc/xml/MailSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,38 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+ <section id='Configuration.Network.Sendmail'>
+ <title>
+ Mail Configuration (Sendmail or Postfix)
+ </title>
+ <para>
+ For the mail configuration of the client this
+ module lets you create a detailed mail configuration. The module
+ contains various options and it is recommended to use it at least for
+ the initial configuration.
+
+ </para>
+ <example>
+ <title>Mail Configuration</title>
+ <screen>
+ <xi:include href="examples/example.mail.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+</example>
+ </section>
+

Added: trunk/autoinstallation/doc/xml/Makefile
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Makefile?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/Makefile (added)
+++ trunk/autoinstallation/doc/xml/Makefile Mon Aug 8 14:12:13 2011
@@ -0,0 +1,730 @@
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
+# doc/xml/Makefile. Generated from Makefile.in by configure.
+
+# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
+# 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation,
+# Inc.
+# This Makefile.in is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
+
+
+#
+# Makefile.am for y2c_autoinst/doc
+#
+# $Id: Makefile.am 63765 2011-04-11 15:40:31Z ug $
+#
+
+
+pkgdatadir = $(datadir)/autoyast2
+pkgincludedir = $(includedir)/autoyast2
+pkglibdir = $(libdir)/autoyast2
+pkglibexecdir = $(libexecdir)/autoyast2
+am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
+install_sh_DATA = $(install_sh) -c -m 644
+install_sh_PROGRAM = $(install_sh) -c
+install_sh_SCRIPT = $(install_sh) -c
+INSTALL_HEADER = $(INSTALL_DATA)
+transform = $(program_transform_name)
+NORMAL_INSTALL = :
+PRE_INSTALL = :
+POST_INSTALL = :
+NORMAL_UNINSTALL = :
+PRE_UNINSTALL = :
+POST_UNINSTALL = :
+build_triplet = x86_64-suse-linux-gnu
+host_triplet = x86_64-suse-linux-gnu
+target_triplet = x86_64-suse-linux-gnu
+subdir = doc/xml
+DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
+ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
+am__aclocal_m4_deps = $(top_srcdir)/configure.in
+am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
+ $(ACLOCAL_M4)
+mkinstalldirs = $(install_sh) -d
+CONFIG_CLEAN_FILES =
+CONFIG_CLEAN_VPATH_FILES =
+SOURCES =
+DIST_SOURCES =
+RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+ html-recursive info-recursive install-data-recursive \
+ install-dvi-recursive install-exec-recursive \
+ install-html-recursive install-info-recursive \
+ install-pdf-recursive install-ps-recursive install-recursive \
+ installcheck-recursive installdirs-recursive pdf-recursive \
+ ps-recursive uninstall-recursive
+am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
+am__vpath_adj = case $$p in \
+ $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
+ *) f=$$p;; \
+ esac;
+am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`;
+am__install_max = 40
+am__nobase_strip_setup = \
+ srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'`
+am__nobase_strip = \
+ for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||"
+am__nobase_list = $(am__nobase_strip_setup); \
+ for p in $$list; do echo "$$p $$p"; done | \
+ sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \
+ $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \
+ if (++n[$$2] == $(am__install_max)) \
+ { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \
+ END { for (dir in files) print dir, files[dir] }'
+am__base_list = \
+ sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \
+ sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g'
+am__installdirs = "$(DESTDIR)$(htmldir)"
+DATA = $(html_DATA)
+RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive \
+ distclean-recursive maintainer-clean-recursive
+AM_RECURSIVE_TARGETS = $(RECURSIVE_TARGETS:-recursive=) \
+ $(RECURSIVE_CLEAN_TARGETS:-recursive=) tags TAGS ctags CTAGS \
+ distdir
+ETAGS = etags
+CTAGS = ctags
+DIST_SUBDIRS = $(SUBDIRS)
+DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
+am__relativize = \
+ dir0=`pwd`; \
+ sed_first='s,^\([^/]*\)/.*$$,\1,'; \
+ sed_rest='s,^[^/]*/*,,'; \
+ sed_last='s,^.*/\([^/]*\)$$,\1,'; \
+ sed_butlast='s,/*[^/]*$$,,'; \
+ while test -n "$$dir1"; do \
+ first=`echo "$$dir1" | sed -e "$$sed_first"`; \
+ if test "$$first" != "."; then \
+ if test "$$first" = ".."; then \
+ dir2=`echo "$$dir0" | sed -e "$$sed_last"`/"$$dir2"; \
+ dir0=`echo "$$dir0" | sed -e "$$sed_butlast"`; \
+ else \
+ first2=`echo "$$dir2" | sed -e "$$sed_first"`; \
+ if test "$$first2" = "$$first"; then \
+ dir2=`echo "$$dir2" | sed -e "$$sed_rest"`; \
+ else \
+ dir2="../$$dir2"; \
+ fi; \
+ dir0="$$dir0"/"$$first"; \
+ fi; \
+ fi; \
+ dir1=`echo "$$dir1" | sed -e "$$sed_rest"`; \
+ done; \
+ reldir="$$dir2"
+ACLOCAL = ${SHELL} /space/YaST_trunk/trunk/autoinstallation/missing --run
aclocal-1.11
+AMTAR = ${SHELL} /space/YaST_trunk/trunk/autoinstallation/missing --run tar
+AUTOCONF = ${SHELL} /space/YaST_trunk/trunk/autoinstallation/missing --run
autoconf
+AUTOHEADER = ${SHELL} /space/YaST_trunk/trunk/autoinstallation/missing --run
autoheader
+AUTOMAKE = ${SHELL} /space/YaST_trunk/trunk/autoinstallation/missing --run
automake-1.11
+AWK = gawk
+CAT_ENTRY_END = -->
+CAT_ENTRY_START = <!--
+CYGPATH_W = echo
+DEFS = -DPACKAGE_NAME=\"autoyast2\" -DPACKAGE_TARNAME=\"autoyast2\"
-DPACKAGE_VERSION=\"2.21.0\" -DPACKAGE_STRING=\"autoyast2\ 2.21.0\"
-DPACKAGE_BUGREPORT=\"http://bugs.opensuse.org/\"; -DPACKAGE_URL=\"\"
-DPACKAGE=\"autoyast2\" -DVERSION=\"2.21.0\"
+DOCBOOK_ROOT = /usr/share/xml/docbook/stylesheet/nwalsh/current
+ECHO_C =
+ECHO_N = -n
+ECHO_T =
+INSTALL = /usr/bin/install -c -p
+INSTALL_DATA = ${INSTALL} -m 644
+INSTALL_PROGRAM = ${INSTALL}
+INSTALL_SCRIPT = ${INSTALL}
+INSTALL_STRIP_PROGRAM = $(install_sh) -c -s
+LIBOBJS =
+LIBS =
+LN_S = ln -s
+LTLIBOBJS =
+MAINTAINER = Uwe Gansert <ug@xxxxxxx>
+MAKEINFO = ${SHELL} /space/YaST_trunk/trunk/autoinstallation/missing --run
makeinfo
+MKDIR_P = /bin/mkdir -p
+PACKAGE = autoyast2
+PACKAGE_BUGREPORT = http://bugs.opensuse.org/
+PACKAGE_NAME = autoyast2
+PACKAGE_STRING = autoyast2 2.21.0
+PACKAGE_TARNAME = autoyast2
+PACKAGE_URL =
+PACKAGE_VERSION = 2.21.0
+PATH_SEPARATOR = :
+PKG_CONFIG_PATH =
+RPMNAME = autoyast2
+SET_MAKE =
+SHELL = /bin/sh
+STRIP =
+STYLESHEET_CSS = default.css
+STYLESHEET_HTML = /usr/share/YaST2/data/docbook/stylesheets/customize-html.xsl
+STYLESHEET_PDF = /usr/share/YaST2/data/docbook/stylesheets/customize-fo.xsl
+STYLESHEET_YCPDOC = /usr/share/YaST2/data/docbook/stylesheets/ycpdoc.xsl
+STYLESHEET_YDOC = /usr/share/YaST2/data/docbook/stylesheets/ydoc.xsl
+VERSION = 2.21.0
+XGETTEXT = /usr/bin/xgettext
+XML_CATALOG = /etc/xml/catalog
+XSLTPROC = /usr/bin/xsltproc
+XSLTPROC_FLAGS = --nonet
+Y2DEVTOOLS_PREFIX = /usr
+YCPC = /usr/bin/ycpc
+YCPDOC = /usr/lib/YaST2/bin/ycpdoc
+YCPMAKEDEP = /usr/lib/YaST2/bin/ycpmakedep
+abs_builddir = /space/YaST_trunk/trunk/autoinstallation/doc/xml
+abs_srcdir = /space/YaST_trunk/trunk/autoinstallation/doc/xml
+abs_top_builddir = /space/YaST_trunk/trunk/autoinstallation
+abs_top_srcdir = /space/YaST_trunk/trunk/autoinstallation
+agentdir = ${prefix}/lib/YaST2/servers_non_y2
+am__leading_dot = .
+am__tar = tar --format=ustar -chf - "$$tardir"
+am__untar = tar -xf -
+bindir = ${exec_prefix}/bin
+build = x86_64-suse-linux-gnu
+build_alias =
+build_cpu = x86_64
+build_os = linux-gnu
+build_vendor = suse
+builddir = .
+clientdir = ${prefix}/share/YaST2/clients
+datadir = ${datarootdir}
+datarootdir = ${prefix}/share
+desktopdir = ${prefix}/share/applications/YaST2
+docdir = ${prefix}/share/doc/packages/autoyast2
+dvidir = ${docdir}
+exec_prefix = ${prefix}
+execcompdir = ${prefix}/lib/YaST2
+fillupdir = /var/adm/fillup-templates
+host = x86_64-suse-linux-gnu
+host_alias =
+host_cpu = x86_64
+host_os = linux-gnu
+host_vendor = suse
+htmldir = $(docdir)/html
+imagedir = ${prefix}/share/YaST2/images
+includedir = ${prefix}/include/YaST2
+infodir = ${datarootdir}/info
+install_sh = ${SHELL} /space/YaST_trunk/trunk/autoinstallation/install-sh
+libdir = /usr/lib64
+libexecdir = ${exec_prefix}/libexec
+localedir = ${prefix}/share/YaST2/locale
+localstatedir = ${prefix}/var
+mandir = ${prefix}/share/man
+mkdir_p = /bin/mkdir -p
+moduledir = ${prefix}/share/YaST2/modules
+oldincludedir = /usr/include
+pdfdir = ${docdir}
+pkgconfigdatadir = ${datadir}/pkgconfig
+pkgconfigdir = ${libdir}/pkgconfig
+plugindir = ${libdir}/YaST2/plugin
+potdir = ${docdir}/pot
+prefix = /usr
+program_transform_name = s,x,x,
+psdir = ${docdir}
+sbindir = ${exec_prefix}/sbin
+schemadir = ${prefix}/share/YaST2/schema
+scrconfdir = ${prefix}/share/YaST2/scrconf
+sharedstatedir = ${prefix}/com
+srcdir = .
+sysconfdir = /etc
+target = x86_64-suse-linux-gnu
+target_alias =
+target_cpu = x86_64
+target_os = linux-gnu
+target_vendor = suse
+themedir = ${prefix}/share/YaST2/theme
+top_build_prefix = ../../
+top_builddir = ../..
+top_srcdir = ../..
+yast2dir = ${prefix}/share/YaST2
+ybindir = ${prefix}/lib/YaST2/bin
+ydatadir = ${prefix}/share/YaST2/data
+yncludedir = ${prefix}/share/YaST2/include
+ystartupdir = ${prefix}/lib/YaST2
+SUBDIRS =
+xml_file = autoyast.xml
+xml_files = $(wildcard *.xml)
+EXTRA_DIST = $(xml_files) $(wildcard *.xsl) web/default.css
+CLEANFILES = .html.sum profile.dtd.xml elements \
+ elements.xml elements.ent profile.dtd.xml examples.ent\
+ components.ent .ps.sum autoyast.out autoyast.pdf autoyast.fo \
+ images.ent
+
+html_DATA = $(wildcard html/*.html) \
+ html/index.html \
+ html/yast2docs.css \
+ html/default.css
+
+all: all-recursive
+
+.SUFFIXES:
+$(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps)
+ @for dep in $?; do \
+ case '$(am__configure_deps)' in \
+ *$$dep*) \
+ ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \
+ && { if test -f $@; then exit 0; else break; fi; }; \
+ exit 1;; \
+ esac; \
+ done; \
+ echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu doc/xml/Makefile'; \
+ $(am__cd) $(top_srcdir) && \
+ $(AUTOMAKE) --gnu doc/xml/Makefile
+.PRECIOUS: Makefile
+Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
+ @case '$?' in \
+ *config.status*) \
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
+ *) \
+ echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@
$(am__depfiles_maybe)'; \
+ cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@
$(am__depfiles_maybe);; \
+ esac;
+
+$(top_builddir)/config.status: $(top_srcdir)/configure
$(CONFIG_STATUS_DEPENDENCIES)
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+$(top_srcdir)/configure: $(am__configure_deps)
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(ACLOCAL_M4): $(am__aclocal_m4_deps)
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(am__aclocal_m4_deps):
+install-htmlDATA: $(html_DATA)
+ @$(NORMAL_INSTALL)
+ test -z "$(htmldir)" || $(MKDIR_P) "$(DESTDIR)$(htmldir)"
+ @list='$(html_DATA)'; test -n "$(htmldir)" || list=; \
+ for p in $$list; do \
+ if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
+ echo "$$d$$p"; \
+ done | $(am__base_list) | \
+ while read files; do \
+ echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(htmldir)'"; \
+ $(INSTALL_DATA) $$files "$(DESTDIR)$(htmldir)" || exit $$?; \
+ done
+
+uninstall-htmlDATA:
+ @$(NORMAL_UNINSTALL)
+ @list='$(html_DATA)'; test -n "$(htmldir)" || list=; \
+ files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \
+ test -n "$$files" || exit 0; \
+ echo " ( cd '$(DESTDIR)$(htmldir)' && rm -f" $$files ")"; \
+ cd "$(DESTDIR)$(htmldir)" && rm -f $$files
+
+# This directory's subdirectories are mostly independent; you can cd
+# into them and run `make' without going through this Makefile.
+# To change the values of `make' variables: instead of editing Makefiles,
+# (1) if the variable is set in `config.status', edit `config.status'
+# (which will cause the Makefiles to be regenerated when you run `make');
+# (2) otherwise, pass the desired values on the `make' command line.
+$(RECURSIVE_TARGETS):
+ @fail= failcom='exit 1'; \
+ for f in x $$MAKEFLAGS; do \
+ case $$f in \
+ *=* | --[!k]*);; \
+ *k*) failcom='fail=yes';; \
+ esac; \
+ done; \
+ dot_seen=no; \
+ target=`echo $@ | sed s/-recursive//`; \
+ list='$(SUBDIRS)'; for subdir in $$list; do \
+ echo "Making $$target in $$subdir"; \
+ if test "$$subdir" = "."; then \
+ dot_seen=yes; \
+ local_target="$$target-am"; \
+ else \
+ local_target="$$target"; \
+ fi; \
+ ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+ || eval $$failcom; \
+ done; \
+ if test "$$dot_seen" = "no"; then \
+ $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
+ fi; test -z "$$fail"
+
+$(RECURSIVE_CLEAN_TARGETS):
+ @fail= failcom='exit 1'; \
+ for f in x $$MAKEFLAGS; do \
+ case $$f in \
+ *=* | --[!k]*);; \
+ *k*) failcom='fail=yes';; \
+ esac; \
+ done; \
+ dot_seen=no; \
+ case "$@" in \
+ distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
+ *) list='$(SUBDIRS)' ;; \
+ esac; \
+ rev=''; for subdir in $$list; do \
+ if test "$$subdir" = "."; then :; else \
+ rev="$$subdir $$rev"; \
+ fi; \
+ done; \
+ rev="$$rev ."; \
+ target=`echo $@ | sed s/-recursive//`; \
+ for subdir in $$rev; do \
+ echo "Making $$target in $$subdir"; \
+ if test "$$subdir" = "."; then \
+ local_target="$$target-am"; \
+ else \
+ local_target="$$target"; \
+ fi; \
+ ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+ || eval $$failcom; \
+ done && test -z "$$fail"
+tags-recursive:
+ list='$(SUBDIRS)'; for subdir in $$list; do \
+ test "$$subdir" = . || ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS)
tags); \
+ done
+ctags-recursive:
+ list='$(SUBDIRS)'; for subdir in $$list; do \
+ test "$$subdir" = . || ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS)
ctags); \
+ done
+
+ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
+ list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+ unique=`for i in $$list; do \
+ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+ done | \
+ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+ END { if (nonempty) { for (i in files) print i; }; }'`; \
+ mkid -fID $$unique
+tags: TAGS
+
+TAGS: tags-recursive $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
+ $(TAGS_FILES) $(LISP)
+ set x; \
+ here=`pwd`; \
+ if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
+ include_option=--etags-include; \
+ empty_fix=.; \
+ else \
+ include_option=--include; \
+ empty_fix=; \
+ fi; \
+ list='$(SUBDIRS)'; for subdir in $$list; do \
+ if test "$$subdir" = .; then :; else \
+ test ! -f $$subdir/TAGS || \
+ set "$$@" "$$include_option=$$here/$$subdir/TAGS"; \
+ fi; \
+ done; \
+ list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+ unique=`for i in $$list; do \
+ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+ done | \
+ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+ END { if (nonempty) { for (i in files) print i; }; }'`; \
+ shift; \
+ if test -z "$(ETAGS_ARGS)$$*$$unique"; then :; else \
+ test -n "$$unique" || unique=$$empty_fix; \
+ if test $$# -gt 0; then \
+ $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
+ "$$@" $$unique; \
+ else \
+ $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
+ $$unique; \
+ fi; \
+ fi
+ctags: CTAGS
+CTAGS: ctags-recursive $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
+ $(TAGS_FILES) $(LISP)
+ list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+ unique=`for i in $$list; do \
+ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+ done | \
+ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+ END { if (nonempty) { for (i in files) print i; }; }'`; \
+ test -z "$(CTAGS_ARGS)$$unique" \
+ || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
+ $$unique
+
+GTAGS:
+ here=`$(am__cd) $(top_builddir) && pwd` \
+ && $(am__cd) $(top_srcdir) \
+ && gtags -i $(GTAGS_ARGS) "$$here"
+
+distclean-tags:
+ -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
+
+distdir: $(DISTFILES)
+ @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+ topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+ list='$(DISTFILES)'; \
+ dist_files=`for file in $$list; do echo $$file; done | \
+ sed -e "s|^$$srcdirstrip/||;t" \
+ -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
+ case $$dist_files in \
+ */*) $(MKDIR_P) `echo "$$dist_files" | \
+ sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
+ sort -u` ;; \
+ esac; \
+ for file in $$dist_files; do \
+ if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
+ if test -d $$d/$$file; then \
+ dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
+ if test -d "$(distdir)/$$file"; then \
+ find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx
{} \;; \
+ fi; \
+ if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
+ cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \
+ find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx
{} \;; \
+ fi; \
+ cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \
+ else \
+ test -f "$(distdir)/$$file" \
+ || cp -p $$d/$$file "$(distdir)/$$file" \
+ || exit 1; \
+ fi; \
+ done
+ @list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
+ if test "$$subdir" = .; then :; else \
+ test -d "$(distdir)/$$subdir" \
+ || $(MKDIR_P) "$(distdir)/$$subdir" \
+ || exit 1; \
+ fi; \
+ done
+ @list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
+ if test "$$subdir" = .; then :; else \
+ dir1=$$subdir; dir2="$(distdir)/$$subdir"; \
+ $(am__relativize); \
+ new_distdir=$$reldir; \
+ dir1=$$subdir; dir2="$(top_distdir)"; \
+ $(am__relativize); \
+ new_top_distdir=$$reldir; \
+ echo " (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS)
top_distdir="$$new_top_distdir" distdir="$$new_distdir" \\"; \
+ echo " am__remove_distdir=: am__skip_length_check=:
am__skip_mode_fix=: distdir)"; \
+ ($(am__cd) $$subdir && \
+ $(MAKE) $(AM_MAKEFLAGS) \
+ top_distdir="$$new_top_distdir" \
+ distdir="$$new_distdir" \
+ am__remove_distdir=: \
+ am__skip_length_check=: \
+ am__skip_mode_fix=: \
+ distdir) \
+ || exit 1; \
+ fi; \
+ done
+check-am: all-am
+check: check-recursive
+all-am: Makefile $(DATA)
+installdirs: installdirs-recursive
+installdirs-am:
+ for dir in "$(DESTDIR)$(htmldir)"; do \
+ test -z "$$dir" || $(MKDIR_P) "$$dir"; \
+ done
+install: install-recursive
+install-exec: install-exec-recursive
+install-data: install-data-recursive
+uninstall: uninstall-recursive
+
+install-am: all-am
+ @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
+
+installcheck: installcheck-recursive
+install-strip:
+ $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+ install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+ `test -z '$(STRIP)' || \
+ echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
+mostlyclean-generic:
+
+clean-generic:
+ -test -z "$(CLEANFILES)" || rm -f $(CLEANFILES)
+
+distclean-generic:
+ -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
+ -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f
$(CONFIG_CLEAN_VPATH_FILES)
+
+maintainer-clean-generic:
+ @echo "This command is intended for maintainers to use"
+ @echo "it deletes files that may require special tools to rebuild."
+clean: clean-recursive
+
+clean-am: clean-generic clean-local mostlyclean-am
+
+distclean: distclean-recursive
+ -rm -f Makefile
+distclean-am: clean-am distclean-generic distclean-tags
+
+dvi: dvi-recursive
+
+dvi-am:
+
+html: html-recursive
+
+html-am:
+
+info: info-recursive
+
+info-am:
+
+install-data-am: install-data-local install-htmlDATA
+
+install-dvi: install-dvi-recursive
+
+install-dvi-am:
+
+install-exec-am:
+
+install-html: install-html-recursive
+
+install-html-am:
+
+install-info: install-info-recursive
+
+install-info-am:
+
+install-man:
+
+install-pdf: install-pdf-recursive
+
+install-pdf-am:
+
+install-ps: install-ps-recursive
+
+install-ps-am:
+
+installcheck-am:
+
+maintainer-clean: maintainer-clean-recursive
+ -rm -f Makefile
+maintainer-clean-am: distclean-am maintainer-clean-generic
+
+mostlyclean: mostlyclean-recursive
+
+mostlyclean-am: mostlyclean-generic
+
+pdf: pdf-recursive
+
+pdf-am:
+
+ps: ps-recursive
+
+ps-am:
+
+uninstall-am: uninstall-htmlDATA
+
+.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) ctags-recursive \
+ install-am install-strip tags-recursive
+
+.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
+ all all-am check check-am clean clean-generic clean-local \
+ ctags ctags-recursive distclean distclean-generic \
+ distclean-tags distdir dvi dvi-am html html-am info info-am \
+ install install-am install-data install-data-am \
+ install-data-local install-dvi install-dvi-am install-exec \
+ install-exec-am install-html install-html-am install-htmlDATA \
+ install-info install-info-am install-man install-pdf \
+ install-pdf-am install-ps install-ps-am install-strip \
+ installcheck installcheck-am installdirs installdirs-am \
+ maintainer-clean maintainer-clean-generic mostlyclean \
+ mostlyclean-generic pdf pdf-am ps ps-am tags tags-recursive \
+ uninstall uninstall-am uninstall-htmlDATA
+
+
+#doc_DATA = autoyast.pdf
+
+components: components.ent
+ bin/components.sh noref > components.ent
+
+examples: examples.ent
+ bin/examples.sh > examples.ent
+
+html/index.html: autoyast.xml
+ XML_CATALOG_FILES=/etc/xml/catalog \
+ time -p /usr/bin/xsltproc --xinclude \
+ -stringparam chunk.fast '1' \
+ --stringparam html.stylesheet $(STYLESHEET_CSS) \
+ /usr/share/YaST2/data/docbook/stylesheets/customize-html.xsl
autoyast.xml
+ XML_CATALOG_FILES=/etc/xml/catalog \
+ time -p /usr/bin/xsltproc --xinclude \
+ -stringparam base.dir 'html/devel/' \
+ -stringparam chunk.fast '1' \
+ --stringparam html.stylesheet $(STYLESHEET_CSS) \
+ /usr/share/YaST2/data/docbook/stylesheets/customize-html.xsl
creating_autoyast2_modules.xml
+ cd html/devel; \
+ ln -s ../default.css ./default.css; \
+ ln -s ../images ./images
+ cd ../..
+
+html/index.html: autoyast.xml
+ XML_CATALOG_FILES=/etc/xml/catalog \
+ /usr/bin/xsltproc --xinclude
/usr/share/YaST2/data/docbook/stylesheets/customize-html.xsl \
+ $<
+
+#autoyast.fo: autoyast.xml
+# XML_CATALOG_FILES=/etc/xml/catalog \
+# /usr/bin/xsltproc --nonet --xinclude \
+# -o $@ /usr/share/YaST2/data/docbook/stylesheets/customize-fo.xsl $<
+
+#autoyast.fo: autoyast.xml
+# saxon -o autoyast.fo autoyast.xml
/usr/share/YaST2/data/docbook/stylesheets/customize-fo.xsl
+
+#autoyast.pdf: autoyast.fo
+# fop -q $< $@
+
+autoyast.xml: images.ent examples components
+
+html/yast2docs.css: html/index.html
+ cp /usr/share/YaST2/data/docbook/css/yast2docs.css html
+ cp -a $(ydatadir)/docbook/images html
+
+html/default.css: html/index.html webimages
+ cp web/default.css html
+
+images.ent:
+ @make -r -C images/WEB -f makefile.ent ima
+ mv ../images.ent .
+
+: images.ent chunks webimages
+
+webimages:
+ mkdir -p html/img
+ cp -a images/WEB/*png html/img
+
+.PHONY: images examples.ent components.ent
+
+images: images/EPS/* images/PNG/*
+ @if ! [ -e "img" ]; then \
+ mkdir -p img; \
+ fi
+ @if ! [ -e "img/Makefile" ]; then \
+ ln -s ../images/makefile.images img/Makefile; \
+ fi
+
+ @echo "generating PNG files for all outputs...";
+ @if [ "$(IMAGES)" = "all" ]; then \
+ rm -f img/*.{png,pdf}; \
+ fi;
+
+ @for j in `bin/findImages.sh` ; do \
+ if [ -e "images/EPS/$$j" ]; then \
+ source="images/EPS/$$j"; eps="1";\
+ elif [ -e "images/PNG/$$j" ]; then \
+ source="images/PNG/$$j"; eps="0"; \
+ fi; \
+ dest=`echo "img/$$j" | sed -e "s|_|-|g;s|.eps||g;s|.png||g;"`; \
+ if [ -e "$$source" ]; then \
+ if [ ! -f $$dest".png" ] || [ $$dest".png" -ot $$source
]; then \
+ if [ $$eps == "1" ]; then \
+ echo " converting $$source ->
$$dest'.pdf'"; \
+ bin/epstopdf12 -o=$$dest".pdf"
$$source; \
+ echo " converting $$source ->
$$dest'.png'"; \
+ convert $$source $$dest".png"; \
+ else \
+ echo " linking $$source ->
$$dest'.png'"; \
+ convert -depth 8 $$source $$dest".png";
\
+ fi; \
+ fi; \
+ fi; \
+ done
+ @make -r -C img ima
+
+install-data-local:
+ install -d -m 755 $(DESTDIR)$(htmldir)
+ cp -a $(srcdir)/html/images $(DESTDIR)$(htmldir)
+ cp -a $(srcdir)/html/img $(DESTDIR)$(htmldir)
+ cp -a $(srcdir)/html/devel $(DESTDIR)$(htmldir)
+
+clean-local:
+ rm -rf html
+
+# Tell versions [3.59,3.63) of GNU make to not export all variables.
+# Otherwise a system limit (for SysV at least) may be exceeded.
+.NOEXPORT:

Added: trunk/autoinstallation/doc/xml/Makefile.am
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Makefile.am?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/Makefile.am (added)
+++ trunk/autoinstallation/doc/xml/Makefile.am Mon Aug 8 14:12:13 2011
@@ -0,0 +1,137 @@
+#
+# Makefile.am for y2c_autoinst/doc
+#
+# $Id: Makefile.am 63765 2011-04-11 15:40:31Z ug $
+#
+
+SUBDIRS =
+htmldir = $(docdir)/html
+
+xml_file = autoyast.xml
+xml_files = $(wildcard *.xml)
+
+
+EXTRA_DIST = $(xml_files) $(wildcard *.xsl) web/default.css
+
+CLEANFILES = .html.sum profile.dtd.xml elements \
+ elements.xml elements.ent profile.dtd.xml examples.ent\
+ components.ent .ps.sum autoyast.out autoyast.pdf autoyast.fo \
+ images.ent
+
+STYLESHEET_CSS = default.css
+
+html_DATA = $(wildcard html/*.html) \
+ html/index.html \
+ html/yast2docs.css \
+ html/default.css
+
+#doc_DATA = autoyast.pdf
+
+components: components.ent
+ bin/components.sh noref > components.ent
+
+examples: examples.ent
+ bin/examples.sh > examples.ent
+
+html/index.html: autoyast.xml
+ XML_CATALOG_FILES=@XML_CATALOG@ \
+ time -p @XSLTPROC@ --xinclude \
+ -stringparam chunk.fast '1' \
+ --stringparam html.stylesheet $(STYLESHEET_CSS) \
+ @STYLESHEET_HTML@ autoyast.xml
+ XML_CATALOG_FILES=@XML_CATALOG@ \
+ time -p @XSLTPROC@ --xinclude \
+ -stringparam base.dir 'html/devel/' \
+ -stringparam chunk.fast '1' \
+ --stringparam html.stylesheet $(STYLESHEET_CSS) \
+ @STYLESHEET_HTML@ creating_autoyast2_modules.xml
+ cd html/devel; \
+ ln -s ../default.css ./default.css; \
+ ln -s ../images ./images
+ cd ../..
+
+html/index.html: autoyast.xml
+ XML_CATALOG_FILES=@XML_CATALOG@ \
+ @XSLTPROC@ --xinclude @STYLESHEET_HTML@ \
+ $<
+
+#autoyast.fo: autoyast.xml
+# XML_CATALOG_FILES=@XML_CATALOG@ \
+# @XSLTPROC@ @XSLTPROC_FLAGS@ --xinclude \
+# -o $@ @STYLESHEET_PDF@ $<
+
+#autoyast.fo: autoyast.xml
+# saxon -o autoyast.fo autoyast.xml @STYLESHEET_PDF@
+
+#autoyast.pdf: autoyast.fo
+# fop -q $< $@
+
+autoyast.xml: images.ent examples components
+
+html/yast2docs.css: html/index.html
+ cp @STYLESHEET_CSS@ html
+ cp -a $(ydatadir)/docbook/images html
+
+html/default.css: html/index.html webimages
+ cp web/default.css html
+
+images.ent:
+ @make -r -C images/WEB -f makefile.ent ima
+ mv ../images.ent .
+
+: images.ent chunks webimages
+
+
+webimages:
+ mkdir -p html/img
+ cp -a images/WEB/*png html/img
+
+
+.PHONY: images examples.ent components.ent
+
+images: images/EPS/* images/PNG/*
+ @if ! [ -e "img" ]; then \
+ mkdir -p img; \
+ fi
+ @if ! [ -e "img/Makefile" ]; then \
+ ln -s ../images/makefile.images img/Makefile; \
+ fi
+
+ @echo "generating PNG files for all outputs...";
+ @if [ "$(IMAGES)" = "all" ]; then \
+ rm -f img/*.{png,pdf}; \
+ fi;
+
+ @for j in `bin/findImages.sh` ; do \
+ if [ -e "images/EPS/$$j" ]; then \
+ source="images/EPS/$$j"; eps="1";\
+ elif [ -e "images/PNG/$$j" ]; then \
+ source="images/PNG/$$j"; eps="0"; \
+ fi; \
+ dest=`echo "img/$$j" | sed -e "s|_|-|g;s|.eps||g;s|.png||g;"`; \
+ if [ -e "$$source" ]; then \
+ if [ ! -f $$dest".png" ] || [ $$dest".png" -ot $$source
]; then \
+ if [ $$eps == "1" ]; then \
+ echo " converting $$source ->
$$dest'.pdf'"; \
+ bin/epstopdf12 -o=$$dest".pdf"
$$source; \
+ echo " converting $$source ->
$$dest'.png'"; \
+ convert $$source $$dest".png"; \
+ else \
+ echo " linking $$source ->
$$dest'.png'"; \
+ convert -depth 8 $$source $$dest".png";
\
+ fi; \
+ fi; \
+ fi; \
+ done
+ @make -r -C img ima
+
+
+install-data-local:
+ install -d -m 755 $(DESTDIR)$(htmldir)
+ cp -a $(srcdir)/html/images $(DESTDIR)$(htmldir)
+ cp -a $(srcdir)/html/img $(DESTDIR)$(htmldir)
+ cp -a $(srcdir)/html/devel $(DESTDIR)$(htmldir)
+
+clean-local:
+ rm -rf html
+

Added: trunk/autoinstallation/doc/xml/Makefile.in
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Makefile.in?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/Makefile.in (added)
+++ trunk/autoinstallation/doc/xml/Makefile.in Mon Aug 8 14:12:13 2011
@@ -0,0 +1,730 @@
+# Makefile.in generated by automake 1.11.1 from Makefile.am.
+# @configure_input@
+
+# Copyright (C) 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002,
+# 2003, 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation,
+# Inc.
+# This Makefile.in is free software; the Free Software Foundation
+# gives unlimited permission to copy and/or distribute it,
+# with or without modifications, as long as this notice is preserved.
+
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
+# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+# PARTICULAR PURPOSE.
+
+@SET_MAKE@
+
+#
+# Makefile.am for y2c_autoinst/doc
+#
+# $Id: Makefile.am 63765 2011-04-11 15:40:31Z ug $
+#
+
+VPATH = @srcdir@
+pkgdatadir = $(datadir)/@PACKAGE@
+pkgincludedir = $(includedir)/@PACKAGE@
+pkglibdir = $(libdir)/@PACKAGE@
+pkglibexecdir = $(libexecdir)/@PACKAGE@
+am__cd = CDPATH="$${ZSH_VERSION+.}$(PATH_SEPARATOR)" && cd
+install_sh_DATA = $(install_sh) -c -m 644
+install_sh_PROGRAM = $(install_sh) -c
+install_sh_SCRIPT = $(install_sh) -c
+INSTALL_HEADER = $(INSTALL_DATA)
+transform = $(program_transform_name)
+NORMAL_INSTALL = :
+PRE_INSTALL = :
+POST_INSTALL = :
+NORMAL_UNINSTALL = :
+PRE_UNINSTALL = :
+POST_UNINSTALL = :
+build_triplet = @build@
+host_triplet = @host@
+target_triplet = @target@
+subdir = doc/xml
+DIST_COMMON = $(srcdir)/Makefile.am $(srcdir)/Makefile.in
+ACLOCAL_M4 = $(top_srcdir)/aclocal.m4
+am__aclocal_m4_deps = $(top_srcdir)/configure.in
+am__configure_deps = $(am__aclocal_m4_deps) $(CONFIGURE_DEPENDENCIES) \
+ $(ACLOCAL_M4)
+mkinstalldirs = $(install_sh) -d
+CONFIG_CLEAN_FILES =
+CONFIG_CLEAN_VPATH_FILES =
+SOURCES =
+DIST_SOURCES =
+RECURSIVE_TARGETS = all-recursive check-recursive dvi-recursive \
+ html-recursive info-recursive install-data-recursive \
+ install-dvi-recursive install-exec-recursive \
+ install-html-recursive install-info-recursive \
+ install-pdf-recursive install-ps-recursive install-recursive \
+ installcheck-recursive installdirs-recursive pdf-recursive \
+ ps-recursive uninstall-recursive
+am__vpath_adj_setup = srcdirstrip=`echo "$(srcdir)" | sed 's|.|.|g'`;
+am__vpath_adj = case $$p in \
+ $(srcdir)/*) f=`echo "$$p" | sed "s|^$$srcdirstrip/||"`;; \
+ *) f=$$p;; \
+ esac;
+am__strip_dir = f=`echo $$p | sed -e 's|^.*/||'`;
+am__install_max = 40
+am__nobase_strip_setup = \
+ srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*|]/\\\\&/g'`
+am__nobase_strip = \
+ for p in $$list; do echo "$$p"; done | sed -e "s|$$srcdirstrip/||"
+am__nobase_list = $(am__nobase_strip_setup); \
+ for p in $$list; do echo "$$p $$p"; done | \
+ sed "s| $$srcdirstrip/| |;"' / .*\//!s/ .*/ ./; s,\( .*\)/[^/]*$$,\1,' | \
+ $(AWK) 'BEGIN { files["."] = "" } { files[$$2] = files[$$2] " " $$1; \
+ if (++n[$$2] == $(am__install_max)) \
+ { print $$2, files[$$2]; n[$$2] = 0; files[$$2] = "" } } \
+ END { for (dir in files) print dir, files[dir] }'
+am__base_list = \
+ sed '$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;$$!N;s/\n/ /g' | \
+ sed '$$!N;$$!N;$$!N;$$!N;s/\n/ /g'
+am__installdirs = "$(DESTDIR)$(htmldir)"
+DATA = $(html_DATA)
+RECURSIVE_CLEAN_TARGETS = mostlyclean-recursive clean-recursive \
+ distclean-recursive maintainer-clean-recursive
+AM_RECURSIVE_TARGETS = $(RECURSIVE_TARGETS:-recursive=) \
+ $(RECURSIVE_CLEAN_TARGETS:-recursive=) tags TAGS ctags CTAGS \
+ distdir
+ETAGS = etags
+CTAGS = ctags
+DIST_SUBDIRS = $(SUBDIRS)
+DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST)
+am__relativize = \
+ dir0=`pwd`; \
+ sed_first='s,^\([^/]*\)/.*$$,\1,'; \
+ sed_rest='s,^[^/]*/*,,'; \
+ sed_last='s,^.*/\([^/]*\)$$,\1,'; \
+ sed_butlast='s,/*[^/]*$$,,'; \
+ while test -n "$$dir1"; do \
+ first=`echo "$$dir1" | sed -e "$$sed_first"`; \
+ if test "$$first" != "."; then \
+ if test "$$first" = ".."; then \
+ dir2=`echo "$$dir0" | sed -e "$$sed_last"`/"$$dir2"; \
+ dir0=`echo "$$dir0" | sed -e "$$sed_butlast"`; \
+ else \
+ first2=`echo "$$dir2" | sed -e "$$sed_first"`; \
+ if test "$$first2" = "$$first"; then \
+ dir2=`echo "$$dir2" | sed -e "$$sed_rest"`; \
+ else \
+ dir2="../$$dir2"; \
+ fi; \
+ dir0="$$dir0"/"$$first"; \
+ fi; \
+ fi; \
+ dir1=`echo "$$dir1" | sed -e "$$sed_rest"`; \
+ done; \
+ reldir="$$dir2"
+ACLOCAL = @ACLOCAL@
+AMTAR = @AMTAR@
+AUTOCONF = @AUTOCONF@
+AUTOHEADER = @AUTOHEADER@
+AUTOMAKE = @AUTOMAKE@
+AWK = @AWK@
+CAT_ENTRY_END = @CAT_ENTRY_END@
+CAT_ENTRY_START = @CAT_ENTRY_START@
+CYGPATH_W = @CYGPATH_W@
+DEFS = @DEFS@
+DOCBOOK_ROOT = @DOCBOOK_ROOT@
+ECHO_C = @ECHO_C@
+ECHO_N = @ECHO_N@
+ECHO_T = @ECHO_T@
+INSTALL = @INSTALL@
+INSTALL_DATA = @INSTALL_DATA@
+INSTALL_PROGRAM = @INSTALL_PROGRAM@
+INSTALL_SCRIPT = @INSTALL_SCRIPT@
+INSTALL_STRIP_PROGRAM = @INSTALL_STRIP_PROGRAM@
+LIBOBJS = @LIBOBJS@
+LIBS = @LIBS@
+LN_S = @LN_S@
+LTLIBOBJS = @LTLIBOBJS@
+MAINTAINER = @MAINTAINER@
+MAKEINFO = @MAKEINFO@
+MKDIR_P = @MKDIR_P@
+PACKAGE = @PACKAGE@
+PACKAGE_BUGREPORT = @PACKAGE_BUGREPORT@
+PACKAGE_NAME = @PACKAGE_NAME@
+PACKAGE_STRING = @PACKAGE_STRING@
+PACKAGE_TARNAME = @PACKAGE_TARNAME@
+PACKAGE_URL = @PACKAGE_URL@
+PACKAGE_VERSION = @PACKAGE_VERSION@
+PATH_SEPARATOR = @PATH_SEPARATOR@
+PKG_CONFIG_PATH = @PKG_CONFIG_PATH@
+RPMNAME = @RPMNAME@
+SET_MAKE = @SET_MAKE@
+SHELL = @SHELL@
+STRIP = @STRIP@
+STYLESHEET_CSS = default.css
+STYLESHEET_HTML = @STYLESHEET_HTML@
+STYLESHEET_PDF = @STYLESHEET_PDF@
+STYLESHEET_YCPDOC = @STYLESHEET_YCPDOC@
+STYLESHEET_YDOC = @STYLESHEET_YDOC@
+VERSION = @VERSION@
+XGETTEXT = @XGETTEXT@
+XML_CATALOG = @XML_CATALOG@
+XSLTPROC = @XSLTPROC@
+XSLTPROC_FLAGS = @XSLTPROC_FLAGS@
+Y2DEVTOOLS_PREFIX = @Y2DEVTOOLS_PREFIX@
+YCPC = @YCPC@
+YCPDOC = @YCPDOC@
+YCPMAKEDEP = @YCPMAKEDEP@
+abs_builddir = @abs_builddir@
+abs_srcdir = @abs_srcdir@
+abs_top_builddir = @abs_top_builddir@
+abs_top_srcdir = @abs_top_srcdir@
+agentdir = @agentdir@
+am__leading_dot = @am__leading_dot@
+am__tar = @am__tar@
+am__untar = @am__untar@
+bindir = @bindir@
+build = @build@
+build_alias = @build_alias@
+build_cpu = @build_cpu@
+build_os = @build_os@
+build_vendor = @build_vendor@
+builddir = @builddir@
+clientdir = @clientdir@
+datadir = @datadir@
+datarootdir = @datarootdir@
+desktopdir = @desktopdir@
+docdir = @docdir@
+dvidir = @dvidir@
+exec_prefix = @exec_prefix@
+execcompdir = @execcompdir@
+fillupdir = @fillupdir@
+host = @host@
+host_alias = @host_alias@
+host_cpu = @host_cpu@
+host_os = @host_os@
+host_vendor = @host_vendor@
+htmldir = $(docdir)/html
+imagedir = @imagedir@
+includedir = @includedir@
+infodir = @infodir@
+install_sh = @install_sh@
+libdir = @libdir@
+libexecdir = @libexecdir@
+localedir = @localedir@
+localstatedir = @localstatedir@
+mandir = @mandir@
+mkdir_p = @mkdir_p@
+moduledir = @moduledir@
+oldincludedir = @oldincludedir@
+pdfdir = @pdfdir@
+pkgconfigdatadir = @pkgconfigdatadir@
+pkgconfigdir = @pkgconfigdir@
+plugindir = @plugindir@
+potdir = @potdir@
+prefix = @prefix@
+program_transform_name = @program_transform_name@
+psdir = @psdir@
+sbindir = @sbindir@
+schemadir = @schemadir@
+scrconfdir = @scrconfdir@
+sharedstatedir = @sharedstatedir@
+srcdir = @srcdir@
+sysconfdir = @sysconfdir@
+target = @target@
+target_alias = @target_alias@
+target_cpu = @target_cpu@
+target_os = @target_os@
+target_vendor = @target_vendor@
+themedir = @themedir@
+top_build_prefix = @top_build_prefix@
+top_builddir = @top_builddir@
+top_srcdir = @top_srcdir@
+yast2dir = @yast2dir@
+ybindir = @ybindir@
+ydatadir = @ydatadir@
+yncludedir = @yncludedir@
+ystartupdir = @ystartupdir@
+SUBDIRS =
+xml_file = autoyast.xml
+xml_files = $(wildcard *.xml)
+EXTRA_DIST = $(xml_files) $(wildcard *.xsl) web/default.css
+CLEANFILES = .html.sum profile.dtd.xml elements \
+ elements.xml elements.ent profile.dtd.xml examples.ent\
+ components.ent .ps.sum autoyast.out autoyast.pdf autoyast.fo \
+ images.ent
+
+html_DATA = $(wildcard html/*.html) \
+ html/index.html \
+ html/yast2docs.css \
+ html/default.css
+
+all: all-recursive
+
+.SUFFIXES:
+$(srcdir)/Makefile.in: $(srcdir)/Makefile.am $(am__configure_deps)
+ @for dep in $?; do \
+ case '$(am__configure_deps)' in \
+ *$$dep*) \
+ ( cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh ) \
+ && { if test -f $@; then exit 0; else break; fi; }; \
+ exit 1;; \
+ esac; \
+ done; \
+ echo ' cd $(top_srcdir) && $(AUTOMAKE) --gnu doc/xml/Makefile'; \
+ $(am__cd) $(top_srcdir) && \
+ $(AUTOMAKE) --gnu doc/xml/Makefile
+.PRECIOUS: Makefile
+Makefile: $(srcdir)/Makefile.in $(top_builddir)/config.status
+ @case '$?' in \
+ *config.status*) \
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh;; \
+ *) \
+ echo ' cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@
$(am__depfiles_maybe)'; \
+ cd $(top_builddir) && $(SHELL) ./config.status $(subdir)/$@
$(am__depfiles_maybe);; \
+ esac;
+
+$(top_builddir)/config.status: $(top_srcdir)/configure
$(CONFIG_STATUS_DEPENDENCIES)
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+
+$(top_srcdir)/configure: $(am__configure_deps)
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(ACLOCAL_M4): $(am__aclocal_m4_deps)
+ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh
+$(am__aclocal_m4_deps):
+install-htmlDATA: $(html_DATA)
+ @$(NORMAL_INSTALL)
+ test -z "$(htmldir)" || $(MKDIR_P) "$(DESTDIR)$(htmldir)"
+ @list='$(html_DATA)'; test -n "$(htmldir)" || list=; \
+ for p in $$list; do \
+ if test -f "$$p"; then d=; else d="$(srcdir)/"; fi; \
+ echo "$$d$$p"; \
+ done | $(am__base_list) | \
+ while read files; do \
+ echo " $(INSTALL_DATA) $$files '$(DESTDIR)$(htmldir)'"; \
+ $(INSTALL_DATA) $$files "$(DESTDIR)$(htmldir)" || exit $$?; \
+ done
+
+uninstall-htmlDATA:
+ @$(NORMAL_UNINSTALL)
+ @list='$(html_DATA)'; test -n "$(htmldir)" || list=; \
+ files=`for p in $$list; do echo $$p; done | sed -e 's|^.*/||'`; \
+ test -n "$$files" || exit 0; \
+ echo " ( cd '$(DESTDIR)$(htmldir)' && rm -f" $$files ")"; \
+ cd "$(DESTDIR)$(htmldir)" && rm -f $$files
+
+# This directory's subdirectories are mostly independent; you can cd
+# into them and run `make' without going through this Makefile.
+# To change the values of `make' variables: instead of editing Makefiles,
+# (1) if the variable is set in `config.status', edit `config.status'
+# (which will cause the Makefiles to be regenerated when you run `make');
+# (2) otherwise, pass the desired values on the `make' command line.
+$(RECURSIVE_TARGETS):
+ @fail= failcom='exit 1'; \
+ for f in x $$MAKEFLAGS; do \
+ case $$f in \
+ *=* | --[!k]*);; \
+ *k*) failcom='fail=yes';; \
+ esac; \
+ done; \
+ dot_seen=no; \
+ target=`echo $@ | sed s/-recursive//`; \
+ list='$(SUBDIRS)'; for subdir in $$list; do \
+ echo "Making $$target in $$subdir"; \
+ if test "$$subdir" = "."; then \
+ dot_seen=yes; \
+ local_target="$$target-am"; \
+ else \
+ local_target="$$target"; \
+ fi; \
+ ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+ || eval $$failcom; \
+ done; \
+ if test "$$dot_seen" = "no"; then \
+ $(MAKE) $(AM_MAKEFLAGS) "$$target-am" || exit 1; \
+ fi; test -z "$$fail"
+
+$(RECURSIVE_CLEAN_TARGETS):
+ @fail= failcom='exit 1'; \
+ for f in x $$MAKEFLAGS; do \
+ case $$f in \
+ *=* | --[!k]*);; \
+ *k*) failcom='fail=yes';; \
+ esac; \
+ done; \
+ dot_seen=no; \
+ case "$@" in \
+ distclean-* | maintainer-clean-*) list='$(DIST_SUBDIRS)' ;; \
+ *) list='$(SUBDIRS)' ;; \
+ esac; \
+ rev=''; for subdir in $$list; do \
+ if test "$$subdir" = "."; then :; else \
+ rev="$$subdir $$rev"; \
+ fi; \
+ done; \
+ rev="$$rev ."; \
+ target=`echo $@ | sed s/-recursive//`; \
+ for subdir in $$rev; do \
+ echo "Making $$target in $$subdir"; \
+ if test "$$subdir" = "."; then \
+ local_target="$$target-am"; \
+ else \
+ local_target="$$target"; \
+ fi; \
+ ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS) $$local_target) \
+ || eval $$failcom; \
+ done && test -z "$$fail"
+tags-recursive:
+ list='$(SUBDIRS)'; for subdir in $$list; do \
+ test "$$subdir" = . || ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS)
tags); \
+ done
+ctags-recursive:
+ list='$(SUBDIRS)'; for subdir in $$list; do \
+ test "$$subdir" = . || ($(am__cd) $$subdir && $(MAKE) $(AM_MAKEFLAGS)
ctags); \
+ done
+
+ID: $(HEADERS) $(SOURCES) $(LISP) $(TAGS_FILES)
+ list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+ unique=`for i in $$list; do \
+ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+ done | \
+ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+ END { if (nonempty) { for (i in files) print i; }; }'`; \
+ mkid -fID $$unique
+tags: TAGS
+
+TAGS: tags-recursive $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
+ $(TAGS_FILES) $(LISP)
+ set x; \
+ here=`pwd`; \
+ if ($(ETAGS) --etags-include --version) >/dev/null 2>&1; then \
+ include_option=--etags-include; \
+ empty_fix=.; \
+ else \
+ include_option=--include; \
+ empty_fix=; \
+ fi; \
+ list='$(SUBDIRS)'; for subdir in $$list; do \
+ if test "$$subdir" = .; then :; else \
+ test ! -f $$subdir/TAGS || \
+ set "$$@" "$$include_option=$$here/$$subdir/TAGS"; \
+ fi; \
+ done; \
+ list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+ unique=`for i in $$list; do \
+ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+ done | \
+ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+ END { if (nonempty) { for (i in files) print i; }; }'`; \
+ shift; \
+ if test -z "$(ETAGS_ARGS)$$*$$unique"; then :; else \
+ test -n "$$unique" || unique=$$empty_fix; \
+ if test $$# -gt 0; then \
+ $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
+ "$$@" $$unique; \
+ else \
+ $(ETAGS) $(ETAGSFLAGS) $(AM_ETAGSFLAGS) $(ETAGS_ARGS) \
+ $$unique; \
+ fi; \
+ fi
+ctags: CTAGS
+CTAGS: ctags-recursive $(HEADERS) $(SOURCES) $(TAGS_DEPENDENCIES) \
+ $(TAGS_FILES) $(LISP)
+ list='$(SOURCES) $(HEADERS) $(LISP) $(TAGS_FILES)'; \
+ unique=`for i in $$list; do \
+ if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
+ done | \
+ $(AWK) '{ files[$$0] = 1; nonempty = 1; } \
+ END { if (nonempty) { for (i in files) print i; }; }'`; \
+ test -z "$(CTAGS_ARGS)$$unique" \
+ || $(CTAGS) $(CTAGSFLAGS) $(AM_CTAGSFLAGS) $(CTAGS_ARGS) \
+ $$unique
+
+GTAGS:
+ here=`$(am__cd) $(top_builddir) && pwd` \
+ && $(am__cd) $(top_srcdir) \
+ && gtags -i $(GTAGS_ARGS) "$$here"
+
+distclean-tags:
+ -rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
+
+distdir: $(DISTFILES)
+ @srcdirstrip=`echo "$(srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+ topsrcdirstrip=`echo "$(top_srcdir)" | sed 's/[].[^$$\\*]/\\\\&/g'`; \
+ list='$(DISTFILES)'; \
+ dist_files=`for file in $$list; do echo $$file; done | \
+ sed -e "s|^$$srcdirstrip/||;t" \
+ -e "s|^$$topsrcdirstrip/|$(top_builddir)/|;t"`; \
+ case $$dist_files in \
+ */*) $(MKDIR_P) `echo "$$dist_files" | \
+ sed '/\//!d;s|^|$(distdir)/|;s,/[^/]*$$,,' | \
+ sort -u` ;; \
+ esac; \
+ for file in $$dist_files; do \
+ if test -f $$file || test -d $$file; then d=.; else d=$(srcdir); fi; \
+ if test -d $$d/$$file; then \
+ dir=`echo "/$$file" | sed -e 's,/[^/]*$$,,'`; \
+ if test -d "$(distdir)/$$file"; then \
+ find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx
{} \;; \
+ fi; \
+ if test -d $(srcdir)/$$file && test $$d != $(srcdir); then \
+ cp -fpR $(srcdir)/$$file "$(distdir)$$dir" || exit 1; \
+ find "$(distdir)/$$file" -type d ! -perm -700 -exec chmod u+rwx
{} \;; \
+ fi; \
+ cp -fpR $$d/$$file "$(distdir)$$dir" || exit 1; \
+ else \
+ test -f "$(distdir)/$$file" \
+ || cp -p $$d/$$file "$(distdir)/$$file" \
+ || exit 1; \
+ fi; \
+ done
+ @list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
+ if test "$$subdir" = .; then :; else \
+ test -d "$(distdir)/$$subdir" \
+ || $(MKDIR_P) "$(distdir)/$$subdir" \
+ || exit 1; \
+ fi; \
+ done
+ @list='$(DIST_SUBDIRS)'; for subdir in $$list; do \
+ if test "$$subdir" = .; then :; else \
+ dir1=$$subdir; dir2="$(distdir)/$$subdir"; \
+ $(am__relativize); \
+ new_distdir=$$reldir; \
+ dir1=$$subdir; dir2="$(top_distdir)"; \
+ $(am__relativize); \
+ new_top_distdir=$$reldir; \
+ echo " (cd $$subdir && $(MAKE) $(AM_MAKEFLAGS)
top_distdir="$$new_top_distdir" distdir="$$new_distdir" \\"; \
+ echo " am__remove_distdir=: am__skip_length_check=:
am__skip_mode_fix=: distdir)"; \
+ ($(am__cd) $$subdir && \
+ $(MAKE) $(AM_MAKEFLAGS) \
+ top_distdir="$$new_top_distdir" \
+ distdir="$$new_distdir" \
+ am__remove_distdir=: \
+ am__skip_length_check=: \
+ am__skip_mode_fix=: \
+ distdir) \
+ || exit 1; \
+ fi; \
+ done
+check-am: all-am
+check: check-recursive
+all-am: Makefile $(DATA)
+installdirs: installdirs-recursive
+installdirs-am:
+ for dir in "$(DESTDIR)$(htmldir)"; do \
+ test -z "$$dir" || $(MKDIR_P) "$$dir"; \
+ done
+install: install-recursive
+install-exec: install-exec-recursive
+install-data: install-data-recursive
+uninstall: uninstall-recursive
+
+install-am: all-am
+ @$(MAKE) $(AM_MAKEFLAGS) install-exec-am install-data-am
+
+installcheck: installcheck-recursive
+install-strip:
+ $(MAKE) $(AM_MAKEFLAGS) INSTALL_PROGRAM="$(INSTALL_STRIP_PROGRAM)" \
+ install_sh_PROGRAM="$(INSTALL_STRIP_PROGRAM)" INSTALL_STRIP_FLAG=-s \
+ `test -z '$(STRIP)' || \
+ echo "INSTALL_PROGRAM_ENV=STRIPPROG='$(STRIP)'"` install
+mostlyclean-generic:
+
+clean-generic:
+ -test -z "$(CLEANFILES)" || rm -f $(CLEANFILES)
+
+distclean-generic:
+ -test -z "$(CONFIG_CLEAN_FILES)" || rm -f $(CONFIG_CLEAN_FILES)
+ -test . = "$(srcdir)" || test -z "$(CONFIG_CLEAN_VPATH_FILES)" || rm -f
$(CONFIG_CLEAN_VPATH_FILES)
+
+maintainer-clean-generic:
+ @echo "This command is intended for maintainers to use"
+ @echo "it deletes files that may require special tools to rebuild."
+clean: clean-recursive
+
+clean-am: clean-generic clean-local mostlyclean-am
+
+distclean: distclean-recursive
+ -rm -f Makefile
+distclean-am: clean-am distclean-generic distclean-tags
+
+dvi: dvi-recursive
+
+dvi-am:
+
+html: html-recursive
+
+html-am:
+
+info: info-recursive
+
+info-am:
+
+install-data-am: install-data-local install-htmlDATA
+
+install-dvi: install-dvi-recursive
+
+install-dvi-am:
+
+install-exec-am:
+
+install-html: install-html-recursive
+
+install-html-am:
+
+install-info: install-info-recursive
+
+install-info-am:
+
+install-man:
+
+install-pdf: install-pdf-recursive
+
+install-pdf-am:
+
+install-ps: install-ps-recursive
+
+install-ps-am:
+
+installcheck-am:
+
+maintainer-clean: maintainer-clean-recursive
+ -rm -f Makefile
+maintainer-clean-am: distclean-am maintainer-clean-generic
+
+mostlyclean: mostlyclean-recursive
+
+mostlyclean-am: mostlyclean-generic
+
+pdf: pdf-recursive
+
+pdf-am:
+
+ps: ps-recursive
+
+ps-am:
+
+uninstall-am: uninstall-htmlDATA
+
+.MAKE: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) ctags-recursive \
+ install-am install-strip tags-recursive
+
+.PHONY: $(RECURSIVE_CLEAN_TARGETS) $(RECURSIVE_TARGETS) CTAGS GTAGS \
+ all all-am check check-am clean clean-generic clean-local \
+ ctags ctags-recursive distclean distclean-generic \
+ distclean-tags distdir dvi dvi-am html html-am info info-am \
+ install install-am install-data install-data-am \
+ install-data-local install-dvi install-dvi-am install-exec \
+ install-exec-am install-html install-html-am install-htmlDATA \
+ install-info install-info-am install-man install-pdf \
+ install-pdf-am install-ps install-ps-am install-strip \
+ installcheck installcheck-am installdirs installdirs-am \
+ maintainer-clean maintainer-clean-generic mostlyclean \
+ mostlyclean-generic pdf pdf-am ps ps-am tags tags-recursive \
+ uninstall uninstall-am uninstall-htmlDATA
+
+
+#doc_DATA = autoyast.pdf
+
+components: components.ent
+ bin/components.sh noref > components.ent
+
+examples: examples.ent
+ bin/examples.sh > examples.ent
+
+html/index.html: autoyast.xml
+ XML_CATALOG_FILES=@XML_CATALOG@ \
+ time -p @XSLTPROC@ --xinclude \
+ -stringparam chunk.fast '1' \
+ --stringparam html.stylesheet $(STYLESHEET_CSS) \
+ @STYLESHEET_HTML@ autoyast.xml
+ XML_CATALOG_FILES=@XML_CATALOG@ \
+ time -p @XSLTPROC@ --xinclude \
+ -stringparam base.dir 'html/devel/' \
+ -stringparam chunk.fast '1' \
+ --stringparam html.stylesheet $(STYLESHEET_CSS) \
+ @STYLESHEET_HTML@ creating_autoyast2_modules.xml
+ cd html/devel; \
+ ln -s ../default.css ./default.css; \
+ ln -s ../images ./images
+ cd ../..
+
+html/index.html: autoyast.xml
+ XML_CATALOG_FILES=@XML_CATALOG@ \
+ @XSLTPROC@ --xinclude @STYLESHEET_HTML@ \
+ $<
+
+#autoyast.fo: autoyast.xml
+# XML_CATALOG_FILES=@XML_CATALOG@ \
+# @XSLTPROC@ @XSLTPROC_FLAGS@ --xinclude \
+# -o $@ @STYLESHEET_PDF@ $<
+
+#autoyast.fo: autoyast.xml
+# saxon -o autoyast.fo autoyast.xml @STYLESHEET_PDF@
+
+#autoyast.pdf: autoyast.fo
+# fop -q $< $@
+
+autoyast.xml: images.ent examples components
+
+html/yast2docs.css: html/index.html
+ cp @STYLESHEET_CSS@ html
+ cp -a $(ydatadir)/docbook/images html
+
+html/default.css: html/index.html webimages
+ cp web/default.css html
+
+images.ent:
+ @make -r -C images/WEB -f makefile.ent ima
+ mv ../images.ent .
+
+: images.ent chunks webimages
+
+webimages:
+ mkdir -p html/img
+ cp -a images/WEB/*png html/img
+
+.PHONY: images examples.ent components.ent
+
+images: images/EPS/* images/PNG/*
+ @if ! [ -e "img" ]; then \
+ mkdir -p img; \
+ fi
+ @if ! [ -e "img/Makefile" ]; then \
+ ln -s ../images/makefile.images img/Makefile; \
+ fi
+
+ @echo "generating PNG files for all outputs...";
+ @if [ "$(IMAGES)" = "all" ]; then \
+ rm -f img/*.{png,pdf}; \
+ fi;
+
+ @for j in `bin/findImages.sh` ; do \
+ if [ -e "images/EPS/$$j" ]; then \
+ source="images/EPS/$$j"; eps="1";\
+ elif [ -e "images/PNG/$$j" ]; then \
+ source="images/PNG/$$j"; eps="0"; \
+ fi; \
+ dest=`echo "img/$$j" | sed -e "s|_|-|g;s|.eps||g;s|.png||g;"`; \
+ if [ -e "$$source" ]; then \
+ if [ ! -f $$dest".png" ] || [ $$dest".png" -ot $$source
]; then \
+ if [ $$eps == "1" ]; then \
+ echo " converting $$source ->
$$dest'.pdf'"; \
+ bin/epstopdf12 -o=$$dest".pdf"
$$source; \
+ echo " converting $$source ->
$$dest'.png'"; \
+ convert $$source $$dest".png"; \
+ else \
+ echo " linking $$source ->
$$dest'.png'"; \
+ convert -depth 8 $$source $$dest".png";
\
+ fi; \
+ fi; \
+ fi; \
+ done
+ @make -r -C img ima
+
+install-data-local:
+ install -d -m 755 $(DESTDIR)$(htmldir)
+ cp -a $(srcdir)/html/images $(DESTDIR)$(htmldir)
+ cp -a $(srcdir)/html/img $(DESTDIR)$(htmldir)
+ cp -a $(srcdir)/html/devel $(DESTDIR)$(htmldir)
+
+clean-local:
+ rm -rf html
+
+# Tell versions [3.59,3.63) of GNU make to not export all variables.
+# Otherwise a system limit (for SysV at least) may be exceeded.
+.NOEXPORT:

Added: trunk/autoinstallation/doc/xml/NFSSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/NFSSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/NFSSection.xml (added)
+++ trunk/autoinstallation/doc/xml/NFSSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,73 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+ <section>
+ <title>
+ NFS Client and Server
+ </title>
+ <para>
+ Configuration of a system as an NFS client or an NFS server is
+ possible and can be done using the configuration system. The
+ following examples shows how both NFS client and server can be
configured.
+ </para>
+ <para>
+ Up to SLE11 and openSUSE 11.2, the following structure of NFS client
configuration
+ is used:
+ </para>
+ <example>
+ <title>
+ Network configuration: NFS client
+ </title>
+ <screen>
+
+ <xi:include href="examples/example.nfs.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+ <para>
+ From openSUSE 11.3 (SLE12 respectively) on, the structure of NFS client
configuration
+ has changed. Some global configuration options were introduced -
<emphasis>enable_nfs4</emphasis>
+ to switch NFS4 support on/off and <emphasis>idmapd_domain</emphasis> to
define domain name for
+ rpc.idmapd (this only makes sense with enabled NFS4). Attention: the
old structure is not
+ compatible with the new one and the profiles with NFS section created
on older releases will not
+ work with newer products.
+ </para>
+ <example>
+ <title>
+ Network configuration: NFS client - new style (openSUSE 11.3 and
newer)
+ </title>
+ <screen>
+
+ <xi:include href="examples/example.nfs-new.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+
+ <example>
+ <title>
+ Network configuration: NFS Server
+ </title>
+ <screen>
+
+
+ <xi:include href="examples/example.nfsserver.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+</example>
+ </section>
+

Added: trunk/autoinstallation/doc/xml/NISSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/NISSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/NISSection.xml (added)
+++ trunk/autoinstallation/doc/xml/NISSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,42 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+ <section id="Configuration.Network.NIS">
+ <title>NIS</title>
+ <para>
+ Using the <emphasis>nis</emphasis> resource, you can configure the
target machine as a <emphasis>NIS
+ client</emphasis>. The following example shows a detailed
+ configuration using multiple domains.
+ </para>
+ &example.nis;
+ </section>
+ <!--
+ <section id="Configuration.Network.NISplus">
+ <title>
+ NIS+
+ </title>
+ <para>
+ If you activate NIS+, the data of the
+ NIS+ Server will be added to <filename>/etc/hosts</filename>. Keyserv and
the NIS+ cache manager
+ will be started and the NSS and PAM configuration will be modified to use
+ NIS+ and set the Secret Key of a user.
+ </para>
+ &example.nisplus;
+ </section>
+ -->
+

Added: trunk/autoinstallation/doc/xml/NTPSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/NTPSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/NTPSection.xml (added)
+++ trunk/autoinstallation/doc/xml/NTPSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,49 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+ <section id='Configuration.Network.Ntp'>
+ <title>
+ NTP Client
+ </title>
+ <para>
+ Select whether to start the NTP daemon when booting the system. The
NTP
+ daemon resolves host names when initializing. The first
+ synchronization of the clock is performed before the NTP daemon is
+ started. To use this host for initial synchronization configure the
+ property <emphasis>initial_sync</emphasis>.
+ </para>
+ <para>
+ To run NTP daemon in
+ chroot jail, set <emphasis>start_in_chroot</emphasis>. Starting any
daemon
+ in a chroot jail is more secure and strongly recommended.
+ To adjust NTP servers, peers, local clocks, and NTP broadcasting,
+ add the appropriate entry to the control file. an example of various
+ configuration options is shown below.
+ </para>
+ <example>
+ <title>
+ Network configuration: NTP Client
+ </title>
+ <screen>
+ <xi:include href="examples/example.ntp.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+</example>
+ </section>
+

Added: trunk/autoinstallation/doc/xml/NetworkInstallation.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/NetworkInstallation.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/NetworkInstallation.xml (added)
+++ trunk/autoinstallation/doc/xml/NetworkInstallation.xml Mon Aug 8 14:12:13
2011
@@ -0,0 +1,115 @@
+<chapter id="Bootmanagement">
+ <title>Network Based Installation</title>
+ <para>
+ The installation method using AutoYaST provides a way to automatically
+ and identically install groups of systems. The first step when preparing
+ AutoYaST installations is deciding how you want the systems at your
+ site to be installed. For example, the following scenario would be ideal to
+ set up and perform automated installations:
+
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ You need to install SuSE Linux on 50 new systems.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The development department owns 30 out of the 50 new dual processor
+ and SCSI systems, and its systems must be installed as clients with
+ development software.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ The sales department owns 20 out of the 50 new, uni-processor IDE
+ based systems and its systems must be installed as clients with end user
+ software and office tools.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ Prerequisites:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>A boot server on the same Ethernet segment</para>
+ </listitem>
+ <listitem>
+ <para>An install server with the SuSE Linux OS</para>
+ </listitem>
+ <listitem>
+ <para>An AutoYaST configuration server that defines rules and
profiles.</para>
+ </listitem>
+ </itemizedlist>
+
+ <!-- FIXME: Add info about boot server and installation server -->
+
+ <section>
+ <title>Configuration Server</title>
+ <para>
+ A configuration repository holds the control files for multiple
+ machines. The control files can have any file names, which have to
+ specified at the boot time of a client. To avoid supplying the
+ profile name for every client, you can only define the directory of
+ the control files. If a directory is specified, then the client tries
+ to load a file with a name matching it's IP address in HEX
+ mode. This has the advantage that you will be dealing with
+ consistent file names rather than IPs as file names which might lead to
+ some confusion.
+ </para>
+ <para>
+ The configuration repository is the same directory you have to define
+ if you are using the configuration system for creating control files.
+ </para>
+ <section>
+ <title>&http; Repository</title>
+ <para>
+ To be able to use the &http; protocol to retrieve control file while
+ auto-installing, you need a working &http; server on the server
+ side. Install <emphasis>Apache</emphasis> or your favorite web
+ server and enable it using &yast2;. Normally the the web server root
+ directory resides in <filename>/srv/www/htdocs</filename>
+ so you need to create a subdirectory below the root directory of
+ the web server which will be your configuration repository.
+ </para>
+
+ </section>
+ <section>
+ <title>&nfs; Repository</title>
+ <para>
+ Create a directory and make it available via &nfs; to the clients by
+ exporting it. This directory may for example be in the same place
+ where you have copied the CDs. (i.e.
<filename>/usr/local/SuSE</filename>)
+ </para>
+ </section>
+ <section>
+ <title>&tftp; Repository</title>
+ <para>
+ By default the &tftp; directory is available under
+ <filename>/tftpboot</filename> which can also contain boot images
+ if you are booting over network. Do not forget to enable TFTP in
+ the Inetd configuration file
+ (<filename>/etc/inetd.conf</filename>). <emphasis>Inetd</emphasis>
configuration can be
+ done using &yast2;.
+ </para>
+ </section>
+ </section>
+
+</chapter>
+
+
+
+
+
+
+
+
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast2.xml" "book" "chapter")
+ End:
+ -->

Added: trunk/autoinstallation/doc/xml/NetworkSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/NetworkSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/NetworkSection.xml (added)
+++ trunk/autoinstallation/doc/xml/NetworkSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,111 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+ <section id="CreateProfile.Network">
+ <title>
+ Network configuration
+ </title>
+
+ <section id="Configuration.Network.Devices">
+ <title>
+ Network devices, DNS and Routing.
+ </title>
+ <para>
+ Network configuration is used to connect a single &company-suse; Linux
+ workstation to an Ethernet-based LAN or to configure dial-up
+ connection. More complex configuration (multiple network cards,
+ routing, etc.) is also provided. With this module it's possible to
+ configure and setup Ethernet Controllers and Token-Ring Controllers.
+ </para>
+ <para>
+ In the networking section, when this option is set to true (default is
false, this option is available since openSUSE 11.2 but not SLES11):
+ <screen>
+ &lt;keep_install_network
config:type=&quot;boolean&quot;&gt;true&lt;/keep_install_network&gt;
+ </screen>
+ YaST will keep network settings created during installation (via Linuxrc)
+ and/or merge it with network settings from the AutoYaST profile (if these
are defined).
+ AutoYaST settings have higher priority than already present configuration
files.
+ YaST will write ifcfg-* files from profile without removing old ones.
+ If there is none (or empty) dns and routing section, YaST will keep
already present values. Otherwise settings from the profile will be applied.
+ </para>
+ <para>
+ To configure network settings and activate networking automatically,
+ one global resource is used to store the whole network configuration.
+ </para>
+
+ &example.network;
+ </section>
+
+ <section id="Configuration.Network.Proxy">
+ <title>
+ Proxy
+ </title>
+ <para>
+ Configure your Internet proxy (caching) settings using this
+ resource.
+ </para>
+ <para>
+ <emphasis>HTTP proxy</emphasis> is the name of the proxy server for
your access to the world wide web (WWW).
+ <emphasis>FTP proxy</emphasis> is the name of the proxy server for your
access to the file transfer services (FTP).
+ <emphasis>No proxy</emphasis> domains is a list of domains for
+ which the requests should be done directly without caching.
+ </para>
+ <para>
+ If you are using a proxy server with authorization, fill in Proxy user
name and Proxy password.
+ </para>
+ <example>
+ <title>
+ Netwrok configuration: Proxy
+ </title>
+ <screen>
+ <xi:include href="examples/example.proxy.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+
+
+ </section>
+ <section id="Configuration.Network.Inetd">
+ <title>(X)Inetd </title>
+
+ <para>
+ The profile has elements to specify which superserver should be
+ used (netd_service), whether it should be enabled (netd_status) and
+ how the services should be configured (netd_conf).
+ </para>
+ <para>
+ A service description element has conceptually two parts: key and
+ non-key. When writing the configuration, services are matched using
+ the key fields and to the matching service, non-key fields are
+ applied. If no service matches, it is created. If more services
+ match, a warning is reported. The key fields are script, service,
+ protocol and server.
+ </para>
+ <para>
+ Service and protocol are matched literally. script is the base name
+ of the config file: usually a file in<filename>
/etc/xinetd.d</filename>, for example "echo-udp",
+ or "inetd.conf". For compatibility with 8.2, server is matched more
+ loosely: if it is <filename>/usr/sbin/tcpd</filename>, the real server
name is taken from
+ server_args. After that, the basename of the first
+ whitespace-sparated word is taken and these values are compared.
+ </para>
+ &example.inetd;
+
+ </section>
+ </section>
+

Added: trunk/autoinstallation/doc/xml/PartitioningSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/PartitioningSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/PartitioningSection.xml (added)
+++ trunk/autoinstallation/doc/xml/PartitioningSection.xml Mon Aug 8 14:12:13
2011
@@ -0,0 +1,1006 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+ <section id="CreateProfile.Partitioning">
+ <title>
+ Partitioning
+ </title>
+
+ <section>
+ <title>drive configuration</title>
+ <warning>
+ <title>
+ EVMS support dropped in openSUSE 11.1 and SLES11
+ </title>
+ <para>
+since openSUSE 11.1 and SLES11 there is no longer support for EVMS in the
installation system. That means all support for EVMS in AutoYaST was dropped
too. Alll EVMS documentation on this page is on valid for SLES10 (all service
packs) and openSUSE versions prior openSUSE 11.1
+ </para>
+ </warning>
+ <para>
+ The following elements must be between the &lt;partitioning
config:type="list"&gt;&lt;drive&gt; ... &lt;/drive&gt;&lt;/partitioning&gt;
tags in the &lt;profile&gt; section.
+ </para>
+ <table frame='top'>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>device</entry>
+ <entry>the device you want to configure in this section. Since
SUSE Linux 10.1 and SLES10, you can use persistent device names via id, like
<emphasis>/dev/disk/by-id/ata-WDC_WD3200AAKS-75L9A0_WD-WMAV27368122</emphasis>.
With SLES10 SP1 and SUSE Linux 10.2, <emphasis>by-path</emphasis> is possible
too like <emphasis>/dev/disk/by-path/pci-0001:00:03.0-scsi-0:0:0:0</emphasis>.
+
<para><screen>&lt;device&gt;/dev/hda&lt;/device&gt;</screen></para>
+ </entry>
+ <entry>optional. If left out, autoyast tries to guess the
device. A RAID must always have "/dev/md" as device</entry>
+ </row>
+ <row>
+ <entry>initialize</entry>
+ <entry>if set to true, the partition table gets wiped out
before autoyast starts the partition calculation
+<para><screen>&lt;initialize
config:type="boolean"&gt;true&lt;/initialize&gt;</screen></para>
+</entry>
+ <entry>optional. The default is false.</entry>
+ </row>
+ <row>
+ <entry>is_lvm_vg</entry>
+ <entry>This tells autoyast that this device is not a physical
device but a LVM volume group (see LVM configuration below)
+<para><screen>&lt;is_lvm_vg
config:type="boolean"&gt;true&lt;/is_lvm_vg&gt;</screen></para>
+</entry>
+ <entry>DEPRECATED since SLES10SP1 and SL10.2 - use
<emphasis>type</emphasis> instead. Must be true if this device is a LVM volume
group. The default is false.</entry>
+ </row>
+ <row>
+ <entry>is_evms_vg</entry>
+ <entry>this tells autoyast that this device is not a physical
device but an EVMS volume group (see EVMS configuration below)
+<para><screen>&lt;is_evms_vg
config:type="boolean"&gt;true&lt;/is_evms_vg&gt;</screen></para>
+</entry>
+ <entry>DEPRECATED since SLES10SP1 and SL10.2 - use
<emphasis>type</emphasis> instead. Must be true if this device is an EVMS
volume group. The default is false.</entry>
+ </row>
+ <row>
+ <entry>partitions</entry>
+ <entry>this is a list of &lt;partition&gt; entries (see table
below)
+<para><screen>&lt;partitions
config:type="list"&gt;&lt;partition&gt;...&lt;/partition&gt;...&lt;/partitions&gt;</screen></para>
+</entry>
+ <entry>optional. If no partition is specified, autoyast will
create it's own idea of a nice partitioning (see Automated Partitioning
below).</entry>
+ </row>
+ <row>
+ <entry>pesize</entry>
+ <entry>this value makes only sense with LVM/EVMS.
+<para><screen>&lt;pesize&gt;8M&lt;/pesize&gt;</screen></para>
+</entry>
+ <entry>optional. Default is 4M for EVMS/LVM volume
groups.</entry>
+ </row>
+ <row>
+ <entry>use</entry>
+ <entry>this parameter tells autoyast which strategy it shall
use to partition the harddisc.
+<para>You can choose between:</para>
+<itemizedlist>
+<listitem>
+<para>all (uses the whole device while calculating the new partitioning)</para>
+</listitem>
+<listitem>
+<para>linux (only existing linux partitions are used)</para>
+</listitem>
+<listitem>
+<para>free (only unused space on the device gets used. No other partitions
gets touched)</para>
+</listitem>
+<listitem>
+<para>1,2,3 (a list of comma seperated numbers that indicates the partition
numbers to use)</para>
+</listitem>
+</itemizedlist>
+</entry>
+ <entry>this parameter should be provided</entry>
+ </row>
+ <row>
+ <entry>type</entry>
+ <entry>this value describes the type of the
<emphasis>drive</emphasis> and is a replacement for
+<emphasis>is_lvm_vg</emphasis> and <emphasis>is_evms_vg</emphasis> used in
SLES10 and SL10.1
+<para>You can choose between:</para>
+<itemizedlist>
+<listitem>
+<para>CT_DISK for physical harddisks (default)</para>
+</listitem>
+<listitem>
+<para>CT_LVM for LVM volume groups</para>
+</listitem>
+<listitem>
+<para>CT_EVMS for EVMS volume groups</para>
+</listitem>
+</itemizedlist>
+
+<para><screen>&lt;type
config:type="symbol"&gt;CT_LVM&lt;/type&gt;</screen></para>
+</entry>
+ <entry>optional. Default is CT_DISK for a normal physical
harddisk.</entry>
+ </row>
+ <row>
+ <entry>disklabel</entry>
+ <entry>this value describes the type of the partition table
+<para>You can choose between:</para>
+<itemizedlist>
+<listitem>
+<para>msdos</para>
+</listitem>
+<listitem>
+<para>gpt</para>
+</listitem>
+</itemizedlist>
+
+<para><screen>&lt;disklabel&gt;gpt&lt;/disklabel&gt;</screen></para>
+</entry>
+ <entry>optional and available since openSUSE 12.1 and SLES11
SP2. Default is to let yast decide what makes sense (msdos in most
cases)</entry>
+ </row>
+ <row>
+ <entry>keep_unknown_lv</entry>
+ <entry>This value only makes sense for type=CT_LVM drives. If
you are reusing a LVG and you set this to true, all existing LVs in that VG
won't be touched unless they are specified in the &lt;partitioning&gt; section.
So you can keep existing LVs without need to specify them.
+<para><screen>&lt;keep_unknown_lv
config:type="boolean"&gt;false&lt;/keep_unknown_lv&gt;</screen></para>
+</entry>
+ <entry>optional and available since openSUSE 12.1 and SLES11
SP2. The default is false</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+ <section>
+ <title>partition configuration</title>
+ <para>
+ The following elements must be between the &lt;partitions
config:type="list"&gt;&lt;partition&gt; ...
&lt;/partition&gt;&lt;/partitions&gt; tags in the &lt;drive&gt; section.
+ </para>
+ <table frame='top'>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>create</entry>
+ <entry>
+ <para>
+ the "create" tells autoyast if this partition must be
created or if it's already existing
+ </para>
+ <para><screen>&lt;create
config:type="boolean"&gt;false&lt;/create&gt;</screen></para>
+ </entry>
+ <entry>if set to false, there must be some information for
autoyast which partition this is (like with partition_nr)</entry>
+ </row>
+ <row>
+ <entry>mount</entry>
+ <entry>
+ <para>
+ the mountpoint of this partition.
+ </para>
+ <para><screen>&lt;mount&gt;/&lt;/mount&gt;</screen></para>
+ <para><screen>&lt;mount&gt;swap&lt;/mount&gt;</screen></para>
+ </entry>
+ <entry>you should have at least a root partition (/) and a
swap partition</entry>
+ </row>
+ <row>
+ <entry>fstopt</entry>
+ <entry>
+ <para>
+ mount options for this partition
+ </para>
+
<para><screen>&lt;fstopt&gt;ro,noatime,user,data=ordered,acl,user_xattr&lt;/fstopt&gt;</screen></para>
+ </entry>
+ <entry>see "man mount" for the mountoptions you can use</entry>
+ </row>
+ <row>
+ <entry>label</entry>
+ <entry>
+ <para>
+ the label the partition has (useful for the "mountby"
parameter - see below).
+ </para>
+
<para><screen>&lt;label&gt;mydata&lt;/label&gt;</screen></para>
+ </entry>
+ <entry>see "man e2label" for example.</entry>
+ </row>
+ <row>
+ <entry>uuid</entry>
+ <entry>
+ <para>
+ the uuid the partition has (only useful for the "mountby"
parameter - see below).
+ </para>
+
<para><screen>&lt;uuid&gt;1b4e28ba-2fa1-11d2-883f-b9a761bde3fb&lt;/uuid&gt;</screen></para>
+ </entry>
+ <entry>see "man uuidgen"</entry>
+ </row>
+ <row>
+ <entry>size</entry>
+ <entry>
+ <para>
+ the size for the partition like 4G, 4500M, ... The /boot
partition and the swap partition can have "auto" as
+ size too, to let autoyast calculate a reasonable size for
them. On partition can have the value "max" to fillup
+ all available space.
+ </para>
+ <para>
+ with SUSE Linux 10.2 and SLES10 SP1, you can specify the
the size in percentage. So 10% will use 10% of the size
+ of the harddisk/VG. You can mix auto,max,sizes and
percentage like you want.
+ </para>
+ <para><screen>&lt;size&gt;10G&lt;/size&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>format</entry>
+ <entry>
+ <para>
+ shall autoyast format the partition?
+ </para>
+ <para><screen>&lt;format
config:type="boolean"&gt;false&lt;/format&gt;</screen></para>
+ </entry>
+ <entry>if "create" is true, then it's very likely that this is
true too</entry>
+ </row>
+ <row>
+ <entry>filesystem</entry>
+ <entry>
+ <para>
+ what filesystem is used on this partition?
+<itemizedlist>
+<listitem>
+<para>reiser (the default)</para>
+</listitem>
+<listitem>
+<para>ext2</para>
+</listitem>
+<listitem>
+<para>ext3</para>
+</listitem>
+<listitem>
+<para>xfs</para>
+</listitem>
+<listitem>
+<para>jfs</para>
+</listitem>
+<listitem>
+<para>swap</para>
+</listitem>
+</itemizedlist>
+ </para>
+ <para><screen>&lt;filesystem
config:type="symbol"&gt;reiser&lt;/filesystem&gt;</screen></para>
+ </entry>
+ <entry>optional. The default is reiser</entry>
+ </row>
+ <row>
+ <entry>partition_nr</entry>
+ <entry>
+ <para>
+ the partition_nr this partition has/will have. If you have
set create=false or if you use LVM, then you can tell
+ autoyast which partition you mean by the partition_nr. You
can force autoyast to create only
+ primary partitions by configuring only partition numbers
below 5.
+ </para>
+ <para><screen>&lt;partition_nr
config:type="integer"&gt;2&lt;/partition_nr&gt;</screen></para>
+ </entry>
+ <entry>in most cases nr. 1-4 are primary partitions and 5-...
are logical partitions</entry>
+ </row>
+ <row>
+ <entry>partition_id</entry>
+ <entry>
+ <para>
+ the partition_id configures the id of the partition.
If you want something else than 131
+ for linux partition or 130 for swap, you must
configure that with partition_id.
+ </para>
+ <para><screen>&lt;partition_id
config:type="integer"&gt;131&lt;/partition_id&gt;</screen></para>
+ </entry>
+ <entry>the default is 131 for linux partition. 130 for swap is
set by autoyast itself too.</entry>
+ </row>
+ <row>
+ <entry>filesystem_id</entry>
+ <entry>
+ <para>
+ look at partition_id above. For historical reasons
they represent the same.
+ </para>
+ <para><screen>&lt;filesystem_id
config:type="integer"&gt;131&lt;/filesystem_id&gt;</screen></para>
+ </entry>
+ <entry>since 10.1 and SLES10 it's recommended to use
partition_id instead.</entry>
+ </row>
+ <row>
+ <entry>mountby</entry>
+ <entry>
+ <para>
+ instead of a partition number, you can tell autoyast to
mount a partition by label, uuid, path or id which are the udev path and udev
id (see /dev/disk/...)
+ </para>
+ <para><screen>&lt;mountby
config:type="symbol"&gt;label&lt;/mountby&gt;</screen></para>
+ </entry>
+ <entry>see "label" and "uuid" documentation above</entry>
+ </row>
+ <row>
+ <entry>lv_name</entry>
+ <entry>
+ <para>
+ if this partition is in a logical volume in a volume group
(LVM or EVMS)
+ (see is_lvm_vg/is_evms_vg parameter in drive
configuration) you
+ must specifiy the logical volume name here.
+ </para>
+
<para><screen>&lt;lv_name&gt;opt_lv&lt;/lv_name&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>stripes</entry>
+ <entry>
+ <para>
+ It's an integer that tells AutoYaST to do LVM striping.
You can configure across how man devices you want to stripe
+ </para>
+ <para><screen>&lt;stripes
config:type="integer"&gt;2&lt;/stripes&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>stripesize</entry>
+ <entry>
+ <para>
+ It's an integer that tells AutoYaST the size of each block
in kb
+ </para>
+ <para><screen>&lt;stripesize
config:type="integer"&gt;4&lt;/stripesize&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>lvm_group</entry>
+ <entry>
+ <para>
+ if this is a physical partition that is used by (part of)
a volume group (LVM),
+ you have to specify the name of the volume
+ group here.
+ </para>
+
<para><screen>&lt;lvm_group&gt;system&lt;/lvm_group&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>evms_group</entry>
+ <entry>
+ <para>
+ if this physical partition is used by a volume group
(EVMS), you have to specify the name of the volume
+ group here.
+ </para>
+
<para><screen>&lt;evms_group&gt;system&lt;/evms_group&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>raid_name</entry>
+ <entry>
+ <para>
+ this physical volume is part of a RAID and the name of the
raid is specified here.
+ </para>
+
<para><screen>&lt;raid_name&gt;/dev/md0&lt;/raid_name&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>raid_type</entry>
+ <entry>
+ <para>
+ this physical volume is part of a RAID and the type of the
raid is specified here..
+ </para>
+
<para><screen>&lt;raid_type&gt;raid1&lt;/raid_type&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>raid_options</entry>
+ <entry>
+ <para>
+ special options for the raid are specified here. See below.
+ </para>
+
<para><screen>&lt;raid_options&gt;...&lt;/raid_options&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>resize</entry>
+ <entry>
+ <para>
+ This parameter is available since SLES10 SP1 and OpenSUSE
10.2.
+ This boolean must be true if an existing partition should
be resized. In this case,
+ you want to set <emphasis>create</emphasis> to
<emphasis>false</emphasis> too and in
+ most cases you don't want to <emphasis>format</emphasis>
the partition. You need to
+ tell autoyast the <emphasis>partition_nr</emphasis> and
the <emphasis>size</emphasis>.
+ The size can be in percentage of the original size or as a
number of the new size, like
+ <emphasis>800M</emphasis>. <emphasis>max</emphasis> and
<emphasis>auto</emphasis> don't
+ work as size here.
+ </para>
+ <para><screen>&lt;resize
config:type="boolean"&gt;false&lt;/resize&gt;</screen></para>
+ </entry>
+ <entry>The resize only works with physical disks. Not with
LVM/EVMS volumes.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section>
+ <title>raid options</title>
+ <para>
+ The following elements must be between the
&lt;partition&gt;&lt;raid_options&gt; ...
&lt;/raid_options&gt;&lt;/partition&gt; tags.
+ </para>
+ <table frame='top'>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>chunk_size</entry>
+ <entry>
+ <para>
+ </para>
+
<para><screen>&lt;chunk_size&gt;4&lt;/chunk_size&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>parity_algorithm</entry>
+ <entry>
+ <para>
+ possible values are: left_asymmetric, left_symmetric,
right_asymmetric, right_symmetric and since SLES11 SP2 and openSUSE 12.1 you
can use parity_first, parity_last, left_asymmetric_6, left_symmetric_6,
right_asymmetric_6, right_symmetric_6, parity_first_6, n2, o2, f2, n3, o3, f3
for RAID6 and RAID10
+ </para>
+
<para><screen>&lt;parity_algorithm&gt;left_asymmetric&lt;/parity_algorithm&gt;</screen></para>
+ </entry>
+ <entry></entry>
+ </row>
+ <row>
+ <entry>raid_type</entry>
+ <entry>
+ <para>
+ possible values are raid0,raid1 and raid5
+ </para>
+
<para><screen>&lt;raid_type&gt;raid1&lt;/raid_type&gt;</screen></para>
+ </entry>
+ <entry>the default is raid1</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section>
+ <title>
+ Automated Partitioning
+ </title>
+
+ <para>
+ For the automated partitioning to be completed, only the sizes and
mount points of
+ partitions can be provided. All other data needed for successful
partitioning
+ can be calculated during installation if they were not provided in the
control file.
+ </para>
+ <para>
+ If no partitions are defined and the specified drive is also the drive
where
+ the root partition should be created, the following partitions are
created
+ automatically:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>/boot</emphasis>
+ </para>
+ <para>
+ Size of the <emphasis>/boot</emphasis> is determined by the
+ architecture of the target system.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>swap</emphasis>
+ </para>
+ <para>
+ Size of the <emphasis>swap</emphasis> partitions is determined by
the
+ amount of memory available in the system.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>/</emphasis> (root partition)
+ </para>
+ <para>
+ Size of the <emphasis>/</emphasis> (root partition) is the space
left
+ after creating <emphasis>swap</emphasis> and
<emphasis>/boot</emphasis>.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ Depending on the initial status of the drive and how it was
+ previously partitioned, it is possible to create the
<emphasis>default</emphasis>
+ partitioning in the following ways:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>Use free space</emphasis>
+ </para>
+ <para>
+ If the drive is already partitioned, it is possible to create the
+ new partitions using the available space on the hard drive. This
+ requires the availability of enough space for all selected
+ packages in addition to swap.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Reuse all available space</emphasis>
+ </para>
+ <para>
+ This option will lead to the deletion of all existing
+ partitions (Linux and non-Linux partitions).
+
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Reuse all available Linux partitions</emphasis>
+ </para>
+ <para>
+ This option will lead to the deletion of existing Linux
+ partitions. All other partitions (i.e. Windows) will be
+ kept. Note that this works only if the Linux partitions are at the
end of the device.
+
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>Reuse only specified partitions</emphasis>
+ </para>
+ <para>
+ This option will lead to the deletion of the specified partitions.
+ The selection of the partitions scheduled for deletion should be
+ started from the last available partition.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ Repartitioning using only some of the existing partitions can be
+ accomplished only if the region selected to be partitioned exists at
+ the end of the device and only with neighboring partitions. This
+ means that you cannot repartition a region which contains a partition
that
+ should not be touched in the middle.
+ </para>
+
+ <caution>
+ <title>Important Notice</title>
+ <para>
+ The value provided in the <emphasis>use</emphasis> property
determines how existing data and
+ partitions are treated. The value <emphasis>all</emphasis> means that
+ <emphasis>ALL</emphasis> data on the disk will
+ be erased. Make backups and use the <emphasis>confirm</emphasis>
+ property if you are going to
+ keep some partitions with important data. This is automated
+ installation and no pop-ups will notify you about partitions being
deleted.
+ </para>
+ </caution>
+ <para>
+ In case of the presence of multiple drives in the target system, all
+ drives must be identified with their device names and how the
partitioning should be performed.
+ </para>
+
+ <para>
+ Partition sizes can be given in Gigabytes, Megabytes or can be set to
+ a flexible value using the keywords <emphasis>auto</emphasis> and
+ <emphasis>max</emphasis>. <emphasis>max</emphasis> is used to fill a
+ partition to the maximal available space on a
+ drive (Which mean that the partition should be the last one on the
drive).
+ <emphasis>auto</emphasis> can be used to determine the size of
+ a <emphasis>swap</emphasis> or <emphasis>boot</emphasis> partitions
+ depending on the memory available and the type of the system.
+ </para>
+ <para>A fixed size can be given as shown below:</para>
+ <para>
+ <emphasis>1GB</emphasis> will create a partition with 1 GB size.
+ <emphasis>1500MB</emphasis> will create a partition which is 1.5 GB big.
+ </para>
+ <example>
+ <title>Automated partitioning</title>
+ <para>
+ The following is an example of a single drive system, which is not
+ pre-partitioned and should be automatically partitioned according to
+ the described pre-defined partition plan. If you leave the device out,
+ an autodetection of the device will happen. So you don't have to do
+ different profiles for /dev/sda or /dev/hda systems.
+ </para>
+ <screen>
+ <xi:include href="examples/example.partitioning.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ </screen>
+ </example>
+ <para>
+ A more detailed example shows how existing partitions and
+ multiple drives are handled.
+ </para>
+ <example>
+ <title>Detailed automated partitioning</title>
+ <screen>
+ <xi:include href="examples/example.partitioning2.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+ </section>
+
+ <section>
+ <title>Advanced Partitioning features</title>
+ <section>
+ <title>Wipe out partition table</title>
+ <para>
+ In the most cases this is not needed because autoyast can delete
partitions
+ one by one automatically but you have the option to let autoyast clear
the partition table
+ instead of deleting the partitions individually.
+ </para>
+ <para>
+ if you go into the "drive" section, you can add
+ <screen>
+<![CDATA[
+<initialize config:type="boolean">true</initialize>
+]]>
+</screen>
+ which tells Autoyast to delete the partition table before it starts to
analyse the
+ actual partitioning and calculates it's partition plan. Of course this
means, that you
+ can't keep any of your existing partitions.
+ </para>
+ </section>
+ <section>
+ <title>Mount Options</title>
+ <para>
+ By default a file system which is to be mounted is
+ identified in <filename>/etc/fstab</filename> by the device name. This
identification
+ can be changed so the file system is found by searching
+ for a <acronym>UUID</acronym> or a volume label. Note that not all file
systems can be mounted
+ by <acronym>UUID</acronym> or a volume label. To specify how a
+ partition is to be mounted, use the <emphasis>mountby</emphasis>
+ property which has the <emphasis>symbol</emphasis> type. Possible
+ options are:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>device (default)</para>
+ </listitem>
+ <listitem>
+ <para>label</para>
+ </listitem>
+ <listitem>
+ <para>UUID</para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ If you choose to mount the partition using a label, the name
+ entered in the <emphasis>label</emphasis> property is used as the
+ volume label.
+ </para>
+ <para>
+ Add any legal mount option allowed in the fourth field of
+ <filename>/etc/fstab</filename>. Multiple options are separated by
commas. Possible fstab options:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>Mount Read-Only (ro):</emphasis> No writable
+ access to the file system is possible. Default is false.</para>
+
+ </listitem>
+ <listitem>
+ <para><emphasis>No access time (noatime):</emphasis> Access times
+ are not updated when a file is read. Default is false.</para>
+
+ </listitem>
+ <listitem>
+ <para><emphasis>Mountable by User (user):</emphasis> The file
+ system may be mounted by an ordinary user. Default is
+ false.</para>
+
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Data Journaling Mode (ordered | journal |
+ writeback) :</emphasis> Specifies the journaling mode for
+ file data. journal -- All data is committed into the journal
+ prior to being written into the main file system. ordered --
+ All data is forced directly out to the main file system prior
+ to its meta data being committed to the journal. writeback --
+ Data ordering is not preserved.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Access Control List (acl):</emphasis> Enable access
+ control lists on the file system.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Extended User Attributes (user_xattr):</emphasis> Allow
+ extended user attributes on the file system.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+ <example>
+ <title>Mount Options</title>
+
+ <screen>
+ <xi:include href="examples/example.mountoptions.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ </screen>
+ </example>
+ </section>
+
+ <section>
+ <title>Keeping Specific Partitions</title>
+ <para>
+ In some cases you might choose to keep some partitions untouched
+ and only format specific target partitions, rather than creating them
from
+ scratch. This might be the case of Linux installations have to
+ co-exist with another operating system or if certain partitions
+ contain data that you wish to keep untouched.
+ </para>
+ <para>
+ Such scenarios require certain knowledge about the target systems
+ and hard drives. Depending on the scenario, you might need to know
+ the exact partition table of the target hard drive with partition
+ id's, sizes and numbers. With such data you can tell &autoyast; to
+ keep certain partitions, format others and create new partitions if
+ needed.
+ </para>
+
+ <para>
+ The following example will keep partitions 1, 2 and 5 and delete
+ partition 6 to create two new partitions. All kept partitions will
+ be only formatted.
+ </para>
+ <example>
+ <title>
+ Keeping partitions
+ </title>
+ <screen>
+ <xi:include href="examples/example.keepingpart.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+ <para>
+ The last example requires exact knowledge about the existing partition
+ table and about the partition numbers of those partitions that
+ should be kept. In some cases however, such data might be not
+ available, especially in a mixed hardware environment with
+ different hard drive types and configurations. The following
+ scenario is for a system with a non-Linux OS with a designated
+ area for a Linux installation.
+ </para>
+ <figure id="partitioning-keep1">
+ <title id="partitioning-keep1.title" >Keeping partitions</title>
+ <mediaobject>&partitioning-keep1;</mediaobject>
+ </figure>
+
+ <para>
+ In this scenario and as shown in figure <quote><link
+ linkend='partitioning-keep1'
+ endterm="partitioning-keep1.title"/></quote> , &autoyast2;
+ should not in any case create any new
+ partitions, instead it should search for certain partition types on
the system and use
+ them according to the partitioning plan in the control file. No
+ partition numbers are given in this case, only the mount points and
+ the partition types (Additional configuration data can be provided,
+ for example file system options, encryption and filesystem type)
+ </para>
+ <example>
+ <title> Auto-detection of partitions to be kept.</title>
+ <screen> <xi:include href="examples/example.autodetectpart.xml"
parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/></screen>
+ </example>
+ </section>
+ </section>
+
+ <section>
+ <title>Using existing mount table (fstab)</title>
+ <note>
+ <title>New Feature</title>
+ </note>
+ <para>
+ This option will allow the AutoYaST to use an existing
+ <filename>/etc/fstab</filename> and use the partition data from
+ from a previous installation. All partitions are kept and no new
+ partitions are created. The found partitions will be formatted and
+ mounted as specified in <filename>/etc/fstab</filename> found on a
+ Linux root partition.
+ </para>
+ <para>
+ Although the default behaviour is to format all partitions, it is
+ also possible to leave some partitions untouched and only mount them,
+ for example data partitions. If multiple installations are found on
+ the system (multiple root partitions with different
+ <emphasis>fstab</emphasis> files, the installation will abort, unless
+ the desired root partition is configured in the control file. The
+ following example illustrates how this option can be used:
+ </para>
+ <example>
+ <title>
+ Reading existing <filename>/etc/fstab</filename>
+ </title>
+ <screen>
+ <xi:include href="examples/example.fstab.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+ </section>
+
+ <section>
+ <title>
+ Logical Volume Manager (LVM)
+ </title>
+ <para>
+ To configure LVM, first you need to create a <emphasis>physical
volume</emphasis> using the
+ normal partitioning method described above.
+ </para>
+ <example>
+ <title>
+ Create LVM Physical Volume
+ </title>
+ <para>
+ The following example shows how to prepare for LVM in the
+ <emphasis>partitioning</emphasis> resource:
+ </para>
+ <screen>
+ <xi:include href="examples/example.lvmvolume.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+
+ </example>
+ <para>
+ The last example will create a non-formatted partition on device
+ <filename>/dev/sda1</filename> of the type <emphasis>LVM</emphasis> and
+ with the volume group <emphasis>system</emphasis>. The partition
+ created will use all available space on this drive.
+ </para>
+
+ <example>
+ <title>
+ LVM Logical Volumes (New syntax)
+ </title>
+ <screen>
+<xi:include href="examples/example.lvmnew.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+ <para>
+ With SUSE Linux 10.1 and all following versions, it's possible to set
the <emphasis>size</emphasis>
+ to <emphasis>max</emphasis> for the logical volumes. Of course, you can
only use <emphasis>max</emphasis>
+ only for one(!) logical volumes. You can't have two logical volumes in
one volume group with the
+ <emphasis>size</emphasis> set to <emphasis>max</emphasis>
+ </para>
+ </section>
+
+ <section>
+ <title>
+ Enterprise Volume Management System (EVMS) - SLES10 only!
+ </title>
+ <para>
+ SLES10 autoyast has EVMS support. SLES11 has not!
+ </para>
+ <para>
+ Using EVMS is quite similar to using LVM (see above). So switching from
LVM to EVMS
+ is just a small change in the autoyast profile. All you have to do is to
change the
+ "is_lvm_vg" element into "is_evms_vg" and the "lvm_group" element into
"evms_group".
+ </para>
+ <para>
+ With autoyast it's not possible to mix LVM and EVMS.
+ </para>
+ <para>
+ Using the LVM example from above for EVMS now looks like this:
+ </para>
+ <example>
+ <title>
+ EVMS Logical Volumes
+ </title>
+ <screen>
+<xi:include href="examples/example.evms.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+ </section>
+ <section>
+ <title>Software RAID</title>
+ <para>
+ Using &autoyast;, you can create and assemble software RAID devices. The
+ supported RAID levels are the following:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>RAID 0:</emphasis> This level increases your disk
performance.
+ There is <emphasis>NO</emphasis> redundancy in this mode. If one
+ of the drives crashes, data recovery will not be possible.
+
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>RAID 1:</emphasis>This mode has the best redundancy. It can
be
+ used with two or more disks. This mode maintains an exact copy of all
data on all
+ disks. As long as at least one disk is still working, no data is
lost. The partitions
+ used for this type of RAID should have approximately the same size.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <emphasis>RAID 5:</emphasis> This mode combines management of a
larger number
+ of disks and still maintains some redundancy. This mode can be used
on three disks or more.
+ If one disk fails, all data is still intact. If two disks fail
simultaneously,
+ all data is lost.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Multipath:</emphasis>This mode allow access to the same
physical device
+ over multiple controller for redundancy against a fault in a
controller
+ card. This mode can be used with at least two devices.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ As with LVM, you need to create all
<emphasis><acronym>RAID</acronym></emphasis> partitions first and assign
+ the partitions to the <acronym>RAID</acronym> device you want to
+ create and additionally you need to specify whether a partition or a
device should be configured in the
+ <acronym>RAID</acronym> or if it should configured as a
<emphasis>Spare</emphasis> device.
+ </para>
+ <para>
+ The following example shows a simple RAID1 configuration:
+ </para>
+
+
+ <example>
+ <title>RAID1 configuration</title>
+ <screen>
+<xi:include href="examples/example.raidnew.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+
+
+ <para>
+ The following has to be taken into consideration when configuring
+ raid:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>The device for raid is always <emphasis>/dev/md</emphasis></para>
+ </listitem>
+ <listitem>
+ <para>The property <emphasis>partition_nr</emphasis> is used to
+ determine the MD device number. if
+ <emphasis>partition_nr</emphasis> is equal to 0, then
+ <emphasis>/dev/md0</emphasis> is configured.</para>
+ </listitem>
+ <listitem>
+ <para>All RAID specific options are contained in the
+ <emphasis>raid_options</emphasis> resource.</para>
+ </listitem>
+ </itemizedlist>
+
+
+
+ </section>
+ </section>
+

Added: trunk/autoinstallation/doc/xml/PrinterSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/PrinterSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/PrinterSection.xml (added)
+++ trunk/autoinstallation/doc/xml/PrinterSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,64 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+ <section id="CreateProfile.Hardware.Printer">
+ <title>
+ Printer
+ </title>
+<para>
+The YaST printer module was made anew from scratch for openSUSE 11.1 and SUSE
Linux Enterprise Server/Desktop 11. Currently the AutoYaST support for printing
is limited to basic settings how the CUPS printing system is used on a client
workstation to print via network.
+</para>
+<para>
+Currently there is no AutoYaST support to set up local print queues. In
particular when a USB printer is connected to a client workstation it is no
longer possible to have a predefined configuration because USB printers are no
longer accessed via a generic USB device node like "/dev/usb/lp0" but via a
model specific device URI like "usb://ACME/FunPrinter?serial=1a2b3c". There is
a serial number included so that a USB printer device URI works only for one
particular device. Usually it is not possible to know the correct USB device
URI in advance because it is determined by the CUPS backend "usb" during
runtime when the particular device is connected depending on the actual values
which the printer reports via the USB.
+</para>
+<para>
+Intrinsic design of CUPS for printing in the network:
+</para>
+<para>
+The CUPS daemon process (cupsd) of a CUPS network print server sends
information about its print queues to a list of IP addresses (host addresses
and/or broadcast addresses).
+</para>
+<para>
+On client workstations (hosts that only send print jobs to servers) also a
cupsd runs which listens to information from servers. There is a list of
servers from which information is accepted. By default, information is accepted
from all servers.
+</para>
+<para>
+In this way, the queues of the server are available on the clients. Users on
the clients can browse the queues on various servers. Therefore it is called
"Browsing" and all what is to do on a client workstation to use CUPS in its
default Browsing mode is to run the cupsd. The matching settings in the cupsd
configuration file (/etc/cups/cupsd.conf) are "Browsing On" and "BrowseAllow
all".
+</para>
+<para>
+To limit from which CUPS servers browsing information is accepted, a setting
like "BrowseAllow @LOCAL" accepts browsing information only from CUPS servers
in the local network.
+</para>
+<para>
+Multiple "BrowseAllow" entries like "BrowseAllow 192.168.100.1" and
"BrowseAllow 192.168.200.0/255.255.255.0" can be used to accept browsing
information only from particular hosts and/or networks.
+</para>
+<para>
+CUPS Browsing information is recieved via UDP port 631. You may have to check
firewall settings accordingly.
+</para>
+<para>
+Alternatively if there is only one single CUPS server in the network, there is
no need to use CUPS Browsing and have a CUPS daemon running on each client
workstation.
+</para>
+<para>
+Instead it is simpler to specify the CUPS server and access it directly by an
entry like "ServerName 192.168.100.99" in /etc/cups/client.conf (only one such
entry can be set). In this case the specified server is directly accessed so
that a local running cupsd on a client workstation is no longer used so that it
does no longer make sense to have it running.
+</para>
+<para>
+The following is an example of a configuration section. The
&lt;cups_remote_server&gt; entry contains the value of a ServerName entry in
/etc/cups/client.conf. The &lt;server_settings&gt; section contains all values
of the cupsd configuration file (/etc/cups/cupsd.conf) so that a complete
&lt;server_settings&gt; section is required to get a reasonable cupsd
configuration installed.
+</para>
+
+
+ &example.printer;
+ </section>
+

Added: trunk/autoinstallation/doc/xml/Profile.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Profile.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/Profile.xml (added)
+++ trunk/autoinstallation/doc/xml/Profile.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,324 @@
+
+<chapter id="Profile">
+ <title>The Control File</title>
+
+ <section id="Profile.Intro">
+ <title>
+ Introduction
+ </title>
+
+ <para>
+ The control file is in most cases a configuration description for a
+ single system. It consists of
+ sets of resources with properties including support for complex
+ structures representations such as lists, records, trees and large
+ embedded or referenced objects.
+ </para>
+
+ </section>
+ <section id="Profile.Format">
+ <title>
+ Format
+ </title>
+
+ <para>
+ The XML configuration format provides a consistent file structure, which
is
+ easier to learn and remember when attempting to configure a new system.

+ </para>
+ <para>
+ Using XML, you can eliminate (nearly) all of the configuration
+ file parsing and error handling - an external XML parser can do that
instead
+ - (especially if it is a validating parser). To make sure the control
file is
+ well-formatted and that the syntax is valid, you can run the control file
+ through a validating parser before it is actually used for automatic
+ installation. This is especially required if you prefer to edit the
+ profile manually.
+ </para>
+
+ <para>
+ The following example shows a control file in XML format:
+ </para>
+ <example><title>XML Control File (Profile)</title>
+ <screen>
+<![CDATA[
+<?xml version="1.0"?>
+<!DOCTYPE profile>
+ <profile
+ xmlns="http://www.suse.com/1.0/yast2ns";
+ xmlns:config="http://www.suse.com/1.0/configns";>
+ <install> <!-- install is deprecated since SUSE Linux 10.0 -->
+ <partitioning config:type="list">
+ <drive>
+ <device>/dev/hda</device>
+ <partitions config:type="list">
+ <partition>
+ <filesystem config:type="symbol">ext2</filesystem>
+ <size>520Mb</size>
+ <mount>/</mount>
+ </partition>
+ <partition>
+ <filesystem config:type="symbol">reiser</filesystem>
+ <size>1200Mb</size>
+ <mount>/data</mount>
+ </partition>
+ </partitions>
+ </drive>
+ </partitioning>
+ </install> <!-- install is deprecated since SUSE Linux 10.0 -->
+ <configure> <!-- configure is deprecated since SUSE Linux 10.0 -->
+ <scripts>
+ <pre-scripts>
+ <script>
+ <interpreter>shell</interpreter>
+ <filename>start.sh</filename>
+ <source>
+]]>
+ &lt;![CDATA[
+#!/bin/sh
+echo "Starting installation"
+exit 0
+
+]]&gt;
+<![CDATA[
+ </source>
+ </script>
+ </pre-scripts>
+ </scripts>
+ </configure> <!-- configure is deprecated since SUSE Linux 10.0 -->
+</profile>
+]]>
+
+ </screen>
+ </example>
+ </section>
+
+
+
+ <section id="Profile.Structure">
+ <title>
+ Structure
+ </title>
+ <para>
+ Below is an example of a basic control file container, the actual content
+ of which is explained later on in this chapter.
+ </para>
+
+ <example>
+ <title>Control file container</title>
+ <screen>
+<![CDATA[
+<?xml version="1.0"?>
+<!DOCTYPE profile>
+ <profile
+ xmlns="http://www.suse.com/1.0/yast2ns";
+ xmlns:config="http://www.suse.com/1.0/configns";>
+
+<!-- RESOURCES -->
+
+</profile>
+]]>
+ </screen>
+ </example>
+ <para>
+ The profile element (root node) contains one or more distinct resource
+ elements. The permissible resource elements are specified in the schema
files
+ </para>
+ <section>
+ <title>
+ Resources and Properties
+ </title>
+ <para>
+ A resource element either contains multiple and distinct property and
+ resource elements or contains multiple instances of the same resource
+ element or is empty. The permissible content of a resource element is
+ specified in the schema files.
+ </para>
+ <para>
+ A property element is either empty or contains a literal value. The
+ permissible property elements and values in each resource element are
+ specified in the schema files
+ </para>
+ <para>
+ An element can be either a container of other elements (a resource) or
+ have a literal value (a property), it can never be both. This
+ restriction is specified in the schema files. A configuration component
with
+ more than one value must either be represented as some kind of embedded
+ list in a property value or as a nested resource.
+ </para>
+ </section>
+ <section>
+ <title>
+ Nested Resources
+ </title>
+ <para>
+ Nested resource elements allow a tree like structure of configuration
+ components to be built to any level.
+ </para>
+ <example>
+ <title>
+ Nested Resources
+ </title>
+ <screen>
+<![CDATA[
+...
+<drive>
+ <device>/dev/hda</device>
+ <partitions config:type="list">
+ <partition>
+ <size>1000mb</size>
+ <mount>/</mount>
+ </partition>
+ <partition>
+ <size>250mb</size>
+ <mount>/tmp</mount>
+ </partition>
+ </partitions>
+</drive>
+....
+]]>
+ </screen>
+ </example>
+
+ <para>
+ In the example above the disk resource consists of a device property
+ and a partitions resource. The partitions resource contains multiple
+ instances of the partition resource. Each partition resource contains a
+ size and mount property.
+ </para>
+ <para>
+ Although it is specified in the schema files that the partitions
resource
+ contains multiple instances, it is still required to specify this to
+ avoid wrong data typing in &yast2;. Using the example above, imagine
having a
+ drive with only one partition. This will result in interpreting the
+ partition resource as a property. To avoid this the following syntax
+ must be used when defining multiple instances. For more information
+ about type attributes, see next section.
+ </para>
+ <example>
+ <title>
+ Nested Resources with type attributes
+ </title>
+ <screen>
+<![CDATA[
+...
+<drive>
+ <device>/dev/hda</device>
+ <partitions config:type="list">
+ <partition>
+ <size>1000</size>
+ <mount>/</mount>
+ </partition>
+ <partition>
+ <size>250</size>
+ <mount>/tmp</mount>
+ </partition>
+ </partitions>
+</drive>
+....
+]]>
+ </screen>
+ </example>
+ </section>
+
+ <section>
+ <title>
+ Attributes
+ </title>
+ <para>
+ Global profile attributes are used to define meta-data on resources and
+ properties. Attributes are used to define context switching. They are
also used for naming and
+ typing properties as shown in earlier sectionons
+ <footnote>
+ <para>
+ Profile attributes are in a separate namespace so they don't have
+ to be treated as reserved words in the default namespace. New ones
+ can then be added without having to potentially alter existing
+ profiles.
+ </para>
+ </footnote>.
+ </para>
+ <para>
+ Profile attributes are defined in the configuration namespace and must
+ always be prefixed with <emphasis>config:</emphasis> . All profile
attributes are
+ optional. Most can be used with both resource and property elements but
+ some can only be used with one type of element which is specified in
+ the schema files.
+ </para>
+
+
+ <para>
+ The type of an element is defined using the
<emphasis>config:type</emphasis> attribute. The
+ type of a resource element is always RESOURCE , although this can
+ also be made explicit with this attribute (to ensure correct
+ identification of an empty element for example when there is no schema
file
+ to refer to). A resource element cannot be any other type and this
+ restriction is specified in the schema file. The type of a property
element
+ determines the interpretation of its literal value. The type of a
+ property element defaults to <emphasis>STRING</emphasis> , as specified
in the schema file. The
+ full set of permissible types is specified in the schema file.
+ </para>
+
+ </section>
+ </section>
+
+ <section id="Profile.DTD">
+ <title>
+ RELAX NG - a schema language for XML
+ </title>
+ <section>
+ <title>
+ Introduction
+ </title>
+ <para>
+A RELAX NG schema specifies a pattern for the structure and content of an XML
document.
+A RELAX NG schema thus identifies a class of XML documents consisting of those
documents that match the pattern.
+A RELAX NG schema is itself an XML document.
+ </para>
+ <para>
+ Verfify your autoyast XML file
+ <screen>
+/usr/bin/xmllint --noout --relaxng
/usr/share/YaST2/schema/autoyast/rng/profile.rng myAutoYaSTProfile.xml
+ </screen>
+ </para>
+ </section>
+ </section>
+
+
+</chapter>
+
+
+
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast.xml" "part" "chapter")
+ End:
+ -->
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

Added: trunk/autoinstallation/doc/xml/ReportSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/ReportSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/ReportSection.xml (added)
+++ trunk/autoinstallation/doc/xml/ReportSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,77 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+<section id="CreateProfile.Reporting">
+ <title id="CreateProfile.Reporting.title">
+ Reporting
+ </title>
+
+ <para>
+ The <emphasis>report</emphasis> resource manages 3 types of pop-ups
+ that may appear during installation.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Messages Popups (Usually non-critical, informative messages)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Warning Popups (If something might go wrong)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Error Popups (In the case of an error)
+ </para>
+ </listitem>
+ </itemizedlist>
+ <example>
+ <title>Reporting Behavior</title>
+ <screen>
+ <xi:include href="examples/example.reporting.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+
+ <para>
+ Depending on your experience, you can skip, log and show (with timeout)
+ those messages. It is recommended to show all
+ <emphasis>messages</emphasis> with timeout. Warnings can be skipped in
+ some places but should not be ignored.
+ </para>
+ <para>
+ By default, the settings in auto-installation mode is to show all messages
without logging and
+ with a timeout of 10 seconds.
+ </para>
+ <warning>
+ <title>
+ Critical system messages
+ </title>
+ <para>
+ Note that <emphasis>not</emphasis> all messages during installation are
controlled by the
+ <emphasis>report</emphasis> resource. Some critical messages concerning
+ package installation and partitioning will still show up ignoring your
+ settings in the <emphasis>report</emphasis> section. Mostly those
+ messages will have to be answered with <emphasis>Yes</emphasis> or
<emphasis>No</emphasis>.
+ </para>
+ </warning>
+ </section>
+

Added: trunk/autoinstallation/doc/xml/RulesAndClasses.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/RulesAndClasses.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/RulesAndClasses.xml (added)
+++ trunk/autoinstallation/doc/xml/RulesAndClasses.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,883 @@
+
+<chapter id="rulesandclass">
+ <title>Rules and Classes</title>
+ <section id="rules">
+ <title>Rule based auto-installation</title>
+ <para>
+ Rules offer the possibility to configure a system depending on system
+ attributes by merging multiple control file during installation. The
+ rules based installation is controlled by a rules file.
+ </para>
+ <para>
+ The rules file is an XML based file that contains
+ rules for each group of systems (or single systems) that you want to
+ automatically install. A set of rules distinguish a group of systems
based on
+ one or more system attributes, after passing all rules, it links each
+ group of rules to a profile. Both the rules file and the profiles must be
+ located in a pre-defined and accessible location.
+ </para>
+ <para>
+ The rules file is retrieved only if no specific control is supplied
+ using the <emphasis>autoyast</emphasis> keyword. For example, if the
+ following is used, the rules file wont be evaluated:
+ </para>
+ <screen>
+ autoyast=http://10.10.0.1/profile/myprofile.xml
+ autoyast=http://10.10.0.1/profile/rules/rules.xml
+ </screen>
+ instead use
+ <screen>
+ autoyast=http://10.10.0.1/profile/
+ </screen>
+ which will load http://10.10.0.1/profile/rules/rules.xml (the slash at the
end is important)
+ <figure id="rules_fig1">
+ <title id="rules_fig1.title" >Rules</title>
+ <mediaobject>&rules;</mediaobject>
+ </figure>
+ <para>
+ If more than one rule apply, the final profile for each group is
generated
+ on the fly using a merge script. The merging process is based on the
+ order of the rules and later rules override configuration data in
earlier rules.
+ </para>
+ <para>
+ The use of a rules file is optional. If the rules file is not found,
+ system installation proceeds in the
+ classic way by just using the supplied profile or by searching for the
+ profile depending on the <emphasis>MAC</emphasis> or the
+ <emphasis>IP</emphasis> address of the system.
+ </para>
+<!--
+ <para>
+ In the previous scenario, you would create a rules file with two
different
+ rules, one rule for the development and another rule for the sales
+ department. For each rule, you could use different system parameters to
+ distinguish the groups from one another: the development department has
SMP
+ and SCI based systems and the sales group has IDE based systems. Each
rule
+ would also contain a link to an appropriate profile. For example, in the
+ rule for the development department, you would add a link to the
profile, called
+ <filename>devel.xml</filename>, that you created for this department.
And, in the rule
+ for the sales department, you would add a link to the profile, called
+ <filename>sales.xml</filename>, that you created for the sales
department.
+ </para>
+-->
+
+ <section id="rulesfile">
+ <title>Rules File explained</title>
+
+ <example>
+ <title>
+ Simple rules file
+ </title>
+
+ <para>
+ The following simple example illustrates how the rules file is used
+ to retrieve the configuration for a client with known hardware.
+ </para>
+ <screen>
+<![CDATA[
+<?xml version="1.0"?>
+<!DOCTYPE autoinstall>
+<autoinstall xmlns="http://www.suse.com/1.0/yast2ns";
xmlns:config="http://www.suse.com/1.0/configns";>
+ <rules config:type="list">
+ <rule>
+ <disksize>
+ <match>/dev/hdc 1000</match>
+ <match_type>greater</match_type>
+ </disksize>
+ <result>
+ <profile>machine1.xml</profile>
+ <continue config:type="boolean">false</continue>
+ </result>
+ </rule>
+ <rule>
+ <disksize>
+ <match>/dev/hda 1000</match>
+ <match_type>greater</match_type>
+ </disksize>
+ <result>
+ <profile>machine2.xml</profile>
+ <continue config:type="boolean">false</continue>
+ </result>
+ </rule>
+ </rules>
+</autoinstall>
+]]>
+ </screen>
+
+ </example>
+ <para>
+ The last example defines 2 rules and provides a different profile for
+ every rule. The rule used in this case is
+ <emphasis>disksize</emphasis>. After parsing the rules file, &yast2;
+ attempts to match the system being installed to the rules in the
+ <filename>rules.xml</filename> file in the following order: first rule
through the
+ last rule. A rule match occurs when the system being installed matches
+ all of the system attributes defined in the rule. As soon as a system
+ matches a rule, the result resource is added to the
+ stack of profiles &autoyast; will be using to create the final
+ profile. The <emphasis>continue</emphasis> property tells &autoyast;
if it should
+ continue with other rules or not after a match has been found.
+ </para>
+ <para>
+ If the first rule does not match, next rule in the list is examined
+ until a match is found.
+ </para>
+ <para>
+ Using the <emphasis>disksize</emphasis> attribute, you can
+ provide different configurations for different hard drives with
+ different size. First rule checks if the device
+ <emphasis>/dev/hdc</emphasis> is available and if it is greater than 1
+ GB in size using the <emphasis>match</emphasis> property.
+ </para>
+
+ <para>
+ A rule must have at least one attribute to be matched. If you need
+ to check more attributes, i.e. memory or architectures, you can add
+ more attributes in the rule resource as shown in the next example.
+ </para>
+ <example>
+ <title>
+ Simple rules file
+ </title>
+
+ <para>
+ The following simple example illustrates how the rules file is used
+ to retrieve the configuration for a client with known hardware.
+ </para>
+ <screen>
+<![CDATA[
+<?xml version="1.0"?>
+<!DOCTYPE autoinstall>
+<autoinstall xmlns="http://www.suse.com/1.0/yast2ns";
xmlns:config="http://www.suse.com/1.0/configns";>
+ <rules config:type="list">
+ <rule>
+ <disksize>
+ <match>/dev/hdc 1000</match>
+ <match_type>greater</match_type>
+ </disksize>
+ <memsize>
+ <match>1000</match>
+ <match_type>greater</match_type>
+ </memsize>
+ <result>
+ <profile>machine1.xml</profile>
+ <continue config:type="boolean">false</continue>
+ </result>
+ </rule>
+ <rule>
+ <disksize>
+ <match>/dev/hda 1000</match>
+ <match_type>greater</match_type>
+ </disksize>
+ <memsize>
+ <match>256</match>
+ <match_type>greater</match_type>
+ </memsize>
+ <result>
+ <profile>machine2.xml</profile>
+ <continue config:type="boolean">false</continue>
+ </result>
+ </rule>
+ </rules>
+</autoinstall>
+]]>
+ </screen>
+
+ </example>
+ <para>
+ The rules directory must be located in the same referenced directory
+ used with the <emphasis>autoyast</emphasis> keyword on boot time, so
+ if the client was booted using<emphasis>
autoyast=http://10.10.0.1/profiles/</emphasis>,
+ &autoyast; will search for the rules file in
+ <emphasis>http://10.10.0.1/profiles/rules/rules.xml</emphasis>.
+ </para>
+ </section>
+ <section id="customrules">
+ <title>Custom Rules</title>
+ <para>
+ If the attributes autoyast provides for rules are not enough for
you,
+ you can use custom rules. Custom rules are more or less a shell
script
+ you have to write has and whose output on STDOUT is being used to
know
+ which autoyast profile should be fetched. STDERR will be ignored.
+ </para>
+ <para>
+ Here is an example for the use of a custom rules:
+ </para>
+ <para>
+ <screen>
+<![CDATA[
+<rule>
+ <custom1>
+ <script>
+if grep -i intel /proc/cpuinfo > /dev/null; then
+echo -n "intel"
+else
+echo -n "non_intel"
+fi;
+ </script>
+ <match>*</match>
+ <match_type>exact</match_type>
+ </custom1>
+ <result>
+ <profile>@custom1@.xml</profile>
+ <continue config:type="boolean">true</continue>
+ </result>
+</rule>
+]]>
+ </screen>
+ </para>
+ <para>
+ The script in this rule can echo either "intel" or "non_intel" to
STDOUT (the
+ output of the grep command must be directed to /dev/null in this
case).
+ Autoyast will catch that output and will fetch a file with the
name "intel.xml"
+ or "non_intel.xml". This file can contain the autoyast profile
part for the
+ software selection for example, in the case you want to do a
different
+ software selection on intel hardware than on others. So the output
of the rule
+ script will be filled between the two '@' characters, to determine
the filename of
+ the profile to fetch.
+ </para>
+ <para>
+ The number of custom rules is limited to 5. So you can use custom1
to custom5.
+ </para>
+ </section>
+ <section id="matchtypes">
+ <title>Match Types for rules</title>
+ <para>
+ you can have five different match_types:
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ exact - which is the default
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ greater
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ lower
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ range
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ regex (available since 10.1 and SLES10). It's a simple
"=~" operator like in bash
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ "greater" and "lower" can be used for memsize or totaldisk for
+ example. They can match only on rules which return an integer
value.
+ A range is only possible for integer values too and has the form of
+ "value1-value2", for example "512-1024". regex can be used to
match substrings
+ like "ntel" will match "Intel","intel" and "intelligent".
+ </para>
+ </section>
+ <section id="rulescombination">
+ <title>Combine Attributes</title>
+ <para>
+ It's possible to combine multiple attributes via a logical
operator. So it's
+ possible to let a rule match if disksize is greater than 1GB or
memsize
+ is exact 512MB (well, not the best example maybe).
+ </para>
+ <para>
+ You can do that with the "operator" element in the rules.xml file.
Here is
+ an example:
+ </para>
+ <para>
+ <screen>
+<![CDATA[
+<rule>
+ <disksize>
+ <match>/dev/hda 1000</match>
+ <match_type>greater</match_type>
+ </disksize>
+ <memsize>
+ <match>256</match>
+ <match_type>greater</match_type>
+ </memsize>
+ <result>
+ <profile>machine2.xml</profile>
+ <continue config:type="boolean">false</continue>
+ </result>
+ <operator>or</operator>
+</rule>
+]]>
+ </screen>
+ </para>
+ <para>
+ Just "and" and "or" are possible operators and the default
operator
+ is "and".
+ </para>
+ </section>
+ <section id="rulesstructure">
+ <title>Rules file structure</title>
+ <para>
+ The <filename>rules.xml</filename> file must have:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>At least one rule</para>
+ </listitem>
+ <listitem>
+ <para>It must have the name <filename>rules.xml</filename></para>
+ </listitem>
+ <listitem>
+ <para>It must be located in the directory
+ <emphasis>rules</emphasis> in the profile repository</para>
+ </listitem>
+
+ <listitem>
+ <para>At least one attribute to match in the rule</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section id="ruleattributes">
+ <title>Predefined System Attributes</title>
+ <para>
+ The following table lists the predefined system attributes you can
+ match in the rules file.
+ </para>
+ <para>
+ If you are unsure about a value on your system, start an
autoinstallation.
+ If the proposal shows up, switch to the console via CTRL+ALT+F2 and run
+ <screen>/usr/lib/YaST2/bin/y2base ayast_probe ncurses
+ </screen>. It might help to to turn the confirmation on for this, so that
+ the installation does not start in the background while you are watching
the
+ values. The textbox with the values is scrollable.
+ </para>
+ <table frame='top'>
+ <title>System Attributes</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>hostaddress</entry>
+ <entry>IP address of the host</entry>
+ <entry>This attribute must always match exactly</entry>
+ </row>
+ <row>
+ <entry>hostname</entry>
+ <entry>The name of the host</entry>
+ <entry>This attribute must always match exactly</entry>
+ </row>
+ <row>
+ <entry>domain</entry>
+ <entry>Domain name of host</entry>
+ <entry>This attribute must always match exactly</entry>
+ </row>
+ <row>
+ <entry>installed_product</entry>
+ <entry>The name of the product that is getting installed. For
example "SUSE LINUX"</entry>
+ <entry>This attribute must always match exactly</entry>
+ </row>
+ <row>
+ <entry>installed_product_version</entry>
+ <entry>The version of the product that is getting installed.
For example "9.3"</entry>
+ <entry>This attribute must always match exactly</entry>
+ </row>
+ <row>
+ <entry>network</entry>
+ <entry>network address of host</entry>
+ <entry>This attribute must always match exactly</entry>
+ </row>
+ <row>
+ <entry>mac</entry>
+ <entry>MAC address of host</entry>
+ <entry>This attribute must always match exactly. (MAC addresses
+ to be matched should be in the form
<emphasis>0080c8f6484c</emphasis></entry>
+ </row>
+ <row>
+ <entry>linux</entry>
+ <entry>Number of installed Linux partitions on the
system</entry>
+ <entry>This attribute can be 0 or more</entry>
+ </row>
+ <row>
+ <entry>others</entry>
+ <entry>Number of installed non-Linux partitions on the
system</entry>
+ <entry>This attribute can be 0 or more</entry>
+ </row>
+ <row>
+ <entry>xserver</entry>
+ <entry>X Server needed for graphic adapter</entry>
+ <entry>This attribute must always match exactly</entry>
+ </row>
+ <row>
+ <entry>memsize</entry>
+ <entry>Memory available on host in MByes</entry>
+ <entry>All match types are available</entry>
+ </row>
+ <row>
+ <entry>totaldisk</entry>
+ <entry>Total disk space available on host in MBytes</entry>
+ <entry>All match types are available</entry>
+ </row>
+ <row>
+ <entry>haspcmica</entry>
+ <entry>System has PCMCIA (i.e Laptops)</entry>
+ <entry>Exact match required, 1 for available PCMCIA or 0 for
none</entry>
+ </row>
+ <row>
+ <entry>hostid</entry>
+ <entry>Hex representation of IP address</entry>
+ <entry>Exact match required</entry>
+ </row>
+ <row>
+ <entry>arch</entry>
+ <entry>Architecture of host</entry>
+ <entry>Exact match required</entry>
+ </row>
+ <row>
+ <entry>karch</entry>
+ <entry>Kernel Architecture of host (i.e. SMP kernel, Athlon
Kernel)</entry>
+ <entry>Exact match required</entry>
+ </row>
+ <row>
+ <entry>disksize</entry>
+ <entry>Drive device and size</entry>
+ <entry>All match types are available</entry>
+ </row>
+ <row>
+ <entry>product</entry>
+ <entry>The hardware product name as specified in SMBIOS</entry>
+ <entry>Exact match required</entry>
+ </row>
+ <row>
+ <entry>product_vendor</entry>
+ <entry>The hardware vendor as specified in SMBIOS</entry>
+ <entry>Exact match required</entry>
+ </row>
+ <row>
+ <entry>board</entry>
+ <entry>The system board name as specified in SMBIOS</entry>
+ <entry>Exact match required</entry>
+ </row>
+ <row>
+ <entry>board_vendor</entry>
+ <entry>The system board vendor as specified in SMBIOS</entry>
+ <entry>Exact match required</entry>
+ </row>
+ <row>
+ <entry>custom1-5</entry>
+ <entry>Custom rules using shell scripts</entry>
+ <entry>All match types are available</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section id="rules_dialogs">
+ <title>Rules with Dialogs</title>
+ <para>
+ Since openSUSE 11.3 (not SLES11 SP1) you can use dialog popups where
you can select which rules you want to match and which not by checkboxes.
+ </para>
+ <para>
+ The following elements must be between the &lt;rules
config:type="list"&gt;&lt;rule&gt;&lt;dialog&gt; ...
&lt;/dialog&gt;&lt;/rule&gt;&lt;/rules&gt; tags in the rules.xml file.
+ </para>
+ <table frame='top'>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>dialog_nr</entry>
+ <entry>all rules with the same dialog_nr are presented on the
same popup dialog so the same dialog_nr can appear in multiple rules.
+ <para><screen>&lt;dialog_nr
config:type="integer"&gt;3&lt;/dialog_nr&gt;</screen></para>
+ </entry>
+ <entry>This element is optional and the default for a missing
dialog_nr is always "0". If you have one popup only anyway, you don't need to
specify the dialog_nr</entry>
+ </row>
+ <row>
+ <entry>element</entry>
+ <entry>each element needs a uniq id. Even if you have more
than one dialog, you must not use the same id twice like an id "1" on dialog 1
and and id "1" on dialog 2. That's different than with &lt;ask&gt; dialogs,
where you can have the same &lt;element&gt; id on multiple dialogs.
+ <para><screen>&lt;element
config:type="integer"&gt;3&lt;/element&gt;</screen></para>
+ </entry>
+ <entry>optional. If left out, autoyast adds his own id's
internally but you can't use conflicts then (see below)</entry>
+ </row>
+ <row>
+ <entry>title</entry>
+ <entry>the caption of the popup dialog
+ <para><screen>&lt;title&gt;Desktop
Selection&lt;/title&gt;</screen></para>
+ </entry>
+ <entry>optional</entry>
+ </row>
+ <row>
+ <entry>question</entry>
+ <entry>the question text is shown in the popup behind the
checkbox.
+ <para><screen>&lt;question&gt;KDE
Desktop&lt;/question&gt;</screen></para>
+ </entry>
+ <entry>optional. If you don't configure a text here, the name
of the XML file that is triggered by this rule will be shown instead.</entry>
+ </row>
+ <row>
+ <entry>timeout</entry>
+ <entry>a timeout in seconds after which the dialog will
automatically "press" the okay button. Useful for a non blocking installation
in combination with rules-dialogs.
+ <para><screen>&lt;timeout
config:type="integer"&gt;30&lt;/timeout&gt;</screen></para>
+ </entry>
+ <entry>optional. A missing timeout will stop the installation
process until the dialog is confirmed by the user.</entry>
+ </row>
+ <row>
+ <entry>conflicts</entry>
+ <entry>a list of element id's (rules) that conflict with this
rule. If this rule matches or is selected by the user, all conflicting rules
are deselected and disabled in the popup. Take care that you don't create
deadlocks.
+ <para><screen>&lt;conflicts config:type="list"&gt;
+ &lt;element config:type="integer"&gt;1&lt;/element&gt;
+ &lt;element config:type="integer"&gt;5&lt;/element&gt;
+ ...
+&lt;/conflicts&gt;</screen></para>
+ </entry>
+ <entry>optional</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ <para>
+ Here is an example of how to use dialogs with rules:
+ </para>
+ <para>
+ <screen>
+<![CDATA[
+ <rules config:type="list">
+ <rule>
+ <custom1>
+ <script>
+echo -n 100
+ </script>
+ <match>100</match>
+ <match_type>exact</match_type>
+ </custom1>
+ <result>
+ <profile>rules/kde.xml</profile>
+ <continue config:type="boolean">true</continue>
+ </result>
+ <dialog>
+ <element config:type="integer">0</element>
+ <question>KDE Desktop</question>
+ <title>Desktop Selection</title>
+ <conflicts config:type="list">
+ <element config:type="integer">1</element>
+ </conflicts>
+ <dialog_nr config:type="integer">0</dialog_nr>
+ </dialog>
+ </rule>
+ <rule>
+ <custom1>
+ <script>
+echo -n 100
+ </script>
+ <match>101</match>
+ <match_type>exact</match_type>
+ </custom1>
+ <result>
+ <profile>rules/gnome.xml</profile>
+ <continue config:type="boolean">true</continue>
+ </result>
+ <dialog>
+ <element config:type="integer">1</element>
+ <dialog_nr config:type="integer">0</dialog_nr>
+ <question>Gnome Desktop</question>
+ <conflicts config:type="list">
+ <element config:type="integer">0</element>
+ </conflicts>
+ </dialog>
+ </rule>
+ <rule>
+ <custom1>
+ <script>
+echo -n 100
+ </script>
+ <match>100</match>
+ <match_type>exact</match_type>
+ </custom1>
+ <result>
+ <profile>rules/all_the_rest.xml</profile>
+ <continue config:type="boolean">false</continue>
+ </result>
+ </rule>
+ </rules>
+]]>
+ </screen>
+ </para>
+ </section>
+ </section>
+
+
+
+
+ <section id="classes">
+ <title>Classes</title>
+ <para>
+ You can assign a system to different classes which can be defined in the
+ control file. Unlike rules, classes have to be configured in the control
+ file and represent a configuration which is typical for a group of
+ systems.
+ </para>
+ <para>
+ Here is an example of a class definition:
+ </para>
+ <para>
+ <screen>
+<![CDATA[
+<classes config:type="list">
+ <class>
+ <class_name>TrainingRoom</class_name>
+ <configuration>Software.xml</configuration>
+ </class>
+</classes>
+]]>
+ </screen>
+ </para>
+ <para>
+ The file Software.xml must be in the directory "classes/TrainingRoom/"
then and
+ it will get fetched from the same place like the autoyast profile and
the rules were
+ fetched from.
+ </para>
+ <para>
+ If you have multiple kind of profiles and those profiles share parts,
it's recommended to
+ use classes for that. You just have to change the class and all
profiles using that class
+ are fixed too. By the way, you can reach something similar by using
XIncludes.
+ </para>
+ <para>
+ Using the configuration management system, you can define a set of
+ classes. The class definition consists of the following variable for
each class:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Name: Class name
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Descriptions: Class description
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Order: Order (or priority) of the class in the stack of migration
+ </para>
+ </listitem>
+ </itemizedlist>
+ <figure>
+ <title>Defining Classes</title>
+ <mediaobject>&cms-class-definitions;</mediaobject>
+ </figure>
+ <para>
+ You can create as many classes as you need, however it is
+ recommended to keep the set of classes as small as possible to keep the
+ configuration system concise. As an example, the following set of
+ classes can be used:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ site: Classes describing a physical location or site.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ machine: Classes describing a type of machine or make
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ role: Classes describing the function of the machine to be
+ installed
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ group: Classes describing a department or a group within a site
+ or a location.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ A file saved in a class directory can have the same syntax and format
as a
+ regular control file but represents a subset of the configuration. For
example,
+ to create a new control file for a special computer with a specific
network
+ interface, only the resource in the control file, which controls
+ the configuration of the network is needed. Having multiple network
+ types, you can merge the one needed for a special type of hardware
+ with other class files and create a new control file which suits
+ the system being installed.
+ </para>
+
+ </section>
+
+ <section id="mixinfrulesclasses">
+ <title>Mixing Rules and Classes</title>
+ <para>
+ It is possible to mix rules and classes during an auto-installation
+ session. For example you can identify a system using rules which contain
+ class definitions in them. The process is described in the figures
+ <quote><link linkend='rulesflow'
+ endterm="rulesflow.title"></link></quote>.
+ </para>
+ <para>
+ After retrieving the rules and merging them, the generated control file
+ is parsed and the presence of class definitions is checked. If classes
+ are defined, then the class files are retrieved from the original
+ repository and a new merge process is initiated.
+ </para>
+ </section>
+ <section id="merging">
+ <title>The merging process of Rules and Classes</title>
+ <para>
+ With classes and with rules, multiple XML files get merged to one
resulting
+ XML file. This process of merging is often confusing for people, because
+ it behaves different than one would expect.
+ </para>
+ <para>
+ Let's take a look at two XML parts that we want to merge:
+ </para>
+ <para>
+ <screen>
+&lt;partitioning config:type=&quot;list&quot;&gt;
+ &lt;drive&gt;
+ &lt;partitions config:type=&quot;list&quot;&gt;
+ &lt;partition&gt;
+ &lt;filesystem
config:type=&quot;symbol&quot;&gt;swap&lt;/filesystem&gt;
+ &lt;format
config:type=&quot;boolean&quot;&gt;true&lt;/format&gt;
+ &lt;mount&gt;swap&lt;/mount&gt;
+ &lt;partition_id
config:type=&quot;integer&quot;&gt;130&lt;/partition_id&gt;
+ &lt;size&gt;2000mb&lt;/size&gt;
+ &lt;/partition&gt;
+ &lt;partition&gt;
+ &lt;filesystem
config:type=&quot;symbol&quot;&gt;xfs&lt;/filesystem&gt;
+ &lt;partition_type&gt;primary&lt;/partition_type&gt;
+ &lt;size&gt;4Gb&lt;/size&gt;
+ &lt;mount&gt;/data&lt;/mount&gt;
+ &lt;/partition&gt;
+ &lt;/partitions&gt;
+ &lt;/drive&gt;
+&lt;/partitioning&gt;
+ </screen>
+ </para>
+ <para>
+ <screen>
+&lt;partitioning config:type=&quot;list&quot;&gt;
+ &lt;drive&gt;
+ &lt;initialize config:type=&quot;boolean&quot;&gt;false&lt;/initialize&gt;
+ &lt;partitions config:type=&quot;list&quot;&gt;
+ &lt;partition&gt;
+ &lt;format config:type=&quot;boolean&quot;&gt;true&lt;/format&gt;
+ &lt;filesystem
config:type=&quot;symbol&quot;&gt;xfs&lt;/filesystem&gt;
+ &lt;mount&gt;/&lt;/mount&gt;
+ &lt;partition_id
config:type=&quot;integer&quot;&gt;131&lt;/partition_id&gt;
+ &lt;partition_type&gt;primary&lt;/partition_type&gt;
+ &lt;size&gt;max&lt;/size&gt;
+ &lt;/partition&gt;
+ &lt;/partitions&gt;
+ &lt;use&gt;all&lt;/use&gt;
+ &lt;/drive&gt;
+&lt;/partitioning&gt;
+ </screen>
+ </para>
+ <para>
+ What you would expect is, that you'll end up in a profile with 3
partitions.
+ That is not the case. You'll end up with two partitions and the first
partition
+ is a mixup of the swap and the root partition. Stuff that is configured
in both
+ partitions, like <emphasis>mount</emphasis> or
<emphasis>size</emphasis>, will
+ be used from the second file.
+ Stuff that only exists in the first or second partition, will be copied
to the
+ merged partition too.
+ </para>
+ <para>
+ Sometimes this is what you want, but sometimes this is not what you
want. Actually,
+ in my example above, this is both. You don't want a second
<emphasis>drive</emphasis>
+ right? You want the two drives to be merged into one but for partitions
you want three seperate
+ ones.
+ So how can you achieve what you want? In this example, how do you get
three partitions but still
+ one drive?
+ </para>
+ <para>
+ <note>For SLES9/SUSE Linux 10.0 and earlier versions</note> you can only
use a trick. It's
+ not official supported by autoyast and more a workaround than a nice
solution. For each partition
+ in one file, add an attribute to the partition like this:
+ </para>
+ <para>
+ <screen>
+&lt;partition dontmerge=&quot;1&quot;&gt;
+...
+&lt;/partitions&gt;
+ </screen>
+ </para>
+ <para>
+ The trick is, that the merge script will not detect the partitions as
the same element type because of the
+ new attribute. If you have more files, it might be needed to to add more
attributes like <emphasis>dontmerge="2"</emphasis>.
+ </para>
+ <para>
+ <note>For SLES10/SUSE Linux 10.1 and later</note>
+ you can use the <emphasis>dont_merge</emphasis> element in the rules or
classes file
+ like this:
+ </para>
+ <para>
+ <screen>
+&lt;classes config:type=&quot;list&quot;&gt;
+ &lt;class&gt;
+ &lt;class_name&gt;swap&lt;/class_name&gt;
+ &lt;configuration&gt;largeswap.xml&lt;/configuration&gt;
+ &lt;dont_merge config:type=&quot;list&quot;&gt;
+ &lt;element&gt;partition&lt;/element&gt;
+ &lt;/dont_merge&gt;
+ &lt;/class&gt;
+&lt;/classes&gt;
+ </screen>
+ </para>
+ <para>
+ <screen>
+&lt;rule&gt;
+ &lt;board_vendor&gt;
+ &lt;match&gt;ntel&lt;/match&gt;
+ &lt;match_type&gt;regex&lt;/match_type&gt;
+ &lt;/board_vendor&gt;
+ &lt;result&gt;
+ &lt;profile&gt;classes/largeswap.xml&lt;/profile&gt;
+ &lt;continue config:type=&quot;boolean&quot;&gt;true&lt;/continue&gt;
+ &lt;dont_merge config:type=&quot;list&quot;&gt;
+ &lt;element&gt;partition&lt;/element&gt;
+ &lt;/dont_merge&gt;
+ &lt;/result&gt;
+ &lt;board_vendor&gt;
+ &lt;match&gt;PowerEdge [12]850&lt;/match&gt;
+ &lt;match_type&gt;regex&lt;/match_type&gt;
+ &lt;/board_vendor&gt;
+ &lt;result&gt;
+ &lt;profile&gt;classes/smallswap.xml&lt;/profile&gt;
+ &lt;continue config:type=&quot;boolean&quot;&gt;true&lt;/continue&gt;
+ &lt;dont_merge config:type=&quot;list&quot;&gt;
+ &lt;element&gt;partition&lt;/element&gt;
+ &lt;/dont_merge&gt;
+ &lt;/result&gt;
+&lt;/rule&gt;
+ </screen>
+ </para>
+ </section>
+</chapter>
+
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast2.xml" "book" "chapter")
+ End:
+ -->

Added: trunk/autoinstallation/doc/xml/RunlevelSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/RunlevelSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/RunlevelSection.xml (added)
+++ trunk/autoinstallation/doc/xml/RunlevelSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,48 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+ <section id="CreateProfile.Services">
+ <title>
+ Services and Run-levels
+ </title>
+ <para>
+ With the run-level resource you can set the default run-level and specify
+ in detail which system services you want to be started in which
+ run-level.
+ </para>
+ <para>
+ The default property specifies the <emphasis>default</emphasis> run
+ level of the system. Changes to the default run-level will take effect
+ the next time you boot the system. After installation is completed,
+ the system has run-level 5, which is <emphasis>Full multiuser with
+ network and XDM</emphasis>. If you have configured a system with no
+ X11, then it is recommended to reboot the system after the first stage
+ using the <emphasis>reboot</emphasis> property in the
<emphasis>general</emphasis> resource.
+
+ </para>
+ <para>
+ A service should run in using a space delimited list of the run-levels
+ as shown in the following example. An alternative to specifying the
+ exact run-levels is to change the status of the service by either
+ enabling or disabling it using the
+ <emphasis>service_status</emphasis> property.
+ </para>
+ &example.runlevels;
+
+ </section>
+

Added: trunk/autoinstallation/doc/xml/ScriptsSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/ScriptsSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/ScriptsSection.xml (added)
+++ trunk/autoinstallation/doc/xml/ScriptsSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,549 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+ <section id="createprofile.scripts">
+ <title>Custom user scripts</title>
+ <para>
+ By adding scripts to the auto-installation process you can customize the
+ installation for your needs and take control in different stages of the
+ installation.
+ </para>
+ <para>
+ In the auto-installation process, five types of scripts can be executed
and they
+ will be described here in order of "appearance" during the installation.
+ </para>
+ <para>
+ <note>All scripts have to be in the &lt;scritps&gt; section.</note>
+ </para>
+ <para>
+ <itemizedlist>
+ <listitem><emphasis>pre-scripts</emphasis> (very early, before
anything else really happened)</listitem>
+ <listitem><emphasis>postpartitioning-scripts</emphasis> (after
partitioning and mounting to /mnt but before RPM installation - since openSUSE
11.2)</listitem>
+ <listitem><emphasis>chroot-scripts</emphasis> (after the package
installation, before the first boot)</listitem>
+ <listitem><emphasis>post-scripts</emphasis> (during the first boot of
the installed system, no services running)</listitem>
+ <listitem><emphasis>init-scripts</emphasis> (during the first boot of
the installed system, all servies up and running)</listitem>
+ </itemizedlist>
+ </para>
+ <section id="pre-install.scripts">
+ <title>Pre-Install Scripts</title>
+ <para>
+ Executed before &yast2; does any real change to the system
+ (Before partitioning and package installation but after the hardware
detection)
+ </para>
+ <para>
+ You can use the pre-script to modify your profile and let autoyast read
it again.
+ If you want to do that, you can find your profile in
"/tmp/profile/autoinst.xml".
+ Do what you want to do with that file and store the modified version in
+ "/tmp/profile/modified.xml". Autoyast will read that modified script
then again after
+ the pre-script is done.
+ </para>
+ <para>
+ With SUSE Linux 10.0 and all following versions it's possible to change
the partitioning with fdisk
+ in your pre-script. With pre 10.0 versions of SUSE Linux (like SLES9),
that was not possible.
+ </para>
+ <note><title>Pre-Install Scripts with confirmation</title>
+ <para>
+ Pre-scripts are executed at an early stage of the installation.
+ This means if you have requested to confirm the installation, the
+ pre-scripts will be executed before the confirmation screen
+ shows up.
(<emphasis>profile/install/general/mode/confirm</emphasis>)
+ </para>
+ </note>
+ <para>
+ The following elements must be between the
&lt;scripts&gt;&lt;pre-scripts config:type="list"&gt;&lt;script&gt; ...
&lt;/script&gt;&lt;/pre-scripts&gt;...&lt;/scripts&gt; tags
+ </para>
+ <para>
+ <table frame='top'>
+ <title>pre script XML representation</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>location</entry>
+ <entry>you can define a location from where the script gets
fetched.
+ Locations can be the same like for the profile
(http,ftp,nfs,...).
+
<para><screen>&lt;location&gt;http://10.10.0.1/myPreScript.sh&lt;/location&gt;</screen></para></entry>
+ <entry>either &lt;location&gt; or &lt;source&gt; must be
defined</entry>
+ </row>
+ <row>
+ <entry>source</entry>
+ <entry>the script itself. The source code of the script if you
want so. Encapsulated in a CDATA tag. If you don't want
+ to put the whole shell script into the XML profile, look at
the location parameter.
+
+ <para><screen>&lt;source&gt;
+&lt;![CDATA[
+echo "Testing the pre script" &gt; /tmp/pre-script_out.txt
+]]&gt;
+&lt;/source&gt;</screen></para></entry>
+ <entry>Either &lt;location&gt; or &lt;source&gt; must be
defined</entry>
+ </row>
+ <row>
+ <entry>interpreter</entry>
+ <entry>the interpreter that must be used for the script.
Supported options are shell and perl.
+
<para><screen>&lt;interpreter&gt;perl&lt;/interpreter&gt;</screen></para></entry>
+ <entry>optional (default is shell)</entry>
+ </row>
+ <row>
+ <entry>filename</entry>
+ <entry>the filename of the script. It will be stored in a
temporary directory under /tmp/...
+
<para><screen>&lt;filename&gt;myPreScript5.sh&lt;/filename&gt;</screen></para></entry>
+ <entry>optional. The default is the type of the script
(pre-scripts) in this case</entry>
+ </row>
+ <row>
+ <entry>feedback</entry>
+ <entry>if this boolean is true, stdout and stderr of the
script will be shown in a popup that the
+ user has to confirm via ok-button. If stdout and stderr
are empty, no popup is shown and so
+ no confirmation is needed.
+ <para><screen>&lt;feedback
config:type="boolean"&gt;true&lt;/feedback&gt;</screen></para></entry>
+ <entry>optional. The default is false. This option was
invented with SL 10.1 / SLES10</entry>
+ </row>
+ <row>
+ <entry>feedback_type</entry>
+ <entry>this can be "message", "warning", "error" and you can
control the timeout of those popups with the &lt;report&gt; section.
+
<para><screen>&lt;feedback_type&gt;warning&lt;/feedback_type&gt;</screen></para></entry>
+ <entry>optional. If missing, an always blocking popup is used.
This option was invited with openSUSE 11.2 (not SLES11)</entry>
+ </row>
+ <row>
+ <entry>debug</entry>
+ <entry>if this is true, every single line of a shell script is
logged. Perl scripts are run with warnings
+ turned on.
+ <para><screen>&lt;debug
config:type="boolean"&gt;true&lt;/debug&gt;</screen></para></entry>
+ <entry>optional. The default is true. This option was invented
with SL 10.1 / SLES10</entry>
+ </row>
+ <row>
+ <entry>notification</entry>
+ <entry>This text will be shown in a popup for the time the
script is running in the background
+ <para><screen>&lt;notification&gt;Please wait while script is
running ...&lt;/notification&gt;</screen></para></entry>
+ <entry>optional. If not configured, no notification popup will
be shown. This option was invented with openSUSE 11.3/SLES11 SP2 (not
SLES10)</entry>
+ </row>
+ <row>
+ <entry>rerun</entry>
+ <entry>a script is only run once. So even if you use
ayast_setup to run a XML file multiple times, the script is only run once. You
can change that with this boolean.
+ <para><screen>&lt;rerun
config:type="boolean"&gt;true&lt;/rerun&gt;</screen></para></entry>
+ <entry>optional. The default is false which makes scripts only
run one time</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ </section>
+
+ <section id="postpartitioning-install.scripts">
+ <title>Postpartitioning Scripts</title>
+ <note>
+ <para>Available starting from openSUSE 11.2 only (not SLES11).</para>
+ </note>
+ <para>
+ Executed after &yast2; did the partitioning and wrote the fstab. The
empty system is mounted to /mnt already.
+ This type of script is available since openSUSE 11.2 (not SLES11).
+ </para>
+ <para>
+ The following elements must be between the
&lt;scripts&gt;&lt;postpartitioning-scripts
config:type="list"&gt;&lt;script&gt; ...
&lt;/script&gt;&lt;/postpartitioning-scripts&gt;...&lt;/scripts&gt; tags
+ </para>
+ <para>
+ <table frame='top'>
+ <title>postpartitioning script XML representation</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>location</entry>
+ <entry>you can define a location from where the script gets
fetched.
+ Locations can be the same like for the profile
(http,ftp,nfs,...).
+
<para><screen>&lt;location&gt;http://10.10.0.1/myScript.sh&lt;/location&gt;</screen></para></entry>
+ <entry>either &lt;location&gt; or &lt;source&gt; must be
defined</entry>
+ </row>
+ <row>
+ <entry>source</entry>
+ <entry>the script itself. The source code of the script if you
want so. Encapsulated in a CDATA tag. If you don't want
+ to put the whole shell script into the XML profile, look at
the location parameter.
+
+ <para><screen>&lt;source&gt;
+&lt;![CDATA[
+echo "Testing postpart script" &gt; /mnt/postpart_test.txt
+]]&gt;
+&lt;/source&gt;</screen></para></entry>
+ <entry>Either &lt;location&gt; or &lt;source&gt; must be
defined</entry>
+ </row>
+ <row>
+ <entry>interpreter</entry>
+ <entry>the interpreter that must be used for the script.
Supported options are shell and perl.
+
<para><screen>&lt;interpreter&gt;perl&lt;/interpreter&gt;</screen></para></entry>
+ <entry>optional (default is shell)</entry>
+ </row>
+ <row>
+ <entry>filename</entry>
+ <entry>the filename of the script. It will be stored in a
temporary directory under /tmp/...
+
<para><screen>&lt;filename&gt;myScript5.sh&lt;/filename&gt;</screen></para></entry>
+ <entry>optional. The default is the type of the script
(postpartitioning-scripts in this case)</entry>
+ </row>
+ <row>
+ <entry>feedback</entry>
+ <entry>if this boolean is true, stdout and stderr of the
script will be shown in a popup that the
+ user has to confirm via ok-button. If stdout and stderr
are empty, no popup is shown and so
+ no confirmation is needed.
+ <para><screen>&lt;feedback
config:type="boolean"&gt;true&lt;/feedback&gt;</screen></para></entry>
+ <entry>optional. The default is false. This option was
invented with SL 10.1 / SLES10</entry>
+ </row>
+ <row>
+ <entry>feedback_type</entry>
+ <entry>this can be "message", "warning", "error" and you can
control the timeout of those popups with the &lt;report&gt; section.
+
<para><screen>&lt;feedback_type&gt;warning&lt;/feedback_type&gt;</screen></para></entry>
+ <entry>optional. If missing, an always blocking popup is used.
This option was invited with openSUSE 11.2 (not SLES11)</entry>
+ </row>
+ <row>
+ <entry>debug</entry>
+ <entry>if this is true, every single line of a shell script is
logged. Perl scripts are run with warnings
+ turned on.
+ <para><screen>&lt;debug
config:type="boolean"&gt;true&lt;/debug&gt;</screen></para></entry>
+ <entry>optional. The default is true. This option was invented
with SL 10.1 / SLES10</entry>
+ </row>
+ <row>
+ <entry>notification</entry>
+ <entry>This text will be shown in a popup for the time the
script is running in the background
+ <para><screen>&lt;notification&gt;Please wait while script is
running ...&lt;/notification&gt;</screen></para></entry>
+ <entry>optional. If not configured, no notification popup will
be shown. This option was invented with openSUSE 11.3/SLES11 SP2 (not
SLES10)</entry>
+ </row>
+ <row>
+ <entry>rerun</entry>
+ <entry>a script is only run once. So even if you use
ayast_setup to run a XML file multiple times, the script is only run once. You
can change that with this boolean.
+ <para><screen>&lt;rerun
config:type="boolean"&gt;true&lt;/rerun&gt;</screen></para></entry>
+ <entry>optional. The default is false which makes scripts only
run one time</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ </section>
+
+
+
+ <section id="chroot.scripts">
+ <title>Chroot environment scripts</title>
+ <para>Chroot scripts are executed before the machine reboots for the
first time.
+ Actually chroot scripts are two differnt kind of script with
+ one name. You can execute chroot script before the installation chroots
into
+ the installed system and configures the boot loader and you can execute
a script
+ after the chroot into the installed system has happend (look at the
"chrooted" parameter for that). Both types of scripts are
+ executed before yast2 boots for the first time.
+ </para>
+ <para>
+ The following elements must be between the
&lt;scripts&gt;&lt;chroot-scripts config:type="list"&gt;&lt;script&gt; ...
&lt;/script&gt;&lt;/chroot-scripts&gt;...&lt;/scripts&gt; tags
+ </para>
+ <para>
+ <table frame='top'>
+ <title>chroot script XML representation</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>location</entry>
+ <entry>you can define a location from where the script gets
fetched.
+ Locations can be the same like for the profile
(http,ftp,nfs,...).
+ <para>
+
<screen>&lt;location&gt;http://10.10.0.1/myChrootScript.sh&lt;/location&gt;</screen>
+ </para></entry>
+ <entry>either &lt;location&gt; or &lt;source&gt; must be
defined</entry>
+ </row>
+ <row>
+ <entry>source</entry>
+ <entry>the script itself. The source code of the script if you
want so. Encapsulated in a CDATA tag. If you don't want
+ to put the whole shell script into the XML profile, look at
the location parameter.
+ <para><screen>&lt;source&gt;
+&lt;![CDATA[
+echo "Testing the chroot script" &gt; /tmp/chroot_out.txt
+]]&gt;
+&lt;/source&gt;</screen></para></entry>
+ <entry>either &lt;location&gt; or &lt;source&gt; must be
defined</entry>
+ </row>
+ <row>
+ <entry>chrooted</entry>
+ <entry>this value can be true or false. "False" means that the
installed system is still mounted at "/mnt" and no chrooting has happened till
now. The bootloader is not installed too at that stage. "True" means, we did a
chroot into /mnt, so we are now in the installed system. The bootloader is
installed and if you want to change anything in the installed system, you don't
have to use the "/mnt/" prefix anymore.
+ <para><screen>&lt;chrooted
config:type="boolean"&gt;true&lt;/chrooted&gt;</screen></para></entry>
+ <entry>optional (the default is false)</entry>
+ </row>
+ <row>
+ <entry>interpreter</entry>
+ <entry>the interpreter that must be used for the script.
Supported options are shell and perl.and if you are in a chrooted=true
condition, you can use python too if it's installed.
+
<para><screen>&lt;interpreter&gt;perl&lt;/interpreter&gt;</screen></para></entry>
+ <entry>optional (default is shell)</entry>
+ </row>
+ <row>
+ <entry>filename</entry>
+ <entry>the filename of the script. It will be stored in a
temporary directory under /tmp/...
+
<para><screen>&lt;filename&gt;myPreScript5.sh&lt;/filename&gt;</screen></para></entry>
+ <entry>optional. The default is the type of the script
(chroot-scripts) in this case</entry>
+ </row>
+ <row>
+ <entry>feedback</entry>
+ <entry>if this boolean is true, stdout and stderr of the
script will be shown in a popup that the
+ user has to confirm via ok-button. If stdout and stderr
are empty, no popup is shown and so
+ no confirmation is needed.
+ <para><screen>&lt;feedback
config:type="boolean"&gt;true&lt;/feedback&gt;</screen></para></entry>
+ <entry>optional. The default is false. This option was
invented with SL 10.1 / SLES10</entry>
+ </row>
+ <row>
+ <entry>feedback_type</entry>
+ <entry>this can be "message", "warning", "error" and you can
control the timeout of those popups with the &lt;report&gt; section.
+
<para><screen>&lt;feedback_type&gt;warning&lt;/feedback_type&gt;</screen></para></entry>
+ <entry>optional. If missing, an always blocking popup is used.
This option was invited with openSUSE 11.2 (not SLES11)</entry>
+ </row>
+ <row>
+ <entry>debug</entry>
+ <entry>if this is true, every single line of a shell script is
logged. Perl scripts are run with warnings
+ turned on.
+ <para><screen>&lt;debug
config:type="boolean"&gt;true&lt;/debug&gt;</screen></para></entry>
+ <entry>optional. The default is true. This option was invented
with SL 10.1 / SLES10</entry>
+ </row>
+ <row>
+ <entry>notification</entry>
+ <entry>This text will be shown in a popup for the time the
script is running in the background
+ <para><screen>&lt;notification&gt;Please wait while script is
running ...&lt;/notification&gt;</screen></para></entry>
+ <entry>optional. If not configured, no notification popup will
be shown. This option was invented with openSUSE 11.3/SLES11 SP2 (not
SLES10)</entry>
+ </row>
+ <row>
+ <entry>rerun</entry>
+ <entry>a script is only run once. So even if you use
ayast_setup to run a XML file multiple times, the script is only run once. You
can change that with this boolean.
+ <para><screen>&lt;rerun
config:type="boolean"&gt;true&lt;/rerun&gt;</screen></para></entry>
+ <entry>optional. The default is false which makes scripts only
run one time</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ </section>
+ <section id="post-insall.scripts">
+ <title>Post-Install Scripts</title>
+ <para>
+ These scripts are executed after AutoYaST has completed the
+ system configuration and after it has booted the system for the first
time.
+ </para>
+ <para>
+ It is possible to execute the post scripts in an earlier phase while
+ the installation network is still up and before AutoYaST configures
+ the system. To run network enabled post scripts, the boolean
+ property <emphasis>network_needed</emphasis> has to be set to true.
+ </para>
+ <para>
+ The following elements must be between the
&lt;scripts&gt;&lt;post-scripts config:type="list"&gt;&lt;script&gt; ...
&lt;/script&gt;&lt;/post-scripts&gt;...&lt;/scripts&gt; tags
+ </para>
+ <para>
+ <table frame='top'>
+ <title>post script XML representation</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>location</entry>
+ <entry>you can define a location from where the script gets
fetched.
+ Locations can be the same like for the profile
(http,ftp,nfs,...) but then you need a running network interface of course
+ <para>
+
<screen>&lt;location&gt;http://10.10.0.1/myPostScript.sh&lt;/location&gt;</screen>
+ </para></entry>
+ <entry>either &lt;location&gt; or &lt;source&gt; must be
defined</entry>
+ </row>
+ <row>
+ <entry>source</entry>
+ <entry>the script itself. The source code of the script if you
want so. Encapsulated in a CDATA tag. If you don't want
+ to put the whole shell script into the XML profile, look at
the location parameter.
+ <para><screen>&lt;source&gt;
+&lt;![CDATA[
+echo "Testing the chroot script" &gt; /tmp/chroot_out.txt
+]]&gt;
+&lt;/source&gt;</screen></para></entry>
+ <entry>either &lt;location&gt; or &lt;source&gt; must be
defined</entry>
+ </row>
+ <row>
+ <entry>network_needed</entry>
+ <!-- FIXME: double check that. I'm very unsure if this is
correct -->
+ <entry>this value can be true or false. On "false" the script
will run after the yast modules like the user configuration and everything else
are done. The network is configured but still not up and running. With this
value on "true", the script runs before(!) all yast modules are configured. So
there is no local user and no network is configured but the installation
network is still up and running (of course only if you did a network
installation).
+ <para><screen>&lt;network_needed
config:type="boolean"&gt;true&lt;/network_needed&gt;</screen></para></entry>
+ <entry>optional (the default is false)</entry>
+ </row>
+ <row>
+ <entry>interpreter</entry>
+ <entry>the interpreter that must be used for the script.
Supported options are shell, perl and python if it's installed.
+
<para><screen>&lt;interpreter&gt;perl&lt;/interpreter&gt;</screen></para></entry>
+ <entry>optional (default is shell)</entry>
+ </row>
+ <row>
+ <entry>filename</entry>
+ <entry>the filename of the script. It will be stored in a
temporary directory under /tmp/...
+
<para><screen>&lt;filename&gt;myPostScript5.sh&lt;/filename&gt;</screen></para></entry>
+ <entry>optional. The default is the type of the script
(post-scripts) in this case</entry>
+ </row>
+ <row>
+ <entry>feedback</entry>
+ <entry>if this boolean is true, stdout and stderr of the
script will be shown in a popup that the
+ user has to confirm via ok-button. If stdout and stderr
are empty, no popup is shown and so
+ no confirmation is needed.
+ <para><screen>&lt;feedback
config:type="boolean"&gt;true&lt;/feedback&gt;</screen></para></entry>
+ <entry>optional. The default is false. This option was
invented with SL 10.1 / SLES10</entry>
+ </row>
+ <row>
+ <entry>feedback_type</entry>
+ <entry>this can be "message", "warning", "error" and you can
control the timeout of those popups with the &lt;report&gt; section.
+
<para><screen>&lt;feedback_type&gt;warning&lt;/feedback_type&gt;</screen></para></entry>
+ <entry>optional. If missing, an always blocking popup is used.
This option was invited with openSUSE 11.2 (not SLES11)</entry>
+ </row>
+ <row>
+ <entry>debug</entry>
+ <entry>if this is true, every single line of a shell script is
logged. Perl scripts are run with warnings
+ turned on.
+ <para><screen>&lt;debug
config:type="boolean"&gt;true&lt;/debug&gt;</screen></para></entry>
+ <entry>optional. The default is true. This option was invented
with SL 10.1 / SLES10</entry>
+ </row>
+ <row>
+ <entry>notification</entry>
+ <entry>This text will be shown in a popup for the time the
script is running in the background
+ <para><screen>&lt;notification&gt;Please wait while script is
running ...&lt;/notification&gt;</screen></para></entry>
+ <entry>optional. If not configured, no notification popup will
be shown. This option was invented with openSUSE 11.3/SLES11 SP2 (not
SLES10)</entry>
+ </row>
+ <row>
+ <entry>rerun</entry>
+ <entry>a script is only run once. So even if you use
ayast_setup to run a XML file multiple times, the script is only run once. You
can change that with this boolean.
+ <para><screen>&lt;rerun
config:type="boolean"&gt;true&lt;/rerun&gt;</screen></para></entry>
+ <entry>optional. The default is false which makes scripts only
run one time</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ </section>
+ <section id="init.scripts">
+ <title>Init Scripts</title>
+ <para>
+ These scripts are executed during the initial boot process and after
+ &yast2; has finished. The final scripts are executed using a special
+ <emphasis>init.d</emphasis> script which is executed only
+ once. The final scripts are executed toward the end of the boot
+ process and after network has been intialized.
+ </para>
+ <para>
+ Init scripts are configured using the tag
<emphasis>init-scripts</emphasis> and
+ are run using the special purpose <emphasis>init.d</emphasis>
script <filename>/etc/init.d/autoyast</filename>.
+ </para>
+ <para>
+ The following elements must be between the
&lt;scripts&gt;&lt;init-scripts config:type="list"&gt;&lt;script&gt; ...
&lt;/script&gt;&lt;/init-scripts&gt;...&lt;/scripts&gt; tags
+ </para>
+ <para>
+ <table frame='top'>
+ <title>init script XML representation</title>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Element</entry>
+ <entry>Description</entry>
+ <entry>Comment</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>location</entry>
+ <entry>you can define a location from where the script gets
fetched.
+ Locations can be the same like for the profile
(http,ftp,nfs,...) but then you need a running network interface of course
+ <para>
+
<screen>&lt;location&gt;http://10.10.0.1/myInitScript.sh&lt;/location&gt;</screen>
+ </para></entry>
+ <entry>either &lt;location&gt; or &lt;source&gt; must be
defined</entry>
+ </row>
+ <row>
+ <entry>source</entry>
+ <entry>the script itself. The source code of the script if you
want so. Encapsulated in a CDATA tag. If you don't want
+ to put the whole shell script into the XML profile, look at
the location parameter.
+ <para><screen>&lt;source&gt;
+&lt;![CDATA[
+echo "Testing the init script" &gt; /tmp/init_out.txt
+]]&gt;
+&lt;/source&gt;</screen></para></entry>
+ <entry>either &lt;location&gt; or &lt;source&gt; must be
defined</entry>
+ </row>
+ <row>
+ <entry>filename</entry>
+ <entry>the filename of the script. It will be stored in a
temporary directory under /tmp/...
+
<para><screen>&lt;filename&gt;mynitScript5.sh&lt;/filename&gt;</screen></para></entry>
+ <entry>optional. The default is the type of the script
(init-scripts) in this case</entry>
+ </row>
+ <row>
+ <entry>rerun</entry>
+ <entry>a script is only run once. So even if you use
ayast_setup to run a XML file multiple times, the script is only run once. You
can change that with this boolean.
+ <para><screen>&lt;rerun
config:type="boolean"&gt;true&lt;/rerun&gt;</screen></para></entry>
+ <entry>optional. The default is false which makes scripts only
run one time</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ </section>
+ <para>
+ When added to the control file manually, the
+ scripts have to be included in a <emphasis>CDATA</emphasis> element to
avoid confusion with
+ the file syntax and other tags defined in the control file.
+ </para>
+ <section id="script_examples">
+ <title>Script example</title>
+ <example>
+ <title>Post script configuration</title>
+ <screen>
+ <xi:include href="examples/example.scripts.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ </screen>
+ </example>
+ <para>
+ After installation is finished, the scripts and the output logs can be
+ found in the directory <filename>/var/adm/autoinstall</filename>. The
+ scripts are located in <filename>scripts</filename> and the output logs
of the
+ scripts are located in the <filename>log</filename> directory.
+ </para>
+ <para>
+ The log is the output resulting when executing the shell scripts using
+ the following command:
+ </para>
+ <screen>
+ <![CDATA[
+ /bin/sh -x <script_name> 2&> /var/adm/autoinstall/logs/<script_name>.log
+ ]]>
+ </screen>
+ </section>
+ </section>
+

Added: trunk/autoinstallation/doc/xml/SecuritySection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/SecuritySection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/SecuritySection.xml (added)
+++ trunk/autoinstallation/doc/xml/SecuritySection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,90 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+
+ <section id="CreateProfile.Security">
+ <title>
+ Security settings
+ </title>
+
+ <para>
+ Using the features of this module, you will be able to change the local
+ security settings on the target system. The local security settings
+ include the boot configuration, login settings, password settings,
+ user addition settings, and file permissions.
+ </para>
+ <para>
+ Configuring the security settings automatically corresponds to the
+ <emphasis>Custom Settings</emphasis> in the security module available in
+ the running system which lets you create your own, customized
+ configuration.
+ </para>
+
+ &example.security;
+ <section>
+ <title>Password Settings Options</title>
+ <para>
+ Change various password settings. These settings are mainly stored in
the <filename>/etc/login.defs</filename> file.
+ </para>
+ <para>
+ Use this resource to activate one of the
<emphasis>encryption</emphasis> methods currently supported.
+ If not set, <emphasis>DES</emphasis> is configured.
+ </para>
+ <para>
+ <emphasis>DES</emphasis>, the Linux default method, works in all
+ network environments, but it restricts you to passwords no longer than
+ eight characters. <emphasis>MD5</emphasis> allows longer passwords,
+ thus provides more security, but some network protocols don't support
+ this, and you may have problems with NIS. <emphasis>Blowfish</emphasis>
+ is also supported.
+ </para>
+ <para>Additionally, you can setup the system to check for password
+ plausibility and length etc.</para>
+ </section>
+ <section>
+ <title>Boot Settings</title>
+ <para>
+ Use the security resource, you can change various boot settings.
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>How to interpret Ctrl + Alt + Del</emphasis></para>
+ <para>When someone at the console has pressed the CTRL + ALT + DEL
key combination, the system usually reboots. Sometimes it is desirable to
ignore this event, for example, when the system serves as both workstation and
server.</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>Shutdown behavior of KDM</emphasis></para>
+ <para>Set who is allowed to shut down the machine from KDM.</para>
+ </listitem>
+ </itemizedlist>
+
+
+ </section>
+ <section>
+ <title>Login Settings</title>
+ <para>Change various login settings. These settings are mainly stored in
the '/etc/login.defs' file.</para>
+ </section>
+ <section>
+ <title>New user settings (useradd settings)</title>
+ <para>Set the minimum and maximum possible user ID and set the minimum
+ and maximum possible group ID.
+ </para>
+ </section>
+
+ </section>
+

Added: trunk/autoinstallation/doc/xml/SoftwareSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/SoftwareSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/SoftwareSection.xml (added)
+++ trunk/autoinstallation/doc/xml/SoftwareSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,413 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+<section id="CreateProfile.Software">
+ <title>
+ Software
+ </title>
+
+ <section id="Software.Selections.sles10">
+ <title>
+ Package Selections with patterns
+ </title>
+ <para>
+ SLES10 no longer supports <emphasis>selections</emphasis> but uses
+ <emphasis>patterns</emphasis> now. Autoyast is not be able to convert
+ selections into patterns and so you have to do that on your own.
+ If you want to use a SLES9 autoyast profile to install a SLES10
+ server, you have to remove all <emphasis>addon</emphasis> entries and the
+ <emphasis>base</emphasis> entry. Patterns are configured like this:
+ </para>
+ <example>
+ <title>
+ Package selection in control file with patterns
+ </title>
+ <screen>
+<xi:include href="examples/example.software.patterns.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+ <para>
+ As you can see, the <emphasis>packages</emphasis> section is still the
same like on
+ a SLES9. Just the <emphasis>addon</emphasis> and
<emphasis>base</emphasis> is gone.
+ </para>
+ </section>
+ <section>
+ <title>
+ Deploying Images
+ </title>
+ <para>
+ This feature is available since openSUSE 11.1 but not in SLES11.
+ </para>
+ <para>
+ Since openSUSE 11.0 you can choose to use images during installation to
speed up the installation.
+ This is available in openSUSE 11.1 too. At then end, in the installed
system, there is
+ no difference visible if you did an image or a single RPM installation.
+ </para>
+ <example>
+ <title>
+ Activating images deployment
+ </title>
+ <screen>
+<xi:include href="examples/example.software.images.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+ </section>
+
+ <section>
+ <title>
+ Installing additional and customized Packages
+ </title>
+ <para>
+ In addition to the packages available for installation on the CD-ROMs,
+ you can add external packages including customized kernels. Customized
+ kernel packages must be compatible to the &company-suse; packages and
must
+ install the kernel files to the same locations.
+ </para>
+ <para>
+ Unlike earlier versions, to install custom and external packages
+ there is no need for a special resource in the control
+ file. Instead you need to re-create the package database and update
+ it with any new packages or new package versions in the source
repository.
+ </para>
+ <para>
+ A script is provided for this task which will query packages
+ available in the repository and create the required package
+ database.
+ </para>
+
+ <para>
+ Creating a new package database is only needed if new RPMs
+ (i.e. update RPMs) were added. To re-create the database, use the
+ <command>/usr/bin/create_package_descr</command>
+ command. For example, use this command line to create the package
+ database. (When creating the database, all languages will be reset to
English).
+ </para>
+ <example>
+ <title>Creating package database</title>
+ <screen>
+ cd /usr/local/CDs/LATEST/suse
+ create_package_descr -x PATH_TO_EXTRA_PROV -d
/usr/local/CDs/LATEST/suse
+ </screen>
+ </example>
+ <note>
+ <title>Change starting from SUSE Linux 9.1/SLES 9</title>
+ <para>To provide extra dependencies which can not be extracted from the
+ rpm files, an extra file with missing dependencies is available in the
+ directory <filename>suse/setup/descr</filename>. The file
+ <filename>EXTRA_PROV</filename> can be used when recreating the package
+ database using the <emphasis>-x</emphasis> option.</para>
+ </note>
+ <para>
+ In the above example, the directory
+ <filename>/usr/local/CDs/LATEST/suse</filename> contains the architecture
+ dependent and independent packages, i.e. <emphasis>noarch</emphasis> and
<emphasis>i586</emphasis>.
+ This might look different on other architectures.
+ </para>
+ <para>
+ The advantage of this method is that you can keep an up-to-date
+ repository with fixed and updated package (i.e. from &company-suse; FTP
+ server). Additionally this method makes the creation of custom CD-ROMs
easier.
+ </para>
+ <note>
+ <title>Change starting from SUSE Linux 10.1/SLES 10</title>
+ <para>
+ With SLES10/SL10.1, the concept of adding own RPMs to an installation
source has changed.
+ The <emphasis>yast/order</emphasis> and
<emphasis>yast/instorder</emphasis> is no longer supported. Neither
+ by AutoYaST nor by YaST. To add own RPMs to an installation source
(that includes add-on products like the
+ SDK) you have to add a file <emphasis>add_on_products</emphasis> to
the CD1 of the main product.
+ <screen>
+media_url [path_on_media [product_1 [product_2 [....]]]
+ </screen>
+ media_url is URL of the media itself
+ path_on_media is path of the catalog on the media. If not present, /
(root) is assumed
+ product_1 and following are the names for products, which should be
marked for installation. If no product is mentioned, all products found on the
media are selected for installation.
+ For example:
+ <screen>
+http://192.168.66.6/SLES10/sdk/CD1
+http://192.168.66.6/SLES10/CD1/updates
+ </screen>
+ Besides that <emphasis>add_on_products</emphasis> file, you can use
the autoyast profile to specify add-on products. For example:
+ <screen>
+&lt;add-on&gt;
+ &lt;add_on_products config:type=&quot;list&quot;&gt;
+ &lt;listentry&gt;
+ &lt;media_url&gt;http://192.168.66.6/SLES10/CD1/updates&lt;/media_url&gt;
+ &lt;product&gt;SuSE-Linux-Updates&lt;/product&gt;
+ &lt;product_dir&gt;/&lt;/product_dir&gt;
+ &lt;ask_on_error config:type="boolean"&gt;false&lt;/ask_on_error&gt;
&lt;!-- available since openSUSE 11.0 --&gt;
+ &lt;name&gt;MyUpdates&lt;/name&gt; &lt;!-- available since openSUSE
11.1/SLES11 (bnc#433981) --&gt;
+ &lt;/listentry&gt;
+ &lt;/add_on_products&gt;
+&lt;/add-on&gt;
+ </screen>
+ With that entry in the autoyast profile, the
<emphasis>add_on_products</emphasis> file is not necessary.
+ Since openSUSE 11.0 AutoYaST can ask the user to make the add-on
available intead of reporting a timed out error when the add-on can't be found
at the given location. Set ask_on_error to true for that (the default is false).
+ Your add-on can be on a different CD/DVD than the installation source
then.
+ </para>
+ <para>
+ YaST checks the signatures of files on the installation source now. If
a <emphasis>content</emphasis> file is
+ not signed, during a manual installation YaST asks the user what to
do. During an autoinstallation, the
+ installation source gets rejected silently.
+ </para>
+ </note>
+ <para>
+ If you want to use unsigned installation sources with autoyast, you
can turn of the checks with the following
+ configuration in your autoyast profile (part of the
<emphasis>general</emphasis> section.
+ </para>
+ <para>
+ The following elements must be between the
&lt;general&gt;&lt;signature-handling&gt; ...
&lt;/signature-handling&gt;&lt;/general&gt; tags.
+ </para>
+ <para>
+ <table frame='top'>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>accept_unsigned_file</entry>
+ <entry>the installer will accept unsigned files like the
content file
+ <para><screen>&lt;accept_unsigned_file
config:type="boolean"&gt;true&lt;/accept_unsigned_file&gt;</screen></para>
+ </entry>
+ <entry>optional. If left out, autoyast lets yast decide what
to do</entry>
+ </row>
+ <row>
+ <entry>accept_file_without_checksum</entry>
+ <entry>the installer will accept files without a checksum in
the content file
+ <para><screen>&lt;accept_file_without_checksum
config:type="boolean"&gt;true&lt;/accept_file_without_checksum&gt;</screen></para>
+ </entry>
+ <entry>optional. If left out, autoyast lets yast decide what
to do</entry>
+ </row>
+ <row>
+ <entry>accept_verification_failed</entry>
+ <entry>the installer will accept files where the verification
of the signature failed. So the file was signed but the check failed.
+ <para><screen>&lt;accept_verification_failed
config:type="boolean"&gt;true&lt;/accept_verification_failed&gt;</screen></para>
+ </entry>
+ <entry>optional. If left out, autoyast lets yast decide what
to do</entry>
+ </row>
+ <row>
+ <entry>accept_unknown_gpg_key</entry>
+ <entry>the installer will accept new gpg keys on the
installation source that are used to sign the content file for example
+ <para><screen>&lt;accept_unknown_gpg_key
config:type="boolean"&gt;true&lt;/accept_unknown_gpg_key&gt;</screen></para>
+ </entry>
+ <entry>optional. If left out, autoyast lets yast decide what
to do</entry>
+ </row>
+ <row>
+ <entry>accept_non_trusted_gpg_key</entry>
+ <entry>This basically means, we know the key, but it is not
trusted
+ <para><screen>&lt;accept_non_trusted_gpg_key
config:type="boolean"&gt;true&lt;/accept_non_trusted_gpg_key&gt;</screen></para>
+ </entry>
+ <entry>optional. If left out, autoyast lets yast decide what
to do</entry>
+ </row>
+ <row>
+ <entry>import_gpg_key</entry>
+ <entry>the installer will accept and import new gpg keys on
the installation source in it's database.
+ <para><screen>&lt;import_gpg_key
config:type="boolean"&gt;true&lt;/import_gpg_key&gt;</screen></para>
+ </entry>
+ <entry>optional. If left out, autoyast lets yast decide what
to do</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ <para>
+ Since openSUSE 10.3 it's possible to configure the signature handling for
each add-on individually. The following elements must be between the
+ &lt;signature-handling&gt; section of the individual add-on.
+ </para>
+ <para>
+ <table frame='top'>
+ <tgroup cols="3">
+ <thead>
+ <row>
+ <entry>Attribute</entry>
+ <entry>Values</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>accept_unsigned_file</entry>
+ <entry>the installer will accept unsigned files like the
content file for this add-on product
+ <para><screen>&lt;accept_unsigned_file
config:type="boolean"&gt;true&lt;/accept_unsigned_file&gt;</screen></para>
+ </entry>
+ <entry>optional. If left out, the global signature-handing in
the &lt;general&gt; section is used.</entry>
+ </row>
+ <row>
+ <entry>accept_file_without_checksum</entry>
+ <entry>the installer will accept files without a checksum in
the content file for this add-on
+ <para><screen>&lt;accept_file_without_checksum
config:type="boolean"&gt;true&lt;/accept_file_without_checksum&gt;</screen></para>
+ </entry>
+ <entry>optional. If left out, the global signature-handing in
the &lt;general&gt; section is used.</entry>
+ </row>
+ <row>
+ <entry>accept_verification_failed</entry>
+ <entry>the installer will accept files where the verification
of the signature failed. So the file was signed but the check failed.
+ <para><screen>&lt;accept_verification_failed
config:type="boolean"&gt;true&lt;/accept_verification_failed&gt;</screen></para>
+ </entry>
+ <entry>optional. If left out, the global signature-handing in
the &lt;general&gt; section is used.</entry>
+ </row>
+ <row>
+ <entry>accept_unknown_gpg_key</entry>
+ <entry>the installer will accept new gpg keys on the
installation source that are used to sign the content file for example
+ <para><screen>
+ &lt;accept_unknown_gpg_key&gt;
+ &lt;all config:type=&quot;boolean&quot;&gt;false&lt;/all&gt;
+ &lt;keys config:type=&quot;list&quot;&gt;
+ &lt;keyid&gt;3B3011B76B9D6523&lt;/keyid&gt;
+ &lt;/keys&gt;
+ &lt;/accept_unknown_gpg_key&gt;
+ </screen></para>
+ </entry>
+ <entry>optional. If left out, the global signature-handing in
the &lt;general&gt; section is used.</entry>
+ </row>
+ <row>
+ <entry>accept_non_trusted_gpg_key</entry>
+ <entry>This basically means, we know the key, but it is not
trusted
+ <para><screen>
+ &lt;accept_non_trusted_gpg_key&gt;
+ &lt;all config:type=&quot;boolean&quot;&gt;false&lt;/all&gt;
+ &lt;keys config:type=&quot;list&quot;&gt;
+ &lt;keyid&gt;3B3011B76B9D6523&lt;/keyid&gt;
+ &lt;/keys&gt;
+ &lt;/accept_non_trusted_gpg_key&gt;
+</screen></para>
+ </entry>
+ <entry>optional. If left out, the global signature-handing in
the &lt;general&gt; section is used.</entry>
+ </row>
+ <row>
+ <entry>import_gpg_key</entry>
+ <entry>the installer will accept and import new gpg keys on
the installation source in it's database.
+ <para><screen>
+ &lt;import_gpg_key&gt;
+ &lt;all config:type=&quot;boolean&quot;&gt;false&lt;/all&gt;
+ &lt;keys config:type=&quot;list&quot;&gt;
+ &lt;keyid&gt;3B3011B76B9D6523&lt;/keyid&gt;
+ &lt;/keys&gt;
+ &lt;/import_gpg_key&gt;
+ </screen></para>
+ </entry>
+ <entry>optional. If left out, the global signature-handing in
the &lt;general&gt; section is used.</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </para>
+ </section>
+ <section>
+ <title>Kernel packages</title>
+ <para>
+ Kernel packages are not part of any selection. The required kernel
+ is determined during installation. If the kernel package is added to any
selection
+ or to the individual package selection, installation will mostly fail
due to conflicts.
+ </para>
+ <para>
+ To force the installation of a specific kernel, use the
+ <emphasis>kernel</emphasis> property. The following is an example
+ forcing the installation of the default kernel. In this example this
+ kernel will be installed in any case, even if an SMP or other kernel
+ is required</para>
+ <example>
+ <title>
+ Package selection in control file
+ </title>
+ <screen>
+<xi:include href="examples/example.kernel.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+ </screen>
+ </example>
+ </section>
+ <section>
+ <title>Removing automatically selected packages</title>
+ <para>
+ Some packages are selected automatically either because of a
+ dependency or because it available in a selection.
+ </para>
+ <para>
+ Removing such packages might break the system consistency and it is
+ not recommended to remove basic packages unless a replacement which
+ provides same services is provided. Best example for this case are
+ <acronym>MTA</acronym> packages. By default, <emphasis>postfix</emphasis>
+ will be selected and installed. If you wish however to use another
+ <acronym>MTA</acronym> like <emphasis>sendmail</emphasis>, then
+ postfix can be removed from the list of selected package using a list
+ in the software resource. The following example shows how this can be
done:
+
+ </para>
+ <example>
+ <title>
+ Package selection in control file
+ </title>
+ <screen>
+<xi:include href="examples/example.removesoft.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+
+
+ </screen>
+ </example>
+ </section>
+ <section>
+ <title>Installing packages during stage 2</title>
+ <para>
+ if you want to install packages after the reboot during stage 2, instead
of
+ during the normal installation process in stage 1, you can use the
+ <emphasis>post-packages</emphasis> element for that:
+ </para>
+ <screen>
+&lt;software&gt;
+ &lt;post-packages config:type=&quot;list&quot;&gt;
+ &lt;package&gt;yast2-cim&lt;/package&gt;
+ &lt;/post-packages&gt;
+&lt;/software&gt;
+ </screen>
+ </section>
+ <section>
+ <para>
+ Since SLES11 and openSUSE 11.1 you can install patterns in stage 2 too.
+ use the <emphasis>post-patterns</emphasis> element for that:
+ </para>
+ <screen>
+&lt;software&gt;
+ &lt;post-patterns config:type=&quot;list&quot;&gt;
+ &lt;pattern&gt;apparmor&lt;/pattern&gt;
+ &lt;/post-patterns&gt;
+&lt;/software&gt;
+ </screen>
+ </section>
+ <section>
+ <title>Online update in stage2</title>
+ <para>
+ since openSUSE 11.1 you can do an online update at the end of the
installation with the boolean
+ <emphasis>do_online_update</emphasis>.
+ Of course that makes only sense if you add an online update repository
with the suse-register/customer-center section for example or in a post-script.
If the online update repository was available in stage1 already via add-on
section, then autoyast has already installed the latest packages available. If
a kernel update is done via online-update, a reboot at the end of stage2 is
triggered.
+ </para>
+ <screen>
+&lt;software&gt;
+ &lt;do_online_update
config:type=&quot;boolean&quot;&gt;true&lt;/do_online_update&gt;
+&lt;/software&gt;
+ </screen>
+ </section>
+ </section>
+

Added: trunk/autoinstallation/doc/xml/SoundSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/SoundSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/SoundSection.xml (added)
+++ trunk/autoinstallation/doc/xml/SoundSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,30 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+ <section id="CreateProfile.Hardware.Sound">
+ <title>
+ Sound devices
+ </title>
+ <para>
+ An example of sound configuration created using the configuration
+ system is shown below.
+ </para>
+ &example.sound;
+ </section>
+

Added: trunk/autoinstallation/doc/xml/SysconfigSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/SysconfigSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/SysconfigSection.xml (added)
+++ trunk/autoinstallation/doc/xml/SysconfigSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,41 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+
+
+ <section id="createprofile.sysconfig">
+ <title>System variables (Sysconfig)</title>
+ <para>
+ Using the sysconfig resource, it is possible to define configuration
+ variables in the sysconfig repository
+ (<filename>/etc/sysconfig</filename>) directly. Sysconfig
+ variables, offer the possibility to fine-tune many system components and
+ environment variables exactly to your needs.
+ </para>
+
+ <para>
+ Refer to the handbook for more details about the many
+ configuration options available in <filename>/etc/sysconfig</filename>
+ </para>
+ <para>
+ The following example shows how a variable can be set using the sysconfig
+ resource.
+ </para>
+ &example.sysconfig;
+ </section>
+

Added: trunk/autoinstallation/doc/xml/UsersSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/UsersSection.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/UsersSection.xml (added)
+++ trunk/autoinstallation/doc/xml/UsersSection.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,55 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+ <section id="Configuration.Security.users">
+ <title>
+ Users
+ </title>
+ <para>
+ The root user and at least one normal user can be added during install
+ using data supplied in the control file. User data and passwords
+ (encrypted or in clear text) are part of the
<emphasis>configure</emphasis> resource in the
+ control file.
+ </para>
+ <para>
+ At least the root user should be configured during
+ auto-installation, which will insure you will be able to login after
+ installation is finished and of course it will insure nobody else can
login
+ into the system (in case the password is not set).
+ </para>
+ <para>The two users in the following example are added during system
+ configuration.</para>
+
+ <example>
+ <title>
+ User configuration
+ </title>
+ <screen>
+ <xi:include href="examples/example.users.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+ <para>
+ The last example shows the minimal information required for adding
+ users. More options are available for a more customized user account
+ management. The data in <filename>/etc/default/useradd</filename> is
+ used to determine the home directory of the user to be created in
+ addition to other parameters.
+ </para>
+ </section>
+

Added: trunk/autoinstallation/doc/xml/X11Section.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/X11Section.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/X11Section.xml (added)
+++ trunk/autoinstallation/doc/xml/X11Section.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,48 @@
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+]>
+ <section id="Configuration.X11">
+ <title>
+ Monitor and X11 Configuration
+ </title>
+ <note>
+ <para>
+ Since openSUSE 11.2 there is not AutoYaST client for X11
configuration anymore. You can still have the X11 section in your profile but
+ it will be ignored.
+ </para>
+ <para>
+ SLES11 SP1 still has a X11 client.
+ </para>
+ </note>
+ <para>
+ FIXME
+ </para>
+
+ <example>
+ <title>
+ X11 and Monitor configuration (deprecated since openSUSE 11.2)
+ </title>
+ <screen>
+<xi:include href="examples/example.x11.xml" parse="text"
+ xmlns:xi="http://www.w3.org/2001/XInclude"/>
+ </screen>
+ </example>
+
+
+ </section>
+

Added: trunk/autoinstallation/doc/xml/advanced.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/advanced.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/advanced.xml (added)
+++ trunk/autoinstallation/doc/xml/advanced.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,14 @@
+ <chapter id="advanced">
+ <title>Advanced topics</title>
+ &multiple;
+ &linuxrc
+
+
+</chapter>
+
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast2.xml" "book" "chapter")
+ End:
+ -->
\ No newline at end of file

Added: trunk/autoinstallation/doc/xml/appendix-rules.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/appendix-rules.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/appendix-rules.xml (added)
+++ trunk/autoinstallation/doc/xml/appendix-rules.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,16 @@
+
+<appendix id="handlingrules">
+ <title>Handling Rules</title>
+
+ <para>
+ The following figure illustrates how rules are handled and the
processes of retrieval and merge.
+ </para>
+
+
+ <figure id="rulesflow">
+ <title id="rulesflow.title" >Rules Retrieval Process</title>
+ <mediaobject>&RulesFlow;</mediaobject>
+ </figure>
+</appendix>
+
+

Added: trunk/autoinstallation/doc/xml/appendix2.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/appendix2.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/appendix2.xml (added)
+++ trunk/autoinstallation/doc/xml/appendix2.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,71 @@
+<appendix>
+ <title>Advanced Network Installations</title>
+ <sect1>
+ <title> Creating Boot Floppies for Compute Nodes</title>
+
+
+ <para>
+ To create Etherboot floppies, go to the web site <ulink
+ url="http://rom-o-matic.net/";>http://rom-o-matic.net/</ulink>, which
+ can be used to dynamically generate Etherboot ROM images.
+ </para>
+
+ <para>To create a boot floppy on a Linux system, as root, use the
following command line:</para>
+
+
+
+
+</sect1>
+ <sect1>
+ <title>Collecting MAC Addresses</title>
+
+ <para>
+ To configure multiple clients (i.e. when configuring a cluster), it is
required to have the Ethernet MAC address
+ of every node in your cluster.
+ </para>
+
+ <para>
+ To collect the Ethernet MAC addresses of the clients, follow these
steps:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para> Power off all of the compute nodes.</para></listitem>
+ <listitem>
+ <para> Boot the first client with an etherboot floppy.
+ </para></listitem>
+ <listitem>
+ <para> Watch the clientdisplay for a message like
+</para>
+
+<screen>
+Probing...[EEPRO100] Ethernet addr: 00:50:ba:3f:b5:d5
+</screen>
+ <para>
+ Write down the MAC address, which is the numeric string starting with
+ 00:50 (only an example).
+ </para>
+ <para>Alternativly, you can find the MAC address in the system log
+ files where you are running a &dhcp; server, for example:</para>
+
+ <screen>
+Feb 27 00:43:22 avicenna dhcpd: DHCPDISCOVER from 00:50:ba:3f:b5:d5 via eth0
+Feb 27 00:43:22 avicenna dhcpd: DHCPOFFER on 192.168.1.5 to 00:50:ba:3f:b5:d5
via eth0
+Feb 27 00:43:22 avicenna dhcpd: DHCPREQUEST for 192.168.1.5 (192.168.1.1) from
00:50:ba:3f:b5:d5 via eth0
+Feb 27 00:43:22 avicenna dhcpd: DHCPACK on 192.168.1.5 to 00:50:ba:3f:b5:d5
via eth0
+
+</screen>
+</listitem>
+ Power down client.
+ Repeat steps 2 through 4 for each compute node.
+ </orderedlist>
+
+</sect1>
+
+ </appendix>
+
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast2.xml" "book" "appendix")
+ End:
+ -->
\ No newline at end of file

Added: trunk/autoinstallation/doc/xml/autoyast.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/autoyast.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/autoyast.xml (added)
+++ trunk/autoinstallation/doc/xml/autoyast.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,106 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[
+
+<!ENTITY Profile SYSTEM "Profile.xml">
+
+<!ENTITY Introduction SYSTEM "Introduction.xml">
+
+<!ENTITY CreateProfile SYSTEM "CreateProfile.xml">
+<!ENTITY PartitioningSection SYSTEM "PartitioningSection.xml">
+<!ENTITY NetworkInstallation SYSTEM "NetworkInstallation.xml">
+<!ENTITY date SYSTEM "systemdate">
+
+<!ENTITY Installation SYSTEM "Installation.xml">
+<!ENTITY RulesAndClasses SYSTEM "RulesAndClasses.xml">
+
+
+<!ENTITY % images SYSTEM "images.ent">
+%images;
+
+<!ENTITY % entities SYSTEM "entities/en.ent">
+%entities;
+
+
+
+<!-- Create Profile -->
+<!ENTITY CreateProfileDetails SYSTEM "CreateProfileDetails.xml">
+<!ENTITY Advanced SYSTEM "advanced.xml">
+
+
+<!-- Examples -->
+<!ENTITY % examples SYSTEM "examples.ent">
+%examples;
+
+<!-- components -->
+<!ENTITY % components SYSTEM "components.ent">
+%components;
+
+<!ENTITY appendix-linuxrc SYSTEM "linuxrc.xml">
+<!ENTITY appendix-rules SYSTEM "appendix-rules.xml">
+]>
+
+<book>
+
+ <bookinfo>
+ <title>AutoYaST</title>
+ <subtitle>Automatic Linux Installation and Configuration with
+ YaST2</subtitle>
+ <authorgroup>
+ <author>
+ <firstname>Anas</firstname>
+ <surname>Nashif</surname>
+ <affiliation>
+ <jobtitle>Concepts, Development and Documentation</jobtitle>
+ <orgname></orgname>
+ </affiliation>
+ </author>
+ <author>
+ <firstname>Uwe</firstname>
+ <surname>Gansert</surname>
+ <affiliation>
+ <jobtitle>Concepts, Development and Documentation</jobtitle>
+ <orgname></orgname>
+ </affiliation>
+ </author>
+ </authorgroup>
+ <corpauthor>SUSE Linux Products GmbH</corpauthor>
+ <copyright>
+ <year>2004</year>
+ <holder> &company-suse; Linux AG</holder>
+ </copyright>
+ </bookinfo>
+
+
+ <toc>
+ </toc>
+
+ &Introduction;
+
+ &Profile;
+ &CreateProfile;
+ &CreateProfileDetails;
+
+
+ &NetworkInstallation;
+ &RulesAndClasses;
+ &Installation;
+
+
+ &appendix-rules;
+ &appendix-linuxrc;
+ &Elements;
+
+</book>
+
+
+
+
+
+
+
+
+
+
+
+

Added: trunk/autoinstallation/doc/xml/bin
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/bin?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/bin (added)
+++ trunk/autoinstallation/doc/xml/bin Mon Aug 8 14:12:13 2011
@@ -0,0 +1 @@
+link ../bin
\ No newline at end of file

Added: trunk/autoinstallation/doc/xml/catalog.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/catalog.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/catalog.xml (added)
+++ trunk/autoinstallation/doc/xml/catalog.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,17 @@
+<?xml version="1.0"?>
+<!DOCTYPE catalog
+ PUBLIC "-//OASIS/DTD Entity Resolution XML Catalog V1.0//EN"
+ "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd";>
+
+<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog">
+ <uri
+ name="docbook.xsl"
+
uri="file:///usr/share/xml/docbook/stylesheet/nwalsh/current/html/docbook.xsl"/>
+ <uri
+ name="docbook-chunk.xsl"
+
uri="file:///usr/share/xml/docbook/stylesheet/nwalsh/current/html/chunk.xsl"/>
+ <uri
+ name="docbook-fo.xsl"
+
uri="file:///usr/share/xml/docbook/stylesheet/nwalsh/current/fo/docbook.xsl"/>
+
+</catalog>

Added: trunk/autoinstallation/doc/xml/creating_autoyast2_modules.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/creating_autoyast2_modules.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/creating_autoyast2_modules.xml (added)
+++ trunk/autoinstallation/doc/xml/creating_autoyast2_modules.xml Mon Aug 8
14:12:13 2011
@@ -0,0 +1,797 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd";[]>
+
+ <article>
+ <articleinfo>
+ <title>AutoYaST Configuration Management System</title>
+ <author>
+ <firstname>Anas</firstname>
+ <surname>Nashif</surname>
+ </author>
+ <author>
+ <firstname>Uwe</firstname>
+ <surname>Gansert</surname>
+ </author>
+ </articleinfo>
+ <section>
+ <title>Introduction</title>
+ <para>
+ The plugin-like design has the following advantages:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ New Run-time module can be integrated automatically in AutoYaST,
+ thus new features in YaST2 mean new features in the auto-installer.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Only installed run-time modules are offered and used to autoinstall
+ the system. This allows the integration of speciality run-time
modules which are
+ only present on business products for example.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Code which is relevant to one run-time configuration module is kept
in one place
+ instead of maintaining it in different modules.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ <section>
+ <title>The run-time module interface in AutoYaST</title>
+ <para>The new interface (AKA _auto.ycp client) is similar to the proposal
+ structure and consists of functions that can be accessed using
arguments. All the dialog code has been moved to
+ autoyast to simplify the interface and to provide a common user
interface for
+ all modules appearing in the autoyast configuration system.
+ </para>
+ <para>
+ The interface of a run-time configuration module in AutoYaST has the
follwoing
+ components:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>Summary Area,</emphasis>: Contains a summary of the
consifguration with the
+ values if available. If values where not configured, the phrase
+ <emphasis>'Not configured yet'</emphasis> is used, which is available
from the summary module.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Configuration Button</emphasis>: A button which calls the
module in auto mode
+ (<emphasis>&lt;module name&gt;_auto.ycp</emphasis>).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Reset Button</emphasis>: A button for resetting the
+ configuration data. This will delete only data in the running module.
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>
+ The summary area is filled with data from the
<emphasis>Summary</emphasis> function in the
+ module controling the configuration. (i.e
+ <emphasis>NIS::Summary()</emphasis> in the NIS package).
+ </para>
+ </section>
+ <section>
+ <title>Run-time modules in <emphasis>auto</emphasis> mode</title>
+ <para>
+ The &lt;module name&gt;_auto.ycp client accepts 2 arguments:
+ </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ Function
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Configuration Data
+ </para>
+ </listitem>
+ </itemizedlist>
+ <para>The following functions are needed to make any module work in
AutoYaST:</para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis>Import:</emphasis></para>
+ <para>
+ Import existing data into the module, usually done only once at the
beginning.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Summary:</emphasis></para>
+ <para>
+ To provide a brief summary of the configuration.
+ Calls &gt;Module&lt;::Summary()
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Reset:</emphasis></para>
+ <para>
+ Resets the configuration. It returns empty values but it also can
return
+ default values, depending on the module.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Change:</emphasis></para>
+ <para>
+ This function starts the widget sequence
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Write</emphasis></para>
+ <para>
+ Write the configuration without displaying any widgets and popups and
+ without restarting any services etc.
+ Calls &lt;Module&gt;::Write (and sets &lt;Module&gt;::write_only true)
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Export:</emphasis></para>
+ <para>
+ Returns the current configuration
+ Calls &lt;Module&gt;::Export
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>Packages:</emphasis></para>
+ <para>
+ Returns a map with two key/value pairs. First key is
+ <emphasis>install</emphasis> which has a list as the value. the list
+ contains packages that are needed for the service configured by the
+ module to work. This can be a static list of packages or a dynamic
+ list depending on the configuration. The second key is
+ <emphasis>remove</emphasis> which contains packages that should be
+ removed to avoid conflicts with other packages. the packages in
+ <emphasis>remove</emphasis> are normally determined dynamically,
+ depending on the configuration.
+
+ </para>
+ <para>
+ The function can either return a map directly or it can call a module
+ function &lt;Module&gt;::AutoPackages().
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <para>
+ The following example shows &lt;module name&gt;_auto.ycp with the changes
+ needed for the new behaviour.
+ </para>
+ <example>
+ <title>XXpkgXX_auto.ycp (XXpkgXX = module name)</title>
+ <programlisting>
+ <![CDATA[
+ /**
+ * @param function to execute
+ * @param map/list of XXpkgXX settings
+ * @return map edited settings,
+ * Summary or boolean on success depending on called function
+ * @example map mm = $[ "FAIL_DELAY" : "77" ];
+ * @example map ret = WFM::CallFunction ("XXpkgXX_auto", [ "Summary", mm
]);
+ */
+
+ {
+
+ textdomain "XXpkgXX";
+
+ y2milestone("----------------------------------------");
+ y2milestone("XXPkgXX auto started");
+
+ import "XXPkgXX";
+ include "XXpkgXX/wizards.ycp";
+
+ any ret = nil;
+ string func = "";
+ map param = $[];
+
+ /* Check arguments */
+ if(size(Args()) > 0 && is(Args(0), string)) {
+ func = WFM::Args(0);
+ if(size(Args()) > 1 && is(Args(1), map))
+ param = WFM::Args(1);
+ }
+ y2debug("func=%1", func);
+ y2debug("param=%1", param);
+
+ /* Create a summary*/
+ if(func == "Summary") {
+ ret = select(XXPkgXX::Summary(), 0, "");
+ }
+ else if (func == "Import") {
+ ret = XXPkgXX::Import($[]);
+ return ret ;
+ }
+
+ /* Reset configuration */
+ else if (func == "Reset") {
+ XXPkgXX::Import($[]);
+ ret = $[];
+ }
+ /* Change configuration (run AutoSequence) */
+ else if (func == "Change") {
+ ret = XXPkgXXAutoSequence();
+ }
+ /* Return required packages */
+ else if (func == "Packages") {
+ ret = XXPkgXX::AutoPackags();
+ }
+ /* Return actual state */
+ else if (func == "Export") {
+ ret = XXPkgXX::Export();
+ }
+ /* Write given settings */
+ else if (func == "Write") {
+ import "Progress";
+ XXPkgXX::write_only = true;
+ Progress::off();
+ ret = XXPkgXX::Write();
+ Progress::on();
+ return ret;
+ }
+ /* Unknown function */
+ else {
+ y2error("Unknown function: %1", func);
+ ret = false;
+ }
+
+ y2debug("ret=%1", ret);
+ y2milestone("XXPkgXX auto finished");
+ y2milestone("----------------------------------------");
+
+ return ret;
+
+ /* EOF */
+ }
+
+
+
+
+ ]]>
+ </programlisting>
+ </example>
+ </section>
+ <section>
+ <title>Module functions needed for Auto-Install</title>
+ <para>The follwoing is the list of function that should be available with
+ the modules to provide the functionality needed in the AutoYaST.
+ </para>
+ <refentry>
+ <refnamediv>
+ <refname>AutoPackages()</refname>
+ <refpurpose>Return needed packages for module to work</refpurpose>
+ </refnamediv>
+ <refsect1>
+ <title>Description</title>
+ <para>
+ This function return a map of lists which contain packages to be
+ installed or removed during installation (second stage).
+ </para>
+
+ </refsect1>
+
+ <refsect1>
+ <title>Returns</title>
+ <para>
+ For example, the function can return the following structure:
+ </para>
+ <screen>
+ $[
+ "install": ["pkg1", "pkg2"],
+ "remove": ["pkg3"]
+ ]
+ </screen>
+ </refsect1>
+ </refentry>
+ <refentry>
+ <refnamediv>
+ <refname>Import()</refname>
+ <refpurpose>Imports settings from arguments</refpurpose>
+ </refnamediv>
+ <refsect1>
+ <title>Description</title>
+ <para>This function imports settings from arguments and sets the module
+ variables. The <emphasis>Import</emphasis> function should bring the
+ module to a state where the data imported is enough for the module to
+ write (See Write()) a usable configuration.
+ </para>
+
+ </refsect1>
+
+ <refsect1>
+ <title>Returns</title>
+ <para>Import() return false if some of the required keys are missing in
the
+ imported map. If the imported data is empty, it returns true and
+ starts the module using default values.
+ </para>
+ </refsect1>
+ </refentry>
+ <refentry>
+ <refnamediv>
+ <refname>Export()</refname>
+ <refpurpose>Exports configured data to calling module</refpurpose>
+ </refnamediv>
+ <refsect1>
+ <title>Description</title>
+ <para>Exports configured data to calling module. This function also
+ converts the internal variables to unique and human readable
+ variables which can be used in the control file needed for the
+ auto-installation. It is not allowed to export
<emphasis>maps</emphasis> with configured
+ data as the keys. Configured data must be the value of a
variable.</para>
+ </refsect1>
+ <refsect1>
+ <title>Example</title>
+ <example>
+ <title>Export()</title>
+ <programlisting>
+ <![CDATA[
+ global define map Export () ``{
+ return $[
+ "start_nis": start,
+ "nis_servers": servers,
+ "nis_domain": domain,
+ "start_autofs": _start_autofs,
+ ];
+ }
+ ]]>
+ </programlisting>
+ </example>
+ </refsect1>
+ <refsect1>
+ <title>Returns</title>
+ <para>This function returns a map of the configuration data.</para>
+ </refsect1>
+ </refentry>
+
+ <refentry>
+ <refnamediv>
+ <refname>Write()</refname>
+ <refpurpose>Write or commit configured or imported data</refpurpose>
+ </refnamediv>
+ <refsect1>
+ <title>Description</title>
+ <para>Commit configured data. This function is also used in normal
+ operation mode and should not be used to write configuration in
+ auto-installation mode. Instead, use<emphasis> WriteOnly()</emphasis>
+ or set the global variable <emphasis>write_only</emphasis> to true
+ before writing.
+ </para>
+ <para>
+ during the write process, check for the global boolean variable
+ <emphasis>write_only</emphasis> which should be used to prevent the
+ module from restarting services and showing GUI components during
+ autoinstallation which might interfere with the installation widgets.
+ </para>
+
+ </refsect1>
+ </refentry>
+
+ </section>
+ <section>
+ <title>Configuration file</title>
+
+ <para>
+ When AutoYaST is invoked, it checks for the desktop files in
+ <filename>/usr/share/applications/YaST2</filename> and evaluates them to
+ later include them in the configuration interface. AutoYaST uses the
same configuration file used for the YaST2
+ Control Center with some additional enhancements.
+ </para>
+ <para>
+ The following is an example of the configuration file for the NIS module:
+ </para>
+ <example>
+ <title>Auto-Install Configuration file for NIS</title>
+ <programlisting>
+[Desktop Entry]
+Type=Application
+Categories=Qt;X-SuSE-YaST;X-SuSE-YaST-Net_advanced;
+
+X-KDE-ModuleType=Library
+X-KDE-RootOnly=true
+X-KDE-HasReadOnlyMode=true
+X-KDE-Library=yast2
+X-SuSE-YaST-Call=nis
+
+X-SuSE-YaST-Group=Net_advanced
+X-SuSE-YaST-Argument=
+X-SuSE-YaST-RootOnly=true
+X-SuSE-YaST-AutoInst=all
+X-SuSE-YaST-Geometry=
+X-SuSE-YaST-SortKey=
+X-SuSE-YaST-AutoInstClonable=true
+X-SuSE-YaST-AutoLogResource=true
+
+Icon=nis_client
+Exec=/sbin/yast2 nis
+
+Name=NIS Client
+GenericName=Configure NIS client
+
+
+ </programlisting>
+ </example>
+ <para>In addition to the keywords from the last example, AutoYaST also
evaluates
+ the following keywords:</para>
+
+ <itemizedlist>
+ <!-- <title>Desktop file Keywords</title> -->
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoInst</emphasis>
+ - Is the module compatible with the
+ AutoYaST and can Import/Export configurations?</para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para><emphasis>all</emphasis>: Full auto-installation
support,
+ including the AutoYaST interface and writing configurations
+ during autoinstall. </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>write</emphasis>: Write only support. No
+ integration into AutoYaST interface. </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>configure</emphasis>: Configuration only
support.
+ Normally used only with parts related to installation like
+ partitioning and general options which have no run-time
module
+ with support for auto-installation. Data is written using
the
+ common installation process and modules available in
YaST2</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoInstPath</emphasis>
+ - Path in the control file</para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para>configure or install: All run-time configuration
modules are
+ contained in the <emphasis>configure</emphasis> resource.
Only
+ configuration data directly touching the installation of a
system are
+ contained in the <emphasis>install</emphasis>
resource.</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoInstClient</emphasis>
+ - Name of the client to call</para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para>Name of the client to be called by AutoYaST</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Default Value</title>
+ <listitem>
+ <para>&lt;module name&gt;_auto</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoInstDataType</emphasis>
+ - Data type of configuration section</para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para><emphasis>map</emphasis> or
<emphasis>list</emphasis></para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Default Value</title>
+ <listitem>
+ <para>map</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoInstResource</emphasis>
+ - Name of the resource in the Profile</para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para>string</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Default Value</title>
+ <listitem>
+ <para>(empty)</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoInstRequires</emphasis>
+ - What modules are required before this module is run. </para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para>comma delimited list of required modules</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Default Value</title>
+ <listitem>
+ <para>(empty list)</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+<!-- merging stuff -->
+
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoInstMerge</emphasis>
+ - Multiple sections in the profile can be handled by one
module</para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para>comma delimited list of sections to merge
+ (see also X-SuSE-YaST-AutoInstMergeTypes)</para>
+ <para>The Users module for example handles also
+ groups and user_defaults.</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Default Value</title>
+ <listitem>
+ <para>(empty)</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoInstMergeTypes</emphasis>
+ - Which datatypes are the section of that will be merged to be
+ handled by one module</para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para>comma delimited list of datatypes (list or map) for
+ the sections from X-SuSE-YaST-AutoInstMerge</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Default Value</title>
+ <listitem>
+ <para>(empty)</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+<!-- clone stuff -->
+
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoInstClonable</emphasis>
+ - is this module able to clone the actual system</para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para>a boolean (true,false)</para>
+ <para>If this is true, the module will appear in the list of
+ modules you can choose from during the cloning of the actual
+ system. Your module will Read() and Export() it's data from
+ the actual system then.</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Default Value</title>
+ <listitem>
+ <para>false</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+<!-- schema stuff -->
+
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoInstSchema</emphasis>
+ - base name of schema file, including the rnc
+ extension (Relax NG compact syntax)</para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para>string</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Default Value</title>
+ <listitem>
+ <para>(empty)</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoInstOptional</emphasis>
+ - is the element optional in the schema</para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para>a boolean (true,false)</para>
+ <para>Does this element has to appear in the profile?
+ Unless you have a very basic module, this is always
+ true.</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Default Value</title>
+ <listitem>
+ <para>true</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+ <listitem>
+ <para><emphasis>X-SuSE-YaST-AutoLogResource</emphasis>
+ - is the resource of your modul allowed to be logged (since
SLES10SP1/10.2)</para>
+ <itemizedlist>
+ <title>Values</title>
+ <listitem>
+ <para>a boolean (true,false)</para>
+ <para>Do you allow autoyast to log the data of your
resource into the
+ logfile? The default is true but if you have sensible data
like
+ passwords, you might want to set this to false. That can
always be
+ overridden by Y2DEBUG=1</para>
+ </listitem>
+ </itemizedlist>
+ <itemizedlist>
+ <title>Default Value</title>
+ <listitem>
+ <para>true</para>
+ </listitem>
+ </itemizedlist>
+ <para>&nbsp;</para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+ <section>
+ <title>Conventions for module Writers</title>
+ <section>
+ <title>Exported Data</title>
+ <itemizedlist>
+ <listitem>
+ <para><emphasis>Type of exported data</emphasis>: </para>
+ <para>Modules should only export data which is normally selected or
+ entered by the user in normal module operation. No computed or
+ automatically probed data should be exported.</para>
+ </listitem>
+ <listitem>
+ <para><emphasis>Use Namespaces</emphasis></para>
+ <para>Exported variables should have a unique name when possible and
+ when general terminology is being used. To avoid conflicts and
confusion,
+ use a name space identifier with common words. For example, if a
+ module should export the variable name
+ <emphasis>options</emphasis>, it is better to export<emphasis>
&lt;module
+ name&gt;.options</emphasis> to avoid confusion with other modules
using
+ <emphasis>options</emphasis>, which is very common in
configurations.
+ </para>
+ </listitem>
+ <listitem>
+ <para><emphasis>Lower case variables</emphasis></para>
+ <para>To have a common and unified look of the control file, please
+ use lower case variables when exporting the configuration
data.</para>
+ </listitem>
+ <listitem>
+ <para>The structure of the exported data should be readable and not
+ unnecessarly complex.</para>
+ </listitem>
+ <listitem>
+ <para>Avoid using configuration data as the key in a map key/value
+ pair. The key of the pair must always contain the variable name,
+ rather than it's contents</para>
+ </listitem>
+ </itemizedlist>
+
+ </section>
+
+ <section>
+ <title>YaST2 Module Types</title>
+ <para>
+ YaST2 configuration modules and in relation with AutoYaST can be put
+ into three categories:
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>Simple modules which mormally only change sysconfig variable
+ and have simple configuration data structure. (i.e. mail, nis,
+ ldap, etc.)
+ </para>
+ <para>
+ This category needs no special attention and is easy to integrate
with
+ the AutoYaST.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Simple modules dealing with hardware configuration (i.e.
network,
+ sound, printer etc.)
+ </para>
+ <para>
+ These modules need to be able to
+ read and autodetect hardware data during installation if no hardware
+ data is specified in the control file. The behaviour of this type of
+ modules up to 8.1 was to import data and write it wihtout actually
+ reading anything from the system.
+ </para>
+ <para>
+ An additional step has to be added between the import and the
+ write, where hardware data is read and imported into the module. In
+ some case this is simply done by calling the Read function the
module.
+ </para>
+ </listitem>
+ <listitem>
+ <para>Modules for management of complex configuration files
+ (i.e. inetd, sysconfig, runlevel, users, bootloader)
+ </para>
+ <para>
+ This class of modules is much more complex and requires adaptation
+ and special attention. AutoYaST expects that only new and modified
+ entries will be exported and not the whole configuration tree. For
+ example when a user enables a service in inetd, only this service
+ is exported. A user should be able to add new services which are
+ not available in the default configuration file too.
+ </para>
+ </listitem>
+ </orderedlist>
+ </section>
+ <section>
+ <title>Module behaviour</title>
+ <para>
+ In configuration mode for auto-installation, modules <emphasis>should
+ not</emphasis>(configuration system is the machine where the control
+ file is being created):
+ <itemizedlist>
+ <listitem>
+ <para>Read any data from the configuration system</para>
+ </listitem>
+ <listitem>
+ <para>Probe or detect hardware on the configuration system</para>
+ </listitem>
+ <listitem>
+ <para>Change configuration data on the configuration system</para>
+ </listitem>
+ <listitem>
+ <para>Offer a link to other modules (i.e. calling the NIS module
+ from the users module)</para>
+ </listitem>
+
+ <listitem>
+ <para>Check if a needed package is installed on the configuration
system.</para>
+ </listitem>
+
+ </itemizedlist>
+ </para>
+ </section>
+ </section>
+ </article>
+

Added: trunk/autoinstallation/doc/xml/entities
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/entities?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/entities (added)
+++ trunk/autoinstallation/doc/xml/entities Mon Aug 8 14:12:13 2011
@@ -0,0 +1 @@
+link ../entities
\ No newline at end of file

Added: trunk/autoinstallation/doc/xml/examples
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/examples?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/examples (added)
+++ trunk/autoinstallation/doc/xml/examples Mon Aug 8 14:12:13 2011
@@ -0,0 +1 @@
+link ../examples
\ No newline at end of file

Added: trunk/autoinstallation/doc/xml/images
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/images?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/images (added)
+++ trunk/autoinstallation/doc/xml/images Mon Aug 8 14:12:13 2011
@@ -0,0 +1 @@
+link ../images
\ No newline at end of file

Added: trunk/autoinstallation/doc/xml/linuxrc.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/linuxrc.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/linuxrc.xml (added)
+++ trunk/autoinstallation/doc/xml/linuxrc.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,187 @@
+
+<appendix id="appendix.linuxrc">
+
+
+ <title id="appendix.linuxrc.title">Advanced Linuxrc Options</title>
+
+
+ <para>
+
+ Linuxrc is a program used for setting up the kernel for installation
+ purposes. It allows the user to load modules, start an installed system, a
+ rescue system or an installation via YaST.
+ </para><para>
+ Linuxrc is designed to be as small as possible. Therefore, all needed
+ programs are linked directly into one binary. So there is no need for
shared
+ libraries in the initdisk.
+ </para>
+ <note>
+ <para>
+ If you run Linuxrc on an installed system, it will work slightly
+ different as it tries not to destroy your installation. As a consequence
you
+ cannot test all features this way.
+ </para>
+ </note>
+
+ <section>
+ <title>Passing parameters to Linuxrc</title>
+ <para>
+ Unless Linuxrc is in manual mode it will look for an 'info' file in these
+ locations: first <filename>/info</filename> on the floppy disk and if
that does not
+ exsist for <filename>/info</filename> in the initrd. After that it
parses the kernel
+ command line for parameters. You may change the 'info' file Linuxrc reads
+ using the <filename>info</filename> command line parameter. If you don't
want
+ Linuxrc to read the kernel command line (say, because you need to give a
+ kernel parameter that accidentally is recognized by Linuxrc, too), use
+ <emphasis>linuxrc=nocmdline</emphasis>.
+ </para>
+ <para>
+ <note>
+ <title>Change starting from SUSE Linux 10.2</title>
+ <para>
+ The info file is no longer implicitly read. You have to make it
+ explicit, like 'info=floppy:/info'.
+ </para>
+ </note>
+ </para>
+ <para>
+ Independent of the above, Linuxrc will always look for and parse a file
+ <filename>/linuxrc.config</filename>. You can use this file to change
default
+ values, if you need to. But in general, use the
<filename>info</filename> file
+ instead. Note that <filename>/linuxrc.config</filename> is read before
any 'info'
+ file and even in manual mode.
+
+ </para>
+ </section>
+ <section id="info_file_format">
+ <title>'info' file format</title>
+ <para>
+ Lines starting with '<emphasis>#</emphasis>' are comments, valid entries
are of the form
+ <screen>
+ key: value
+ </screen>
+ Note that <emphasis>value</emphasis> extends to the end of the line and
so may contain spaces.
+ <emphasis>key</emphasis> is matched case insensitive.
+ </para>
+ <para>
+ You can use the same key - value pairs on the kernel command line using
the syntax
+ <interface>
+ key=value
+ </interface>
+ Lines that don't have the form described above are ignored.
+ </para>
+ <para>
+ Valid keys are (values given are just examples)
+ </para>
+
+ <table frame='top'>
+ <title>Advanced <command>linuxrc</command> keywords</title>
+ <tgroup cols='2'>
+ <thead>
+ <row>
+ <entry>Keyword/Value</entry>
+ <entry>Description</entry>
+ </row>
+ </thead>
+
+
+ <tbody>
+ <row><entry>Language: de_DE</entry><entry> set the
language</entry></row>
+ <row><entry>Keytable: de-lat1-nd</entry><entry> load this
keytable</entry></row>
+ <row><entry>Display: Color|Mono|Alt</entry><entry> set the menu
color scheme</entry></row>
+ <row><entry>Install: nfs://server/install/8.0-i386</entry><entry>
install
+ via NFS from <emphasis>server</emphasis> (note: you can give
username, password etc. in the URL, too) </entry></row>
+ <row><entry>InstMode: cd|hd|nfs|smb|ftp|http|tftp</entry><entry> set
installation mode</entry></row>
+ <row><entry>HostIP: 10.10.0.2</entry><entry> the client ip
address</entry></row>
+ <row><entry>Netmask: 255.255.0.0</entry><entry> network
mask</entry></row>
+ <row><entry>Gateway: 10.10.0.1</entry><entry> gateway</entry></row>
+ <row><entry>Server: 10.10.0.1</entry><entry> installation server
address</entry></row>
+ <row><entry>Nameserver: 10.10.0.1</entry><entry>
nameserver</entry></row>
+ <row><entry>Proxy: 10.10.0.1</entry><entry> proxy (either ftp or
http)</entry></row>
+ <row><entry>ProxyPort: 10.10.0.1</entry><entry> proxy
port</entry></row>
+ <row><entry>Partition: hda1</entry><entry> partition with install
sources for hard disk install</entry></row>
+ <row><entry>Serverdir: /install/8.0-i386</entry><entry> base
directory of the installation sources</entry></row>
+ <row><entry>Netdevice: eth0</entry><entry> network interface to
use</entry></row>
+ <row><entry>BOOTPWait: 5</entry><entry> sleep 5 seconds between
network activation and starting bootp</entry></row>
+ <row><entry>BOOTPTimeout: 10</entry><entry> 10 seconds timeout for
BOOTP requests</entry></row>
+ <row><entry>DHCPTimeout: 60</entry><entry> 60 seconds timeout for
DHCP requests</entry></row>
+ <row><entry>TFTPTimeout: 10</entry><entry> 10 seconds timeout for
TFTP connection</entry></row>
+ <row><entry>ForceRootimage: 0|1</entry><entry> load the installation
system into ramdisk</entry></row>
+ <row><entry>Textmode: 0|1</entry><entry> start YaST in text
mode</entry></row>
+ <row><entry>Username: name</entry><entry> set user name (e.g. for
FTP install)</entry></row>
+ <row><entry>Password: password</entry><entry> set password (e.g. for
FTP install)</entry></row>
+ <row><entry>WorkDomain: domain</entry><entry> set work domain for
SMB install</entry></row>
+ <row><entry>ForceInsmod: 0|1</entry><entry> use
'<emphasis>-f</emphasis>' option when running
<emphasis>insmod</emphasis></entry></row>
+ <row><entry>DHCP: 0|1</entry><entry> start DHCP daemon
<emphasis>now</emphasis>, but see <emphasis>UseDHCP</emphasis></entry></row>
+ <row><entry>UseDHCP: 0|1</entry><entry> use DHCP instead of BOOTP
(DHCP is default)</entry></row>
+ <row><entry>MemLimit: 10000</entry><entry> ask for swap if free
memory drops below 10000 kB</entry></row>
+ <row><entry>MemYaST: 20000</entry><entry> run YaST in text mode if
free memory is below 20000 kB</entry></row>
+ <row><entry>MemYaSTText: 10000</entry><entry> ask for swap before
starting YaST if free memory is below 10000 kB</entry></row>
+ <row><entry>MemModules: 20000</entry><entry> delete all modules
before starting YaST if free memory is below 20000 kB</entry></row>
+ <row><entry>MemLoadImage: 50000</entry><entry> load installation
system into ramdisk if free memory is above 50000 kB</entry></row>
+ <row><entry>Manual: 0|1</entry><entry> start Linuxrc in manual
mode</entry></row>
+ <row><entry>NoPCMCIA: 0|1</entry><entry> don't start card
manager</entry></row>
+ <row><entry>Domain: zap.de</entry><entry> set domain name (used for
name server lookups)</entry></row>
+ <row><entry>RootImage: /suse/images/root</entry><entry> installation
system image</entry></row>
+ <row><entry>RescueImage: /suse/images/rescue</entry><entry> rescue
system image</entry></row>
+ <row><entry>InstallDir: /suse/inst-sys</entry><entry> installation
system</entry></row>
+ <row><entry>Rescue: 1|nfs://server/dir</entry><entry> load rescue
system; the URL variant specifies the location of the rescue image
explicitly</entry></row>
+ <row><entry>AutoYaST: ftp://autoyastfile</entry><entry> location of
autoinstall file; activates autoinstall mode</entry></row>
+ <row><entry>VNC: 0|1</entry><entry> setup VNC server</entry></row>
+ <row><entry>VNCPassword: password</entry><entry> sets VNC server
password</entry></row>
+ <row><entry>UseSSH: 0|1</entry><entry> setup SSH
server</entry></row>
+ <row><entry>SSHPassword: password</entry><entry> sets SSH server
password (this will not be the final root password!)</entry></row>
+ <row><entry>AddSwap: 0|3|/dev/hda5</entry><entry> if 0, do never ask
for swap; if the argument is a positive number <emphasis>n</emphasis>,
+ activate the <emphasis>n</emphasis>'th swap partition; is the
argument is a partition name, activate this swap partition</entry></row>
+ <row><entry>Exec: command</entry><entry> run
<emphasis>command</emphasis></entry></row>
+ <row><entry>USBWait: 4</entry><entry> wait 4 seconds after loading
USB modules</entry></row>
+ <row><entry>Insmod: module params</entry><entry> load this
module</entry></row>
+ <row><entry>Loghost: 10.10.0.22</entry><entry>Enable remove logging
+ via syslog</entry></row>
+ <row><entry>y2confirm</entry><entry>overrides the confirm parameter
in a profile and pops up the confirm proposal (available since SUSE Linux 10.1
/ SLES10)</entry></row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ </section>
+ <section>
+ <title>Advanced Network Setup</title>
+ <para>The <emphasis>netsetup</emphasis> keyword allows advanced network
+ configurations and enables dialogs to setup the network where
required.</para>
+ <itemizedlist>
+ <listitem>
+ <para>netsetup=1</para>
+ <para>the normal network setup questions</para>
+ </listitem>
+ <listitem>
+ <para>netsetup=xxx,yyy</para>
+ <para>just xxx and yyy</para>
+ </listitem>
+ <listitem>
+ <para> netsetup=+xxx,-yyy</para>
+ <para>default, additionally xxx, but not yyy</para>
+ </listitem>
+ </itemizedlist>
+ <para>
+
+ <emphasis>xxx</emphasis> could have the following values: dhcp, hostip,
+ gateway, netmask, nameserver. nameserverN asks for N nameservers
+ (max. 4).
+ </para>
+ <para>For example, the following can be entered on the command line:</para>
+
+ <screen>
+
+netsetup=-dhcp,+nameserver3
+
+</screen>
+ </section>
+
+</appendix>
+
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast.xml" "book" "sect1")
+ End:
+ -->

Added: trunk/autoinstallation/doc/xml/multiplesource.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/multiplesource.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/multiplesource.xml (added)
+++ trunk/autoinstallation/doc/xml/multiplesource.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,338 @@
+ <appendix id="multiplesources">
+ <title>Creating NFS directory for UL/SLES from distribution CDs</title>
+ <section>
+ <title>Introduction</title>
+ <para>
+ UnitedLinux defines a core set of packages which implement the
UnitedLinux runtime environment.
+ All tests, certifications, and applications are based on this set of
packages
+ which should not be altered in any way. The ideal way to guarantee
+ unaltered data, is providing it on CD-ROM.
+ </para>
+ <para>
+ However, this makes including (vendor specific) extensions and bug-fixes on
+ the same media impossible. A separate media must be supplied for
+ installation.
+ </para>
+ <para>
+ The 'multiple source' approach of YaST gives a solution as it allows
+ installation from several (package) sources. So a customer can start
+ installing from the original UnitedLinux CDs, proceed with a product CD,
+ and end with a patch CD containing the latest security patches.
+ </para>
+ </section>
+ <section>
+ <title>
+ Installation workflow
+ </title>
+
+ <section>
+ <title>
+ The installer source
+ </title>
+ <para>
+ When starting the installation from a media (CD, DVD, NFS, ...),
linuxrc looks
+ for a /boot/root file containing a complete (cramfs based) root-fs for
+ YaST.</para>
+
+ <para> Usually, this file is on the boot CD, but other installation
types are
+ also supported by linuxrc. The information, where the /boot/root file
+ came from, is passed to YaST and defines the installer source.
+
+ </para>
+ <para> YaST now looks at this installer source for a /yast/order file.
If this
+ file exists, YaST goes into the 'multiple installation' mode.
+ </para>
+ <para> In this mode, the source description (information about the
packages) is on
+ the installer source and the source data (the rpm packages itself) is
+ on separate media.
+ </para>
+ <para>
+ If the order file does not exist, YaST does not separate the source
+ description from the source data and both must reside on the same
+ media. (The latter is what happens if you boot the first UnitedLinux
+ CD.)
+ </para>
+ </section>
+
+ <section>
+ <title>
+ The order file
+ </title>
+
+ <para> The order file defines which sources are needed for installation
and their priority for installation.
+ A typical example for an order file is given here:
+ </para>
+<screen>
+# yast/order: priority of installation sources
+#
+# source- product
+# description path
+/yast/sles8 /sles8-i386/CD1
+/yast/ul /unitedlinux-i386/CD1
+/ /
+</screen>
+
+ <para> The order file is ASCII, line based, '#' at the beginning of a
line denote a comment line.</para>
+
+ <para> Each non-comment line should contain two (whitespace separated)
directory specifications. If the second one is omitted, it defaults to
"/".</para>
+
+ <para> The first directory specifies the location of the description.
+ The second directory specifies the location of the product as defined here.
+ For CD/DVD bases products, this is usually "/". But for network
installations, or if several product are placed on a single CD, each product
needs a separate path.
+ You can even specify a full URL (e.g.
"nfs://my-nfs-server.domain.org/product/CD1") in the second column.
+During installation, you can't switch the type of media. If your installer
source is CD, every other source must be CD based. If your installer source is
NFS, every other source is expected to be on the same NFS server.</para>
+ <para>
+
+In the above example of the order file, note the last line being "/". This
means the last of the three installation sources is on the same media as the
installer.
+
+
+
+ </para>
+ </section>
+ <section>
+ <title>
+ The instorder file
+ </title>
+ <para>
+ As stated above, the<filename> /yast/order</filename> file lists the
sources in priority
+ order. So a package from a source listed earlier in this file
+ overrides a package (of the same name) from a later source. This
+ technique is used to override the yast2-translation packages from
+ unitedlinux-i386 (where all help texts refer to UnitedLinux) with
+ yast2-translation packages from sles8-i386 (where all help texts
+ refer to SuSE Linux).</para>
+ <para>
+
+ But the <filename>/yast/order</filename> also defines the
installation order, which might not be wanted when the 'base' packages are on a
lower-priority source
+ This is where <filename>/yast/instorder</filename> comes into play.
This defines the installation
+ order by repeating the entries of the first column of /yast/order in
+ the right order.</para>
+
+
+
+ <para>A typical example for an instorder file is given here:</para>
+ <screen>
+# yast/instorder: order of installation sources
+#
+# install 'ul' before 'sles8'
+#
+/yast/ul
+/yast/sles8
+/
+</screen>
+ </section>
+ <section>
+
+ <title>Setting it all up</title>
+
+ <para> Combining multiple sources requires that all sources comply to
+ the UnitedLinux media description standard.</para>
+
+
+ <para>On the installer source create a <filename>yast/order</filename>
as described above
+ and copy the description data of all sources to separate
+ directories. List these directories in the order file and check for
+ conflicting package (.rpm) or selection (.sel) names.
+ </para>
+ <para>
+ If names conflict, the name coming 'first' in the order file wins.
+ </para>
+
+
+ <para>In the 'order' example above, the 'order' directory structure
+ looks as follows: </para>
+ <screen>
+yast/
+ instorder # instorder file
+ order # order file
+ ul/ # product 'ul', placing it below yast isn't
really needed
+ # but practical.
+ media.1/
+ media # media ID for first CD
+ content # content file, describing the paths
+ UnitedLinux/
+ setup/
+ descr/
+ *.sel
+ packages
+ packages.DU
+ packages.en
+ packages.de
+ ...
+ packages.pt
+ sles8/
+ media.1/
+ media
+ content
+ suse/
+ setup/
+ descr/
+ *.sel
+ packages
+ packages.DU
+ packages.en
+ packages.de
+ ...
+ packages.pt
+
+</screen>
+
+
+
+ <para>
+ YaST now takes this description instead of the one from the 'real'
media for the installation.
+ So when asking for a specific media, this media must match the
media.1/media
+ file from the <emphasis>order</emphasis> directory.
+ </para>
+ <para>
+ All dependencies (package or selection) are fulfilled by looking at
+ all installation sources. If multiple sources provide a dependency,
+ the source listed first in the 'order' file wins.
+
+ (The installation order equals the installation priority
currently).
+ </para>
+ </section>
+ </section>
+ <section>
+ <title>Example using SLES 8 and UnitedLinux 1.0 CDs</title>
+
+ <para>
+ You should at least copy the first CD from both UnitedLinux and SLES
+ 8 sets, depending on what selection of software you want to install.
+ </para>
+ <para>
+ On the NFS server, create a directory which will serve as the
+ installation source and make sure it is exported via NFS. This
+ directory will be used later to specify the installation source using
+ linuxrc.
+ </para>
+ <para>
+ The following script illustrates what directories need to be created
+ and where you should copy the data from the CDs. In this script, it
+ is assumed that you have ISO images. In most cases you will have
+ CDROMs instead. Do not use this script as provided. If you wish to
+ use it, please make sure you have changed the directory names to
+ something suitable to your environment.
+ </para>
+
+ <screen>
+#!/bin/sh
+
+instsource="/exports/sles8"
+#
+# Create CD directories
+#
+cd $instsource
+mkdir -p sles8-i386/CD1
+mkdir unitedlinux-i386/CD{1,2,3}
+
+#
+# Copy SLES CD
+#
+cd sles8-i386/CD1
+
+mount -oloop /iso/SLES-8-i386-CD1.iso /mnt
+cp -a /mnt/* .
+umount /mnt
+
+cd ../..
+
+#
+# Copy UL CDs
+#
+
+# 1
+cd unitedlinux-i386/CD1
+mount -oloop /iso/UnitedLinux-1.0-i386-CD1.iso /mnt
+cp -a /mnt/* .
+umount /mnt
+
+# 2
+cd ../CD2
+mount -oloop /iso/UnitedLinux-1.0-i386-CD2.iso /mnt
+cp -a /mnt/* .
+umount /mnt
+
+
+# 3
+cd ../CD3
+mount -oloop /iso/UnitedLinux-1.0-i386-CD3.iso /mnt
+cp -a /mnt/* .
+umount /mnt
+
+#
+# back to root of source
+#
+cd ../..
+
+#
+# Now we have to move some data around to make this
+# a multiple source directory
+#
+# first we copy the order directory described above.
+
+cp -a sles8-i386/CD1/yast .
+
+#
+# Then the boot directory with the installation image
+#
+cp -a sles8-i386/CD1/boot .
+
+#
+# The content file and the media directory
+#
+cp sles8-i386/CD1/content .
+cp -a sles8-i386/CD1/media.1 .
+
+
+#
+# Now we copy the description files from SLES to the order directory as
+# described earlier.
+#
+mkdir -p yast/sles8/suse/setup/descr
+cp -a sles8-i386/CD1/suse/setup/descr yast/sles8/suse/setup
+cp sles8-i386/CD1/content yast/sles8/
+cp -a sles8-i386/CD1/media.1 yast/sles8/
+
+#
+# We are almost done..
+# Now we'll adapt the order files.
+# Fields of the order files are TAB delimited
+
+cat << EOF > yast/order
+/yast/sles8 /sles8-i386/CD1
+/yast/ul /unitedlinux-i386/CD1
+EOF
+
+cat << EOF > yast/instorder
+/yast/ul /unitedlinux-i386/CD1
+/yast/sles8 /sles8-i386/CD1
+EOF
+
+
+
+#
+# End
+#
+
+ </screen>
+ <note>
+ <para>
+ Fields of the order files have TAB as delimiter.
+ </para>
+ </note>
+
+
+
+ </section>
+
+ </appendix>
+
+
+
+ <!--
+ Local Variables:
+ mode: xml
+ sgml-parent-document: ("autoyast2.xml" "book" "chapter")
+ End:
+ -->
\ No newline at end of file

Added: trunk/autoinstallation/doc/xml/purpose.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/purpose.xml?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/purpose.xml (added)
+++ trunk/autoinstallation/doc/xml/purpose.xml Mon Aug 8 14:12:13 2011
@@ -0,0 +1,4032 @@
+<purposes>
+ <profile>
+ <purpose>The root element of the XML configuration
file.</purpose>
+ <description><![CDATA[
+ <para>
+ The root element of the XML file contains all other
configuration data.
+ </para>
+ <refsect2>
+ <title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+ ]]></description>
+ </profile>
+ <install>
+ <purpose>This main directive contains elements needed for core
+ system installation. This tag is deprecated since SUSE Linux 10.0</purpose>
+ <description><![CDATA[
+ <para>
+ Main directive for installation elements
+ </para>
+ <refsect2>
+ <title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+ ]]></description>
+ </install>
+ <general>
+ <purpose>General Options</purpose>
+ <description><![CDATA[
+ <para>
+ General Options
+ </para>
+ <refsect2>
+ <title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+ ]]></description>
+ </general>
+ <reboot>
+ <purpose>Reboot system before proceeding with
+ post-installation</purpose>
+ <description><![CDATA[
+ <para>
+ In case you have installed a new kernel or for other
reasons,
+ you can reboot the installed system before the post-installation
has been started.
+ </para>
+ <refsect2>
+ <title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+
+
+ <screen>
+ true or false, default is false.
+ </screen>
+ </refsect2>
+ ]]></description>
+ </reboot>
+ <keyboard>
+ <purpose>Sets system keyboard type</purpose>
+ <description><![CDATA[
+ <para>Sets system keyboard type</para>
+ <refsect2><title>Type</title>
+ <para>Property</para>
+
+ </refsect2>
+ <refsect2><title>Values</title>
+ <para>
+ Here's the list of available keyboards on i386 and
Alpha
+ machines:
+ </para>
+ <screen>
+ belgian, czech, czech-qwerty, danish, dutch, dvorak, english-
+ uk, english-us, finnish, french, french-ch, german, german-ch, greek,
+ hungarian, italian, japanese, norwegian, polish, portugese, portugese-br,
+ russian, slovak, slovak-qwerty, spanish, swedish, turkish
+
+ </screen> </refsect2>
+ <refsect2><title>&alice; Compatibility</title>
+ <para>This property is replaces the following tags in
&alice;
+ </para>
+ <itemizedlist>
+ <listitem><para>&lt;SYS_KEYTABLE&gt;</para></listitem>
+ </itemizedlist>
+
+
+
+<para>Use the following table to convert key tables used with &yast1; to
+ &yast2; keyboards</para>
+ <table frame='all'>
+ <title>&yast1; to &yast2; conversion</title>
+ <tgroup cols='2'>
+ <thead>
+ <row>
+ <entry>YaST2</entry>
+ <entry>YaST1</entry>
+ </row>
+ </thead>
+
+
+ <tbody>
+ <row><entry>english-uk </entry><entry> us</entry></row>
+ <row><entry>english-us </entry><entry> us</entry></row>
+ <row><entry>german </entry><entry> de-lat1-nd</entry></row>
+ <row><entry>german-ch </entry><entry> de-lat1-nd</entry></row>
+ <row><entry>french </entry><entry> fr-latin1</entry></row>
+ <row><entry>french-ch </entry><entry> fr-latin1</entry></row>
+ <row><entry>italian </entry><entry> it</entry></row>
+ <row><entry>spanish </entry><entry> es</entry></row>
+ <row><entry>dutch </entry><entry> nl</entry></row>
+ <row><entry>portugese </entry><entry> pt2</entry></row>
+ <row><entry>portugese-br </entry><entry> br-abnt2</entry></row>
+ <row><entry>hungarian </entry><entry> hu</entry></row>
+ <row><entry>polish </entry><entry> Pl02</entry></row>
+ <row><entry>greek </entry><entry> gr</entry></row>
+ <row><entry>turkish </entry><entry> trq</entry></row>
+ <row><entry>russian </entry><entry> ru1</entry></row>
+ <row><entry>czech </entry><entry> cz-lat2</entry></row>
+
+ </tbody>
+ </tgroup>
+ </table>
+ </refsect2>
+ ]]></description>
+ </keyboard>
+ <language>
+ <purpose>Sets the language to use during installation</purpose>
+ <description><![CDATA[
+ <para>
+ Sets the language to use during installation and
the language to install on the system.
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Values</title>
+ <para> Valid language codes are the following
+
+ </para>
+ <screen>
+ cs_CZ, da_DK, en_US, fr_FR, de_DE, hu_HU, is_IS, it_IT,
+ ja_JP.eucJP, no_NO, ro_RO, sk_SK, sl_SI, sr_YU, es_ES,
+ ru_RU.KOI8-R, uk_UA.KOI8-U, sv_SE, tr_TR
+ </screen>
+ </refsect2>
+ <refsect2><title>&alice; Compatibility</title>
+ <para>This property is replaces the following tags in
&alice;
+ </para>
+ <itemizedlist>
+ <listitem><para>&lt;SYS_LANGUAGE&gt;</para></listitem>
+ </itemizedlist>
+
+
+
+ </refsect2>
+ ]]></description>
+ </language>
+ <timezone>
+ <purpose>Sets the Time zone</purpose>
+ <description><![CDATA[
+ <para>
+ Sets the Time zone
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Values</title>
+ <para> Valid timezone codes are the following
+
+ </para>
+ <screen>
+ Africa/Algiers, Africa/Brazzaville, Africa/Cairo, Africa/Casablanca,
+ Africa/Ceuta, Africa/Dakar, Africa/Dar_es_Salaam, Africa/Djibouti,
+ Africa/Freetown, Africa/Johannesburg, Africa/Libreville, Africa/Monrovia,
+ Africa/Nairobi, Africa/Timbuktu, Africa/Tripoli, Africa/Tunis,
+ Africa/Windhoek, America/Asuncion, America/Barbados, America/Bogota,
+ America/Buenos_Aires, America/Caracas, America/Costa_Rica,
+ America/Dominica, America/El_Salvador, America/Grenada,
+ America/Guadeloupe, America/Guatemala, America/Lima, America/Managua,
+ America/Martinique, America/Panama, America/Puerto_Rico, America/Virgin,
+ Antarctica/South_Pole, Arctic/Longyearbyen, Asia/Bahrain, Asia/Bangkok,
+ Asia/Beirut, Asia/Brunei, Asia/Calcutta, Asia/Colombo, Asia/Damascus,
+ Asia/Dubai, Asia/Gaza, Asia/Jakarta, Asia/Katmandu, Asia/Kuala_Lumpur,
+ Asia/Kuwait, Asia/Macao, Asia/Manila, Asia/Qatar, Asia/Saigon,
+ Asia/Samarkand, Asia/Seoul, Asia/Shanghai, Asia/Singapore, Asia/Taipei,
+ Asia/Tashkent, Asia/Tokyo, Asia/Vladivostok, Asia/Yekaterinburg,
+ Atlantic/Azores, Atlantic/Bermuda, Atlantic/Reykjavik, Australia/ACT,
+ Australia/Adelaide, Australia/Canberra, Australia/Darwin,
+ Australia/Melbourne, Australia/NSW, Australia/North, Australia/Perth,
+ Australia/Queensland, Australia/South, Australia/Sydney,
+ Australia/Tasmania, Australia/West, Brazil/East, Brazil/West, CET,
+ CST6CDT, Canada/Atlantic, Canada/Central, Canada/East-Saskatchewan,
+ Canada/Eastern, Canada/Mountain, Canada/Newfoundland, Canada/Pacific,
+ Canada/Saskatchewan, Canada/Yukon, Chile/Continental, Chile/EasterIsland,
+ EET, EST, EST5EDT, Egypt, Etc/GMT, Etc/GMT+0, Etc/GMT+1, Etc/GMT+10,
+ Etc/GMT+11, Etc/GMT+12, Etc/GMT+2, Etc/GMT+3, Etc/GMT+4, Etc/GMT+5,
+ Etc/GMT+6, Etc/GMT+7, Etc/GMT+8, Etc/GMT+9, Etc/GMT-0, Etc/GMT-1,
+ Etc/GMT-10, Etc/GMT-11, Etc/GMT-12, Etc/GMT-13, Etc/GMT-14, Etc/GMT-2,
+ Etc/GMT-3, Etc/GMT-4, Etc/GMT-5, Etc/GMT-6, Etc/GMT-7, Etc/GMT-8,
+ Etc/GMT-9, Etc/GMT0, Etc/Greenwich, Etc/UCT, Etc/UTC, Etc/Universal,
+ Etc/Zulu, Europe/Amsterdam, Europe/Athens, Europe/Belfast,
+ Europe/Belgrade, Europe/Berlin, Europe/Bratislava, Europe/Brussels,
+ Europe/Bucharest, Europe/Budapest, Europe/Chisinau, Europe/Copenhagen,
+ Europe/Dublin, Europe/Gibraltar, Europe/Helsinki, Europe/Istanbul,
+ Europe/Kiev, Europe/Lisbon, Europe/Ljubljana, Europe/London,
+ Europe/Luxembourg, Europe/Madrid, Europe/Malta, Europe/Monaco,
+ Europe/Moscow, Europe/Oslo, Europe/Paris, Europe/Prague, Europe/Riga,
+ Europe/Rome, Europe/Sarajevo, Europe/Skopje, Europe/Sofia,
+ Europe/Stockholm, Europe/Tallinn, Europe/Tirane, Europe/Vaduz,
+ Europe/Vatican, Europe/Vienna, Europe/Vilnius, Europe/Warsaw,
+ Europe/Zagreb, Europe/Zurich, GMT, GMT+0, GMT-0, GMT0, Greenwich, HST,
+ Hongkong, Iceland, Israel, Jamaica, Japan, MET, MST, MST7MDT,
+ Mexico/BajaNorte, Mexico/BajaSur, Mexico/General, Mideast/Riyadh87,
+ Mideast/Riyadh88, Mideast/Riyadh89, NZ, NZ-CHAT, Navajo, PRC, PST8PDT,
+ Pacific/Fiji, Pacific/Galapagos, Pacific/Guadalcanal, Pacific/Guam,
+ Pacific/Midway, Pacific/Nauru, Pacific/Palau, Pacific/Pitcairn,
+ Pacific/Samoa, Pacific/Tahiti, Poland, Portugal, ROC, ROK, Singapore,
+ Turkey, UCT, US/Alaska, US/Aleutian, US/Arizona, US/Central,
+ US/East-Indiana, US/Eastern, US/Hawaii, US/Indiana-Starke, US/Michigan,
+ US/Mountain, US/Pacific, US/Samoa, UTC, Universal, W-SU, WET, Zulu
+
+ </screen>
+ </refsect2>
+ <refsect2><title>&alice; Compatibility</title>
+ <para>This property is replaces the following tags in
&alice;
+ </para>
+ <itemizedlist>
+ <listitem><para>&lt;SYS_TIMEZONE&gt;</para></listitem>
+ </itemizedlist>
+
+ </refsect2>
+ ]]></description>
+ </timezone>
+ <hwclock>
+ <purpose>Specify whether the hardware clock of your machine is
+ set to local time or GMT.</purpose>
+ <description><![CDATA[
+ <para>
+ Most PCs that also have other operating systems
installed (such as Microsoft Windows) use local time.
+ Machines that have only Linux installed should be set to
Greenwich Mean Time (GMT).
+ If you are unsure, use GMT.
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Values</title>
+ <para>
+ GMT or localtime
+ </para>
+ </refsect2>
+ <refsect2><title>&alice; Compatibility</title>
+ <para>This property is replaces the following tags in
&alice;
+ </para>
+ <itemizedlist>
+ <listitem><para>&lt;SYS_HWC_GMT&gt;</para></listitem>
+ </itemizedlist>
+
+ </refsect2>
+ ]]></description>
+ </hwclock>
+ <mouse>
+ <purpose>Choose the mouse type of the mouse attached to the
+ system</purpose>
+ <description><![CDATA[
+ <para>
+ Choose the mouse type of the mouse attached to the system
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Values</title>
+ <table frame='all'>
+ <title>Mouse Types and IDs</title>
+ <tgroup cols='2'>
+ <thead>
+ <row>
+ <entry>ID</entry>
+ <entry>Type</entry>
+ </row>
+ </thead>
+
+
+ <tbody>
+<row><entry>00_ps2</entry><entry>PS/2 mouse (Aux-port)</entry></row
+>
+
+<row><entry>01_ms0</entry><entry>Microsoft compatible serial mouse - (ttyS0 -
COM1)</entry></row>
+
+<row><entry>02_ms</entry><entry>Microsoft compatible serial mouse - (ttyS1 -
COM2)</entry></row>
+
+<row><entry>03_ms30</entry><entry>Microsoft Intellimouse - 3 buttons and wheel
- (ttyS0 - COM1)</entry></row>
+
+<row><entry>04_ms3</entry><entry>Microsoft Intellimouse - 3 buttons and wheel
- (ttyS1 - COM2)</entry></row>
+
+<row><entry>05_msc0</entry><entry>Mouse Systems serial mouse - (ttyS0 -
COM1)</entry></row>
+
+<row><entry>06_msc</entry><entry>Mouse Systems serial mouse - (ttyS1 -
COM2)</entry></row>
+
+<row><entry>07_mman0</entry><entry>Mouse Man protocol (serial Logitech mouse)
- (ttyS0 - COM1)</entry></row>
+
+<row><entry>08_mman</entry><entry>Mouse Man protocol (serial Logitech mouse) -
(ttyS1 - COM2)</entry></row>
+
+<row><entry>09_logi0</entry><entry>Old Logitech serial mouse (series 9) -
(ttyS0 - COM1)</entry></row>
+
+<row><entry>10_logi</entry><entry>Old Logitech serial mouse (series 9) -
(ttyS1 - COM2)</entry></row>
+
+<row><entry>11_busm</entry><entry>Logitech busmouse</entry></row>
+
+<row><entry>12_sun</entry><entry>Sun Mouse - (/dev/sunmouse)</entry></row>
+
+<row><entry>13_bare0</entry><entry>Oldest 2-button serial mouse - (ttyS0 -
COM1)</entry></row>
+
+<row><entry>14_bare</entry><entry>Oldest 2-button serial mouse - (ttyS1 -
COM2)</entry></row>
+
+<row><entry>15_mb</entry><entry>Microsoft busmouse</entry></row>
+
+<row><entry>16_bm</entry><entry>ATI XL busmouse</entry></row>
+
+<row><entry>17_pnp0</entry><entry>Plug-and-Play mice - (ttyS0 -
COM1)</entry></row>
+
+<row><entry>18_pnp</entry><entry>Plug-and-Play mice - (ttyS1 -
COM2)</entry></row>
+
+<row><entry>19_usb</entry><entry>USB mouse</entry></row>
+
+<row><entry>20_imps2</entry><entry>Intelli/Wheel mouse (Aux-port)</entry></row>
+
+<row><entry>21_imps2</entry><entry>Intelli/Wheel mouse (USB)</entry></row>
+
+<row><entry>non</entry><entry>NONE </entry></row>
+ </tbody>
+ </tgroup>
+ </table>
+
+
+ </refsect2>
+ ]]></description>
+ </mouse>
+ <configure>
+ <purpose>Data for post-configuration after the system has been
+ setup. This tag is deprecated since SUSE Linux 10.0</purpose>
+ <description><![CDATA[
+ <para>
+ Data for post-configuration after the system has been
setup.
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+ ]]></description>
+ </configure>
+ <bootloader>
+ <purpose>Configure Bootloader (Lilo, ELILO etc.).</purpose>
+ <description><![CDATA[
+ <para>
+ The directive handles the bootloader configuration.
Using the vootloader element, theuser can specify where lilo should be
installed and whether some hardware dependent parameters should be activated.
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+ ]]></description>
+ </bootloader>
+ <encrypted>
+ <purpose>Is the given password encrypted?</purpose>
+ <description><![CDATA[
+ <para>
+ Specify whether the given password is encrypted. If the
+ password is given in clear text, then it will be encrypted,
otherwise it
+ will be kept as is.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Values</title>
+ <para>
+ This element takes a boolean as a value. Possible values are
<emphasis>true</emphasis> or <emphasis>false</emphasis>.
+ </para>
+ </refsect2>
+ ]]></description>
+ </encrypted>
+ <boot>
+ <purpose>Name of the device (e.g. a hard disk partition) that
+ contains the boot sector.</purpose>
+ <description><![CDATA[
+ <para> See <emphasis>lilo.conf(5)</emphasis>
+ <refsect2><title>Values</title>
+ <para>
+ a hard disk partition
+ </para>
+ </refsect2>
+ ]]></description>
+ </boot>
+ <lba32>
+ <purpose>Generate 32-bit Logical Block Addresses instead of
+ sector/head/cylinder addresses.</purpose>
+ <description><![CDATA[
+ <para> See <emphasis>lilo.conf(5)</emphasis>
+
+ </para>
+ <refsect2><title>Values</title>
+ <para>
+ <emphasis>boolean</emphasis>
+ </para>
+ </refsect2>
+ ]]></description>
+ </lba32>
+ <menuscheme>
+ <purpose>Color scheme of the boot menu</purpose>
+ <description><![CDATA[
+ <para> See <emphasis>lilo.conf(5)</emphasis>
+
+ </para>
+ <refsect2><title>Values</title>
+ <para>
+ &lt;color-scheme&gt;
+ </para>
+ </refsect2>
+ ]]></description>
+ </menuscheme>
+ <message>
+ <purpose>specifies a file containing a message that is
+ displayed before the boot prompt.</purpose>
+ <description><![CDATA[
+ <para> See <emphasis>lilo.conf(5)</emphasis>
+
+ </para>
+ <refsect2><title>Values</title>
+ <para>
+ message-file
+ </para>
+ </refsect2>
+ ]]></description>
+ </message>
+ <prompt>
+ <purpose>The boot loader will issue the boot: prompt and wait
+ for user input before proceeding (see timeout TODO).</purpose>
+ <description><![CDATA[
+ <para> See <emphasis>lilo.conf(5)</emphasis>
+
+ </para>
+ <refsect2><title>Values</title>
+ <para>
+ <emphasis>boolean</emphasis>
+ </para>
+ </refsect2>
+ ]]></description>
+ </prompt>
+ <readonly>
+ <purpose>This specifies that the root file system should be
+ mounted read- only.</purpose>
+ <description><![CDATA[
+ <para> See <emphasis>lilo.conf(5)</emphasis>
+
+ </para>
+ <refsect2><title>Values</title>
+ <para>
+ <emphasis>boolean</emphasis>
+ </para>
+ </refsect2>
+ ]]></description>
+ </readonly>
+ <timeout>
+ <purpose>Sets the timeout for timed messages</purpose>
+ <description><![CDATA[
+ <para>
+ Timeout before a message disappears.
+ </para>
+ <refsect2><title>Values</title>
+ <para>
+ Timeout in seconds.
+ </para>
+ </refsect2>
+ ]]></description>
+ </timeout>
+ <show>
+ <purpose>Show pop-up messages</purpose>
+ <description><![CDATA[
+ <para>
+ Determine whether to show pop-up messages, warnings or erros.
+ </para>
+ <refsect2><title>Values</title>
+ <para>
+ boolean
+ </para>
+ </refsect2>
+ ]]></description>
+ </show>
+ <log>
+ <purpose>Log pop-up messages</purpose>
+ <description><![CDATA[
+ <para>
+ Determine whether to log pop-up messages, warnings or erros.
+ </para>
+ <refsect2><title>Values</title>
+ <para>
+ boolean
+ </para>
+ </refsect2>
+ ]]></description>
+ </log>
+ <vga>
+ <purpose>This specifies the VGA text mode that should be
+ selected when booting.</purpose>
+ <description><![CDATA[
+ <para> See <emphasis>lilo.conf(5)</emphasis>
+
+ </para>
+ <refsect2><title>Values</title>
+ <itemizedlist>
+ <listitem>
+ <Para><emphasis>normal</emphasis>: select normal 80x25 text
mode.</para>
+ </listitem>
+ <listitem>
+ <Para><emphasis>extended (or ext)</emphasis>: select 80x50
text mode.</para>
+ </listitem>
+ <listitem>
+ <Para><emphasis>ask</emphasis>: stop and ask for user input
(at boot time).</para>
+ </listitem>
+ <listitem>
+ <Para><emphasis>&lt;number&gt;</emphasis>: use the
corresponding
+ text mode. A list of available modes can be obtained by
booting with <emphasis>>vga=ask</emphasis>
+ and pressing [Enter].
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ </refsect2>
+ ]]></description>
+ </vga>
+ <lilo_password>
+ <purpose>Enables password authentification when
+ booting.</purpose>
+ <description><![CDATA[
+ <para> See <emphasis>lilo.conf(5)</emphasis>
+
+ </para>
+ <refsect2><title>Values</title>
+ <para>
+ password
+ </para>
+ </refsect2>
+ ]]></description>
+ </lilo_password>
+ <security>
+ <purpose>Security Options.</purpose>
+ <description><![CDATA[
+ <para>
+ Security Options
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+ ]]></description>
+ </security>
+ <pass_max_len>
+ <purpose>Maximum kength for passwords</purpose>
+ <description><![CDATA[
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Values</title>
+ <para>
+ Integer
+ </para>
+ </refsect2>
+ ]]></description>
+ </pass_max_len>
+ <root_login_remote>
+ <purpose>allow root logins from other machines</purpose>
+ <description><![CDATA[
+ <para>
+ If you want to allow root logins from other machines,
set ROOT_LOGIN_REMOTE
+ to "yes". (Logging in via ssh is not affected by this
variable since SSH
+ is seen as a safe login method).
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Values</title>
+ <para>
+ yes or no
+ </para>
+ </refsect2>
+ ]]></description>
+ </root_login_remote>
+ <console_shutdown>
+ <purpose>determines how ctrl-alt-del is handled.</purpose>
+ <description><![CDATA[
+ <para>
+
+ determines how ctrl-alt-del is handled.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ ignore, reboot or halt
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </console_shutdown>
+ <cwd_in_root_path>
+ <purpose>Do you want to have dot in root path?</purpose>
+ <description><![CDATA[
+ <para>
+
+ Do you want to have a dot in root path? This is not
recommended, but
+ many people do prefer it (yes/no). The setting affects all
system
+ users (with uid < 100)
+
+ </para>
+ <refsect2>
+ <title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ yes or no
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </cwd_in_root_path>
+ <faillog_enab>
+ <purpose>Enable logging and display of /var/log/faillog login
+ failure info.</purpose>
+ <description><![CDATA[
+ <para>
+ Enable logging and display of
<filename>/var/log/faillog</filename> login failure info.
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ yes or no
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </faillog_enab>
+ <fail_delay>
+ <purpose>Delay in seconds before being allowed another attempt
+ after a login failure</purpose>
+ <description><![CDATA[
+ <para>
+
+ Delay in seconds before being allowed another attempt after
a login failure
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ number representing seconds.
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </fail_delay>
+ <gid_max>
+ <purpose>Min/max values for automatic gid selection in
+ groupadd</purpose>
+ <description><![CDATA[
+ <para>
+
+ Min/max values for automatic gid selection in groupadd
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ ]]></description>
+ </gid_max>
+ <gid_min>
+ <purpose>Min/max values for automatic gid selection in
+ groupadd</purpose>
+ <description><![CDATA[
+ <para>
+
+ Min/max values for automatic gid selection in groupadd
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ ]]></description>
+ </gid_min>
+ <uid_max>
+ <purpose>Min/max values for automatic uid selection in
+ useradd</purpose>
+ <description><![CDATA[
+ <para>
+
+ Min/max values for automatic uid selection in useradd
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ ]]></description>
+ </uid_max>
+ <uid_min>
+ <purpose>Min/max values for automatic uid selection in
+ useradd</purpose>
+ <description><![CDATA[
+ <para>
+
+ Min/max values for automatic uid selection in useradd
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ ]]></description>
+ </uid_min>
+ <kdm_shutdown>
+ <purpose>who will be able to shutdown the system in
+ kdm</purpose>
+ <description><![CDATA[
+ <para> Determines who will be able to shutdown the
+ system in kdm.
+
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ "root", "all", "none", "local", "auto"
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </kdm_shutdown>
+ <lastlog_enab>
+ <purpose>Enable logging and display of /var/log/lastlog login
+ time info.</purpose>
+ <description><![CDATA[
+ <para>
+ Enable logging and display of /var/log/lastlog login time
info.
+
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ yes or no
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </lastlog_enab>
+ <md5_support>
+ <purpose>Enable MD5 Support</purpose>
+ <description><![CDATA[
+ <para>
+ Activate MD5 encryption for passwords
+
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ yes or no
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </md5_support>
+ <obscure_changes_enab>
+ <purpose>Enable additional checks upon password
+ changes.</purpose>
+ <description><![CDATA[
+ <para>
+
+ Enable additional checks upon password changes.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ yes or no
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </obscure_changes_enab>
+ <passwd_use_cracklib>
+ <purpose>Use cracklib?</purpose>
+ <description><![CDATA[
+ <para>
+
+ Use Cracklib
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ yes or no
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </passwd_use_cracklib>
+ <pass_max_days>
+ <purpose>Maximum number of days a password may be
+ used.</purpose>
+ <description><![CDATA[
+ <para>
+
+ Maximum number of days a password may be used.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ Number
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </pass_max_days>
+ <pass_min_days>
+ <purpose>Minimum number of days allowed between password
+ changes.</purpose>
+ <description><![CDATA[
+ <para>
+
+ Minimum number of days allowed between password changes.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ Number
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </pass_min_days>
+ <pass_min_len>
+ <purpose>Minimum acceptable password length.</purpose>
+ <description><![CDATA[
+ <para>
+
+
+ Minimum acceptable password length.
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ Number
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </pass_min_len>
+ <pass_warn_age>
+ <purpose>Number of days warning given before a password
+ expires.</purpose>
+ <description><![CDATA[
+ <para>
+
+ Number of days warning given before a password
expires.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+
+ Number
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </pass_warn_age>
+ <permission_security>
+ <purpose>Permission Security configuration to use.</purpose>
+ <description><![CDATA[
+ <para>
+
+ &company-suse; Linux contains two different configurations
for
+ chkstat. The differences can be found in
<filename>/etc/permissions.secure</filename>
+ and <filename>/etc/permissions.easy</filename>. If you
create your own configuration
+ (e.g. permissions.foo), you can enter the extension here as
well.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+ easy/secure local foo whateveryouwant
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </permission_security>
+ <run_updatedb_as>
+ <purpose>Which user should updatedb use to run?</purpose>
+ <description><![CDATA[
+ <para>
+ updatedb has a parameter "--localuser".
+ It runs the "find" command as this user. Some people think
this is a
+ security hole if set to 'root' (because some directory
information can
+ be read which is normally protected). Others think it is
useful to hold
+ all files in the database.
+ So if you want full information in locate db, set
RUN_UPDATEDB_AS to root.
+ If you want security use RUN_UPDATEDB_AS with nobody.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+ user name
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </run_updatedb_as>
+ <activate>
+ <purpose>activate partition where LILO is installed</purpose>
+ <description><![CDATA[
+ <para> activate partition where LILO is installed. Set
this option to
+ true to mark the partition as active. Usually this
+ is not required, but, on some systems, the BIOS only boots
from an active partition.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+ boolean: true or false
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </activate>
+ <linear>
+ <purpose>Use lilo&apos;s linear option</purpose>
+ <description><![CDATA[
+ <para>
+ Generate linear sector addresses instead of
sector/head/cylinder
+ addresses. Linear addresses are translated at run time and
do not depend
+ on disk geometry. When using `linear' with large disks,
+ <command>/sbin/lilo</command> may generate references to
inaccessible
+ disk areas, because 3D sector addresses are not known before
boot
+ time. 'lba32' avoids many of these pitfalls with its use of
packet
+ addressing, but requires a recent BIOS. (See man
lilo.conf(5))
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+ boolean: true or false
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </linear>
+ <location>
+ <purpose>Bootloader device location</purpose>
+ <description><![CDATA[
+ <para>
+ Sets the name of the device (e.g. a hard disk partition)
that contains
+ the boot sector. If <emphasis>mbr</emphasis> is given, lilo
will be written on the MBR disk.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+ mbr, floppy or a partition device (or a hard drive device)
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </location>
+ <parameters>
+ <purpose>Bootloader device location</purpose>
+ <description><![CDATA[
+ <para>
+
+ Appends the options specified to the parameter line passed
to the kernel.
+ This is typically used to specify parameters of hardware
that can't be
+ entirely auto-detected or for which probing may be dangerous.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+ kernel parameters, i.e. "enableapic hdb=ide-scsi" (without
the quotes)
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </parameters>
+ <confirm>
+ <purpose>Configure reporting and pop-ups</purpose>
+ <description><![CDATA[
+ <para>
+ Confirm installation before anything is done on the system.
This is
+ to avoid any recrusive installations.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Values</title>
+ <para>
+ boolean, true by default.
+
+ </para>
+ </refsect2>
+ ]]></description>
+ </confirm>
+ <report>
+ <purpose>Configure reporting and pop-ups</purpose>
+ <description><![CDATA[
+ <para>
+ See <quote><link linkend='CreateProfile.Reporting'
endterm="CreateProfile.Reporting.title"></link></quote>
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </report>
+ <messages>
+ <purpose>Configure message pop-ups</purpose>
+ <description><![CDATA[
+ <para>
+ See <quote><link linkend='CreateProfile.Reporting'
endterm="CreateProfile.Reporting.title"></link></quote>
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </messages>
+ <errors>
+ <purpose>Configure error pop-ups</purpose>
+ <description><![CDATA[
+ <para>
+ See <quote><link linkend='CreateProfile.Reporting'
endterm="CreateProfile.Reporting.title"></link></quote>
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </errors>
+ <warnings>
+ <purpose>Configure warning pop-ups</purpose>
+ <description><![CDATA[
+ <para>
+ See <quote><link linkend='CreateProfile.Reporting'
endterm="CreateProfile.Reporting.title"></link></quote>
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </warnings>
+ <users>
+ <purpose>Add users to the system</purpose>
+ <description><![CDATA[
+ <para>
+ Using this resource, you will be able to add users to the
system.
+ This resource is also used to set the root password.
+
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </users>
+ <user>
+ <purpose>The user resource</purpose>
+ <description><![CDATA[
+ <para>
+ This resource contains data about a single user that should
be added to
+ the system.
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </user>
+ <username>
+ <purpose>The user name, or login</purpose>
+ <description><![CDATA[
+ <para>
+ The user name, or login
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ string, use
+ <emphasis>lowercase</emphasis> letters (no accented
characters), digits, and <emphasis>._-</emphasis>
+ User names have stricter restrictions than passwords!
+ </para>
+ </refsect2>
+ ]]></description>
+ </username>
+ <user_password>
+ <purpose>The user password</purpose>
+ <description><![CDATA[
+ <para>
+ A password should have at least 5 characters and, as a rule,
not contain any
+ special characters (e.g., accented characters).
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ valid password
+ </para>
+ </refsect2>
+ ]]></description>
+ </user_password>
+ <home>
+ <purpose>home directory of the user</purpose>
+ <description><![CDATA[
+ <para>The home directory of the user. Normally this is
+ /home/username.
+
+ </para>
+ <refsect2>
+ <title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string, example <filename>/home/nashif</filename>
+ </para>
+ </refsect2>
+ ]]></description>
+ </home>
+ <forename>
+ <purpose>User forename</purpose>
+ <description><![CDATA[
+ <para>
+ User forename
+
+ </para>
+ <refsect2>
+ <title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string
+ </para>
+ </refsect2>
+ ]]></description>
+ </forename>
+ <surname>
+ <purpose>user surname</purpose>
+ <description><![CDATA[
+ <para>
+ User surname
+
+ </para>
+ <refsect2>
+ <title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string
+ </para>
+ </refsect2>
+ ]]></description>
+ </surname>
+ <gid>
+ <purpose>Group ID(gid)</purpose>
+ <description><![CDATA[
+ <para>
+ In addition to its name, a group has to be assigned a
numerical ID for its
+ internal representation. These values are between 0 and a
value defined
+ in <filename>/etc/login.defs</filename>. Some of the IDs are
already
+ assigned during installation.
+
+
+ </para>
+ <para>
+ Leave empty if unsure, &yast2; will determine the value
automatically.
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string
+ </para>
+ </refsect2>
+ ]]></description>
+ </gid>
+ <uid>
+ <purpose>User ID(uid)</purpose>
+ <description><![CDATA[
+ <para>
+ Each user is known to the system by a unique number,
+ the "User ID". For normal users, you should use
+ a UID bigger than the value defined in the system, because
the smaller UIDs are used
+ by the system for special purposes and pseudo logins.
+
+ </para>
+ <para>
+ Leave empty if unsure, &yast2; will determine the value
automatically.
+ </para>
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string
+ </para>
+ </refsect2>
+ ]]></description>
+ </uid>
+ <shell>
+ <purpose>The login shell (command interpreter) for the
+ user.</purpose>
+ <description><![CDATA[
+ <para>
+ Select one shell from the list of all shells installed
+ on your system.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string
+ </para>
+ </refsect2>
+ ]]></description>
+ </shell>
+ <grouplist>
+ <purpose>Additional group membership</purpose>
+ <description><![CDATA[
+ <para>
+ All additional memberships in groups for the user.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ comma seprated values
+ </para>
+ </refsect2>
+ ]]></description>
+ </grouplist>
+ <x11>
+ <purpose>X11 configuration</purpose>
+ <description><![CDATA[
+ <para>
+ configure the X11 system
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </x11>
+ <configure_x11>
+ <purpose>Activate X11 configuration</purpose>
+ <description><![CDATA[
+ <para>
+ Activate X11 configuration
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ boolean
+ </para>
+ </refsect2>
+ ]]></description>
+ </configure_x11>
+ <min_hsync>
+ <purpose>Minimal horizontal frequency</purpose>
+ <description><![CDATA[
+ <para>
+ The <emphasis>horizontal frequency</emphasis> (in kHz) specifies
how many times
+ per second the monitor can write a horizontal scan line. This is a
+ hard limit of the monitor, independent of the screen resolution.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ integer
+ </para>
+ </refsect2>
+ ]]></description>
+ </min_hsync>
+ <max_hsync>
+ <purpose>Maximal horizontal frequency</purpose>
+ <description><![CDATA[
+ <para>
+ The <emphasis>horizontal frequency</emphasis> (in kHz) specifies
how many times
+ per second the monitor can write a horizontal scan line. This is a
+ hard limit of the monitor, independent of the screen resolution.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ integer
+ </para>
+ </refsect2>
+ ]]></description>
+ </max_hsync>
+ <max_vsync>
+ <purpose>Maximal vertical frequency</purpose>
+ <description><![CDATA[
+ <para>
+ The <emphasis>vertical frequency</emphasis> (in Hz) specifies how
many times per
+ second the image on the screen is refreshed. This value depends on the
+ screen resolution and the monitor's maximum horizontal frequency.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ integer
+ </para>
+ </refsect2>
+ ]]></description>
+ </max_vsync>
+ <min_vsync>
+ <purpose>Minimal vertical frequency</purpose>
+ <description><![CDATA[
+ <para>
+ The <emphasis>vertical frequency</emphasis> (in Hz) specifies how many
times per
+ second the image on the screen is refreshed. This value depends on the
+ screen resolution and the monitor's maximum horizontal frequency.
+
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ integer
+ </para>
+ </refsect2>
+ ]]></description>
+ </min_vsync>
+ <color_depth>
+ <purpose>Color depth when configuring X11</purpose>
+ <description><![CDATA[
+ <para>
+ Color depth in bit.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ 8, 15 (PPC), 16, 24, 32
+ </para>
+ </refsect2>
+ ]]></description>
+ </color_depth>
+ <display_manager>
+ <purpose>Display Manager</purpose>
+ <description><![CDATA[
+ <para>
+ What display manager to install
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string: kdm or gdm
+ </para>
+ </refsect2>
+ ]]></description>
+ </display_manager>
+ <enable_3d>
+ <purpose>Enable 3D Support</purpose>
+ <description><![CDATA[
+ <para>
+ Enable 3D support for X11.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ boolean: true or false
+ </para>
+ </refsect2>
+ ]]></description>
+ </enable_3d>
+ <resolution>
+ <purpose>X11 Resolution</purpose>
+ <description><![CDATA[
+ <para>
+ Configure X11 Resolution. &yast2; will by default add all lower
resolution
+ up to the selected one.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ 640x480, 800x600, 1024x768, 1152x864, 1280x960, 1280x1024,
1600x1200
+ </para>
+ </refsect2>
+ ]]></description>
+ </resolution>
+ <monitor>
+ <purpose>Monitor configuration</purpose>
+ <description><![CDATA[
+ <para>
+ Monitor configuration
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </monitor>
+ <display>
+ <purpose>Display configuration and properties</purpose>
+ <description><![CDATA[
+ <para>
+ Display configuration and properties
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </display>
+ <monitor_device>
+ <purpose>Monitor device name</purpose>
+ <description><![CDATA[
+ <para>
+ Monitor device name
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </monitor_device>
+ <monitor_vendor>
+ <purpose>Monitor vendor name</purpose>
+ <description><![CDATA[
+ <para>
+ Monitor vendor name
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </monitor_vendor>
+ <mail>
+ <purpose>Mail Settings</purpose>
+ <description><![CDATA[
+ <para>
+ Configure Mail settings
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </mail>
+ <aliases>
+ <purpose>Configure mail aliases</purpose>
+ <description><![CDATA[
+ <para>
+ This table redirects mail delivered locally. Redirect it to
another local
+ user (useful for system accounts, especially for root), to a remote
+ address, or to a list of addresses. See the aliases(5) manual page
for a
+ description of advanced features.
+
+
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </aliases>
+ <mta>
+ <purpose>Mail transport agent to use</purpose>
+ <description><![CDATA[
+ <para>
+ Mail transport agent to use
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string: sendmail or postfix
+ </para>
+ </refsect2>
+ ]]></description>
+ </mta>
+ <alias_entry>
+ <purpose>An email alias entry</purpose>
+ <description><![CDATA[
+ <para>
+ A single mail alias entry
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+
+ ]]></description>
+ </alias_entry>
+ <comment>
+ <purpose>A Comment</purpose>
+ <description><![CDATA[
+ <para>
+ A comment
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Shared Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string
+ </para>
+ </refsect2>
+ ]]></description>
+ </comment>
+ <alias>
+ <purpose>Alias for incoming mail redirection</purpose>
+ <description><![CDATA[
+ <para>
+ Alias for incoming mail redirection
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string
+ </para>
+ </refsect2>
+ ]]></description>
+ </alias>
+ <from_header>
+ <purpose>Email from header</purpose>
+ <description><![CDATA[
+ <para>
+ You may want the mail you sent to appear as if it originated from
company.com instead of pc-042.company.com.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string: domain name
+ </para>
+ </refsect2>
+ ]]></description>
+ </from_header>
+ <local_domains>
+ <purpose>Local domains</purpose>
+ <description><![CDATA[
+ <para>
+ specify the domains for which the mail will be delivered locally.
If you enter nothing, the local host name is assumed.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ List Property
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </local_domains>
+ <outgoing_mail_server>
+ <purpose>Outgoing mail server</purpose>
+ <description><![CDATA[
+ <para>
+ The outgoing mail server is generally intended for dial-up
connections. Enter the Internet service provider's SMTP server, such as
smtp.provider.com.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string: valid smtp server name
+ </para>
+ </refsect2>
+ ]]></description>
+ </outgoing_mail_server>
+ <use_amavis>
+ <purpose>Use a virus scanner (AMaViS).</purpose>
+ <description><![CDATA[
+ <para>
+ Use a virus scanner (AMaViS), amavis-sendmail or amavis-postfix
must be installed.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ boolean: true or false
+ </para>
+ </refsect2>
+ ]]></description>
+ </use_amavis>
+ <connection_type>
+ <purpose>Connection type of machine</purpose>
+ <description><![CDATA[
+ <para>
+ How are you connected to the Internet?
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ string: permanent, dialup or none
+ </para>
+ </refsect2>
+ ]]></description>
+ </connection_type>
+ <networking>
+ <purpose>Network configuration</purpose>
+ <description><![CDATA[
+ <para>
+ Configure interfaces, DNS and routing
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </networking>
+ <interfaces>
+ <purpose>Network interfaces</purpose>
+ <description><![CDATA[
+ <para>
+ A List of network interfaces available in the system.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </interfaces>
+ <interface>
+ <purpose>Configure a network interface</purpose>
+ <description><![CDATA[
+ <para>
+ Configure a network interface
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </interface>
+ <options>
+ <purpose>NIC kernel module options</purpose>
+ <description><![CDATA[
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </options>
+ <startmode>
+ <purpose>Boot mode of a network interface</purpose>
+ <description><![CDATA[
+ <para>
+ Configure the boot mode of a network interface. This property
describes
+ the mode of the device setup, missing means "onboot"
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ onboot|hotplug|manual
+ </para>
+ </refsect2>
+ ]]></description>
+ </startmode>
+ <bootproto>
+ <purpose>Boot protocol of a network interface</purpose>
+ <description><![CDATA[
+ <para>
+ Configure the boot protocol of a network interface. This property
describes
+ the setup protocol, if missing or "none", fixed address is used
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ none|bootp|dhcp
+ </para>
+ </refsect2>
+ ]]></description>
+ </bootproto>
+ <ipaddr>
+ <purpose>IP address v4.</purpose>
+ <description><![CDATA[
+ <para>
+ IP4 address
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ valid ipv4 address
+ </para>
+ </refsect2>
+ ]]></description>
+ </ipaddr>
+ <netmask>
+ <purpose>Configure network interface Netmask</purpose>
+ <description><![CDATA[
+ <para>
+ Configure network interface Netmas
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property (NETMASK)
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ valid netmask, i.e. 255.255.255.0
+ </para>
+ </refsect2>
+ ]]></description>
+ </netmask>
+ <network>
+ <purpose>Configure network interface Netmask</purpose>
+ <description><![CDATA[
+ <para>
+ Configure network interface Netmask
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ valid netmask, i.e. 255.255.255.0
+ </para>
+ </refsect2>
+ ]]></description>
+ </network>
+ <broadcast>
+ <purpose>Configure network interface broadcast</purpose>
+ <description><![CDATA[
+ <para>
+ Configure network interface broadcast
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ valid broadcast value , i.e. 10.10.0.255
+ </para>
+ </refsect2>
+ ]]></description>
+ </broadcast>
+ <device>
+ <purpose>Network device name or harddisk device</purpose>
+ <description><![CDATA[
+ <itemizedlist>
+ <listitem>
+ <para>
+ Network device name.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Harddisk device
+ </para>
+ </listitem>
+ </itemizedlist>
+
+ <refsect2><title>Type</title>
+ <para>
+ Shared property
+ </para>
+ </refsect2>
+ <refsect2>
+ <title>Value</title>
+ <para>
+ <emphasis>eth</emphasis> or <emphasis>tr</emphasis> with device
number or
+ a valid hard disk device, i.e. <emphasis>/dev/hda</emphasis>
+ </para>
+ </refsect2>
+ ]]></description>
+ </device>
+ <dns>
+ <purpose>DNS configuration</purpose>
+ <description><![CDATA[
+ <para>
+ configure DNS and hostname
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </dns>
+ <dhcp_hostname>
+ <purpose>Set hostname using DHCP </purpose>
+ <description><![CDATA[
+ <para>
+ Set hostname using DHCP
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ boolean: true or false
+ </para>
+ </refsect2>
+ ]]></description>
+ </dhcp_hostname>
+ <domain>
+ <purpose>Set domain name</purpose>
+ <description><![CDATA[
+ <para>
+ set domain name
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ valid domain name
+ </para>
+ </refsect2>
+ ]]></description>
+ </domain>
+ <hostname>
+ <purpose>Set hostname</purpose>
+ <description><![CDATA[
+ <para>
+ set hostname
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ valid host name
+ </para>
+ </refsect2>
+ ]]></description>
+ </hostname>
+ <nameservers>
+ <purpose>Set the list of nameservers</purpose>
+ <description><![CDATA[
+ <para>
+ Configure a list of nameservers to be used
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </nameservers>
+ <nameserver>
+ <purpose>configure a nameserver</purpose>
+ <description><![CDATA[
+ <para>
+ Configure a nameserver to be used
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ valid nameserver name
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </nameserver>
+ <searchlist>
+ <purpose>Set the DNS search list</purpose>
+ <description><![CDATA[
+ <para>
+ Configure a list of domains to search first
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </searchlist>
+ <search>
+ <purpose>configure a search entry</purpose>
+ <description><![CDATA[
+ <para>
+ Configure the domains to be searched
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ valid search entry (domain name)
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </search>
+ <routing>
+ <purpose>Routing configuration</purpose>
+ <description><![CDATA[
+ <para>
+ configure alist of routing destinations
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </routing>
+ <routes>
+ <purpose>A List of route entries</purpose>
+ <description><![CDATA[
+ <para>
+ Routing list
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </routes>
+ <route>
+ <purpose>A single route entry</purpose>
+ <description><![CDATA[
+ <para>
+ Add a route entry to the routing list.
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </route>
+ <destination>
+ <purpose>Destination for mail aliases or destination of a
+ routing entry</purpose>
+ <description><![CDATA[
+
+ <itemizedlist>
+ <listitem>
+ <para>
+ Routing entry destination
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Destination of an alias for incoming mail.
+ </para>
+ </listitem>
+ </itemizedlist>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Shared Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ string
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </destination>
+ <software>
+ <purpose>Configure Software selections and packages</purpose>
+ <description><![CDATA[
+ <para>
+ Configure Software selections and packages
+ </para>
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </software>
+ <base>
+ <purpose>Configure base software selection</purpose>
+ <description><![CDATA[
+
+ <para>
+ Base software selection
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ A software selection name as described in table <link
+ linkend="StandardSL" endterm="StandardSL.title"></link>
+ </para>
+ </refsect2>
+ <refsect2><title>&alice; Compatibility</title>
+ <para>This property is replaces the following tags in
&alice;
+ </para>
+ <itemizedlist>
+ <listitem><para>&lt;SYS_SW_SELECTION&gt;</para><para>Only the
+ name of the selection is required. The extention <emphasis>.sel</emphasis>
+ should be ommited.</para></listitem>
+ </itemizedlist>
+
+ </refsect2>
+
+ ]]></description>
+ </base>
+ <addons>
+ <purpose>Configure add-on software selections</purpose>
+ <description><![CDATA[
+
+ <para>
+ Add-on software selection
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </addons>
+ <addon>
+ <purpose>Add-on software selection</purpose>
+ <description><![CDATA[
+
+ <para>
+ Add-on software selection
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+
+ <refsect2><title>Value</title>
+ <para>
+ A software selection name as described in table <link
+ linkend="StandardSL" endterm="StandardSL.title"></link>
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </addon>
+ <packages>
+ <purpose>A list of packages to install</purpose>
+ <description><![CDATA[
+
+ <para>
+ A list of packages to install
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </packages>
+ <package>
+ <purpose>Packages that are not part of any selections and
+ custom packages</purpose>
+ <description><![CDATA[
+
+ <para>
+ Add Packages that are not part of any selections and custom
packages.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+
+ <refsect2><title>Value</title>
+ <para>
+ A package name available in in the package repository.
+ </para>
+ </refsect2>
+
+ ]]></description>
+ </package>
+ <chroot-scripts>
+ <purpose>A list of post-install scripts (Chroot
+ environment)</purpose>
+ <description><![CDATA[
+
+ <para>
+ A list of scripts that get executed before the system boots for
the first
+ time and before the actual system is mounted, hence chroot
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </chroot-scripts>
+ <pre-scripts>
+ <purpose>A list of pre-install scripts</purpose>
+ <description><![CDATA[
+
+ <para>
+ A list of scripts that get executed before the system is installed.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </pre-scripts>
+ <post-scripts>
+ <purpose>A list of post-install scripts</purpose>
+ <description><![CDATA[
+
+ <para>
+ A list of scripts that get executed after the system is installed.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </post-scripts>
+ <script>
+ <purpose>A custom shell or perl script </purpose>
+ <description><![CDATA[
+
+ <para>
+ Custom scripts can be executed in 3 different stages of the installation
+ to give the user maximum flexibility configuring the system.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Shared Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </script>
+ <source>
+ <purpose>Source of a custom shell or perl script</purpose>
+ <description><![CDATA[
+
+ <para>
+ Custom scripts can be executed in 3 different stages of the
installation
+ to give the user maximum flexibility configuring the system.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ CDATA Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Source code of a custom script. Source must be included in CDATA
tags.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </source>
+ <filename>
+ <purpose>File name of a custom user script</purpose>
+ <description><![CDATA[
+
+ <para>
+ Name of the script file
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Unique string
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </filename>
+ <interpreter>
+ <purpose>The interpreter to be used with a specific
+ script</purpose>
+ <description><![CDATA[
+
+ <para>
+ Perl scripts can only be used in post-install. Shell scripts can
be used
+ throughout the entire installation.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ perl or shell
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </interpreter>
+ <partitioning>
+ <purpose>Resource controlling partitioning of hard
+ drives</purpose>
+ <description><![CDATA[
+
+ <para>
+ A List of drives with partition data and partitioning behaviour.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </partitioning>
+ <drive>
+ <purpose>Drive descriptions and partition plans</purpose>
+ <description><![CDATA[
+
+ <para>
+ A List of drives with partition data and partitioning behaviour.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </drive>
+ <partitions>
+ <purpose>List of partitions in a drive</purpose>
+ <description><![CDATA[
+
+ <para>
+ A List of partitions in a drive.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </partitions>
+ <use>
+ <purpose>Determine how to handle existing partitions on a
+ target drive</purpose>
+ <description><![CDATA[
+
+ <para>
+ Determine how to handle existing partitions on a target drive
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ all, free, or a list of partition numbers to be used for the
installation.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </use>
+ <partition>
+ <purpose>Partition data</purpose>
+ <description><![CDATA[
+
+ <para>
+ Partition data
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </partition>
+ <crypt_fs>
+ <purpose>Determine if a specific partition should be
+ encrypted</purpose>
+ <description><![CDATA[
+
+ <para>
+ Determine if a specific partition should be encrypted
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ boolean
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </crypt_fs>
+ <crypt_key>
+ <purpose>Crypt key for a crypted filesystem</purpose>
+ <description><![CDATA[
+
+ <para>
+ Set the crypt key for a file system.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ string
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </crypt_key>
+ <files>
+ <purpose>List of configuration files</purpose>
+ <description><![CDATA[
+
+ <para>
+ List of files tp be copied into the target system.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </files>
+ <config_file>
+ <purpose>Copy a complete configuration file to target
+ system</purpose>
+ <description><![CDATA[
+
+ <para>
+ This resource lets you define a configuration file to be copied or
dumped
+ into the the target system.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </config_file>
+ <file_contents>
+ <purpose>Contents of a configuration file</purpose>
+ <description><![CDATA[
+
+ <para>
+ The source of a configuration file.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ CDATA Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Any data
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </file_contents>
+ <file_path>
+ <purpose>The location of the configuration file</purpose>
+ <description><![CDATA[
+
+ <para>
+ Define where to copy a configuration file in the target system.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ String representing a path.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </file_path>
+ <runlevels>
+ <purpose>Configure runlevels and services</purpose>
+ <description><![CDATA[
+
+ <para>
+ Configure what runlevel should the system boot to and what services
+ should be started.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </runlevels>
+ <services>
+ <purpose>Configure services</purpose>
+ <description><![CDATA[
+
+ <para>
+ Configure what services should be started.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </services>
+ <service>
+ <purpose>Configure service runlevels</purpose>
+ <description><![CDATA[
+
+ <para>
+ Configure in what runlevels should a services be started or
stopped.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </service>
+ <default>
+ <purpose>Default Runlevel</purpose>
+ <description><![CDATA[
+
+ <para>
+ Define the default runlevel.
+ </para>
+ <para>As specifed in <filename>/etc/inittab</filename>, the following run
+ levels are possible</para>
+ <screen>
+# runlevel 0 is System halt (Do not use this for initdefault!)
+# runlevel 1 is Single user mode
+# runlevel 2 is Local multiuser without remote network (e.g. NFS)
+# runlevel 3 is Full multiuser with network
+# runlevel 4 is Not used
+# runlevel 5 is Full multiuser with network and xdm
+# runlevel 6 is System reboot (Do not use this for initdefault!)
+</screen>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ A number representing the runlevel.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </default>
+ <service_name>
+ <purpose>Service name</purpose>
+ <description><![CDATA[
+ <para>
+ Service name. Normally this is the name of a script available in
<filename>/etc/init.d</filename>.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ String, service must be available in <filename>/etc/init.d</filename>
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </service_name>
+ <service_start>
+ <purpose>Runlevels to start a service in</purpose>
+ <description><![CDATA[
+ <para>
+ A space seperated list of runlevels this service should be started in.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ String (Space seperated list of numbers)
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </service_start>
+ <service_stop>
+ <purpose>Runlevels to stop a service in</purpose>
+ <description><![CDATA[
+ <para>
+ A space seperated list of runlevels this service should be stopped in.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ String (Space seperated list of numbers)
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </service_stop>
+ <encryption_method>
+ <purpose>Encryption Method for passwords</purpose>
+ <description><![CDATA[
+ <para>
+ <emphasis>DES</emphasis>, the Linux default method, works in all
+ network environments, but it restricts you to passwords no longer than
+ eight characters. <emphasis>MD5</emphasis> allows longer passwords,
+ thus provides more security, but some network protocols don't support
+ this, and you may have problems with NIS.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ &des; or &md5;, default is &md5;
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </encryption_method>
+ <ldap>
+ <purpose>Authenticate users with an OpenLDAP server</purpose>
+ <description><![CDATA[
+ <para>
+ Using this resource, the target machine can be set up as a
+<emphasis>LDAP client</emphasis> to authenticate users with an OpenLDAP server.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+
+ ]]></description>
+ </ldap>
+ <ldap_domain>
+ <purpose>LDAP search base</purpose>
+ <description><![CDATA[
+ <para>
+Enter the name of the search base (base DN, e.g, dc=mydomain,dc=com)
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ base DN, e.g, dc=mydomain,dc=com
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </ldap_domain>
+ <ldap_server>
+ <purpose>LDAP server</purpose>
+ <description><![CDATA[
+ <para>IP address of the LDAP server
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ IP address.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </ldap_server>
+ <ldap_v2>
+ <purpose>Use LDAP protocol version 2</purpose>
+ <description><![CDATA[
+ <para>Normally, the &ldap; version 3 protocol
+will be used. If you have a &ldap; server using protocol 2 (for example
+&openldap; v1), you should activate <emphasis>&ldap; Version 2</emphasis>
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ IP address.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </ldap_v2>
+ <start_ldap>
+ <purpose>Activate machine as LDAP client</purpose>
+ <description><![CDATA[
+
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Boolean
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </start_ldap>
+ <nis>
+ <purpose>Authenticate users with a NIS server</purpose>
+ <description><![CDATA[
+
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+
+ ]]></description>
+ </nis>
+ <nfs>
+ <purpose>Configure NFS mounts</purpose>
+ <description><![CDATA[
+ <para>
+ Add NFS mounts
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+
+ ]]></description>
+ </nfs>
+ <nfs_entry>
+ <purpose>Configure NFS mounts</purpose>
+ <description><![CDATA[
+ <para>
+ One &nfs; entry to be added in thr <filename>/etc/fstab</filename> file.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+
+ ]]></description>
+ </nfs_entry>
+ <nfs_options>
+ <purpose>NFS mount options</purpose>
+ <description><![CDATA[
+ <para>Options for a &nfs; entry as described in the
+ <emphasis>fstab(5)</emphasis> man page.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Valid options as described in <emphasis>fstab(5)</emphasis>
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </nfs_options>
+ <server_path>
+ <purpose>NFS server and path</purpose>
+ <description><![CDATA[
+
+
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Network path for the exported file system (i.e. 192.168.1.1:/exported)
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </server_path>
+ <nis_server>
+ <purpose>NIS server</purpose>
+ <description><![CDATA[
+ <para>&ip; address of the &nis; server
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ &ip; address.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </nis_server>
+ <nisplus_server>
+ <purpose>NIS+ server</purpose>
+ <description><![CDATA[
+ <para>&ip; address of the &nisplus; server
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ &ip; address.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </nisplus_server>
+ <nis_domain>
+ <purpose>NIS Domain</purpose>
+ <description><![CDATA[
+ <para>
+Enter the name of the &nis; domain, i.e. host.com
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Valid domain name
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </nis_domain>
+ <nis_servers>
+ <purpose>NIS server</purpose>
+ <description><![CDATA[
+ <para>&ip; addresses of the &nis; servers
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+
+ ]]></description>
+ </nis_servers>
+ <start_autofs>
+ <purpose>Start Autofs</purpose>
+ <description><![CDATA[
+ <para>
+Automounter is a daemon that mounts directories automatically.
+It is assumed that its configuration files (auto.*) already exist,
+either locally or over &nis;.
+
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Boolean
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </start_autofs>
+ <start_nis>
+ <purpose>Activate machine as NIS client</purpose>
+ <description><![CDATA[
+
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Boolean
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </start_nis>
+ <nisplus_domain>
+ <purpose>NIS+ Domain</purpose>
+ <description><![CDATA[
+ <para>
+Enter the name of the &nisplus; domain, i.e. host.com
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Valid domain name
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </nisplus_domain>
+ <nisplus>
+ <purpose>NIS+ Domain Configuration</purpose>
+ <description><![CDATA[
+ <para>
+Configure client as &nisplus; client.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </nisplus>
+ <start_nisplus>
+ <purpose>Activate machine as NIS+ client</purpose>
+ <description><![CDATA[
+
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Boolean
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </start_nisplus>
+ <extra_packages>
+ <purpose>Packages that are not part of SuSE Linux</purpose>
+ <description><![CDATA[
+
+ <para>
+ This resource lets you add packages which are not part of
&company-suse; Linux.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </extra_packages>
+ <kernel>
+ <purpose>Specify a kernel package different than the
standard</purpose>
+ <description><![CDATA[
+ <para>
+ Specify a kernel package different than the standard
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ String (Package name without the .rpm extension)
+ </para>
+ </refsect2>
+ <refsect2><title>&alice; Compatibility</title>
+ <para>This property is replaces the following tags in
&alice;
+ </para>
+ <itemizedlist>
+ <listitem><para>&lt;SYS_INST_KERNEL&gt;</para></listitem>
+ </itemizedlist>
+
+ </refsect2>
+
+
+ ]]></description>
+ </kernel>
+ <package_location>
+ <purpose>Location of non-SuSE packages on installation
medium</purpose>
+ <description><![CDATA[
+ <para>
+ Location of the extra package. This directory should be available in the
+ same directory where all other RPMs are, in <filename>suse</filename>
+ sub-directory of the installation root.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ String
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </package_location>
+ <filesystem>
+ <purpose>File system used for a certain partition</purpose>
+ <description><![CDATA[
+ <para>
+ Define which type of filesystem should be used on a certain partition.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ reiser, jfs, xfs, ext2, ext3.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </filesystem>
+ <mount>
+ <purpose>Mount point for a partition</purpose>
+ <description><![CDATA[
+ <para>
+ Define the mount point of a partition during installation.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Valid string representing a mountpoint (i.e. <filename>/local</filename>)
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </mount>
+ <size>
+ <purpose>Size of a partition</purpose>
+ <description><![CDATA[
+ <para>
+ Set the size of a partition.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Size in MB or GB, i.e. 1gb or 1500mb.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </size>
+ <mount_point>
+ <purpose>Mount point for a NFS entry</purpose>
+ <description><![CDATA[
+ <para>
+ Define the mount point of a NFS entry
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Valid string representing a mountpoint (i.e. <filename>/local</filename>)
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </mount_point>
+ <module>
+ <purpose>Kernel module of a netwrok interface</purpose>
+ <description><![CDATA[
+ <para>
+ Kernel module of a netwrok interface
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ String representing a kernel module for a network interface.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </module>
+ <filesystem_id>
+ <purpose>File system ID used for a certain partition</purpose>
+ <description><![CDATA[
+ <para>
+ Define which filesystem ID should be used on a certain partition.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ The id f the file system as can be seen in <command>fdisk</command>
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </filesystem_id>
+ <format>
+ <purpose>Specify if a certain partition should be
formatted</purpose>
+ <description><![CDATA[
+ <para>Specify if a certain partition should be formatted
+
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Boolean value
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </format>
+ <gateway>
+ <purpose>Gateway</purpose>
+ <description><![CDATA[
+ <para>
+ Configure a gateway for routing IP trafic
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ IP of a gateway
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </gateway>
+ <sysconfig>
+ <purpose>Set Sysconfig variables</purpose>
+ <description><![CDATA[
+
+ <para>
+ Use this resource to set syscofnig variables in
<filename>/etc/sysconfig</filename>
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </sysconfig>
+ <sysconfig_entry>
+ <purpose>Set a Sysconfig variable</purpose>
+ <description><![CDATA[
+
+ <para>
+ Use this resource to set syscofnig variable in
<filename>/etc/sysconfig</filename>
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </sysconfig_entry>
+ <sysconfig_key>
+ <purpose>Sysconfig variable key</purpose>
+ <description><![CDATA[
+ <para>
+ The key of a sysconfig variable or the variable itself
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Any variable defined in a sysconfig file in
<filename>/etc/sysconfig</filename>
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </sysconfig_key>
+ <sysconfig_value>
+ <purpose>Sysconfig variable value</purpose>
+ <description><![CDATA[
+ <para>
+ The value of a sysconfig variable
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Any value and according to specification defined in the sysconfig file.li
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </sysconfig_value>
+ <sysconfig_path>
+ <purpose>Sysconfig variable file path</purpose>
+ <description><![CDATA[
+ <para>
+ The path to a sysconfig file relative to
<filename>/etc/sysconfig</filename>
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ File path relative to <filename>/etc/sysconfig</filename>
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </sysconfig_path>
+ <lvm>
+ <purpose>LVM Configuration</purpose>
+ <description><![CDATA[
+
+ <para>
+ Configure LVM
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </lvm>
+ <lvm_group>
+ <purpose>LVM Group</purpose>
+ <description><![CDATA[
+
+ <para>
+ Configure a LVM Group
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </lvm_group>
+ <logical_volumes>
+ <purpose>Add LVM Logical Volumes</purpose>
+ <description><![CDATA[
+
+ <para>
+ Configure LVM logical volumes.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ List Resource
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </logical_volumes>
+ <lv>
+ <purpose>LVM Logical Volume data</purpose>
+ <description><![CDATA[
+ <para>
+ Logical Volume data
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Resource
+ </para>
+ </refsect2>
+
+
+
+
+ ]]></description>
+ </lv>
+ <lv_fs>
+ <purpose>File system of a LVM logical volume</purpose>
+ <description><![CDATA[
+ <para>
+ File system to use on a LVM logical volume.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ One of the following: ext2, ext3, reiser, jfs or xfs
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </lv_fs>
+ <lv_mount>
+ <purpose>Mount point of a LVM logical volume</purpose>
+ <description><![CDATA[
+ <para>
+ Mount point of a LVM logical volume.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Valid mount point.
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </lv_mount>
+ <lv_name>
+ <purpose>Name of a LVM logical volume</purpose>
+ <description><![CDATA[
+ <para>
+ Name of a LVM logical volume.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Name of the volume, i.e. <emphasis>optlv</emphasis>
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </lv_name>
+ <lv_size>
+ <purpose>Size of a LVM logical volume</purpose>
+ <description><![CDATA[
+ <para>
+ Size of a LVM logical volume.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Size of the volume, i.e. <emphasis>2gb</emphasis> or
<emphasis>1500mb</emphasis>
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </lv_size>
+ <lvm_name>
+ <purpose>Name of the LVM Group</purpose>
+ <description><![CDATA[
+ <para>
+ Name of a LVM Group.
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+ <refsect2><title>Value</title>
+ <para>
+ Normally called <emphasis>System</emphasis>
+ </para>
+ </refsect2>
+
+
+
+ ]]></description>
+ </lvm_name>
+ <pesize>
+ <purpose>LVM Physical Extent Size</purpose>
+ <description><![CDATA[
+ <para>
+ LVM Physical Extent Size
+ </para>
+
+
+ <refsect2><title>Type</title>
+ <para>
+ Property
+ </para>
+ </refsect2>
+
+
+
+
+ ]]></description>
+ </pesize>
+</purposes>

Added: trunk/autoinstallation/doc/xml/web
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/web?rev=65274&view=auto
==============================================================================
--- trunk/autoinstallation/doc/xml/web (added)
+++ trunk/autoinstallation/doc/xml/web Mon Aug 8 14:12:13 2011
@@ -0,0 +1 @@
+link ../web
\ No newline at end of file

--
To unsubscribe, e-mail: yast-commit+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-commit+help@xxxxxxxxxxxx

< Previous Next >
This Thread
  • No further messages