June 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] 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

[opensuse-autoinstall] Installer resolution
by Alan Mosca 15 Jun '07

15 Jun '07

Hi, I was wondering if there was an option to change the screen resolution used in the install process, can anyone help? Thanks. -- Alan Mosca -- 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] Configuring multiple volume groups
by Oliver Schweikert 14 Jun '07

14 Jun '07

Hi list, I have problems to create a working autoyast profile with 2 physical volumes and 2 volume groups. I am using SLES 10 and profile works for one VG. After adding another PV and a VG, yast complains, that it could not create "a logical volume of requested size" an no note has been logged to y2log. Size of disks is large enought available, of course. Here is the partitioning part of my profile: <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>auto</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>auto</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_type>primary</partition_type> <size>1GB</size> </partition> <partition> <lvm_group>system</lvm_group> <mount></mount> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/system</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>usr</lv_name> <mount>/usr</mount> <size>2GB</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>var</lv_name> <mount>/var</mount> <size>2GB</size> <partition> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <lv_name>tmp</lv_name> <mount>/tmp</mount> <size>1GB</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>srv</lv_name> <mount>/srv</mount> <size>5GB</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> <drive> <device>/dev/cciss/c0d1</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <lvm_group>database</lvm_group> <mount></mount> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/database</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiserfs</filesystem> <format config:type="boolean">true</format> <lv_name>oracle</lv_name> <mount>/var/opt/oracle</mount> <size>20GB</size> </partition> </partitions> <pesize>4M</pesize> <use>all</use> </drive> </partitioning> I also tried to use 2 seperate partitioning elements, but the later one overrides all. Also surprising was, that when using an empty partions list for the second volume group, a `pvscan' during installation shows, that both PVs are assigned to the same VG 'system'. Has anybody an idea? Regards Oliver -- Oliver Schweikert Software Development Horiba Europe Automation Division GmbH Zabergäustr. 3 73765 Neuhausen Tel: +49 - (0)7158-933-413 Fax: +49 - (0)7158-933-613 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 6

[opensuse-autoinstall] nfs mount options in info file?
by Jochen Schaefer 13 Jun '07

13 Jun '07

Hi list, how can I specify nfs options in the info file? When installing SLES10-SP1-RC5 via nfs we tried nfs://10.1.6.1/install/sles10-sp1-rc5,fg,nointr,hard,v3,nolock,rsize=32768,wsize=32768,udp,noacl the result in the installation environment was: cat /proc/mounts ... 10.1.6.1:/install/sles10-sp1-rc5 /var/adm/mount/AP_0x00000001 nfs ro,v3,rsize=32768,wsize=32768,soft,nolock,proto=tcp,addr=10.1.6.1 0 0 see the difference: udp changed to tcp and hard to soft So it seems that the parameters given with the above used syntax are partially ignored. Thanks, Jochen -- 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] mount option "notail" in autoyast
by Jung, Jochen 13 Jun '07

13 Jun '07

Hi, I'm trying to mount a reiserfs filesystem with the notail option using autoyast, but it seams to me, autoyast can not handle this option. Here is an example, what my partition definitions in autoyast.xml look like: <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>rootlv</lv_name> <fstopt>defaults,notail</fstopt> <mount>/</mount> <size>500mb</size> </partition> I tried an installation of SLES9. Maybe autoyast just understands the "normal" options, wich could be used along with any filesystem. Has anyone successfully createt a partition with the notail option? With kind regards Jochen Jung > Freudenberg IT > > Freudenberg Hosting KG > Hoehnerweg 2 - 4 > 69469 Weinheim, Germany > County Court Mannheim, HRA 431161 > Phone +49 (0) 62 01 80-82 47 > mailto: jochen.jung(a)freudenberg-it.com > http://www.freudenberg-it.com > -- 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] Problem with local update repository
by Stephens, Bill {PBSG} 13 Jun '07

13 Jun '07

Hi, I'm really scratching my head on this one. I had a working update directory for my SLES10 install tree. I pulled down the current updates from Novell's site, and ran create_package_descr -x setup/descr/EXTRA_PROV. Now when I try to install from my source tree, my script only wants to install 18 packages, instead of the requested packages: <packages config:type="list"> <package>gnome-vfs2-32bit</package> <package>libbonobo-32bit</package> <package>libidl-32bit</package> <package>orbit2-32bit</package> <package>gdbm-32bit</package> <package>gdbm-devel</package> <package>rpm-python</package> <package>python-elementtree</package> <package>python-sqlite</package> <package>python-urlgrabber</package> <package>dbus-python</package> <package>pygobject2</package> <package>yum</package> <package>yum-utils</package> <package>yumex</package> <package>kyum</package> <package>createrepo</package> <package>ed</package> <package>dejavu</package> <package>psmisc</package> <package>findutils-locate</package> <package>yast2-powertweak</package> </packages> <patterns config:type="list"> <pattern>dhcp_dns_server</pattern> <pattern>ccb</pattern> <pattern>apparmor</pattern> <pattern>lamp_server</pattern> <pattern>Basis-Devel</pattern> <pattern>x11</pattern> <pattern>gnome</pattern> <pattern>base</pattern> <pattern>WBEM</pattern> </patterns> Any ideas what I might be missing? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

[opensuse-autoinstall] Autoinstall of all packages...
by Cameron Seader 13 Jun '07

13 Jun '07

Greetings, Red Hat has a way of selecting everything when installing their distribution. Is there a way to do the same thing with SUSE Linux. Anyone have any ideas?? -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] Why getting different setups on identical HW although "CLONING" using autoyast ??
by Elmar Marschke 12 Jun '07

12 Jun '07

Hi, I'm trying to create an exact clone of a machine running openSuSE 10.1. Highest priority is to end up with a pair of machines that have EXACTLY the SAME SOFTWARE PACKAGES installed. These machines are build exactly of the same hardware, shipped from the same vendor on the same day, so there should'nt be a problem (HP Pavilion AMD 64 X2 Dual Core). 1. I did a fresh install on the first machine; and directly after that (without changing anything on that machine)... 2. i created a xml-profile using "yast2 autoyast", choosed "create reference profile" (and did NOT choose or change anything else manually...) and copied this file to a webserver running on a third machine. 3. I started a network installation on the second machine, telling it to use that profile (boot option "autoyast=http://my_ip/my_profile.xml") and to use the same installation source as was used for the first machine (that was a SuSE 10.1 DVD lying around on a samba share of a fourth machine). I expect this to end up with exactly the same software installed on both machines (is this right or do i misunderstand something??); and besides that anything else also be the same (partitioning and so on...). Unfortunately this is not the case. I checked the output of "rpm -qa" of both machines with a perl script i wrote and it reported the following differences: "This exists in machine2.txt only: libgcj-32bit-4.1.0-25 This exists in machine2.txt only: java-1_4_2-gcj-compat-32bit-1.4.2.0-33" I doublechecked this manually; it's true. On the first machine, these packages are not installed, however packages of the same name but without the "32bit" in it are installed (but these are ALSO installed on the second machine). Question 1: Can someone explain me why this is happening? Is there a mistake in my approach? Besides that i got the same problem trying to do the same on some production servers, which are running since a long time. However in those cases the difference is even bigger, there are around 80 packages reported to be installed on just the second machine, which i expected to be an exact clone (also identical hardware and so on). My assumption in this case is that some packages are being installed on the "clone", because an "addon" section like "KDE" is in the profile.xml; while some packages of the "kde" selection were separately removed from the "original" machine after installation (without removing the whole selection "kde"). Could this be the cause? Question 2: Does "yast2 autoyast / create reference profile" really represent the actual status of that machine concerning installed software and anything else? Is there a better way to reach my goal (two machines with exactly the same software installed; exact clone); how can i create a working xml-profile that ensures this; even if there were lots of software installations and deinstallations on the original machine after the first "initial setup"? Thanks in advance.. -- Dipl.Ing FH Elmar Marschke Schenker & CO AG IT-Innovation SO-Europa / IT-Innovation SE-Europe 1010 Wien / Vienna Austria -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 8

[opensuse-autoinstall] Install / Copy Question
by King, Richard (CE1 UNIX Admin) 08 Jun '07

08 Jun '07

Hello All, I am installing NLD9 via autoyast, which I've been using for a long time, and does work very well. However, I have a new RPM to add, but the only catch is that the rpm will not install unless the "--force" option is used, if I were to install the rpm by hand with the "--force" option, the rpm will install. I did edit the control file accordingly and added the new rpm. After the install is finshed, the new rpm is listed when I run "rpm -qa", however, the file is not present. I was curious if there was a way to use the "--force" option during the autoyast install process for the software section. If not, I could copy the files needed onto the target machine during the autoyast install. This leads me to my next question. If I need to copy a binary file to a specific directory on the target machine, what is the best way to to accomplish this task during the autoyast install? As a test, I wrote a script in the pre-script section of the control file to "cp -p binary_file /usr/sbin", which didn't work. Then I used the absolute path of the binary_file, "cp -p /local/SuSE/i386/nld9/binary_file /usr/sbin/binary_file", which didn't work either. **Background** The new rpm that I am referring to is the new tg3 NIC driver which I created an rpm from a source rpm. The old tg3 driver will not work with the new workstations. Help with this problem would be greatly appreciated. -- Rick King -- 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] IBM x3550 SLES 9 Autoyast with PXE Boot
by Jonathan Buys 08 Jun '07

08 Jun '07

Hello All, I've got a rack full of IBM x3550's which need SLES 9 installed on them. I've configured a PXE and Autoyast server, which seem to be working, however, the 3550's seem to have a problem with the sles9 sp3 driver module. The nic will not load properly, and the autoinstall process fails out almost immediately after the syslinux kernel is loaded. I have the kernel set to load the bnx2 module, which is what it uses once it is installed locally, but I'm still not having any luck. Any suggestions? Thanks, Jon -- 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] updating sles 10 during autoinstallation through a proxy
by Rich 05 Jun '07

05 Jun '07

it seems that we have hit a couple of problems/questions regarding sles10 update through a proxy during autoinstallation. sles10 with sles10_root_fix_v0.4 applied was used; 1. autoinstallation profile has both <customer_center> and valid proxy set. unfortunately, an attempt to register at ncc during autoinstallation fails - it does not use proxy as configured in yast/autoyast. it seems that this proxy is not exported to profile early enough, as adding "export http_proxy=<valid proxy>" allows registering to proceed. that seems a bit hackish approach, so maybe there is another, better way to solve this issue ? 2. update itself requires another way of a proxy setting, "rug set proxy-url". is there a way to force rug to use a proxy specified in environment variable or maybe there is a separate setting in the profile available (though using the proxy set through yast/variables would be preferred :) ) -- 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] Mounting existing LVM partition
by Frank Steiner 04 Jun '07

04 Jun '07

Hi, reinstalling a server with SLES 10/SuSE 10.1 I want to keep and just mount an existing LVM partition. The fstab looks like this /dev/sda1 / ... /dev/sda2 swap ... /dev/sda5 /tmp ... /dev/sda6 /var ... /dev/exportraid/export /export ... /dev/sda7 is used for the LVM. I tried this profile: ... <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>defaults,acl</fstopt> <mount>/var</mount> <partition_nr config:type="integer">6</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <lvm_group>exportraid</lvm_group> <partition_nr config:type="integer">7</partition_nr> </partition> </partitions> </drive> <drive> <device>/dev/exportraid</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">false</format> <fstopt>defaults,acl</fstopt> <lv_name>export</lv_name> <mount>/export</mount> </partition> </partitions> </drive> And also without the partition entry for "exportraid" and just with the "drive" entry for "/dev/exportraid". But the result is that AY ignores /dev/exportraid/ completely. AY says it plans to set the mountpoints of /dev/sda1,2,5 and 6 and format some of them, but says nothing about /dev/exportraid/export. How can I make AY mount the lv? 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

2 8

[opensuse-autoinstall] dhclient_client_id
by Alan Mosca 01 Jun '07

01 Jun '07

Hi all, I see that by default dhclient sends the MAC address as the client id, and there is an option in autoyast to change that value. Is it possible to instruct dhclient not to send a client id at all? Regards, -- Alan Mosca -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0