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

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

28 Oct '09

2009/10/28 Uwe Gansert <ug(a)suse.de>: > on Wednesday 28 October 2009 Jung Wilhelm wrote: > >> And another question, if I want to put the autoyast.xml into the initrd, >> Then how can I do to make linuxrc load it. >> Thank you. > > first of all, linuxrc is not loading the autoyast.xml at all - but that's > nitpicking ;) > put it in the inst-sys directory that I described in my previous post and > refer to it as autoyast=file:///... > > -- > 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 > > Thanks for clarifying it. I put the autoyast.xml in the inst-sys with other driver modules stuff. And it appears just under the root of installation system as I expected. It saved my day. : - ) After all, all this technical details has not been documented. So it takes me couples of day to figure it out. Thanks for your kind help! -- Man kann alles,was Man will. -- 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

1 0

[opensuse-autoinstall] How to debug a failed Autoyast install of a Factory-Xen DomU?
by PGNet Dev 27 Oct '09

27 Oct '09

I use Autoyast to install Xen DomUs. Installing an OpenSuse 11.1 DomU, with autoyast= invoked in the DomU's .cfg, works just fine. Installing an OpenSuse Factory DomU, the install launches, and proceeds to some random , late-stage package install (@ ~ 80-90% complete, in each of 4 attempts), then just hangs -- taking the Dom0 with it. All connections are dropped, and a system reboot is required. I'm trying to debug the process. Launching the DomU with, extra = 'linuxrc.debug=1 linuxrc.log=/dev/console linemode=1 textmode=1 xencons=tty vnc=0 edd=off autoyast=nfs://192.168.1.200/home/autoyast.xml install=http://download.opensuse.org/factory/repo/oss?device=eth0 netdevice=eth0 hostip=192.168.1.201/24 gateway=192.168.1.101 nameserver=192.168.1.106' isn't providing any log trace of what the problem might be. At least not that I've been able to see/find @ the xen console, or in any logs @ the Dom0. What/where additional logging can I turn on to track down the failure in the autoyast DomU process? Thanks. -- 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] Missing Checksum(s) for SLES 10.2 CD that's manually created
by Jason Babicka 15 Oct '09

15 Oct '09

I am looking into creating a SLES 10 SP2 ISO that contains both the relevant security updates released by Novell as well as RPM for the products needed by my employers products. Here are the steps that I used to set up a source for creating the ISO image: 1. I copied the contents of the entire SUSE 10 SP2 DVD into /[path_to_dvd_contents]/ 2. I then followed this link < http://www.suse.de/~ug/AutoYaST_FAQ.html#b9> that Uwe Gansert wrote about adding RPMs to an SLES installation source. I will list out the steps for a reference: a. Using version 20060925 of the create_update_source.sh script, I ran the following command: ./create_update_source.sh /[path_to_dvd_contents]/ b. I then copied all of the desired Novell Security Update RPMS along with the RPMs required for my employers product to /[path_to_dvd_contents]/updates/suse/i586/ c. I then ran the following commands from /[path_to_dvd_contents]/isoroot/updates/suse/ (as outlined in create_update_source.sh description from here <http://en.opensuse.org/Inst-source-utils#Short_description_of_the_scripts>) i. create_package_descr -x setup/descr/EXTRA_PROV ii. cd setup/descr iii. create_directory.yast . iv. create_md5sums . d. I then created an add_on_products file in /[path_to_dvd_contents]/ with the location for these add-on products, the contents of the add_on_products file are just "dvd:///updates" 3. I then followed this link <http://www.suse.de/~ug/AutoYaST_FAQ.html#bB> that Uwe Gansert wrote for signing an add-on product with my companies gpg key. I will list out the steps for a reference: a. gpg --export --armor $KEY_ID > /[path_to_dvd_contents]/updates/content.key b. gpg -b --sign --armor /[path_to_dvd_contents]/updates/content c. ls /[path_to_dvd_contents]/updates/ > /[path_to_dvd_contents]/updates/directory.yast d. I then SU in as root to do the following: i. ./unpackInitrd /[path_to_dvd_contents]/boot/i386/loader/initrd ii. cd /tmp/work-initrd iii. gpg --export --armor $KEY_ID > my-key.gpg iv. find . | cpio -H newc -o > /tmp/initrd v. gzip /tmp/initrd vi. mv /tmp/initrd.gz /[path_to_dvd_contents]/boot/i386/loader/initrd 4. At this point I would run the mkisofs command to build the ISO. 5. I then burn the ISO onto a DVD. Now that I have my DVD, I wanted to test this upgrading an existing box that we have that is running SLES 10 SP1. I inserted the DVD and booted from the DVD, I selected Installation and told it to upgrade the existing product. Soon after doing this, the following message box is displayed: ==================================================================================== No Checksum Found Now checksum for file /suse/setup/descr/EXTRA_PROV Was found in the source. This means that the file is part of the signed source, but the list of checksums on this source does not mention this file. Using the file may put the integrity of your system at risk. Use it anyway? ==================================================================================== It will show the same message box for the following files on the dvd: /suse/setup/descr/EXTRA_PROV /suse/setup/descr/packages /suse/setup/descr/packages.de /suse/setup/descr/packages.en I wanted to check /var/log/YaST2/y2log to see if you it could provide any more information. Here is a snippet of what is said: 2009-10-14 16:43:40 <1> linux(3177) [source] SourceImpl.cc(getPossibleCachedMetadataFile):386 File dvd:///updates/suse/setup/descr/EXTRA_PROV has no checksum available. Now, it seems to me that this error could possibly be related to checking md5sums since one of the steps that I performed was using the create_md5sums script. Another thing that I noticed is that two files within the /suse/setup/descr/ directory on the DVD did not get this message: /suse/setup/descr/MD5SUMS /suse/setup/descr/directory.yast I am not really sure where to check further for any more information. So, if anyone on this list would be willing to provide some help I would greatly appreciate it. Thank you in advance for any help you may be able to provide! Thank You, Jason Babicka -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] rules.xml on DVD install
by Jeromy Smith 07 Oct '09

07 Oct '09

I am trying to add my rules to a openSUSE 11.1 DVD installation medium. I need the rules to reside on the DVD instead of an ftp, etc server. I have verified that my rules work when I invoke the install using autoyast= ftp://192.168.1.120/autoyast/11.1/x86_64/ where the rules reside under rules/rules.xml and the profiles are in autoyast/11.1/x86_64/. When I try to copy the files to the DVD, I have problems. It seems to find the rules.xml when I put it on the DVD under /rules. When it comes time to copy the profiles, this is where the problem arises. After the rules have run, I see this in the y2log: [YCP] autoinstall/io.ycp:119 Copy profile: cp /default.xml /tmp/YaST2-03147-PNVUlC/rules/ default.xml [bash] ShellCommand.cc(shellcommand):78 cp: missing destination file operand after '/default.xml' [bash] ShellCommand.cc(shellcommand):78 Try 'cp --help' for more information. [bash] ShellCommand.cc(shellcommand):78 sh: line 1: /tmp/YaST2-03147-PNVUlC/rules/default.xml: No such file or directory Any suggestions on how to fix this? I've already read over the documentation, FAQ, and everything google turned up. I'm pretty desperate at this point. Jeromy -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 6

[opensuse-autoinstall] postinstall script questions
by Simon Loewenthal/NL/Tele2 07 Oct '09

07 Oct '09

Hi, I have some post installation scripts that I would like to call from my generic autoyast.xml file. This involves three related questions : 1) One file reads, # cat ntp.conf.sh <source> <![CDATA[ cp -f /etc/ntp.conf /etc/ntp.conf.original.autoyast cat > /etc/ntp.conf << EOF server 127.127.1.0 fudge 127.127.1.0 stratum 10 driftfile /var/lib/ntp/drift/ntp.drift logfile /var/log/ntp keys /etc/ntp.keys trustedkey 1 requestkey 1 server 10.254.26.3 iburst restrict 10.254.26.2 restrict time.versatel.com EOF chmod 640 /etc/ntp.conf chown root:ntp /etc/ntp.conf ]]> </source> How would I reference this in the autoyast.xml script. 2) I would like to create separate package installation XML files that can be called by autoyast depending on what will be installed. One such file might read: # cat postinstall-squid.xml <software> <packages config:type="list"> <package>squid</package> </software> Where in the autoyast.xml would I call this and how. 3) Finally. if I add the package squid to the list of packages to be installed, then will autoyast install and add the nessecary user, or will I have to add the squid user into the postinstall-squid.xml with something like: <user> <encrypted config:type="boolean">true</encrypted> <fullname>WWW-proxy squid</fullname> <gid>65534</gid> <home>/var/cache/squid</home> <password_settings> <expire></expire> <flag></flag> <inact></inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/false</shell> <uid>31</uid> <user_password>*</user_password> <username>squid</username> </user> Best 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

3 5

Re: [opensuse-autoinstall] postinstall script questions
by Jochen Schaefer 07 Oct '09

07 Oct '09

Hi Simon regarding 1) reference this by a statement like: root /etc/init.d/boot.local 744 regarding 2) solve this with a rule file. Everything is described in Uwes documentation www.suse.de/~ug. Or if you like it more advanced do it with a prescript. regarding 3) normally squid's rpm should ensure creation of squid account. If you need to modify defaults of squid user you can use the -tag. But that has nothing to do with postinstall. Jochen >>> Simon Loewenthal/NL/Tele2 10/07/09 12:56 PM >>> Hi, I have some post installation scripts that I would like to call from my generic autoyast.xml file. This involves three related questions : 1) One file reads, # cat ntp.conf.sh How would I reference this in the autoyast.xml script. 2) I would like to create separate package installation XML files that can be called by autoyast depending on what will be installed. One such file might read: # cat postinstall-squid.xml squid Where in the autoyast.xml would I call this and how. 3) Finally. if I add the package squid to the list of packages to be installed, then will autoyast install and add the nessecary user, or will I have to add the squid user into the postinstall-squid.xml with something like: true WWW-proxy squid 65534 /var/cache/squid 99999 0 7 /bin/false 31 * squid Best 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 -- 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] "SHA1 sum wrong" after modifying control.xom
by Andreas Taschner 06 Oct '09

06 Oct '09

Hi I have created a YaST client module that snaps into the AutoYaST workflow for running displaying the progress of custom scripts (http://www.novell.com/communities/node/8961/) and a part of this game is to modify <instsrc>/control.xml. While this works fine for SLES 10, SLES 11 is more careful. First it gave me an error like this : <instsrc>/control.xml : SHA1 sum wrong. If you really trust your repository, you may continue in an insecure mode. (OK/Back) Hmm ... OK fair enough - naively I entered a new SHA1 sum in <instsrc>/content hoping that would be it. :( Now I get a less friendly popup saying : <instsrc>/content: Invalid signature Aborting installation I see there is a content.key file, but since I don't know the password to it, it guess it is useless to try to generate a new content.asc. Is there any way around this, or do we not want customer's to port their customizations to SLE 11 ? Thanks. Best regards Andreas Taschner -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 4

[opensuse-autoinstall] Classes do not work in 11.1 autoyast installation
by mwani＠fkf.mpg.de 06 Oct '09

06 Oct '09

Hi, I want to use classes in my autoyast installation. With the 'autoyast' parameter I'm loading the xml-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"> <classes config:type="list"> <class> <class_name>default</class_name> <configuration>software.xml</configuration> </class> <class> <class_name>laptop</class_name> <configuration>partitions.xml</configuration> </class> </classes> </profile> I'm booting the client via PXE boot. I can see in the log file of the http server, that the client fetches the xml file. But in contrast the client does not even try to load the class files. I can not see an obvious error in the y2log file. With 10.3 that procedure worked that way. With 11.1 it has broken for me. Any hints are appreciated. thanks, Michael Wanitschek -- 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] Autoinstallation of SLES 10.2 is failing with addition of custom add-on, possibly due to placement of gpg key for custom add-on
by Jason Babicka 03 Oct '09

03 Oct '09

This is my first email to this list, so I will try to include as much information as possible to describe my problem. I am trying to make a custom DVD that includes all of the standard SLES 10.2 files along with an RPM for my companies product. I think that the problem that I am running into is due to not placing the gpg for my companies product in the correct location, but I am not entirely sure at this point. Let me describe what I have done so far and hopefully someone can help me see where I may have gone wrong. Here is what I did to set up the directory for building the iso: 1. I copied the contents of the entire SUSE 10 SP2 DVD into /[path_to_dvd_contents]/isoroot/ 2. I think followed this link < http://www.suse.de/~ug/AutoYaST_FAQ.html#b9> that Uwe Gansert wrote about adding your own RPMs to an SLES installation source a. I used version 20060925 of the create_update_source.sh script b. I copied our owned signed RPM to /[path_to_dvd_contents]/updates/suse/i586/ c. I then ran the following commands from /[path_to_dvd_contents]/isoroot/updates/suse/ (as outlined in create_update_source.sh description from here <http://en.opensuse.org/Inst-source-utils#Short_description_of_the_scripts>) i. create_package_descr -x setup/descr/EXTRA_PROV ii. cd setup/descry iii. create_directory.yast . iv. create_md5sums . d. Opting now to add this installation source to our existing autoinst.xml files, I created an add_on_products file located at /[path_to_dvd_contents]/isoroot/add_on_products i. The contents of this file is just "dvd:///updates" 3. I then followed this link <http://www.suse.de/~ug/AutoYaST_FAQ.html#bB> that Uwe Gansert wrote for signing an add-on product with our gpg key 4. At this point I would run the mkisofs command to build the iso I tested this by installing this custom installation DVD on a VM. Using an existing autoinst.xml file, I began installing on the VM. When it gets to the portion where it tries to configure the software selections, a window is displayed that says: +--------------------------------------------+ | Error occurred while creating the catalog. | | | | +-----------------------------+ | | | dvd:///updates | | | | Source rejected by the user | | | +-----------------------------+ | +--------------------------------------------+ I noticed that when this message was displayed, that it was trying to download from dvd:///updates/content.key which lead me to think that I needed to re-sign our add-on product properly. I followed this link <http://www.suse.de/~ug/AutoYaST_FAQ.html#bB> that Uwe Gansert wrote for signing an add-on product with our gpg key. After completing these steps, I redid step 2c that I listed above and remade the iso. I again tested this by installing this custom installation DVD on a VM. Using the same existing autoinst.xml file, I began installing on the VM. When it gets to the portion where it tries to configure the software selections this time, the following error message is displayed: +----------------------------------------------------------------------------------------------+ | Error | | | | The package resolver run failed. Please check your software section in the autoyast profile. | +----------------------------------------------------------------------------------------------+ Looking at the software section of the autoinst.xml file that I am using looks like this: <software> <patterns config:type="list"> <pattern>base</pattern> <pattern>ha_sles</pattern> </patterns> <packages config:type="list"> <package>emacs</package> <package>[custom_rpm_name]</package> <package>ipsec-tools</package> <package>perl-Net-Daemon</package> <package>perl-XML-RegExp</package> <package>perl-PlRPC</package> <package>perl-Data-ShowTable</package> <package>perl-XML-DOM</package> <package>perl-DBD-mysql</package> <package>perl-DBI</package> </packages> </software> If anyone can provide any suggestions for other things to try or perhaps where I may have gone wrong, I would greatly appreciate it. If you need more information then please let me know. Thank you, Jason Babicka -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3