YaST Commits
Threads by month
- ----- 2024 -----
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
November 2011
- 21 participants
- 322 discussions
[yast-commit] r66713 - /trunk/autoinstallation/doc/xml/GeneralSection.xml
by emap@svn2.opensuse.org 05 Nov '11
by emap@svn2.opensuse.org 05 Nov '11
05 Nov '11
Author: emap
Date: Sat Nov 5 11:57:49 2011
New Revision: 66713
URL: http://svn.opensuse.org/viewcvs/yast?rev=66713&view=rev
Log:
edited by emap
Modified:
trunk/autoinstallation/doc/xml/GeneralSection.xml
Modified: trunk/autoinstallation/doc/xml/GeneralSection.xml
URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/General…
==============================================================================
--- trunk/autoinstallation/doc/xml/GeneralSection.xml (original)
+++ trunk/autoinstallation/doc/xml/GeneralSection.xml Sat Nov 5 11:57:49 2011
@@ -31,34 +31,37 @@
<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 <general><mode> section
+ The mode section configures the behavior of &ay; with regard to confirmation and rebooting. The following has to be in the <general><mode> 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><remark>emap 2011-11-05: variable name is not specified, I assume it's
+ 'confirm' as in the commented table below.</remark> By default, the user
+ must confirm the auto-installation process. This option allows the user to
+ view and change the settings for a target system before they are committed
+ and can be used for debugging. <emphasis>confirm</emphasis> is set to "true"
+ by default to avoid recursive installs when the system schedules a reboot
+ after initial system setup. Only disable confirmation if you want to carry
+ out a fully unattended installation.
</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
+ With <emphasis>halt</emphasis> you cause &ay; to shut down the machine
+ after all packages have been installed. Instead of a 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.
+ <emphasis>final_halt</emphasis> and <emphasis>final_reboot</emphasis>
+ have been introduced with openSUSE 11.0 and SLES11. You can reboot or
+ halt the machine after installation and configuration are finished at the
+ end of stage 2.
</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>
+ 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. The value "true" will reboot, "false" will
+ not reboot and a missing <emphasis>forceboot</emphasis> option uses the
+ product's default.
+ </para><remark>emap 2011-11-05: Fixed some issues above according to the commented additional information in the table below.</remark>
<!-- FIXME: not allowed inside of example
<informaltable frame='top'>
<tgroup cols="3">
@@ -72,45 +75,45 @@
<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.
+ <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><confirm config:type="boolean">true</confirm></screen></para>
</entry>
- <entry>optional. The default is true</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
+ <entry>Shuts 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><halt config:type="boolean">true</halt></screen></para>
</entry>
- <entry>optional. The default is false</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.
+ <entry>This boolean determines 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><second_stage config:type="boolean">true</second_stage></screen></para>
</entry>
- <entry>optional. The default is true</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)
+ <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><final_reboot config:type="boolean">true</final_reboot></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>
+ <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)
+ <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><final_halt config:type="boolean">true</final_halt></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>
+ <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><forceboot config:type="boolean">true</forceboot></screen></para>
</entry>
- <entry>optional. The default is false.</entry>
+ <entry>Optional. The default is "false".</entry>
</row>
</tbody>
</tgroup>
@@ -124,12 +127,12 @@
<para>
- AutoYaST in openSUSE 11.1 allows you to configure the proposal screen with the <proposals config:type="list">
+ &ay; in openSUSE 11.1 allows you to configure the proposal screen with the <proposals config:type="list">
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.
+ <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):
+ This is the proposal list openSUSE 11.1, which you can also find in the <filename>control.xml</filename> file on the installation source:
</para>
<itemizedlist>
<listitem>
@@ -184,29 +187,34 @@
</listitem>
</itemizedlist>
<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.
+ The <emphasis>wait</emphasis> section has been introduced with openSUSE
+ 11.1 and SLES11. You can let &ay; <command>sleep</command> before and
+ after each module run during the second stage. You can run scripts
+ and/or pass a value (in seconds) for &ay; to sleep. In the example
+ above &ay; will sleep for 15 seconds (10+5) before the network
+ configuration starts 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. They are only used to show how scripts in the wait section
+ work now.
</para>
<note>
- <title>Change starting from SUSE Linux 10.1/SLES10</title>
+ <title>Changes since 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.
+ <emphasis>clock</emphasis> properties in the
+ <emphasis>general</emphasis> resource were moved to the root
+ (<emphasis>profile</emphasis>) element of the autoyast profile. Do
+ not 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.
+ Now you can use the <emphasis>second_stage</emphasis> property to turn off &ay; after the first reboot (set to "false"). Then the complete second stage is a manual installation. Default is "true", which means &ay; 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 or turn off the machine at the end of stage 2.
</para>
<para>
- For the signature-handling, please read the <emphasis>Software</emphasis> chapter
- of this documentation.
+ For signature handling, please read the <emphasis>Software</emphasis>
+ chapter of this documentation.<remark>emap 2011-11-05: Add proper ref?</remark>
</para>
</note>
</section>
--
To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-commit+help(a)opensuse.org
1
0
[yast-commit] r66712 - /trunk/autoinstallation/doc/xml/creating_autoyast2_modules.xml
by emap@svn2.opensuse.org 05 Nov '11
by emap@svn2.opensuse.org 05 Nov '11
05 Nov '11
Author: emap
Date: Sat Nov 5 11:01:08 2011
New Revision: 66712
URL: http://svn.opensuse.org/viewcvs/yast?rev=66712&view=rev
Log:
edited by emap
Modified:
trunk/autoinstallation/doc/xml/creating_autoyast2_modules.xml
Modified: trunk/autoinstallation/doc/xml/creating_autoyast2_modules.xml
URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/creatin…
==============================================================================
--- trunk/autoinstallation/doc/xml/creating_autoyast2_modules.xml (original)
+++ trunk/autoinstallation/doc/xml/creating_autoyast2_modules.xml Sat Nov 5 11:01:08 2011
@@ -4,7 +4,7 @@
<article>
<articleinfo>
- <title>AutoYaST Configuration Management System</title>
+ <title>&ay; Configuration Management System</title>
<author>
<firstname>Anas</firstname>
<surname>Nashif</surname>
@@ -17,47 +17,45 @@
<section>
<title>Introduction</title>
<para>
- The plugin-like design has the following advantages:
+ The plugin-like design of &ay; 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.
+ A new run-time module can be integrated automatically in &ay;.
+ New features in &yast; 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.
+ Only installed run-time modules are offered and used to automatically install
+ the system. This allows the integration of special 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.
+ Code relevant to one run-time configuration module is kept in one place
+ instead of maintaining it in different modules.<remark>emap 2011-11-05: This makes no sense. If the code is only relevant to one module, why should it be stored in different places?</remark>
</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
+ <title>The Run-time Module Interface in &ay;</title>
+ <para>The new interface (aka _auto.ycp client) is similar to the &yast; 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.
+ &ay; to simplify and align the user interface for all modules in the &ay; configuration system.
</para>
<para>
- The interface of a run-time configuration module in AutoYaST has the follwoing
+ The interface of a run-time configuration module in &ay; 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.
+ <emphasis>Summary Area</emphasis>: Contains a summary of the configuration with the respective settings. If values where not configured, the phrase
+ <emphasis>'Not configured yet'</emphasis> is used.
</para>
</listitem>
<listitem>
@@ -69,47 +67,47 @@
<listitem>
<para>
<emphasis>Reset Button</emphasis>: A button for resetting the
- configuration data. This will delete only data in the running module.
+ configuration data. This will only delete 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
+ The data in the summary area is provided by the <emphasis>Summary</emphasis> function in the
+ module controlling 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>
+ <title>Run-time Modules in <emphasis>Auto</emphasis> Mode</title>
<para>
- The <module name>_auto.ycp client accepts 2 arguments:
+ The <module name>_auto.ycp client accepts two arguments:
</para>
<itemizedlist>
<listitem>
<para>
- Function
+ Function,
</para>
</listitem>
<listitem>
<para>
- Configuration Data
+ Configuration Data.
</para>
</listitem>
</itemizedlist>
- <para>The following functions are needed to make any module work in AutoYaST:</para>
+ <para>The following functions are needed for any module to work in &ay;:</para>
<itemizedlist>
<listitem>
<para>
<emphasis>Import:</emphasis></para>
<para>
- Import existing data into the module, usually done only once at the beginning.
+ Imports 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.
+ Provides a brief summary of the configuration.
Calls >Module<::Summary()
</para>
</listitem>
@@ -117,7 +115,7 @@
<para>
<emphasis>Reset:</emphasis></para>
<para>
- Resets the configuration. It returns empty values but it also can return
+ Resets the configuration. It returns empty values, but can also return
default values, depending on the module.
</para>
</listitem>
@@ -125,43 +123,40 @@
<para>
<emphasis>Change:</emphasis></para>
<para>
- This function starts the widget sequence
+ 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 <Module>::Write (and sets <Module>::write_only true)
+ Writes the configuration without displaying any widgets or popups
+ and without restarting any services, etc. Calls
+ <Module>::Write (and sets <Module>::write_only true).
</para>
</listitem>
<listitem>
<para>
<emphasis>Export:</emphasis></para>
<para>
- Returns the current configuration
- Calls <Module>::Export
+ Returns the current configuration, calls <Module>::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
+ Returns a map with two key-value pairs. The first key is
+ <emphasis>install</emphasis>, which has a list as 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.
-
+ <emphasis>remove</emphasis>. Its value contains packages that should
+ be removed to avoid conflicts with other packages. These packages
+ are normally determined dynamically, depending on the configuration.
</para>
<para>
- The function can either return a map directly or it can call a module
+ The function can either return a map or it can call a module
function <Module>::AutoPackages().
</para>
</listitem>
@@ -169,7 +164,7 @@
<para>
The following example shows <module name>_auto.ycp with the changes
- needed for the new behaviour.
+ needed for the new behavior.
</para>
<example>
<title>XXpkgXX_auto.ycp (XXpkgXX = module name)</title>
@@ -265,19 +260,19 @@
</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.
+ <title>Module Functions Needed for Auto-Install</title>
+ <para>The following functions should be available with
+ the modules to provide the functionality needed in &ay;.
</para>
<refentry>
<refnamediv>
<refname>AutoPackages()</refname>
- <refpurpose>Return needed packages for module to work</refpurpose>
+ <refpurpose>Returns 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
+ Returns a map of lists which contain packages to be
installed or removed during installation (second stage).
</para>
@@ -286,7 +281,7 @@
<refsect1>
<title>Returns</title>
<para>
- For example, the function can return the following structure:
+ For example, this function can return the following structure:
</para>
<screen>
$[
@@ -299,38 +294,39 @@
<refentry>
<refnamediv>
<refname>Import()</refname>
- <refpurpose>Imports settings from arguments</refpurpose>
+ <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>This function imports settings from arguments and sets the
+ module variables. The <emphasis>Import</emphasis> function should
+ provide sufficient data 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>Import() returns "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>
+ <refpurpose>Exports configured data to the 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>
+ <para>Exports configured data to the calling module. This function
+ also converts internal variables to unique and human readable
+ variables which can be used in the control file needed for the
+ auto-installation. Do not use configuration data as the key in a
+ key-value pair. The key of the pair must always contain the variable
+ name, rather than its contents.</para>
</refsect1>
<refsect1>
<title>Example</title>
@@ -359,21 +355,21 @@
<refentry>
<refnamediv>
<refname>Write()</refname>
- <refpurpose>Write or commit configured or imported data</refpurpose>
+ <refpurpose>Writes or commits configured or imported data.</refpurpose>
</refnamediv>
<refsect1>
<title>Description</title>
- <para>Commit configured data. This function is also used in normal
+ <para>Commits 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
+ 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.
+ auto-install, which might interfere with the installation widgets.
</para>
</refsect1>
@@ -381,19 +377,19 @@
</section>
<section>
- <title>Configuration file</title>
+ <title>Configuration File</title>
<para>
- When AutoYaST is invoked, it checks for the desktop files in
+ When &ay; 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.
+ later include them in the configuration interface. &ay; uses the same
+ configuration file as the &yast; Control Center with some 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>
+ <title>Auto-Install Configuration File for NIS</title>
<programlisting>
[Desktop Entry]
Type=Application
@@ -423,32 +419,32 @@
</programlisting>
</example>
- <para>In addition to the keywords from the last example, AutoYaST also evaluates
+ <para>In addition to the keywords in the example above, &ay; 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>
+ The &yast; module compatible with the &ay; version. Configurations can be imported and exported.</para>
<itemizedlist>
<title>Values</title>
<listitem>
<para><emphasis>all</emphasis>: Full auto-installation support,
- including the AutoYaST interface and writing configurations
- during autoinstall. </para>
+ including the &ay; interface and writing configurations
+ during auto-install. </para>
</listitem>
<listitem>
- <para><emphasis>write</emphasis>: Write only support. No
- integration into AutoYaST interface. </para>
+ <para><emphasis>write</emphasis>: Write-only support. No
+ integration into the &ay; 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>
+ <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-install. Data is written using the common
+ installation process and modules available in &yast;.</para>
</listitem>
</itemizedlist>
<para> </para>
@@ -456,13 +452,13 @@
<listitem>
<para><emphasis>X-SuSE-YaST-AutoInstPath</emphasis>
- - Path in the control file</para>
+ 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
+ configuration data directly controlling the installation of a system are
contained in the <emphasis>install</emphasis> resource.</para>
</listitem>
</itemizedlist>
@@ -471,11 +467,11 @@
<listitem>
<para><emphasis>X-SuSE-YaST-AutoInstClient</emphasis>
- - Name of the client to call</para>
+ Name of the client to call.</para>
<itemizedlist>
<title>Values</title>
<listitem>
- <para>Name of the client to be called by AutoYaST</para>
+ <para>Name of the client to be called by &ay;.</para>
</listitem>
</itemizedlist>
<itemizedlist>
@@ -489,7 +485,7 @@
<listitem>
<para><emphasis>X-SuSE-YaST-AutoInstDataType</emphasis>
- - Data type of configuration section</para>
+ Data type of configuration section.</para>
<itemizedlist>
<title>Values</title>
<listitem>
@@ -507,7 +503,7 @@
<listitem>
<para><emphasis>X-SuSE-YaST-AutoInstResource</emphasis>
- - Name of the resource in the Profile</para>
+ Name of the resource in the profile.</para>
<itemizedlist>
<title>Values</title>
<listitem>
@@ -525,11 +521,11 @@
<listitem>
<para><emphasis>X-SuSE-YaST-AutoInstRequires</emphasis>
- - What modules are required before this module is run. </para>
+ List of modules required before this module is run. </para>
<itemizedlist>
<title>Values</title>
<listitem>
- <para>comma delimited list of required modules</para>
+ <para>Comma-separated list of required modules.</para>
</listitem>
</itemizedlist>
<itemizedlist>
@@ -545,12 +541,12 @@
<listitem>
<para><emphasis>X-SuSE-YaST-AutoInstMerge</emphasis>
- - Multiple sections in the profile can be handled by one module</para>
+ Multiple sections in the profile to 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>Comma-separated 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>
@@ -566,13 +562,12 @@
<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>
+ Data types of the merged sections 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>
+ <para>Comma-separated list of data types (list or map) for
+ the sections specified in X-SuSE-YaST-AutoInstMerge.</para>
</listitem>
</itemizedlist>
<itemizedlist>
@@ -588,15 +583,15 @@
<listitem>
<para><emphasis>X-SuSE-YaST-AutoInstClonable</emphasis>
- - is this module able to clone the actual system</para>
+ Specify if this module is able to clone a system.</para>
<itemizedlist>
<title>Values</title>
<listitem>
- <para>a boolean (true,false)</para>
+ <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>
+ modules you can choose from during the cloning of a
+ system. The module will Read() and Export() its data from
+ the actual system.</para>
</listitem>
</itemizedlist>
<itemizedlist>
@@ -612,8 +607,8 @@
<listitem>
<para><emphasis>X-SuSE-YaST-AutoInstSchema</emphasis>
- - base name of schema file, including the rnc
- extension (Relax NG compact syntax)</para>
+ Base name of the schema file, including the rnc
+ extension (Relax NG compact syntax).</para>
<itemizedlist>
<title>Values</title>
<listitem>
@@ -631,14 +626,14 @@
<listitem>
<para><emphasis>X-SuSE-YaST-AutoInstOptional</emphasis>
- - is the element optional in the schema</para>
+ Specify if the element is 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>
+ <para>a boolean (true, false)</para>
+ <para>Is this element mandatory or optional in the
+ profile? Unless you have a very basic module, it is
+ always optional and therefore "true".</para>
</listitem>
</itemizedlist>
<itemizedlist>
@@ -652,14 +647,14 @@
<listitem>
<para><emphasis>X-SuSE-YaST-AutoLogResource</emphasis>
- - is the resource of your modul allowed to be logged (since SLES10SP1/10.2)</para>
+ Should the resource of your module be logged (since SLES10 SP1/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
+ <para>a boolean (true, false)</para> <para>Do want &ay; to
+ log the data of your resource in the logfile? The default
+ is "true", but if you have sensitive data like passwords,
+ you may want to set this to "false". The setting can be
overridden by Y2DEBUG=1</para>
</listitem>
</itemizedlist>
@@ -676,77 +671,79 @@
</section>
<section>
- <title>Conventions for module Writers</title>
+ <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
+ <para>Modules should only export data which is 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> <module
- name>.options</emphasis> to avoid confusion with other modules using
- <emphasis>options</emphasis>, which is very common in configurations.
+ <para>Exported variables should have a unique name.<remark>emap 2011-11-05: Better use 'must' instead of 'should'?</remark>
+ To avoid conflicts and confusion when using general terminology,
+ add a name space identifier. For example, if a module should
+ export a variable <emphasis>options</emphasis>, better use
+ <emphasis> <module name>.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>
+ <para>To have a common and unified look of the control file when
+ exporting the configuration data, please use lower case
+ variables.</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
+ <para>Do not use 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>
+ rather than its contents.</para>
</listitem>
</itemizedlist>
</section>
<section>
- <title>YaST2 Module Types</title>
+ <title>&yast; Module Types</title>
<para>
- YaST2 configuration modules and in relation with AutoYaST can be put
+ &yast; configuration modules and their relation to &ay; can be divided
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>Modules which only change sysconfig variables
+ and have a 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.
+ This category needs no special attention and is easy to integrate
+ with &ay;.
</para>
</listitem>
<listitem>
- <para>Simple modules dealing with hardware configuration (i.e. network,
- sound, printer etc.)
+ <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.
+ These modules need to be able to auto-detect and read hardware
+ data during installation if no hardware data is specified in the
+ control file. The behavior of this type of modules up to SuSE
+ Linux 8.1 was to import data and write it without actually reading
+ anything from the system.<remark>emap 2011-11-05: Is this info
+ about ancient behavior necessary after so many years?</remark>
</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.
+ some case this is simply done by calling the Read function of the module.<remark>emap 2011-11-05: I assume info gained while probing the actual hardware will override data specified in the control file. Should this be mentioned?</remark>
</para>
</listitem>
<listitem>
@@ -755,38 +752,37 @@
</para>
<para>
This class of modules is much more complex and requires adaptation
- and special attention. AutoYaST expects that only new and modified
+ and special attention. &ay; 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.
+ example, when a user enables a service in inetd, only this service
+ is exported. A user should also be able to add new services which
+ are not available in the default configuration file.
</para>
</listitem>
</orderedlist>
</section>
<section>
- <title>Module behaviour</title>
+ <title>Module Behavior</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):
+ Find below a list of common pitfalls. The configuration system is the machine where the control file is created. In configuration mode for auto-installation, modules <emphasis>should
+ not</emphasis>:
<itemizedlist>
<listitem>
- <para>Read any data from the configuration system</para>
+ <para>read any data from the configuration system,</para>
</listitem>
<listitem>
- <para>Probe or detect hardware on the configuration system</para>
+ <para>probe or detect hardware on the configuration system,</para>
</listitem>
<listitem>
- <para>Change configuration data on the configuration system</para>
+ <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>
+ <para>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>
+ <para>check if a needed package is installed on the configuration
+ system.</para>
</listitem>
</itemizedlist>
--
To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-commit+help(a)opensuse.org
1
0
[yast-commit] r66711 - /trunk/autoinstallation/doc/xml/CreateProfileDetails.xml
by emap@svn2.opensuse.org 05 Nov '11
by emap@svn2.opensuse.org 05 Nov '11
05 Nov '11
Author: emap
Date: Sat Nov 5 08:37:04 2011
New Revision: 66711
URL: http://svn.opensuse.org/viewcvs/yast?rev=66711&view=rev
Log:
edited by emap
Modified:
trunk/autoinstallation/doc/xml/CreateProfileDetails.xml
Modified: trunk/autoinstallation/doc/xml/CreateProfileDetails.xml
URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/CreateP…
==============================================================================
--- trunk/autoinstallation/doc/xml/CreateProfileDetails.xml (original)
+++ trunk/autoinstallation/doc/xml/CreateProfileDetails.xml Sat Nov 5 08:37:04 2011
@@ -2,22 +2,23 @@
<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,
+ standard purposes. To learn about other available options,
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
+ then some packages might be missing and 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.
+ &yast; will install packages required in the second phase of the
+ installation and before the post-installation phase of &ay; has
+ started. However, if necessary &yast; modules are not available in the
+ system, important configuration steps will be skipped. 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"/>
@@ -43,20 +44,20 @@
<section id="CreateProfile.Hardware">
<title>
- Miscellaneous hardware and system components
+ 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
+ authentication and security, &ay;2 <remark>emap 2011-11-05: Should the '2' be there?</remark> offers a wide range of
+ hardware and system configuration options, the same as 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.
+ cards and any other hardware components which have a module within &yast;.
</para>
<para>
- Any new configuration options that will be added to &yast2; will be
- automatically available as an auto-installation resource.
+ Any new configuration options added to &yast; will be
+ automatically available in &ay;.
</para>
--
To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-commit+help(a)opensuse.org
1
0
[yast-commit] r66710 - /trunk/autoinstallation/doc/xml/BootloaderSection.xml
by emap@svn2.opensuse.org 04 Nov '11
by emap@svn2.opensuse.org 04 Nov '11
04 Nov '11
Author: emap
Date: Fri Nov 4 18:37:44 2011
New Revision: 66710
URL: http://svn.opensuse.org/viewcvs/yast?rev=66710&view=rev
Log:
edited by emap
Modified:
trunk/autoinstallation/doc/xml/BootloaderSection.xml
Modified: trunk/autoinstallation/doc/xml/BootloaderSection.xml
URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Bootloa…
==============================================================================
--- trunk/autoinstallation/doc/xml/BootloaderSection.xml (original)
+++ trunk/autoinstallation/doc/xml/BootloaderSection.xml Fri Nov 4 18:37:44 2011
@@ -18,10 +18,10 @@
]>
<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>
+ <title>The Boot Loader</title><remark>emap 2011-11-04: Please check my changes to 'original_name throughout. It made little sense. Search for: "windows" or other.</remark>
+ <para>This documentation is for yast2-bootloader <remark>emap 2011-11-04: Proper formatting, entity? Throughout the text.</remark> and applies to SLE11 and openSUSE 11.0+. For older versions, use the documentation that comes with your distribution in /usr/share/doc/packages/autoyast2/</para>
<para>
- General scope of autoyast profile only bootloader part.
+ General scope of &ay; profile only bootloader part.<remark>emap 2011-11-04: Unclear and incomplete sentence.</remark>
</para>
<screen>
<bootloader>
@@ -43,7 +43,7 @@
<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).
+You can define devices and their order in <filename>device.map</filename>, but it is not necessary. yast2-bootloader checks the devices during installation and proposes a device.map. It can happen that the order of the devices is wrong or you have defined a different order than the one set in the BIOS. Take care when you make changes there. The system might not boot afterwards.
</para>
<screen>
<device_map config:type="list">
@@ -56,7 +56,7 @@
</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.
+ This is an important if optional part. Define here where to install GRUB and how the boot process will work. Again, yast2-bootloader proposes a configuration if you don't define one. Usually the &ay; profile includes only this part and all other parts are added automatically during installation by yast2-bootloader. Unless you have some special requirements, don't specify the bootloader config in the XML file.
</para>
<screen>
<global>
@@ -81,7 +81,7 @@
<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>Set the boot flag on the boot partition. The boot partition can be "/" if there is no separate /boot partition. If the boot partition is on a logical partition, the boot flag is set to the extended partition.
</para>
<para><literal><activate>true</activate></literal></para>
</entry>
@@ -91,7 +91,7 @@
<entry>default</entry>
<entry>
<para>
- name(title) of the default boot section from menu.lst
+ Name (title) of the default boot section from <filename>menu.lst</filename>.
</para>
<para><literal><default>openSUSE 11.2 - 2.6.31.5-0.1</default></literal></para>
</entry>
@@ -101,7 +101,7 @@
<entry>gfxmenu</entry>
<entry>
<para>
- path to the graphical boot menu (/boot/message). 'none' means don't use graphical boot menu
+ Path to the graphical boot menu (/boot/message). Set to 'none' if you do not want to use a graphical boot menu.
</para>
<para><literal><gfxmenu>(hd0,1)/boot/message</gfxmenu></literal></para>
</entry>
@@ -111,7 +111,7 @@
<entry>timeout</entry>
<entry>
<para>
- timeout in seconds for automatic booting the default boot section from menu.lst
+ The timeout in seconds for automatically booting the default boot section from <filename>menu.lst</filename>.
</para>
<para><literal><timeout config:type="integer">10</timeout></literal></para>
</entry>
@@ -121,7 +121,7 @@
<entry>generic_mbr</entry>
<entry>
<para>
- write generic boot code to MBR. (It is ignored if boot_mbr is set to true)
+ Write generic boot code to MBR, will be ignored if boot_mbr is set to "true".
</para>
<para><literal><generic_mbr>false</generic_mbr></literal></para>
</entry>
@@ -131,7 +131,7 @@
<entry>boot_mbr</entry>
<entry>
<para>
- write GRUB to MBR of the first disk in the order (device.map include order of disks)
+ Write GRUB to MBR of the first disk in the order (device.map includes order of disks).
</para>
<para><literal><boot_mbr>false</boot_mbr></literal></para>
</entry>
@@ -141,7 +141,7 @@
<entry>boot_boot</entry>
<entry>
<para>
- write GRUB to separate /boot partition (if separate /boot partition missing GRUB will be written to "/")
+ Write GRUB to separate /boot partition. If no separate /boot partition exists, GRUB will be written to "/".
</para>
<para><literal><boot_boot>false</boot_boot></literal></para>
</entry>
@@ -151,7 +151,7 @@
<entry>boot_root</entry>
<entry>
<para>
- write GRUB to "/" partition
+ Write GRUB to "/" partition.
</para>
<para><literal><boot_root>false</boot_root></literal></para>
</entry>
@@ -161,7 +161,7 @@
<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.
+Write GRUB to the extended partition (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><literal><boot_extended>false</boot_extended></literal></para>
</entry>
@@ -171,7 +171,7 @@
<entry>boot_custom</entry>
<entry>
<para>
- write GRUB to custom device.
+ Write GRUB to custom device.
</para>
<para><literal><boot_custom>/dev/sda3</boot_custom></literal></para>
</entry>
@@ -181,7 +181,7 @@
<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.
+ Use trusted GRUB instead of the classical GRUB (gfxmenu is deleted automatically if this option is true). Do not use trusted GRUB if your hardware does not support it.
</para>
<para><literal><trusted_grub>false</trusted_grub></literal></para>
</entry>
@@ -191,7 +191,7 @@
<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.
+ Internal option specifying the cache id for perl-Bootloader. Do not use or change it in a cloned XML file.
</para>
<para><literal></literal></para>
</entry>
@@ -204,12 +204,12 @@
</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.
+ A list of initrd modules. Do not create your own list if you do not fully understand the impact. &ay; will take care of it for you.
</para>
</section>
<section><title>Loader Type</title>
<para>
- This part defines the type of the bootloader. It could be grub, lilo, ppc or elilo.
+ Define which boot loader to use: grub, lilo, ppc or elilo.
</para>
<screen>
<loader_type>grub</loader_type>
@@ -217,7 +217,7 @@
</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.
+ The configuration of the boot sections in the menu.lst is added automatically here by yast2-bootloader during installation. yast2-bootloader deletes boot sections with no valid kernel and initrd path.
</para>
<screen>
<sections config:type="list">
@@ -261,9 +261,9 @@
</section>
<section><title>Options</title>
<para>
-the options depend on the <emphasis>type</emphasis>.
+ Available options depend on the <emphasis>type</emphasis>.
</para>
- <section><title>Options for section type: image and xen</title>
+ <section><title>Options for Section Type: image and xen</title>
<informaltable frame='top'>
<tgroup cols="3">
<thead>
@@ -278,7 +278,7 @@
<entry>append</entry>
<entry>
<para>
- list of kernel args but without(!) vga= and root=
+ List of kernel args but without(!) vga= and root=.
</para>
<para><literal><append>splash=silent quiet showopts</append></literal></para>
</entry>
@@ -288,7 +288,7 @@
<entry>image</entry>
<entry>
<para>
- path to the kernel
+ Path to the kernel.
</para>
<para><literal><image>(hd0,0)/vmlinuz-2.6.31-10</image></literal></para>
</entry>
@@ -298,7 +298,7 @@
<entry>initrd</entry>
<entry>
<para>
- path to the initrd
+ Path to the initrd.
</para>
<para><literal><initrd>(hd0,0)/my-initrd</initrd></literal></para>
</entry>
@@ -308,7 +308,7 @@
<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.
+ Internal option specifying the cache id for perl-Bootloader. Do not use or change it in a cloned XML file.
</para>
<para><literal></literal></para>
</entry>
@@ -318,7 +318,7 @@
<entry>name</entry>
<entry>
<para>
- name of section
+ Name of section.
</para>
<para><literal><name>Productive System</name></literal></para>
</entry>
@@ -328,7 +328,7 @@
<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.
+ Internal name of section parsed by &yast; from a comment in the configuration file. There are some rules for names, and original_name helps to determine if the boot section is "linux" or "failsafe". For chainloader it helps to determine if it is "windows" or other (linux, floppy, etc). Use a simple original_name: linux, xen, windows, floppy, etc.
</para>
<para><literal><original_name>linux</original_name></literal></para>
</entry>
@@ -338,7 +338,7 @@
<entry>root</entry>
<entry>
<para>
- location of the root partition ("/")
+ Location of the root partition ("/").
</para>
<para><literal><root>/dev/mapper/sil_ajacccbhejai_part3</root></literal></para>
</entry>
@@ -348,7 +348,7 @@
<entry>type</entry>
<entry>
<para>
- type of section it could (image/xen/other/menu)
+ Type of section (image/xen/other/menu).
</para>
<para><literal><type>xen</type></literal></para>
</entry>
@@ -358,7 +358,7 @@
<entry>vgamode</entry>
<entry>
<para>
- kernel arg for vga (vga=)
+ Kernel arg for vga (vga=).
</para>
<para><literal><vgamode>0x31a</vgamode></literal></para>
</entry>
@@ -368,7 +368,7 @@
<entry>xen</entry>
<entry>
<para>
- path to xen.gz
+ Path to xen.gz.
</para>
<para><literal><xen>(hd0,0)/xen.gz</xen></literal></para>
</entry>
@@ -378,7 +378,7 @@
<entry>xen_append</entry>
<entry>
<para>
- kernel args for XEN
+ Kernel args for XEN.
</para>
<para><literal><xen_append></xen_append></literal></para>
</entry>
@@ -388,7 +388,7 @@
</tgroup>
</informaltable>
</section>
- <section><title>Options for section type: other (chainloader)</title>
+ <section><title>Options for Section Type: other (chainloader)</title>
<informaltable frame='top'>
<tgroup cols="3">
<thead>
@@ -403,7 +403,7 @@
<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.
+ Internal option specifying the cache id for perl-Bootloader. Do not use or change it in a cloned XML file.
</para>
<para><literal></literal></para>
</entry>
@@ -413,7 +413,7 @@
<entry>name</entry>
<entry>
<para>
- name or title of section
+ Name or title of the section.
</para>
<para><literal><name>Floppy</name></literal></para>
</entry>
@@ -423,7 +423,7 @@
<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.
+ Internal name of the section parsed by &yast; from a comment in the configuration file. There are some rules for names and original_name helps to determine if the boot section is "linux" or "failsafe". For the chainloader it helps to determine if it is "windows" or other (linux, floppy, etc). Use a simple original_name: linux, xen, windows, floppy etc.
</para>
<para><literal><original_name>linux</original_name></literal></para>
</entry>
@@ -433,7 +433,7 @@
<entry>type</entry>
<entry>
<para>
- type of section it could (image/xen/other/menu)
+ Type of section (image/xen/other/menu).
</para>
<para><literal><type>other</type></literal></para>
</entry>
@@ -443,7 +443,7 @@
<entry>blockoffset</entry>
<entry>
<para>
- offset in chainloader (used only in grub)
+ Offset in chainloader (used only in grub).
</para>
<para><literal><blockoffset>1</blockoffset></literal></para>
</entry>
@@ -453,7 +453,7 @@
<entry>chainloader</entry>
<entry>
<para>
- partition part for chainloader (so chainloader+blockoffset get final chainloader item in grub)
+ Partition part for chainloader (so chainloader+blockoffset get final chainloader item in grub).<remark>emap 2011-11-04: Not sure what the parenthesis is supposed to say.</remark>
</para>
<para><literal><chainloader>/dev/fd0</chainloader></literal></para>
</entry>
@@ -463,7 +463,7 @@
<entry>noverifyroot</entry>
<entry>
<para>
- with/without checking root
+ With or without checking root. <remark>emap 2011-11-04: Awkward. Can someone make this clearer?</remark>
</para>
<para><literal><noverifyroot>true</noverifyroot></literal></para>
</entry>
@@ -473,7 +473,7 @@
<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)
+ Windows-specific option for remapping hard disks, for example switch the first and second disk: map (hd0) (hd1) map (hd1) (hd0)
</para>
<para><literal><remap>false</remap></literal></para>
</entry>
@@ -483,7 +483,7 @@
<entry>makeactive</entry>
<entry>
<para>
- add the makeactive argument for chainloader section
+ Add the makeactive argument for the chainloader section.
</para>
<para><literal><makeactive>false</makeactive></literal></para>
</entry>
@@ -508,7 +508,7 @@
<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.
+ Internal option specifying the cache id for perl-Bootloader. Do not use or change it in a cloned XML file.
</para>
<para><literal></literal></para>
</entry>
@@ -518,7 +518,7 @@
<entry>name</entry>
<entry>
<para>
- name or title of section
+ Name or title of section.
</para>
<para><literal><name>Floppy</name></literal></para>
</entry>
@@ -528,7 +528,7 @@
<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.
+ Internal name of section parsed by YaST from a comment in the configuration file. There are some rules for names and original_name helps to determine if the boot section is "linux" or "failsafe". For the chainloader it helps to determine if it is "windows" or other (linux, floppy etc). Use a simple original_name: linux, xen, windows, floppy etc.
</para>
<para><literal><original_name>linux</original_name></literal></para>
</entry>
@@ -538,7 +538,7 @@
<entry>type</entry>
<entry>
<para>
- type of section it could (image/xen/other/menu)
+ Type of section (image/xen/other/menu).
</para>
<para><literal><type>other</type></literal></para>
</entry>
@@ -548,7 +548,7 @@
<entry>configfile</entry>
<entry>
<para>
- path to menu.lst config file
+ Path to menu.lst config file.
</para>
<para><literal><configfile>1</configfile></literal></para>
</entry>
@@ -558,7 +558,7 @@
<entry>root</entry>
<entry>
<para>
- device name for loading menu.lst from other installation of linux
+ Device name for loading menu.lst from another installation of Linux.
</para>
<para><literal><root>/dev/sda1</root></literal></para>
</entry>
--
To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-commit+help(a)opensuse.org
1
0
[yast-commit] r66709 - /trunk/autoinstallation/doc/xml/ASKSection.xml
by emap@svn2.opensuse.org 04 Nov '11
by emap@svn2.opensuse.org 04 Nov '11
04 Nov '11
Author: emap
Date: Fri Nov 4 17:31:40 2011
New Revision: 66709
URL: http://svn.opensuse.org/viewcvs/yast?rev=66709&view=rev
Log:
edited by emap
Modified:
trunk/autoinstallation/doc/xml/ASKSection.xml
Modified: trunk/autoinstallation/doc/xml/ASKSection.xml
URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/ASKSect…
==============================================================================
--- trunk/autoinstallation/doc/xml/ASKSection.xml (original)
+++ trunk/autoinstallation/doc/xml/ASKSection.xml Fri Nov 4 17:31:40 2011
@@ -26,10 +26,10 @@
</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
+ parts of the profile during the installation. If you use this feature,
+ a popup will ask the user to
+ enter a specific part of the profile during installation. If you want a full auto installation,
+ but the user should set the password of the local account, you can do
this via the <emphasis>ask</emphasis> directive in the profile.
</para>
<para>
@@ -51,44 +51,44 @@
<entry>question</entry>
<entry><para>The question you want to ask the user.</para>
<screen><question>Enter the LDAP server</question></screen></entry>
- <entry>The default value is the path to the element (the path often looks strange, so I recommend to enter a question)</entry>
+ <entry>The default value is the path to the element (the path often looks strange, so we recommend to enter a question)</entry><remark>emap 2011-11-04: not sure I understand this.</remark>
</row>
<row>
<entry>default</entry>
- <entry><para>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.
+ <entry><para>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><default>dc=suse,dc=de</default></screen></entry>
- <entry>optional</entry>
+ <entry>Optional.</entry>
</row>
<row>
<entry>help</entry>
<entry><para>An optional helptext that is shown on the left side of the question.
</para><screen><help>Enter the LDAP server address.</help></screen></entry>
- <entry>optional</entry>
+ <entry>Optional.</entry>
</row>
<row>
<entry>title</entry>
<entry><para>An optional title that is shown above the questions.
</para><screen><title>LDAP server</title></screen></entry>
- <entry>optional</entry>
+ <entry>Optional.</entry>
</row>
<row>
<entry>type</entry>
- <entry><para>the type of the element you want to change. Possible values are "symbol","boolean","string" and "integer".
+ <entry><para>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><type>symbol</type></screen></entry>
- <entry>optional. The defaul is string. If type is "symbol" you must provide the selection element too (see below)</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><para>if this boolean is set to "true", a password dialog pops up instead of a simple text entry. Setting this
+ <entry><para>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><password config:type="boolean">true</password></screen></entry>
- <entry>optional. The default is "false"</entry>
+ <entry>Optional. The default is "false".</entry>
</row>
<row>
<entry>path (deprecated since openSUSE 11.0 - use pathlist)</entry>
@@ -99,43 +99,43 @@
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 provie <emphasis>path</emphasis> or <emphasis>file</emphasis></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)
+ <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>
- <entry><para>this information is optional but you should at least provie <emphasis>path</emphasis> or <emphasis>file</emphasis></para></entry>
+ <entry><para>This information is optional but you should at least provide <emphasis>path</emphasis> or <emphasis>file</emphasis>.</para></entry>
</row>
<row>
<entry>file (available since SLES10 SP1 and SL 10.2)</entry>
- <entry><para>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/
+ <entry><para>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. Use the commnad: "cp /tmp/my_answer /mnt/tmp/". The reason 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><file>/tmp/answer_hostname</file></screen></entry>
- <entry><para>this information is optional but you should at least provie <emphasis>path</emphasis> or <emphasis>file</emphasis></para></entry>
+ <entry><para>This information is optional, but you should at least provide <emphasis>path</emphasis> or <emphasis>file</emphasis></para></entry>
</row>
<row>
<entry>password</entry>
- <entry><para>if this boolean is set to "true", a password dialog pops up instead of a simple text entry. Setting this
+ <entry><para>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><password config:type="boolean">true</password></screen></entry>
- <entry>optional. The default is "false"</entry>
+ <entry>Optional. The default is "false".</entry>
</row>
<row>
<entry>stage</entry>
- <entry><para>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
+ <entry><para>Stage configures the installation stage in which the question pops up. You can set this value to "cont" or
+ "initial". "initial" means the popup comes up very early in the installation, shortly 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
+ Of course it does not make sense to ask for the filesystem to use during the "cont" phase. The harddisk is already
partitioned at that stage and the question will have no effect.
</para><screen><stage>cont</stage></screen></entry>
- <entry>optional. The default is "initial"</entry>
+ <entry>Optional. The default is "initial".</entry>
</row>
<row>
<entry>selection</entry>
- <entry><para>the selection element contains a list of <entry> 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
+ <entry><para>The selection element contains a list of <entry> elements. Each entry represents a possible option
+ for the user to choose. The user cannot enter a value in a textfield, but he can choose from a list
of values.
</para><screen>
<selection config:type="list">
@@ -156,59 +156,58 @@
</label>
</entry>
</selection></screen></entry>
- <entry>optional for type=string, not possible for type=boolean and a must have for type=symbol</entry>
+ <entry>Optional for type=string, not possible for type=boolean and mandatory for type=symbol.</entry>
</row>
<row>
<entry>dialog (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
- to specifiy the dialog-id with an integer. All questions with the same dialog-id are on the same dialog.
+ <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.
The dialogs are sorted by the id too.
</para><screen><dialog config:type="integer">3</dialog></screen></entry>
- <entry>optional</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
- to specifiy the element-id with an integer. The questions on a dialog are sorted by the id.
+ <entry><para>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 in a dialog are sorted by id.
</para><screen><element config:type="integer">1</element></screen></entry>
- <entry>optional (see dialog></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 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.
+ <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.
</para><screen><frametitle>User data</frametitle></screen></entry>
- <entry>optional (default is no frametitle)</entry>
+ <entry>Optional. Default is no frame title.</entry>
</row>
<row>
- <entry>script (available since SL 10.3 not in SLES10 SP1)</entry>
- <entry><para>with 10.3 you can run scripts after a question has been answered (see the table below for detailed instructions about scripts)
+ <entry>script (available since SL 10.3, not in SLES10 SP1)</entry>
+ <entry><para>Since 10.3, you can run scripts after a question has been answered (see the table below for detailed instructions about scripts).
</para><screen><script>...</script></screen></entry>
<entry>optional (default is no script)</entry>
</row>
<row>
- <entry>ok_label (available since openSUSE 11.2 / SLES11 SP2</entry>
- <entry><para>You can change the Label on the "Ok" button. The last element that specifies the label for a dialog wins.
+ <entry>ok_label (available since openSUSE 11.2 and SLES11 SP2</entry>
+ <entry><para>You can change the label on the "Ok" button. The last element that specifies the label for a dialog wins.
</para><screen><ok_label>Finish</ok_label></screen></entry>
- <entry>optional</entry>
+ <entry>Optional.</entry>
</row>
<row>
- <entry>back_label (available since openSUSE 11.2 / SLES11 SP2</entry>
- <entry><para>You can change the Label on the "Back" button. The last element that specifies the label for a dialog wins.
+ <entry>back_label (available since openSUSE 11.2 and SLES11 SP2</entry>
+ <entry><para>You can change the label on the "Back" button. The last element that specifies the label for a dialog wins.
</para><screen><back_label>change values</back_label></screen></entry>
- <entry>optional</entry>
+ <entry>Optional.</entry>
</row>
<row>
- <entry>timeout (available since openSUSE 11.2 / SLES11-SP2</entry>
- <entry><para>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.
+ <entry>timeout (available since openSUSE 11.2 and SLES11-SP2</entry>
+ <entry><para>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 or changes any widget in the dialog, the timeout is turned off and the dialog has to be confirmed via the ok-button.
</para><screen><timeout config:type="integer">30</timeout></screen></entry>
- <entry>optional. A missing value is interpreted as 0 which means that there is no timeout</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><para>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.
+ <entry>default_value_script (available since openSUSE 11.2 and SLES11-SP2)</entry>
+ <entry><para>You can run scripts to set the default value for a question (see the table below for detailed instructions about default value scripts). This feature is useful if you can "calculate" a useful default value, especially in combination with the "timeout" option.
</para><screen><default_value_script>...</default_value_script></screen></entry>
- <entry>optional (default is no script)</entry>
+ <entry>Optional. Default is no script.</entry>
</row>
</tbody>
</tgroup>
@@ -216,7 +215,7 @@
</table>
<para>
- The following elements must be between the <ask-list config:type="list"><ask><default_value_script>...</default_value_script>...</ask></ask-list> tags in the <general> section. It's available since 11.2 and SLES11-SP2
+ The following elements must be between the <ask-list config:type="list"><ask><default_value_script>...</default_value_script>...</ask></ask-list> tags in the <general> section. This is available since 11.2 and SLES11-SP2.
</para>
<table frame='top'>
<title>XML representation</title>
@@ -231,15 +230,15 @@
<tbody>
<row>
<entry>source</entry>
- <entry><para>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
+ <entry><para>The source code of the script. Whatever you <command>echo</command> 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 use <command>echo -n</command> to suppress the <literal>\n</literal> and that you echo reasonable values and not "okay" for a boolean
</para><screen><source>...</source></screen></entry>
- <entry>this value is required. Otherwise nothing would be executed</entry>
+ <entry>This value is required, otherwise nothing would be executed.</entry>
</row>
<row>
<entry>interpreter</entry>
- <entry><para>the interpreter to use
+ <entry><para>The interpreter to use.
</para><screen><interpreter>perl</interpreter></screen></entry>
- <entry>default is shell (you can set "/bin/myinterpreter" as value too)</entry>
+ <entry>The default is shell. You can also set "/bin/myinterpreter" as value.</entry>
</row>
</tbody>
</tgroup>
@@ -247,7 +246,7 @@
<para>
- The following elements must be between the <ask-list config:type="list"><ask><script>...</script>...</ask></ask-list> tags in the <general> section. It's available since 10.3 (not SLES10 SP1).
+ The following elements must be between the <ask-list config:type="list"><ask><script>...</script>...</ask></ask-list> tags in the <general> section. Available since 10.3 (not SLES10 SP1).
</para>
<table frame='top'>
<title>XML representation</title>
@@ -262,39 +261,39 @@
<tbody>
<row>
<entry>filename</entry>
- <entry><para>the filename of the script
+ <entry><para>The filename of the script.
</para><screen><filename>my_ask_script.sh</filename></screen></entry>
- <entry>default is ask_script.sh</entry>
+ <entry>The default is ask_script.sh</entry>
</row>
<row>
<entry>source</entry>
- <entry><para>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)
+ <entry><para>The source code of the script. Together with "rerun_on_error" activated, 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 specifying the next dialog &ay; will raise. A value of -1 terminates the ask sequence. If that file is not created, &ay; will run the dialogs in the normal order (since 11.0 only).
</para><screen><source>...</source></screen></entry>
- <entry>this value is required. Otherwise nothing would be executed</entry>
+ <entry>This value is required, otherwise nothing would be executed.</entry>
</row>
<row>
<entry>environment</entry>
- <entry><para>a boolean that passes the "value" of the answer to the question as an environment variable to the script. The variable is named "VAL".
+ <entry><para>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><environment config:type="boolean">true</environment></screen></entry>
- <entry>optional (default is "false").</entry>
+ <entry>Optional. Default is "false".</entry>
</row>
<row>
<entry>feedback</entry>
- <entry><para>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.
+ <entry><para>A boolean that turns on feedback for the script execution. STDOUT will be displayed in a popup window that must be confirmed after the script execution.
</para><screen><feedback config:type="boolean">true</feedback></screen></entry>
- <entry>optional (default is "false").</entry>
+ <entry>Optional, default is "false".</entry>
</row>
<row>
<entry>debug</entry>
- <entry><para>a boolean that turns on debugging for the script execution
+ <entry><para>A boolean that turns on debugging for the script execution.
</para><screen><debug config:type="boolean">true</debug></screen></entry>
- <entry>optional (default is "true"). This value needs feedback to be turned on too.</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><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 popup an error with the "feedback" option.
+ <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>
+ <entry>Optional, default is "false". This value should be used together with the feedback option.</entry>
</row>
</tbody>
</tgroup>
@@ -371,7 +370,7 @@
</screen>
<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.
+The following example is a nice way to choose between &ay; profiles. &ay; will read the <filename>modified.xml</filename> file again after the ask-dialogs are done. This way you can fetch a complete new profile.
</para>
<screen>
@@ -407,7 +406,7 @@
</ask>
</screen>
<para>
-Since openSUSE 11.0 you can verify the answer of a question with a script like this:
+Since openSUSE 11.0, you can verify the answer of a question with a script like this:
</para>
<screen>
--
To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-commit+help(a)opensuse.org
1
0
[yast-commit] r66708 - in /branches/SuSE-Code-11-SP1-Branch/bootloader: VERSION package/yast2-bootloader.changes src/routines/autoinstall.ycp
by snwint@svn2.opensuse.org 04 Nov '11
by snwint@svn2.opensuse.org 04 Nov '11
04 Nov '11
Author: snwint
Date: Fri Nov 4 17:15:22 2011
New Revision: 66708
URL: http://svn.opensuse.org/viewcvs/yast?rev=66708&view=rev
Log:
- don't question device mapping passed to us explicitly by autoyast (bnc #717978)
- 2.17.82
Modified:
branches/SuSE-Code-11-SP1-Branch/bootloader/VERSION
branches/SuSE-Code-11-SP1-Branch/bootloader/package/yast2-bootloader.changes
branches/SuSE-Code-11-SP1-Branch/bootloader/src/routines/autoinstall.ycp
Modified: branches/SuSE-Code-11-SP1-Branch/bootloader/VERSION
URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP1-Branch/bootl…
==============================================================================
--- branches/SuSE-Code-11-SP1-Branch/bootloader/VERSION (original)
+++ branches/SuSE-Code-11-SP1-Branch/bootloader/VERSION Fri Nov 4 17:15:22 2011
@@ -1 +1 @@
-2.17.81
+2.17.82
Modified: branches/SuSE-Code-11-SP1-Branch/bootloader/package/yast2-bootloader.changes
URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP1-Branch/bootl…
==============================================================================
--- branches/SuSE-Code-11-SP1-Branch/bootloader/package/yast2-bootloader.changes (original)
+++ branches/SuSE-Code-11-SP1-Branch/bootloader/package/yast2-bootloader.changes Fri Nov 4 17:15:22 2011
@@ -1,4 +1,11 @@
-------------------------------------------------------------------
+Fri Nov 4 17:13:29 CET 2011 - snwint(a)suse.de
+
+- don't question device mapping passed to us explicitly by
+ autoyast (bnc #717978)
+- 2.17.82
+
+-------------------------------------------------------------------
Mon Oct 17 14:57:39 CEST 2011 - snwint(a)suse.de
- fix activating partition on raid setups (bnc #715436)
Modified: branches/SuSE-Code-11-SP1-Branch/bootloader/src/routines/autoinstall.ycp
URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP1-Branch/bootl…
==============================================================================
--- branches/SuSE-Code-11-SP1-Branch/bootloader/src/routines/autoinstall.ycp (original)
+++ branches/SuSE-Code-11-SP1-Branch/bootloader/src/routines/autoinstall.ycp Fri Nov 4 17:15:22 2011
@@ -283,6 +283,8 @@
return $[ entry["linux"]:"" : firmware ];
});
exp["specific", "device_map"] = device_map;
+ // accept everything
+ BootCommon::bois_id_missing = false;
}
}
--
To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-commit+help(a)opensuse.org
1
0
[yast-commit] r66707 - in /branches/SuSE-Code-11-SP1-Branch/bootloader: VERSION package/yast2-bootloader.changes src/grub/misc.ycp src/routines/lilolike.ycp
by snwint@svn2.opensuse.org 04 Nov '11
by snwint@svn2.opensuse.org 04 Nov '11
04 Nov '11
Author: snwint
Date: Fri Nov 4 17:13:03 2011
New Revision: 66707
URL: http://svn.opensuse.org/viewcvs/yast?rev=66707&view=rev
Log:
- fix activating partition on raid setups (bnc #715436)
- 2.17.81
Modified:
branches/SuSE-Code-11-SP1-Branch/bootloader/VERSION
branches/SuSE-Code-11-SP1-Branch/bootloader/package/yast2-bootloader.changes
branches/SuSE-Code-11-SP1-Branch/bootloader/src/grub/misc.ycp
branches/SuSE-Code-11-SP1-Branch/bootloader/src/routines/lilolike.ycp
Modified: branches/SuSE-Code-11-SP1-Branch/bootloader/VERSION
URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP1-Branch/bootl…
==============================================================================
--- branches/SuSE-Code-11-SP1-Branch/bootloader/VERSION (original)
+++ branches/SuSE-Code-11-SP1-Branch/bootloader/VERSION Fri Nov 4 17:13:03 2011
@@ -1 +1 @@
-2.17.80
+2.17.81
Modified: branches/SuSE-Code-11-SP1-Branch/bootloader/package/yast2-bootloader.changes
URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP1-Branch/bootl…
==============================================================================
--- branches/SuSE-Code-11-SP1-Branch/bootloader/package/yast2-bootloader.changes (original)
+++ branches/SuSE-Code-11-SP1-Branch/bootloader/package/yast2-bootloader.changes Fri Nov 4 17:13:03 2011
@@ -1,4 +1,10 @@
-------------------------------------------------------------------
+Mon Oct 17 14:57:39 CEST 2011 - snwint(a)suse.de
+
+- fix activating partition on raid setups (bnc #715436)
+- 2.17.81
+
+-------------------------------------------------------------------
Wed Sep 21 11:35:04 CEST 2011 - snwint(a)suse.de
- enable resume for s390x (bnc #692606)
Modified: branches/SuSE-Code-11-SP1-Branch/bootloader/src/grub/misc.ycp
URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP1-Branch/bootl…
==============================================================================
--- branches/SuSE-Code-11-SP1-Branch/bootloader/src/grub/misc.ycp (original)
+++ branches/SuSE-Code-11-SP1-Branch/bootloader/src/grub/misc.ycp Fri Nov 4 17:13:03 2011
@@ -73,6 +73,9 @@
integer num = BootCommon::myToInteger( p_dev["nr"]:nil );
string mbr_dev = p_dev["disk"]:"";
+ y2milestone("getPartitionToActivate(%1): mbr_dev = %2, num = %3", loader_device, mbr_dev, num);
+ y2milestone("getPartitionToActivate: p_dev = %1", p_dev);
+
// If loader_device is /dev/md* (which means bootloader is installed to
// /dev/md*), return the info map for the first device in BIOS ID order
// that underlies the soft-RAID and that has a BIOS ID (devices without
@@ -101,6 +104,7 @@
map p_dev = Storage::GetDiskPartition (device);
num = BootCommon::myToInteger( p_dev["nr"]:nil );
mbr_dev = p_dev["disk"]:"";
+ y2milestone("getPartitionToActivate: raid setup: mbr_dev = %1, num = %2", mbr_dev, num);
}
}
// If loader_device is a disk device ("/dev/sda"), that means that we
@@ -145,29 +149,33 @@
// (bnc # 337742) - Unable to boot the openSUSE (32 and 64 bits) after installation
// if loader_device is disk device activate BootCommon::BootPartitionDevice
// - only if boot partition is on mbr device
+ // - watch out for raid setups: mbr_dev != loader_device
if (num == 0)
{
p_dev = Storage::GetDiskPartition (BootCommon::BootPartitionDevice);
string p_disk = p_dev["disk"]:"";
integer p_num = BootCommon::myToInteger( p_dev["nr"]:nil );
- y2milestone ("loader_device is disk device: mbr = %1, dev = %2, num = %3, activate = %4",
- mbr_dev, p_disk, p_num, p_disk == mbr_dev
- );
+ boolean activate = p_disk == mbr_dev || p_disk == loader_device;
+
// as it's not really possible to say 'no', we return num = 0 which will
// eventually result in not activating the partition - dead ugly, I know
- if (p_disk == mbr_dev) { num = p_num; }
+ if (activate) { num = p_num; }
+
+ y2milestone ("getPartitionToActivate: mbr_dev = %1, disk = %2, num = %3, p_num = %4, activate = %5",
+ mbr_dev, p_disk, num, p_num, activate
+ );
}
if (num > 4)
{
- y2milestone ("Bootloader partition type is logical");
+ y2milestone ("getPartitionToActivate: logical partition");
map tm = Storage::GetTargetMap ();
list<map> partitions = tm[mbr_dev, "partitions"]:[];
foreach (map p, partitions, ``{
if (p["type"]:nil == `extended)
{
num = p["nr"]:num;
- y2milestone ("Using extended partition %1 instead",num);
+ y2milestone ("getPartitionToActivate: using extended partition %1", num);
}
});
}
@@ -178,7 +186,8 @@
"dev" : Storage::GetDeviceName (mbr_dev, num),
];
- y2milestone("Partition for activating: %1", ret);
+ y2milestone("getPartitionToActivate: activating partition: %1", ret);
+
return ret;
}
Modified: branches/SuSE-Code-11-SP1-Branch/bootloader/src/routines/lilolike.ycp
URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP1-Branch/bootl…
==============================================================================
--- branches/SuSE-Code-11-SP1-Branch/bootloader/src/routines/lilolike.ycp (original)
+++ branches/SuSE-Code-11-SP1-Branch/bootloader/src/routines/lilolike.ycp Fri Nov 4 17:13:03 2011
@@ -110,19 +110,21 @@
* @return string mbr device
*/
global string FindMBRDisk() {
+ y2milestone("FindMBRDisk: current MBR = %1", BootCommon::mbrDisk);
+
// check the disks order, first has MBR
list<string> order = DisksOrder ();
if (size (order) > 0)
{
string ret = order[0]:"";
- y2milestone ("First disk in the order: %1, using for MBR", ret);
+ y2milestone ("FindMBRDisk: using first disk, new MBR = %1", ret);
return ret;
}
// OK, order empty, use the disk with boot partition
map mp = Storage::GetMountPoints();
string boot_disk = mp["/boot",2]:(mp["/",2]:"");
- y2milestone ("Disk with boot partition: %1, using for MBR", boot_disk);
+ y2milestone ("FindMBRDisk: using disk with /boot, new MBR = %1", boot_disk);
return boot_disk;
}
--
To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-commit+help(a)opensuse.org
1
0
[yast-commit] r66706 - /trunk/autoinstallation/doc/xml/appendix2.xml
by emap@svn2.opensuse.org 04 Nov '11
by emap@svn2.opensuse.org 04 Nov '11
04 Nov '11
Author: emap
Date: Fri Nov 4 16:32:13 2011
New Revision: 66706
URL: http://svn.opensuse.org/viewcvs/yast?rev=66706&view=rev
Log:
edited by emap
Modified:
trunk/autoinstallation/doc/xml/appendix2.xml
Modified: trunk/autoinstallation/doc/xml/appendix2.xml
URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/appendi…
==============================================================================
--- trunk/autoinstallation/doc/xml/appendix2.xml (original)
+++ trunk/autoinstallation/doc/xml/appendix2.xml Fri Nov 4 16:32:13 2011
@@ -10,7 +10,7 @@
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>
+ <para>To create a boot floppy on a Linux system, as root, use the following command line:</para><remark>emap 2011-11-04: Add the command.</remark>
@@ -20,7 +20,7 @@
<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
+ To configure multiple clients (i.e. when configuring a cluster), you will need the Ethernet MAC address
of every node in your cluster.
</para>
@@ -45,7 +45,7 @@
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>
+ files where you are running a &dhcp; server,<remark>emap 2011-11-04: Should this read: in the system log files of your &dhcp; server?</remark> for example:</para>
<screen>
Feb 27 00:43:22 avicenna dhcpd: DHCPDISCOVER from 00:50:ba:3f:b5:d5 via eth0
@@ -68,4 +68,4 @@
mode: xml
sgml-parent-document: ("autoyast2.xml" "book" "appendix")
End:
- -->
\ No newline at end of file
+ -->
--
To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-commit+help(a)opensuse.org
1
0
[yast-commit] r66705 - in /branches/SuSE-Code-11-SP2-Branch/firewall: VERSION package/yast2-firewall.changes src/subdialogs.ycp
by locilka@svn2.opensuse.org 04 Nov '11
by locilka@svn2.opensuse.org 04 Nov '11
04 Nov '11
Author: locilka
Date: Fri Nov 4 16:20:15 2011
New Revision: 66705
URL: http://svn.opensuse.org/viewcvs/yast?rev=66705&view=rev
Log:
- Added function keys for buttons (bnc#595564)
- 2.17.12
Modified:
branches/SuSE-Code-11-SP2-Branch/firewall/VERSION
branches/SuSE-Code-11-SP2-Branch/firewall/package/yast2-firewall.changes
branches/SuSE-Code-11-SP2-Branch/firewall/src/subdialogs.ycp
Modified: branches/SuSE-Code-11-SP2-Branch/firewall/VERSION
URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/firew…
==============================================================================
--- branches/SuSE-Code-11-SP2-Branch/firewall/VERSION (original)
+++ branches/SuSE-Code-11-SP2-Branch/firewall/VERSION Fri Nov 4 16:20:15 2011
@@ -1 +1 @@
-2.17.11
+2.17.12
Modified: branches/SuSE-Code-11-SP2-Branch/firewall/package/yast2-firewall.changes
URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/firew…
==============================================================================
--- branches/SuSE-Code-11-SP2-Branch/firewall/package/yast2-firewall.changes (original)
+++ branches/SuSE-Code-11-SP2-Branch/firewall/package/yast2-firewall.changes Fri Nov 4 16:20:15 2011
@@ -1,4 +1,10 @@
-------------------------------------------------------------------
+Fri Nov 4 16:21:00 CET 2011 - locilka(a)suse.cz
+
+- Added function keys for buttons (bnc#595564)
+- 2.17.12
+
+-------------------------------------------------------------------
Thu Oct 13 10:34:54 CEST 2011 - locilka(a)suse.cz
- Fixed a typo in text marked for translation (bnc#722459).
Modified: branches/SuSE-Code-11-SP2-Branch/firewall/src/subdialogs.ycp
URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/firew…
==============================================================================
--- branches/SuSE-Code-11-SP2-Branch/firewall/src/subdialogs.ycp (original)
+++ branches/SuSE-Code-11-SP2-Branch/firewall/src/subdialogs.ycp Fri Nov 4 16:20:15 2011
@@ -75,9 +75,9 @@
),
`HBox (
// TRANSLATORS: push button
- `PushButton(`id("change_firewall_interface"), _("&Change...")),
+ `PushButton(`id("change_firewall_interface"), `opt(`key_F4), _("&Change...")),
// TRANSLATORS: push button
- `PushButton(`id("user_defined_firewall_interface"), _("C&ustom...")),
+ `PushButton(`id("user_defined_firewall_interface"), `opt(`key_F7), _("C&ustom...")),
`HStretch ()
)
)
@@ -225,14 +225,14 @@
),
`HSquash( `VBox (
`VSpacing( 1.1 ),
- `PushButton ( `id ( "add_allowed_service" ), `opt ( `hstretch ), " " + Label::AddButton() + " "),
+ `PushButton ( `id ( "add_allowed_service" ), `opt ( `hstretch, `key_F3 ), " " + Label::AddButton() + " "),
- `PushButton ( `id ( "remove_allowed_service" ), `opt ( `hstretch ), " " + Label::DeleteButton() + " "),
+ `PushButton ( `id ( "remove_allowed_service" ), `opt ( `hstretch, `key_F5 ), " " + Label::DeleteButton() + " "),
`Empty(`opt(`vstretch)),
// TRANSLATORS: push button
- `PushButton ( `id ( "advanced_allowed_service" ), `opt ( `hstretch ), " " + _("A&dvanced...") + " ")
+ `PushButton ( `id ( "advanced_allowed_service" ), `opt ( `hstretch, `key_F7 ), " " + _("A&dvanced...") + " ")
))
)
);
@@ -264,8 +264,8 @@
), []
),
`HBox (
- `PushButton(`id("add_redirect_to_masquerade"), Label::AddButton()),
- `PushButton(`id("remove_redirect_to_masquerade"), Label::DeleteButton()),
+ `PushButton(`id("add_redirect_to_masquerade"), `opt(`key_F3), Label::AddButton()),
+ `PushButton(`id("remove_redirect_to_masquerade"), `opt(`key_F5), Label::DeleteButton()),
`HStretch()
)
)
@@ -408,8 +408,8 @@
), []
),
`HBox (
- `PushButton(`id("add_redirect_to_masquerade"), Label::AddButton()),
- `PushButton(`id("remove_redirect_to_masquerade"), Label::DeleteButton()),
+ `PushButton(`id("add_redirect_to_masquerade"), `opt(`key_F3), Label::AddButton()),
+ `PushButton(`id("remove_redirect_to_masquerade"), `opt(`key_F5), Label::DeleteButton()),
`HStretch()
)
)
@@ -772,8 +772,8 @@
[]
),
`Left (`HBox (
- `PushButton (`id (`add_br), _("&Add...")),
- `PushButton (`id (`delete_br), _("&Delete"))
+ `PushButton (`id (`add_br), `opt(`key_F3), _("&Add...")),
+ `PushButton (`id (`delete_br), `opt(`key_F5), _("&Delete"))
))
);
@@ -909,8 +909,8 @@
[]
),
`HBox (
- `PushButton(`id("add_custom_rule"), Label::AddButton()),
- `PushButton(`id("remove_custom_rule"), Label::DeleteButton()),
+ `PushButton(`id("add_custom_rule"), `opt(`key_F3), Label::AddButton()),
+ `PushButton(`id("remove_custom_rule"), `opt(`key_F5), Label::DeleteButton()),
`HStretch ()
)
)
--
To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-commit+help(a)opensuse.org
1
0
[yast-commit] r66704 - /trunk/autoinstallation/doc/xml/BootMedia.xml
by emap@svn2.opensuse.org 04 Nov '11
by emap@svn2.opensuse.org 04 Nov '11
04 Nov '11
Author: emap
Date: Fri Nov 4 16:16:16 2011
New Revision: 66704
URL: http://svn.opensuse.org/viewcvs/yast?rev=66704&view=rev
Log:
edited by emap
Modified:
trunk/autoinstallation/doc/xml/BootMedia.xml
Modified: trunk/autoinstallation/doc/xml/BootMedia.xml
URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/BootMed…
==============================================================================
--- trunk/autoinstallation/doc/xml/BootMedia.xml (original)
+++ trunk/autoinstallation/doc/xml/BootMedia.xml Fri Nov 4 16:16:16 2011
@@ -2,16 +2,15 @@
<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.
+ 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 bootable 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
+ 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
@@ -27,9 +26,8 @@
<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.
+ special, pre-defined file name (<filename>autoinst.xml</filename>). &yast2; will check for
+ <filename>autoinst.xml</filename> upon startup. If it finds the file, &yast2; switches from interactive to automated installation.
</para>
</section>
@@ -37,14 +35,13 @@
<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>
+ media, i.e. with a floppy to hold the control file. Alternatively, save the control file via the network interface on a remote machine.
+ </para><remark>emap 2011-11-04: I'm surprised there's still mention of floppies but not a word about USB sticks, etc.</remark>
<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.
+ saved on the CD-ROM. This method requires creation of new CD-ROMs
+ every time you wish to change the configuration.
</para>
</section>
</section>
--
To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org
For additional commands, e-mail: yast-commit+help(a)opensuse.org
1
0