June 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

sgnature-handling
by Lars Stavholm 13 Jun '06

13 Jun '06

The signature-handling override for additional packages as specified in the autoyast doco section 4.5.4 doesn't work for me. I specify all four items (accept_unsigned_file, accept_file_without_checksum, accept_verification_failed, and accept_unknown_gpg_key) as "true" in my autoinst.xml in hope of avoiding the confirmation prompt. The confirmation prompt still appears. Anyone? R /Lars Stavholm

2 6

Custom CDs & autoinst.xml
by Don Coffin 13 Jun '06

13 Jun '06

I'm building custom installation CDs for SLES9, and I'd like them to autoinstall. I've created an autoinst.xml file per the docs at: http://www.suse.com/~ug/autoyast_doc/index.html In section 7.2.2 ("Booting From CD-ROM"), there's this tempting sentence: "It is also possible to create customized CD-ROMs to hold only the package you need in addition to the control file which also can be saved on the CD-ROM." I've got an "install server" environment setup already, although I don't plan on doing any network installs. Instead, I hope to create custom installation ISOs using cd-creator. My question is this: where do you place the autoinst.xml file in the installation tree for creating install ISOs? In the top level of the first SLES9 CD? Any pointers are greatly appreciated. Thanks much!

3 3

Re: [suse-autoinstall] adding online_update without /etc/youservers
by Darin Perusich 13 Jun '06

13 Jun '06

Stanislav Visnovsky wrote: >> when i used --type=YUM to add the source 'rug up' worked. > > But I was trying to point out to use --type=zypp ;-) ahh, i will give it a try shortly. >> the next question that i've been pondering over is what happens when SuSE >> 10.2 becomes available, am i going to have to remove this source and add >> another? > > --type=YUM does not sync the source to YaST. Thus, after the upgrade to 10.2, > YaST will not see the source, only ZMD/rug/zen-updater will. If you use > --type=zypp, the source will survive the upgrade. but i don't want this source to survive because it's specificly for 10.1 updates. >> this is what was nice about /etc/youservers, one only needed to >> provide the url to the base of the update tree. > > I'm sorry, I don't know how /etc/youservers worked :( cat /etc/youservers # This file is read by the YaST Online Update (YOU) to build the list of # servers used for getting updates. It may contain URLs to the base # directories where an update tree is located. # # Examples: # #ftp://ftp.suse.com/pub/suse #cd:/// #dir:///var/lib/YaST2/you/mnt http://my.local.repot/pub/suse YOU would then figure out where it needed to get the updates from. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 darinper(a)cognigencorp.com

1 0

Re: [suse-autoinstall] adding online_update without /etc/youservers
by Darin Perusich 13 Jun '06

13 Jun '06

stano, Stanislav Visnovsky wrote: > > Rug type 'nu' is for Novell Updates exclusively. Use --type=zypp to > add your own YUM or SUSEtags sources. There is also a rug type 'yum', > but if you use 'zypp', the source will be propagated to YaST as well, > so you will get support in both YaST and ZMD stacks. when i used --type=YUM to add the source 'rug up' worked. the next question that i've been pondering over is what happens when SuSE 10.2 becomes available, am i going to have to remove this source and add another? this is what was nice about /etc/youservers, one only needed to provide the url to the base of the update tree. -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 darinper(a)cognigencorp.com

1 0

Network Installation nightmares
by Francois Uldry 13 Jun '06

13 Jun '06

Hello, This is driving me nuts, I am trying to get a simple Network Installation Server (over NFS) to work. What I have done : - Through the control centre, on a SLES 9 SP3, used the control panel to create a SLES Network Installation Image as documented, used the SLES 9 original CDs as delivered by Novell. Added the SP 3 CDs to the tree. - Configured DHCP and TFTP to allow network boot. (that works perfectly fine) I have : /install/SLES9, which is the root of the exported filesystem. My problem : - Booting from the network, Yast cannot find package description. Has anyone had that much trouble just getting to a network installation server ? Any help, question, idea welcome ! Best regards, François

1 0

RE: [suse-autoinstall] xmllint
by fraser_bailey＠agilent.com 13 Jun '06

13 Jun '06

Absolutely not. The DTDs have not been correct since I started using SLES about 3+ years ago. I suspect they aren't tested. I don't think yast always generates a valid autoyast xml file either. I've always had to edit mine until autoyast will read it back in again without error. -----Original Message----- From: Lars Stavholm [mailto:stava@telcotec.se] Sent: Tuesday, June 13, 2006 7:27 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] xmllint For sake of completeness I try to validate my autoinst.xml on SuSE Linux 10.1 using "xmllint --noout --validate autoinst.xml". Loads of errors are displayed. But the basis of my autoinst.xml is produced by autoyast by means of cloning (Create Reference Profil). Q: Is this supposed to work? I.e. are the DTD's up-to-date? R /Lars -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 2

How can I configure a static ip address of network adpapter
by Zhan Xiang 13 Jun '06

13 Jun '06

Hi, I have a question about network configuration(maybe quite simple). I want to set a static ip address for the adpater which was used to install SLES10. But there maybe more than one adpaters in node, and I cannot confirm what adapter was used to do installation before installing. I even probably cannot know the MAC address of the installing adpater, since the node can be identified by its UUID, instead of a MAC address. If I use a chroot-script to set the ip address after installation, the ip address will be reset by autoyast after creating boot loader. So I'd like to add some information in autoyast profile to config them. Thank you. Walkinmud _________________________________________________________________ 享用世界上最大的电子邮件系统― MSN Hotmail。 http://www.hotmail.com

2 1

adding online_update without /etc/youservers
by Darin Perusich 12 Jun '06

12 Jun '06

now that YOU has been replaced with libzypp there is no longer the /etc/youservers for specifying your list of servers. is there an equivalent to the /etc/youservers file? -- Darin Perusich Unix Systems Administrator Cognigen Corporation 395 Youngs Rd. Williamsville, NY 14221 darinper(a)cognigencorp.com

3 4

additional rpms
by Lars Stavholm 11 Jun '06

11 Jun '06

I've added my own rpms following Uwe's instructions... create_update_source.sh myInstSrc cp my rpm's into myInstSrc/updates/suse/ cd myInstSrc/updates/suse create_package_descr cd setup/descr ls > directory.yast echo 'http://install/suse/...' > myInstSrc/add_on_products ...and it all works just great. Doing a manual (network) install, I can find my added rpms (using Search) and the select them to be installed as needed. Doing an automated install over the network, with my rpm's specified explicitly in the autoinst.xml file, my added rpm's gets installed as well. However, I wonder if there's any way one can add a selection like "MyAddons" using a "MyAddons.sel" file as was the case in previous versions of autoyast? Reason being that when doing a manual install, I would like to have a selection "MyAddons" already on the first page so the user doesn't have to worry about the exact rpm's that is contained in that selection (the way all the other selections work, like Min, Minimal+X11, etc.). Another reason is that this is what my users are used to from our SuSE 9.3 days. Anyone? R /Lars Stavholm

1 1

network configuration not applied
by Dejan Muhamedagic 09 Jun '06

09 Jun '06

Hello, After successful (more or less) auto installation, the resulting network configuration on the target hosts consists of what was defined for netdevice in linuxrc and not what was configured in the autoyast XML file. The configuration is definitely good and autoyast reports no errors. Is linuxrc wrong place to specify the network interface configuration for installation? Should one try with the info file? This is on SLES9 SP3. Boot is from a CD, but the sources and autoyast files are accessed over HTTP. BTW, I tried similar static network configuration, but with network boot using DHCP/PXE/tftp and the resulting network config was fine. Cheers, Dejan

2 2