September 2007 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] using https to fetch xml file
by Johan Hansson 27 Sep '07

27 Sep '07

I'm trying to invoke an installation with SLES10 SP1 and https and can't get it to work. The installation halts while fetching the rules.xml file (no return code or error in the GUI). Changing it to http in the VNC window allows the installation to continue without problem. There is no problem using https on the server and it works from different browsers. Apache log files are silent (ssl-requests). y2log file says standard can't find URL: https://192.168.1.10/media/repository/rules/rules.xml Are there any certificate requirements ( right now I'm just using self signed test certificates )? Or anyone who has any other idea of what could be wrong? relevant parameters in info file autoyast=https://192.168.1.10/media/repository/ install=http://192.168.1.10/media/SLES-10-SP1-x86_64/ loghost=192.168.1.10 As I understand the only thing supported is to fetch the xml files by https not the installation rpm's, is that correct? While using autoyast and loghost parameter on SLES9 SP2 more or less everything was sent to the loghost. Can I activate debug logging on SLES10 SP1 installations? or do I have to locally get the y2log file? Thanks in advance Johan Hansson -- 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] anyway to signal yast installer to re-read install.inf?
by John Willis 26 Sep '07

26 Sep '07

got a situation where it would be very very good to run a pre-script under SLES 9 and modify the /etc/install.inf created by linuxrc during install. problem is yast doesn't seem to re-read the install.inf under SLES 9 SP3 after the pre-script is run, so none of the custom changes are used. does anyone know anything about signaling yast to re-read its install.inf? Thanks! -- 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] any way to embed "install=" into the XML file?
by Alan McKay 26 Sep '07

26 Sep '07

Hey folks, In my Fedora Core / Red Hat kickstart files I can embed the "install" location. Is there any way for me to do this with the SuSe XML file? It will just save me a great deal of typing and eliminate typos. I'd much rather just type in the "autoyast=" line and let the XML file specify where to get it from. I know that I can make a special boot CD that will include all of this, but the problem with that is that every time I issue a new load I have to make a new boot CD to include it as an option. thanks, -Alan -- "Aikido has but one principle - the universal reality of life" - Mitsugi Saotome -- 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] RE: Autoyast can't find packages, patterns
by Tompkins, Joel 21 Sep '07

21 Sep '07

Hi! I'm a newbie to this list. I am trying this list because I have received no response from Novell's own forum for installing SLES10. I have a SLES9 server we use for Autoyast NFS network installs of SLES9 servers. I am trying to set it up with a SLES10 build in the same manner. Everything looks good as far as copying files from the CD isos up to the installation source directory, and the directories look good and mount ok via NFS, but when I try to install via NFS using the boot from a SLES10 DVD, it reaches a point where it stops with a list of the packages we put in the XML profile and says it can't find the packages. After hitting enter, then it says it can't find the patterns. I can see the packages in Suse/i586 and the patterns files in Suse/setup/descr. Both of these places are pointed to in the content file. The path given for the installation source directory is correct. The install server syslog reports repeated authentication for mounts and unmounts for the nfs with no errors. Can someone help me with what I am missing here? Can it somehow be not finding the path or dropping the path? TIA! Joel Tompkins Senior ERP Support ------------------------------------------------------------------------------ This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ============================================================================== "EMF <idahopower.com>" made the previous annotations. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 4

Re: [opensuse-autoinstall] Custom kernel
by Yan Fitterer 14 Sep '07

14 Sep '07

Never tried this for the kernel, but it works for other packages: 1) create a new install source 2) Add it to your list of sources 3) Specify the kernel as per your xml snippet below. To help with 1) you may want to look at: http://developer.novell.com/wiki/index.php/Creating_Add-On_Media_with_YaST Yan >>> On 14/09/2007 at 17:58, in message <33c5a6c30709140958k5217773bj73ebaab3643e3381(a)mail.gmail.com>, "Dan Stromberg" <dstromberglists(a)gmail.com> wrote: > I have a Linus 2.6.21 kernel packaged up as an RPM, modified slightly > to do the grub changes. It's based on a heavily modified > kernel-source*.rpm from openSUSE. > > I'm now trying to get this kernel to be loaded automatically as part > of an autoyast install. > > I dumped the kernel into our RPM repository, but the kernel is not > being loaded for some reason. If I remove the kernel-default, I get a > kernelless install, so I'm pretty sure I've got the right directory of > RPM's. > > When I look at suse/setup/descr/packages, I don't see my kernel > listed. Do I need to run some command to get it added? Does it need > to appear in this file? > > I also tried to add the kernel to the XML controlling the install with: > <software> > <kernel>kernel-2.6.21.7DRSwashere</kernel> > > ...however still no luck. BTW, the actual kernel has "DRS-was-here", > not "DRSwashere" - in some contexts and not others the software seems > to want to strip the dashes. > > What do I need to do to get this kernel loaded and made the default kernel? > > Thanks! -- 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] Custom kernel
by Dan Stromberg 14 Sep '07

14 Sep '07

I have a Linus 2.6.21 kernel packaged up as an RPM, modified slightly to do the grub changes. It's based on a heavily modified kernel-source*.rpm from openSUSE. I'm now trying to get this kernel to be loaded automatically as part of an autoyast install. I dumped the kernel into our RPM repository, but the kernel is not being loaded for some reason. If I remove the kernel-default, I get a kernelless install, so I'm pretty sure I've got the right directory of RPM's. When I look at suse/setup/descr/packages, I don't see my kernel listed. Do I need to run some command to get it added? Does it need to appear in this file? I also tried to add the kernel to the XML controlling the install with: <software> <kernel>kernel-2.6.21.7DRSwashere</kernel> ...however still no luck. BTW, the actual kernel has "DRS-was-here", not "DRSwashere" - in some contexts and not others the software seems to want to strip the dashes. What do I need to do to get this kernel loaded and made the default kernel? Thanks! -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 2

[opensuse-autoinstall] autoyast SLES10 and SLES10sp1 boot loader configuration....
by Cameron Seader 10 Sep '07

10 Sep '07

Greetings, I have two autoinst.xml files one for SLES10 and one for SLES10 SP1, and the boot loader sections are identical other than the labels in the menu.lst. The SLES10 autoinst.xml works great, but the SLES10 SP1 never works right at all. I always have to go in after the system is installed and install grub from there. What changes were made to the bootloader? Is there something that i can do in autoyast to make this work? Thanks, Cameron -- 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] Problem to install grub-0.97-40.x86_64.rpm
by Fabien Chaudier 10 Sep '07

10 Sep '07

Hello, I do the following autoinst.xml file All softwares seem to be installed perfectly, excepted the grub software installation (see picture yast2-001.png) Somebody tell me where is the problem ? PS : I am sorry for my poor english...

1 0

[opensuse-autoinstall] Problems using classes with SLES10
by Michael T. Halligan 03 Sep '07

03 Sep '07

I'm attempting to normalize our library of AutoYaST XML files, and am running into some problems Here's how I'm calling the class in my autoinst.xml file : <classes config:type="list"> <class> <class_name>Database</class_name> <configuration>Files.xml</configuration> <configuration>Software.xml</configuration> </class> </classes> Here's the file in classes/Database : <software> <packages config:type="list"> <package>findutils-locate</package> <package>perl-Net-SNMP</package> <package>rcs</package> <package>seccheck</package> <package>net-snmp</package> <package>freetype2-devel</package> <package>openssl-devel</package> <package>freetype2</package> <package>freetype2-devel</package> <package>xorg-x11-devel</package> <package>fontconfig-devel</package> <package>libmcrypt</package> <package>gd-devel</package> <package>libpng-devel</package> <package>compat-curl2</package> <package>curl</package> <package>curl-devel</package> </packages> <patterns config:type="list"> <pattern>base</pattern> <pattern>Basis-Devel</pattern> </patterns> </software> Here's the error I get on the console when attempting to install with this: Software.xml:2: namespace error : Namespace prefix config for type on packages is not defined <packages config:type="list"> ^ Soft.xml:21: namespace error : Namespace prefix config for type on patterns is not defined <patterns config:type="list"> ^ What am I doing wrong here? I followed Uwe's documentation verbatim. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 9