July 2012 - openSUSE Autoinstall - openSUSE Mailing Lists

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

[opensuse-autoinstall] openSUSE 12.2 and autoyast-configured services
by Conny Seidel 12 Nov '12

12 Nov '12

Hello list, I'm having difficulties enabling systemd services in openSUSE 12.2 from the autoyast file. Our current way doesn't work anymore: <runlevel> <default>3</default> <services config:type="list"> <service> <service_name>rpcbind</service_name> <service_status>enable</service_status> </service> </services> </runlevel> At least not for rpcbind. My workaround currently is to use a post-script to do a "systemctl enable rpcbind.service". -- Kind regards. Conny Seidel ################################################################## # Email : conny.seidel(a)amd.com GnuPG-Key : 0xA6AB055D # # Fingerprint: 17C4 5DB2 7C4C C1C7 1452 8148 F139 7C09 A6AB 055D # ################################################################## # Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach # # General Managers: Alberto Bozzo # # Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen # # HRB Nr. 43632 # ################################################################## -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

5 5

[opensuse-autoinstall] autoyast with multiple LVM Volume Groups
by big beer 07 Sep '12

07 Sep '12

Hello, I'm trying to have autoyast setup some LVM volume groups. I can get things setup with a single volume group, but if try to add 2 volume groups I seem to be running into some issue. I'm using the following xml inside the partitioning section to setup the PVs and add to the volume groups. . . . <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <lvm_group>firstvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdc</device> <partitions config:type="list"> <partition> <lvm_group>secondvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> . . . The problem is that both disks are configured as PVs in the same VG. Both sdb and sdc will be added to firstvg and secondvg will not exist. Am I trying this wrong or am I hitting some sort of bug? thanks -- bigbeer -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

5 7

[opensuse-autoinstall] Specify RIS service as add_on?
by Joschi Brauchle 04 Sep '12

04 Sep '12

Hey everyone, another simple Autoyast question: Can I somehow specify a RIS (http://en.opensuse.org/openSUSE:Standards_Repository_Index_Service) URL, so that YaST gets all repositories from a RIS repoindex.xml file? I tried to add is as an add_on product: <add_on_products config:type="list"> <listentry> <media_url>nfs://<server>/ha/export/install/linux/opensuse/11.4/ris/base</media_url> <product>OpenSUSE11.4</product> <product_dir>/</product_dir> <name>AutoYaST_LNT_RIS</name> </listentry> ... But this did not work. The AutoYast Docs did not lead me to a solution yet, still looking though. BTW: Thanks Uwe for your answer to my "copy directory" question! -- Dipl.-Ing. Joschi Brauchle, M.S. Institute for Communications Engineering (LNT) Technische Universitaet Muenchen (TUM) 80290 Munich, Germany Tel (work): +49 89 289-23474 Fax (work): +49 89 289-23490 E-mail: joschi.brauchle(a)tum.de Web: http://www.lnt.ei.tum.de/

2 8

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

[opensuse-autoinstall] SLES11 SP2
by Mario Gzuk 20 Jul '12

20 Jul '12

Hi, I use the following option to set a releay host: <outgoing_mail_server>test.com</outgoing_mail_server> For SP1 it is working fine, but with SP2 the relay_host in the postfix main.cf isnt set any more. Also the alias config: <aliases config:type="list"> <alias> <alias>root</alias> <comment></comment> <destinations>bla(a)blub.com</destinations> </alias> </aliases> is written, but the "newaliases" command seems not to be executed after the alias is set. mail to root will be sent local, after running newaliases the mail is send to bla(a)blub.com. Thank you for an answer. Cheers Mario -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

4 9

[opensuse-autoinstall] opensuse 11.4: Order of packages to install
by Daniel Spannbauer 20 Jul '12

20 Jul '12

Hello, we install a 11.4-system with autoyast. Works nearly perfectly. But now, I have a problem and don't know how to solve it.... There are several packages which generate users with fixed IDs.And there is one package (not from us) which creates a user without a fixed ID. So the user gets the next free uid. In most cases it works, but sometimes the package with the random uid is installed before our packages with the fixed uid. In this case the uid already exists when our package is installed and yast shows an error and stops here....our user is not created. Which order are the packages installed? Are they installed randomly? Any Ideas how to solve it? 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

4 4

[opensuse-autoinstall] autoyast 12.2 factory troubles: cannot find /usr/bin/xsltproc
by Matthias Danzl 20 Jul '12

20 Jul '12

Trying to set up autoyast for the 12.2 development version, I encountered the error stating autoyast can't find /usr/bin/xsltproc during execution of pre-installation scripts. Using the command line, I found out that xsltproc is nowhere in $PATH. Any ideas on this? TIA -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

3 11

[opensuse-autoinstall] Installation: Can't configure net with "linuxrc"
by Dominik Baumann 16 Jul '12

16 Jul '12

Hello, for using autoyast per http i want to configure network with linuxrc [1] and its kernel boot parameters (hostip, netmask, ...), resp. with the appropriate installation dialogue [2]. Unfortunately both don't work for me: The machine doesn't react to ping nor is "ifconfig -a" showing an active network interface or ip address. But i can set it manually with "ifconfig eth0 inet ..." at the same phase of installation, so missing network drivers shouldn't be the problem. The problem appears both on opensuse release 12.1 and 12.2/Milestone-3, both in a virtual and a physical machine. Any hints? PS: I know that linuxrc hasn't directly to do with autoyast, but perhaps it's often used there(?). I already asked at the german opensuse-de@ mailing list, but found no solution there. Dominik. [1] http://en.opensuse.org/SDB:Linuxrc [2] http://paste.opensuse.org/6379e182 http://paste.opensuse.org/af7f337d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

4 18

[opensuse-autoinstall] proxy and suse_register/smt problem (and workaround)
by Oliver Gorwits 09 Jul '12

09 Jul '12

Hi, (I'm new to SuSE & AutoYaST, and not sure whether this is a problem with AutoYaST, or a SuSE package, or my own mistake...) I noticed that configuring both <proxy> and <suse_register> in an autoyast profile fails if <no_proxy> is needed to access the SMT server. What seems to happen is that the <proxy> section of the autoyast profile is parsed, but the root user's .curlrc file only gets the --proxy setting and not any --noproxy setting. This makes SMT registration fail. A workaround is to have a script like this in the autoyast profile: <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <source><![CDATA[ echo "--noproxy 'localhost,.example.com'" >> /root/.curlrc ]]> </source> </script> </chroot-scripts> So, this message is partly for the benefit of people searching the list archives, but also an open question whether anyone else is aware of the problem. For info, I am installing from a SLES 11 SP2 DVD, and the suseRegister package version is 1.4-1.24.1. regards, oliver. -- Oliver Gorwits Networks and Computer Security ECMWF -- 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.1, autoyast and systemd
by 686f6c6d 04 Jul '12

04 Jul '12

Hi, here's the problems I ran into. They all seem to be related to systemd, but I did not want to hijack the other thread, although this one might solve the other problem, too. 1. The final kexec/reboot is not executed. Both <final_reboot config:type="boolean">false</final_reboot>, meaning kexec will be used, and <final_reboot config:type="boolean">true</final_reboot> have no effect at all[0]. This also means that... 2. Init-Services (<runlevel>) defined in autoyast are not started/stopped, so, f.e., no ssh keys are generated. (This also results in a lot of subsequent errors in our setup.) To fix this, just include: <software> <remove-packages config:type="list"> <package>systemd-sysvinit</package> </remove-packages> </software> This way, sysvinit-init will be installed and used. When can we expect autoyast to support systemd? [0]: Once you do a manual reboot (if you happen to have access other than ssh to the machine), the machine will do the autoyast kexec/reboot after that. -- Kind regards/Mit freundlichen Grüßen 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

5 20

[opensuse-autoinstall] partitioning and skiplist
by Jochen Schaefer 03 Jul '12

03 Jul '12

Hi, I want to prevent the partitioning of all /dev/sdxxx devices by autoyast. How to achieve that? Regarding to Uwe's blog I can use the skip_list feature. But I'm uncertain about which skip_key and skip_value to use? Thanks, Jochen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 4

[opensuse-autoinstall] Copy directories from remote source using <file_location>
by Joschi Brauchle 02 Jul '12

02 Jul '12

Hi there, I just wanted to check before I do a trial and error test... Autoyast's file section currently allows me to: * Fetch files from remote source using <file_location>http://my.server.site/issue</file_location> for example. * Create directories by adding a slash, i.e., <file_path>/mydir/a/b/c/</file_path> So, natural question: Can Autoyast fetch directories by combining both? <file_location>http://my.server.site/issue/</file_location> <file_path>/mydir/a/b/c/</file_path> If not, I will use a script to do that... but it would be nice :-) -- Dipl.-Ing. Joschi Brauchle, M.S. Institute for Communications Engineering (LNT) Technische Universitaet Muenchen (TUM) 80290 Munich, Germany Tel (work): +49 89 289-23474 Fax (work): +49 89 289-23490 E-mail: joschi.brauchle(a)tum.de Web: http://www.lnt.ei.tum.de/

2 1

[opensuse-autoinstall] ldap-configuration using ldap
by Robert Klein 02 Jul '12

02 Jul '12

Hi, I'm currently testing ldap-client configuration using autoyast. Here is a list of issues I found. Please comment. I'll probably file some bug reports next week. Testing system is factory snapshot from April 12, 2012 (that is, M3, probably). - (YaST) Issues during installation: - Both the reference profile and the XML schema allow the parameter <bind_dn>, but there's no binddn in /etc/ldap after installation. - missing support for additional LDAP configuration parameters, for example there ought to be a parameter <bind_pw> resulting in a bindpw in /etc/ldap.conf after installation. Also, I could use a way wo put the tls certfile into the autoyast xml, e.g. using a parameter <tls_cacertfile-content><source><![CDATA[...]]></... - Yast Reference Profile (created using Yast -> Autoyast -> Tools -> Create Reference Profile) issues: - A created reference profile has a parameter <mkhomedir>, but it isn't allowed according to the XML schema (/usr/share/YaST2/schema/autoyast/rng/ldap.rng) and apparently isn't used, i.e. it didn't appear in /etc/ldap.conf after installation (I only had it set to "false", though). - schema only issues: - The parameters <sssd>, <tls_cacertdir> and <tls_cacertfile> aren't in the XML schema (/usr/share/YaST2/schema/autoyast/rng/ldap.rng) They are, however reference profiles created with Yast -> AutoYast and are used during installation Thanks and best regards Robert -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

4 3