openSUSE Autoinstall September 2007

autoinstall@lists.opensuse.org

18 participants
19 discussions

by John Willis

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!

8 years, 10 months

RE: [suse-autoinstall] SLES 10 RC2 remove-packages section?

by Matt Gillard

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.

13 years, 7 months

[opensuse-autoinstall] is it possible to install latest SLES 10 SP1 patches during autoinstall?

by Chris Partridge

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

13 years, 11 months

[opensuse-autoinstall] apache configuration with sles10 sp1

by Rich

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

13 years, 11 months

[opensuse-autoinstall] autoyast from command line/shell ?

by abhijit

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

14 years

[opensuse-autoinstall] anyone know the YCL that executes prescripts?

by John Willis

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

14 years

[opensuse-autoinstall] Strange problem with creating a modified.xml

by Mike Marion

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

14 years

[opensuse-autoinstall] "Error while configuring partitions. Try again"

by Alan McKay

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

14 years

[opensuse-autoinstall] autoyast 10.2 manual partitioning

by Yogesh Bhanu

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

14 years

[opensuse-autoinstall] Re: CD Creator fix

by kAlym

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

14 years

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall September 2007