openSUSE Autoinstall June 2007

autoinstall@lists.opensuse.org

21 participants
22 discussions

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] 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] Password encryption
by Alan Mosca 11 Jul '07

11 Jul '07

Hi, I was wondering if there was a way of changing the encryption algorithm in the user passwords. More specifically I would like to get whatever the root password is in /etc/shadow and put it in autoyast.xml. I don't need to decrypt it. Is there a way of doing this? Regards -- Alan Mosca -- 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] Unfulfilled requirement...but it is uninstallable
by Oliver Schweikert 27 Jun '07

27 Jun '07

Hello all, since updating to SP1 (SLES10) package resolving fails during autoinstall and i get messages like the following at y2log: Unfulfilled requirement '[package] (namedcap) jre >= 1.6.0'. trying different solution Error!>>There are no installable providers of jre >= 1.6.0 for vets-gui-base-3.0-1.1.noarch Important!>>jre-1.6.0-fcs.i586 provides jre == 1.6.0-1, but it is uninstallable. Try installing it on its own for more details. When i install a base system and later that package, all works fine. Why does yast mark the package as uninstallable? Kind regards Oliver Schweikert -- 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] SLES10 SP1 fails to setup aliases
by Frank Steiner 27 Jun '07

27 Jun '07

Hi, when installing SLES10 SP1 with autoyast, a profile like <mail> <aliases config:type="list"> <alias> <alias>root</alias> <comment></comment> <destinations>bioroot@whatever,de</destinations> </alias> </aliases> </mail> results in a /etc/aliases file with this content: rootbioroot(a)whatever.de So all mails sent to root during or after the installation go to the root account of our toplevel domain (which is very bad...). This worked in SLES10. cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

[opensuse-autoinstall] NIC bonding/teaming
by Doctor Who 26 Jun '07

26 Jun '07

On 6/25/07, Michael T. Halligan <michael(a)halligan.org> wrote: > On Jun 25, 2007, at 5:15 PM, Doctor Who wrote: > > > Can NIC bonding/teaming be accomplish using AutoYaST? I imagine this > > would be done with a post-install script. Assuming there were 2 > > 10/100 NICs (normally eth0 & eth1) what might this look like? > > Here's my hack to do this: > > > > > > > <files config:type="list"> > <file> > <file_contents><![CDATA[BOOTPROTO='NONE' > MTU='9000' > NAME='Hewlett-Packard Company NetXtreme BCM5721 Gigabit Ethernet PCI > Express' > STARTMODE='off' > UNIQUE='rBUF.5sChhDFnqQ7' > _nm_name='bus-pci-0000:02:00.0' > ]]></file_contents> > <file_owner>root</file_owner> > <file_path>/etc/sysconfig/network/ifcfg-eth0</file_path> > <file_permissions>644</file_permissions> > </file> > <file> > <file_contents><![CDATA[BOOTPROTO='NONE' > MTU='9000' > NAME='Hewlett-Packard Company NetXtreme BCM5721 Gigabit Ethernet PCI > Express' > STARTMODE='off' > UNIQUE='JNkJ.5sChhDFnqQ7' > _nm_name='bus-pci-0000:03:00.0' > ]]></file_contents> > <file_owner>root</file_owner> > <file_path>/etc/sysconfig/network/ifcfg-eth1</file_path> > <file_permissions>644</file_permissions> > </file> > <file> > <file_contents><![CDATA[STARTMODE='onboot' > BOOTPROTO='static' > IPADDR='10.1.108.51/24' > BONDING_MASTER='yes' > BONDING_SLAVE_0='eth0' # you can use eth0 here, too > BONDING_SLAVE_1='eth1' # or eth1 > BONDING_MODULE_OPTS='mode=1 primary=eth1 arp_interval=1000 > arp_ip_target=+10.1.108.1' # backup mode > ]]></file_contents> > <file_owner>root</file_owner> > <file_path>/etc/sysconfig/network/ifcfg-bond0</file_path> > <file_permissions>644</file_permissions> > </file> > >/files> > Thanks, so this is just inserted into the auto.xml file rather than used as a post-install script? Also, can you resend the text as an attachment as the formatting appears a bit messed up in the body of the message? Thanks again! -- 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] NIC bonding/teaming
by Doctor Who 26 Jun '07

26 Jun '07

Can NIC bonding/teaming be accomplish using AutoYaST? I imagine this would be done with a post-install script. Assuming there were 2 10/100 NICs (normally eth0 & eth1) what might this look like? 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] How to display license agreement when using autoyast
by Harry Hart 16 Jun '07

16 Jun '07

Hello - [Please note: I previously posted this question over at yast-devel(a)opensuse.org, but was advised to re-ask my question in this forum. Please forgive the cross-posting.] Please forgive the very basic question, but I'm hoping someone can suggest a solution. How can I arrange for a license agreement to be displayed during an autoyast install? I have tried the following possibilities, but so far, none seems to work: 1. Turned on <confirm>true</confirm> in the autoyast XML control file. 2. Added a "workflow" and "module" element in the autoyast control file. 3. Added a license.zip file to one of the "add-on products" (This works when adding the "add-on" after installation, but not during auto-install.) 4. Added the yast2-firstboot package to the list of packages to be installed. If I understood how autoyast determines which YCP modules to run (and in what order), then I could try adding my own (to the "root" CRAMFS archive on the installation medium), but so far, I don't understand how to tell autoyast to run an additional new module. (I am using SLES 10, not OpenSUSE.) Any help, pointers, explanation would be much appreciated. Thanks in advance! - Harry -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

[opensuse-autoinstall] Patterns
by Maurice Burrows 15 Jun '07

15 Jun '07

Hey, I have a question that I'm sure someone has encountered before: I find the 'Base Server System' pattern under SLES10 SP1 RC5 rather bloated and would like a somewhat leaner base pattern. How does one include custom patterns for a SLES 10 SP1 install source without YaST/AutoYaST complaining that it can't create the catalog, or that the source was rejected by the user, or could not not set patterns or selections 'patttern-name' ? I've edited /install-src/CD1/suse/setup/descr/directory.yast and patterns to include the new pattern file. I've noticed that /install-src/content has a hash for each pattern within the descr directory, do I need to include my new pattern in this file? How do I create a SHA1 hash for my new pattern that will be accepted by YaST? Do I even need to do this? So many questions.. Help is most appreciated. Cheers --Maurice-- -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall June 2007