May 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] 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] 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] Creating common server certificate?
by Steve Francis 31 May '07

31 May '07

So, when installing Suse manually from CD's, there is the option of creating a common server certificate as part of the installation. Is there a way to also create a common server certificate during the installation when it is driven by Autoyast? Thanks -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

Fwd: Re: [opensuse-autoinstall] Rule based auto-installation
by 1977-Hamlet＠gmx.at 30 May '07

30 May '07

Wrong address. Wanted the list. ;-) -------- Original-Nachricht -------- Datum: Wed, 30 May 2007 14:20:36 +0200 Von: 1977-Hamlet(a)gmx.at An: Uwe Gansert <ug(a)suse.de> Betreff: Re: [opensuse-autoinstall] Rule based auto-installation -------- Original-Nachricht -------- Datum: Wed, 30 May 2007 13:53:26 +0200 Von: Uwe Gansert <ug(a)suse.de> An: opensuse-autoinstall(a)opensuse.org Betreff: Re: [opensuse-autoinstall] Rule based auto-installation > On Wednesday 30 May 2007 13:41, 1977-Hamlet(a)gmx.at wrote: > > > <rule> > > <memsize> > > <match> > > 16 > > </match> > > remove the whitesaces please: > <match>16</match> Removing the whitespaces did the job. Thanks! Leonhard. -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer -- 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] Rule based auto-installation
by 1977-Hamlet＠gmx.at 30 May '07

30 May '07

Hi! I'm using openSUSE 10.2 (i586) within a vmWare Server virtual machine. I'm trying to get AutoYaST running with an rules file but it simply doesn't work. :-( I use TFTP and NFS. My "/srv/tftpboot/pxelinux.cfg/default" contains the following entry: # install label linux kernel linux append initrd=initrd splash=silent showopts install=nfs://192.168.1.50/srv/nfs/OpenSuSE/10-2/CD1 language=de_DE autoyast=nfs://192.168.1.50/var/lib/autoinstall/repository/ My "/var/lib/autoinstall/repository/" directory contains a directory called rules where a file "rules.xml" is to be found. The file "rules.xml" is for testing purpose and has the following content: <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <memsize> <match> 16 </match> <match_type> greater </match_type> </memsize> <result> <profile> ./a.xml </profile> <continue config:type="boolean"> false </continue> </result> </rule> </rules> </autoinstall> When I boot another PC (another virtual machine) through PXE at first everything seems to work fine. I enter linux to the syslinux bootloader and as expected it starts the AutoYaST installation procedure. The YaST2 GUI gets started and it starts with "Hardware-Erkennung". Next comes "Steuerdatei abrufen & einlesen". All of this seems to work. :-) But now it should load the "./a.xml" profile. Nevertheless AutoYast does not find a profile file. It prompts me to enter the "Pfad für Systemprofil" (= path for system profile). It already has filled in the path "nfs://192.168.1.50/var/lib/autoinstall/repository/" and simply waits for the filename to be entered. QUESTION: Why does AutoYaST not recognize the profile name within the rules.xml file? Is this a bug? BTW: When I use AutoYast with just one profile (entering "autoyast=nfs://192.168.1.50/var/lib/autoinstall/repository/a.xml" within "/srv/tftpboot/pxelinux.cfg/default") it simply works. Regards, Leonhard. -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail -- 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] yast2 autoyast
by Alan Mosca 29 May '07

29 May '07

Hi, I'm trying to write a script to make life easier for me and ideally I would like to open 'yast2 autoyast' and tell it to read in my autoyast.xml. Is this supported somehow? Regards, -- 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