August 2008 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] add-on repository aliases
by Peter Bowen 14 Aug '08

14 Aug '08

On openSUSE 11.0, I have some rpm-md repos from the openSUSE Build Service as add-ons in my AutoYaST control file. <add-on> <add_on_products config:type="list"> <listentry> <media_url>nfs://172.30.0.1/inst/build-service/system_management/openSUSE_11.0</media_url> <product>System:Management</product> <ask_on_error config:type="boolean">true</ask_on_error> <signature-handling> <accept_non_trusted_gpg_key> <all config:type="boolean">false</all> <keys config:type="list"> <keyid>8EA7CA44C6411BD2</keyid> </keys> </accept_non_trusted_gpg_key> <import_gpg_key> <all config:type="boolean">false</all> <keys config:type="list"> <keyid>8EA7CA44C6411BD2</keyid> </keys> </import_gpg_key> </signature-handling> </listentry> </add_on_products> </add-on> Everything works great, except the resulting repos in zypper are called "openSUSE_11.0". Is there a way to specify the repo alias used by zypper in AutoYaST? Thanks. Peter -- 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] autoyast complete configuration files?
by pierre.girard＠gerad.ca 14 Aug '08

14 Aug '08

Hello, i was trying to setup some printers and i have some PPD files for them that aren't included in opensuse so i went in autoyast and created a new "complete configuration file" and loaded the PPD file into it. In the "File path" i typed the complete file name and i filled the owner and permissions (root:root and 644). After the installation is complete when i go to the directory where the file should be it isn't there. Is there a way to debug this without reinstalling each time? Thanks for your help. -- 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] How to have ZMD running at the time I have a post script being called
by Alan Mosca 05 Aug '08

05 Aug '08

Hi, I have an install with a post script that needs to run some commands using 'rug' (mainly to add repositories and do some logging of the status of the machine and what's available on it). The problem is that I keep getting "ERROR: ZMD does not appear to be running." in the log. I have attached the xml for the script (it's quite a long script and I don't want to bother you with it - if I run it alone it works). Does anyone have any suggestions on how to get zmd up before this is run? -------- <scripts> <post-scripts config:type="list"> <script> <debug config:type="boolean">false</debug> <feedback config:type="boolean">false</feedback> <filename>setupcluster.pl</filename> <interpreter>perl</interpreter> <network_needed config:type="boolean">false</network_needed> <source><![CDATA[#!/usr/bin/perl #(script removed) ]]></source> </script> </post-scripts> </scripts> ---------- Thank you all! Alan Mosca -- 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] How to bypass AutoYaST license WITHOUT removing the license from the media?
by Richard Hefner 04 Aug '08

04 Aug '08

Hi all - We have an environment where we loop mount (read-only, of course) our SuSE media and do not have the option of removing the license.zip (or the entries in the directory.yast file) to bypass the license agreements upon an auto installation with AutoYaST. Is there any other possible way to do this? I don't really care if it's just a hack to get it working.. We just need something. =20 One method I've been trying is using a pre-install script: for each system, I customize an initrd for it and throw a modified control.xml (control.xml.bak) file into it, along with an info file and an autoyast.xml file. I was thinking that it could be possible to run a pre-install script that copies the modified control.xml.bak file (the one with the license module(s) commented out) to the "real" control.xml file. The only problem with this approach that I've seen is that yast needs to re-read the modified control.xml file, as if the pre-install script does this, I have errors with my partitioning plan. Is there any way to invoke a re-read of this file without killing yast and restarting? If not, what's the best way to accomplish a reload of yast without exiting the installation? The only answers I've seen on this list is to remove the license files from the media. Or, one method that I've seen that works is to leave the license files on the media but comment out (or remove) the section for the license modules in the control.xml file. Hopefully there's a way to do this? Thank you for your time! -Richard Hefner -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 10