Mailinglist Archive: yast-commit (265 mails)
| < Previous | Next > |
[yast-commit] r67161 - in /trunk/autoinstallation/doc/xml: ASKSection.xml PartitioningSection.xml SoftwareSection.xml
- From: ug@xxxxxxxxxxxxxxxxx
- Date: Thu, 12 Jan 2012 13:53:21 -0000
- Message-id: <20120112135321.AF1FE3251E@svn2.opensuse.org>
Author: ug
Date: Thu Jan 12 14:53:20 2012
New Revision: 67161
URL: http://svn.opensuse.org/viewcvs/yast?rev=67161&view=rev
Log:
docu fixed
Modified:
trunk/autoinstallation/doc/xml/ASKSection.xml
trunk/autoinstallation/doc/xml/PartitioningSection.xml
trunk/autoinstallation/doc/xml/SoftwareSection.xml
Modified: trunk/autoinstallation/doc/xml/ASKSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/ASKSection.xml?rev=67161&r1=67160&r2=67161&view=diff
==============================================================================
--- trunk/autoinstallation/doc/xml/ASKSection.xml (original)
+++ trunk/autoinstallation/doc/xml/ASKSection.xml Thu Jan 12 14:53:20 2012
@@ -96,18 +96,18 @@
</row>
<row>
<entry>path (deprecated since openSUSE 11.0 - use
pathlist)</entry>
- <entry><para>The path to the element in the profile. It's a
comma seperated list of elements that describes the
+ <entry><para>deprecated
+ </para><screen>deprecated</screen></entry>
+ <entry>deprecated</entry>
+ </row>
+ <row>
+ <entry><para>pathlist (available since openSUSE 11.0 and
replaces <emphasis>path</emphasis>)</para></entry>
+ <entry><para>A list of <emphasis>path</emphasis> elements. A
path is 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 <ldap><ldap_server> 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 <users config:type="list">
list of users in the profile.
-
</para><screen><path>networking,dns,hostname</path></screen></entry>
- <entry>This information is optional, but you should at least
provide <emphasis>path</emphasis> or <emphasis>file</emphasis>.</entry>
- </row>
- <row>
- <entry><para>pathlist (available since openSUSE 11.0 and
replaces <emphasis>path</emphasis>)</para></entry>
- <entry><para>A list of <emphasis>path</emphasis> elements (see
above).
</para><screen><pathlist config:type="list"
><path>networking,dns,hostname</path>
<path>...</path></screen></entry>
@@ -165,22 +165,22 @@
</row>
<row>
<entry>dialog (available since SL 10.3 and SLES10 SP2)</entry>
- <entry><para>Since OpenSUSE 10.3, you can ask more than one
question per dialog. To do so, specifiy the dialog-id with an integer. All
questions with the same dialog-id belong to the same dialog.
+ <entry><para>you can ask more than one question per dialog. To
do so, specifiy the dialog-id with an integer. All questions with the same
dialog-id belong to the same dialog.
The dialogs are sorted by the id too.
</para><screen><dialog
config:type="integer">3</dialog></screen></entry>
<entry>Optional.</entry>
</row>
<row>
<entry>element (available since SL 10.3 and SLES10 SP2)</entry>
- <entry><para>Since OpenSUSE 10.3, you can have more than one
question per dialog. To make that possible you have
+ <entry><para>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 in a
dialog are sorted by id.
</para><screen><element
config:type="integer">1</element></screen></entry>
<entry>Optional (see dialog>.</entry>
</row>
<row>
<entry>frametitle (available since SL 10.3 and SLES10
SP2)</entry>
- <entry><para>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 frame title, a small caption for each
question. Since openSUSE 11.3, you can put multiple elements into one frame.
They have to have the same frame title.
+ <entry><para>you can have more than one question per dialog.
Each question on a dialog has
+ a frame that can have a frame title, a small caption for each
question. You can put multiple elements into one frame. They have to have the
same frame title.
</para><screen><frametitle>User
data</frametitle></screen></entry>
<entry>Optional. Default is no frame title.</entry>
</row>
@@ -295,7 +295,7 @@
<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>rerun_on_error</entry>
<entry><para>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 display an error with the "feedback" option.
</para><screen><rerun_on_error
config:type="boolean">true</rerun_on_error></screen></entry>
<entry>Optional, default is "false". This value should be used
together with the feedback option.</entry>
@@ -407,7 +407,7 @@
</script>
</ask></screen>
<para>
-Since openSUSE 11.0, you can verify the answer of a question with a script
like this:
+you can verify the answer of a question with a script like this:
</para>
<screen><ask>
Modified: trunk/autoinstallation/doc/xml/PartitioningSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/PartitioningSection.xml?rev=67161&r1=67160&r2=67161&view=diff
==============================================================================
--- trunk/autoinstallation/doc/xml/PartitioningSection.xml (original)
+++ trunk/autoinstallation/doc/xml/PartitioningSection.xml Thu Jan 12 14:53:20
2012
@@ -52,10 +52,10 @@
<tbody>
<row>
<entry>device</entry>
- <entry><para>The device you want to configure in this section.
You can use persistent device names via id, like
<emphasis>/dev/disk/by-id/ata-WDC_WD3200AAKS-75L9A0_WD-WMAV27368122</emphasis>
or <emphasis>by-path</emphasis>,like
<emphasis>/dev/disk/by-path/pci-0001:00:03.0-scsi-0:0:0:0</emphasis>.</para>
+ <entry><para>The device you want to configure in this
<drive> section. You can use persistent device names via id, like
<emphasis>/dev/disk/by-id/ata-WDC_WD3200AAKS-75L9A0_WD-WMAV27368122</emphasis>
or <emphasis>by-path</emphasis>,like
<emphasis>/dev/disk/by-path/pci-0001:00:03.0-scsi-0:0:0:0</emphasis>.</para>
<screen><device>/dev/hda</device></screen>
</entry>
- <entry>Optional. If left out, &ay; tries to guess the device.
A RAID must always have "/dev/md" as device.</entry>
+ <entry>Optional. If left out, &ay; tries to guess the device
(on openSUSE 12.2 and SLES11 SP2 you can influess the guessing - see below this
table for instructions on how to do that). A RAID must always have "/dev/md" as
device.</entry>
</row>
<row>
<entry>initialize</entry>
@@ -169,8 +169,37 @@
</tbody>
</tgroup>
</informaltable>
- </section>
-
+ <para>Since openSUSE 12.2 and SLES11 SP2 you can influence the
device-guessing of AutoYaST for the case that you don't specify a
<device> entry on your own. Usually AutoYaST would use the first device
it can find and that looks reasonable but you can configure to skip some
devices like this:
+</para>
+<screen>
+<partitioning config:type="list">
+ <drive>
+ <initialize config:type="boolean">true</initialize>
+ <!-- the skip_list is optional and available since openSUSE 12.2 and
SLES11 SP2 -->
+ <skip_list config:type="list">
+ <listentry>
+ <!-- skip devices that use the usb-storage driver -->
+ <skip_key>driver</skip_key>
+ <skip_value>usb-storage</skip_value>
+ </listentry>
+ <listentry>
+ <!-- skip devices that are smaller than 1GB -->
+ <skip_key>size_k</skip_key>
+ <skip_value>1048576</skip_value>
+ <skip_if_less_than
config:type="boolean">true</skip_if_less_than>
+ </listentry>
+ <listentry>
+ <!-- skip devices that are larger than 100GB -->
+ <skip_key>size_k</skip_key>
+ <skip_value>104857600</skip_value>
+ <skip_if_more_than
config:type="boolean">true</skip_if_more_than>
+ </listentry>
+ </skip_list>
+ ...
+</screen><para>
+For a list of all possible <skip_key>, run "yast2 ayast_probe" on
openSUSE 12.2 or SLES11SP2
+ </para>
+</section>
<section>
<title>Partition Configuration</title>
<para>
Modified: trunk/autoinstallation/doc/xml/SoftwareSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/SoftwareSection.xml?rev=67161&r1=67160&r2=67161&view=diff
==============================================================================
--- trunk/autoinstallation/doc/xml/SoftwareSection.xml (original)
+++ trunk/autoinstallation/doc/xml/SoftwareSection.xml Thu Jan 12 14:53:20 2012
@@ -95,14 +95,6 @@
<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 with 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
--
To unsubscribe, e-mail: yast-commit+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-commit+help@xxxxxxxxxxxx
Date: Thu Jan 12 14:53:20 2012
New Revision: 67161
URL: http://svn.opensuse.org/viewcvs/yast?rev=67161&view=rev
Log:
docu fixed
Modified:
trunk/autoinstallation/doc/xml/ASKSection.xml
trunk/autoinstallation/doc/xml/PartitioningSection.xml
trunk/autoinstallation/doc/xml/SoftwareSection.xml
Modified: trunk/autoinstallation/doc/xml/ASKSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/ASKSection.xml?rev=67161&r1=67160&r2=67161&view=diff
==============================================================================
--- trunk/autoinstallation/doc/xml/ASKSection.xml (original)
+++ trunk/autoinstallation/doc/xml/ASKSection.xml Thu Jan 12 14:53:20 2012
@@ -96,18 +96,18 @@
</row>
<row>
<entry>path (deprecated since openSUSE 11.0 - use
pathlist)</entry>
- <entry><para>The path to the element in the profile. It's a
comma seperated list of elements that describes the
+ <entry><para>deprecated
+ </para><screen>deprecated</screen></entry>
+ <entry>deprecated</entry>
+ </row>
+ <row>
+ <entry><para>pathlist (available since openSUSE 11.0 and
replaces <emphasis>path</emphasis>)</para></entry>
+ <entry><para>A list of <emphasis>path</emphasis> elements. A
path is 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 <ldap><ldap_server> 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 <users config:type="list">
list of users in the profile.
-
</para><screen><path>networking,dns,hostname</path></screen></entry>
- <entry>This information is optional, but you should at least
provide <emphasis>path</emphasis> or <emphasis>file</emphasis>.</entry>
- </row>
- <row>
- <entry><para>pathlist (available since openSUSE 11.0 and
replaces <emphasis>path</emphasis>)</para></entry>
- <entry><para>A list of <emphasis>path</emphasis> elements (see
above).
</para><screen><pathlist config:type="list"
><path>networking,dns,hostname</path>
<path>...</path></screen></entry>
@@ -165,22 +165,22 @@
</row>
<row>
<entry>dialog (available since SL 10.3 and SLES10 SP2)</entry>
- <entry><para>Since OpenSUSE 10.3, you can ask more than one
question per dialog. To do so, specifiy the dialog-id with an integer. All
questions with the same dialog-id belong to the same dialog.
+ <entry><para>you can ask more than one question per dialog. To
do so, specifiy the dialog-id with an integer. All questions with the same
dialog-id belong to the same dialog.
The dialogs are sorted by the id too.
</para><screen><dialog
config:type="integer">3</dialog></screen></entry>
<entry>Optional.</entry>
</row>
<row>
<entry>element (available since SL 10.3 and SLES10 SP2)</entry>
- <entry><para>Since OpenSUSE 10.3, you can have more than one
question per dialog. To make that possible you have
+ <entry><para>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 in a
dialog are sorted by id.
</para><screen><element
config:type="integer">1</element></screen></entry>
<entry>Optional (see dialog>.</entry>
</row>
<row>
<entry>frametitle (available since SL 10.3 and SLES10
SP2)</entry>
- <entry><para>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 frame title, a small caption for each
question. Since openSUSE 11.3, you can put multiple elements into one frame.
They have to have the same frame title.
+ <entry><para>you can have more than one question per dialog.
Each question on a dialog has
+ a frame that can have a frame title, a small caption for each
question. You can put multiple elements into one frame. They have to have the
same frame title.
</para><screen><frametitle>User
data</frametitle></screen></entry>
<entry>Optional. Default is no frame title.</entry>
</row>
@@ -295,7 +295,7 @@
<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>rerun_on_error</entry>
<entry><para>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 display an error with the "feedback" option.
</para><screen><rerun_on_error
config:type="boolean">true</rerun_on_error></screen></entry>
<entry>Optional, default is "false". This value should be used
together with the feedback option.</entry>
@@ -407,7 +407,7 @@
</script>
</ask></screen>
<para>
-Since openSUSE 11.0, you can verify the answer of a question with a script
like this:
+you can verify the answer of a question with a script like this:
</para>
<screen><ask>
Modified: trunk/autoinstallation/doc/xml/PartitioningSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/PartitioningSection.xml?rev=67161&r1=67160&r2=67161&view=diff
==============================================================================
--- trunk/autoinstallation/doc/xml/PartitioningSection.xml (original)
+++ trunk/autoinstallation/doc/xml/PartitioningSection.xml Thu Jan 12 14:53:20
2012
@@ -52,10 +52,10 @@
<tbody>
<row>
<entry>device</entry>
- <entry><para>The device you want to configure in this section.
You can use persistent device names via id, like
<emphasis>/dev/disk/by-id/ata-WDC_WD3200AAKS-75L9A0_WD-WMAV27368122</emphasis>
or <emphasis>by-path</emphasis>,like
<emphasis>/dev/disk/by-path/pci-0001:00:03.0-scsi-0:0:0:0</emphasis>.</para>
+ <entry><para>The device you want to configure in this
<drive> section. You can use persistent device names via id, like
<emphasis>/dev/disk/by-id/ata-WDC_WD3200AAKS-75L9A0_WD-WMAV27368122</emphasis>
or <emphasis>by-path</emphasis>,like
<emphasis>/dev/disk/by-path/pci-0001:00:03.0-scsi-0:0:0:0</emphasis>.</para>
<screen><device>/dev/hda</device></screen>
</entry>
- <entry>Optional. If left out, &ay; tries to guess the device.
A RAID must always have "/dev/md" as device.</entry>
+ <entry>Optional. If left out, &ay; tries to guess the device
(on openSUSE 12.2 and SLES11 SP2 you can influess the guessing - see below this
table for instructions on how to do that). A RAID must always have "/dev/md" as
device.</entry>
</row>
<row>
<entry>initialize</entry>
@@ -169,8 +169,37 @@
</tbody>
</tgroup>
</informaltable>
- </section>
-
+ <para>Since openSUSE 12.2 and SLES11 SP2 you can influence the
device-guessing of AutoYaST for the case that you don't specify a
<device> entry on your own. Usually AutoYaST would use the first device
it can find and that looks reasonable but you can configure to skip some
devices like this:
+</para>
+<screen>
+<partitioning config:type="list">
+ <drive>
+ <initialize config:type="boolean">true</initialize>
+ <!-- the skip_list is optional and available since openSUSE 12.2 and
SLES11 SP2 -->
+ <skip_list config:type="list">
+ <listentry>
+ <!-- skip devices that use the usb-storage driver -->
+ <skip_key>driver</skip_key>
+ <skip_value>usb-storage</skip_value>
+ </listentry>
+ <listentry>
+ <!-- skip devices that are smaller than 1GB -->
+ <skip_key>size_k</skip_key>
+ <skip_value>1048576</skip_value>
+ <skip_if_less_than
config:type="boolean">true</skip_if_less_than>
+ </listentry>
+ <listentry>
+ <!-- skip devices that are larger than 100GB -->
+ <skip_key>size_k</skip_key>
+ <skip_value>104857600</skip_value>
+ <skip_if_more_than
config:type="boolean">true</skip_if_more_than>
+ </listentry>
+ </skip_list>
+ ...
+</screen><para>
+For a list of all possible <skip_key>, run "yast2 ayast_probe" on
openSUSE 12.2 or SLES11SP2
+ </para>
+</section>
<section>
<title>Partition Configuration</title>
<para>
Modified: trunk/autoinstallation/doc/xml/SoftwareSection.xml
URL:
http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/SoftwareSection.xml?rev=67161&r1=67160&r2=67161&view=diff
==============================================================================
--- trunk/autoinstallation/doc/xml/SoftwareSection.xml (original)
+++ trunk/autoinstallation/doc/xml/SoftwareSection.xml Thu Jan 12 14:53:20 2012
@@ -95,14 +95,6 @@
<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 with 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
--
To unsubscribe, e-mail: yast-commit+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-commit+help@xxxxxxxxxxxx
| < Previous | Next > |