February 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 29 Sep '07

29 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 creating extended partition
by Ian Grant 21 Mar '07

21 Mar '07

Dear List (and Uwe), I am using openSUSE 10.2. When I try to do an autoyast install I get an error dialog when the program tries to set the type of the extended partition: Error: Failure occurred during the following action: Setting type of partition /dev/sda3 to F System error code was: -1012 And the install quits. It leaves the MBR corrupt with an invalid partition type so subsequent autoinstalls don't work (parted says it can't use the format and refuses to create partitions etc.) Does anyone know a way around this? Here is my partitioning XML which I got from 'clone this system for autoyast' on a successful manual install of the same machine. All I have changed is the <use>1,2,3 etc</use> to <use>all</use>: <partitioning config:type="list"> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_nr config:type="integer">0</partition_nr> <raid_options> <persistent_superblock config:type="boolean">false</persistent_superblock> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <lvm_group>system</lvm_group> <partition_nr config:type="integer">1</partition_nr> <raid_options> <persistent_superblock config:type="boolean">false</persistent_superblock> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <lvm_group>scratch</lvm_group> <partition_nr config:type="integer">2</partition_nr> <raid_options> <persistent_superblock config:type="boolean">false</persistent_superblock> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/scratch</device> <lvm2 config:type="boolean">true</lvm2> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>scratch</lv_name> <mount>/local/scratch</mount> <size>32212254720</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_LVM</type> <use>all</use> </drive> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>21476205568</size> </partition> <partition> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>21476205568</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_nr config:type="integer">5</partition_nr> <size>2154990592</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">6</partition_nr> <raid_name>/dev/md1</raid_name> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">7</partition_nr> <raid_name>/dev/md2</raid_name> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">8</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">9</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">10</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">11</partition_nr> <size>38724585472</size> </partition> </partitions> <use>2,3,4,5,6,7,8,9,10,11</use> </drive> <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>21476205568</size> </partition> <partition> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <partition_type>primary</partition_type> <size>21476205568</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_nr config:type="integer">5</partition_nr> <size>2154990592</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">6</partition_nr> <raid_name>/dev/md1</raid_name> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">7</partition_nr> <raid_name>/dev/md2</raid_name> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">8</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">9</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">10</partition_nr> <size>42952379392</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">11</partition_nr> <size>38724585472</size> </partition> </partitions> <use>2,3,4,5,6,7,8,9,10,11</use> </drive> <drive> <device>/dev/system</device> <lvm2 config:type="boolean">true</lvm2> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>tmp</lv_name> <mount>/tmp</mount> <size>10737418240</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>var</lv_name> <mount>/var</mount> <size>8053063680</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_LVM</type> <use>all</use> </drive> </partitioning> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 6

[opensuse-autoinstall] How can I set the repository using SLES 10 DVD?
by Jonathan Meller 01 Mar '07

01 Mar '07

Hey! The autoyast FAQ only explains the repository layout for SLES 10 CDs. What about the DVD? -- Jonathan Meller jonathan.meller(a)tet.com.br ======================================================= Tools & Technologies - T&T Engenheiros Associados Ltda. Projetos de SW - Desenvolvendo soluções. Rua Riachuelo, 1098 Conj. 901 Centro - Porto Alegre - CEP 90010-272 Fone DDR: (51)3220-3244 Fone/Fax: (51)3220-3220 / 3220-3206 http://www.tet.com.br/ tet(a)tet.com.br =======================================================

2 1

[opensuse-autoinstall] Error while configuring partitions. Try again!
by jaiber john 28 Feb '07

28 Feb '07

hi I'm attempting a SLES10 autoyast installation on a disk with pre-configured partitions and getting the following error: Error while configuring partitions. Try again! in the preparing system for Automated installation screen. I came across this thread [http://lists.opensuse.org/archive/opensuse-autoinstall/2005-12/msg00040.html] , but the workarounds suggested (usepart config:type "integer", etc) in it did not work. I am using SLES10 while the other mail thread mentioned SuSE10. Was it a bug in SLES10 that got fixed later - say SLES10.1? Please let me know, I can provide more details if required. Thanks. Here's the partitions list (fdisk -l): Disk /dev/sdb: 79.9 GB, 79930851328 bytes 255 heads, 63 sectors/track, 9717 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 1 841 6755301 83 Linux /dev/sdb2 842 1589 6008310 83 Linux /dev/sdb3 1590 1714 1004062+ 82 Linux swap / Solaris /dev/sdb4 1715 9717 64284097+ 5 Extended /dev/sdb5 1715 1865 1212876 83 Linux /dev/sdb6 1866 2540 5421906 83 Linux /dev/sdb7 2541 2592 417658+ 83 Linux /dev/sdb8 2593 3122 4257193+ 83 Linux /dev/sdb9 3123 3128 48163+ 82 Linux swap / Solaris /dev/sdb10 3129 3157 232911 82 Linux swap / Solaris And here's the partition portion from the autoyast.xml (It is actually /tmp/autoinst/modified.xml -> The one modified through a pre-script to change to correct device - /dev/sdb for example). <partitioning config:type="list"> <drive> <device>/dev/sdb</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">false</format> <mount>/boot</mount> <partition_nr config:type="integer">1</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">false</format> <mount>/</mount> <partition_nr config:type="integer">2</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_nr config:type="integer">3</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">false</format> <mount>/tmp</mount> <partition_nr config:type="integer">5</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">false</format> <mount>/usr</mount> <partition_nr config:type="integer">6</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">false</format> <mount>/var</mount> <partition_nr config:type="integer">7</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">false</format> <mount>/usr/local</mount> <partition_nr config:type="integer">8</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_nr config:type="integer">9</partition_nr> </partition> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_nr config:type="integer">10</partition_nr> </partition> </partitions> </drive> </partitioning> -- <Jaiber John> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

Scripting dirinstall?
by Teun 25 Feb '07

25 Feb '07

Does anyone know if it is possible to use the 'dirinstall' from the command line? For instance i would like to be able to do something like: # yast dirinstall -d /someroot -s mypackages.sel If i do yast -h it says: "Usage: /sbin/yast [OPTIONS] [MODULE] [module specific parameters]" But is there a way to find out what 'module specific parameters' are available for a specific module? Thanks, Teun

3 2

[opensuse-autoinstall] Add_on_products file causes seg fault [SUSE Linux 10.1]
by Marlier, Ian 23 Feb '07

23 Feb '07

Hey, all -- I've been trying to figure out a way to get the non-oss-inst-source and updates/10.1 sources added in to my autoyasted SUSE Linux 10.1 machines for a while now. I had tried the <add-on-products> section of the XML file, and that didn't work. But, I noticed the discussion earlier this week of the add_on_products file in the inst-source directory and decided to give it a shot. I've added two additional sources, each one on its own line in the file (which is a plain text file): nfs://<server>/LinuxDistros/suse/10.1/non-oss-inst-source nfs://<server>/LinuxDistros/suse/update/10.1 When the installation system is starting, I can see those directories get mounted by the machine that's being built, presumably to read their catalogs. Partitioning happens, and the new partitions are formatted. Then, the installation errors out. The following error is given: "Segmenation fault at /mounts/instsys/usr/share/YaST2/clients/inst_rpmcopy.ycp:75 "/usr/lib/YaST2/startup/YaST2.call: line 306: 3244 Segmentation fault (core dumped) $OPT_FBITERM y2base "$Y2_MODULE_NAME" $Y2_MODE_FLAGS $Y2_MODULE_ARGS $Y2_MODE $Y2_UI_ARGS" Without the add_on_products file, everything happens exactly the way that it's supposed to, and the machine ends up installed. (But, with the old, effectively non-working versions of things like rug) Anyone have any thoughts on why this might be erroring out this way? Any suggests on what I might do to make the seg fault stop happening -- ideally, while leaving the add_on_products in place? (And, before anyone asks, I have added the appropriate signature-handling section to my autoyast profile :-) Thanks, Ian -- 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] FW: How to get nic setup in initial autoyast sequence
by John Comitas 23 Feb '07

23 Feb '07

________________________________________ From: John Comitas Sent: Thursday, February 22, 2007 10:09 AM To: 'opensuse-autoinstall(a)opensuse.org' Subject: How to get nic setup in initial autoyast sequence After pre-install and system reboots, I always get a stop where it states at least one nic must be configured and I have to press ok, then it continues. What do I need to do to stop this? 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] SLES10 asking value for nameserver
by Carlos Temes 22 Feb '07

22 Feb '07

Hi all, I'm having some problems with autoyast on SuSE SLES 10. I want to ask values for network configuration to the user. It works for all values (domain, IP address, network mask and gateway) but nameserver. I've tried using "<path>" or "<file>" tags in autoinst.xml: - With "<path>" the /etc/resolv.conf file contains only one line for domain, and none for nameserver. <ask> <path>networking,dns,nameservers,nameserver</path> <title>Nameserver</title> <question>Enter IP address</question> <stage>initial</stage> <default>192.168.1.11</default> </ask> - With "<file>", "/tmp/nameserver_address.tmp" is always empty. <ask> <file>/tmp/nameserver.tmp</file> <title>Nameserver</title> <question>Enter IP address</question> <stage>initial</stage> <default>192.168.1.11</default> </ask> Any idea about what's wrong? Thanks in advance, Carlos -- Carlos Temes Casas Allenta Consulting carlos(a)allenta.com www.allenta.com -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3