April 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] Post-Scripts Not Working
by King, Richard (CE1 UNIX Admin) 02 May '07

02 May '07

SuSE: 10.1 Hello All! I've been trying to run 2 post-scripts, and it appears they are not working. I'll I am trying to is modify 2 files, /etc/passwd & /etc/shadow. This is what I have in the autoyast file: <scripts> <post-scripts config:type="list"> <script> <debug config:type="boolean">false</debug> <feedback config:type="boolean">false</feedback> <filename>nispasswd</filename> <interpreter>shell</interpreter> <location></location> <network_needed config:type="boolean">false</network_needed> <source><![CDATA[cat /etc/passwd | sed 's/+::::::/+::0:0:::/g'] >> /etc/passwd.tmp mv /etc/passwd.tmp /etc/passwd ]]></source> </script> <script> <debug config:type="boolean">false</debug> <feedback config:type="boolean">false</feedback> <filename>nisshadow</filename> <interpreter>shell</interpreter> <location></location> <network_needed config:type="boolean">false</network_needed> <source><![CDATA[cat /etc/shadow | sed 's/+/+::0:0:0::::/g'] >> /etc/shadow.tmp mv /etc/shadow.tmp /etc/shadow ]]></source> </script> </post-scripts> </scripts> As you can see, I am just trying to edit the passwd & shadow files. These scripts are within the <profile></profile> tags. Can someone help me understand why these post scripts are not working? Is there a better way to edit these files? My best to you, -- Rick King -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 5

[opensuse-autoinstall] Removal of Packages
by King, Richard (CE1 UNIX Admin) 02 May '07

02 May '07

SuSE Version: 10.1 Greetings All! I am currently testing a install image for SuSE 10.1. In the control file, I have the following entry to remove software packages: <remove-packages config:type="list"> <package>kdegames3</package> <package>xmoto</package> <package>bsd-games</package> <package>freeciv</package> <package>frozen-bubble</package> <package>supertux</package> <package>knights</package> <package>enigma</package> <package>autofs</package> </remove-packages> The install went fine, however, the packages that I want removed, were installed. I have the remove-packages section within the <software></software> tag. Anything else I am missing? My best to you, -- Rick King -- 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] Preferred installation source
by Lars Stavholm 02 May '07

02 May '07

Does anyone know of a way to tell autoyast to select packages from a specific installation source? I've got my addons installation source setup and it works just fine. However, I've built my own rpm for nagios version 2.9, whereas the suse (10.2) installation contains nagios version 2.5. The version 2.5 is always installed when selected. How do I tell autoyast that I want the 2.9 from my addons? Despite the fact that my rpm is newer, autoyast always selects the 2.5 version from the stock suse 10.2 kit instead of my own addons. I've got an updates addon setup as well, working just fine and I keep it updated. I've noticed that if autoyast finds a newer package in my updates addon, it will select the newer one. But not when from my other addon. Why? It feels like I'm missing something here. Setup is: suse-10.2 suse-10.2/addons suse-10.2/updates Any ideas appreciated /Lars Stavholm -- 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 going from DHCP to static address during autoinstall
by Jacob Emcken 27 Apr '07

27 Apr '07

Hi. I'm using autoyast to install SLES9 on a machine. The install itself works. But I have a problem with the network configuration. During the install the machine obtains a dhcp address and performs the install. When the install is applying the static ipadress defined in the autoyast xml configuration file the dhcp address isn't released and I get something looking like this: 2: eth0: <BROADCAST,MULTICAST,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:17:a4:f8:19:7d brd ff:ff:ff:ff:ff:ff inet 10.73.18.249/24 brd 10.255.255.255 scope global eth0 inet 10.73.18.55/24 brd 10.73.18.255 scope global secondary eth0 inet6 fe80::217:a4ff:fef8:197d/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether 00:17:a4:f8:19:7c brd ff:ff:ff:ff:ff:ff The address 10.73.18.249 is provided by the DHCP during install. The address 10.73.18.55 is defined in the autoyast configuration file. This gives problems later on when mounting NFS shares, because the NFS shares is restricted to the address 10.73.18.55 and the machine connects to the NFS server as 10.73.18.249 How is this resolveable? Is this a known bug? -- Kind regards Jacob Emcken -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 7

[opensuse-autoinstall] does autoyast can resolve the software dependency automaticlly?
by Zheng, Shaohui 27 Apr '07

27 Apr '07

Hi, all I can not find any software dependency description in autoyast manual. It just tells you how to install software and what is the format of the configuration file. I need to confirm it now. Most time we use the GUI to help us generate the autoyast configure file and calculate the dependent software. but now I need generate manually and I need to specify some software but I will not calculate the dependency, I just list some packages. Does the installation program can help me calculate it automatically? The following is a piece of configure file. <software> <packages config:type="list"> <package>apache</package> </packages> <patterns config:type="list"/> </software> I specify apache only, does autoyast can calculate the dependency and install the dependent software automatically? If you have some suggestions or solutions, would you please share it with me, Thanks so much. Shaohui Best Regards -- 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] autoyast in chroot
by Ragnar Kjørstad 26 Apr '07

26 Apr '07

Hi Is it possible to run autoyast in a mode where installs the distribution in a chroot on an existing system instead of installing a new system? In other words, the result would be a directory structure with the new OS installed inside the existing system directory structure. Thanks. -- Ragnar Kjørstad Software Engineer Scali - http://www.scali.com Scaling the Linux Datacenter -- 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] Looking for scripts
by King, Richard (CE1 UNIX Admin) 26 Apr '07

26 Apr '07

Hello, I was looking for the create_directory.yast & create_md5sums scripts, but I cannot seem to find them. Can someone direct me where I can find these scripts? Thanks! -- Rick King -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

Re: [opensuse-autoinstall] Problem going from DHCP to static address during autoinstall
by Jacob Emcken 26 Apr '07

26 Apr '07

Hi. ----- "Uwe Gansert" <ug(a)suse.de> wrote: > On Thursday 26 April 2007 13:52, you wrote: > > > <network_needed > config:type="boolean">true</network_needed> > > sorry, I meant "false", not true. Can you try "false". Thanks it seems it worked. Now my post scripts have access to the NFS shares because the machine uses the static ip address to connect to the NFS server instead of that DHCP address. Cheers mate. Kind regards Jacob Emcken -- 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] 10.2 Autoyast working but Bootmanager fails
by Ralf Prengel 25 Apr '07

25 Apr '07

Hallo, my problem: An Standard-Suse-10.2 Installation was rebuild with autoyast. the Installations works fine but after the first reboot of the clone grub stops with error 15. After booting the system from CD and repairing the bootmanger the clone works perfect. The same happens when using lilo instead of grub. Any ideas what is going wrong? -- i.A. Ralf Prengel Customer Care Manager Comline AG Hauert 8 D-44227 Dortmund/Germany Fon +49231 97575- 904 Fax +49231 97575- 905 EMail ralf.prengel(a)comline.de www.comline.de Vorstand Stephan Schilling Aufsichtsrat Dr. Franz Schoser (Vorsitzender) HR Dortmund B 14570 USt.-ID-Nr. DE 124727422 -- 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] update in chroot non-interactive
by Ingo Wichmann 21 Apr '07

21 Apr '07

Hi! I install my computers with fai (fully automatic installation for debian), and it's usually working quite well. This time I want to install openSuSE 10.2 . The prinziple is simple: 0. A Debian-based installer boots over NFS 1. Partitions and filesystems are created 2. a tar-image is extracted 3. changes individual to the system are made One step within these changes is updating the system. Therefore I run the command: chroot /tmp/target zypper update -y And that's not working perfectly: ------------------- from the install log ----------------------------- [S1:0][package]kdelibs3-3.5.5-45.4.i586 Subprocess failed. Error: RPM failed: error: failed to stat /sys/kernel/debug: No such file or directory ------------------- from the install log ----------------------------- It seems, that rpm is expecting to have /sys/kernel/debug mounted as debugfs - but the debian kernel does not hat that feature. And later: ------------------- from the install log ----------------------------- [S1:0][package]kdebase3-3.5.5-102.3.i586 Subprocess failed. Error: RPM failed: error: failed to stat /sys/kernel/debug: No such file or directory Starting SuSEconfig, the SuSE Configuration Tool... Running module permissions only ERROR - can not find /dev/nfs/lib/YaST/SuSEconfig.functions!! This should not happen. Exit... error: %post(kdebase3-3.5.5-102.3.i586) scriptlet failed, exit status 1 (with nodeps+force)Invalid object (A)bort, (R)etry, (I)gnore? ------------------- from the install log ----------------------------- Well, I can give that rpm it's lib/YaST/SuSEconfig.functions , but why is it looking at /dev/nfs/lib/YaST/SuSEconfig.functions for it? I'll solve that with a symlink or mount --bind, but still: I don't like beeing asked questions when I'm away ... is there a better way to update a openSuSE 10.2 system in a chroot non-interactively? Is yum doing better? Are there some options to zypper I've missed? Ingo -- Linuxhotel, Inh. Reinhard Wiesemann, StNr. 111/5324/0471, UStID DE 180305557 Antonienallee 1, 45279 Essen, Tel.: 0201 8536-600, http://www.linuxhotel.de -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

Re: [opensuse-autoinstall] About -1012 error while creating LVM partitions.
by Arkadiusz Kita 11 Apr '07

11 Apr '07

Hi, I have the same problem with openSUSE 10.2 with 2 identical machines so hardware failures could be excluded. I have already tested the same machine on SUSE Linux Enterprise Server and the same autoyast profile works on it. > Hi, > > I use opensue10.2 and want to use autoyast to setting LVM partitions. > > But I got a problem that -1012 error occurs while making simple LVM partitions, below message is at this problem. > > "Setting hda4 to type F" > > Othes type of partitions got no error. > I got same error only making "LVM" partitions. > > > Is this a BUG?? Any ideas? > > > > show below that section; > > <partitioning config:type="list"> > <drive> > <device>/dev/hda</device> > <partitions config:type="list"> > <partition> > <filesystem config:type="symbol">ext3</filesystem> > <filesystem_id config:type="integer">131</filesystem_id> > <format config:type="boolean">true</format> > <mount>/boot</mount> > <partition_id config:type="integer">131</partition_id> > <partition_nr config:type="integer">1</partition_nr> > <partition_type>primary</partition_type> > <size>73995264</size> > </partition> > <partition> > <filesystem_id config:type="integer">142</filesystem_id> > <lvm_group>system</lvm_group> > <partition_id config:type="integer">142</partition_id> > <partition_nr config:type="integer">2</partition_nr> > <partition_type>primary</partition_type> > <size>82269250560</size> > </partition> > </partitions> > <type config:type="symbol">CT_DISK</type> > <use>all</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>home</lv_name> > <mount>/home</mount> > <size>26843545600</size> > </partition> > <partition> > <filesystem config:type="symbol">ext3</filesystem> > <format config:type="boolean">true</format> > <lv_name>root</lv_name> > <mount>/</mount> > <size>21474836480</size> > </partition> > <partition> > <filesystem config:type="symbol">swap</filesystem> > <format config:type="boolean">true</format> > <lv_name>swap</lv_name> > <mount>swap</mount> > <size>922746880</size> > </partition> > </partitions> > <pesize>4M</pesize> > <type config:type="symbol">CT_LVM</type> > <use>all</use> > </drive> > </partitioning> > > > -- > K.F > casiopea@xxxxxxxxxxxxxxxxx > > > > -- > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@xxxxxxxxxxxx > For additional commands, e-mail: opensuse-autoinstall+help@xxxxxxxxxxxx -- Best regards, kitarek -- 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] Adding the SLES10 SDK to a repository?
by Michael T. Halligan 10 Apr '07

10 Apr '07

So, as with several other oddities, I've found my standard SLES9 method of using Yast2 to import the SDK as an add-on product is no longer possible. How would one go about adding SLES10's SDK to an autoyast repository properly? I've attempted using yast2 to create an installation source, and adding this (actually `yast autoyast` added this) following xml to an autoinstall.xml, but with no luck: <add-on> <add_on_products config:type="list"> <listentry> <media_url>ftp://10.1.100.9/SLES10SDK</media_url> <product>SUSE-Linux-Enterprise-SDK-x86_64</product> <product_dir>/</product_dir> </listentry> </add_on_products> </add-on> What am I doing wrong? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 4

[opensuse-autoinstall] Re: [suse-sles-e] installation_sources command?
by Michael T. Halligan 10 Apr '07

10 Apr '07

Thanks.. Was there logic behind this? I mean, when Redhat removed a bunch of rpms like php4-snmp in RHEL3U3 then brought it back in RHEL4, I switched to SLES due to a lack of faith. On Apr 9, 2007, at 11:02 PM, Marcus Meissner wrote: > On Mon, Apr 09, 2007 at 06:30:52PM -0700, Michael T. Halligan wrote: >> Does anybody know what installation_sources (SLES9: yast2- >> packagemanager) was replaced with? > > rug sl > > for SLE10 SP1 there will be a installation_sources again in the > "zypper" > RPM. > > Ciao, Marcus -- 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] installation_sources command?
by Michael T. Halligan 10 Apr '07

10 Apr '07

Does anybody know what installation_sources (SLES9: yast2- packagemanager) was replaced with? -- 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] Re: Adding the SLES10 SDK to a repository?
by Michael T. Halligan 10 Apr '07

10 Apr '07

So, I'm wondering if anybody has ever successfully done it? There hasn't been much chatter about this on the list. I've tried creating the repository with autoyast, which is broken in 10 different ways. I've tried creating it manually. I've tried using Uwe's script which creates a mystical new driverupdate file to deal with license.zip. This is highly frustrating. It seems that year after year goes by, nobody is actually maintaining Autoyast. Is it perhaps just end of lifed with a better replacement that's actually d ocumented and supported by Novell, but nobody has told any of us? On Apr 9, 2007, at 4:08 PM, Michael T. Halligan wrote: > So, as with several other oddities, I've found my standard SLES9 > method of using Yast2 to import the SDK as an add-on product is no > longer possible. How would one go about adding SLES10's SDK to an > autoyast repository properly? I've attempted using yast2 to create > an installation source, and adding this (actually `yast autoyast` > added this) following xml to an autoinstall.xml, but with no luck: > > <add-on> > <add_on_products config:type="list"> > <listentry> > <media_url>ftp://10.1.100.9/SLES10SDK</media_url> > <product>SUSE-Linux-Enterprise-SDK-x86_64</product> > <product_dir>/</product_dir> > </listentry> > </add_on_products> > </add-on> > > > What am I doing wrong? -- 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] SLES9 YOU repository on SLES10?
by Michael T. Halligan 05 Apr '07

05 Apr '07

What would be involved in running a YOU repository/update service for sles9 clients on a SLES10 server? The YOU server option seems to have disappeared from Yast2 in SLES10. -- 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] ldap problems
by Lars Stavholm 05 Apr '07

05 Apr '07

Hi All, I've managed to use the ldap client (<ldap>) and server (<ldap-server>) sections of my autoinst.xml to setup the server with both as ldap server and ldap client. I would assume that the ldap client stuff will work eventually, but there's a problem with the server part: the ldap database does not get initialized, I still have to go in and do that step manually. Does anyone know how to automate this step? Any thoughts appreciated /Lars -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 4

[opensuse-autoinstall] xmllint autoinst.xml
by Lars Stavholm 05 Apr '07

05 Apr '07

Is the following supposed to work? % xmllint --noout --relaxng \ /usr/share/YaST2/schema/autoyast/rng/profile.rng autoinst.xml Cheers /Lars -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 5

[opensuse-autoinstall] Brainshare session TUT226 Autoyast in Anger
by Simon Crute 05 Apr '07

05 Apr '07

Hi All, A couple of weeks ago at Novell Brainshare in Salt Lake City, I presented a breakout session on Autoyast. I mentioned to a couple of people I'd post it to this this list, so here it is. It covers setting up the install server, setting up a pxe server, as well as the autoyast profiles themselves and some script examples. I think there's at least one typo error in one of the scripts, so keep an eye out for it. I hope it's useful to some people. -- Simon Crute IS&T Bracknell Novell UK Ltd

2 1

[opensuse-autoinstall] bootloader for RAID1
by Lars Stavholm 05 Apr '07

05 Apr '07

Hi All, I've got a setup with three RAID1 SATA disks, using grub as boot loader. All works fine except for one thing: I can only boot on the first disk. This is my boot loader definition in autoinst.xml: [snip] <bootloader> <global> <activate>true</activate> <generic_mbr>true</generic_mbr> <gfxmenu>/boot/message</gfxmenu> <timeout config:type="integer">5</timeout> </global> <loader_device>/dev/md</loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">true</repl_mbr> </bootloader> [snip] After successful installation, I can see that /etc/grub.conf only mentions the first disk, where it should mention all three. After reading the documentation, I'm still not wiser. If I fix it using YaST2 on the installed machine, all I have to do is to select "o Boot from Boot Partition", install the new bootloader, check out /etc/grub.conf, and sure enough, there's the three disks. What do I have to do to get autoyast to install the boot loader on all three disks, not just the first one? Or, what are the legal values for "<location>"? What am I doing wrong here? Any advice appreciated /Lars Stavholm -- 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] autoinst.xml pxe
by Martin Lehmann 05 Apr '07

05 Apr '07

hi list, i'm trying to get an auto installation with pxe and autoyast2 rules running (over http) but it seems to be impossible ... because i have to specify the control file explicitly with the autoyast= parameter .... but if i specify this parameter the rules directory will net get examined anymore .... thats why its impossible to combine network installation and rules if i didnt get anything wrong ... so why doesnt autoyast2 look for default control files (autoinst.xml) in network install sources???? regards martin -- 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] Install OO with response file via autoyast
by Michael Welle 03 Apr '07

03 Apr '07

Hi, can I install the OO suite via autoyast and parametrize OO with a response file? What is the best practice to install and configure OO for a large number of desktops using autoyast? Copying the adjusted ~/.ooo* to every client after the installation process? Michael -- biff4emacsen - A biff-like tool for (X)Emacs http://www.c0t0d0s0.de/biff4emacsen/biff4emacsen.html -- 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] Repository layout for SLES10 SP?
by Jeremy Silver 02 Apr '07

02 Apr '07

All, I have searched this list and www.suse.de/~ug/.cannot and cannot find any documentation on adding a service pack to a SLES10 installation repository - is this documented anywhere? Thanks, -- Jeremy Silver jeremy(a)broadware.com -- 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] Error while configuring partitions. Try again.
by Ian Grant 02 Apr '07

02 Apr '07

Dear List With my autoyast script I get a dialog "Error while configuring partitions. Try again." during the phase 'Create partition plans.' A syslog server sees only a few kernel log message from the install host. The /var/log/Yast2 log on the install host gives no clue about what the error is. Can anyone suggest how to get a more useful diagnostic? Here is my xml file FWIW <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <add-on> <add_on_products config:type="list"/> </add-on> <bootloader> <activate config:type="boolean">true</activate> <device_map config:type="list"> <device_map_entry> <firmware>fd0</firmware> <linux>/dev/fd0</linux> </device_map_entry> <device_map_entry> <firmware>hd0</firmware> <linux>/dev/sda</linux> </device_map_entry> </device_map> <global> <activate>true</activate> <boot_root>true</boot_root> <gfxmenu>/boot/message</gfxmenu> <lines_cache_id>3</lines_cache_id> <timeout config:type="integer">8</timeout> </global> <loader_device>/dev/sda</loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">true</repl_mbr> </bootloader> <firewall> <FW_ALLOW_FW_BROADCAST_DMZ></FW_ALLOW_FW_BROADCAST_DMZ> <FW_ALLOW_FW_BROADCAST_EXT>ntp</FW_ALLOW_FW_BROADCAST_EXT> <FW_ALLOW_FW_BROADCAST_INT></FW_ALLOW_FW_BROADCAST_INT> <FW_DEV_DMZ></FW_DEV_DMZ> <FW_DEV_EXT>eth0</FW_DEV_EXT> <FW_DEV_INT></FW_DEV_INT> <FW_SERVICES_EXT_TCP>ssh</FW_SERVICES_EXT_TCP> <FW_SERVICES_EXT_UDP>ntp</FW_SERVICES_EXT_UDP> <enable_firewall config:type="boolean">true</enable_firewall> <start_firewall config:type="boolean">true</start_firewall> </firewall> <general> <mode> <confirm config:type="boolean">true</confirm> <halt config:type="boolean">false</halt> <second_stage config:type="boolean">true</second_stage> </mode> <mouse> <id>none</id> </mouse> <signature-handling> <accept_file_without_checksum config:type="boolean">false</accept_file_without_checksum> <accept_unknown_gpg_key config:type="boolean">false</accept_unknown_gpg_key> <accept_unsigned_file config:type="boolean">false</accept_unsigned_file> <accept_verification_failed config:type="boolean">false</accept_verification_failed> <import_gpg_key config:type="boolean">false</import_gpg_key> </signature-handling> </general> <keyboard> <keymap>english-uk</keymap> </keyboard> <language> <language>en_GB</language> <languages></languages> </language> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <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">1</partition_nr> <partition_type>primary</partition_type> <size>max</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <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">2</partition_nr> <partition_type>primary</partition_type> <size>4G</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <proxy> <enabled config:type="boolean">true</enabled> <ftp_proxy>http://host.cam.ac.uk:8080/</ftp_proxy> <http_proxy>http://host.cam.ac.uk:8080/</http_proxy> <https_proxy></https_proxy> <no_proxy>localhost, 127.0.0.1, cam.ac.uk</no_proxy> <proxy_password></proxy_password> <proxy_user></proxy_user> </proxy> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </warnings> <yesno_messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </yesno_messages> </report> <runlevel> <default>5</default> </runlevel> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>obscured</user_password> <username>root</username> </user> </users> <scripts> <init-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <filename>post-init</filename> <location></location> <source><![CDATA[#! /bin/bash echo "$(date): in post-init script" >>/tmp/install.log # Mount filer volume mkdir /mnt/nfs || exit 1 mount somehost:/vol/vol3/sys-li9/suse-10.2 /mnt/nfs || exit 1 # Call out to shell script, logging everything /bin/bash -x /mnt/nfs/autoyast/post-init.sh >>/tmp/install.log 2>&1 umount /mnt/nfs ]]></source> </script> </init-scripts> </scripts> <software> <patterns config:type="list"> <pattern>apparmor</pattern> <pattern>base</pattern> <pattern>fonts</pattern> <pattern>imaging</pattern> <pattern>kde</pattern> <pattern>kde_basis</pattern> <pattern>kde_imaging</pattern> <pattern>sw_management</pattern> <pattern>sw_management_x11</pattern> <pattern>x11</pattern> <pattern>xgl</pattern> <pattern>yast2_basis</pattern> <pattern>zmd</pattern> <pattern>zmd_x11</pattern> </patterns> <remove-packages config:type="list"> <package>smtp_daemon</package> </remove-packages> </software> <timezone> <hwclock>UTC</hwclock> <timezone>Europe/London</timezone> </timezone> <user_defaults> <expire></expire> <group>100</group> <groups>video,dialout</groups> <home>/home</home> <inactive>-1</inactive> <shell>/bin/bash</shell> <skel>/etc/skel</skel> </user_defaults> <networking> <dhcp_options> <dhclient_additional_options></dhclient_additional_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <managed config:type="boolean">false</managed> <modules config:type="list"> <module_entry> <device>static-0</device> <module></module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> <online_update> <autoget config:type="boolean">false</autoget> <enable_autoupdate config:type="boolean">true</enable_autoupdate> <skipPre config:type="boolean">false</skipPre> <update_time> <day config:type="integer">0</day> <hour config:type="integer">0</hour> <minute config:type="integer">0</minute> <random_time config:type="boolean">true</random_time> <timing>daily</timing> </update_time> </online_update> <x11> <color_depth>24</color_depth> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">false</enable_3d> <window_manager>kde</window_manager> </x11> </profile> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 4