openSUSE Autoinstall February 2010

autoinstall@lists.opensuse.org

14 participants
20 discussions

by John Willis

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!

8 years, 10 months

[opensuse-autoinstall] Repository Priority

by Tim Kirby

Repository Priority is obviously a useful thing to be able to manipulate. Yast lets me set it and zypper lets me set it. Yet, if I have multiple repositories defined at the beginning of my autoyast (including update repos so I get an up to date system built out of the box), I don't seem to have any control over the respective repository priorities - they're all defaulted. Or did I miss a subtle option somewhere? Tim -- Tim Kirby 651-605-9074 trk(a)cray.com Cray Inc. Information Systems -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 years

[opensuse-autoinstall] OT: Centralized patch management for OpenSuse 11.x

by Ivan De Masi

Hello, someone may start to laugh now for my (OT) question, but I can't find a satisfying solution :-/ How do you manage patches, updates, etc. for your running opensuse clients (not enterprise linux, just the "regular" opensuse distribution)? Is there a way like known from M$-World (WSUS)? As I know "Zend Management Server" is not open source (and not supported any more?!). Or can the complete management only be handled with self written scripts? Thanks! Regards, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 years, 9 months

[opensuse-autoinstall] Adding packages to profile triggers error message

by Isaac Hailperin

Hi, I try to install sles 11 via autoyast. I did an installation from dvd, and pulled an autoyast profile. This profile works, and can be installed via pxe. Now I want to add the following packages: findutils-locate, dhcp-server, bind, apache2, vsftpd, nfs-kernel-server I do this via the gui. I have also tried to do it with an editor, as the gui messed up profiles in sles10sp2. In both cases, after the first reboot, I get the errormessage: "The package resolver run failed. Please check your software section in the aut" [oyast profile] (last part invisible, I guess it should be the software section in my autoyast profile :-)) This a real problem, as I have to confirm this message, thus it stops the autoinstall process. After confirming, the autoinstall process continues. Right bevor I can log in, I get "Could not update ICEauthority file /var/lib/gdm/.ICEauthority" I confirm, and get: "There is a problem with the configuration server. (/usr/lib/GConf/2/gconf-sanity-check-2 exited with status 256)" I confirm, and can log in. Theses messages are presistend after reboot. Its annoying, but not a stopper like the first problem. Why is this? Can I avoid this? Isaac -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 years, 11 months

[opensuse-autoinstall] general rules question

by dutchguy69

I have a working autoyast install for 11.1 without using rules. Right now I would like to introduce rules but I do not seem to understand exactly how to make this work. The current install is done by supplying information for a linuxrc info file on the kernel command line info=nfs://<ip-address>/<path>/1055_init.linuxrc The info file has several parameters defined for network access, the install and the autoyast variable autoyast: nfs://<ip-address>/<path>/1055_init.autoyast <- this is my autoinst profile below the path I have created the rules directory which includes a rules .xml file with following content <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd">  <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> # CPU_TYPE on vm's is giving same result for CPU as on real hardware we have to extend to video to understand the difference between virtual and real CPU_TYPE=`cat /proc/cpuinfo|grep 'model name'|uniq|awk 'BEGIN {FS=":"};{print $2}'` VIDEO_TYPE=`/sbin/lspci | grep "VGA compatible controller"|awk 'BEGIN {FS=":"};{print $3}'` if [ "$CPU_TYPE" == " AMD Athlon(tm) 64 X2 Dual Core Processor 4400+" ]; then if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev a1)" ]; then echo -n "host1.xml" elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox Graphics Adapter" ]; then echo -n "host1-virtualbox.xml" fi # information for scan64-3200 elif [ "$CPU_TYPE" == " AMD Athlon(tm) 64 Processor 3200+" ]; then if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev a1)" ]; then echo -n "host2.xml" elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox Graphics Adapter" ]; then echo -n "host2-virtualbox.xml" fi fi </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>@custom1@</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom> <script> </script> <match>*</match> <match_type>exact</match_type> </custom> <result> <profile>1055_init.autoyast</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> I have tried to change the autoyast parameter in the info file with the following values autoyast: nfs://<ip-address>/<path>/ <-- question about profile location autoyast: nfs://<ip-address>/<path>/rules/ <-- question about profile location autoyast: nfs://<ip-address>/<path>/rules/rules.xml Above direct reference to rules file seems to work but not as expected. When I check the box I can see that in /tmp/profile/autoinst.xml I find a copy of my rules.xml file where I'm expecting a merged profile from my 1055_init.autoyast and host2.xml information I'm not sure exactly what I'm doing wrong and even after extensive check via google haven't found the right references. I've used http://forgeftp.novell.com/yast/doc/SL11.1/autoinstall/ for documentation but it is not giving me enough detail to solve above issue. Any input would be welcomed. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

11 years, 3 months

[opensuse-autoinstall] /etc/sysconfig/network/dhcp der Parameter WRITE_HOSTNAME_TO_HOSTS von "yes" auf "no" SLES11

by Dirk.Lohmann＠Bertelsmann.de

Hello, we want to set in /etc/sysconfig/network/dhcp WRITE_HOSTNAME_TO_HOSTS from "yes" to "no" in SLES11 How can wie do that with xml ? Dirk Lohmann

11 years, 7 months

[opensuse-autoinstall] openSUSE11.2: resize existing & create new partitions

by Guenther Haas

Hi all! Having a lot of notebooks with existing Windows installation on which I have to install openSUSE 11.2, I have tried to resize the Windows partition automatically with autoyast before creating the linux partitions. Is this possible? Using the following doesn't work and y2log doesn't really answer my question why: <partitions config:type="list">  <partition> <partition_nr config:type="integer">1</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> </partition>  <partition> <partition_nr config:type="integer">2</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> </partition>  <partition> <partition_nr config:type="integer">3</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <resize config:type="boolean">true</resize> <size>72GB</size> </partition>  <partition> <partition_nr config:type="integer">5</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext4</filesystem> <mountby config:type="device">id</mountby> <mount>/home</mount> <size>80GB</size> </partition> <partition> <partition_nr config:type="integer">6</partition_nr> <partition_id config:type="integer">130</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">swap</filesystem> <mountby config:type="device">id</mountby> <mount>swap</mount> <size>4GB</size> </partition> <partition> <partition_nr config:type="integer">7</partition_nr> <partition_id config:type="integer">131</partition_id> <create config:type="boolean">true</create> <format config:type="boolean">true</format> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext4</filesystem> <mountby config:type="device">id</mountby> <mount>/</mount> <size>max</size> </partition> </partitions> </drive> </partitioning> Using olny the first part works, although I thought, autoyast would complain about the missing linux partition. But it works, at least until starting the real installation: <partitions config:type="list">  <partition> <partition_nr config:type="integer">1</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> </partition>  <partition> <partition_nr config:type="integer">2</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> </partition>  <partition> <partition_nr config:type="integer">3</partition_nr> <create config:type="boolean">false</create> <format config:type="boolean">false</format> <resize config:type="boolean">true</resize> <size>72GB</size> </partition> </partitions> </drive> </partitioning> As soon as I add an additional partition, which uses the new diskspace, won by resizing the existing Windows 7 partition, the whole installations stops with an error. Even if I only ad one partition of the three given above. Any idea? Next idea was, that I could only have the resizing part in the autoyast config, then manually add the linux partitions before starting the real installation and after that checking /var/adm/autoinstall/cache/installedSystem.xml so see, what I have to enter in my autoyast config. But this doesn't work. There, I can only find what already was given in the configuration, not what I changed later manually. So it's not really the config of the "installedSystem". :-( Regards, -- Guenther Haas, Uni Ulm, Institut TAIT, guenther.haas(a)gmx.de

11 years, 8 months

[opensuse-autoinstall] package yum is not found by autoyast

by Magyari, Miklos

hi, I'm working with SLED11 and have an autoyast file containing (among lots of other stuff): <package>yum</package> it was working perfectly until I have added several new updates to my updatesource (there is no update for yum package itself). Since that autoyast complains that it cannot find the pacakge yum. Checking apache logs suggests that it doesn't even try to fetch it, just concludes that it does not exist at all. I'm lost on what went wrong. After copying the updates to updatesource, I have executed create_package_descr and create_sha1sums as usual (I have a script for this, completely unchanged). The only real change is that number of packages in updatesource increased as several packages has different versions/releases present paralelly. Do anyone has a pointer where to look for the problem? thanks in advance, Miki -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

11 years, 8 months

[opensuse-autoinstall] ayast_setup and script status posibilities

by R.E. van Holk

Hi, We are currently developing a SLES 11 setup which is run on vmware. We do not install the systems by installserver but just deploy vmware templates (clones ) on the vm's. These clones have all needed rpm's and products installed, but do not have any configuration. So in the boot process of the clone , we call a scripts which collects a prepared autoyast profile from an webserver and runs the profile using the ayast_setup procedure. So far so good , it al works and the whole system and all components are configured properly. But to make all the configuration stuff work , we have added a bunch of scripts to the autoyast profile which needs to run at the end of the ayast_setup procedure. This also works fine. The problem we have is that the script processing might take a great deal of time, during that period the status bar of ayast_setup is at 100 % all of the time. There is no status at all shown on which script is run at the moment or what is happening. I know I could turn on the option which shows the stdin and stdout , but this also asks for user confirmation to continue. So my question is : Is there a way with SLES11 autoyast profiles to produces pop-ups or something similar , without any required user input ? ( we don't want any user input , the process should be fully unattendend ) We have about 20 scripts running from autoyast right now , the total time they take to complete is now 30 minutes, that's the reason why we would like to show somehow that there is something actually runnning. Any help is appreciated. Ron -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

11 years, 8 months

Re: [opensuse-autoinstall] How to remove a section using XSLT?

by Uwe Gansert

on Wednesday 10 February 2010 Erico Mendonça wrote: > >> I m using a <ask> dialog on my autoyast file to ask the user for the > >> desired profile. However, it will go into a loop (ask the same > >> information again) when it's reloaded by autoyast. > > > > why? has your chosen profile the same ask-list again? > > Oops. You're right. :) > > Anyway, removing a section via XSLT could be useful later on. Do you > have any ideas on that? I dont think you need that very often but here is how you can solve that with xslt. The problem in your xslt file was the missing namespace (I called it "y" here) <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet· xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:y="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" version="1.0"> · <xsl:template match="*|processing-instruction()|comment()"> <xsl:copy> <xsl:copy-of select="@*"/> <xsl:apply-templates/> </xsl:copy> </xsl:template> <xsl:template match="y:ask-list"> </xsl:template> </xsl:stylesheet> -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

11 years, 8 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall February 2010