- openSUSE Autoinstall

[opensuse-autoinstall] Autoyast : Grub doesn't install
by Dsant 19 Aug '12

19 Aug '12

Hello, I Have the same problem as in the RESOLVED bug here : https://bugzilla.novell.com/show_bug.cgi?id=757523 * created a xml file with yast2 * like in the description, autoyast has lost user, root password. * Then image : https://bugzilla.novell.com/attachment.cgi?id=486439&action=edit is the file produced by yast2 corrupted ? Dsant Here is the Yast2 file : <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <bootloader> <device_map config:type="list"> <device_map_entry> <firmware>fd0</firmware> <linux>/dev/sdc</linux> </device_map_entry> </device_map> <global> <activate>true</activate> <boot_boot>false</boot_boot> <boot_extended>false</boot_extended> <boot_mbr>true</boot_mbr> <boot_root>false</boot_root> <default>Linux_sda1</default> <gfxmenu>/boot/message</gfxmenu> <timeout config:type="integer">8</timeout> </global> <loader_type>grub</loader_type> <sections config:type="list"> <section> <append>splash=silent quiet showopts</append> <image>/boot/vmlinuz</image> <initrd>/boot/initrd</initrd> <name>Linux_sda1</name> <noverifyroot>false</noverifyroot> <original_name>linux</original_name> <root>(hd0,0)</root> <type>image</type> <vgamode>0x314</vgamode> </section> <section> <append>splash=silent quiet showopts</append> <image>/boot/vmlinuz</image> <initrd>/boot/initrd</initrd> <name>Linux_sda2</name> <noverifyroot>false</noverifyroot> <original_name>linux</original_name> <root>(hd0,1)</root> <type>image</type> <vgamode>0x314</vgamode> </section> <section> <append>showopts apm=off noresume nosmp maxcpus=0 edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset x11failsafe</append> <image>/boot/vmlinuz</image> <initrd>/boot/initrd</initrd> <name>Failsafe</name> <original_name>failsafe</original_name> <root></root> <type>image</type> </section> </sections> </bootloader> <deploy_image> <image_installation config:type="boolean">false</image_installation> </deploy_image> <firewall> <enable_firewall config:type="boolean">false</enable_firewall> <start_firewall config:type="boolean">false</start_firewall> </firewall> <groups config:type="list"> <group> <gid>7</gid> <group_password>x</group_password> <groupname>lp</groupname> <userlist>dd</userlist> </group> <group> <gid>305</gid> <group_password>!</group_password> <groupname>vboxusers</groupname> <userlist>dd</userlist> </group> <group> <gid>33</gid> <group_password>x</group_password> <groupname>video</groupname> <userlist>gdm,dd</userlist> </group> <group> <gid>17</gid> <group_password>x</group_password> <groupname>audio</groupname> <userlist>dd,pulse</userlist> </group> </groups> <keyboard> <keymap>french</keymap> </keyboard> <login_settings/> <networking> <dhcp_options> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <domain>lyon</domain> <hostname>mypc</hostname> <nameservers config:type="list"> <nameserver>192.168.200.1</nameserver> <nameserver>8.8.8.8</nameserver> </nameservers> <resolv_conf_policy>auto</resolv_conf_policy> <searchlist config:type="list"> <search>lyon</search> </searchlist> <write_hostname config:type="boolean">true</write_hostname> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <ipv6 config:type="boolean">true</ipv6> <managed config:type="boolean">false</managed> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> <partitioning config:type="list"/> <runlevel> <default>5</default> <services config:type="list"> <service> <service_name>sshd</service_name> <service_start>3 5</service_start> </service> </services> </runlevel> <software> <packages config:type="list"> <package>autoyast2-installation</package> </packages> <patterns config:type="list"> <pattern>base</pattern> </patterns> </software> <sshd> <config> <AllowTcpForwarding config:type="list"> <listentry>yes</listentry> </AllowTcpForwarding> <Compression config:type="list"> <listentry>yes</listentry> </Compression> <MaxAuthTries config:type="list"> <listentry>6</listentry> </MaxAuthTries> <PermitRootLogin config:type="list"> <listentry>no</listentry> </PermitRootLogin> <Port config:type="list"> <listentry>1975</listentry> </Port> <PrintMotd config:type="list"> <listentry>yes</listentry> </PrintMotd> <PubkeyAuthentication config:type="list"> <listentry>yes</listentry> </PubkeyAuthentication> <RSAAuthentication config:type="list"> <listentry>no</listentry> </RSAAuthentication> <X11Forwarding config:type="list"> <listentry>no</listentry> </X11Forwarding> </config> <status config:type="boolean">true</status> </sshd> <timezone> <hwclock>UTC</hwclock> <timezone>Europe/Paris</timezone> </timezone> <user_defaults> <group>25</group> <groups>video</groups> <home>/home</home> <inactive>-1</inactive> <shell>/bin/bash</shell> <skel>/etc/skel</skel> <umask>022</umask> </user_defaults> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <fullname>dd</fullname> <gid>25</gid> <home>/home/dd</home> <password_settings> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1000</uid> <user_password>$1$kL54rgJ2$3j8iyHtLs8IkFkFVv7VyW0</user_password> <username>dd</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <fullname>root</fullname> <gid>0</gid> <home>/root</home> <password_settings> <inact>-1</inact> <max>-1</max> <min>-1</min> <warn>-1</warn> </password_settings> <shell>/bin/bash</shell> <uid>0</uid> <user_password>$1$C0LfrEWK$LK83dzU/fuoz/5rlEwkWD/</user_password> <username>root</username> </user> </users> </profile> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 1

[opensuse-autoinstall] Autoyast - Grub : which arguments ?
by Dsant 19 Aug '12

19 Aug '12

With autoyast, in the xml file I put the grub arguments : kernel : /boot/vmlinuz initrd : /boot/initrd root : (hd0,0) However, during installation I can see that /boot is empty ! And grub install fails ("An error occurred during initrd creation"). What are the correct arguments ? Dsant, from France XML file (part) : <section> <append>splash=silent quiet showopts</append> <image>/boot/vmlinuz</image> <initrd>/boot/initrd</initrd> <name>Linux_sda1</name> <noverifyroot>false</noverifyroot> <original_name>linux</original_name> <root>(hd0,0)</root> <type>image</type> </section> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

[opensuse-autoinstall] xml tag to add "sudoers_base" line to /etc/ldap.conf file?
by Nefi Munoz 16 Aug '12

16 Aug '12

Hi, Is there an autoyast tag to add a sudoers line to /etc/ldap.conf file? My customer tried adding this line to <ldap> section but this didn't work: <sudoers_base>ou=sudoers,dc=HPC,dc=COMPANY,dc=COM</sudoers_base> Below is the complete ldap section (I masked company name) Thanks in advance, Nefi M. --------------------------- <ldap> <base_config_dn>ou=ldapconfig,dc=HPC,dc=COMPANY,dc=COM</base_config_dn> <bind_dn></bind_dn> <create_ldap config:type="boolean">false</create_ldap> <file_server config:type="boolean">false</file_server> <ldap_domain>dc=HPC,dc=COMPANY,dc=COM</ldap_domain> <ldap_server>server.hpc.COMPANY.com server.hpc.COMPANY.com</ldap_server> <ldap_tls config:type="boolean">false</ldap_tls> <ldap_v2 config:type="boolean">false</ldap_v2> <login_enabled config:type="boolean">true</login_enabled> <member_attribute>member</member_attribute> <nss_base_group>ou=Group,dc=HPC,dc=COMPANY,dc=COM</nss_base_group> <nss_base_passwd>ou=People,dc=HPC,dc=COMPANY,dc=COM</nss_base_passwd> <nss_base_shadow>ou=People,dc=HPC,dc=COMPANY,dc=COM</nss_base_shadow> <pam_password>exop</pam_password> <start_autofs config:type="boolean">true</start_autofs> <start_ldap config:type="boolean">true</start_ldap> <tls_cacertdir>/etc/ssl/certs</tls_cacertdir> <sudoers_base>ou=sudoers,dc=HPC,dc=COMPANY,dc=COM</sudoers_base> </ldap> -----------------------------

2 2

[opensuse-autoinstall] schema fixes for <files>
by Andrew Daugherity 13 Aug '12

13 Aug '12

The autoyast schema currently lacks the file_location element and thus my profile fails to validate (despite working properly). I've fixed this in my "simple_files_fix" branch on github[1]. I've also made a "files_cleanup" branch that enforces what I think autoyast expects (open to correction, of course): * there should only be file_content or file_location, not both * file_path should be mandatory * everything else (file_owner, file_permissions, file_script) is optional but should only occur once per file * all of the file_* elements can occur in any order within the <file> tag Which brings me to a point of confusion: my profile, which I based on a previous version of the AutoYaST documentation, uses <file> rather than <config_file>, e.g.: <files config:type="list"> <file> <file_location>http://blah.blah/foo</file_location> <file_path>/foo/bar</file_path> </file> ... </files> However, the current documentation[2] uses <config_file> instead of <file>. My profile works correctly in both SLES 11 SP1 & SP2 and openSUSE 12.1, and the schema expects <file>, so this appears correct, but I hesitate to call the documentation wrong without further input. Whichever way is correct, everything should be reconciled. BTW, it's great that YaST on github now -- it makes fixes like this a lot easier! Uwe (or others), please let me know how you wish to proceed, and I'll file a github pull request and/or a BugZilla entry. Thanks, Andrew Daugherity Systems Analyst Division of Research, Texas A&M University [1] https://github.com/adaugherity/yast-autoinstallation/branches [2] http://www.suse.de/~ug/autoyast_doc/configuration.html#createprofile.comple… -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] USB-Stick as installation-Source
by Daniel Spannbauer 08 Aug '12

08 Aug '12

Hello, I wan't to install opensuse 11.4 with an USB Stick as the installation source. But how do I tell the system where the source is? I tried it with install=hd:// install=usb:// install=/dev/sdc1, with 2 Slashes, 3 slashes, on slash....nothing seems to work. Regards Daniel -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

5 23

[opensuse-autoinstall] Nachricht: INFO
by INFO Firmen 08 Aug '12

08 Aug '12

Guten Tag, Wir sind in Besitz neuer, aktualisierter Datenbanken deutscher Firmen und Unternehmen. Ihre Konkurrenz sucht täglich nach neuen Methoden der Kundengewinnung. Unser Produkt ermöglicht dies Ihnen auf effektive Weise. Wir laden Sie dazu ein, Gebrauch aus unseren Lösungen für eine gelungene Werbekampagne zu machen. Wir bieten Ihnen Datenbanken der aktivsten Firmen auf dem deutschen Markt, die gerne Interesse für Ihr Produkt zeigen und eine feste Zusammenarbeit mit Ihnen knüpfen. http://www.firmen-de.com/verzeichnis/ Beweis der Wirksamkeit unserer Produkte, ist die ständig wachsende Liste zufriedener Kunden, die für Ihr Angebot schnell neue Abnehmer fanden. Unsere Kataloge sind auf Branchen und Unterbranchen aufgeteilt, weshalb es einfach ist Kampagnen an Personen und Firmen zu wenden, die Abnehmer für Ihre Produkte und Dienstleistungen sein können. Die Datenbank wird alle drei Monate aktualisiert, zusätzlich bieten wir jedem neuen Kunden, der Datenbanken von Firmen bei uns kauft, die erste Aktualisierung KOSTENLOS an. Das Produkt wird elektronisch und auf CD-ROM geliefert. Weitere Informationen finden Sie auf unserer Website: http://www.firmen-de.com/ Sie können uns auch gerne persönlich kontaktieren, wir sind bereit Ihnen auf alle Fragen zu antworten. Mit freundlichem Gruß --- http://www.firmen-de.com -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

[opensuse-autoinstall] 12.2RC2: Failed to fetch init script from NFS, all other scripts OK
by Joschi Brauchle 07 Aug '12

07 Aug '12

Hey there, I just started testing 12.2RC2 and noticed to following. There are multiple custom user scripts in my XML file, all of which get pulled from an NFS server. Now, all scripts were transferred successfully to the installation system under /var/adm/autoinstall/scripts, EXCEPT the init script! The Init script is mention like this in my XML: -------- <init-scripts config:type="list"> <script> <filename>init0000_final_installation.sh</filename> <location><![CDATA[nfs://<server>/<path>/init0000_final_installation.sh]]></location> </script> </init-scripts> -------- All other scripts come from the same NFS server, same path, different filename (of course) and work nicely. In y2log, it says: -------- 2012-08-06 10:34:13 <1> test122(3344) [Interpreter] clients/autoinst_scripts2_finish.ycp:60 Calling YaST client autoinst_scripts2_finish 2012-08-06 10:34:13 <1> test122(3344) [YCP] clients/autoinst_scripts2_finish.ycp:33 starting autoinst_scripts2_finish 2012-08-06 10:34:13 <1> test122(3344) [YCP] AutoinstScripts.ycp:690 Writing init script into /var/adm/autoinstall/init.d/init0000_final_installation.sh 2012-08-06 10:34:13 <1> test122(3344) [agent-system] SystemAgent.cc(Execute):1130 mkdir /tmp/YaST2-03344-nXRhf8/tmp_mount 2012-08-06 10:34:13 <2> test122(3344) [YCP] autoinstall/io.ycp:196 Mount failed 2012-08-06 10:34:13 <3> test122(3344) [YCP] AutoinstScripts.ycp:696 script nfs://<server>/<path>/init0000_final_installation.sh could not be retrieved -------- Another init script is included with its source in the XML file, and this is running fine. Hence, it looks like the problem lies in mounting the remote NFS path when running the init scripts...? Best regards, Joschi Brauchle

4 10

[opensuse-autoinstall] update repo/kernel-default problems [was: 12.1, autoyast and systemd]
by 686f6c6d 31 Jul '12

31 Jul '12

Splitting this because AFAICT it has nothing to do with systemd, I just ran into it while trying to get systemd to work. On Tue, Apr 10, 2012 at 1:19 PM, 686f6c6d <686f6c6d(a)googlemail.com> wrote: > On Mon, Apr 2, 2012 at 16:16, 686f6c6d <686f6c6d(a)googlemail.com> wrote: >> >> - Using kernel-default-3.1.0-1.2.1.x86_64 from the "install" repo, the >> installation succeeds. >> - Using kernel-default-3.1.9-1.4.1.x86_64 from the "update" repo, the >> installation fails. > > Let me correct that: Once I changed the profile again to re-include > some of our scripts (that were disabled while debugging), even > kernel-default 3.1.0 fails with the same problem. > Need to do further debugging. Those seem to be unrelated problems. One thing I can say with certainty right now is that my profile does not work when I enable the update repo: installation of kernel-default fails because large parts of the device nodes in /dev are missing. When I disable the repo, everything works fine. Uwe: What is the best way to proceed from here? Should I open a bug for autoyast (although autoyast is not the real culprit here), or should we debug further on this list/off-list and then open bugs for the correct packages? I'm currently sanitizing the logs of both installations with and without the update repo enabled, which will take a while. -- Kind regards 686f6c6d / Christopher 'm4z' Holm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 9

[opensuse-autoinstall] custom user scripts
by dutchguy69 23 Jul '12

23 Jul '12

So far I have used custom user scripts via the <source> tag within my autoyast profile. When I was browsing the autoYast documentation I noticed that it is also possible to use the <location> tag instead which makes everything a bit cleaner from my perspective. Made the required changes and did some tests. Works fine for pre, post and init scripts. Having issues with chroot and post partition one. Although the creation of post and init scripts during the autoyast run is logged within the y2log I do not see much for the others. Using <location> tag for chroot does not work, no error in the y2log. When I revert back to <source> method for this it is fine and works. The post partitioning one doesn't work in both situations. Again no errors that I can find on this. Had not used this one before within my processing. I'm running this inside of a virtual box VM and the overall profile is combined via rules. The final profile used for the build looks fine to me though. The scripts that I reference within the <location> tag are all within the same area with same permissions so obviously they are all available. They are available via NFS <init-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <filename>_init.sh</filename> <interpreter>shell</interpreter> <location>nfs://xx.xx.xx.xx/data/linux/autoYast/init.sh</location> <notification>Please wait while init.sh script is running...</notification> </script> </init-scripts> This is on an 12.1 install, but I do not believe that matters as I can only see references to v11 as to when these options seem to have been added to autoyast. Is anyone using this mechanism and if so does it work for you. I'm expecting that the same mechanism is used internally in autoyast for the processing of these scripts so quite surprised one works where the other doesn't. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] Makeup mirror suppliers shared photos with you
by Makeup mirror suppliers 21 Jul '12

21 Jul '12

Dear: We have obtained your name and address from internet search,I know you sell fashion and promotion item,and we are writing to inquire whether you would be willing to establish business relations with us. We have been manufacturing promotion gift for many years now.our main products have makeup mirror,cosmetic brush,hair comb/brush,manicure sets, bottle opener,measuring tape etc.At present we are interested in extending our overseas market and would appreciate your respond. Considering our competitive prices and high quality,we expect to establish a long-term partnership With you. We look forward to your early reply. Thanks Best Regards! ------------------------------------ Ike Sale Manager Ningbo Yinzhou Victy Craft Factory

2 1