November 2011 - YaST Commits - openSUSE Mailing Lists

[yast-commit] r66723 - /trunk/autoinstallation/doc/xml/MailSection.xml
by emap＠svn2.opensuse.org 06 Nov '11

06 Nov '11

Author: emap Date: Sun Nov 6 13:05:05 2011 New Revision: 66723 URL: http://svn.opensuse.org/viewcvs/yast?rev=66723&view=rev Log: edited by emap Modified: trunk/autoinstallation/doc/xml/MailSection.xml Modified: trunk/autoinstallation/doc/xml/MailSection.xml URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/MailSec… ============================================================================== --- trunk/autoinstallation/doc/xml/MailSection.xml (original) +++ trunk/autoinstallation/doc/xml/MailSection.xml Sun Nov 6 13:05:05 2011 @@ -21,9 +21,9 @@ Mail Configuration (Sendmail or Postfix) </title> <para> - For the mail configuration of the client this + For the mail configuration of the client, this module lets you create a detailed mail configuration. The module - contains various options and it is recommended to use it at least for + contains various options. We recommended you use it at least for the initial configuration. </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] r66722 - /trunk/autoinstallation/doc/xml/NTPSection.xml
by emap＠svn2.opensuse.org 06 Nov '11

06 Nov '11

Author: emap Date: Sun Nov 6 13:03:29 2011 New Revision: 66722 URL: http://svn.opensuse.org/viewcvs/yast?rev=66722&view=rev Log: edited by emap Modified: trunk/autoinstallation/doc/xml/NTPSection.xml Modified: trunk/autoinstallation/doc/xml/NTPSection.xml URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/NTPSect… ============================================================================== --- trunk/autoinstallation/doc/xml/NTPSection.xml (original) +++ trunk/autoinstallation/doc/xml/NTPSection.xml Sun Nov 6 13:03:29 2011 @@ -23,9 +23,9 @@ </title> <para> Select whether to start the NTP daemon when booting the system. The NTP - daemon resolves host names when initializing. The first + daemon resolves host names <remark>emap 2011-11-06: Really the NTP daemon?</remark>when initializing. The first synchronization of the clock is performed before the NTP daemon is - started. To use this host for initial synchronization configure the + started. To use this host for initial synchronization, configure the property <emphasis>initial_sync</emphasis>. </para> <para> @@ -33,7 +33,7 @@ chroot jail, set <emphasis>start_in_chroot</emphasis>. Starting any daemon in a chroot jail is more secure and strongly recommended. To adjust NTP servers, peers, local clocks, and NTP broadcasting, - add the appropriate entry to the control file. an example of various + add the appropriate entry to the control file. An example of various configuration options is shown below. </para> <example> -- 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] r66721 - /trunk/autoinstallation/doc/xml/NFSSection.xml
by emap＠svn2.opensuse.org 06 Nov '11

06 Nov '11

Author: emap Date: Sun Nov 6 12:42:12 2011 New Revision: 66721 URL: http://svn.opensuse.org/viewcvs/yast?rev=66721&view=rev Log: edited by emap Modified: trunk/autoinstallation/doc/xml/NFSSection.xml Modified: trunk/autoinstallation/doc/xml/NFSSection.xml URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/NFSSect… ============================================================================== --- trunk/autoinstallation/doc/xml/NFSSection.xml (original) +++ trunk/autoinstallation/doc/xml/NFSSection.xml Sun Nov 6 12:42:12 2011 @@ -21,17 +21,16 @@ NFS Client and Server </title> <para> - Configuration of a system as an NFS client or an NFS server is - possible and can be done using the configuration system. The - following examples shows how both NFS client and server can be configured. + Configuring a system as an NFS client or an NFS server is + can be done using the configuration system. The + following examples show how both NFS client and server can be configured. </para> <para> - Up to SLE11 and openSUSE 11.2, the following structure of NFS client configuration - is used: + Up to SLE11 and openSUSE 11.2, the following structure of NFS client configuration has been used: </para> <example> <title> - Network configuration: NFS client + Network Configuration: NFS Client </title> <screen> @@ -40,16 +39,18 @@ </screen> </example> <para> - From openSUSE 11.3 (SLE12 respectively) on, the structure of NFS client configuration - has changed. Some global configuration options were introduced - <emphasis>enable_nfs4</emphasis> - to switch NFS4 support on/off and <emphasis>idmapd_domain</emphasis> to define domain name for - rpc.idmapd (this only makes sense with enabled NFS4). Attention: the old structure is not - compatible with the new one and the profiles with NFS section created on older releases will not - work with newer products. + From openSUSE 11.3 (SLE12 respectively) on, the structure of NFS + client configuration has changed. Some global configuration options + were introduced: <emphasis>enable_nfs4</emphasis> to switch NFS4 + support on/off and <emphasis>idmapd_domain</emphasis> to define domain + name for rpc.idmapd (this only makes sense with enabled + NFS4). Attention: the old structure is not compatible with the new one + and the profiles with an NFS section created on older releases will + not work with newer products. </para> <example> <title> - Network configuration: NFS client - new style (openSUSE 11.3 and newer) + Network Configuration: NFS Client - New Style (openSUSE 11.3 and newer) </title> <screen> @@ -60,7 +61,7 @@ <example> <title> - Network configuration: NFS Server + Network Configuration: NFS Server </title> <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] r66720 - /trunk/autoinstallation/doc/xml/LDAPSection.xml
by emap＠svn2.opensuse.org 06 Nov '11

06 Nov '11

Author: emap Date: Sun Nov 6 12:37:57 2011 New Revision: 66720 URL: http://svn.opensuse.org/viewcvs/yast?rev=66720&view=rev Log: edited by emap Modified: trunk/autoinstallation/doc/xml/LDAPSection.xml Modified: trunk/autoinstallation/doc/xml/LDAPSection.xml URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/LDAPSec… ============================================================================== --- trunk/autoinstallation/doc/xml/LDAPSection.xml (original) +++ trunk/autoinstallation/doc/xml/LDAPSection.xml Sun Nov 6 12:37:57 2011 @@ -22,12 +22,12 @@ </title> <para> The installed machine can be set up as an - <emphasis>> &ldap; client</emphasis> to authenticate users with an + <emphasis>&ldap; client</emphasis> to authenticate users with an OpenLDAP; server. Required data are the name of the search base (base DN, e.g, dc=mydomain,dc=com) - and the IP address of the &ldap; server (e.g., 10.20.0.2). + and the IP address of the &ldap; server (e.g., 10.20.0.2). </para> <para> - If &ldap; is activated, <emphasis>NSS</emphasis> and <emphasis>PAM</emphasis> + If &ldap; is activated, <emphasis>NSS</emphasis> and <emphasis>PAM</emphasis> will be configured accordingly to use &ldap; for user authentication. </para> &example.ldapclient; -- 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] r66719 - /trunk/autoinstallation/doc/xml/NetworkSection.xml
by emap＠svn2.opensuse.org 06 Nov '11

06 Nov '11

Author: emap Date: Sun Nov 6 12:34:51 2011 New Revision: 66719 URL: http://svn.opensuse.org/viewcvs/yast?rev=66719&view=rev Log: edited by emap Modified: trunk/autoinstallation/doc/xml/NetworkSection.xml Modified: trunk/autoinstallation/doc/xml/NetworkSection.xml URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Network… ============================================================================== --- trunk/autoinstallation/doc/xml/NetworkSection.xml (original) +++ trunk/autoinstallation/doc/xml/NetworkSection.xml Sun Nov 6 12:34:51 2011 @@ -18,32 +18,33 @@ ]> <section id="CreateProfile.Network"> <title> - Network configuration + Network Configuration </title> <section id="Configuration.Network.Devices"> <title> - Network devices, DNS and Routing. + Network Devices, DNS and Routing. </title> <para> Network configuration is used to connect a single &company-suse; Linux - workstation to an Ethernet-based LAN or to configure dial-up - connection. More complex configuration (multiple network cards, - routing, etc.) is also provided. With this module it's possible to - configure and setup Ethernet Controllers and Token-Ring Controllers. + workstation to an Ethernet-based LAN or to configure a dial-up + connection. More complex configurations (multiple network cards, + routing, etc.) are also provided. With this module it is possible to + configure and setup Ethernet controllers and Token-Ring controllers. </para> <para> - In the networking section, when this option is set to true (default is false, this option is available since openSUSE 11.2 but not SLES11): + In the networking section, set this option to "true" (default is + "false", available since openSUSE 11.2 but not in SLES11): </para> <screen> <keep_install_network config:type="boolean">true</keep_install_network> </screen> <para> - YaST will keep network settings created during installation (via Linuxrc) - and/or merge it with network settings from the AutoYaST profile (if these are defined). - AutoYaST settings have higher priority than already present configuration files. - YaST will write ifcfg-* files from profile without removing old ones. - If there is none (or empty) dns and routing section, YaST will keep already present values. Otherwise settings from the profile will be applied. + &yast; will keep network settings created during installation (via Linuxrc) + and/or merge it with network settings from the &ay; profile (if defined). + &ay; settings have higher priority than already present configuration files. + &yast; will write ifcfg-* files from profile without removing old ones. + If there is an empty or no dns and routing section, &yast; will keep already present values. Otherwise settings from the profile will be applied. </para> <para> To configure network settings and activate networking automatically, @@ -58,21 +59,20 @@ Proxy </title> <para> - Configure your Internet proxy (caching) settings using this - resource. + Configure your Internet proxy (caching) settings. </para> <para> <emphasis>HTTP proxy</emphasis> is the name of the proxy server for your access to the world wide web (WWW). <emphasis>FTP proxy</emphasis> is the name of the proxy server for your access to the file transfer services (FTP). - <emphasis>No proxy</emphasis> domains is a list of domains for - which the requests should be done directly without caching. + <emphasis>No proxy</emphasis> domains<remark>emap 2011-11-06: Does 'domains' belong here? Delete or put within 'emphasis' tag?</remark> is a list of domains for + which requests should be carried out directly without caching. </para> <para> If you are using a proxy server with authorization, fill in Proxy user name and Proxy password. </para> <example> <title> - Netwrok configuration: Proxy + Network configuration: Proxy </title> <screen> <xi:include href="examples/example.proxy.xml" parse="text" @@ -91,20 +91,23 @@ how the services should be configured (netd_conf). </para> <para> - A service description element has conceptually two parts: key and - non-key. When writing the configuration, services are matched using - the key fields and to the matching service, non-key fields are - applied. If no service matches, it is created. If more services - match, a warning is reported. The key fields are script, service, - protocol and server. - </para> - <para> - Service and protocol are matched literally. script is the base name - of the config file: usually a file in<filename> /etc/xinetd.d</filename>, for example "echo-udp", - or "inetd.conf". For compatibility with 8.2, server is matched more - loosely: if it is <filename>/usr/sbin/tcpd</filename>, the real server name is taken from - server_args. After that, the basename of the first - whitespace-sparated word is taken and these values are compared. + A service description element has two parts: key and non-key. When + writing the configuration, services are matched using the key fields; + to the matching service, non-key fields are applied. If no service + matches, it is created. If more services match, a warning is + reported. The key fields are <emphasis>script, service, protocol and + server.</emphasis> + </para> + <para> + <emphasis>service</emphasis> and <emphasis>protocol</emphasis> are + matched literally. <emphasis>script</emphasis> is the base name of the + config file: usually a file in<filename> /etc/xinetd.d</filename>, for + example "echo-udp", or "inetd.conf". For compatibility with 8.2, + <emphasis>server</emphasis> is matched more loosely: if it is + <filename>/usr/sbin/tcpd</filename>, the real server name is taken + from <emphasis>server_args</emphasis>. After that, the basename of the + first whitespace-separated word is taken and these values are + compared. </para> &example.inetd; -- 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] r66718 - /trunk/autoinstallation/doc/xml/FilesSection.xml
by emap＠svn2.opensuse.org 06 Nov '11

06 Nov '11

Author: emap Date: Sun Nov 6 12:14:53 2011 New Revision: 66718 URL: http://svn.opensuse.org/viewcvs/yast?rev=66718&view=rev Log: edited by emap Modified: trunk/autoinstallation/doc/xml/FilesSection.xml Modified: trunk/autoinstallation/doc/xml/FilesSection.xml URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/FilesSe… ============================================================================== --- trunk/autoinstallation/doc/xml/FilesSection.xml (original) +++ trunk/autoinstallation/doc/xml/FilesSection.xml Sun Nov 6 12:14:53 2011 @@ -18,41 +18,41 @@ ]> <section id="createprofile.completeconf"> - <title>Adding complete configurations</title> + <title>Adding Complete Configurations</title> <para> For many applications and services you might have prepared a - configuration file which should be copied in a complete form to some - location in the installed system. This is for example if you are - installing a web server and have a <emphasis>ready to go</emphasis> + configuration file which should be copied to the appropriate + location in the installed system, for example if you are + installing a web server and have a <emphasis>ready to go</emphasis> server configuration file (<filename>httpd.conf</filename>). </para> <para> Using this resource, you can embed the file into the control file by - specifying the final path on the installed system. &yast2; will copy this + specifying the final path on the installed system. &yast; will copy this file to the specified location. </para> <para> This feature requires the autoyast2 package to be installed. If the package is - missing, AutoYaST will silently ignore the <emphasis>files</emphasis> section. - Since openSUSE 11.1 and SLES11 AutoYaST will install the package on it's own if - it's missing. + missing, &ay; will silently ignore the <emphasis>files</emphasis> section. + Since openSUSE 11.1 and SLES11, &ay; will install the package automatically if + it is missing. </para> <para> - Since openSUSE 11.1 and SLES11 you can specify a <emphasis>file_location</emphasis> - where the file should be retrieved from, like an HTTP server for example. That would - look like this <emphasis><file_location>http://my.server.site/issue</file_location></emphasis> + Since openSUSE 11.1 and SLES11, you can specify the <emphasis>file_location</emphasis> + where the file should be retrieved from. For an HTTP server this would + look like: <emphasis><file_location>http://my.server.site/issue</file_location></emphasis>. </para> <para> - Since openSUSE 11.2 (not SLES11) you can create directories by specifying a file_path that ends with a slash. + Since openSUSE 11.2 (not SLES11), you can create directories by specifying a <emphasis>file_path</emphasis> that ends with a slash. </para> &example.files; <para> - A more advanced example is shown below. This configuration will create - a file using the content supplied in <emphasis>file_contents</emphasis> - and will change the permissions and ownership of the file. After the - file has been copied to the system, a script is executed which can be - used to manipulate the file and prepare it for the environment of the client. + A more advanced example is shown below. This configuration will create a + file using the content supplied in <emphasis>file_contents</emphasis> + and change the permissions and ownership of the file. After the file has + been copied to the system, a script is executed, which can be used to + manipulate the file and prepare it for the environment of the client. </para> &example.filesadv; </section> -- 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] r66717 - /trunk/autoinstallation/doc/xml/RunlevelSection.xml
by emap＠svn2.opensuse.org 05 Nov '11

05 Nov '11

Author: emap Date: Sat Nov 5 17:44:26 2011 New Revision: 66717 URL: http://svn.opensuse.org/viewcvs/yast?rev=66717&view=rev Log: edited by emap Modified: trunk/autoinstallation/doc/xml/RunlevelSection.xml Modified: trunk/autoinstallation/doc/xml/RunlevelSection.xml URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Runleve… ============================================================================== --- trunk/autoinstallation/doc/xml/RunlevelSection.xml (original) +++ trunk/autoinstallation/doc/xml/RunlevelSection.xml Sat Nov 5 17:44:26 2011 @@ -18,29 +18,29 @@ ]> <section id="CreateProfile.Services"> <title> - Services and Run-levels + Services and Runlevels </title> <para> - With the run-level resource you can set the default run-level and specify + With the runlevel resource you can set the default runlevel and specify in detail which system services you want to be started in which run-level. </para> <para> - The default property specifies the <emphasis>default</emphasis> run - level of the system. Changes to the default run-level will take effect - the next time you boot the system. After installation is completed, - the system has run-level 5, which is <emphasis>Full multiuser with - network and XDM</emphasis>. If you have configured a system with no - X11, then it is recommended to reboot the system after the first stage - using the <emphasis>reboot</emphasis> property in the <emphasis>general</emphasis> resource. - + The <emphasis>default</emphasis> property specifies the default runlevel + of the system. Changes to the default runlevel will take effect the next + time you boot the system. After the installation is completed, the + system runs in runlevel 5, which is <emphasis>full multiuser with + network and XDM</emphasis>. If you have configured a system with no X11, + it is recommended to reboot the system after stage 1, using the + <emphasis>reboot</emphasis> property in the <emphasis>general</emphasis> + resource.<remark>emap 2011-11-05: Something missing, like setting + "default" to runlevel 3?</remark> </para> <para> - A service should run in using a space delimited list of the run-levels - as shown in the following example. An alternative to specifying the - exact run-levels is to change the status of the service by either - enabling or disabling it using the - <emphasis>service_status</emphasis> property. + Specify in which runlevels a service should run via a space separated + list of the runlevels, as shown in the following example. Alternatively + change the status of the service by either enabling or disabling it + using the <emphasis>service_status</emphasis> property. </para> &example.runlevels; -- 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] r66716 - /trunk/autoinstallation/doc/xml/SoftwareSection.xml
by emap＠svn2.opensuse.org 05 Nov '11

05 Nov '11

Author: emap Date: Sat Nov 5 17:30:39 2011 New Revision: 66716 URL: http://svn.opensuse.org/viewcvs/yast?rev=66716&view=rev Log: edited by emap Modified: trunk/autoinstallation/doc/xml/SoftwareSection.xml Modified: trunk/autoinstallation/doc/xml/SoftwareSection.xml URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Softwar… ============================================================================== --- trunk/autoinstallation/doc/xml/SoftwareSection.xml (original) +++ trunk/autoinstallation/doc/xml/SoftwareSection.xml Sat Nov 5 17:30:39 2011 @@ -24,19 +24,18 @@ <section id="Software.Selections.sles10"> <title> - Package Selections with patterns + Package Selections with Patterns </title> <para> - SLES10 no longer supports <emphasis>selections</emphasis> but uses - <emphasis>patterns</emphasis> now. Autoyast is not be able to convert - selections into patterns and so you have to do that on your own. - If you want to use a SLES9 autoyast profile to install a SLES10 - server, you have to remove all <emphasis>addon</emphasis> entries and the - <emphasis>base</emphasis> entry. Patterns are configured like this: + SLES10 no longer supports <emphasis>selections</emphasis> but uses + <emphasis>patterns</emphasis>. &ay; cannot convert selections to + patterns. If you want to use a SLES9 &ay; profile to install a SLES10 + server, you have to remove all <emphasis>addon</emphasis> entries and + the <emphasis>base</emphasis> entry. Patterns are configured like this: </para> <example> <title> - Package selection in control file with patterns + Package Selection in Control File with Patterns </title> <screen> <xi:include href="examples/example.software.patterns.xml" parse="text" @@ -44,8 +43,9 @@ </screen> </example> <para> - As you can see, the <emphasis>packages</emphasis> section is still the same like on - a SLES9. Just the <emphasis>addon</emphasis> and <emphasis>base</emphasis> is gone. + The <emphasis>packages</emphasis> section is still the same as on a + SLES9. Just the <emphasis>addon</emphasis> and <emphasis>base</emphasis> + sections are gone. </para> </section> <section> @@ -56,13 +56,12 @@ This feature is available since openSUSE 11.1 but not in SLES11. </para> <para> - Since openSUSE 11.0 you can choose to use images during installation to speed up the installation. - This is available in openSUSE 11.1 too. At then end, in the installed system, there is - no difference visible if you did an image or a single RPM installation. + Since openSUSE 11.0 you can use images during installation to speed up the installation. + This feature is available in openSUSE 11.1 as well. </para> <example> <title> - Activating images deployment + Activating Image Deployment </title> <screen> <xi:include href="examples/example.software.images.xml" parse="text" @@ -73,42 +72,35 @@ <section> <title> - Installing additional and customized Packages + Installing Additional and Customized Packages </title> <para> In addition to the packages available for installation on the CD-ROMs, - you can add external packages including customized kernels. Customized - kernel packages must be compatible to the &company-suse; packages and must + you can add external packages including customized kernels. Customized + kernel packages must be compatible to the &company-suse; packages and must install the kernel files to the same locations. </para> <para> - Unlike earlier versions, to install custom and external packages - there is no need for a special resource in the control - file. Instead you need to re-create the package database and update - it with any new packages or new package versions in the source repository. - </para> - <para> - A script is provided for this task which will query packages - available in the repository and create the required package - database. - </para> - - <para> - Creating a new package database is only needed if new RPMs - (i.e. update RPMs) were added. To re-create the database, use the - <command>/usr/bin/create_package_descr</command> - command. For example, use this command line to create the package - database. (When creating the database, all languages will be reset to English). + Unlike in earlier in versions, you do not need a special resource in the + control file to install custom and external packages. Instead you need + to re-create the package database and update it with any new packages or + new package versions in the source repository. + </para> + <para> + A script is provided for this task which will query packages available + in the repository and create the package database. Use the + command <command>/usr/bin/create_package_descr</command>. When creating + the database, all languages will be reset to English. </para> <example> - <title>Creating package database</title> + <title>Creating Package Database</title> <screen> cd /usr/local/CDs/LATEST/suse create_package_descr -x PATH_TO_EXTRA_PROV -d /usr/local/CDs/LATEST/suse </screen> </example> <note> - <title>Change starting from SUSE Linux 9.1/SLES 9</title> + <title>Change starting with SUSE Linux 9.1/SLES 9</title> <para>To provide extra dependencies which can not be extracted from the rpm files, an extra file with missing dependencies is available in the directory <filename>suse/setup/descr</filename>. The file @@ -123,31 +115,34 @@ </para> <para> The advantage of this method is that you can keep an up-to-date - repository with fixed and updated package (i.e. from &company-suse; FTP + repository with fixed and updated package (e.g. from &company-suse; FTP server). Additionally this method makes the creation of custom CD-ROMs easier. </para> <note> - <title>Change starting from SUSE Linux 10.1/SLES 10</title> + <title>Changes starting with SUSE Linux 10.1/SLES 10</title> <para> - With SLES10/SL10.1, the concept of adding own RPMs to an installation source has changed. - The <emphasis>yast/order</emphasis> and <emphasis>yast/instorder</emphasis> is no longer supported. Neither - by AutoYaST nor by YaST. To add own RPMs to an installation source (that includes add-on products like the - SDK) you have to add a file <emphasis>add_on_products</emphasis> to the CD1 of the main product. + With SLES10/SL10.1, the concept of adding your own RPMs to an + installation source has changed. Neither + <emphasis>yast/order</emphasis> nor + <emphasis>yast/instorder</emphasis> are supported any longer by &ay; + or by &yast;. To add your own RPMs to an installation source (or + add-on products like the SDK), add a file + <emphasis>add_on_products</emphasis> to CD1 of the main product. </para> <screen> media_url [path_on_media [product_1 [product_2 [....]]] </screen> <para> - media_url is URL of the media itself - path_on_media is path of the catalog on the media. If not present, / (root) is assumed - product_1 and following are the names for products, which should be marked for installation. If no product is mentioned, all products found on the media are selected for installation. - For example: -</para><screen> -http://192.168.66.6/SLES10/sdk/CD1 -http://192.168.66.6/SLES10/CD1/updates + media_url is the URL of the media, path_on_media is the path to the + catalog on the media. If not present, / (root) is assumed. product_1 + and following are the names of products, which should be marked for + installation. If no product is specified, all products found on the + media are selected for installation. For example: </para><screen> + http://192.168.66.6/SLES10/sdk/CD1 + http://192.168.66.6/SLES10/CD1/updates </screen> <para> - Besides that <emphasis>add_on_products</emphasis> file, you can use the autoyast profile to specify add-on products. For example: + Besides the <emphasis>add_on_products</emphasis> file, you can use the &ay; profile to specify add-on products. For example: </para> <screen> <add-on> @@ -163,19 +158,19 @@ </add-on> </screen> <para> - With that entry in the autoyast profile, the <emphasis>add_on_products</emphasis> file is not necessary. - Since openSUSE 11.0 AutoYaST can ask the user to make the add-on available intead of reporting a timed out error when the add-on can't be found at the given location. Set ask_on_error to true for that (the default is false). - Your add-on can be on a different CD/DVD than the installation source then. + With this entry in the &ay; profile, the <emphasis>add_on_products</emphasis> file is not necessary. + Since openSUSE 11.0, &ay; can ask the user to make add-on products available instead of reporting a time-out error when an add-on product cannot be found at the given location. Set ask_on_error to "true" (the default is "false"). + Then your add-on product can be on a different CD/DVD than the installation source. </para> <para> - YaST checks the signatures of files on the installation source now. If a <emphasis>content</emphasis> file is - not signed, during a manual installation YaST asks the user what to do. During an autoinstallation, the - installation source gets rejected silently. + &yast; checks the signatures of files on the installation source. If a <emphasis>content</emphasis> file is + not signed, during a manual installation &yast; asks the user what to do. During an automatic installation, the + installation source is rejected silently. </para> </note> <para> - If you want to use unsigned installation sources with autoyast, you can turn of the checks with the following - configuration in your autoyast profile (part of the <emphasis>general</emphasis> section. + If you want to use unsigned installation sources with &ay;, turn off the checks with the following + configuration in your &ay; profile (part of the <emphasis>general</emphasis> section. </para> <para> The following elements must be between the <general><signature-handling> ... </signature-handling></general> tags. @@ -192,53 +187,53 @@ <tbody> <row> <entry>accept_unsigned_file</entry> - <entry><para>the installer will accept unsigned files like the content file</para> + <entry><para>If set to "true", &ay; will accept unsigned files like the content file.</para> <para><literal><accept_unsigned_file config:type="boolean">true</accept_unsigned_file></literal></para> </entry> - <entry>optional. If left out, autoyast lets yast decide what to do</entry> + <entry>Optional. If left out, &ay; lets &yast; decide what to do.</entry><remark>emap 2011-11-05: Is this correct? How will YaST make the decision? Above we write that YaST will ask the user, but during auto-install the package will be rejected. So which is it?</remark> </row> <row> <entry>accept_file_without_checksum</entry> - <entry><para>the installer will accept files without a checksum in the content file</para> + <entry><para>If set to "true", &ay; will accept files without a checksum in the content file.</para> <para><literal><accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum></literal></para> </entry> - <entry>optional. If left out, autoyast lets yast decide what to do</entry> + <entry>Optional. If left out, &ay; lets &yast; decide what to do.</entry><remark>emap 2011-11-05: See my previous remark.</remark> </row> <row> <entry>accept_verification_failed</entry> - <entry><para>the installer will accept files where the verification of the signature failed. So the file was signed but the check failed.</para> + <entry><para>If set to "true", &ay; will accept signed files even when the verification of the signature failed.</para> <para><literal><accept_verification_failed config:type="boolean">true</accept_verification_failed></literal></para> </entry> - <entry>optional. If left out, autoyast lets yast decide what to do</entry> + <entry>Optional. If left out, &ay; lets &yast; decide what to do.</entry><remark>emap 2011-11-05: Same here. Unless I'm just not getting it, please fix all other occurrences below.</remark> </row> <row> <entry>accept_unknown_gpg_key</entry> - <entry><para>the installer will accept new gpg keys on the installation source that are used to sign the content file for example</para> + <entry><para>If set to "true", &ay; will accept new gpg keys on the installation source, for example the key used to sign the content file.</para> <para><literal><accept_unknown_gpg_key config:type="boolean">true</accept_unknown_gpg_key></literal></para> </entry> - <entry>optional. If left out, autoyast lets yast decide what to do</entry> + <entry>Optional. If left out, &ay; lets &yast; decide what to do.</entry> </row> <row> <entry>accept_non_trusted_gpg_key</entry> - <entry><para>This basically means, we know the key, but it is not trusted</para> + <entry><para>This basically means, we know the key, but it is not trusted.</para> <para><literal><accept_non_trusted_gpg_key config:type="boolean">true</accept_non_trusted_gpg_key></literal></para> </entry> - <entry>optional. If left out, autoyast lets yast decide what to do</entry> + <entry>Optional. If left out, &ay; lets &yast; decide what to do.</entry> </row> <row> <entry>import_gpg_key</entry> - <entry><para>the installer will accept and import new gpg keys on the installation source in it's database.</para> + <entry><para>If set to "true", &ay; will accept and import new gpg keys on the installation source in its database.</para> <para><literal><import_gpg_key config:type="boolean">true</import_gpg_key></literal></para> </entry> - <entry>optional. If left out, autoyast lets yast decide what to do</entry> + <entry>Optional. If left out, &ay; lets &yast; decide what to do.</entry> </row> </tbody> </tgroup> </informaltable> <para> - Since openSUSE 10.3 it's possible to configure the signature handling for each add-on individually. The following elements must be between the - <signature-handling> section of the individual add-on. + Since openSUSE 10.3, it is possible to configure the signature handling for each add-on product individually. The following elements must be between the + <signature-handling> section of the individual add-on product. </para> <informaltable frame='top'> @@ -253,28 +248,28 @@ <tbody> <row> <entry>accept_unsigned_file</entry> - <entry><para>the installer will accept unsigned files like the content file for this add-on product</para> + <entry><para>If set to "true", &ay; will accept unsigned files like the content file for this add-on product.</para> <para><literal><accept_unsigned_file config:type="boolean">true</accept_unsigned_file></literal></para> </entry> - <entry>optional. If left out, the global signature-handing in the <general> section is used.</entry> + <entry>Optional. If left out, the global signature-handing in the <general> section is used.</entry> </row> <row> <entry>accept_file_without_checksum</entry> - <entry><para>the installer will accept files without a checksum in the content file for this add-on</para> + <entry><para>If set to "true", &ay; will accept files without a checksum in the content file for this add-on.</para> <para><literal><accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum></literal></para> </entry> - <entry>optional. If left out, the global signature-handing in the <general> section is used.</entry> + <entry>Optional. If left out, the global signature-handing in the <general> section is used.</entry> </row> <row> <entry>accept_verification_failed</entry> - <entry><para>the installer will accept files where the verification of the signature failed. So the file was signed but the check failed.</para> + <entry><para>If set to "true", &ay; will accept signed files even when the verification of the signature fails.</para> <para><literal><accept_verification_failed config:type="boolean">true</accept_verification_failed></literal></para> </entry> - <entry>optional. If left out, the global signature-handing in the <general> section is used.</entry> + <entry>Optional. If left out, the global signature-handing in the <general> section is used.</entry> </row> <row> <entry>accept_unknown_gpg_key</entry> - <entry><para>the installer will accept new gpg keys on the installation source that are used to sign the content file for example</para> + <entry><para>If set to "true", &ay; will accept new gpg keys on the installation source, for example the key used to sign the content file.</para> <screen> <accept_unknown_gpg_key> <all config:type="boolean">false</all> @@ -284,11 +279,11 @@ </accept_unknown_gpg_key> </screen> </entry> - <entry>optional. If left out, the global signature-handing in the <general> section is used.</entry> + <entry>Optional. If left out, the global signature-handing in the <general> section is used.</entry> </row> <row> <entry>accept_non_trusted_gpg_key</entry> - <entry><para>This basically means, we know the key, but it is not trusted</para> + <entry><para>This basically means, we know the key, but it is not trusted.</para> <screen> <accept_non_trusted_gpg_key> <all config:type="boolean">false</all> @@ -302,7 +297,7 @@ </row> <row> <entry>import_gpg_key</entry> - <entry><para>the installer will accept and import new gpg keys on the installation source in it's database.</para> + <entry><para>If set to "true", &ay; will accept and import new gpg keys on the installation source into its database.</para> <screen> <import_gpg_key> <all config:type="boolean">false</all> @@ -312,7 +307,7 @@ </import_gpg_key> </screen> </entry> - <entry>optional. If left out, the global signature-handing in the <general> section is used.</entry> + <entry>Optional. If left out, the global signature-handing in the <general> section is used.</entry> </row> </tbody> </tgroup> @@ -320,7 +315,7 @@ </section> <section> - <title>Kernel packages</title> + <title>Kernel Packages</title> <para> Kernel packages are not part of any selection. The required kernel is determined during installation. If the kernel package is added to any selection @@ -328,13 +323,12 @@ </para> <para> To force the installation of a specific kernel, use the - <emphasis>kernel</emphasis> property. The following is an example - forcing the installation of the default kernel. In this example this - kernel will be installed in any case, even if an SMP or other kernel - is required</para> + <emphasis>kernel</emphasis> property. The following is an example of + forcing the installation of the default kernel. This kernel will be + installed even if an SMP or other kernel is required.</para> <example> <title> - Package selection in control file + Package Selection in Control File<remark>emap 2011-11-05: Should this read: Kernel Selection in Control File?</remark> </title> <screen> <xi:include href="examples/example.kernel.xml" parse="text" @@ -344,25 +338,25 @@ </example> </section> <section> - <title>Removing automatically selected packages</title> + <title>Removing Automatically Selected Packages</title> <para> Some packages are selected automatically either because of a - dependency or because it available in a selection. + dependency or because it is available in a selection. </para> <para> - Removing such packages might break the system consistency and it is - not recommended to remove basic packages unless a replacement which - provides same services is provided. Best example for this case are - <acronym>MTA</acronym> packages. By default, <emphasis>postfix</emphasis> - will be selected and installed. If you wish however to use another - <acronym>MTA</acronym> like <emphasis>sendmail</emphasis>, then - postfix can be removed from the list of selected package using a list - in the software resource. The following example shows how this can be done: - + Removing such packages might break the system consistency and it is not + recommended to remove basic packages unless a replacement which provides + the same services is provided. The best example for this case are + <acronym>MTA</acronym> packages. By default, + <emphasis>postfix</emphasis> will be selected and installed. If you wish + to use another <acronym>MTA</acronym> like + <emphasis>sendmail</emphasis>, then postfix can be removed from the list + of selected package using a list in the software resource. The following + example shows how this can be done: </para> <example> <title> - Package selection in control file + Package Selection in Control File </title> <screen> <xi:include href="examples/example.removesoft.xml" parse="text" @@ -373,9 +367,9 @@ </example> </section> <section> - <title>Installing packages during stage 2</title> + <title>Installing Packages in Stage 2</title> <para> - if you want to install packages after the reboot during stage 2, instead of + If you want to install packages after the reboot during stage 2, instead of during the normal installation process in stage 1, you can use the <emphasis>post-packages</emphasis> element for that: </para> @@ -388,10 +382,10 @@ </screen> </section> <section> - <title>FIXME Title</title> + <title>FIXME Title</title><remark>emap 2011-11-05: Just drawing attention to this fixme. How about: Installing Patterns in Stage 2</remark> <para> - Since SLES11 and openSUSE 11.1 you can install patterns in stage 2 too. - use the <emphasis>post-patterns</emphasis> element for that: + Since SLES11 and openSUSE 11.1, you can also install patterns in stage 2. + Use the <emphasis>post-patterns</emphasis> element for that: </para> <screen> <software> @@ -402,11 +396,10 @@ </screen> </section> <section> - <title>Online update in stage2</title> + <title>Online Update in Stage 2</title> <para> - since openSUSE 11.1 you can do an online update at the end of the installation with the boolean - <emphasis>do_online_update</emphasis>. - Of course that makes only sense if you add an online update repository with the suse-register/customer-center section for example or in a post-script. If the online update repository was available in stage1 already via add-on section, then autoyast has already installed the latest packages available. If a kernel update is done via online-update, a reboot at the end of stage2 is triggered. + Since openSUSE 11.1, you can perform an online update at the end of the installation. Set the boolean <emphasis>do_online_update</emphasis> to "true". + Of course this makes only sense if you add an online update repository in the suse-register/customer-center section, for example, or in a post-script. If the online update repository was available in stage 1 already via add-on section, then &ay; has already installed the latest packages available. If a kernel update is done via online-update, a reboot at the end of stage 2 is triggered. </para> <screen> <software> -- 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] r66715 - /trunk/autoinstallation/doc/xml/PartitioningSection.xml
by emap＠svn2.opensuse.org 05 Nov '11

05 Nov '11

Author: emap Date: Sat Nov 5 16:06:03 2011 New Revision: 66715 URL: http://svn.opensuse.org/viewcvs/yast?rev=66715&view=rev Log: edited by emap Modified: trunk/autoinstallation/doc/xml/PartitioningSection.xml Modified: trunk/autoinstallation/doc/xml/PartitioningSection.xml URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Partiti… ============================================================================== --- trunk/autoinstallation/doc/xml/PartitioningSection.xml (original) +++ trunk/autoinstallation/doc/xml/PartitioningSection.xml Sat Nov 5 16:06:03 2011 @@ -21,13 +21,16 @@ <title>Partitioning</title> <section> - <title>drive configuration</title> + <title>Drive Configuration</title> <warning> <title> - EVMS support dropped in openSUSE 11.1 and SLES11 + EVMS Support Dropped in openSUSE 11.1 and SLES11 </title> <para> -since openSUSE 11.1 and SLES11 there is no longer support for EVMS in the installation system. That means all support for EVMS in AutoYaST was dropped too. Alll EVMS documentation on this page is on valid for SLES10 (all service packs) and openSUSE versions prior openSUSE 11.1 + Since openSUSE 11.1 and SLES11, EVMS is no longer supported in the + installation system. That means all support for EVMS in &ay; was + dropped as well. Alll EVMS documentation here is only valid for SLES10 + (all service packs) and openSUSE versions prior to openSUSE 11.1. </para> </warning> <para> @@ -45,111 +48,110 @@ <tbody> <row> <entry>device</entry> - <entry><para>the device you want to configure in this section. Since SUSE Linux 10.1 and SLES10, you can use persistent device names via id, like <emphasis>/dev/disk/by-id/ata-WDC_WD3200AAKS-75L9A0_WD-WMAV27368122</emphasis>. With SLES10 SP1 and SUSE Linux 10.2, <emphasis>by-path</emphasis> is possible too like <emphasis>/dev/disk/by-path/pci-0001:00:03.0-scsi-0:0:0:0</emphasis>.</para> + <entry><para>The device you want to configure in this section. Since SUSE Linux 10.1 and SLES10, you can use persistent device names via id, like <emphasis>/dev/disk/by-id/ata-WDC_WD3200AAKS-75L9A0_WD-WMAV27368122</emphasis>. With SLES10 SP1 and SUSE Linux 10.2, <emphasis>by-path</emphasis> is possible too, like <emphasis>/dev/disk/by-path/pci-0001:00:03.0-scsi-0:0:0:0</emphasis>.</para> <para><literal><device>/dev/hda</device></literal></para> </entry> - <entry>optional. If left out, autoyast tries to guess the device. A RAID must always have "/dev/md" as device</entry> + <entry>Optional. If left out, &ay; tries to guess the device. A RAID must always have "/dev/md" as device.</entry> </row> <row> <entry>initialize</entry> - <entry><para>if set to true, the partition table gets wiped out before autoyast starts the partition calculation</para> + <entry><para>If set to "true", the partition table gets wiped out before &ay; starts the partition calculation.</para> <para><literal><initialize config:type="boolean">true</initialize></literal></para> </entry> - <entry>optional. The default is false.</entry> + <entry>Optional. The default is "false".</entry> </row> <row> <entry>is_lvm_vg</entry> - <entry><para>This tells autoyast that this device is not a physical device but a LVM volume group (see LVM configuration below)</para> + <entry><para>Specifies if a device is not a physical device but a LVM volume group (see LVM configuration below).</para> <para><literal><is_lvm_vg config:type="boolean">true</is_lvm_vg></literal></para> </entry> - <entry><para>DEPRECATED since SLES10SP1 and SL10.2 - use <emphasis>type</emphasis> instead. Must be true if this device is a LVM volume group. The default is false.</para></entry> + <entry><para><emphasis>Deprecated</emphasis> since SLES10SP1 and SL10.2. Use <emphasis>type</emphasis> instead. Must be "true" if this device is a LVM volume group. The default is "false".</para></entry> </row> <row> <entry>is_evms_vg</entry> - <entry><para>this tells autoyast that this device is not a physical device but an EVMS volume group (see EVMS configuration below)</para> + <entry><para>Specifies if a device is not a physical device but an EVMS volume group (see EVMS configuration below).</para> <para><literal><is_evms_vg config:type="boolean">true</is_evms_vg></literal></para> </entry> - <entry><para>DEPRECATED since SLES10SP1 and SL10.2 - use <emphasis>type</emphasis> instead. Must be true if this device is an EVMS volume group. The default is false.</para></entry> + <entry><para><emphasis>Deprecated</emphasis> since SLES10SP1 and SL10.2. Use <emphasis>type</emphasis> instead. Must be "true" if this device is an EVMS volume group. The default is "false".</para></entry> </row> <row> <entry>partitions</entry> - <entry><para>this is a list of <partition> entries (see table below)</para> + <entry><para>A list of <partition> entries (see table below).</para> <para><literal><partitions config:type="list"><partition>...</partition>...</partitions></literal></para> </entry> - <entry>optional. If no partition is specified, autoyast will create it's own idea of a nice partitioning (see Automated Partitioning below).</entry> + <entry>Optional. If no partitions are specified, &ay; will create a reasonable partitioning (see Automated Partitioning below).</entry> </row> <row> <entry>pesize</entry> - <entry><para>this value makes only sense with LVM/EVMS.</para> + <entry><para>This value makes only sense with LVM/EVMS.</para> <para><literal><pesize>8M</pesize></literal></para> </entry> - <entry>optional. Default is 4M for EVMS/LVM volume groups.</entry> + <entry>Optional. Default is 4M for EVMS/LVM volume groups.</entry> </row> <row> <entry>use</entry> - <entry><para>this parameter tells autoyast which strategy it shall use to partition the harddisc.</para> -<para>You can choose between:</para> + <entry><para>Specifies the strategy &ay; will use to partition the hard disk.</para> +<para>Choose between:</para> <itemizedlist> <listitem> -<para>all (uses the whole device while calculating the new partitioning)</para> +<para>all (uses the whole device while calculating the new partitioning),</para> </listitem> <listitem> -<para>linux (only existing linux partitions are used)</para> +<para>linux (only existing linux partitions are used),</para> </listitem> <listitem> -<para>free (only unused space on the device gets used. No other partitions gets touched)</para> +<para>free (only unused space on the device is used, no other partitions are touched),</para> </listitem> <listitem> -<para>1,2,3 (a list of comma seperated numbers that indicates the partition numbers to use)</para> +<para>1,2,3 (a list of comma separated partition numbers to use).</para> </listitem> </itemizedlist> </entry> - <entry>this parameter should be provided</entry> + <entry>This parameter should be provided.</entry> </row> <row> <entry>type</entry> - <entry><para>this value describes the type of the <emphasis>drive</emphasis> and is a replacement for -<emphasis>is_lvm_vg</emphasis> and <emphasis>is_evms_vg</emphasis> used in SLES10 and SL10.1</para> -<para>You can choose between:</para> + <entry><para>Specify the type of the <emphasis>drive</emphasis> (This parameter replaces <emphasis>is_lvm_vg</emphasis> and <emphasis>is_evms_vg</emphasis> in SLES10 and SL10.1)</para> +<para>Choose between:</para> <itemizedlist> <listitem> -<para>CT_DISK for physical harddisks (default)</para> +<para>CT_DISK for physical hard disks (default),</para> </listitem> <listitem> -<para>CT_LVM for LVM volume groups</para> +<para>CT_LVM for LVM volume groups,</para> </listitem> <listitem> -<para>CT_EVMS for EVMS volume groups</para> +<para>CT_EVMS for EVMS volume groups.</para> </listitem> </itemizedlist> <para><literal><type config:type="symbol">CT_LVM</type></literal></para> </entry> - <entry>optional. Default is CT_DISK for a normal physical harddisk.</entry> + <entry>Optional. Default is CT_DISK for a normal physical hard disk.</entry> </row> <row> <entry>disklabel</entry> - <entry><para>this value describes the type of the partition table</para> -<para>You can choose between:</para> + <entry><para>Describes the type of the partition table.</para> +<para>Choose between:</para> <itemizedlist> <listitem> -<para>msdos</para> +<para>msdos,</para> </listitem> <listitem> -<para>gpt</para> +<para>gpt.</para> </listitem> </itemizedlist> <para><literal><disklabel>gpt</disklabel></literal></para> </entry> - <entry>optional and available since openSUSE 12.1 and SLES11 SP2. Default is to let yast decide what makes sense (msdos in most cases)</entry> + <entry>Optional and available since openSUSE 12.1 and SLES11 SP2. By default &yast; decides what makes sense (msdos in most cases).</entry> </row> <row> <entry>keep_unknown_lv</entry> - <entry><para>This value only makes sense for type=CT_LVM drives. If you are reusing a LVG and you set this to true, all existing LVs in that VG won't be touched unless they are specified in the <partitioning> section. So you can keep existing LVs without need to specify them.</para> + <entry><para>This value only makes sense for type=CT_LVM drives. If you are reusing a LVG and you set this to "true", all existing LVs in that VG will not be touched unless they are specified in the <partitioning> section. So you can keep existing LVs without specifying them.</para> <para><literal><keep_unknown_lv config:type="boolean">false</keep_unknown_lv></literal></para> </entry> - <entry>optional and available since openSUSE 12.1 and SLES11 SP2. The default is false</entry> + <entry>Optional and available since openSUSE 12.1 and SLES11 SP2. The default is "false".</entry> </row> </tbody> </tgroup> @@ -157,7 +159,7 @@ </section> <section> - <title>partition configuration</title> + <title>Partition Configuration</title> <para> The following elements must be between the <partitions config:type="list"><partition> ... </partition></partitions> tags in the <drive> section. </para> @@ -175,64 +177,63 @@ <entry>create</entry> <entry> <para> - the "create" tells autoyast if this partition must be created or if it's already existing + Specify if this partition must be created or if it already exists. </para> <para><literal><create config:type="boolean">false</create></literal></para> </entry> - <entry>if set to false, there must be some information for autoyast which partition this is (like with partition_nr)</entry> + <entry>If set to "false", provide information for &ay; which partition this is (like with partition_nr).</entry> </row> <row> <entry>mount</entry> <entry> <para> - the mountpoint of this partition. + The mountpoint of this partition. </para> <para><literal><mount>/</mount></literal></para> <para><literal><mount>swap</mount></literal></para> </entry> - <entry>you should have at least a root partition (/) and a swap partition</entry> + <entry>You should have at least a root partition (/) and a swap partition.</entry> </row> <row> <entry>fstopt</entry> <entry> <para> - mount options for this partition + Mount options for this partition. </para> <para><literal><fstopt>ro,noatime,user,data=ordered,acl,user_xattr</fstopt></literal></para> </entry> - <entry>see "man mount" for the mountoptions you can use</entry> + <entry>See <command>man mount</command> for available mount options.</entry> </row> <row> <entry>label</entry> <entry> <para> - the label the partition has (useful for the "mountby" parameter - see below). + The label of the partition (useful for the "mountby" parameter; see below). </para> <para><literal><label>mydata</label></literal></para> </entry> - <entry>see "man e2label" for example.</entry> + <entry>See <command>man e2label</command> for an example.</entry> </row> <row> <entry>uuid</entry> <entry> <para> - the uuid the partition has (only useful for the "mountby" parameter - see below). + The uuid of the partition (only useful for the "mountby" parameter; see below). </para> <para><literal><uuid>1b4e28ba-2fa1-11d2-883f-b9a761bde3fb</uuid></literal></para> </entry> - <entry>see "man uuidgen"</entry> + <entry>See <command>man uuidgen</command>.</entry> </row> <row> <entry>size</entry> <entry> <para> - the size for the partition like 4G, 4500M, ... The /boot partition and the swap partition can have "auto" as - size too, to let autoyast calculate a reasonable size for them. On partition can have the value "max" to fillup - all available space. + The size of the partition, e.g. 4G, 4500M, etc. The /boot partition and the swap partition can have "auto" as + size. Then &ay; calculates a reasonable size. One partition can have the value "max" to use all remaining space. </para> <para> - with SUSE Linux 10.2 and SLES10 SP1, you can specify the the size in percentage. So 10% will use 10% of the size - of the harddisk/VG. You can mix auto,max,sizes and percentage like you want. + With SUSE Linux 10.2 and SLES10 SP1, you can specify the the size in percentage. So 10% will use 10% of the size + of the hard disk or VG. You can mix auto, max, size, and percentage as you like. </para> <para><literal><size>10G</size></literal></para> </entry> @@ -242,94 +243,96 @@ <entry>format</entry> <entry> <para> - shall autoyast format the partition? + Specify if &ay; should format the partition. </para> <para><literal><format config:type="boolean">false</format></literal></para> </entry> - <entry>if "create" is true, then it's very likely that this is true too</entry> + <entry>If you set "create" to "true", then you likely want this is option set to "true" as well.</entry> </row> <row> <entry>filesystem</entry> <entry> <para> - what filesystem is used on this partition? + Specify the filesystem to use on this partition: </para> <itemizedlist> <listitem> -<para>reiser (the default)</para> +<para>reiser,</para><remark>emap 2011-11-05: Should 'reiser' read 'reiserfs'? I doubt reiserfs is still the default. Ext3? Then maybe add (default) there and move it to the top of the list.</remark> </listitem> <listitem> -<para>ext2</para> +<para>ext2,</para> </listitem> <listitem> -<para>ext3</para> +<para>ext3,</para> </listitem> <listitem> -<para>xfs</para> +<para>xfs,</para> </listitem> <listitem> -<para>jfs</para> +<para>jfs,</para> </listitem> <listitem> -<para>swap</para> +<para>swap.</para> </listitem> </itemizedlist> <para><literal><filesystem config:type="symbol">reiser</filesystem></literal></para> </entry> - <entry>optional. The default is reiser</entry> + <entry>Optional. The default is reiser</entry><remark>emap 2011-11-05: Fix this too.</remark> </row> <row> <entry>partition_nr</entry> <entry> <para> - the partition_nr this partition has/will have. If you have set create=false or if you use LVM, then you can tell - autoyast which partition you mean by the partition_nr. You can force autoyast to create only - primary partitions by configuring only partition numbers below 5. + The partition number of this partition. If you have set + create=false or if you use LVM, then you can specify the + partition via partition_nr. You can force &ay; to only + create primary partitions by assigning numbers below 5. </para> <para><literal><partition_nr config:type="integer">2</partition_nr></literal></para> </entry> - <entry>in most cases nr. 1-4 are primary partitions and 5-... are logical partitions</entry> + <entry>In most cases, numbers 1 to 4 are primary partitions + while 5 and higher are logical partitions.</entry> </row> <row> <entry>partition_id</entry> <entry> <para> - the partition_id configures the id of the partition. If you want something else than 131 - for linux partition or 130 for swap, you must configure that with partition_id. + The partition_id sets the id of the partition. If you want different identifiers than 131 + for Linux partition or 130 for swap, configure them with partition_id. </para> <para><literal><partition_id config:type="integer">131</partition_id></literal></para> </entry> - <entry>the default is 131 for linux partition. 130 for swap is set by autoyast itself too.</entry> + <entry>The default is 131 for linux partition and 130 for swap.</entry> </row> <row> <entry>filesystem_id</entry> <entry> <para> - look at partition_id above. For historical reasons they represent the same. + See partition_id above. For historical reasons they represent the same. </para> <para><literal><filesystem_id config:type="integer">131</filesystem_id></literal></para> </entry> - <entry>since 10.1 and SLES10 it's recommended to use partition_id instead.</entry> + <entry>Since 10.1 and SLES10 it is recommended to use partition_id instead.</entry> </row> <row> <entry>mountby</entry> <entry> <para> - instead of a partition number, you can tell autoyast to mount a partition by label, uuid, path or id which are the udev path and udev id (see /dev/disk/...) + Instead of a partition number, you can tell &ay; to mount a partition by label, uuid, path or id, which are the udev path and udev id (see /dev/disk/...). </para> <para><literal><mountby config:type="symbol">label</mountby></literal></para> </entry> - <entry>see "label" and "uuid" documentation above</entry> + <entry>See "label" and "uuid" documentation above.</entry> </row> <row> <entry>lv_name</entry> <entry> <para> - if this partition is in a logical volume in a volume group (LVM or EVMS) - (see is_lvm_vg/is_evms_vg parameter in drive configuration) you - must specifiy the logical volume name here. - </para> + If this partition is in a logical volume in a volume group + (LVM or EVMS) specify the logical volume name here (see + is_lvm_vg or is_evms_vg parameter in drive configuration). + </para> <para><literal><lv_name>opt_lv</lv_name></literal></para> </entry> <entry></entry> @@ -338,7 +341,7 @@ <entry>stripes</entry> <entry> <para> - It's an integer that tells AutoYaST to do LVM striping. You can configure across how man devices you want to stripe + An integer that configures LVM striping. Specify across how many devices you want to stripe (spread data). </para> <para><literal><stripes config:type="integer">2</stripes></literal></para> </entry> @@ -348,7 +351,7 @@ <entry>stripesize</entry> <entry> <para> - It's an integer that tells AutoYaST the size of each block in kb + Specify the size of each block in kb. </para> <para><literal><stripesize config:type="integer">4</stripesize></literal></para> </entry> @@ -358,8 +361,8 @@ <entry>lvm_group</entry> <entry> <para> - if this is a physical partition that is used by (part of) a volume group (LVM), - you have to specify the name of the volume + If this is a physical partition used by (part of) a volume + group (LVM), you have to specify the name of the volume group here. </para> <para><literal><lvm_group>system</lvm_group></literal></para> @@ -370,8 +373,9 @@ <entry>evms_group</entry> <entry> <para> - if this physical partition is used by a volume group (EVMS), you have to specify the name of the volume - group here. + If this physical partition is used by a volume group + (EVMS), you have to specify the name of the volume group + here. </para> <para><literal><evms_group>system</evms_group></literal></para> </entry> @@ -381,7 +385,8 @@ <entry>raid_name</entry> <entry> <para> - this physical volume is part of a RAID and the name of the raid is specified here. + If this physical volume is part of a RAID, specify the + name of the RAID. </para> <para><literal><raid_name>/dev/md0</raid_name></literal></para> </entry> @@ -391,7 +396,7 @@ <entry>raid_type</entry> <entry> <para> - this physical volume is part of a RAID and the type of the raid is specified here.. + Specify the type of the RAID. </para> <para><literal><raid_type>raid1</raid_type></literal></para> </entry> @@ -401,7 +406,7 @@ <entry>raid_options</entry> <entry> <para> - special options for the raid are specified here. See below. + Specify RAID options, see below. </para> <para><literal><raid_options>...</raid_options></literal></para> </entry> @@ -412,12 +417,12 @@ <entry> <para> This parameter is available since SLES10 SP1 and OpenSUSE 10.2. - This boolean must be true if an existing partition should be resized. In this case, - you want to set <emphasis>create</emphasis> to <emphasis>false</emphasis> too and in + This boolean must be "true" if an existing partition should be resized. In this case, + you want to set <emphasis>create</emphasis> to <emphasis>false</emphasis> and in most cases you don't want to <emphasis>format</emphasis> the partition. You need to - tell autoyast the <emphasis>partition_nr</emphasis> and the <emphasis>size</emphasis>. - The size can be in percentage of the original size or as a number of the new size, like - <emphasis>800M</emphasis>. <emphasis>max</emphasis> and <emphasis>auto</emphasis> don't + tell &ay; the <emphasis>partition_nr</emphasis> and the <emphasis>size</emphasis>. + The size can be in percentage of the original size or a number, like + <emphasis>800M</emphasis>. <emphasis>max</emphasis> and <emphasis>auto</emphasis> do not work as size here. </para> <para><literal><resize config:type="boolean">false</resize></literal></para> @@ -429,7 +434,7 @@ </informaltable> </section> <section> - <title>raid options</title> + <title>RAID Options</title> <para> The following elements must be between the <partition><raid_options> ... </raid_options></partition> tags. </para> @@ -456,7 +461,7 @@ <entry>parity_algorithm</entry> <entry> <para> - possible values are: left_asymmetric, left_symmetric, right_asymmetric, right_symmetric and since SLES11 SP2 and openSUSE 12.1 you can use parity_first, parity_last, left_asymmetric_6, left_symmetric_6, right_asymmetric_6, right_symmetric_6, parity_first_6, n2, o2, f2, n3, o3, f3 for RAID6 and RAID10 + Possible values are: left_asymmetric, left_symmetric, right_asymmetric, right_symmetric. Since SLES11 SP2 and openSUSE 12.1 you can use: parity_first, parity_last, left_asymmetric_6, left_symmetric_6, right_asymmetric_6, right_symmetric_6, parity_first_6, n2, o2, f2, n3, o3, f3 for RAID6 and RAID10 </para> <para><literal><parity_algorithm>left_asymmetric</parity_algorithm></literal></para> </entry> @@ -466,11 +471,11 @@ <entry>raid_type</entry> <entry> <para> - possible values are raid0,raid1 and raid5 + Possible values are: raid0,raid1 and raid5. </para> <para><literal><raid_type>raid1</raid_type></literal></para> </entry> - <entry>the default is raid1</entry> + <entry>The default is raid1.</entry> </row> </tbody> </tgroup> @@ -482,14 +487,13 @@ </title> <para> - For the automated partitioning to be completed, only the sizes and mount points of - partitions can be provided. All other data needed for successful partitioning - can be calculated during installation if they were not provided in the control file. + For automated partitioning, you only need to provide the sizes and + mount points of partitions. All other data needed for successful partitioning is calculated during installation—unless provided in the control file. </para> <para> - If no partitions are defined and the specified drive is also the drive where - the root partition should be created, the following partitions are created - automatically: + If no partitions are defined and the specified drive is also the drive + where the root partition should be created, the following partitions + are created automatically: </para> <itemizedlist> <listitem> @@ -497,8 +501,8 @@ <emphasis>/boot</emphasis> </para> <para> - Size of the <emphasis>/boot</emphasis> is determined by the - architecture of the target system. + The size of the <emphasis>/boot</emphasis> partition is determined + by the architecture of the target system. </para> </listitem> <listitem> @@ -506,8 +510,8 @@ <emphasis>swap</emphasis> </para> <para> - Size of the <emphasis>swap</emphasis> partitions is determined by the - amount of memory available in the system. + The size of the <emphasis>swap</emphasis> partition is determined + by the amount of memory available in the system. </para> </listitem> <listitem> @@ -515,8 +519,9 @@ <emphasis>/</emphasis> (root partition) </para> <para> - Size of the <emphasis>/</emphasis> (root partition) is the space left - after creating <emphasis>swap</emphasis> and <emphasis>/boot</emphasis>. + The size of the root partition is determined by the space left + after creating <emphasis>swap</emphasis> and + <emphasis>/boot</emphasis>. </para> </listitem> </itemizedlist> @@ -533,7 +538,7 @@ </para> <para> If the drive is already partitioned, it is possible to create the - new partitions using the available space on the hard drive. This + new partitions using the free space on the hard drive. This requires the availability of enough space for all selected packages in addition to swap. </para> @@ -543,8 +548,8 @@ <emphasis>Reuse all available space</emphasis> </para> <para> - This option will lead to the deletion of all existing - partitions (Linux and non-Linux partitions). + Use this option to delete all existing + partitions (Linux and non-Linux). </para> </listitem> @@ -554,11 +559,10 @@ <emphasis>Reuse all available Linux partitions</emphasis> </para> <para> - This option will lead to the deletion of existing Linux - partitions. All other partitions (i.e. Windows) will be - kept. Note that this works only if the Linux partitions are at the end of the device. - - </para> + This option deletes all existing Linux partitions. Other + partitions (i.e. Windows) remain untouched. Note that this works + only if the Linux partitions are at the end of the device. + </para> </listitem> <listitem> @@ -566,60 +570,57 @@ <emphasis>Reuse only specified partitions</emphasis> </para> <para> - This option will lead to the deletion of the specified partitions. - The selection of the partitions scheduled for deletion should be - started from the last available partition. + This option allows you to select specific partitions to delete. + Start the selection with the last available partition. </para> </listitem> </itemizedlist> <para> - Repartitioning using only some of the existing partitions can be - accomplished only if the region selected to be partitioned exists at - the end of the device and only with neighboring partitions. This - means that you cannot repartition a region which contains a partition that - should not be touched in the middle. + Repartitioning only works if the selected partitions are neighbors and + located at the end of the device. </para> <caution> <title>Important Notice</title> <para> - The value provided in the <emphasis>use</emphasis> property determines how existing data and - partitions are treated. The value <emphasis>all</emphasis> means that - <emphasis>ALL</emphasis> data on the disk will - be erased. Make backups and use the <emphasis>confirm</emphasis> - property if you are going to - keep some partitions with important data. This is automated - installation and no pop-ups will notify you about partitions being deleted. + The value provided in the <emphasis>use</emphasis> property + determines how existing data and partitions are treated. The value + <emphasis>all</emphasis> means that <emphasis>ALL</emphasis> data on + the disk will be erased. Make backups and use the + <emphasis>confirm</emphasis> property if you are going to keep some + partitions with important data. During automated installation, + no popups will notify you about partitions being deleted. </para> </caution> <para> - In case of the presence of multiple drives in the target system, all - drives must be identified with their device names and how the partitioning should be performed. + If multiple drives are present in the target system, identify all + drives with their device names and specify how the partitioning should + be performed. </para> <para> - Partition sizes can be given in Gigabytes, Megabytes or can be set to + Partition sizes can be given in gigabytes, megabytes or can be set to a flexible value using the keywords <emphasis>auto</emphasis> and - <emphasis>max</emphasis>. <emphasis>max</emphasis> is used to fill a - partition to the maximal available space on a - drive (Which mean that the partition should be the last one on the drive). - <emphasis>auto</emphasis> can be used to determine the size of - a <emphasis>swap</emphasis> or <emphasis>boot</emphasis> partitions - depending on the memory available and the type of the system. + <emphasis>max</emphasis>. <emphasis>max</emphasis> uses all available + space on a drive, therefore should only be set for the last partition + on the drive. With <emphasis>auto</emphasis> the size of a + <emphasis>swap</emphasis> or <emphasis>boot</emphasis> partition is + determined automatically, depending on the memory available and the + type of the system. </para> <para>A fixed size can be given as shown below:</para> <para> - <emphasis>1GB</emphasis> will create a partition with 1 GB size. - <emphasis>1500MB</emphasis> will create a partition which is 1.5 GB big. + <emphasis>1GB</emphasis> will create a partition of the size 1 GB. + <emphasis>1500MB</emphasis> will create a partition of the size 1.5 GB. </para> <example> - <title>Automated partitioning</title> + <title>Automated Partitioning</title> <para> The following is an example of a single drive system, which is not pre-partitioned and should be automatically partitioned according to - the described pre-defined partition plan. If you leave the device out, - an autodetection of the device will happen. So you don't have to do - different profiles for /dev/sda or /dev/hda systems. + the described pre-defined partition plan. If you do not specify the + device, it will be automatically detected. You do not have to create + different profiles for /dev/sda or /dev/hda systems. </para> <screen> <xi:include href="examples/example.partitioning.xml" parse="text" @@ -628,11 +629,11 @@ </screen> </example> <para> - A more detailed example shows how existing partitions and + A more detailed example shows how existing partitions and multiple drives are handled. </para> <example> - <title>Detailed automated partitioning</title> + <title>Detailed Automated Partitioning</title> <screen> <xi:include href="examples/example.partitioning2.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude"/> @@ -641,85 +642,90 @@ </section> <section> - <title>Advanced Partitioning features</title> + <title>Advanced Partitioning Features</title> <section> - <title>Wipe out partition table</title> + <title>Wipe out Partition Table</title> <para> - In the most cases this is not needed because autoyast can delete partitions - one by one automatically but you have the option to let autoyast clear the partition table - instead of deleting the partitions individually. + In most cases this is not needed because &ay; can delete partitions + one by one automatically, but you have the option to let &ay; clear + the partition table instead of deleting partitions individually. </para> <para> - if you go into the "drive" section, you can add + Go to the "drive" section and add: </para> <screen> <![CDATA[ <initialize config:type="boolean">true</initialize> ]]> </screen> -<para> which tells Autoyast to delete the partition table before it starts to analyse the - actual partitioning and calculates it's partition plan. Of course this means, that you - can't keep any of your existing partitions.</para> +<para> With this setting &ay; will delete the partition table before it starts +to analyse the actual partitioning and calculates its partition plan. Of +course this means, that you cannot keep any of your existing +partitions.</para> </section> <section> <title>Mount Options</title> <para> - By default a file system which is to be mounted is - identified in <filename>/etc/fstab</filename> by the device name. This identification - can be changed so the file system is found by searching - for a <acronym>UUID</acronym> or a volume label. Note that not all file systems can be mounted - by <acronym>UUID</acronym> or a volume label. To specify how a - partition is to be mounted, use the <emphasis>mountby</emphasis> - property which has the <emphasis>symbol</emphasis> type. Possible - options are: + By default a file system to be mounted is identified in + <filename>/etc/fstab</filename> by the device name. This + identification can be changed so the file system is found by searching + for a <acronym>UUID</acronym> or a volume label. Note that not all + file systems can be mounted by <acronym>UUID</acronym> or a volume + label. To specify how a partition is to be mounted, use the + <emphasis>mountby</emphasis> property which has the + <emphasis>symbol</emphasis> type. Possible options are: </para> <itemizedlist> <listitem> - <para>device (default)</para> + <para>device (default),</para> </listitem> <listitem> - <para>label</para> + <para>label,</para> </listitem> <listitem> - <para>UUID</para> + <para>UUID.</para> </listitem> </itemizedlist> <para> If you choose to mount the partition using a label, the name - entered in the <emphasis>label</emphasis> property is used as the + entered for the <emphasis>label</emphasis> property is used as the volume label. </para> <para> - Add any legal mount option allowed in the fourth field of - <filename>/etc/fstab</filename>. Multiple options are separated by commas. Possible fstab options: + Add any legal mount option in the fourth field of + <filename>/etc/fstab</filename>. Multiple options are separated by commas. Possible fstab options: </para> <itemizedlist> <listitem> - <para><emphasis>Mount Read-Only (ro):</emphasis> No writable - access to the file system is possible. Default is false.</para> - + <para><emphasis>Mount read-only (ro):</emphasis> No write + access to the file system. Default is "false".</para> </listitem> <listitem> <para><emphasis>No access time (noatime):</emphasis> Access times - are not updated when a file is read. Default is false.</para> - + are not updated when a file is read. Default is "false".</para> </listitem> <listitem> <para><emphasis>Mountable by User (user):</emphasis> The file - system may be mounted by an ordinary user. Default is - false.</para> - + system can be mounted by a normal user. Default is + "false".</para> </listitem> <listitem> <para> - <emphasis>Data Journaling Mode (ordered | journal | - writeback) :</emphasis> Specifies the journaling mode for - file data. journal -- All data is committed into the journal - prior to being written into the main file system. ordered -- - All data is forced directly out to the main file system prior - to its meta data being committed to the journal. writeback -- - Data ordering is not preserved. - </para> + <emphasis>Data Journaling Mode (ordered, journal, + writeback):</emphasis> Specifies the journaling mode for file + data. </para> + <itemizedlist> + <listitem><emphasis>journal</emphasis>: All data is committed to the + journal prior to being written to the main file system. + </listitem> + <listitem><emphasis>ordered</emphasis>: All data is + directly written to the main file system before its meta data is + committed to the journal. + </listitem> + <listitem><emphasis>writeback</emphasis>: Data ordering is not + preserved. + </listitem> + </itemizedlist> </listitem> <listitem> <para> @@ -749,25 +755,24 @@ <section> <title>Keeping Specific Partitions</title> <para> - In some cases you might choose to keep some partitions untouched - and only format specific target partitions, rather than creating them from - scratch. This might be the case of Linux installations have to - co-exist with another operating system or if certain partitions - contain data that you wish to keep untouched. + In some cases you may want to leave partitions untouched and only + format specific target partitions, rather than creating them from + scratch. For example, if different Linux installations coexist, or you + have another operating system installed, likely you do not want to + wipe these out. Or you may want to leave data partitions untouched. </para> <para> Such scenarios require certain knowledge about the target systems and hard drives. Depending on the scenario, you might need to know the exact partition table of the target hard drive with partition - id's, sizes and numbers. With such data you can tell &autoyast; to + ids, sizes and numbers. With this data you can tell &ay; to keep certain partitions, format others and create new partitions if needed. </para> - <para> The following example will keep partitions 1, 2 and 5 and delete - partition 6 to create two new partitions. All kept partitions will - be only formatted. + partition 6 to create two new partitions. All remaining partitions will + only be formatted.<remark>emap 2011-11-05: Not the best example for the scenarios two paras up with coexisting operating systems or data partitions. Who'd want to format those?</remark> </para> <example> <title> @@ -779,9 +784,9 @@ </screen> </example> <para> - The last example requires exact knowledge about the existing partition - table and about the partition numbers of those partitions that - should be kept. In some cases however, such data might be not + The last example requires exact knowledge of the existing partition + table and the partition numbers of those partitions that + should be kept. In some cases however, such data may not be available, especially in a mixed hardware environment with different hard drive types and configurations. The following scenario is for a system with a non-Linux OS with a designated @@ -793,15 +798,14 @@ </figure> <para> - In this scenario and as shown in figure <quote><xref + In this scenario, shown in figure <quote><xref linkend='partitioning-keep1' - endterm="partitioning-keep1.title"/></quote>, &autoyast2; - should not in any case create any new - partitions, instead it should search for certain partition types on the system and use + endterm="partitioning-keep1.title"/></quote>, &ay; + will not create new partitions. Instead it searches for certain partition types on the system and uses them according to the partitioning plan in the control file. No partition numbers are given in this case, only the mount points and - the partition types (Additional configuration data can be provided, - for example file system options, encryption and filesystem type) + the partition types (additional configuration data can be provided, + for example file system options, encryption and filesystem type). </para> <example> <title> Auto-detection of partitions to be kept.</title> @@ -812,15 +816,15 @@ </section> <section> - <title>Using existing mount table (fstab)</title> + <title>Using Existing Mount Table (fstab)</title> <note> <title>New Feature</title> <para> - This option will allow the AutoYaST to use an existing + This option will allow &ay; to use an existing <filename>/etc/fstab</filename> and use the partition data from - from a previous installation. All partitions are kept and no new - partitions are created. The found partitions will be formatted and - mounted as specified in <filename>/etc/fstab</filename> found on a + a previous installation. All partitions are kept and no new + partitions are created. The partitions will be formatted and + mounted as specified in <filename>/etc/fstab</filename> on a Linux root partition. </para> </note> @@ -830,7 +834,7 @@ for example data partitions. If multiple installations are found on the system (multiple root partitions with different <emphasis>fstab</emphasis> files, the installation will abort, unless - the desired root partition is configured in the control file. The + the root partition is configured in the control file. The following example illustrates how this option can be used: </para> <example> @@ -849,7 +853,7 @@ Logical Volume Manager (LVM) </title> <para> - To configure LVM, first you need to create a <emphasis>physical volume</emphasis> using the + To configure LVM, first create a <emphasis>physical volume</emphasis> using the normal partitioning method described above. </para> <example> @@ -867,12 +871,11 @@ </example> <para> - The last example will create a non-formatted partition on device + In the last example, a non-formatted partition is created on device <filename>/dev/sda1</filename> of the type <emphasis>LVM</emphasis> and - with the volume group <emphasis>system</emphasis>. The partition - created will use all available space on this drive. + with the volume group <emphasis>system</emphasis>. This partition + will use all space available on the drive. </para> - <example> <title> LVM Logical Volumes (New syntax) @@ -883,30 +886,30 @@ </screen> </example> <para> - With SUSE Linux 10.1 and all following versions, it's possible to set the <emphasis>size</emphasis> + With SUSE Linux 10.1 and all following versions, it is possible to set the <emphasis>size</emphasis> to <emphasis>max</emphasis> for the logical volumes. Of course, you can only use <emphasis>max</emphasis> - only for one(!) logical volumes. You can't have two logical volumes in one volume group with the - <emphasis>size</emphasis> set to <emphasis>max</emphasis> + for one(!) logical volume. You cannot set two logical volumes in one volume group to + <emphasis>size</emphasis> <emphasis>max</emphasis> </para> </section> <section> <title> - Enterprise Volume Management System (EVMS) - SLES10 only! + Enterprise Volume Management System (EVMS) — SLES10 only! </title> <para> - SLES10 autoyast has EVMS support. SLES11 has not! + SLES10 &ay; has EVMS support. SLES11 has not! </para> <para> - Using EVMS is quite similar to using LVM (see above). So switching from LVM to EVMS - is just a small change in the autoyast profile. All you have to do is to change the - "is_lvm_vg" element into "is_evms_vg" and the "lvm_group" element into "evms_group". + Using EVMS is quite similar to using LVM (see above). Switching from LVM to EVMS + is just a small change in the &ay; profile. Change the + "is_lvm_vg" element to "is_evms_vg" and the "lvm_group" element to "evms_group". </para> <para> - With autoyast it's not possible to mix LVM and EVMS. + With &ay; it is not possible to mix LVM and EVMS. </para> <para> - Using the LVM example from above for EVMS now looks like this: + Using the LVM example from above for EVMS, looks like this: </para> <example> <title> @@ -921,48 +924,52 @@ <section> <title>Software RAID</title> <para> - Using &autoyast;, you can create and assemble software RAID devices. The + Using &ay;, you can create and assemble software RAID devices. The supported RAID levels are the following: </para> <itemizedlist> <listitem> <para> <emphasis>RAID 0:</emphasis> This level increases your disk performance. - There is <emphasis>NO</emphasis> redundancy in this mode. If one + There is <emphasis>no</emphasis> redundancy in this mode. If one of the drives crashes, data recovery will not be possible. </para> </listitem> <listitem> <para> - <emphasis>RAID 1:</emphasis>This mode has the best redundancy. It can be - used with two or more disks. This mode maintains an exact copy of all data on all - disks. As long as at least one disk is still working, no data is lost. The partitions - used for this type of RAID should have approximately the same size. + <emphasis>RAID 1:</emphasis>This mode offers the best redundancy. It + can be used with two or more disks. An exact copy of all data is + maintained on all disks. As long as at least one disk is still + working, no data is lost. The partitions used for this type of RAID + should have approximately the same size. </para> </listitem> <listitem> <para> - <emphasis>RAID 5:</emphasis> This mode combines management of a larger number - of disks and still maintains some redundancy. This mode can be used on three disks or more. - If one disk fails, all data is still intact. If two disks fail simultaneously, - all data is lost. + <emphasis>RAID 5:</emphasis> This mode combines management of a + larger number of disks and still maintains some redundancy. This + mode can be used on three disks or more. If one disk fails, all + data is still intact. If two disks fail simultaneously, all data is + lost.<remark>emap 2011-11-05: Really all data is lost, although + there are three or more disks?</remark> </para> </listitem> <listitem> <para> - <emphasis>Multipath:</emphasis>This mode allow access to the same physical device - over multiple controller for redundancy against a fault in a controller - card. This mode can be used with at least two devices. + <emphasis>Multipath:</emphasis>This mode allows access to the same + physical device via multiple controllers for redundancy against a + fault in a controller card. This mode can be used with at least two + devices. </para> </listitem> </itemizedlist> <para> As with LVM, you need to create all <emphasis><acronym>RAID</acronym></emphasis> partitions first and assign the partitions to the <acronym>RAID</acronym> device you want to - create and additionally you need to specify whether a partition or a device should be configured in the - <acronym>RAID</acronym> or if it should configured as a <emphasis>Spare</emphasis> device. + create. Additionally you need to specify whether a partition or a device should be configured in the + <acronym>RAID</acronym> or if it should be configured as a <emphasis>Spare</emphasis> device. </para> <para> The following example shows a simple RAID1 configuration: @@ -979,8 +986,7 @@ <para> - The following has to be taken into consideration when configuring - raid: + Consider the following when configuring raid: </para> <itemizedlist> <listitem> @@ -988,12 +994,12 @@ </listitem> <listitem> <para>The property <emphasis>partition_nr</emphasis> is used to - determine the MD device number. if + determine the MD device number. If <emphasis>partition_nr</emphasis> is equal to 0, then <emphasis>/dev/md0</emphasis> is configured.</para> </listitem> <listitem> - <para>All RAID specific options are contained in the + <para>All RAID-specific options are contained in the <emphasis>raid_options</emphasis> resource.</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] r66714 - /trunk/autoinstallation/doc/xml/ReportSection.xml
by emap＠svn2.opensuse.org 05 Nov '11

05 Nov '11

Author: emap Date: Sat Nov 5 12:04:41 2011 New Revision: 66714 URL: http://svn.opensuse.org/viewcvs/yast?rev=66714&view=rev Log: edited by emap Modified: trunk/autoinstallation/doc/xml/ReportSection.xml Modified: trunk/autoinstallation/doc/xml/ReportSection.xml URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/ReportS… ============================================================================== --- trunk/autoinstallation/doc/xml/ReportSection.xml (original) +++ trunk/autoinstallation/doc/xml/ReportSection.xml Sat Nov 5 12:04:41 2011 @@ -23,23 +23,23 @@ </title> <para> - The <emphasis>report</emphasis> resource manages 3 types of pop-ups - that may appear during installation. + The <emphasis>report</emphasis> resource manages three types of popups + that may appear during installation: </para> <itemizedlist> <listitem> <para> - Messages Popups (Usually non-critical, informative messages) + message popups (usually non-critical, informative messages), </para> </listitem> <listitem> <para> - Warning Popups (If something might go wrong) + warning popups (if something might go wrong), </para> </listitem> <listitem> <para> - Error Popups (In the case of an error) + error popups (in case an error occurs). </para> </listitem> </itemizedlist> @@ -58,17 +58,17 @@ some places but should not be ignored. </para> <para> - By default, the settings in auto-installation mode is to show all messages without logging and + The default setting in auto-installation mode is to show all messages without logging and with a timeout of 10 seconds. </para> <warning> <title> - Critical system messages + Critical System Messages </title> <para> Note that <emphasis>not</emphasis> all messages during installation are controlled by the <emphasis>report</emphasis> resource. Some critical messages concerning - package installation and partitioning will still show up ignoring your + package installation and partitioning will show up ignoring your settings in the <emphasis>report</emphasis> section. Mostly those messages will have to be answered with <emphasis>Yes</emphasis> or <emphasis>No</emphasis>. </para> -- To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-commit+help(a)opensuse.org

1 0