September 2007 - openSUSE Autoinstall - openSUSE Mailing Lists

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?
by Matt Gillard 05 Mar '08

05 Mar '08

I dont have kinternet installed. This is what doesnt seem to work: <software> <patterns config:type="list"> <pattern>default</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> </patterns> <packages config:type="list"> <packages>perl-libwww-perl</packages> <packages>net-snmp</packages> <packages>kernel-source</packages> </packages> <remove-packages config:type="list"> <packages>pptp</packages> <packages>smpppd</packages> <packages>ppp</packages> <packages>wvdial</packages> <packages>mutt</packages> </remove-packages> </software> In y2log it mentions that those packages should be removed, but it goes ahead and installs them anyway. I can do it manually on the command line: # rpm -e pptp smpppd ppp wvdial mutt and that works fine so I know I have no dependency problems. matt > -----Original Message----- > From: Uwe Gansert [mailto:ug@suse.de] > Sent: Friday, 30 June 2006 12:50 AM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] SLES 10 RC2 remove-packages section? > > > On Thursday 29 June 2006 16:45, Manfred Hollstein wrote: > > > If that fails, you have kinternet installed; add that to > the list and it > > should work. > > good point. > <remove-packages> can not break dependencies and so it's very > likely that > there is still a package that needs those packages. > I did a very small installation with no X - so it worked for me. > > -- > ciao, Uwe Gansert > > Uwe Gansert, Server Technologies Team > SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany > Fax: +49-(0)911-74053-476, Web: http://www.suse.de/~ug > now playing Covenant - Wasteland > > -- > 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 6

[opensuse-autoinstall] is it possible to install latest SLES 10 SP1 patches during autoinstall?
by Chris Partridge 19 Nov '07

19 Nov '07

I am using SLES 10 SP1 and AutoYaST. I have my autoyast profile setup to configure Novell Customer Center with the correct registration code and I verified that my server gets registered with NCC. Now I'd like to have AutoYaST install all the latest patches at the appropriate place during auto-installation. Is this possible? Thanks, Chris -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

6 5

[opensuse-autoinstall] apache configuration with sles10 sp1
by Rich 16 Nov '07

16 Nov '07

we are trying to use same autoyast profile created for sles10 for sles10sp1. after solving some minor kernel and nfs issues, an interesting problem with apache has popped up. after autoinstallation process has finished, default-server.conf is empty (0 size). if i now remove apache, then install it again, the file is correctly created. is there some change in autoyast profile needed (i have searched archives, but found nothing), or is there a problem with autoinstallation process ? -- Rich -- 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] autoyast from command line/shell ?
by abhijit 09 Oct '07

09 Oct '07

hi, i am trying to build a multi-distro installer (loaded via pxe) and want to invoke autoyast from command line/shell passing the autoinst.xml file to drive the install. i have the following questions: 0. is this possible? because i've always seen autoyast being invoked via "linuxrc". looking up linuxrc source it seems quite a fair bit of setup needs to be done before invoking autoyast. i dont (and cannot use) "linuxrc" as my "init" program. 1. if its possible, is there a doc or link that describes the environment (files/directory structure/shell-vars etc.) that needs to be setup before invoking autoyast? 2. what should the command line look for the invocation: something like: # yast ??? if all this is already mentioned in some document, i'd be more than glad to go thru it. link please? thanks a lot in advance s. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 7

[opensuse-autoinstall] anyone know the YCL that executes prescripts?
by John Willis 01 Oct '07

01 Oct '07

I'm looking to study the source code for the installer that runs prescripts. [ Suse 9/ Sles 9] Specifically I was wondering if it checks the exit code or communicates with the prescript through signals or in any other manner. Thanks - john -- 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] Strange problem with creating a modified.xml
by Mike Marion 28 Sep '07

28 Sep '07

What does "Can't detect Profile Version" usually indicate? >From y2log.. === 2007-02-28 01:27:04 <1> 10.42.37.174(3375) [YCP] AutoinstScripts.ycp:545 Script Execution command: /bin/sh /tmp/YaST2-03375-S80cIe/pre-scripts/pre.sh 2&> /tmp/YaST2-03375-S80cIe/pre-scripts/logs/pre.sh.log 2007-02-28 01:27:04 <1> 10.42.37.174(3375) [YCP] XML.ycp:113 Reading /tmp/profile/modified.xml 2007-02-28 01:27:04 <1> 10.42.37.174(3375) [agent-xml] XmlAgent.cc(Read):758 Setting XML generic error handler 2007-02-28 01:27:04 <1> 10.42.37.174(3375) [agent-xml] XmlAgent.cc(Read):793 Freeing generic XML error handler 2007-02-28 01:27:04 <1> 10.42.37.174(3375) [YCP] Profile.ycp:167 importing profile 2007-02-28 01:27:04 <1> 10.42.37.174(3375) [YCP] Profile.ycp:149 Can't detect Profile Version === The bizarre thing is that I'm trying to use a pre.sh script to replace some lines in the profile, writing it out as /tmp/profile/modified.xml and this fails. But, if I take exactly that modified.xml file (scp'd off via the console) and feed that back into the same host again on a new attempt at installing, I get the above error, but the autoinst.xml (which should be invalid too since it's identical[*]) works fine. This makes no sense... why would it reject modified.xml but work just fine as the fallback? Is there something in the parsing of modified.xml that is a little more strict I might be missing? [*]there are differences in a couple of the scripts, the parsing I'm doing removes the backslashes that I used i some sed commands, so I double backslash them. This doesn't effect the profile itself though. A diff shows that the autoinst.xml (which works) vs the modified.xml (which is rejected) are the same, other then the backslashes inside the scripts CDATA blocks. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Grandpa: "Quick! We have to kill the boy!" Marge: "How'd you know he's a vampire?" Grandpa: "He's a vampire?!? Ahhh...." [runs away] ==> Simpsons -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 9

[opensuse-autoinstall] "Error while configuring partitions. Try again"
by Alan McKay 27 Sep '07

27 Sep '07

Hi folks, Google brought me to you. I see 2 other people have reported this problem but I don't see exactly the variant I have here. I have just downloaded Opensuse 10.2 for x86_64 and after my first installation I clicked the box to have it save the configuration for Autoyast. Then I booted the new system and retrieved the file, and stuck it on my install server, where the contents of the DVD are as well. Note that the only change I made to the file was something I found also with Google about editing the specifics on the ethernet card and changing it to "eth0" from the default which includes the MAC. I made no change to HD configuration. Then to initiate the install I boot the first CD from Opensuse 10.2, and select the "Installation" option. Then in the "append" space below I enter my "install=http://blah/blah autoyast=http://blah/blah" It chugs along fine. If it matters, my network does not have DHCP so it fails the first time, then comes back with a prompt so I can manually enter network info. After entering the info it takes 3 or 4 retries for the network to come up. Then Autoyast seems to chug right along. Until it gets to the disk partition. Below is that section of the XML file. Note I do not see a size of "max" anywhere there. That seemed to be the problem for someone else who reported this. Note the partitioning is precisely what Yast came up with on it's own for the first installation. thanks, -Alan <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <label>/boot</label> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>131571712</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <label>/</label> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>4293596160</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <label>/recovery</label> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>1077511168</size> </partition> <partition> <partition_id config:type="integer">5</partition_id> <partition_nr config:type="integer">4</partition_nr> <size>244496447488</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <label>SWAP-hda5</label> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>1077479424</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">6</partition_nr> <size>21476173824</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">7</partition_nr> <size>21476173824</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">8</partition_nr> <size>200466491392</size> </partition> </partitions> <use>all</use> </drive> </partitioning> -- "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 10

[opensuse-autoinstall] autoyast 10.2 manual partitioning
by Yogesh Bhanu 27 Sep '07

27 Sep '07

Hi , I have 20 workstations with 10 different disks from 30 GB - 300 GB disks. Some have more than one disk and some have Windows partitions too. Some also have LVMs. here is the my disk partioning setup of my test auotyast file which works great except for I would like to have the ability to choose manual disk partitioning. Is this possible. What should be modified here in the sample file. <partitioning config:type="list"> <drive> <initialize config:type="boolean">false</initialize> </drive> </partitioning> Thanks in advance -- 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] Re: CD Creator fix
by kAlym 27 Sep '07

27 Sep '07

Hello, I am currently trying to generate a custom CD on SLES 10 but CD Creator does not copy packages I selected. I first tried package patterns but only 61 packages were copied. Then I tried individual packages... same problem. I noticed this problem has been reported in August 2006. Has this issue been fixed ? How to update my system ? (No online package source is configured in YaST) -- kAlym -- 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] 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