April 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

x11 - sax2
by Peter Guyan 26 Apr '05

26 Apr '05

Hi My newbie-question: In a classroom with six identical machines i try to netinstall with pxe and autoyast2 under suse9.2. I set up one machine and create a profile with it. All works fine until after the first boot, where I just get a text based login. I have to login as root, run SaX2 and init 5 to test and complete. On the "master"-machine X11 works fine. After reading some messages in the archive i suppose, that autoyast2 can't install X11. Is this correct? There were some hints on a very basic installation with VESA, which I also tried to setup - without success. Can someone give me an example of a post-install-script to setup SaX2, because my attempts did not work. Thanks. Peter

2 1

Re: [suse-autoinstall] How can I regularly update the install repository?
by Michael Marion 25 Apr '05

25 Apr '05

On 13 Apr, Luca Pacor wrote: > I am asking myself whether it would be possible to online_update the > autoinstall repository: it would be nice to be able to install new > machines using an up-to-date repository reducing this way the install > time ... > I am using SuSE 9.2 You could regularly pull down updates into your own update path, and use that. I created a SUSE-Updates tree at the same level as my SUSE-CORE and SUSE-SLES paths, and put updates into there. Then use create_package_descr to make the descr files. i.e. under sles9/SUSE-Updates/updates I have dirs for i586, x86_64, noarch and setup I put the rpms into the right paths based on arch, then cd into sles9/SUSE-Updates/updates and run: /opt/kde3/share/apps/krpmview/create_package_descr -d . That creates the files under setup: cornholio updates {1229}$ find setup/ setup/ setup/descr setup/descr/packages setup/descr/packages.DU setup/descr/packages.en Note that you have to remove conflicting old rpms too.. i.e. if you put something new in, like autofs-4.1.4, you have to remove autofs-4.1.3 before running the create_package_descr script. You could setup a tree like this and rsync in new packages when you get them, and even remove older ones if you script well enough. I do it by hand since we have to test all new changes and stuff here before we push them out into our compute farm. You also have to have the order and instorder files setup to see that path, mine are: cornholio sles9 {1234}$ cat yast/order /SUSE-Updates /SUSE-Updates /SUSE-SLES-Version-9/CD1 /SUSE-SLES-Version-9/CD1 /SUSE-CORE-Version-9/CD1 /SUSE-CORE-Version-9/CD1 cornholio sles9 {1235}$ cat yast/instorder /SUSE-CORE-Version-9/CD1 /SUSE-Updates /SUSE-SLES-Version-9/CD1 When you start a new install, or use yast to point to the Updates path, you'll know pretty quickly if it's seen as valid or not. I've used this setup to add in a lot of things we needed that weren't stock in sles9, or just to update packages. I added openafs, updated autofs with direct map support, updated kernel (mostly for autofs patches), etc. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com [Jerry and George describe wedgies to Elaine] Elaine: "Boys are sick!" Jerry: "Well what do girls do?" Elaine: "We just tease someone until they develop an eating disorder." ==> Seinfeld.

4 3

auto updating install tree
by Ashe Canvar 25 Apr '05

25 Apr '05

Hi all, I am tryng to make a fully automated installation system for SLES9 for x86_64 and i386. First of all I must congratulate Suse for such an excellent, well thought out installation automation system. Yast does have its issues, but once I learnt the ropes it has made me pretty productive. The issue I am not clear about is as follows: - I created my base install image following the docs in http://www.suse.de/~nashif/autoinstall/9.1/html/ch05s02.html#id2523126 - if I install 20 machines and then YOU them then it takes a long time, even if I run a local YOU server. - What I ideally want is to update the installation tree I have created above such that doing a YOU update post-install is not even required. Is there any way to accomplish this ? How do I download the rpm's that have been released as updates to the base SLES9 release ? Doing that through the portal site is pretty painful/manual. I would ideally like to automate this if possible as a weekl build/test/publish cycle for my organization. Thanks!

2 1

Autoinstall and Root-Password
by Daniel Spannbauer 25 Apr '05

25 Apr '05

Hello, I'm a novice in Installing with autoyast. I try a lot at this time. I have some trouble with installig SuSE 9.2 with autoyast. Problem1: The User "root" has no password, I try to fix it with: <window_manager>kde</window_manager> </x11> <users config:type="list"> <user> <username>root</username> <user_password>password</user_password> <encrypted>true</encrypted> <forename/> <surname/> </user> </users> </configure> After this the User "root" has a password but I can*t login as root. Must the password in the config-File be Plain Text? Problem2: The Installation gives an Error-Message. "Wrong LDAP-Config". This Message comes with or without an Ldap-Entry in the config-File. Has anybody the same Problems? Greetings Daniel -- Daniel Spannbauer EDV Systembetreuung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-66 Auf der Wies 8, D 87727 Babenhausen Fax +49 8333 9233-11 http://www.marco.de/ Email ds(a)marco.de

4 4

autoinstall of OES novell components
by Victor Billings 25 Apr '05

25 Apr '05

Sorry if this has been answered previously, I have done a rudimentary search of the archive and found no answers. I have used autoinstall in the past and been quite pleased. But now I am trying to do an autoinstall of the Novell components of OES. While I can get the packages to install correctly, the YaST configuration is a complete mystery. The Novell components all show up in my software addons section ie; <addon>novell-base</addon> <addon>novell-eDirectory</addon> correctly, but I do not have the respective configuration of those components. I have been unable to find a UI in Autoinstall for the configuration of the novell components. Is this currently possible via autoinstall? Thanks, Victor

2 1

SuSE 9.0 Mount From a Post-Install Script "only root can do that"
by Ragnar Skaret 23 Apr '05

23 Apr '05

Hi, I use SuSE 9.0 professional CD version as installation source. I'm trying to run a mount within a post script but as reported earlier it fails with "mount: only root can do that" Here is the result log from post.sh.log: ----------------------- + id uid=0(root) gid=0(root) + whoami root + mount /dev/sda1 on / type ext3 (rw) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/sda3 on /data type ext3 (rw) tmpfs on /dev/shm type tmpfs (rw) + ls -l total 156 drwxr-xr-x 2 bin bin 4096 2005-04-01 11:42 bin drwxr-xr-x 3 root root 4096 2005-04-01 11:42 boot drwxr-xr-x 3 root root 4096 2005-04-01 11:38 data drwxr-xr-x 31 root root 73728 2005-04-01 11:44 dev drwxr-xr-x 43 root root 4096 2005-04-01 11:45 etc drwxr-xr-x 3 root root 4096 2005-04-01 11:45 home drwxr-xr-x 8 root root 4096 2005-04-01 11:41 lib drwx------ 2 root root 16384 2005-04-01 11:38 lost+found drwxr-xr-x 5 root root 4096 2005-04-01 11:45 media drwxr-xr-x 2 root root 4096 2003-09-23 18:02 mnt drwxr-xr-x 3 root root 4096 2005-04-01 11:39 opt dr-xr-xr-x 49 root root 0 2005-04-01 11:43 proc drwx------ 5 root root 4096 2005-04-01 11:45 root drwxr-xr-x 3 daemon daemon 8192 2005-04-01 11:41 sbin drwxr-xr-x 4 root root 4096 2005-04-01 11:39 srv drwxrwxrwt 7 root root 4096 2005-04-01 11:45 tmp drwxr-xr-x 12 root root 4096 2005-04-01 11:39 usr drwxr-xr-x 13 root root 4096 2005-04-01 11:39 var + mount -a 192.168.113.107:/data1/SuSE90 /mnt mount: only root can do that + cd /mnt/post_scripts/ /var/adm/autoinstall/scripts/post.sh: line 9: cd: /mnt/post_scripts/: No such file or directory + cp php-4.3.4.tar.gz /tmp ----------------------- When the installation is finished I executed command "mount" and then the installation media was mounted (nfs) but it was not mounted at this point of the installation process Is the post scripts executed "between" first boot and the installation of the remaining RPMs? (Since I'm using a CD version as installation media, the CD1 is installed then a boot is performed and then the remaining CDs are installed) Is there a fix for this problem anywhere? Should I provide more logs? Any help is much appreciated This is part of my autoyast xml: <scripts> <post-scripts config:type="list" > <script> <filename>post.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh id whoami mount ls -l mount -a 192.168.113.107:/data1/SuSE90 /mnt cd /mnt/post_scripts/ cp php-4.3.4.tar.gz /tmp ]]> </source> </script> </post-scripts> </scripts> Regards Ragnar Skaret ------------------------------------------------------------ Få din egen @start.no-adresse gratis på http://www.start.no/

1 0

Autoyast file(s)
by suse_list 22 Apr '05

22 Apr '05

Hi, I was wondering a few things about the YAST autoinstall config files. I have setup the rules file correctly and all seems to work. Now what i would like to do is to split up the config files so that the <software> section is in a separate file and can be included in different config files. Basically i want custom configurations only for partitioning trees, and the rest to be modular. Another question is, how would i set it up in the config files that when it installs it also runs online updates as well and configures it to do auto-online updates from a specified server? Please let me know Thanks Sascha

2 1

multiple ethernet interfaces causes duplicate host records in the /etc/hosts file?
by deet 22 Apr '05

22 Apr '05

Hello. I am using autoyast/sles9. I just started building hosts with more than 1 physical ethernet interface which resulted in some surprising entries in the /etc/hosts file. here is the snippet of my control.xml file that pertains to the hosts networking setup. <?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"> <configure> <networking> <dns> <domain>atl.company.com</domain> <hostname>app01</hostname> <nameservers config:type="list"> <nameserver>172.17.9.25</nameserver> </nameservers> <searchlist config:type="list"> <search>atl.company.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <startmode>onboot</startmode> <broadcast>172.17.177.255</broadcast> <netmask>255.255.255.0</netmask> <ipaddr>172.17.177.54</ipaddr> </interface> <interface> <bootproto>static</bootproto> <device>eth1</device> <startmode>onboot</startmode> <broadcast>10.170.3.255</broadcast> <netmask>255.255.255.0</netmask> <ipaddr>10.170.3.21</ipaddr> </interface> </interfaces> The resulting hosts file has these 2 entries. 10.170.3.21 app01.atl.company.com 172.17.177.54 app01.atl.company.com app01 The question is. Why is the line "10.170.3.21 app01.atl.company.com" being added to the /etc/hosts file? If I cannot stop this from occuring can I at least control the name that gets associated with the 2nd interface so I might end up with 10.170.3.21 eth1-app01.atl.company.com or something like that? TIA. Deet.

2 1

rules.xml and profiles question - howto define variable in rules.xml
by deet 19 Apr '05

19 Apr '05

Hello. We are running SLES9 and use autoyast to perform our client installations. I'm trying to get my installation environment to the point where I can build machines which have a hostname set and non dhcp ip's for eth0/eth1 with various routes entries. I've now been able to kind of get a working understanding of using rules.xml and profiles (mainly through reading postings from this list). So i've got this rule working which grabs the appropriated domain profile (extra domains removed for readability). The domain profile basically has all the general high level settings that apply to hosts in a domain. But then I need to be able to incorporate each host specific profile which contains host specific entries such as hostname/ip address/gateway/static routes/etc. <rule> <domain> <match>ca.company.net</match> <match_type>exact</match_type> </domain> <result> <profile>sles9.ca.cfg</profile> <continue config:type="boolean">true</continue> </result> </rule> But now I'm trying to configure the host specific profile. I realized I could add in and rule for every single host that I'm installing which would do the following but I dont like the idea of having to edit the rules file for every single host that I install. <rule> <mac> <operator>and</operator> <match>00093f10cc32</match> <match_type>exact</match_type> </mac> <result> <result> <profile>host42.ca.company.net.xml</profile> </result> </rule> Ideally I would like to see something where I have a catch all rule for all hosts which ends in a match and the resulting profile it looks for is an xml file that I have created which would be something like <mac_address>.xml or <ip_address>.xml. I've seen a posting from Anas that I could use some notation like <profile>profile-@mac@.xml</profile> But I dont know how to set that "mac" variable within the rule. Would I do a custom rule to do this and if so how would I do it? If I'm running a custom script do I embed it in the xml or have a path to a script that gets executed? I would really appreciate any pointers or tips on this topic as I feel if I can get over this last hurdle I will have a fairly portable autoyast structure that I can propogate to our various sites without much modification. If anyone would be able to include any custom rule examples I would be very greatful. Thanks for your help! Derek.

2 1

Re: [suse-autoinstall] Custom install source for yast in SLES9
by Michael Marion 15 Apr '05

15 Apr '05

On 15 Apr, Campbell, Fraser wrote: > Can anyone point me to documentation on this? Are there tools to help set > this up? Not sure on full docs, But I created a media.1 dir and a content file. So I have: SUSE-Updates/ /updates/ /i586/ /noarch/ /setup/ /x86_64/ /media1/ /directory.yast /info.txt /media /products /content Content is (Created by slightly modifying the one that came with sles9): PRODUCT SUSE Updates VERSION 9 DISTPRODUCT SUSE-Linux-SLES-x86-64 DISTVERSION 9-0 BASEPRODUCT SUSE CORE BASEVERSION 9 YOUTYPE business YOUPATH x86_64/update/SUSE-SLES/9 YOUURL http://www.suse.de/cgi-bin/suseservers.cgi VENDOR SUSE LINUX AG RELNOTESURL http://www.suse.com/relnotes/x86_64/SUSE-SLES/9/release-notes.rpm ARCH.x86_64 x86_64 i686 i586 i486 i386 noarch DEFAULTBASE x86_64 REQUIRES sles-release-9 LINGUAS de en LABEL SUSE Updates LABEL.de SUSE SLES in der Version 9 DESCRDIR updates/setup/descr DATADIR updates FLAGS update LANGUAGE en_US TIMEZONE America/Los_Angeles ====== In media.1.. directory.yast is: info.txt media products ====== info.txt is just a direct copy from the sles9 media.1 ====== media is: SuSE Linux AG 20040702194312 1 ====== Products is: / SUSE-Updates-x86-64 9 ====== I don't know which are completely required, but I was just copying files from sles9 and editing them as I saw fit.. and I'd keep trying to add the path as an install source until it worked. And it worked with the above. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com The needs of the many outweigh the needs of the few, or the one. That's from Trek. Pretty cool, huh? -- Dennis Miller

1 0