- openSUSE Autoinstall

[opensuse-autoinstall] AW: IPv6 and autoyast
by Dirk.Lohmann＠Bertelsmann.de 06 Jun '11

06 Jun '11

Hello, is it possible to use ipv6 with autoyast ? And what is to do ? How is the syntax ? Thank you Mit freundlichen Grüßen Dirk Lohmann NMI-OSV Systemadministrator Linux ----------------------------------------------------------------------- arvato systems GmbH An der Autobahn 33311 Gütersloh Dirk.Lohmann(a)Bertelsmann.de Telefon: +49 (0) 5241 80-5865 Fax: +49 (0) 5241 65865 http://www.arvato-systems.de Geschäftsführung: Dr. Michael Pesch Amtsgericht Gütersloh - HRB 3981 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] opensuse 11.4 pxe installation - no repository in 'iso:/?iso=openSUSE-11.4-DVD-i586.iso&url=nfs://...
by Pierre Girard 27 May '11

27 May '11

Hello, I'm trying to install opensuse 11.4 and so far the machine loads pxe, starts initrd and linux, and starts the installation process. At some point it looks to add repositories and I get an error message saying there was a problem adding a repository. Here's the message from y2log: 2011-03-14 10:56:08 <1> client.example.com(3182) [YCP] Progress.ycp:599 Subprogress initialization skipped 2011-03-14 10:56:08 <3> client.example.com(3182) [YCP] Packages.ycp:1484 No repository in 'iso:/?iso=openSUSE-11.4-DVD-i586.iso&url=nfs://nfsserver.example.com/suse/o…' 2011-03-14 10:56:08 <1> client.example.com(3182) [Pkg] Packages.ycp:1063 Pkg Builtin called: LastError I checked the path, and I was able to manually mount the directory from one of the terminals without problem. Here's part of the pxelinux.cfg/default label workstation11.4-32 kernel linux11.4-32 append initrd=initrd11.4-32 ramdisk_size=65536 insmod=e100 textmode=1 autoyast=nfs://nfsserver.example.com/suse/autoyast-workstation-11.4 install=nfs://nfsserver.example.com/suse/opensuse/distribution/11.4/iso/ope… label manual11.4-32 kernel linux11.4-32 append initrd=initrd11.4-32 ramdisk_size=65536 manual=1 install='nfs://nfsserver.example.com/suse/opensuse/distribution/11.4/iso/openSUSE-11…' For now I'm trying to make the manual installation work. I have the same lines for opensuse 11.3 and 11.2 and those installations work correctly. Any idea what could be the problem? Thank you. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

11 19

[opensuse-autoinstall] post-install reboot
by Swartz, Patrick H 24 May '11

24 May '11

Hi All, We are finally close to our final autoyast.xml configuration, but have a question about forcing one more reboot. One of the last scripts we run is to setup the atomic update partition and cloning, after we do this we need the system to reboot. I have tried just adding a reboot to this script, but that doesn't work - guessing because the script is never "complete" and the system continues to reboot. Patrick Swartz UNIX Planning & Engineering (DSUSSE) First Data 402-777-7337 desk 402-201-1192 Company cell 402-871-8981 Personal cell ----------------------------------------- The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer. -- 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] ssh service
by Gavin Reid 23 May '11

23 May '11

Greetings , i am attempting to have ssh start automatically after the install as finished vi autoyast on opensuse 11.4 however I cannot seem to make it function snipped from my autoyast : <runlevel> <default>3</default> <services config:type="list"> <service> <service_name>sshd</service_name> <service_status>enable</service_status> <service_start>3 5</service_start> <service_stop>3 5</service_stop> </service> </services> </runlevel> where am I going wrong ? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 6

[opensuse-autoinstall] relurl with SLES11 SP1
by Vladimir Ondrus 23 May '11

23 May '11

Hello, I have similar problem to http://lists.opensuse.org/opensuse-autoinstall/2010-10/msg00054.html. I am also using SLES11 SP1 Is relurl working with SLES11 SP1, or will work only with SLES11 SP2? I have this in autoyast.xml: <add-on> <add_on_products config:type="list"> <listentry> <media_url>relurl:///</media_url> <product>SuSE-Linux-Updates</product> <product_dir>updates</product_dir> <name>MyUpdates</name>  </listentry> </add_on_products> </add-on> here is my update repository: sles11sp1:/autoinst/ins_rep # l total 176 drwxr-xr-x 7 root root 4096 May 23 22:43 ./ drwxr-xr-x 7 root root 4096 May 23 22:19 ../ -rw-r--r-- 1 root root 9218 May 23 22:18 autoinst_noraid.xml -rw-r--r-- 1 root root 12006 May 23 22:18 autoinst_raid.xml -rw-r--r-- 1 root root 5314 May 23 22:43 autoinst_simple.xml dr-xr-xr-x 3 root root 4096 May 20 2010 boot/ -rw-r--r-- 1 root root 14457 May 23 22:19 content -rw-r--r-- 1 root root 197 May 23 22:19 content.asc -rw-r--r-- 1 root root 1710 May 23 22:19 content.key -r--r--r-- 1 root root 55168 May 12 2010 control.xml -r--r--r-- 1 root root 877 May 20 2010 gpg-pubkey-0dfb3188-41ed929b.asc -r--r--r-- 1 root root 1032 May 20 2010 gpg-pubkey-1d061a62-4bd70bfa.asc -r--r--r-- 1 root root 613 May 20 2010 gpg-pubkey-307e3d54-4be01a65.asc -r--r--r-- 1 root root 1694 May 20 2010 gpg-pubkey-3d25d3d9-36e12d04.asc -r--r--r-- 1 root root 938 May 20 2010 gpg-pubkey-7e2e3b05-4be037ca.asc -r--r--r-- 1 root root 1698 May 20 2010 gpg-pubkey-9c800aca-4be01999.asc -r--r--r-- 1 root root 1803 May 20 2010 gpg-pubkey-a1912208-446a0899.asc -r--r--r-- 1 root root 1348 May 20 2010 gpg-pubkey-b37b98a9-4be01a1a.asc drwxr-xr-x 2 root root 4096 May 23 19:19 media.1/ drwxr-xr-x 6 root root 4096 May 23 19:16 suse/ drwxr-xr-x 4 root root 4096 May 23 19:38 updates/ drwxr-xr-x 2 root root 4096 May 23 19:33 yast/ sles11sp1:/autoinst/ins_rep # find updates/ updates/ updates/SHA1SUMS updates/suse updates/suse/noarch ... updates/suse/noarch/SHA1SUMS updates/suse/setup updates/suse/setup/descr updates/suse/setup/descr/SHA1SUMS updates/suse/setup/descr/packages.en updates/suse/setup/descr/packages updates/suse/setup/descr/directory.yast updates/suse/setup/descr/packages.DU updates/directory.yast updates/media.1 updates/media.1/products updates/media.1/SHA1SUMS updates/media.1/media updates/media.1/directory.yast updates/content But when installing from this repository I have this in y2log: 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [YCP] clients/add-on_auto.ycp:20 ---------------------------------------- 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [YCP] clients/add-on_auto.ycp:21 add-on auto started 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] clients/add-on_auto.ycp:170 Pkg Builtin called: SourceCreate 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] PkgProgress.cc(_receiver):96 PkgReceiver progress: 0 (0%), running: true 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] Source_Create.cc(createManagedSource):174 Original URL: relurl:///, product directory: ./updates 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] Source_Create.cc(createManagedSource):180 Alias from URL: '' 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] PkgFunctions.cc(CreateRepoManager):242 Path to repository files: /etc/zypp/repos.d 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] RepoManager.cc(init_knownRepositories):546 start construct known repos 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] RepoManager.cc(init_knownRepositories):567 end construct known repos 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] Source_Create.cc(createManagedSource):215 Probing source type: 'relurl:///updates' 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] PkgFunctions.cc(CreateRepoManager):242 Path to repository files: /etc/zypp/repos.d 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] RepoManager.cc(init_knownRepositories):546 start construct known repos 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] RepoManager.cc(init_knownRepositories):567 end construct known repos 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] RepoManager.cc(probe):1176 going to probe the repo type at relurl:///updates () 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp++] MediaSetAccess.cc(rewriteUrl):385 Rewriting url relurl:///updates 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] MediaAccess.cc(open):110 Trying scheme 'relurl' 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 MediaAccess.cc(open):153 THROW: MediaAccess.cc(open):153: Unsupported URI schem e in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 RepoManager.cc(probe):1208 CAUGHT: MediaAccess.cc(open):153: Unsupported URI sch eme in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp++] RepoManager.cc(probe):1209 problem checking for repodata/repomd.xml file 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp++] MediaSetAccess.cc(rewriteUrl):385 Rewriting url relurl:///updates 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] MediaAccess.cc(open):110 Trying scheme 'relurl' 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 MediaAccess.cc(open):153 THROW: MediaAccess.cc(open):153: Unsupported URI schem e in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 RepoManager.cc(probe):1224 CAUGHT: MediaAccess.cc(open):153: Unsupported URI sch eme in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp++] RepoManager.cc(probe):1225 problem checking for content file 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] MediaAccess.cc(open):110 Trying scheme 'relurl' 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 MediaAccess.cc(open):153 THROW: MediaAccess.cc(open):153: Unsupported URI schem e in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp++] MediaSetAccess.cc(release):424 Releasing all media IDs held by this MediaSetAccess 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 RepoManager.cc(probe):1244 CAUGHT: MediaAccess.cc(open):153: Unsupported URI sch eme in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 RepoManager.cc(probe):1248 THROW: RepoManager.cc(probe):1248: Unknown error rea ding from 'relurl:///updates' 2011-05-23 16:44:34 <3> 219.1.90.86(3481) [Pkg] Source_Create.cc(SourceCreateEx):731 SourceCreate for 'relurl:///' product './updates' has failed 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] PkgProgress.cc(_receiver):96 PkgReceiver progress: 0 (0%), running: true 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] PkgProgress.cc(Done):84 Evaluating ProcessDone callback... 2011-05-23 16:44:34 <3> 219.1.90.86(3481) [YCP] Report.ycp:472 Failed to add add-on product. 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [ui] YPushButton.cc(setFunctionKey):183 Guessing button role YOKButton for YPushButton "OK" at 0x34fe800 from f unction key F10 (END) Why relurl is not working? Regards, Vladimir Ondrus -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] complete documentation
by Vladimir Ondrus 23 May '11

23 May '11

Hello, Where can I find a complete list of elements, which are possible inside networking section: I know that static ip address can be configured this way: <networking> <interfaces config:type="list"> <interface> <ipaddr>219.1.90.100</ipaddr> <netmask>255.255.255.128</netmask> </interface> But its not described in: http://www.suse.com/~ug/autoyast_doc/CreateProfile.Network.html Is there a link to old style autoyast documentation? Regards, Vladimir Ondrus -- 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] ask-list for specific network interface
by Swartz, Patrick H 18 May '11

18 May '11

Hello, I am trying to convert our SLES10 ask-list to work with SLES11sp1. However, the option to set the primary ethernet device has changed or doesn't work. Here is what worked in SLES10 <ask-list config:type="list"> <ask> <path>networking,dns,hostname</path> <question>Enter Hostname (server name)</question> <stage>initial</stage> <default>enter your hostname here</default> </ask> <ask> <path>networking,interfaces,interface,device</path> <question>Enter the primary ethernet device:</question> <stage>initial</stage> <default>eth-id-</default> </ask> <ask> <path>networking,interfaces,interface,ipaddr</path> <question>Enter the primary IP Address:</question> <stage>initial</stage> <default>127.0.0.1</default> </ask> <ask> <path>networking,interfaces,interface,netmask</path> <question>Enter the Netmask Address:</question> <stage>initial</stage> <default>255.255.255.0</default> </ask> <ask> <path>networking,routing,routes,0,gateway</path> <question>Enter the primary Gateway Address:</question> <stage>initial</stage> <default>10.112.0.1</default> </ask> </ask-list> And the device entry would be in the format of "eth-id-00-50-56-95-01-0f" so that the rest of our ask-list sections that set the IP and gateway would use that specific MAC address. The reason this is important is that the servers we setup will have 4 - 6 network interfaces and 2 could be active during the install (not on the same network). The <keep_install_network config:type="boolean">true</keep_install_network> works, but we can not guarantee that the interface that the system finds during install will be the one that we need set. Also, I would like to be able to "ask" for the primary and back up network information during install. I have tried using the <listentry> sections but can not find the right combinations nor documentation. Here is the <listentry> I have so far... <listentry> <default>172.16.163.223</default> <path>networking,interfaces,0,ipaddr</path> <question>Enter Server IP address:</question> <stage>initial</stage> <title>IP Address</title> </listentry> <listentry> <default>255.255.255.0</default> <path>networking,interfaces,0,netmask</path> <question>Enter subnet mask:</question> <stage>initial</stage> <title>Enter Subnet Mask:</title> </listentry> <listentry> <default>172.16.163.1</default> <path>networking,routing,0,gateway</path> <question>Enter default gateway address:</question> <stage>initial</stage> <title>IP Address</title> </listentry> I'm expecting it has something to do with the <path> section --- <path>networking,interfaces,0,ipaddr</path> where the # would be the specific interface, but that hasn't proven to be the case so far. Okay, enough ramblings.... Any help would be greatly appreciated. Patrick Patrick Swartz UNIX Planning & Engineering (DSUSSE) First Data 402-777-7337 desk 402-201-1192 Company cell 402-871-8981 Personal cell ----------------------------------------- The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 7

[opensuse-autoinstall] <forceboot> + <kernel> installs wrong kernel for stage2
by Joschi Brauchle 13 May '11

13 May '11

Hi everyone, I have the following problem with an AutoYast installation of Opensuse 11.4: Some of my machine hang when Yast tries to start the installed kernel via the kexec command (original problem), thus I decided to put ------ <general> <mode> <forceboot config:type="boolean">true</forceboot> </mode> </general> ------ in my XML file. This forces Yast to reboot the machine after the first installation stage. So far so good (circumventing the original problem). Now I decided to install the default instead of the desktop kernel, because these are headless machines for scientific simulations, this I don't need the desktop optimizations of the desktop-kernel. Thus I put ------ <software>  <kernel>kernel-default</kernel> </software> ------ in the XML file. But now, when I install these machines with Autoyast, I hangs during the reboot after stage one (second and bigger problem)!! The error message is some what like "mount: unknown filesystem type 'ext4' -- could not mount root filesystem" when the kernel tries to mount the root partition (formatted with ext4). I diagnosed the problem somewhat and discovered that although I want the default kernel to be used, Yast installs and tries to boot the DESKTOP kernel for stage 2 of the installation process. This does not work, because only the modules for the DEFAULT kernel were installed before, thus the desktop kernel cannot find the ext4 module (or whatever it need to mount ext4). I have made some screenshots of the GRUB menu when the stage2 process is started and it shows as the first entry "Desktop -- openSUSE 11.4 - ..." and this is what it tries to boot. Only the third option is "openSUSE 11.4", which looks like the default kernel... Did anybody ever experience this problem? Uwe: should I create a bugreport about this? I have taken some screenshots of the boot process of stage 2 with the exact error message if needed, but I think the problem should become clear without them! Best regards, Joschi -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 6

[opensuse-autoinstall] RE: How to fetch scripts from outside profile file (was: AutoYast script location)
by Sivaraju, Sravan (ext) 02 May '11

02 May '11

SGVsbG8gRXZlcnlvbmUsDQogDQpJIGFtIHRyeWluZyB0byBmZXRjaCB0aGUgY2hyb290LCBwb3N0IGFuZCBpbml0IHNjcmlwdHMgZnJvbSB0aGUgY2QgaW5zdGVhZCBvZiBkaXJlY3RseSBpbmNsdWRpbmcgdGhlbSBpbiB0aGUgcHJvZmlsZSBmaWxlLg0KV2UgYXJlIHVzaW5nIFNMRVMtMTAtU1AxDQogDQpJIGhhdmUgdXNlZCBiZWxvdyBzdHJ1Y3R1cmUgaW4gdGhlIHByb2ZpbGUgZmlsZToNCiANCiA8c2NyaXB0cz4NCiAgICAgICAgPGNocm9vdC1zY3JpcHRzIGNvbmZpZzp0eXBlPSJsaXN0Ij4NCiAgICAgICAgICAgPHNjcmlwdD4NCiAgICAgICAgICAgICAgICA8Y2hyb290ZWQgY29uZmlnOnR5cGU9ImJvb2xlYW4iPnRydWU8L2Nocm9vdGVkPg0KICAgICAgICAgICAgICAgIDxpbnRlcnByZXRlcj5zaGVsbDwvaW50ZXJwcmV0ZXI+DQogICAgICAgICAgICAgICAgPGZpbGVuYW1lPmJwX2Nocm9vdGVkLnNoPC9maWxlbmFtZT4NCiAgICAgICAgICAgICAgICA8bG9jYXRpb24+ZmlsZTovLy9hdXRveWFzdC9icF9jaHJvb3RlZC5zaDwvbG9jYXRpb24+DQogICAgICAgICAgIDwvc2NyaXB0Pg0KICAgICAgICA8L2Nocm9vdC1zY3JpcHRzPg0KICAgICAgICA8cG9zdC1zY3JpcHRzIGNvbmZpZzp0eXBlPSJsaXN0Ij4NCiAgICAgICAgICAgPHNjcmlwdD4NCiAgICAgICAgICAgICAgICA8ZmlsZW5hbWU+YnBfcG9zdC5zaDwvZmlsZW5hbWU+DQogICAgICAgICAgICAgICAgPGludGVycHJldGVyPnNoZWxsPC9pbnRlcnByZXRlcj4NCiAgICAgICAgICAgICAgICA8bG9jYXRpb24+ZmlsZTovLy9hdXRveWFzdC9icF9wb3N0LnNoPC9sb2NhdGlvbj4NCiAgICAgICAgICAgPC9zY3JpcHQ+DQogICAgICAgIDwvcG9zdC1zY3JpcHRzPg0KICAgICAgICA8aW5pdC1zY3JpcHRzIGNvbmZpZzp0eXBlPSJsaXN0Ij4NCiAgICAgICAgICAgPHNjcmlwdD4NCiAgICAgICAgICAgICAgPGZpbGVuYW1lPmJwX2luaXQuc2g8L2ZpbGVuYW1lPg0KICAgICAgICAgICAgICA8aW50ZXJwcmV0ZXI+c2hlbGw8L2ludGVycHJldGVyPg0KICAgICAgICAgICAgICA8bG9jYXRpb24+ZmlsZTovLy9hdXRveWFzdC9icF9pbml0LnNoPC9sb2NhdGlvbj4NCiAgICAgICAgICAgPC9zY3JpcHQ+DQogICAgICAgIDwvaW5pdC1zY3JpcHRzPg0KICA8L3NjcmlwdHM+DQoNCiANCkJ1dCwgaSBhbSBnZXR0aW5nIGJlbG93IGVycm9yIGluIHRoZSB5MmxvZy0xLCB5MmxvZyBhbmQgdGhlIHNjcmlwdHMgYXJlIG5vdCBiZWluZyBleGVjdXRlZCBpbiB0aGVpciByZXNwZWN0aXZlIHN0YWdlcy4NCiANCiANCiANCjIwMTEtMDQtMjkgMTM6MDM6MzMgPDE+IDEwLjk5LjIuMSgzMzcxKSBbWUNQXSBBdXRvaW5zdFNjcmlwdHMueWNwOjQ4NCBXcml0aW5nIGNocm9vdCBzY3JpcHQgaW50byAvbW50L3Zhci9hZG0vYXV0b2luc3RhbGwvc2NyaXB0cy9icF9jaHJvb3RlZC5zaA0KMjAxMS0wNC0yOSAxMzowMzozMyA8MT4gMTAuOTkuMi4xKDMzNzEpIFthZ2VudC1zeXN0ZW1dIFN5c3RlbUFnZW50LmNjKEV4ZWN1dGUpOjEwOTggbWtkaXIgL3RtcC9ZYVNUMi0wMzM3MS1QQnNTT28vdG1wX21vdW50DQoyMDExLTA0LTI5IDEzOjAzOjMzIDwxPiAxMC45OS4yLjEoMzM3MSkgW1lDUF0gYXV0b2luc3RhbGwvaW8ueWNwOjExOSBDb3B5IHByb2ZpbGU6IGNwIC9hdXRveWFzdC9icF9jaHJvb3RlZC5zaCAvbW50L3Zhci9hZG0vYXV0b2luc3RhbGwvc2NyaXB0cy9icF9jaHJvb3RlZC5zaA0KMjAxMS0wNC0yOSAxMzowMzozMyA8MT4gMTAuOTkuMi4xKDMzNzEpIFtZQ1BdIGF1dG9pbnN0YWxsL2lvLnljcDoxMzEgVHJ5aW5nIHRvIGZpbmQgZmlsZSBvbiBpbnN0YWxsYXRpb24gbWVkaWE6IGNkDQoyMDExLTA0LTI5IDEzOjAzOjM2IDwxPiAxMC45OS4yLjEoMzM3MSkgW1lDUF0gYXV0b2luc3RhbGwvaW8ueWNwOjE0NSBDb3B5IHByb2ZpbGU6IGNwIC90bXAvWWFTVDItMDMzNzEtUEJzU09vL3RtcF9tb3VudC8vYXV0b3lhc3QvYnBfY2hyb290ZWQuc2ggL21udC92YXIvYWRtL2F1dG9pbnN0YWxsL3NjcmlwdHMvYnBfY2hyb290ZWQuc2gNCjIwMTEtMDQtMjkgMTM6MDM6MzYgPDM+IDEwLjk5LjIuMSgzMzcxKSBbWUNQXSBBdXRvaW5zdFNjcmlwdHMueWNwOjQ4OSBzY3JpcHQgZmlsZTovLy9hdXRveWFzdC9icF9jaHJvb3RlZC5zaCA8ZmlsZTovLy9hdXRveWFzdC9icF9jaHJvb3RlZC5zaD4gIGNvdWxkIG5vdCBiZSByZXRyaWV2ZWQNCiANCiANCiANCjIwMTEtMDQtMjkgMTM6MTE6MTcgPDE+IHNldHVwKDQwOTkpIFtZQ1BdIEF1dG9pbnN0U2NyaXB0cy55Y3A6NTAyIFdyaXRpbmcgIHNjcmlwdCBpbnRvIC92YXIvYWRtL2F1dG9pbnN0YWxsL3NjcmlwdHMvYnBfcG9zdC5zaA0KMjAxMS0wNC0yOSAxMzoxMToxNyA8MT4gc2V0dXAoNDA5OSkgW2FnZW50LXN5c3RlbV0gU3lzdGVtQWdlbnQuY2MoRXhlY3V0ZSk6MTA5OCBta2RpciAvdG1wL1lhU1QyLTA0MDk5LVNyNm9iWS90bXBfbW91bnQNCjIwMTEtMDQtMjkgMTM6MTE6MTcgPDE+IHNldHVwKDQwOTkpIFtZQ1BdIGF1dG9pbnN0YWxsL2lvLnljcDoxMTkgQ29weSBwcm9maWxlOiBjcCAvYXV0b3lhc3QvYnBfcG9zdC5zaCAvdmFyL2FkbS9hdXRvaW5zdGFsbC9zY3JpcHRzL2JwX3Bvc3Quc2gNCjIwMTEtMDQtMjkgMTM6MTE6MTcgPDM+IHNldHVwKDQwOTkpIFtiYXNoXSBTaGVsbENvbW1hbmQuY2Moc2hlbGxjb21tYW5kKTo3OCBjcDogQXVmcnVmIHZvbiBzdGF0IGbDg8K8ciDDouKCrMW+L2F1dG95YXN0L2JwX3Bvc3Quc2jDouKCrMWTIG5pY2h0IG3Dg8K2Z2xpY2g6IERhdGVpIG9kZXIgVmVyemVpY2huaXMgbmljaHQgZ2VmdW5kZW4NCjIwMTEtMDQtMjkgMTM6MTE6MTcgPDE+IHNldHVwKDQwOTkpIFtZQ1BdIGF1dG9pbnN0YWxsL2lvLnljcDoxMzEgVHJ5aW5nIHRvIGZpbmQgZmlsZSBvbiBpbnN0YWxsYXRpb24gbWVkaWE6IGNkDQoyMDExLTA0LTI5IDEzOjExOjE5IDwxPiBzZXR1cCg0MDk5KSBbWUNQXSBhdXRvaW5zdGFsbC9pby55Y3A6MTQ1IENvcHkgcHJvZmlsZTogY3AgL3RtcC9ZYVNUMi0wNDA5OS1TcjZvYlkvdG1wX21vdW50Ly9hdXRveWFzdC9icF9wb3N0LnNoIC92YXIvYWRtL2F1dG9pbnN0YWxsL3NjcmlwdHMvYnBfcG9zdC5zaA0KMjAxMS0wNC0yOSAxMzoxMToxOSA8Mz4gc2V0dXAoNDA5OSkgW2Jhc2hdIFNoZWxsQ29tbWFuZC5jYyhzaGVsbGNvbW1hbmQpOjc4IGNwOiBBdWZydWYgdm9uIHN0YXQgZsODwrxyIMOi4oKsxb4vdG1wL1lhU1QyLTA0MDk5LVNyNm9iWS90bXBfbW91bnQvL2F1dG95YXN0L2JwX3Bvc3Quc2jDouKCrMWTIG5pY2h0IG3Dg8K2Z2xpY2g6IERhdGVpIG9kZXIgVmVyemVpY2huaXMgbmljaHQgZ2VmdW5kZW4NCjIwMTEtMDQtMjkgMTM6MTE6MTkgPDM+IHNldHVwKDQwOTkpIFtZQ1BdIEF1dG9pbnN0U2NyaXB0cy55Y3A6NTA3IHNjcmlwdCBmaWxlOi8vL2F1dG95YXN0L2JwX3Bvc3Quc2ggPGZpbGU6Ly8vYXV0b3lhc3QvYnBfcG9zdC5zaD4gIGNvdWxkIG5vdCBiZSByZXRyaWV2ZWQNCiANCiANCg0KMjAxMS0wNC0yOSAxMzoxMToxOSA8MT4gc2V0dXAoNDA5OSkgW1lDUF0gQXV0b2luc3RTY3JpcHRzLnljcDo1NDggU2NyaXB0IEV4ZWN1dGlvbiBjb21tYW5kOiAvYmluL3NoIC14IC92YXIvYWRtL2F1dG9pbnN0YWxsL3NjcmlwdHMvYnBfcG9zdC5zaCAyJj4gL3Zhci9hZG0vYXV0b2luc3RhbGwvbG9ncy9icF9wb3N0LnNoLmxvZyANCjIwMTEtMDQtMjkgMTM6MTE6MTkgPDE+IHNldHVwKDQwOTkpIFtZQ1BdIEF1dG9pbnN0U2NyaXB0cy55Y3A6NDY1IFdyaXRpbmcgaW5pdCBzY3JpcHQgaW50byAvdmFyL2FkbS9hdXRvaW5zdGFsbC9pbml0LmQvYnBfaW5pdC5zaA0KMjAxMS0wNC0yOSAxMzoxMToxOSA8MT4gc2V0dXAoNDA5OSkgW2FnZW50LXN5c3RlbV0gU3lzdGVtQWdlbnQuY2MoRXhlY3V0ZSk6MTA5OCBta2RpciAvdG1wL1lhU1QyLTA0MDk5LVNyNm9iWS90bXBfbW91bnQNCjIwMTEtMDQtMjkgMTM6MTE6MTkgPDE+IHNldHVwKDQwOTkpIFtZQ1BdIGF1dG9pbnN0YWxsL2lvLnljcDoxMTkgQ29weSBwcm9maWxlOiBjcCAvYXV0b3lhc3QvYnBfaW5pdC5zaCAvdmFyL2FkbS9hdXRvaW5zdGFsbC9pbml0LmQvYnBfaW5pdC5zaA0KMjAxMS0wNC0yOSAxMzoxMToxOSA8Mz4gc2V0dXAoNDA5OSkgW2Jhc2hdIFNoZWxsQ29tbWFuZC5jYyhzaGVsbGNvbW1hbmQpOjc4IGNwOiBBdWZydWYgdm9uIHN0YXQgZsODwrxyIMOi4oKsxb4vYXV0b3lhc3QvYnBfaW5pdC5zaMOi4oKsxZMgbmljaHQgbcODwrZnbGljaDogRGF0ZWkgb2RlciBWZXJ6ZWljaG5pcyBuaWNodCBnZWZ1bmRlbg0KMjAxMS0wNC0yOSAxMzoxMToxOSA8MT4gc2V0dXAoNDA5OSkgW1lDUF0gYXV0b2luc3RhbGwvaW8ueWNwOjEzMSBUcnlpbmcgdG8gZmluZCBmaWxlIG9uIGluc3RhbGxhdGlvbiBtZWRpYTogY2QNCjIwMTEtMDQtMjkgMTM6MTE6MjAgPDE+IHNldHVwKDQwOTkpIFtZQ1BdIGF1dG9pbnN0YWxsL2lvLnljcDoxNDUgQ29weSBwcm9maWxlOiBjcCAvdG1wL1lhU1QyLTA0MDk5LVNyNm9iWS90bXBfbW91bnQvL2F1dG95YXN0L2JwX2luaXQuc2ggL3Zhci9hZG0vYXV0b2luc3RhbGwvaW5pdC5kL2JwX2luaXQuc2gNCjIwMTEtMDQtMjkgMTM6MTE6MjAgPDM+IHNldHVwKDQwOTkpIFtiYXNoXSBTaGVsbENvbW1hbmQuY2Moc2hlbGxjb21tYW5kKTo3OCBjcDogQXVmcnVmIHZvbiBzdGF0IGbDg8K8ciDDouKCrMW+L3RtcC9ZYVNUMi0wNDA5OS1TcjZvYlkvdG1wX21vdW50Ly9hdXRveWFzdC9icF9pbml0LnNow6LigqzFkyBuaWNodCBtw4PCtmdsaWNoOiBEYXRlaSBvZGVyIFZlcnplaWNobmlzIG5pY2h0IGdlZnVuZGVuDQoyMDExLTA0LTI5IDEzOjExOjIwIDwzPiBzZXR1cCg0MDk5KSBbWUNQXSBBdXRvaW5zdFNjcmlwdHMueWNwOjQ3MSBzY3JpcHQgZmlsZTovLy9hdXRveWFzdC9icF9pbml0LnNoIDxmaWxlOi8vL2F1dG95YXN0L2JwX2luaXQuc2g+ICBjb3VsZCBub3QgYmUgcmV0cmlldmVkDQogDQogDQpXaXRoIGJlc3QgcmVnYXJkcywNClNyYXZhbg0K-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.orgFor additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 4

[opensuse-autoinstall] chroot-scripts on SLES
by Erico Mendonça 29 Apr '11

29 Apr '11

Hi there... I need to run some scripts after the partitions are formatted on SLES 11SP1. I tried "chroot-scripts", but it's not being executed at all. Is there a known limitation for SLES11 SP1? The other types of scripts are being executed just fine (pre, post, init scripts). -- -- Erico -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 7