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

[yast-commit] r66713 - /trunk/autoinstallation/doc/xml/GeneralSection.xml
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

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>  <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

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

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

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

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

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

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

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

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

[yast-commit] r66703 - /tags/stable-2_21_2/firewall/
by locilka＠svn2.opensuse.org 04 Nov '11

04 Nov '11

Author: locilka Date: Fri Nov 4 16:06:16 2011 New Revision: 66703 URL: http://svn.opensuse.org/viewcvs/yast?rev=66703&view=rev Log: Created tag stable-2_21_2 for firewall Added: tags/stable-2_21_2/firewall/ - copied from r66702, trunk/firewall/ -- 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] r66702 - in /trunk/firewall: VERSION package/yast2-firewall.changes src/subdialogs.ycp
by locilka＠svn2.opensuse.org 04 Nov '11

04 Nov '11

Author: locilka Date: Fri Nov 4 15:50:21 2011 New Revision: 66702 URL: http://svn.opensuse.org/viewcvs/yast?rev=66702&view=rev Log: - Added function keys for buttons (bnc#595564) - 2.21.2 Modified: trunk/firewall/VERSION trunk/firewall/package/yast2-firewall.changes trunk/firewall/src/subdialogs.ycp Modified: trunk/firewall/VERSION URL: http://svn.opensuse.org/viewcvs/yast/trunk/firewall/VERSION?rev=66702&r1=66… ============================================================================== --- trunk/firewall/VERSION (original) +++ trunk/firewall/VERSION Fri Nov 4 15:50:21 2011 @@ -1 +1 @@ -2.21.1 +2.21.2 Modified: trunk/firewall/package/yast2-firewall.changes URL: http://svn.opensuse.org/viewcvs/yast/trunk/firewall/package/yast2-firewall.… ============================================================================== --- trunk/firewall/package/yast2-firewall.changes (original) +++ trunk/firewall/package/yast2-firewall.changes Fri Nov 4 15:50:21 2011 @@ -1,4 +1,10 @@ ------------------------------------------------------------------- +Fri Nov 4 15:50:22 CET 2011 - locilka(a)suse.cz + +- Added function keys for buttons (bnc#595564) +- 2.21.2 + +------------------------------------------------------------------- Thu Oct 13 10:34:54 CEST 2011 - locilka(a)suse.cz - Fixed a typo in text marked for translation (bnc#722459). Modified: trunk/firewall/src/subdialogs.ycp URL: http://svn.opensuse.org/viewcvs/yast/trunk/firewall/src/subdialogs.ycp?rev=… ============================================================================== --- trunk/firewall/src/subdialogs.ycp (original) +++ trunk/firewall/src/subdialogs.ycp Fri Nov 4 15:50:21 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] r66701 - in /trunk/qt-pkg: VERSION.cmake package/yast2-qt-pkg.changes src/YQPackageSelector.cc
by tgoettlicher＠svn2.opensuse.org 04 Nov '11

04 Nov '11

Author: tgoettlicher Date: Fri Nov 4 14:32:09 2011 New Revision: 66701 URL: http://svn.opensuse.org/viewcvs/yast?rev=66701&view=rev Log: - Changed default for "Ignore recommended packages for already installed packages" (bnc #716017) - Version: 2.21.14 Modified: trunk/qt-pkg/VERSION.cmake trunk/qt-pkg/package/yast2-qt-pkg.changes trunk/qt-pkg/src/YQPackageSelector.cc Modified: trunk/qt-pkg/VERSION.cmake URL: http://svn.opensuse.org/viewcvs/yast/trunk/qt-pkg/VERSION.cmake?rev=66701&r… ============================================================================== --- trunk/qt-pkg/VERSION.cmake (original) +++ trunk/qt-pkg/VERSION.cmake Fri Nov 4 14:32:09 2011 @@ -1,3 +1,3 @@ SET(VERSION_MAJOR "2") SET(VERSION_MINOR "21") -SET(VERSION_PATCH "13") +SET(VERSION_PATCH "14") Modified: trunk/qt-pkg/package/yast2-qt-pkg.changes URL: http://svn.opensuse.org/viewcvs/yast/trunk/qt-pkg/package/yast2-qt-pkg.chan… ============================================================================== --- trunk/qt-pkg/package/yast2-qt-pkg.changes (original) +++ trunk/qt-pkg/package/yast2-qt-pkg.changes Fri Nov 4 14:32:09 2011 @@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Fri Nov 4 14:31:32 CET 2011 - tgoettlicher(a)suse.de + +- Changed default for "Ignore recommended packages for already installed + packages" (bnc #716017) +- Version: 2.21.14 + +------------------------------------------------------------------- Mon Oct 24 17:50:20 CEST 2011 - tgoettlicher(a)suse.de - Fixed bnc#725953: Package manager settings are saved but not applied on start Modified: trunk/qt-pkg/src/YQPackageSelector.cc URL: http://svn.opensuse.org/viewcvs/yast/trunk/qt-pkg/src/YQPackageSelector.cc?… ============================================================================== --- trunk/qt-pkg/src/YQPackageSelector.cc (original) +++ trunk/qt-pkg/src/YQPackageSelector.cc Fri Nov 4 14:32:09 2011 @@ -1719,8 +1719,8 @@ pkgVerifySytemModeChanged ( _verifySystemModeAction->isChecked() ); _ignoreAlreadyRecommendAction->setChecked( - updateMode() ? false : settings.value("Options/IgnoreRecommendedPackagesForAlreadyInstalledPackages", - zypp::getZYpp()->resolver()->ignoreAlreadyRecommended() ).toBool() ); + settings.value("Options/IgnoreRecommendedPackagesForAlreadyInstalledPackages", + false )); pkgIgnoreAlreadyRecommendedChanged(_ignoreAlreadyRecommendAction->isChecked()); -- 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] r66700 - /tags/branch-Code-11-SP1-2_17_17_3/wagon/
by lslezak＠svn2.opensuse.org 04 Nov '11

04 Nov '11

Author: lslezak Date: Fri Nov 4 11:09:42 2011 New Revision: 66700 URL: http://svn.opensuse.org/viewcvs/yast?rev=66700&view=rev Log: Created tag branch-Code-11-SP1-2_17_17_3 for wagon Added: tags/branch-Code-11-SP1-2_17_17_3/wagon/ (props changed) - copied from r66699, branches/SuSE-Code-11-SP1-Branch/wagon/ -- 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] r66699 - /tags/branch-Code-11-SP1-2_17_17_3/
by lslezak＠svn2.opensuse.org 04 Nov '11

04 Nov '11

Author: lslezak Date: Fri Nov 4 11:09:39 2011 New Revision: 66699 URL: http://svn.opensuse.org/viewcvs/yast?rev=66699&view=rev Log: Created tag branch-Code-11-SP1-2_17_17_3 Added: tags/branch-Code-11-SP1-2_17_17_3/ -- 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] r66698 - in /branches/SuSE-Code-11-SP1-Branch/wagon: VERSION package/yast2-wagon.changes src/config/online_migration.xml
by lslezak＠svn2.opensuse.org 04 Nov '11

04 Nov '11

Author: lslezak Date: Fri Nov 4 11:08:01 2011 New Revision: 66698 URL: http://svn.opensuse.org/viewcvs/yast?rev=66698&view=rev Log: - display "Registration Code" checkbox in the registration step (bnc#724957) - 2.17.17.3 Modified: branches/SuSE-Code-11-SP1-Branch/wagon/VERSION branches/SuSE-Code-11-SP1-Branch/wagon/package/yast2-wagon.changes branches/SuSE-Code-11-SP1-Branch/wagon/src/config/online_migration.xml Modified: branches/SuSE-Code-11-SP1-Branch/wagon/VERSION URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP1-Branch/wagon… ============================================================================== --- branches/SuSE-Code-11-SP1-Branch/wagon/VERSION (original) +++ branches/SuSE-Code-11-SP1-Branch/wagon/VERSION Fri Nov 4 11:08:01 2011 @@ -1 +1 @@ -2.17.17.2 +2.17.17.3 Modified: branches/SuSE-Code-11-SP1-Branch/wagon/package/yast2-wagon.changes URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP1-Branch/wagon… ============================================================================== --- branches/SuSE-Code-11-SP1-Branch/wagon/package/yast2-wagon.changes (original) +++ branches/SuSE-Code-11-SP1-Branch/wagon/package/yast2-wagon.changes Fri Nov 4 11:08:01 2011 @@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Thu Nov 3 15:55:33 UTC 2011 - lslezak(a)suse.cz + +- display "Registration Code" checkbox in the registration step + (bnc#724957) +- 2.17.17.3 + +------------------------------------------------------------------- Mon Aug 1 11:40:57 UTC 2011 - lslezak(a)suse.cz - display solver error in the migration propsal, do not allow Modified: branches/SuSE-Code-11-SP1-Branch/wagon/src/config/online_migration.xml URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP1-Branch/wagon… ============================================================================== --- branches/SuSE-Code-11-SP1-Branch/wagon/src/config/online_migration.xml (original) +++ branches/SuSE-Code-11-SP1-Branch/wagon/src/config/online_migration.xml Fri Nov 4 11:08:01 2011 @@ -20,6 +20,9 @@ <default_subworkflow>manual</default_subworkflow> +  + <display_register_forcereg config:type="boolean">true</display_register_forcereg> + <subworkflows config:type="list"> <!-- Simple workflow: Used when WAGON is called from applet -- 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] r66697 - /branches/SuSE-Code-11-SP1-Branch/wagon/src/clients/wagon_registration_check.ycp
by lslezak＠svn2.opensuse.org 04 Nov '11

04 Nov '11

Author: lslezak Date: Fri Nov 4 11:06:49 2011 New Revision: 66697 URL: http://svn.opensuse.org/viewcvs/yast?rev=66697&view=rev Log: fixed help text Modified: branches/SuSE-Code-11-SP1-Branch/wagon/src/clients/wagon_registration_check.ycp Modified: branches/SuSE-Code-11-SP1-Branch/wagon/src/clients/wagon_registration_check.ycp URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP1-Branch/wagon… ============================================================================== --- branches/SuSE-Code-11-SP1-Branch/wagon/src/clients/wagon_registration_check.ycp (original) +++ branches/SuSE-Code-11-SP1-Branch/wagon/src/clients/wagon_registration_check.ycp Fri Nov 4 11:06:49 2011 @@ -186,7 +186,7 @@ ); // help text - string help_text = "<p>" + _("YaST checks whether the installed products are the installed products are registered.") + string help_text = "<p>" + _("YaST checks whether the installed products are registered.") + "</p><p>" + _("Migrating unregistered or partly registered system might result in broken system.") + "</p>"; Wizard::SetContents (heading_text, contents, help_text, -- 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] r66696 - /tags/branch-Code-11-SP2-2_17_26/wagon/
by lslezak＠svn2.opensuse.org 04 Nov '11

04 Nov '11

Author: lslezak Date: Fri Nov 4 10:48:46 2011 New Revision: 66696 URL: http://svn.opensuse.org/viewcvs/yast?rev=66696&view=rev Log: Created tag branch-Code-11-SP2-2_17_26 for wagon Added: tags/branch-Code-11-SP2-2_17_26/wagon/ (props changed) - copied from r66695, branches/SuSE-Code-11-SP2-Branch/wagon/ -- 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] r66695 - in /branches/SuSE-Code-11-SP2-Branch/wagon: VERSION package/yast2-wagon.changes src/config/online_migration.xml
by lslezak＠svn2.opensuse.org 04 Nov '11

04 Nov '11

Author: lslezak Date: Fri Nov 4 10:48:11 2011 New Revision: 66695 URL: http://svn.opensuse.org/viewcvs/yast?rev=66695&view=rev Log: - display "Registration Code" checkbox in the registration step (bnc#724957) - 2.17.26 Modified: branches/SuSE-Code-11-SP2-Branch/wagon/VERSION branches/SuSE-Code-11-SP2-Branch/wagon/package/yast2-wagon.changes branches/SuSE-Code-11-SP2-Branch/wagon/src/config/online_migration.xml Modified: branches/SuSE-Code-11-SP2-Branch/wagon/VERSION URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/wagon… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/wagon/VERSION (original) +++ branches/SuSE-Code-11-SP2-Branch/wagon/VERSION Fri Nov 4 10:48:11 2011 @@ -1 +1 @@ -2.17.25 +2.17.26 Modified: branches/SuSE-Code-11-SP2-Branch/wagon/package/yast2-wagon.changes URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/wagon… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/wagon/package/yast2-wagon.changes (original) +++ branches/SuSE-Code-11-SP2-Branch/wagon/package/yast2-wagon.changes Fri Nov 4 10:48:11 2011 @@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Thu Nov 3 15:55:33 UTC 2011 - lslezak(a)suse.cz + +- display "Registration Code" checkbox in the registration step + (bnc#724957) +- 2.17.26 + +------------------------------------------------------------------- Thu Sep 1 12:11:50 UTC 2011 - lslezak(a)suse.cz - fixed a typo (bnc#714957) Modified: branches/SuSE-Code-11-SP2-Branch/wagon/src/config/online_migration.xml URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/wagon… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/wagon/src/config/online_migration.xml (original) +++ branches/SuSE-Code-11-SP2-Branch/wagon/src/config/online_migration.xml Fri Nov 4 10:48:11 2011 @@ -20,6 +20,9 @@ <default_subworkflow>manual</default_subworkflow> +  + <display_register_forcereg config:type="boolean">true</display_register_forcereg> + <subworkflows config:type="list"> <!-- Simple workflow: Used when WAGON is called from applet -- 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] r66694 - /tags/stable-2_21_13/storage/
by fehr＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: fehr Date: Thu Nov 3 17:42:39 2011 New Revision: 66694 URL: http://svn.opensuse.org/viewcvs/yast?rev=66694&view=rev Log: Created tag stable-2_21_13 for storage Added: tags/stable-2_21_13/storage/ (props changed) - copied from r66693, trunk/storage/ -- 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] r66693 - in /trunk/storage: VERSION package/yast2-storage.changes
by fehr＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: fehr Date: Thu Nov 3 17:42:32 2011 New Revision: 66693 URL: http://svn.opensuse.org/viewcvs/yast?rev=66693&view=rev Log: version 2.21.13 Modified: trunk/storage/VERSION trunk/storage/package/yast2-storage.changes Modified: trunk/storage/VERSION URL: http://svn.opensuse.org/viewcvs/yast/trunk/storage/VERSION?rev=66693&r1=666… ============================================================================== --- trunk/storage/VERSION (original) +++ trunk/storage/VERSION Thu Nov 3 17:42:32 2011 @@ -1 +1 @@ -2.21.12 +2.21.13 Modified: trunk/storage/package/yast2-storage.changes URL: http://svn.opensuse.org/viewcvs/yast/trunk/storage/package/yast2-storage.ch… ============================================================================== --- trunk/storage/package/yast2-storage.changes (original) +++ trunk/storage/package/yast2-storage.changes Thu Nov 3 17:42:32 2011 @@ -1,6 +1,7 @@ ------------------------------------------------------------------- Wed Nov 2 13:04:19 CET 2011 - fehr(a)suse.de +- version 2.21.13 - add nofail for fstab entries on USB, ISCSI and FCOE disks (bnc#726926) -- 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] r66692 - /tags/stable-2_21_9/iscsi-client/
by fehr＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: fehr Date: Thu Nov 3 17:32:48 2011 New Revision: 66692 URL: http://svn.opensuse.org/viewcvs/yast?rev=66692&view=rev Log: Created tag stable-2_21_9 for iscsi-client Added: tags/stable-2_21_9/iscsi-client/ - copied from r66691, trunk/iscsi-client/ -- 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] r66691 - in /trunk/iscsi-client: VERSION package/yast2-iscsi-client.changes src/IscsiClientLib.ycp src/widgets.ycp
by fehr＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: fehr Date: Thu Nov 3 17:32:05 2011 New Revision: 66691 URL: http://svn.opensuse.org/viewcvs/yast?rev=66691&view=rev Log: +- 2.21.9 +- call discovery with "-t fw" if "-t st" does not provide any targets (bnc#725833) Modified: trunk/iscsi-client/VERSION trunk/iscsi-client/package/yast2-iscsi-client.changes trunk/iscsi-client/src/IscsiClientLib.ycp trunk/iscsi-client/src/widgets.ycp Modified: trunk/iscsi-client/VERSION URL: http://svn.opensuse.org/viewcvs/yast/trunk/iscsi-client/VERSION?rev=66691&r… ============================================================================== --- trunk/iscsi-client/VERSION (original) +++ trunk/iscsi-client/VERSION Thu Nov 3 17:32:05 2011 @@ -1 +1 @@ -2.21.8 +2.21.9 Modified: trunk/iscsi-client/package/yast2-iscsi-client.changes URL: http://svn.opensuse.org/viewcvs/yast/trunk/iscsi-client/package/yast2-iscsi… ============================================================================== --- trunk/iscsi-client/package/yast2-iscsi-client.changes (original) +++ trunk/iscsi-client/package/yast2-iscsi-client.changes Thu Nov 3 17:32:05 2011 @@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Thu Nov 3 13:06:10 CET 2011 - fehr(a)suse.de + +- 2.21.9 +- call discovery with "-t fw" if "-t st" does not provide any + targets (bnc#725833) + +------------------------------------------------------------------- Thu Oct 27 11:41:58 CEST 2011 - fehr(a)suse.de - 2.21.8 Modified: trunk/iscsi-client/src/IscsiClientLib.ycp URL: http://svn.opensuse.org/viewcvs/yast/trunk/iscsi-client/src/IscsiClientLib.… ============================================================================== --- trunk/iscsi-client/src/IscsiClientLib.ycp (original) +++ trunk/iscsi-client/src/IscsiClientLib.ycp Thu Nov 3 17:32:05 2011 @@ -856,9 +856,9 @@ }); } -global string GetDiscoveryCmd( string ip, string port) +global string GetDiscoveryCmd( string ip, string port, boolean fw) { - y2milestone( "GetDiscoveryCmd ip:%1 port:%2", ip, port); + y2milestone( "GetDiscoveryCmd ip:%1 port:%2 fw:%3", ip, port, fw); string command = "-m discovery -P 1"; if( useISNS() ) command = command + " -t isns"; @@ -868,7 +868,11 @@ y2milestone( "ifs=%1", ifs ); ifs = maplist( string s, ifs, ``("-I "+s)); y2milestone( "ifs=%1", ifs ); - command = command + sformat( " -t st %3 -p %1:%2", ip, port, mergestring(ifs," ")); + string tgt = "st"; + if( fw ) + tgt = "fw"; + command = command + sformat( " -t %4 %3 -p %1:%2", ip, port, + mergestring(ifs," "), tgt); } command = GetAdmCmd(command); y2milestone( "GetDiscoveryCmd %1", command ); Modified: trunk/iscsi-client/src/widgets.ycp URL: http://svn.opensuse.org/viewcvs/yast/trunk/iscsi-client/src/widgets.ycp?rev… ============================================================================== --- trunk/iscsi-client/src/widgets.ycp (original) +++ trunk/iscsi-client/src/widgets.ycp Thu Nov 3 17:32:05 2011 @@ -472,10 +472,16 @@ //y2internal("auth: %1/%2, %3/%4", user_in, pass_in, user_out, pass_out); bg_finish=false; // ` with authentication - string command = IscsiClientLib::GetDiscoveryCmd(ip,port); + string command = IscsiClientLib::GetDiscoveryCmd(ip,port,false); list<string>trg_list = runInBg( command ); - IscsiClientLib::targets = IscsiClientLib::ScanDiscovered( trg_list ); while(!bg_finish){}; + if( size(trg_list)==0 ) + { + command = IscsiClientLib::GetDiscoveryCmd(ip,port,true); + trg_list = runInBg( command ); + while(!bg_finish){}; + } + IscsiClientLib::targets = IscsiClientLib::ScanDiscovered( trg_list ); // restore old config IscsiClientLib::oldConfig(); -- 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] r66690 - /trunk/mail/agents/setup_dkim_verifying.pl
by varkoly＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: varkoly Date: Thu Nov 3 17:20:25 2011 New Revision: 66690 URL: http://svn.opensuse.org/viewcvs/yast?rev=66690&view=rev Log: Add missed file Added: trunk/mail/agents/setup_dkim_verifying.pl (with props) Added: trunk/mail/agents/setup_dkim_verifying.pl URL: http://svn.opensuse.org/viewcvs/yast/trunk/mail/agents/setup_dkim_verifying… ============================================================================== --- trunk/mail/agents/setup_dkim_verifying.pl (added) +++ trunk/mail/agents/setup_dkim_verifying.pl Thu Nov 3 17:20:25 2011 @@ -0,0 +1,190 @@ +#!/usr/bin/perl + +BEGIN { push @INC, "/usr/lib/YaST2/servers_non_y2"; } + +use strict; +use MasterCFParser; +my $DOMAIN=`postconf -h mydomain`; +chomp $DOMAIN; + +if( ! "$DOMAIN" ) { + print "Bad postfix configuration. mydomain can not be detected"; + exit 1; +} + +#Generate the key +if( ! -e "/var/db/dkim/$DOMAIN.pem" ){ + print "Creating /var/db/dkim/$DOMAIN.pem\n"; + system( "mkdir -p /var/db/dkim/; amavisd genrsa /var/db/dkim/$DOMAIN.pem;"); +} + +#Introduce key into /etc/amavisd.conf +my $amavisd = ""; +my $enable_dkim_signing = 0; +open IN, "</etc/amavisd.conf"; +while(<IN>) +{ + if( /^\$inet_socket_port/ ) + { + $amavisd .= '$inet_socket_port = [10024,10026];'."\n"; + next; + } + if( /^\$enable_dkim_signing/ ) + { + $amavisd .= '$enable_dkim_signing = 1;'."\n"; + $enable_dkim_signing = 1; + next; + } + if( $enable_dkim_signing ) + { + my $dkim = "dkim_key('$DOMAIN', 'default', '/var/db/dkim/$DOMAIN.pem');"; + if( ! /$dkim/ ) + { + $amavisd .= "$dkim\n$_"; + } + $enable_dkim_signing = 0; + next; + } + $amavisd .= $_; +} +close IN; +system("cp /etc/amavisd.conf /etc/amavisd.conf.backup"); +open OUT, ">/etc/amavisd.conf"; +print OUT $amavisd; +close OUT; + +#Now we adapt master.cf +my $msc = new MasterCFParser(); +$msc->readMasterCF(); + +if( ! $msc->serviceExists( { service => 'submission' , command => 'smtpd' } )) +{ + if( $msc->addService( { 'service' => 'submission', + 'type' => 'inet', + 'private' => 'n', + 'unpriv' => '-', + 'chroot' => 'n', + 'wakeup' => '-', + 'maxproc' => '-', + 'command' => 'smtpd', + 'options' => { 'content_filte' => 'amavis:[127.0.0.1]:10026', + 'smtpd_recipient_restrictions' => 'permit_sasl_authenticated,permit_mynetworks,reject' } + }) ) + { + print "ERROR in addService()\n"; + } +} +else +{ + if( $msc->modifyService( { 'service' => 'submission', + 'type' => 'inet', + 'private' => 'n', + 'unpriv' => '-', + 'chroot' => 'n', + 'wakeup' => '-', + 'maxproc' => '-', + 'command' => 'smtpd', + 'options' => { 'content_filte' => 'amavis:[127.0.0.1]:10026', + 'smtpd_recipient_restrictions' => 'permit_sasl_authenticated,permit_mynetworks,reject' } + }) ) + { + print "ERROR in modifyService()\n"; + } +} + +$msc->writeMasterCF(); +#!/usr/bin/perl + +BEGIN { push @INC, "/usr/lib/YaST2/servers_non_y2"; } + +use strict; +use MasterCFParser; +my $DOMAIN=`postconf -h mydomain`; +chomp $DOMAIN; + +if( ! "$DOMAIN" ) { + print "Bad postfix configuration. mydomain can not be detected"; + exit 1; +} + +#Generate the key +if( ! -e "/var/db/dkim/$DOMAIN.pem" ){ + print "Creating /var/db/dkim/$DOMAIN.pem\n"; + system( "mkdir -p /var/db/dkim/; amavisd genrsa /var/db/dkim/$DOMAIN.pem"); +} + +#Introduce key into /etc/amavisd.conf +my $amavisd = ""; +my $enable_dkim_signing = 0; +open IN, "</etc/amavisd.conf"; +while(<IN>) +{ + if( /^\$inet_socket_port/ ) + { + $amavisd .= '$inet_socket_port = [10024,10026];'."\n"; + next; + } + if( /^\$enable_dkim_signing/ ) + { + $amavisd .= '$enable_dkim_signing = 1;'."\n"; + $enable_dkim_signing = 1; + next; + } + if( $enable_dkim_signing ) + { + my $dkim = "dkim_key('$DOMAIN', 'default', '/var/db/dkim/$DOMAIN.pem');"; + if( ! /dkim_key\('$DOMAIN', 'default'/ ) + { + $amavisd .= "$dkim\n$_"; + next; + } + $enable_dkim_signing = 0; + } + $amavisd .= $_; +} +close IN; +system("cp /etc/amavisd.conf /etc/amavisd.conf.backup"); +open OUT, ">/etc/amavisd.conf"; +print OUT $amavisd; +close OUT; + +#Now we adapt master.cf +my $msc = new MasterCFParser(); +$msc->readMasterCF(); + +if( ! $msc->serviceExists( { service => 'submission' , command => 'smtpd' } )) +{ + if( $msc->addService( { 'service' => 'submission', + 'type' => 'inet', + 'private' => 'n', + 'unpriv' => '-', + 'chroot' => 'n', + 'wakeup' => '-', + 'maxproc' => '-', + 'command' => 'smtpd', + 'options' => { 'content_filte' => 'amavis:[127.0.0.1]:10026', + 'smtpd_recipient_restrictions' => 'permit_sasl_authenticated,permit_mynetworks,reject' } + }) ) + { + print "ERROR in addService()\n"; + } +} +else +{ + if( $msc->modifyService( { 'service' => 'submission', + 'type' => 'inet', + 'private' => 'n', + 'unpriv' => '-', + 'chroot' => 'n', + 'wakeup' => '-', + 'maxproc' => '-', + 'command' => 'smtpd', + 'options' => { 'content_filte' => 'amavis:[127.0.0.1]:10026', + 'smtpd_recipient_restrictions' => 'permit_sasl_authenticated,permit_mynetworks,reject' } + }) ) + { + print "ERROR in modifyService()\n"; + } +} + +$msc->wramavisiteMasterCF(); -- 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] r66689 - /tags/branch-Code-11-SP2-2_17_120/storage/
by fehr＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: fehr Date: Thu Nov 3 16:40:14 2011 New Revision: 66689 URL: http://svn.opensuse.org/viewcvs/yast?rev=66689&view=rev Log: Created tag branch-Code-11-SP2-2_17_120 for storage Added: tags/branch-Code-11-SP2-2_17_120/storage/ (props changed) - copied from r66688, branches/SuSE-Code-11-SP2-Branch/storage/ -- 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] r66688 - /tags/branch-Code-11-SP2-2_17_120/
by fehr＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: fehr Date: Thu Nov 3 16:40:13 2011 New Revision: 66688 URL: http://svn.opensuse.org/viewcvs/yast?rev=66688&view=rev Log: Created tag branch-Code-11-SP2-2_17_120 Added: tags/branch-Code-11-SP2-2_17_120/ -- 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] r66687 - in /branches/SuSE-Code-11-SP2-Branch/storage: VERSION package/yast2-storage.changes
by fehr＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: fehr Date: Thu Nov 3 16:32:41 2011 New Revision: 66687 URL: http://svn.opensuse.org/viewcvs/yast?rev=66687&view=rev Log: version 2.17.120 Modified: branches/SuSE-Code-11-SP2-Branch/storage/VERSION branches/SuSE-Code-11-SP2-Branch/storage/package/yast2-storage.changes Modified: branches/SuSE-Code-11-SP2-Branch/storage/VERSION URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/stora… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/storage/VERSION (original) +++ branches/SuSE-Code-11-SP2-Branch/storage/VERSION Thu Nov 3 16:32:41 2011 @@ -1 +1 @@ -2.17.119 +2.17.120 Modified: branches/SuSE-Code-11-SP2-Branch/storage/package/yast2-storage.changes URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/stora… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/storage/package/yast2-storage.changes (original) +++ branches/SuSE-Code-11-SP2-Branch/storage/package/yast2-storage.changes Thu Nov 3 16:32:41 2011 @@ -1,6 +1,7 @@ ------------------------------------------------------------------- Thu Nov 3 10:55:36 CET 2011 - fehr(a)suse.de +- version 2.17.120 - fix fstab handling when mount-by-uuid is reformatted (bnc#728000) - add local static struct to getContVolInfo to prevent strings from being freed while perl interface might still access them -- 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] r66686 - /tags/stable-2_21_5/nis-client/
by locilka＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: locilka Date: Thu Nov 3 14:31:17 2011 New Revision: 66686 URL: http://svn.opensuse.org/viewcvs/yast?rev=66686&view=rev Log: Created tag stable-2_21_5 for nis-client Added: tags/stable-2_21_5/nis-client/ - copied from r66685, trunk/nis-client/ -- 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] r66685 - in /trunk/nis-client: VERSION package/yast2-nis-client.changes testsuite/tests/readwrite.out
by locilka＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: locilka Date: Thu Nov 3 14:30:57 2011 New Revision: 66685 URL: http://svn.opensuse.org/viewcvs/yast?rev=66685&view=rev Log: - Fixed testsuite - 2.21.5 Modified: trunk/nis-client/VERSION trunk/nis-client/package/yast2-nis-client.changes trunk/nis-client/testsuite/tests/readwrite.out Modified: trunk/nis-client/VERSION URL: http://svn.opensuse.org/viewcvs/yast/trunk/nis-client/VERSION?rev=66685&r1=… ============================================================================== --- trunk/nis-client/VERSION (original) +++ trunk/nis-client/VERSION Thu Nov 3 14:30:57 2011 @@ -1 +1 @@ -2.21.4 +2.21.5 Modified: trunk/nis-client/package/yast2-nis-client.changes URL: http://svn.opensuse.org/viewcvs/yast/trunk/nis-client/package/yast2-nis-cli… ============================================================================== --- trunk/nis-client/package/yast2-nis-client.changes (original) +++ trunk/nis-client/package/yast2-nis-client.changes Thu Nov 3 14:30:57 2011 @@ -1,4 +1,10 @@ ------------------------------------------------------------------- +Thu Nov 3 14:30:58 CET 2011 - locilka(a)suse.cz + +- Fixed testsuite +- 2.21.5 + +------------------------------------------------------------------- Mon Oct 24 11:38:22 CEST 2011 - jsuchome(a)suse.cz - testsuite adapted to last change of yast2-pam Modified: trunk/nis-client/testsuite/tests/readwrite.out URL: http://svn.opensuse.org/viewcvs/yast/trunk/nis-client/testsuite/tests/readw… ============================================================================== --- trunk/nis-client/testsuite/tests/readwrite.out (original) +++ trunk/nis-client/testsuite/tests/readwrite.out Thu Nov 3 14:30:57 2011 @@ -17,7 +17,6 @@ Read .sysconfig.displaymanager.DISPLAYMANAGER_PASSWORD_LESS_LOGIN "no" Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_init | /usr/bin/grep -q '[0-6]:on'" 0 Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_setup | /usr/bin/grep -q '[0-6]:on'" 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Read .init.scripts.runlevel "rpcbind" $["autofs":$["start":["3", "5"], "stop":["3", "5"]], "rpcbind":$["start":["3", "5"], "stop":["3", "5"]], "ypbind":$["start":["3", "5"], "stop":["3", "5"]]] Read .init.scripts.comment "rpcbind" $["autofs":$[], "rpcbind":$[], "ypbind":$[]] @@ -69,7 +68,6 @@ Execute .target.bash "/sbin/service rpcbind status" $["TERM":"raw"] 0 Execute .target.bash_output "/etc/init.d/ypbind start" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":"mydomain\n"] Execute .target.bash "/usr/bin/ypwhich >/dev/null" 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump auto policy Execute .target.bash "/sbin/chkconfig -l ypbind | /usr/bin/grep -q '[0-6]:on'" 0 @@ -142,5 +140,4 @@ Execute .target.bash "/usr/bin/ypwhich >/dev/null" 0 Execute .target.bash_output "/sbin/service autofs stop" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":"mydomain\n"] Execute .target.bash_output "/sbin/service autofs start" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":"mydomain\n"] -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true -- 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] r66684 - /tags/branch-Code-11-SP2-2_17_95/installation/
by aschnell＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: aschnell Date: Thu Nov 3 14:24:15 2011 New Revision: 66684 URL: http://svn.opensuse.org/viewcvs/yast?rev=66684&view=rev Log: Created tag branch-Code-11-SP2-2_17_95 for installation Added: tags/branch-Code-11-SP2-2_17_95/installation/ (props changed) - copied from r66683, branches/SuSE-Code-11-SP2-Branch/installation/ -- 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] r66683 - /tags/stable-2_21_2/tftp-server/
by locilka＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: locilka Date: Thu Nov 3 14:09:08 2011 New Revision: 66683 URL: http://svn.opensuse.org/viewcvs/yast?rev=66683&view=rev Log: Created tag stable-2_21_2 for tftp-server Added: tags/stable-2_21_2/tftp-server/ - copied from r66682, trunk/tftp-server/ -- 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] r66682 - in /trunk/tftp-server: VERSION package/yast2-tftp-server.changes testsuite/tests/readwrite.out
by locilka＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: locilka Date: Thu Nov 3 14:08:47 2011 New Revision: 66682 URL: http://svn.opensuse.org/viewcvs/yast?rev=66682&view=rev Log: - Fixed testsuite - 2.21.2 Modified: trunk/tftp-server/VERSION trunk/tftp-server/package/yast2-tftp-server.changes trunk/tftp-server/testsuite/tests/readwrite.out Modified: trunk/tftp-server/VERSION URL: http://svn.opensuse.org/viewcvs/yast/trunk/tftp-server/VERSION?rev=66682&r1… ============================================================================== --- trunk/tftp-server/VERSION (original) +++ trunk/tftp-server/VERSION Thu Nov 3 14:08:47 2011 @@ -1 +1 @@ -2.21.1 +2.21.2 Modified: trunk/tftp-server/package/yast2-tftp-server.changes URL: http://svn.opensuse.org/viewcvs/yast/trunk/tftp-server/package/yast2-tftp-s… ============================================================================== --- trunk/tftp-server/package/yast2-tftp-server.changes (original) +++ trunk/tftp-server/package/yast2-tftp-server.changes Thu Nov 3 14:08:47 2011 @@ -1,4 +1,10 @@ ------------------------------------------------------------------- +Thu Nov 3 14:08:48 CET 2011 - locilka(a)suse.cz + +- Fixed testsuite +- 2.21.2 + +------------------------------------------------------------------- Mon Sep 26 15:06:35 CEST 2011 - visnov(a)suse.cz - set dialog title Modified: trunk/tftp-server/testsuite/tests/readwrite.out URL: http://svn.opensuse.org/viewcvs/yast/trunk/tftp-server/testsuite/tests/read… ============================================================================== --- trunk/tftp-server/testsuite/tests/readwrite.out (original) +++ trunk/tftp-server/testsuite/tests/readwrite.out Thu Nov 3 14:08:47 2011 @@ -5,7 +5,6 @@ Read .etc.xinetd_d.tftp.value.tftp.server_args "-s -v /srv/boot" Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_init | /usr/bin/grep -q '[0-6]:on'" 0 Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_setup | /usr/bin/grep -q '[0-6]:on'" 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Write .etc.xinetd_d.tftp.value.tftp."{" "" true Write .etc.xinetd_d.tftp.value_type.tftp."{" 1 true @@ -22,5 +21,4 @@ Read .init.scripts.comment "xinetd" $["inetd":$[], "network":$[], "networkmanager":$[], "xinetd":$[]] Execute .target.bash "/usr/bin/killall in.tftpd" 0 Execute .target.bash_output "/sbin/service xinetd restart" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":"p3316\ncxinetd\n"] -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true -- 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] r66681 - /tags/stable-2_21_2/nfs-server/
by locilka＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: locilka Date: Thu Nov 3 14:04:58 2011 New Revision: 66681 URL: http://svn.opensuse.org/viewcvs/yast?rev=66681&view=rev Log: Created tag stable-2_21_2 for nfs-server Added: tags/stable-2_21_2/nfs-server/ - copied from r66680, trunk/nfs-server/ -- 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] r66680 - in /branches/SuSE-Code-11-SP2-Branch/storage: libstorage/src/Volume.cc libstorage/src/Volume.h package/yast2-storage.changes
by fehr＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: fehr Date: Thu Nov 3 13:54:09 2011 New Revision: 66680 URL: http://svn.opensuse.org/viewcvs/yast?rev=66680&view=rev Log: - fix fstab handling when mount-by-uuid is reformatted (bnc#728000) Modified: branches/SuSE-Code-11-SP2-Branch/storage/libstorage/src/Volume.cc branches/SuSE-Code-11-SP2-Branch/storage/libstorage/src/Volume.h branches/SuSE-Code-11-SP2-Branch/storage/package/yast2-storage.changes Modified: branches/SuSE-Code-11-SP2-Branch/storage/libstorage/src/Volume.cc URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/stora… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/storage/libstorage/src/Volume.cc (original) +++ branches/SuSE-Code-11-SP2-Branch/storage/libstorage/src/Volume.cc Thu Nov 3 13:54:09 2011 @@ -542,9 +542,7 @@ if (!entry.fs_uuid.empty()) { - uuid = entry.fs_uuid; - alt_names.remove_if(string_contains("/by-uuid/")); - alt_names.push_back("/dev/disk/by-uuid/" + uuid); + updateUuid(entry.fs_uuid); } if (!entry.fs_label.empty()) @@ -916,6 +914,13 @@ return( ret ); } +void Volume::updateUuid( const string& new_uuid ) + { + uuid = new_uuid; + alt_names.remove_if(string_contains("/by-uuid/")); + alt_names.push_back("/dev/disk/by-uuid/" + uuid); + } + int Volume::doFormat() { static int fcount=1000; @@ -1083,6 +1088,10 @@ if( ret==0 ) { triggerUdevUpdate(); + Blkid blkid(mountDevice()); + Blkid::Entry entry; + if( findBlkid( blkid, entry ) && entry.is_fs && !entry.fs_uuid.empty()) + updateUuid( entry.fs_uuid ); } if( ret==0 && !orig_mp.empty() ) { @@ -2734,6 +2743,7 @@ else if( l ) ret = l->loopFile(); } + y2mil( "dev:" << dev << " ret:" << ret ); return( ret ); } Modified: branches/SuSE-Code-11-SP2-Branch/storage/libstorage/src/Volume.h URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/stora… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/storage/libstorage/src/Volume.h (original) +++ branches/SuSE-Code-11-SP2-Branch/storage/libstorage/src/Volume.h Thu Nov 3 13:54:09 2011 @@ -217,6 +217,7 @@ void getLoopData( SystemCmd& loopData ); void getMountData(const ProcMounts& mounts, bool swap_only = false); void getFstabData( EtcFstab& fstabData ); + void updateUuid( const string& new_uuid ); void replaceAltName( const string& prefix, const string& newn ); string getMountByString() const; string getFstabDevice() const; Modified: branches/SuSE-Code-11-SP2-Branch/storage/package/yast2-storage.changes URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/stora… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/storage/package/yast2-storage.changes (original) +++ branches/SuSE-Code-11-SP2-Branch/storage/package/yast2-storage.changes Thu Nov 3 13:54:09 2011 @@ -1,6 +1,7 @@ ------------------------------------------------------------------- Thu Nov 3 10:55:36 CET 2011 - fehr(a)suse.de +- fix fstab handling when mount-by-uuid is reformatted (bnc#728000) - add local static struct to getContVolInfo to prevent strings from being freed while perl interface might still access them -- 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] r66679 - in /trunk/nfs-server: VERSION package/yast2-nfs-server.changes testsuite/tests/readwrite-unfsd.out testsuite/tests/readwrite.out testsuite/tests/readwrite2.out
by locilka＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: locilka Date: Thu Nov 3 13:48:25 2011 New Revision: 66679 URL: http://svn.opensuse.org/viewcvs/yast?rev=66679&view=rev Log: - Fixed testsuites - 2.21.2 Modified: trunk/nfs-server/VERSION trunk/nfs-server/package/yast2-nfs-server.changes trunk/nfs-server/testsuite/tests/readwrite-unfsd.out trunk/nfs-server/testsuite/tests/readwrite.out trunk/nfs-server/testsuite/tests/readwrite2.out Modified: trunk/nfs-server/VERSION URL: http://svn.opensuse.org/viewcvs/yast/trunk/nfs-server/VERSION?rev=66679&r1=… ============================================================================== --- trunk/nfs-server/VERSION (original) +++ trunk/nfs-server/VERSION Thu Nov 3 13:48:25 2011 @@ -1 +1 @@ -2.21.1 +2.21.2 Modified: trunk/nfs-server/package/yast2-nfs-server.changes URL: http://svn.opensuse.org/viewcvs/yast/trunk/nfs-server/package/yast2-nfs-ser… ============================================================================== --- trunk/nfs-server/package/yast2-nfs-server.changes (original) +++ trunk/nfs-server/package/yast2-nfs-server.changes Thu Nov 3 13:48:25 2011 @@ -1,4 +1,10 @@ ------------------------------------------------------------------- +Thu Nov 3 13:48:33 CET 2011 - locilka(a)suse.cz + +- Fixed testsuites +- 2.21.2 + +------------------------------------------------------------------- Wed Sep 21 11:42:35 CEST 2011 - visnov(a)suse.cz - set dialog title Modified: trunk/nfs-server/testsuite/tests/readwrite-unfsd.out URL: http://svn.opensuse.org/viewcvs/yast/trunk/nfs-server/testsuite/tests/readw… ============================================================================== --- trunk/nfs-server/testsuite/tests/readwrite-unfsd.out (original) +++ trunk/nfs-server/testsuite/tests/readwrite-unfsd.out Thu Nov 3 13:48:25 2011 @@ -6,7 +6,6 @@ Read .sysconfig.nfs.NFS_SECURITY_GSS nil Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_init | /usr/bin/grep -q '[0-6]:on'" 0 Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_setup | /usr/bin/grep -q '[0-6]:on'" 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Write OK Read .target.dir "/projects" nil @@ -34,7 +33,6 @@ Execute .target.bash_output "/sbin/service nfslock restart" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Execute .target.bash_output "/sbin/service nfsserver start" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Execute .target.bash "/sbin/service nfsserver status" $["TERM":"raw"] 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Write KO Read .target.dir "/projects" nil Modified: trunk/nfs-server/testsuite/tests/readwrite.out URL: http://svn.opensuse.org/viewcvs/yast/trunk/nfs-server/testsuite/tests/readw… ============================================================================== --- trunk/nfs-server/testsuite/tests/readwrite.out (original) +++ trunk/nfs-server/testsuite/tests/readwrite.out Thu Nov 3 13:48:25 2011 @@ -6,7 +6,6 @@ Read .sysconfig.nfs.NFS_SECURITY_GSS nil Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_init | /usr/bin/grep -q '[0-6]:on'" 0 Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_setup | /usr/bin/grep -q '[0-6]:on'" 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Write OK Read .target.dir "/projects" nil @@ -33,7 +32,6 @@ Execute .target.bash_output "/sbin/service nfslock restart" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Execute .target.bash_output "/sbin/service nfsserver start" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Execute .target.bash "/sbin/service nfsserver status" $["TERM":"raw"] 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Write KO Read .target.dir "/projects" nil Modified: trunk/nfs-server/testsuite/tests/readwrite2.out URL: http://svn.opensuse.org/viewcvs/yast/trunk/nfs-server/testsuite/tests/readw… ============================================================================== --- trunk/nfs-server/testsuite/tests/readwrite2.out (original) +++ trunk/nfs-server/testsuite/tests/readwrite2.out Thu Nov 3 13:48:25 2011 @@ -8,7 +8,6 @@ Read .sysconfig.nfs.NFS_SECURITY_GSS nil Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_init | /usr/bin/grep -q '[0-6]:on'" 0 Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_setup | /usr/bin/grep -q '[0-6]:on'" 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Dump Write - services will be stopped @@ -30,7 +29,6 @@ Execute .target.bash_output "/sbin/service nfslock stop" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Read .init.scripts.runlevel "nfslock" $["nfsserver":$["start":["3", "5"], "stop":["3", "5"]], "rpcbind":$["start":["3", "5"], "stop":["3", "5"]]] Read .init.scripts.comment "nfslock" $["nfsserver":$[], "rpcbind":$[]] -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Dump Read - services are running @@ -69,7 +67,6 @@ Execute .target.bash_output "/sbin/service nfslock restart" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Execute .target.bash_output "/sbin/service nfsserver start" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Execute .target.bash "/sbin/service nfsserver status" $["TERM":"raw"] 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Dump Read - services are stopped @@ -99,7 +96,6 @@ Execute .target.bash_output "/sbin/service nfslock stop" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Read .init.scripts.runlevel "nfslock" $["nfsserver":$["start":[], "stop":[]], "rpcbind":$["start":[], "stop":[]]] Read .init.scripts.comment "nfslock" $["nfsserver":$[], "rpcbind":$[]] -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Dump Read - services are stopped @@ -140,5 +136,4 @@ Execute .target.bash_output "/sbin/service nfslock restart" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Execute .target.bash_output "/sbin/service nfsserver start" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Execute .target.bash "/sbin/service nfsserver status" $["TERM":"raw"] 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true -- 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] r66678 - /tags/stable-2_21_2/nfs-client/
by locilka＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: locilka Date: Thu Nov 3 13:41:45 2011 New Revision: 66678 URL: http://svn.opensuse.org/viewcvs/yast?rev=66678&view=rev Log: Created tag stable-2_21_2 for nfs-client Added: tags/stable-2_21_2/nfs-client/ (props changed) - copied from r66677, trunk/nfs-client/ -- 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] r66677 - in /trunk/nfs-client: VERSION package/yast2-nfs-client.changes testsuite/tests/readwrite.out testsuite/tests/readwrite2.out
by locilka＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: locilka Date: Thu Nov 3 13:41:19 2011 New Revision: 66677 URL: http://svn.opensuse.org/viewcvs/yast?rev=66677&view=rev Log: - Fixed testsuites - 2.21.2 Modified: trunk/nfs-client/VERSION trunk/nfs-client/package/yast2-nfs-client.changes trunk/nfs-client/testsuite/tests/readwrite.out trunk/nfs-client/testsuite/tests/readwrite2.out Modified: trunk/nfs-client/VERSION URL: http://svn.opensuse.org/viewcvs/yast/trunk/nfs-client/VERSION?rev=66677&r1=… ============================================================================== --- trunk/nfs-client/VERSION (original) +++ trunk/nfs-client/VERSION Thu Nov 3 13:41:19 2011 @@ -1 +1 @@ -2.21.1 +2.21.2 Modified: trunk/nfs-client/package/yast2-nfs-client.changes URL: http://svn.opensuse.org/viewcvs/yast/trunk/nfs-client/package/yast2-nfs-cli… ============================================================================== --- trunk/nfs-client/package/yast2-nfs-client.changes (original) +++ trunk/nfs-client/package/yast2-nfs-client.changes Thu Nov 3 13:41:19 2011 @@ -1,4 +1,10 @@ ------------------------------------------------------------------- +Thu Nov 3 13:40:49 CET 2011 - locilka(a)suse.cz + +- Fixed testsuites +- 2.21.2 + +------------------------------------------------------------------- Wed Sep 21 10:54:32 CEST 2011 - visnov(a)suse.cz - set dialog title Modified: trunk/nfs-client/testsuite/tests/readwrite.out URL: http://svn.opensuse.org/viewcvs/yast/trunk/nfs-client/testsuite/tests/readw… ============================================================================== --- trunk/nfs-client/testsuite/tests/readwrite.out (original) +++ trunk/nfs-client/testsuite/tests/readwrite.out Thu Nov 3 13:41:19 2011 @@ -4,7 +4,6 @@ Read .etc.idmapd_conf "Domain" "localhost" Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_init | /usr/bin/grep -q '[0-6]:on'" 0 Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_setup | /usr/bin/grep -q '[0-6]:on'" 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Write OK Read .etc.fstab [$["file":"/", "freq":1, "mntops":"defaults", "passno":2, "spec":"/dev/hda6", "vfstype":"reiserfs"], $["file":"/home", "freq":0, "mntops":"defaults", "passno":0, "spec":"foo.bar.com:/home", "vfstype":"nfs"], $["file":"/var/spool/mail", "freq":0, "mntops":"defaults", "passno":0, "spec":"foo.bar.com:/var/spool/mail", "vfstype":"nfs"], $["file":"/a\\040space", "freq":1, "mntops":"defaults", "passno":3, "spec":"/dev/hda7", "vfstype":"reiserfs"], $["file":"/b\\040space", "freq":0, "mntops":"defaults", "passno":0, "spec":"foo.bar.com:/space\\040dir", "vfstype":"nfs"]] @@ -26,7 +25,6 @@ Execute .target.bash "/sbin/service portmap status" $["TERM":"raw"] 0 Execute .target.bash_output "/sbin/service nfs start" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Execute .target.bash "/sbin/service nfs status" $["TERM":"raw"] 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Write KO Read .etc.fstab [$["file":"/", "freq":1, "mntops":"defaults", "passno":2, "spec":"/dev/hda6", "vfstype":"reiserfs"], $["file":"/home", "freq":0, "mntops":"defaults", "passno":0, "spec":"foo.bar.com:/home", "vfstype":"nfs"], $["file":"/var/spool/mail", "freq":0, "mntops":"defaults", "passno":0, "spec":"foo.bar.com:/var/spool/mail", "vfstype":"nfs"], $["file":"/a\\040space", "freq":1, "mntops":"defaults", "passno":3, "spec":"/dev/hda7", "vfstype":"reiserfs"], $["file":"/b\\040space", "freq":0, "mntops":"defaults", "passno":0, "spec":"foo.bar.com:/space\\040dir", "vfstype":"nfs"]] Modified: trunk/nfs-client/testsuite/tests/readwrite2.out URL: http://svn.opensuse.org/viewcvs/yast/trunk/nfs-client/testsuite/tests/readw… ============================================================================== --- trunk/nfs-client/testsuite/tests/readwrite2.out (original) +++ trunk/nfs-client/testsuite/tests/readwrite2.out Thu Nov 3 13:41:19 2011 @@ -6,7 +6,6 @@ Read .etc.idmapd_conf "Domain" "localhost" Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_init | /usr/bin/grep -q '[0-6]:on'" 0 Execute .target.bash "/sbin/chkconfig -l SuSEfirewall2_setup | /usr/bin/grep -q '[0-6]:on'" 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Dump Write - nfs is in use - start services @@ -29,7 +28,6 @@ Execute .target.bash "/sbin/service portmap status" $["TERM":"raw"] 0 Execute .target.bash_output "/sbin/service nfs start" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Execute .target.bash "/sbin/service nfs status" $["TERM":"raw"] 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Dump Read - nfs is in use & stopped @@ -61,7 +59,6 @@ Execute .target.bash "/sbin/service portmap status" $["TERM":"raw"] 0 Execute .target.bash_output "/sbin/service nfs start" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] Execute .target.bash "/sbin/service nfs status" $["TERM":"raw"] 0 -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Dump Read - nfs not used & running @@ -78,7 +75,6 @@ Write .etc.fstab [$["file":"/", "freq":1, "mntops":"defaults", "passno":2, "spec":"/dev/hda6", "vfstype":"ext3"]] true Write .sysconfig.nfs.NFS4_SUPPORT "no" true Execute .target.bash_output "/sbin/service nfs stop" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true Dump Dump Read - nfs not used & services are stopped @@ -95,5 +91,4 @@ Write .etc.fstab [$["file":"/", "freq":1, "mntops":"defaults", "passno":2, "spec":"/dev/hda6", "vfstype":"ext3"]] true Write .sysconfig.nfs.NFS4_SUPPORT "no" true Execute .target.bash_output "/sbin/service nfs stop" $["TERM":"raw"] $["exit":0, "stderr":"", "stdout":""] -Execute .target.bash "/sbin/service SuSEfirewall2_init status" $["TERM":"raw"] 0 Return true -- 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] r66676 - /tags/branch-Code-11-SP2-2_17_30/iscsi-client/
by fehr＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: fehr Date: Thu Nov 3 13:11:41 2011 New Revision: 66676 URL: http://svn.opensuse.org/viewcvs/yast?rev=66676&view=rev Log: Created tag branch-Code-11-SP2-2_17_30 for iscsi-client Added: tags/branch-Code-11-SP2-2_17_30/iscsi-client/ (props changed) - copied from r66675, branches/SuSE-Code-11-SP2-Branch/iscsi-client/ -- 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] r66675 - in /branches/SuSE-Code-11-SP2-Branch/iscsi-client: VERSION package/yast2-iscsi-client.changes src/IscsiClientLib.ycp src/widgets.ycp
by fehr＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: fehr Date: Thu Nov 3 13:11:32 2011 New Revision: 66675 URL: http://svn.opensuse.org/viewcvs/yast?rev=66675&view=rev Log: - vesion 2.17.30 - call discovery with "-t fw" if "-t st" does not provide any targets (bnc#725833) Modified: branches/SuSE-Code-11-SP2-Branch/iscsi-client/VERSION branches/SuSE-Code-11-SP2-Branch/iscsi-client/package/yast2-iscsi-client.changes branches/SuSE-Code-11-SP2-Branch/iscsi-client/src/IscsiClientLib.ycp branches/SuSE-Code-11-SP2-Branch/iscsi-client/src/widgets.ycp Modified: branches/SuSE-Code-11-SP2-Branch/iscsi-client/VERSION URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/iscsi… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/iscsi-client/VERSION (original) +++ branches/SuSE-Code-11-SP2-Branch/iscsi-client/VERSION Thu Nov 3 13:11:32 2011 @@ -1 +1 @@ -2.17.29 +2.17.30 Modified: branches/SuSE-Code-11-SP2-Branch/iscsi-client/package/yast2-iscsi-client.changes URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/iscsi… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/iscsi-client/package/yast2-iscsi-client.changes (original) +++ branches/SuSE-Code-11-SP2-Branch/iscsi-client/package/yast2-iscsi-client.changes Thu Nov 3 13:11:32 2011 @@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Thu Nov 3 13:06:10 CET 2011 - fehr(a)suse.de + +- 2.17.30 +- call discovery with "-t fw" if "-t st" does not provide any + targets (bnc#725833) + +------------------------------------------------------------------- Wed Oct 26 15:26:38 CEST 2011 - fehr(a)suse.de - 2.17.29 Modified: branches/SuSE-Code-11-SP2-Branch/iscsi-client/src/IscsiClientLib.ycp URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/iscsi… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/iscsi-client/src/IscsiClientLib.ycp (original) +++ branches/SuSE-Code-11-SP2-Branch/iscsi-client/src/IscsiClientLib.ycp Thu Nov 3 13:11:32 2011 @@ -857,9 +857,9 @@ }); } -global string GetDiscoveryCmd( string ip, string port) +global string GetDiscoveryCmd( string ip, string port, boolean fw) { - y2milestone( "GetDiscoveryCmd ip:%1 port:%2", ip, port); + y2milestone( "GetDiscoveryCmd ip:%1 port:%2 fw:%3", ip, port, fw); string command = "-m discovery -P 1"; if( useISNS() ) command = command + " -t isns"; @@ -869,7 +869,11 @@ y2milestone( "ifs=%1", ifs ); ifs = maplist( string s, ifs, ``("-I "+s)); y2milestone( "ifs=%1", ifs ); - command = command + sformat( " -t st %3 -p %1:%2", ip, port, mergestring(ifs," ")); + string tgt = "st"; + if( fw ) + tgt = "fw"; + command = command + sformat( " -t %4 %3 -p %1:%2", ip, port, + mergestring(ifs," "), tgt); } command = GetAdmCmd(command); y2milestone( "GetDiscoveryCmd %1", command ); Modified: branches/SuSE-Code-11-SP2-Branch/iscsi-client/src/widgets.ycp URL: http://svn.opensuse.org/viewcvs/yast/branches/SuSE-Code-11-SP2-Branch/iscsi… ============================================================================== --- branches/SuSE-Code-11-SP2-Branch/iscsi-client/src/widgets.ycp (original) +++ branches/SuSE-Code-11-SP2-Branch/iscsi-client/src/widgets.ycp Thu Nov 3 13:11:32 2011 @@ -472,10 +472,16 @@ //y2internal("auth: %1/%2, %3/%4", user_in, pass_in, user_out, pass_out); bg_finish=false; // ` with authentication - string command = IscsiClientLib::GetDiscoveryCmd(ip,port); + string command = IscsiClientLib::GetDiscoveryCmd(ip,port,false); list<string>trg_list = runInBg( command ); - IscsiClientLib::targets = IscsiClientLib::ScanDiscovered( trg_list ); while(!bg_finish){}; + if( size(trg_list)==0 ) + { + command = IscsiClientLib::GetDiscoveryCmd(ip,port,true); + trg_list = runInBg( command ); + while(!bg_finish){}; + } + IscsiClientLib::targets = IscsiClientLib::ScanDiscovered( trg_list ); // restore old config IscsiClientLib::oldConfig(); -- 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] r66674 - in /trunk/installation: VERSION package/yast2-installation.changes startup/YaST2.call startup/common/network.sh startup/common/vnc.sh
by aschnell＠svn2.opensuse.org 03 Nov '11

03 Nov '11

Author: aschnell Date: Thu Nov 3 12:20:48 2011 New Revision: 66674 URL: http://svn.opensuse.org/viewcvs/yast?rev=66674&view=rev Log: - use same code to display ip addresses during vnc and ssh installation (bnc#727802) Modified: trunk/installation/VERSION trunk/installation/package/yast2-installation.changes trunk/installation/startup/YaST2.call trunk/installation/startup/common/network.sh trunk/installation/startup/common/vnc.sh Modified: trunk/installation/VERSION URL: http://svn.opensuse.org/viewcvs/yast/trunk/installation/VERSION?rev=66674&r… ============================================================================== --- trunk/installation/VERSION (original) +++ trunk/installation/VERSION Thu Nov 3 12:20:48 2011 @@ -1 +1 @@ -2.21.27 +2.21.28 Modified: trunk/installation/package/yast2-installation.changes URL: http://svn.opensuse.org/viewcvs/yast/trunk/installation/package/yast2-insta… ============================================================================== --- trunk/installation/package/yast2-installation.changes (original) +++ trunk/installation/package/yast2-installation.changes Thu Nov 3 12:20:48 2011 @@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Thu Nov 03 11:52:08 CET 2011 - aschnell(a)suse.de + +- use same code to display ip addresses during vnc and ssh + installation (bnc#727802) +- 2.21.28 + +------------------------------------------------------------------- Wed Nov 2 17:14:51 CET 2011 - fcrozat(a)suse.com - Ensure network is not started by systemd before Firstboot / Modified: trunk/installation/startup/YaST2.call URL: http://svn.opensuse.org/viewcvs/yast/trunk/installation/startup/YaST2.call?… ============================================================================== --- trunk/installation/startup/YaST2.call (original) +++ trunk/installation/startup/YaST2.call Thu Nov 3 12:20:48 2011 @@ -392,6 +392,7 @@ # 1) Source common script functions #--------------------------------------------- . /usr/lib/YaST2/startup/common/functions.sh +. /usr/lib/YaST2/startup/common/network.sh . /usr/lib/YaST2/startup/requires #============================================= Modified: trunk/installation/startup/common/network.sh URL: http://svn.opensuse.org/viewcvs/yast/trunk/installation/startup/common/netw… ============================================================================== --- trunk/installation/startup/common/network.sh (original) +++ trunk/installation/startup/common/network.sh Thu Nov 3 12:20:48 2011 @@ -41,6 +41,13 @@ return 1 } + +function list_ifaces() +{ + /sbin/ifconfig | grep -A1 "^[a-z]" +} + + #----[ vnc_message ]-----# function vnc_message () { #-------------------------------------------------- @@ -70,7 +77,6 @@ active interfaces: EOF - /sbin/ifconfig | grep -A1 "^[a-z]" + list_ifaces echo } - Modified: trunk/installation/startup/common/vnc.sh URL: http://svn.opensuse.org/viewcvs/yast/trunk/installation/startup/common/vnc.… ============================================================================== --- trunk/installation/startup/common/vnc.sh (original) +++ trunk/installation/startup/common/vnc.sh Thu Nov 3 12:20:48 2011 @@ -44,38 +44,27 @@ # start Xvnc server and write a log file from the # VNC server process # - # .../ # The IP set in install.inf may not be valid if the DHCP server # gave us a different lease in the meantime (#43974). - # sed: don't print; if it's localhost, skip; try locating IPv4; - # skip if not found; otherwise print and exit - # ---- - IP=`ip addr list | sed -n \ - -e '/127.0.0.[[:digit:]]/b;s/^[[:space:]]*inet[[:space:]]$[^/]*$.*/\1/;T;p;q'` echo echo starting VNC server... echo A log file will be written to: /var/log/YaST2/vncserver.log ... cat <<-EOF - + *** - *** You can connect to $IP, display :1 now with vncviewer - *** Or use a Java capable browser on http://$IP:5801/ + *** You can connect to <host>, display :1 now with vncviewer + *** Or use a Java capable browser on http://<host>:5801/ *** - + (When YaST2 is finished, close your VNC viewer and return to this window.) - + + Active interfaces: + EOF - #========================================== - # Fake hostname to make VNC screen pretty - #------------------------------------------ - if [ "$(hostname)" = "(none)" ] ; then - hostname $IP - fi - #========================================== - # store hostname for use in desktop option - #------------------------------------------ - VNC_HOSTNAME=`hostname` + list_ifaces + echo + #========================================== # Start Xvnc... # For -noreset see BNC #351338 @@ -83,7 +72,7 @@ $Xbindir/Xvnc $Xvncparam :0 \ -noreset \ -rfbauth /root/.vnc/passwd.yast \ - -desktop "Installation at: $VNC_HOSTNAME" \ + -desktop "Installation" \ -geometry 800x600 \ -depth 16 \ -rfbwait 120000 \ -- To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-commit+help(a)opensuse.org

1 0