October 2009 - 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] OT: Centralized patch management for OpenSuse 11.x
by Ivan De Masi 14 Jan '11

14 Jan '11

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

3 3

[opensuse-autoinstall] Adding packages to profile triggers error message
by Isaac Hailperin 07 Nov '10

07 Nov '10

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

3 2

[opensuse-autoinstall] general rules question
by dutchguy69 26 Jul '10

26 Jul '10

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

3 5

[opensuse-autoinstall] Problems with rules in openSUSE 11.2 (milestone7)
by Werner Hack 27 Nov '09

27 Nov '09

Hello, I tried to install openSUSE 11.2 (milestone7) via autoyast for testing purpose. I am using the rules feature to create a profile dynamically. I have no problems within former openSUSE releases. But in openSUSE 11.2 it fails. 'xsltproc' is missing here (for merging the profiles) ! Is this problem already known? autoyast is not working yet. Is there a bugfix available or even a workaround to solve this problem? This will be great. At the moment I can not test autoinstallation in release 11.2. Regards, Werner Hack --

5 9

[opensuse-autoinstall] Feature request _ask_ for rules/class merging
by Martin Vogt 24 Nov '09

24 Nov '09

Hello, I would like to have the following feature: on the server I have some templates("rules") for different partitioning,software etc. But I like the user who installs the system to select these rules (instead of the automatic matching) During Autoyast, before the installation starts, a window should appear which shows all rules by Name and the user then clicks the rulenames which he wants to be applied to the autoyast.xml file. I know that there are "rules/classes" already and its possible to add <ask> dialogs during autoinstall. But I think its not possible to merge rules with an ask statement. regards, Martin -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 7

[opensuse-autoinstall] autoyast log files
by Simon Loewenthal/NL/Tele2 02 Nov '09

02 Nov '09

Dear all, Just a quick question: Once a system is installed via autoyast, does it leave a log file of what was done and what failed afterwards. I had a look in /root but saw nothing obvious. Does it log on the server? Regards, S -- Simon Loewenthal/Tele2 GSM: +31 6 2000 5427 [ -d . ] || echo 'Oh!' ******** IMPORTANT NOTICE ******** This e-mail (including any attachments) may contain information that is confidential or otherwise protected from disclosure and it is intended only for the addressees. If you are not the intended recipient, please note that any copying, distribution or other use of information contained in this e-mail (and its attachments) is not allowed. If you have received this e-mail in error, kindly notify us immediately by telephone or e-mail and delete the message (including any attachments) from your system. Please note that e-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be subject of unauthorized interception or other interference without the knowledge of sender or recipient. Tele2 only send and receive e-mails on the basis that Tele2 is not responsible for any such computer viruses, corruption or other interference or any consequences thereof. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

5 10

[opensuse-autoinstall] Location for image installation with autoyast
by Leonardo L. P. da Mata 02 Nov '09

02 Nov '09

This is another test that i'm doing, i'd like to use this feature: <software> <image> <script_location>http://10.10.0.162/image.sh</script_location> <run_kickoff config:type="boolean">true</run_kickoff> </image> </software> http://ugansert.blogspot.com/2009/03/imagine-autoyast.html But i'd like to store both the script and the image that will be used in the installation on the media DVD, the script_location tag may have device://<cdrom_device>/image.sh parameter?? How do i identify what's my dvdrom drive inside these scripts? Thanks -- Leonardo Luiz Padovani da Mata barroca(a)gmail.com "May the force be with you, always" "Nerd Pride... eu tenho. Voce tem?" -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 8

[opensuse-autoinstall] Script to merge profiles server side
by Winther, Hinrich 28 Oct '09

28 Oct '09

Hi, I had some difficulties with the way AutoYaST merges xml files. So I wrote a little python script that merges the files in a way that I could better understand. The actual merging is done on a server who delivers the final profile xml file. I specifically had the problem that I wanted to have multiple class files that contain a files section which gave me a headache. To cut a long story short I guess one or the other has similar difficulties which is why I publish my script. You can find the documentation and the source here: http://www.students.uni-mainz.de/winther/pyAutoyast/ Sincerely, Hinrich Winther.-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] Incorporate dud/driverdisk into initrd issue
by Jung Wilhelm 28 Oct '09

28 Oct '09

Though there is someone point out that "dud=http://......" or something alike is not supported by SLES10SP2. But I still want to know that when I remaster a SLES10SP2 DVD that support the new RAID controller on my new server. When I insert a dud(a vfat img file) into initrd(copy from SLES10SP2 DVD), and want linuxrc load this driver update disk by passing a command line parameter like "dud=file:///dd.img",but linuxrc just didn't notice that. I am just wonder it is there any chance to insert a dud into initrd( /boot/i386/loader/initrd), and let linuxrc know that there is a dud to load. I have to do it that way because I have no network around, So anyone can help me to figure it out.Thank you! -- Man kann alles,was Man will. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 7