openSUSE Autoinstall July 2006

autoinstall@lists.opensuse.org

36 participants
54 discussions

Problem with Printer setup
by GUNREBEN, PETER (Peter) 17 Jul '06

17 Jul '06

Hi, my autoinstallation of SuSE 10.1 interrupts with an error message stating the the CUPS server could not be contacted. However, if I finish the installation I can setup the printers with yast2 in the same way as I did it in the autoyast configurator and do not face any problems. Here's the y2log snippet: 2006-07-11 18:47:12 <1> felix11(3831) [YCP] clients/inst_autoconfigure.ycp:96 current resource: printer 2006-07-11 18:47:12 <1> felix11(3831) [YCP] clients/inst_autoconfigure.ycp:107 Writing configuration for printer 2006-07-11 18:47:12 <1> felix11(3831) [YCP] clients/inst_autoconfigure.ycp:134 Calling auto client with: $["cups_installation":`server, "default":"default", "printcap":[$["ff":false, "info":"Canon iR2200", "location":"1-G327", "manufacturer":"Canon", "model":" imageRunner 330s", "name":"default", "nick":"Canon imageRunner 330s Foomatic/ljet4 (recommended)", "ppd_options":[$["key":"HalftoningAlgorithm", "value":"Standard"], $["key":"InputSlot", "value":"Default"], $["key":"PageSize", "value":"A4"], $["key":"Resolution", "value":"600x600dpi"]], "raw":false, "uri":"lpd://GE1884COFPS2/dexx100418prtca08"], $["ff":false, "info":"Xeroc Document Center CS50", "location":"1-G327", "manufacturer":"Xerox", "model":" DocuPrint C55", "name":"color", "nick":"Xerox DocuPrint C55 Foomatic/Postscript (recommended)", "ppd_options":[$["key":"Duplex", "value":"None"], $["key":"PageSize", "value":"A4"], $["key":"PreFilter", "value":"No"], $["key":"Resolution", "value":"default"]], "raw":false, "uri":"lpd://GE1884COFPS2/CC58404C1"]], "spooler":"cups"] 2006-07-11 18:47:12 <1> felix11(3831) [YCP] clients/inst_autoconfigure.ycp:38 current step: 27 2006-07-11 18:47:12 <2> felix11(3831) [Parser] printer/misc.ycp:729 Warning: find(...) is deprecated, please fix 2006-07-11 18:47:12 <2> felix11(3831) [Parser] printer/misc.ycp:729 Warning: find(...) is deprecated, please fix 2006-07-11 18:47:12 <2> felix11(3831) [Parser] printer/misc.ycp:729 Warning: find(...) is deprecated, please fix 2006-07-11 18:47:12 <1> felix11(3831) [wfm] Y2CCWFM.cc(createInLevel):153 Parsing finished 2006-07-11 18:47:12 <1> felix11(3831) [Interpreter] printer/dialogs.ycp:333 Calling YaST client printer_auto (arguments: ["Write"]) 2006-07-11 18:47:12 <1> felix11(3831) [YCP] Printer.ycp:1411 Write called; spooler: cups, cups inst type: `server 2006-07-11 18:47:12 <1> felix11(3831) [YCP] Printer.ycp:1419 Daemon will run for this configuration: true 2006-07-11 18:47:13 <1> felix11(3831) [YCP] CUPS.ycp:219 CUPS settings read: $["BrowseAllow":["@LOCAL"], "BrowseDeny":["All"], "Group":["lp"], "LogLevel":["info"], "Port":["631"], "Printcap":["/etc/printcap"], "RunAsUser":["Yes"], "User":["lp"]] 2006-07-11 18:47:13 <1> felix11(3831) [YCP] CUPS.ycp:220 CUPS permissions read: $["/":$["Allow":["127.0.0.1", "127.0.0.2", "@LOCAL"], "Deny":["All"], "Order":["Deny,Allow"]], "/admin":$["Allow":["127.0.0.1"], "AuthClass":["Group"], "AuthGroupName":["sys"], "AuthType":["BasicDigest"], "Deny":["All"], "Order":["Deny,Allow"]]] 2006-07-11 18:47:13 <1> felix11(3831) [YCP] CUPS.ycp:256 CUPS settings writing success: true 2006-07-11 18:47:13 <3> felix11(3831) [agent-cups] PrintersConf.cc(readSettings):32 PrintersConf::getPrinters failed 2006-07-11 18:47:13 <3> felix11(3831) [agent-cups] CupsCalls.cc(setPrinter):53 Error while contacting CUPS server occured. 2006-07-12 12:48:34 <3> felix11(3831) [agent-cups] PrintersConf.cc(readSettings):32 PrintersConf::getPrinters failed 2006-07-12 12:48:34 <3> felix11(3831) [agent-cups] CupsCalls.cc(setPrinter):53 Error while contacting CUPS server occured. 2006-07-12 12:48:40 <3> felix11(3831) [agent-cups] CupsCalls.cc(setDefaultDest):473 Error while contacting CUPS server occured and the .xml snippet <printer> <cups_installation config:type="symbol">server</cups_installation> <default>default</default> <printcap config:type="list"> <printcap_entry> <ff config:type="boolean">false</ff> <info>Canon iR2200</info> <location>1-G327</location> <manufacturer>Canon</manufacturer> <model> imageRunner 330s</model> <name>default</name> <nick>Canon imageRunner 330s Foomatic/ljet4 (recommended)</nick> <options config:type="list"/> <ppd_options config:type="list"> <ppd_option> <key>HalftoningAlgorithm</key> <value>Standard</value> </ppd_option> <ppd_option> <key>InputSlot</key> <value>Default</value> </ppd_option> <ppd_option> <key>PageSize</key> <value>A4</value> </ppd_option> <ppd_option> <key>Resolution</key> <value>600x600dpi</value> </ppd_option> </ppd_options> <raw config:type="boolean">false</raw> <uri>lpd://GE1884COFPS2/dexx100418prtca08</uri> </printcap_entry> <printcap_entry> <ff config:type="boolean">false</ff> <info>Xeroc Document Center CS50</info> <location>1-G327</location> <manufacturer>Xerox</manufacturer> <model> DocuPrint C55</model> <name>color</name> <nick>Xerox DocuPrint C55 Foomatic/Postscript (recommended)</nick> <options config:type="list"/> <ppd_options config:type="list"> <ppd_option> <key>Duplex</key> <value>None</value> </ppd_option> <ppd_option> <key>PageSize</key> <value>A4</value> </ppd_option> <ppd_option> <key>PreFilter</key> <value>No</value> </ppd_option> <ppd_option> <key>Resolution</key> <value>default</value> </ppd_option> </ppd_options> <raw config:type="boolean">false</raw> <uri>lpd://GE1884COFPS2/CC58404C1</uri> </printcap_entry> </printcap> <server_hostname></server_hostname> <spooler>cups</spooler> </printer>

2 1

Custom Add-On Source twice in Installation Sources
by Goetz Rieger 13 Jul '06

13 Jul '06

Hi, I do autoinstalls using an HTTP source and packages from a custom add-on source. After installation the entry for the add-on exists twice in YaST2 Installation Sources. Not that this is doing any harm, I just wonder why. Cheers, Goetz

2 1

SLED10: Install Older Package Version
by Goetz Rieger 12 Jul '06

12 Jul '06

Hi guys, I would like to install an older version of a package (actually it's the Groupwise client) then the one included on the SLED10 DVD. So I created an add-on source with the older RPM and added the add-on to the control file. Naturally now the autoinstall installs the newest version. I can think of some ways to get the older version installed but I really want to do it the proper way (TM). So I will stay away from trying to delete the newer version from the DVD package database or the like. Now, what is the proper way? ;-)) Thanks in advance, Goetz

2 2

post install scripts with prompts
by Simon Crute 12 Jul '06

12 Jul '06

Hi, I'm trying to install some RPMs during the post install script using rug (the ati drivers) However, they require the agreement to a license agreement. Has anyone figured out a way of agreeing to this automatically ? -- Simon Crute IS&T Bracknell Novell UK Ltd

1 0

URL encoding in rules.xml
by Luzian Scherrer 11 Jul '06

11 Jul '06

Hi there, This URL part from rules.xml ... <result> <profile>controlfiles/getcontrolfile.xml?mac=@mac@</profile> <continue config:type="boolean">true</continue> </result> ... gets converted to controlfiles/getcontrolfile.xml%3fmac%3d... from (as far as I understand) SuSE 10.1 on. This conversion did not happen in earlier versions. In my opinion this is wrong; users should be able to add parameters using the http-get syntax in rules.xml. Is this fact already known and if so, is it considered a feature or will it be changed? Thanks, -Luzian

3 3

Integrating patches in 10.1
by Beat Rubischon 11 Jul '06

11 Jul '06

Hello! I'm still fighting against Autoyast to get fresh installed SuSE 10.1 systems containing all recent patches. Before the libzypp update I was able to add an local copy of the update directory using "rug service-add" and "rug subscribe -a" - A "rug update" did then the job. Since the libzypp update [1] this approach is no longer possible as the update does not install. I need to use YaST in an unscripteable way. An approach like in 10.0 using the command line "online_update -u nfs://192.0.1.1/export/suse/updates -V -l en" is also not possible as this binarie does no longer exist. [1] http://lists.suse.com/archive/suse-security-announce/2006-Jun/0004.html My next try was to integrate the updates into the installsource. I found several more or less usable postings in this mailinglist - the only way it works is to get a local mirror of the current updates and integrate them into the installsource using create_update_source.sh [2] and create_package_descr [3]. I followed the instructions in the scripts and added a add_on_products in the install directory as described in the FAQ [4]. [2] http://www.suse.com/~ug/tools/create_update_source.sh [3] http://www.suse.com/~ug/tools/create_package_descr [4] http://www.suse.com/~ug/AutoYaST_FAQ.html#b9 To avoid the dialog about unsigned packages, I added the needed statements to my autoyast file: <general> <signature-handling> <accept_unsigned_file config:type="boolean">true</accept_unsigned_file> <accept_file_without_checksum config:type="boolean">true</accept_file_without_checksum> </signature-handling> </general> I even patched my installsource using the root image updater [5] - I followed the instruction that the utility must be run on a x86_64 system to provide an update for those architecture. The YaST logfile shows that the configuration entrys are parsed - but the dialog [6] still appears :-( [5] http://lists.suse.com/archive/suse-autoinstall/2006-Jun/0109.html [6] http://www.0x1b.ch/~beat/autoyast.png Any other solution? Delivering systems to a customer without patches is quite often a security problem and It does not make a good impression when the customer needs to run YaST twice with a reboot between it and download half a Gig of patches - on the other hand, we need a way to integrate those patches without user intervention. SLES10 - when finished - is only a solution for customers who are willing to pay the license... Beat Rubischon -- Beat Rubischon <beat.rubischon(a)dalco.ch> DALCO AG, Industriestrasse 28, 8604 Volketswil

2 2

Howto export the package-selection in 10.1
by Guido Kölsch 11 Jul '06

11 Jul '06

Hi, i have to migrate from SuSE 9.3 to 10.1 and i want to use the old package-selection from 9.3. I want to upgrade one old 9.3 to 10.1 so that yast create the new software-selection based on the old selection. This method works from 8.2 to 9.3 but not for 10.1 because in yast there is no function to export the current selection. Is there a different way to keep the old package-selection and migrate it to 10.1? Regards Guido Kölsch -- ------------------------------------------------------------------------ Guido Kölsch -Rechenzentrum- Max-Planck-Institut fuer Radioastronomie Phone: +49 (0)228 525 164 Auf dem Huegel 69, D-53121 Bonn, Germany FAX : +49 (0)228 525 229 email: gkoelsch(a)mpifr-bonn.mpg.de ------------------------------------------------------------------------

1 1

SLES 9.3 geometry and initialize after Windows install
by John Willis 10 Jul '06

10 Jul '06

Hi, I've come across a curious effect and have a solution, but would like some confirmation, or commentary. Symptom: hardware - 32 bit i386 SLES9.3, fibre channel volume using qla2300 hba, devoid of any partition table. Windows 2000 is installed upon it then SLES 9.3 is installed upon it, completely wiping out windows partitions using autoyast and <initialize> true. Installation proceeds for a while then halts with the message "insufficient space to continue". Using ALT+F6 to get to the console, the root partition / is sized to 1.1 GB out of 10 GB where autoyast was told to use <auto> and <max> for the partitions, it should be much larger, a lot of the disk space is unpartitioned. If the SLES 9.3 installation is tried again, it succeeds, and the partitions now use the whole disk. Solution: Looking over /var/log/YaST/y2log, the hardware detect phase seems to detect the drive geometry based on something the Windows 2000 install leaves in the partition table, and makes its calculations based on that. Even if none of the windows partitions are saved, and then the partition table is <re-initialized> with a linux partition table. Using <initialize> true </initialize> causes the problem. Using <initialize> false </initialize> does not cause the problem. Thoughts: browsing the y2log file of a failure and success, it appears the disk geometry is acquired "before" the partition is re-initialized with a linux partition "type" table, in the windows->sles9.3 failure the cyclinders are reported as 1274, in the sles9.3->sles9.3 success they are reported as 9997. They are both correct as the windows type geometry has one set of CHS and the linux type geometry has a different set of CHS. the solution wouldn't bother me except the thought of having no control over the actual disk geometry used by the autoyast installer, is there a way of overriding the hardware detection of disk geometry? or a way of triggering a new disk geometry acquisition after the partition table is initialized and before the partitions are auto-calculated? (I'd guess the right thing would have been for "initialize" to occur before hardware geometry detect.) but i think my preference would be access from a pre-script to modify or provide the values I choose for CHS to the autoyast installer, but I don't know how to access the hardware detect information thats acquired before the pre-script. Would it be in a staging log somewhere? Thanks for any considerations. And I sincerely apologize if this belongs in a developers forum.

2 1

Custom RPMs SLED 10 RC3
by Goetz Rieger 09 Jul '06

09 Jul '06

Hi list, I'm trying to add some custom RPM's to a SLED10 autoinstall using a customized DVD. The basic autoinstall works well. I understand that the simple recreation of the package database and the <package>rpm</package> section in autoinst.xml is not working for this anymore. So I have created a directory in the DVD root with a new tree using the create_update_source.sh script, copied a test RPM there and build the package database. As stated in the docs. And I even disabled the signature check. The add_on_products file in the DVD root looks like dvd:///updates It is not really clear to me how the add-on stuff works. So I did add a <addons config:type="list"> <addon>updates</addon> </addons> to the xml file. It's not working and I will spare the details because I think I am doing something wrong. Do I need to add more to the xml file? Like a selection? The docs are a pretty secretive on this, could someone shine a bit of light on this?. Cheers, Goetz

3 5

RE: [suse-autoinstall] where do I get a usable 10.1 ISO image
by Matt Gillard 07 Jul '06

07 Jul '06

All those files should exist - the ones under x86_64 anyway. What do you see under x86_64 ? Perhaps bad apache config? Bad permissions? > -----Original Message----- > From: Lonni J Friedman [mailto:netllama@gmail.com] > Sent: Thursday, 29 June 2006 8:36 AM > To: Jesus Gonzalez > Cc: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] where do I get a usable 10.1 ISO image > > > On 6/28/06, Jesus Gonzalez <jgjnet(a)gmail.com> wrote: > > 2006/6/27, Lonni J Friedman <netllama(a)gmail.com>: > > > > > I feel like i'm talking to myself on this list. I'm > trying to used > > > autoyast to install suse-10.1, yet all I keep getting are > errors which > > > seem to suggest that I'm not using a valid installation > source. I've > > > tried the DVD image from the opensuse.org website, and also tried > > > pointing directly at a mirror (mirrors.kernel.org). Neither is > > > working. Surely I'm missing something very obvious, yet I can't > > > figure out what. > > > > > > The same autoyast.xml just works for both 10.0 & 9.3. > > > > > > Please, can someone point me to a known good installation > source for > > > 10.1 (x86 & x86_64) that autoyast won't barf at? many thanks. > > > > > > > > Perhaps you are facing the same "signature nightmare" I > found the first time > > I tried this new version. > > > > Try to add the following to your autoyast.xml: > > > > <general> > > <signature-handling> > > <accept_unsigned_file > > config:type="boolean">true</accept_unsigned_file> > > <accept_file_without_checksum > > config:type="boolean">true</accept_file_without_checksum> > > <accept_verification_failed > > config:type="boolean">true</accept_verification_failed> > > <accept_unknown_gpg_key > > config:type="boolean">true</accept_unknown_gpg_key> > > </signature-handling> > > </general> > > Tried this, no luck. I still get the same failure: > Could not set patterns/selections: Basis-Devel, > GNome,Kde,Kde-Desktop,Kernel-devel > > In y2log I see: > Bad media attach point: http://10.31.40.58/distros/suse/os/10.1/x86_64/ If I check the apache server's on 10.31.40.58 error_log I see the following: File does not exist: /storage/distributions/distros/suse/os/10.1/x86_64/media.1/installfiles File does not exist: /storage/distributions/distros/suse/os/10.1/x86_64/media.1/info.txt File does not exist: /storage/distributions/distros/suse/os/10.1/x86_64/part.info File does not exist: /storage/distributions/distros/suse/os/10.1/x86_64/driverupdate Anyone know why yast is looking for those files when they do not exist in the 10.1 installation source? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama(a)gmail.com LlamaLand http://netllama.linux-sxs.org -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.

4 12

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall July 2006