August 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

YOU wants to install patches that are already installed by multiple source autoinstall
by Teun 07 Sep '05

07 Sep '05

Hello, After a lot of trouble setting up an installation server, serving both a SuSE 9. 3 Pro source and an update source, i finally was able to autoinstall a machine which installed all packages and updates in one go. (So it installs the updated packages straight away and not first the older version.) However, when i then run YaST Online Update on the machine it still wants to install all the updates that are already on the system. It even reports that the installed version of a particular package is the exact same package as the one it wants to install. I already found that if i move a file from /var/lib/YaST2/you/mnt/i386/update/9. 3/patches to /var/lib/YaST2/you/installed the problem is solved for that particular package. But the first directory also contains files for packages that are not installed at all, so just copying all of them would not work. I really hope there is a clean solution to fix this? Any help would be highly appreciated. Regards, Teun

1 1

Re: Intel SE7210TP1+ AutoYast installation problem
by Renato Sartori 31 Aug '05

31 Aug '05

Hi!, I fixed the problem :) Yours autoyast must have a boot kernel from Suse 9.3 ..... easy ;) I was using 9.2 version, causing problem with disk controller. []´s RSartori ----- Original Message ----- From: "Renato Sartori" <renatosartori(a)uol.com.br> To: <suse-autoinstall(a)suse.com> Sent: Tuesday, August 23, 2005 6:02 PM Subject: Intel SE7210TP1+ AutoYast installation problem > Hi Friends, > > I have a Intel SE7210 + P4 3.0 HT 1M cache + Sata Raid Array Adaptec 2810SA > w/ 6 discs Seagate Barracuda Sata 300GB that install ok with Suse 9.3 using > CDROM. > But .. whein I try to install with AutoYast by network, I had a message like > this: "Error while configuring partitions. Try again" > > ps. AutoYast works fine whit another kinds of configuration ( Intel PERLX, > Compaq DL380G3/G4, Abit IS7 etc etc) > ps2. I alread try to take off the adaptec, setting up on onbard controller > but i got the same error. > ps3. I changed the disc to a 80gb, without success. > > Someone knows whys it happens ??? > > Thaks in advance > RSartori > >

1 0

Networking
by Bill Cavalieri 31 Aug '05

31 Aug '05

Does anyone have or point me towards some examples have handling networking setup? What I would like to do is in my autoyast xml say, eth0 will be 192.168.3.254, and eth1 will be dhcp. Then during install let it detect what nic module is needed. So far I have only been able to get it to work when I specify the module. Thanks, -Bill

1 0

Re: [suse-autoinstall] Yast not starting upon VNC reconnect after reboot.
by Teun 31 Aug '05

31 Aug '05

Okay, so this only happens when you select 'minimal' during the VNC based installation process. Not very smooth if you ask me.... Teun Quoting Teun <suse(a)teund.dds.nl>: > Hello, > > I am trying to do a remote install using VNC, installing SuSE 9.3 > Professional. > This all goes fine until Yast wants to do the first reboot. The machine > reboots and after coming back up the console tells me to reconnect my VNC > viewer and finish the installation. > > However, if i reconnect my viewer i just get an empty screen. It seems to be > a > gray pattern empty X screen with a mouse pointer. But Yast is not coming back > to finish the install. > > Is this a known issue? Or is there anything i should check? > > Regards, > Teun > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > >

1 0

SLES 9 SP2 frustrations with x86_64
by Michael T. Halligan 31 Aug '05

31 Aug '05

So, I'm attempting to work with Novell's support, but that's turning into a slower process than I thought it would be. Here's my setup. I've got a dozen Dell SC1425 with dual drives, which I want to do software RAID on. I do not have these boxes setup for "hardware raid" which is the first caveat on them. My process was thus : 1. Use Yast2 to create an installation source (x86_64) 2. Use Yast2 to patch the installation source with SP2 3. build a server manually 4. Use Yast to create a reference file 5. Try to install . This always fails. I get one or two errors, either Error An error occurred whiel trying to create the partitioning plans. Make sure the control file has the correct syntax and values. Or An error occurred during partitioning. Now, beyond being all fancy, I've tried using : - The control file included on the SP1 cd - The control file from the yast2-autoinstall file I've tried doing these both with, and without any partitoning. I always get these errors. At one point, I believe I did actually get an autoinstall to work with no partitioning, but it's been so long I forget. This is really frustrating. When I create an reference file from a machine, then try to validate it, that should not fail, I don't even have the remote ability to break it. I am starting to believe that yast2's method of creating an installation is terribly broken. Here's what I end up with : drwxr-xr-x 7 root root 168 Aug 30 18:35 SUSE-CORE-Version-9 drwxr-xr-x 5 root root 120 Aug 30 18:47 SUSE-SLES-9-Service-Pack-Version-2 drwxr-xr-x 3 root root 72 Aug 30 18:30 SUSE-SLES-Version-9 lrwxrwxrwx 1 root root 28 Aug 30 18:31 boot -> SUSE-SLES-Version-9/CD1/boot lrwxrwxrwx 1 root root 31 Aug 30 18:31 content -> SUSE-SLES-Version-9/CD1/content -r--r--r-- 1 root root 17621 Aug 31 00:27 control.xml lrwxrwxrwx 1 root root 51 Aug 30 18:38 driverupdate -> SUSE-SLES-9-Service-Pack-Version-2/CD1/driverupdate lrwxrwxrwx 1 root root 44 Aug 30 18:38 linux -> SUSE-SLES-9-Service-Pack-Version-2/CD1/linux lrwxrwxrwx 1 root root 31 Aug 30 18:31 media.1 -> SUSE-SLES-Version-9/CD1/media.1 drwxr-xr-x 2 root root 104 Aug 30 18:36 yast I have tried : - Booting from the initrd & kernel which comes with SLES9 - Booting from the initrd & kernel which comes with SP2 - Copying the initrd and kernel from SP2/CD1/boot into SUSE-SLES-Version-9/CD1/boot (overwriting the default) - A hundred different variations of all this. Does anybody have any good ideas before I give up?

2 6

Re: [suse-autoinstall] SLES 9 SP2 frustrations with x86_64
by Hans-Joachim Ehlers 31 Aug '05

31 Aug '05

Hi Michael > Does anybody have any good ideas before I give up? Sure, do not give up . The first step is to verify that your installation source is in a correct state. I assume that you have read the documentation to build a SUSE-SLES-9 including SP2 So just boot your machine with a boot/installation cd and use for installation your installation server. If this works i would think that the installation server is fine. If not do your homework and RTFM. The next step is to use a simple autoinstallation file ( We assume /export/sles9/autoinstall.xml as filename ) Create this file with " yast2 autoyast " which should contain the bootloader, minimum installation ( save time for testing ) , ip . and save is as /export/sles9/autoinstall.xml Validate this file with "xmllint" Now boot from CD and supply the nessesary parameter for automatic installation If you still have a floppy drive to might use a file named "info" on a floppy. Otherwise to have to supply at least server=, serverdir=, hostip=, and autoyast= on the command line or use dhcp #Example #See file "README.linuxrc" for details textmode: 1 language: en_US instmode: nfs netdevice: eth0 ip: 10.1.0.1 netmask: 255.255.0.0 broadcast: 10.1.255.255 gateway: 10.1.0.1 server: 10.1.0.225 serverdir: /export/sles9 autoyast: /export/sles9/autoinstall.xml Now you should be able to start debugging the installation process. As mentioned before maybe the autodection for the new sata disk does not work ? hth Hajo >>> "Michael T. Halligan" <michael(a)halligan.org> 08/31/05 10:14 am >>> So, I'm attempting to work with Novell's support, but that's turning into a slower process than I thought it would be. Here's my setup. I've got a dozen Dell SC1425 with dual drives, which I want to do software RAID on. I do not have these boxes setup for "hardware raid" which is the first caveat on them. My process was thus : 1. Use Yast2 to create an installation source (x86_64) 2. Use Yast2 to patch the installation source with SP2 3. build a server manually 4. Use Yast to create a reference file 5. Try to install . This always fails. I get one or two errors, either Error An error occurred whiel trying to create the partitioning plans. Make sure the control file has the correct syntax and values. Or An error occurred during partitioning. Now, beyond being all fancy, I've tried using : - The control file included on the SP1 cd - The control file from the yast2-autoinstall file I've tried doing these both with, and without any partitoning. I always get these errors. At one point, I believe I did actually get an autoinstall to work with no partitioning, but it's been so long I forget. This is really frustrating. When I create an reference file from a machine, then try to validate it, that should not fail, I don't even have the remote ability to break it. I am starting to believe that yast2's method of creating an installation is terribly broken. Here's what I end up with : drwxr-xr-x 7 root root 168 Aug 30 18:35 SUSE-CORE-Version-9 drwxr-xr-x 5 root root 120 Aug 30 18:47 SUSE-SLES-9-Service-Pack-Version-2 drwxr-xr-x 3 root root 72 Aug 30 18:30 SUSE-SLES-Version-9 lrwxrwxrwx 1 root root 28 Aug 30 18:31 boot -> SUSE-SLES-Version-9/CD1/boot lrwxrwxrwx 1 root root 31 Aug 30 18:31 content -> SUSE-SLES-Version-9/CD1/content -r--r--r-- 1 root root 17621 Aug 31 00:27 control.xml lrwxrwxrwx 1 root root 51 Aug 30 18:38 driverupdate -> SUSE-SLES-9-Service-Pack-Version-2/CD1/driverupdate lrwxrwxrwx 1 root root 44 Aug 30 18:38 linux -> SUSE-SLES-9-Service-Pack-Version-2/CD1/linux lrwxrwxrwx 1 root root 31 Aug 30 18:31 media.1 -> SUSE-SLES-Version-9/CD1/media.1 drwxr-xr-x 2 root root 104 Aug 30 18:36 yast I have tried : - Booting from the initrd & kernel which comes with SLES9 - Booting from the initrd & kernel which comes with SP2 - Copying the initrd and kernel from SP2/CD1/boot into SUSE-SLES-Version-9/CD1/boot (overwriting the default) - A hundred different variations of all this. Does anybody have any good ideas before I give up? -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Re: [suse-autoinstall] autoyast fails on partitioning on Dell Precision 670
by GrueMaster 31 Aug '05

31 Aug '05

Thanks for the rules help. I've been studying the online documentation and was very confused about the directory structure needed for the rules.xml. Your rules.xml example worked flawlessly. I'd recommend adding your example as it is written to the documentation. I've now progressed to getting the system imaged and booting (Whoo Hoo!) Now to get my post install script running again (I yanked it to simplify debugging the partitioning issues). Next question, is there a setting to allow installing without the "Licensing" prompt, or does the timeout automaticly assume acceptance? Tobin Hans-Joachim Ehlers <HansJoachim.Ehlers(a)eumetsat.int> wrote: My partitioning section is directly AFTER . I have been told that the order shall not matter but who knows. So give it a try. If the order change will help then there is no need for a rules.xml At least at my site i have no problems with SATA and IDE drive. About SCSI i can not tell. If you need a rules.xml 1) Get the documentation about autoyast ( Mentioned in a previous post to this list by me ) 2) Below your autoinstallation source directory ( Example: MyServer:/export/suse/autoinstall/ ) create the following subdirectories: ./rules ( Will hold only the rules.xml ) ./classes ( Will hold the autoinstall.xml and sda.xml and hda.xml ) A few importent hints: A) The autoyast entry MUST end with an "/" . Example: autoyast=nfs://MyServer:/export/suse/autoinstall/ otherwise the rules.cml will NOT be parsed. B) The rules.xml MUST include a rule to include your standard "installation.xml" because it will be parsed only what has a MATCH in the rules.xml C) You must use " echo -n" in your script section to get rid of the NEWLINE. Otherwise the match will not work. The following is an example of a "rules.xml" to determine the disk type xmlns:config="http://www.suse.com/1.0/configns"> if grep hda /proc/partitions > /dev/null; then echo -n "hda" else echo -n "sda" fi; ]]> * exact classes/@custom1@.xml true * exact classes/autoinst.xml false ---------------------------------------------------------- The first rule will parse your ( sda.xml or hda.xml ) and continue to the next rule The second rule will match everything so it does include the classes/autoinst.xml File. Now further rules will be parsed afterwards. The sda.xml is just a stript down version from your autoinst.xml containing a Section like down below ( NOT tested ) . For the hda.xml you must just change the device section. To get these Section i would use "yast2 autoyast " and create a new xml file where only the paritioning section has been configured with yast2. Afterwards take everthing out of the file what is not related to the partitioning . Run "xmllint" to verify the file and you should be happy. xmlns:config="http://www.suse.com/1.0/configns"> /dev/sda all hth Hajo >>> GrueMaster 08/26/05 5:49 pm >>> I fixed the boot loader section, but that isn't where the problem is. Yast fails at "Create partition plans". Hey, I think I figured it out (somewhat). I added /dev/sda to the partitioning section and it now blows past that and installs. Now I need to figure out how to use rules, as we have IDE, SCSI, and SATA systems. SATA and SCSI will work with this config, but IDE needs /dev/hda. Any suggestions? --------------------------------- Start your day with Yahoo! - make it your home page

2 1

Software RAID examples
by Egan Ford 30 Aug '05

30 Aug '05

Can any point me to an XML autoyast file with an example of software RAID 0 or 1 with two disks. The disks must boot. Thanks.

2 2

Re: [suse-autoinstall] SLES SP2 AutoYast problems.
by Hans-Joachim Ehlers 29 Aug '05

29 Aug '05

Hi Michael, sometime things are not the way they should be. Its took me about one week to get an auto install for a simple network installation and this list to solve some major understanding problems. >From what i am right now know it should take only a hour to understand the whole process. But that's another story. So back to your problem. Like i said before: Create a simple xml file for installation. Do not use a reference. For testing there is just no need. Since you are at a remote location you might consider using the "vnc" option for installation. I never tested it. But from my understanding a VNC server will be started so you can remotely connect. ( i think it is used for headless system. ) See http://www.novell.com/coolsolutions/feature/15568.html for details Also please do not complain about autoyast: Its a nice tool which will sometimes gives you a lession in " zen and the are of patience" . So please post your info file and your command line options and try vnc to find out whats going on your client. A good book ( pdf) is: Autoyast Automatic Linux Installation and Configuration with Yast2 by Anas Nashif, Suse Linux AG hth Hajo who is now facing of MAINTAINING a suse system. >>> "Michael T. Halligan" <michael(a)halligan.org> 08/26/05 3:34 pm >>> Is there any way to redirect all of these logs to a loghost, if there's more that isn't being seen when I boot with loghost=IP.ADDR. It's pretty complicated for me to get to my datacenter right now, and remote serial console on these dells do not work (of course dell, in theirvery helpful way, has told me there will be new firmwares in a month). What I really don't get, is why should there be ANY problem with installing a server from a reference profile? Shouldn't that install also have failed then? It seems that autoyast is just writing ugly xml and then not being able to read it back in? >From my experience: >Keep thinks simple in the beginning > > >1 ) So no software raid and what so ever. > - Simple Partition schema > - Do not name the disk for installation ( SATA will be detected as >/dev/sd[a-z]X devices >2 ) use text mode for Installation ( Graphical Installations fails for >me ) >3 ) Have a large defined swap partition because if you use http for >installation autoyast will copy pretty much of the installation to its >local ram disk ( memory ) >You can use "top" on a different terminal >4) Take a look at the /var/log/Yast log files ( The ones on the ram >disk ) >5) Switch to terminal 4 ( from memory ) to see what has been loaded and >what has happend. > > >hth >Hajo > > > > >>>>"Michael T. Halligan" <michael(a)halligan.org> 08/26/05 3:02 pm >>> >>>> >>>> >So I've been struggling for a couple of days trying to get AutoYast to > >work. I can install on these servers manually.. However, if I create a > >reference profile, or creaet my own profile, >or really do anything with autoyast, every time I try to install, the >server gets as far as loading the device driver disks, then stops with >a >big red box reading "An error occurred during installation" >That's it. > > >I built an installation source using SLES 9S SP2 x86_64. I am trying >to >boot with y2debug and setting a loghost, but the messages i'm getting >aren't exactly helpful. >The servers I'm installing on are del sc1425s with single 3ghz procs >and >dual sata drives. I'm attempting to setup sles9-sp2 with software >raid1. >Any help would be >appreciated. > > >The last few lines I'll see in syslog are: >ug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] >NCurses.cc(Refresh):407 >start refresh ... >Aug 25 22:10:39 BOB yast2[3642]: <1> [ncurses] NCurses.cc(SetTitle):459 > >Draw title called >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] >NCurses.cc(Refresh):411 done refresh ... >Aug 25 22:10:39 BOB yast2[3606]: <1> [wfm] >Y2WFMComponent.cc(SetLanguage):403 SET encoding to: UTF-8 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Accept" >-> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Add" -> F3 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Back" -> F8 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Cancel" >-> F9 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Do Not Accept" >-> F9 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Don't install" >-> F9 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Finish" >-> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Help" -> F1 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Install" >-> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Next" -> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "No" -> F9 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "OK" -> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Quit" -> F9 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Save" -> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Yes" -> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Close" -> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Continue" >-> F10 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Delete" >-> F5 >Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] >YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Edit" -> F4 >Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:243 >before >.probe.floppy >Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:245 after > >.probe.floppy >Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:267 >FloppyDrives [] >Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] >YNCursesUI.cc(YNCursesUI):114 Stop YNCursesUI >Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] >NCurses.cc(NCurses):160 Shutdown NCurses... >Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] >NCurses.cc(NCurses):169 NCurses down >Aug 25 22:10:39 BOB yast2[3606]: <1> [liby2] >genericfrontend.cc(main):437 Finished YaST2 component >'y2base' > > > > -- Michael T. Halligan Chief Technology Officer ------------------- BitPusher, LLC http://www.bitpusher.com/ 1.888.9PUSHER 415.724.7998 (Mobile) 415.520.0876 (Fax) -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Yast not starting upon VNC reconnect after reboot.
by Teun 27 Aug '05

27 Aug '05

Hello, I am trying to do a remote install using VNC, installing SuSE 9.3 Professional. This all goes fine until Yast wants to do the first reboot. The machine reboots and after coming back up the console tells me to reconnect my VNC viewer and finish the installation. However, if i reconnect my viewer i just get an empty screen. It seems to be a gray pattern empty X screen with a mouse pointer. But Yast is not coming back to finish the install. Is this a known issue? Or is there anything i should check? Regards, Teun

1 0

Problems installing Festival 1.9.5 on Suse 9.3
by Marc Scheib 27 Aug '05

27 Aug '05

Sorry for bothering you: I am trying to install the Festival RPM from the KDE Accessibility Project, but YAST does not show anything about the new Version. I am a bloody newbie to the Suse Installation System and therefore would like to ask you kindly for a hint on my installation problem. I am working on a Suse 9.3 Installation. Konqueror shows me a button 'Install Package with YAST' when I download the RPM from http:// accessibility.kde.org/developer/kttsd/index.php, but when I click on that button YAST shows me only the old Version 1.4.3 from the Suse- Repository.. Please, how can I point Yast towards the new RPM? Thank you for your cooperation, Marc Scheib (mailto:marc(at)mindbomb.de)

1 0

Re: [suse-autoinstall] autoyast fails on partitioning on Dell Precision 670
by Hans-Joachim Ehlers 26 Aug '05

26 Aug '05

Hi Tobin, the Example to determine the disk type is not from me. I found it on the net and used it as an example for our installation enviroment. But anyway. The Licensing prompt should stay for 10 seconds and then the installation should procced further. If not you have another problem. have a nice weekend Hajo who will be back on monday. >>> GrueMaster <gruemaster(a)yahoo.com> 08/26/05 8:32 pm >>> Thanks for the rules help. I've been studying the online documentation and was very confused about the directory structure needed for the rules.xml. Your rules.xml example worked flawlessly. I'd recommend adding your example as it is written to the documentation. I've now progressed to getting the system imaged and booting (Whoo Hoo!) Now to get my post install script running again (I yanked it to simplify debugging the partitioning issues). Next question, is there a setting to allow installing without the "Licensing" prompt, or does the timeout automaticly assume acceptance? ....

1 0

Re: [suse-autoinstall] autoyast fails on partitioning on Dell Precision 670
by Hans-Joachim Ehlers 26 Aug '05

26 Aug '05

My partitioning section is directly AFTER </general> . I have been told that the order shall not matter but who knows. So give it a try. If the order change will help then there is no need for a rules.xml At least at my site i have no problems with SATA and IDE drive. About SCSI i can not tell. If you need a rules.xml 1) Get the documentation about autoyast ( Mentioned in a previous post to this list by me ) 2) Below your autoinstallation source directory ( Example: MyServer:/export/suse/autoinstall/ ) create the following subdirectories: ./rules ( Will hold only the rules.xml ) ./classes ( Will hold the autoinstall.xml and sda.xml and hda.xml ) A few importent hints: A) The autoyast entry MUST end with an "/" . Example: autoyast=nfs://MyServer:/export/suse/autoinstall/ otherwise the rules.cml will NOT be parsed. B) The rules.xml MUST include a rule to include your standard "installation.xml" because it will be parsed only what has a MATCH in the rules.xml C) You must use " echo -n" in your script section to get rid of the NEWLINE. Otherwise the match will not work. The following is an example of a "rules.xml" to determine the disk type <?xml version="1.0"?> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> <![CDATA[ if grep hda /proc/partitions > /dev/null; then echo -n "hda" else echo -n "sda" fi; ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/@custom1@.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom1> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/autoinst.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> ---------------------------------------------------------- The first rule will parse your ( sda.xml or hda.xml ) and continue to the next rule The second rule will match everything so it does include the classes/autoinst.xml File. Now further rules will be parsed afterwards. The sda.xml is just a stript down version from your autoinst.xml containing a Section like down below ( NOT tested ) . For the hda.xml you must just change the device section. To get these Section i would use "yast2 autoyast " and create a new xml file where only the paritioning section has been configured with yast2. Afterwards take everthing out of the file what is not related to the partitioning . Run "xmllint" to verify the file and you should be happy. <?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"> <install> <partitioning config:type="list"> <device>/dev/sda</device> <drive> <use>all</use> </drive> </partitioning> </install> </profile> hth Hajo >>> GrueMaster <gruemaster(a)yahoo.com> 08/26/05 5:49 pm >>> I fixed the boot loader section, but that isn't where the problem is. Yast fails at "Create partition plans". Hey, I think I figured it out (somewhat). I added <device>/dev/sda</device> to the partitioning section and it now blows past that and installs. Now I need to figure out how to use rules, as we have IDE, SCSI, and SATA systems. SATA and SCSI will work with this config, but IDE needs /dev/hda. Any suggestions?

1 0

Re: [suse-autoinstall] autoyast fails on partitioning on Dell Precision 670
by Hans-Joachim Ehlers 26 Aug '05

26 Aug '05

Stripped down xml file ? You are kidding ;-) Does the creation of the partion fails or is just the bootloader not active. Also for troubleshooting: Have you verified your auto.xml with "xmllint" Does the driver for your hba are being loaded ? BTW: What i do not understand is your bootloader Section: Because it says not to activate it. Below yor xml File i have put an extract of my boatloader section. hth Hajo >From your xml File .... <bootloader> <activate config:type="boolean">false</activate> <global config:type="list"/> <loader_device></loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">false</repl_mbr> </bootloader> .... Extract from my xml File: <bootloader> <activate config:type="boolean">true</activate> <global config:type="list"/> <loader_device></loader_device> <loader_type>lilo</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">true</repl_mbr> <sections config:type="list"/> </bootloader> >>> GrueMaster <gruemaster(a)yahoo.com> 08/26/05 2:03 am >>> I'm still trying to get autoinstall for Suse 9.3 to work on this system. Autoyast fails to create partitions. Works just fine installing manually, but I need to be able to implement autoinstall. Attached is my stripped down auto.xml file. It worked on a few older systems, but not here. Anything else I can try? Tobin --------------------------------- Start your day with Yahoo! - make it your home page ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 eMail : hansjoachim.ehlers(a)eumetsat.int iNet : www.eumetsat.de

3 2

Re: [suse-autoinstall] SLES SP2 AutoYast problems.
by Hans-Joachim Ehlers 26 Aug '05

26 Aug '05

>From my experience: Keep thinks simple in the beginning 1 ) So no software raid and what so ever. - Simple Partition schema - Do not name the disk for installation ( SATA will be detected as /dev/sd[a-z]X devices 2 ) use text mode for Installation ( Graphical Installations fails for me ) 3 ) Have a large defined swap partition because if you use http for installation autoyast will copy pretty much of the installation to its local ram disk ( memory ) You can use "top" on a different terminal 4) Take a look at the /var/log/Yast log files ( The ones on the ram disk ) 5) Switch to terminal 4 ( from memory ) to see what has been loaded and what has happend. hth Hajo >>> "Michael T. Halligan" <michael(a)halligan.org> 08/26/05 3:02 pm >>> So I've been struggling for a couple of days trying to get AutoYast to work. I can install on these servers manually.. However, if I create a reference profile, or creaet my own profile, or really do anything with autoyast, every time I try to install, the server gets as far as loading the device driver disks, then stops with a big red box reading "An error occurred during installation" That's it. I built an installation source using SLES 9S SP2 x86_64. I am trying to boot with y2debug and setting a loghost, but the messages i'm getting aren't exactly helpful. The servers I'm installing on are del sc1425s with single 3ghz procs and dual sata drives. I'm attempting to setup sles9-sp2 with software raid1. Any help would be appreciated. The last few lines I'll see in syslog are: ug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] NCurses.cc(Refresh):407 start refresh ... Aug 25 22:10:39 BOB yast2[3642]: <1> [ncurses] NCurses.cc(SetTitle):459 Draw title called Aug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] NCurses.cc(Refresh):411 done refresh ... Aug 25 22:10:39 BOB yast2[3606]: <1> [wfm] Y2WFMComponent.cc(SetLanguage):403 SET encoding to: UTF-8 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Accept" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Add" -> F3 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Back" -> F8 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Cancel" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Do Not Accept" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Don't install" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Finish" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Help" -> F1 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Install" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Next" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "No" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "OK" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Quit" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Save" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Yes" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Close" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Continue" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Delete" -> F5 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Edit" -> F4 Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:243 before .probe.floppy Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:245 after .probe.floppy Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:267 FloppyDrives [] Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] YNCursesUI.cc(YNCursesUI):114 Stop YNCursesUI Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] NCurses.cc(NCurses):160 Shutdown NCurses... Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] NCurses.cc(NCurses):169 NCurses down Aug 25 22:10:39 BOB yast2[3606]: <1> [liby2] genericfrontend.cc(main):437 Finished YaST2 component 'y2base' -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

SLES SP2 AutoYast problems.
by Michael T. Halligan 26 Aug '05

26 Aug '05

So I've been struggling for a couple of days trying to get AutoYast to work. I can install on these servers manually.. However, if I create a reference profile, or creaet my own profile, or really do anything with autoyast, every time I try to install, the server gets as far as loading the device driver disks, then stops with a big red box reading "An error occurred during installation" That's it. I built an installation source using SLES 9S SP2 x86_64. I am trying to boot with y2debug and setting a loghost, but the messages i'm getting aren't exactly helpful. The servers I'm installing on are del sc1425s with single 3ghz procs and dual sata drives. I'm attempting to setup sles9-sp2 with software raid1. Any help would be appreciated. The last few lines I'll see in syslog are: ug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] NCurses.cc(Refresh):407 start refresh ... Aug 25 22:10:39 BOB yast2[3642]: <1> [ncurses] NCurses.cc(SetTitle):459 Draw title called Aug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] NCurses.cc(Refresh):411 done refresh ... Aug 25 22:10:39 BOB yast2[3606]: <1> [wfm] Y2WFMComponent.cc(SetLanguage):403 SET encoding to: UTF-8 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Accept" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Add" -> F3 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Back" -> F8 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Cancel" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Do Not Accept" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Don't install" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Finish" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Help" -> F1 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Install" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Next" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "No" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "OK" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Quit" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Save" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Yes" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Close" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Continue" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Delete" -> F5 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Edit" -> F4 Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:243 before .probe.floppy Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:245 after .probe.floppy Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:267 FloppyDrives [] Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] YNCursesUI.cc(YNCursesUI):114 Stop YNCursesUI Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] NCurses.cc(NCurses):160 Shutdown NCurses... Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] NCurses.cc(NCurses):169 NCurses down Aug 25 22:10:39 BOB yast2[3606]: <1> [liby2] genericfrontend.cc(main):437 Finished YaST2 component 'y2base'

1 0

autoyast fails on partitioning on Dell Precision 670
by GrueMaster 26 Aug '05

26 Aug '05

I'm still trying to get autoinstall for Suse 9.3 to work on this system. Autoyast fails to create partitions. Works just fine installing manually, but I need to be able to implement autoinstall. Attached is my stripped down auto.xml file. It worked on a few older systems, but not here. Anything else I can try? Tobin --------------------------------- Start your day with Yahoo! - make it your home page

1 0

USEFUL AutoYast logging information?
by Michael T. Halligan 24 Aug '05

24 Aug '05

I'm failing miserably at installing SLES9 on a pile of Dell SC1425s. I have no idea why. I'm booting with verbose=1 and loghost=my.loghost .. The messages I'm seeing when the install fails are "An error occured during installation". The only information being sent to my loghost is : Aug 23 16:22:35 newhost yast2[1860]: <1> [YCP] StorageDevices.ycp:243 before .probe.floppy Aug 23 16:22:35 newhost yast2[1860]: <1> [YCP] StorageDevices.ycp:245 after .probe.floppy Aug 23 16:22:35 newhost yast2[1860]: <1> [YCP] StorageDevices.ycp:267 FloppyDrives [] Aug 23 16:22:35 newhost yast2[1860]: <1> [ui-ncurses] YNCursesUI.cc(YNCursesUI):114 Stop YNCursesUI Aug 23 16:22:35 newhost yast2[1860]: <1> [ui-ncurses] NCurses.cc(NCurses):160 Shutdown NCurses... Aug 23 16:22:35 newhost yast2[1860]: <1> [ui-ncurses] NCurses.cc(NCurses):169 NCurses down Aug 23 16:22:35 newhost yast2[1860]: <1> [liby2] genericfrontend.cc(main):437 Finished YaST2 component 'y2base' The problem has been compounded by the complete worthlessness of Dell's BMC and their broken serial port.

1 0

Re: [suse-autoinstall] Question about ndiswrapper
by Hans-Joachim Ehlers 24 Aug '05

24 Aug '05

On my Suse 9.3 PC i have found: # modprobe -l ndiswrapper /lib/modules/2.6.11.4-20a-default/extra/ndiswrapper.ko and a # rpm -qf /lib/modules/2.6.11.4-20a-default/extra/ndiswrapper.ko kernel-default-2.6.11.4-20a hth Hajo >>> "Malcom Kemp" <mkemp(a)bellsouth.net> 08/21/05 8:48 pm >>> This may be a little off subject, but if someone could point me in the right direction, I would appreciate it. I have 9.3 and am trying to get an unsupported WAN card to work. I have used Yast to install the ndiswrapper package, which it does. I have used the -i to install the driver, and with the -l option it tells me it is there and that it looks correct. When I try to modprobe ndiswrapper however, it gives me fatal error, "Module ndiswrapper not found". I removed the package and reinstalled it, but still have same error. How do I get the kernel module put on the system? -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Re: [suse-autoinstall] Adding the file "info" to an bootable CD/DVD
by Hans-Joachim Ehlers 24 Aug '05

24 Aug '05

Hi Lee, thanks to you and the others as well. I had to do only cometic changes to your example: ----> gzip -dc /work-iso/initrd >/tmp/initrd.img <------ mkdir /work-initrd; cd /work-initrd # make a place to extract it cpio -i < /tmp/initrd.img # Extract it from cpio archive cp YOUR_INFO_FILE info # Put your info file in there ----> find . | cpio -H newc -o > /tmp/initrd.img <----- ----> gzip -c /tmp/initrd.img >/work-iso/initrd <----- So thanks a lot Hajo >>> Lee Mayes <autoinst(a)mayeses.com> 08/23/05 2:12 pm >>> Hi Hajo, initrd is on the CD, but it's in its compressed form. Starting with 9.3 for suse (I think it's linux 2.6.10 and greater but don't hold me to that, Fedora Core 4 is the same way :) initrd.img is now a cpio image, not a filesystem, so you don't have to loopmount it to make changes. # I assume the original ISO is exploded under /work-iso gzip -dc /work-iso/initrd.img >/tmp/initrd.img # Uncompress it mkdir /work-initrd; cd /work-initrd # make a place to extract it cpio -i </tmp/initrd.img # Extract it from cpio archive cp /YOUR_INFO_FILE info # Put your info file in there find . | cpio -H newc -o /tmp/initrd.img # make new initrd.img gzip -c /tmp/initrd.img >/work-iso/initrd.img # Put in iso dir run mkisofs against /work-iso to create a new ISO image with your info file in it. Since I've got initrd open anyway, I also poke my autoyast.xml file in there and add: AutoYaST: file:///autoyast.xml to the info file so the bootimage is 100% self contained. Hope that helps! Lee On Tue, 2005-08-23 at 13:48 +0200, Hans-Joachim Ehlers wrote: > Hi folks, > Give 9.3 Suse Pro > Booting from CD > Installation from Network > > > I would like to put the file "info" with is used by linuxrc on the > installation cd because using an additional floppy causes to much > trouble. > > But i am a little bit lost about howto do that. > > Do i have to change the isolinux.cfg ? > Documentation tells me that the info file should be in initrd but i can > not find that directory. ? > > Any tips ? > tia > Hajo > > > > > > > ============================ > Hans-Joachim Ehlers > UNIX Systems Engineer > EUMETSAT > Am Kavalleriesand, 31 > 64295, Darmstadt, Germany > Tel : +49 6151 807-7307 > eMail : hansjoachim.ehlers(a)eumetsat.int > iNet : www.eumetsat.de > -- Lee Mayes <autoinst(a)mayeses.com>

1 0

Forcing disc mount points during install/after install [SP 9.3]
by Marlier, Ian 24 Aug '05

24 Aug '05

Hey, all -- Trying to set up autoinstall for a number of servers with the following discs: 80 GB SATA attached to an onboard SiL SATA controller (uses sata_sil module) 80 GB SATA attached to the same SiL SATA controller 678 GB RAID-5 attached to a 3Ware 9500-series SATA controller (uses 3w-9xxx module) I've got the partition set up complete and it should be working fine, but I'm having technical difficulty getting it to actually install. Specifically: the two 80GB disks should be imported as /dev/sda and /dev/sdb (both during installation and afterwards). But they're not. The array exported from the 3Ware card is always mounted as /dev/sda (and, what's more, gets the grub stuff installed on it, along with the /boot partition). What I would like to do is change the order in which the disks are imported. I need the onboard disks to be mounted first, and the 3ware array to be mounted afterward. I would like the final configuration to be something like this: 80 GB onboard as /dev/sda: 100 MB ext3 partition as /boot 2 GB swap partition as swap max Linux-RAID partition 80 GB onboard as /dev/sdb: 100 MB ext3 partition as /boot-secondary (synced w/ unison from /boot) 2 GB swap partition as swap Max Linux-RAID partition Linux raid partitions joined as /dev/md0(RAID-1): Max ext3 partition as / 678 GB RAID-5 array as /dev/sdc: 678 LVM partition with 278 GB ext3 partition allocated and mounted as /space Leaving out, for the moment, the fact that this setup is kind of weird: Anyone have thoughts on how I might get the stupid boot order to change? Is there a way to specify that the hardware probe should check for SiL controllers before it checks for 3ware controllers? Help? Please? Thanks, Ian

1 0

SLES9-SP1 autoyast not setting proxy-config correctly
by suselist＠nlsn.nu 24 Aug '05

24 Aug '05

Hi all, Are there any known bugs in autoyast for SLES9-SP1 that affects proxy-config? Our profiles set proxy, but its not set after install. / Daniel

4 3

Adding the file "info" to an bootable CD/DVD
by Hans-Joachim Ehlers 23 Aug '05

23 Aug '05

Hi folks, Give 9.3 Suse Pro Booting from CD Installation from Network I would like to put the file "info" with is used by linuxrc on the installation cd because using an additional floppy causes to much trouble. But i am a little bit lost about howto do that. Do i have to change the isolinux.cfg ? Documentation tells me that the info file should be in initrd but i can not find that directory. ? Any tips ? tia Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 eMail : hansjoachim.ehlers(a)eumetsat.int iNet : www.eumetsat.de

3 2

autoyast locked users with command file
by Evan Bills 22 Aug '05

22 Aug '05

Hello, Is there a way to setup locked users with Autoyast? What I'm looking for is something similar to the command: 'passwd -l user' I can script this in, but would rather use real command file tags if they exist, and I'm not seeing a reference to them in the documentation. Thanks all! ~Evan Bills

1 0

Question about ndiswrapper
by Malcom Kemp 21 Aug '05

21 Aug '05

This may be a little off subject, but if someone could point me in the right direction, I would appreciate it. I have 9.3 and am trying to get an unsupported WAN card to work. I have used Yast to install the ndiswrapper package, which it does. I have used the -i to install the driver, and with the -l option it tells me it is there and that it looks correct. When I try to modprobe ndiswrapper however, it gives me fatal error, "Module ndiswrapper not found". I removed the package and reinstalled it, but still have same error. How do I get the kernel module put on the system?

1 0

Re: [suse-autoinstall] SLES9 + autoyast2
by Michael Marion 18 Aug '05

18 Aug '05

On 18 Aug, fisch wrote: > I want to create an autoyast config file from my system - is there any > way to import the complete system configuration? They removed the clearly understood "clone system" when sles9 came out.. but you can still do it. Start yast2, under Misc choose Autoinstallation, then Under "tools" choose "create reference profile." Now comes the completely non-intuitive part... do NOT check the boxes of the things you want cloned into the resulting xml file. If you check it, it then makes those bits "reference" settings. So basically, if you just leave everything unchecked, and click the "create" button, it should clone your system. You'll go back to the previous display and can now look at things like partitioning, or software, and see that it's set to the system's settings. Then you can save the file from the "file" menu. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Alcohol and Calculus don't mix. Never drink and derive. ==> Another /. gem

1 0

SLES9 + autoyast2
by fisch 18 Aug '05

18 Aug '05

hi, I want to create an autoyast config file from my system - is there any way to import the complete system configuration? bye fisch

1 0

FYI: Configured xinetd service not active.
by Hans-Joachim Ehlers 18 Aug '05

18 Aug '05

Problem. Configured xinetd service not active. Given from autoinst.xml created by autoyast ... <conf> <protocol>tcp</protocol> <script>rsh</script> <server>/usr/sbin/in.rshd</server> <service>shell</service> </conf> ... After automatic installation the service is not active: Extract from /etc/xinetd/rsh ... service shell { # server_args = /usr/sbin/in.rshd -L disable = yes ... } The yast log tells me: .... "inetd":$["last_created":0, "netd_conf":[$["protocol":"tcp", "script":"rsh", "server":"/usr/sbin/in.rshd", "service":false]], .... Solution: Found in the autoyast.pdf Guide: Add <enabled config:type="boolan">true</enabled> by hand. Since "yast autoyast" does not add this line to the xml file i would suggest it as a bug from what i know about autoyast. hth Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 eMail : hansjoachim.ehlers(a)eumetsat.int iNet : www.eumetsat.de

4 3

RE: [suse-autoinstall] FYI: Configured xinetd service not active.
by fraser_bailey＠agilent.com 18 Aug '05

18 Aug '05

This has never worked since SUSE 9 started. -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Thursday, August 18, 2005 11:31 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] FYI: Configured xinetd service not active. On Thursday 18 August 2005 12:29, Martin Vidner wrote: > > Problem. Configured xinetd service not active. > > I will forward the report. Which product release is it? I check that too at the moment. At least SL10 beta1 is broken too. I try beta2 now (have to install it first on my test machine). -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Re: [suse-autoinstall] FYI: Configured xinetd service not active.
by Hans-Joachim Ehlers 18 Aug '05

18 Aug '05

Suse Pro 9.3 with autoyast2-installation-2.11.14-0.1 autoyast2-2.11.14-0.1 autoyast2-utils-2.11.14-0.1 hth Hajo >>> Martin Vidner <mvidner(a)suse.cz> 08/18/05 12:29 pm >>> On Thu, Aug 18, 2005 at 11:29:16AM +0200, Hans-Joachim Ehlers wrote: > Problem. Configured xinetd service not active. I will forward the report. Which product release is it? -- Martin Vidner, YaST developer SuSE CR, s.r.o. e-mail: mvidner(a)suse.cz Drahobejlova 27 tel:+420-296542390 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 eMail : hansjoachim.ehlers(a)eumetsat.int iNet : www.eumetsat.de

1 0

Display the currently loaded config-file
by Guido Kölsch 18 Aug '05

18 Aug '05

Hi, is it possible to add a label to the autoyast-module, where the currently loaded xml-file is displayed? It's a bit confusing if you have a large amount of files to edit. thanks, -- ------------------------------------------------------------------------ Guido Kölsch Max-Planck-Institut fuer Radioastronomie Phone: +49 (0)228 525 164 Auf dem Huegel 69, D-53121 Bonn, Germany FAX : +49 (0)228 525 229 email: gkoelsch(a)mpifr-bonn.mpg.de ------------------------------------------------------------------------

2 1

SLES9: Reread of partition table failed
by John Clemens 18 Aug '05

18 Aug '05

I've got fully automated SLES9 installations almost working with our software (we provide a virtualized system, with virtual network and virtual disk). The only problem I've yet to solve is that the install pauses halfway through with the above error, making the user press ok to continue. When you do press ok, the install works fine, and the right partitions are set up and installed. Well, ok, that's not the only problem, but the others (network config not getting setup even though specified in the xml, and inittab trying to run getty's on tty1-6 even though its a serial port install) I think are solvable. This one however.. Looking at the yast2-storage source, it appears it's searching the fdisk output for WARNING (which fdisk prints out if the BLKRRPART ioctl fails). however, if i run fdisk manually on the system, and set up the partitions exactly the same way, I don't see that error. I've even gone so far as to mount the root install image via loopback/chroot and run that version of fdisk, and i still don't see that error message. So I don't know why yast, which seems to be reading the output of fdisk(?) would fail and trigger this dialog. Also, looking at the <report> section of my xml file, I see that errors, messages, and warnings are all set to timeout in 10 seconds. Why does this message not time out? Any thoughts? I'm including the partition section of the XML below my sig if it helps. Checking the archives it looks like something like this has happened before, but it seems it should have been solved years ago. I'm guessing I'm doing something wrong.. john.c - -- John Clemens jclemens(a)virtualiron.com <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>4.3GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>4.3GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>4.3GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>1,4</use> </drive> </partitioning>

2 4

network driver built into kernel?
by John Clemens 17 Aug '05

17 Aug '05

Hi, another quick question. Our virtual network driver is built into the kernel that we install. I'm like to set this up to use DHCP but default and come up on boot. I have this section in my XML file: <networking> <dhcp_options> <dhclient_additional_options>-B</dhclient_additional_options> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain>virtualiron.com</domain> <hostname>linux</hostname> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> </interfaces> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> I have also tried the above with this included: <modules config:type="list"> <module_entry> <device>eth0</device> <module>kveth</module> <options></options> </module_entry> </modules> In both cases, The autoinstall completes, but on first boot, it fails to configure eth0 (startup scripts after initial yast run, show 'eth0 ... unused'). If I manually go in after bootup and use yast to configure eth0 for dhcp, then it works fine. Looking at /var/log/YaST2/y2log (snippet below) it appears that all of these options are passed to yast2 correctly, and that dhcpcd finds the correct IP information, but because I don't have a module name specified it refuses to write out the configuration...? How can i specify that the network driver is really in the kernel and not to bother with trying to load a module? or is that not the problem? thanks, john.c 2005-09-17 15:55:22 <1> linux(509) [Interpreter] network/install.ycp:389 Calling YaST client lan_auto (arguments: ["Import", $["dhcp_options":$["dhclient_additi onal_options":"-B", "dhclient_hostname_option":"AUTO"], "dns":$["dhcp_hostname": true, "dhcp_resolv":true, "domain":"virtualiron.com", "hostname":"linux"], "inte rfaces":[$["bootproto":"dhcp", "device":"eth0", "startmode":"onboot"]], "routing ":$["ip_forward":false]]]) 2005-09-17 15:55:22 <1> linux(509) [YCP] clients/lan_auto.ycp:14 --------------- ------------------------- 2005-09-17 15:55:22 <1> linux(509) [YCP] clients/lan_auto.ycp:15 Lan autoinst cl ient started 2005-09-17 15:55:22 <1> linux(509) [YCP] clients/lan_auto.ycp:106 InstallInf($["bootproto":"dhcp", "gateway":"10.1.5.1", "hwaddr":"00:0f:4b:00:00:22", "installation":"yes", "ipaddr":"10.1.5.12", "nameserver":"10.1.1.3", "netmask":"255.255.255.0", "type":"eth"]) 2005-09-17 15:55:22 <1> linux(509) [YCP] Lan.ycp:1089 hw=[] 2005-09-17 15:55:22 <3> linux(509) [YCP] Lan.ycp:483 No HW info found: $[] 2005-09-17 15:55:22 <1> linux(509) [YCP] Lan.ycp:488 No detailed HW info: 2005-09-17 15:55:22 <4> linux(509) [YCP] Lan.ycp:503 hw=$[] 2005-09-17 15:55:22 <1> linux(509) [YCP] clients/lan_auto.ycp:218 hw from type = [] 2005-09-17 15:55:22 <3> linux(509) [YCP] network/hardware.ycp:308 Item not found in Hardware: 1 (0) 2005-09-17 15:55:22 <3> linux(509) [YCP] Lan.ycp:483 No HW info found: $[] 2005-09-17 15:55:22 <1> linux(509) [YCP] Lan.ycp:488 No detailed HW info: 2005-09-17 15:55:22 <4> linux(509) [YCP] Lan.ycp:503 hw=$[] 2005-09-17 15:55:22 <1> linux(509) [YCP] Lan.ycp:504 device= 2005-09-17 15:55:22 <1> linux(509) [YCP] network/routines.ycp:266 input=$["confi g":$["dhcp":$["DHCLIENT_ADDITIONAL_OPTIONS":"-B", "DHCLIENT_HOSTNAME_OPTION":"AU TO", "DHCLIENT_MODIFY_RESOLV_CONF":true, "DHCLIENT_SET_HOSTNAME":true]], "device s":$["":$["":$["BOOTPROTO":"dhcp", "STARTMODE":"onboot", "UNIQUE":"", "_type":"" ]]], "dhcp_options":$["dhclient_additional_options":"-B", "dhclient_hostname_opt ion":"AUTO"], "dns":$["dhcp_hostname":true, "dhcp_resolv":true, "domain":"virtualiron.com", "hostname":"linux"], "hwcfg":$["":$["MODULE":"", "MODULE_OPTIONS":"", "STARTMODE":"auto"]], "interfaces":[$["bootproto":"dhcp", "device":"eth0", "startmode":"onboot"]], "routing":$["ip_forward":false]] 2005-09-17 15:55:22 <1> linux(509) [YCP] clients/lan_auto.ycp:388 Lan auto finished . . . YaST client lan_auto (arguments: ["Write", $["dhcp_options":$["dhclient_additio nal_options":"-B", "dhclient_hostname_option":"AUTO"], "dns":$["dhcp_hostname":t rue, "dhcp_resolv":true, "domain":"virtualiron.com", "hostname":"linux"], "inter faces":[$["bootproto":"dhcp", "device":"eth0", "startmode":"onboot"]], "routing" :$["ip_forward":false]]]) 2005-09-17 15:55:24 <1> linux(509) [YCP] clients/lan_auto.ycp:14 --------------- ------------------------- 2005-09-17 15:55:24 <1> linux(509) [YCP] clients/lan_auto.ycp:15 Lan autoinst cl ient started 2005-09-17 15:55:24 <1> linux(509) [YCP] Lan.ycp:291 Writing configuration 2005-09-17 15:55:24 <1> linux(509) [YCP] NetworkModules.ycp:183 Writing configur ation 2005-09-17 15:55:24 <1> linux(509) [YCP] NetworkModules.ycp:189 OriginalMods=nil 2005-09-17 15:55:24 <1> linux(509) [YCP] NetworkModules.ycp:190 Mods=$["":$["MOD ULE":"", "MODULE_OPTIONS":"", "STARTMODE":"auto"]] 2005-09-17 15:55:24 <1> linux(509) [YCP] NetworkModules.ycp:199 Deleted=[] 2005-09-17 15:55:24 <1> linux(509) [YCP] NetworkDevices.ycp:262 Writing configur ation 2005-09-17 15:55:24 <1> linux(509) [YCP] NetworkDevices.ycp:268 OriginalDevs=nil 2005-09-17 15:55:24 <1> linux(509) [YCP] NetworkDevices.ycp:269 Devs=$[] 2005-09-17 15:55:24 <1> linux(509) [YCP] NetworkDevices.ycp:278 Deleted=[] 2005-09-17 15:55:24 <1> linux(509) [YCP] NetworkConfig.ycp:86 Writing configuration

1 1

Re: [suse-autoinstall] SLES9: Reread of partition table failed
by Hans-Joachim Ehlers 17 Aug '05

17 Aug '05

If you are starting from scratch without a partition table or with an invalid one you should use: <use>all</use> This should wipe the partition table. Also all partions should be formated. If you going to install additional Suse linux version to the other partitions then you there is no NEED anymore for partitioning. Of cource then you have to use the "rules.xml" Also if you define "/" you should also define swap ! ... -> <format config:type="boolean">true</format> .... .... <partition> <crypt>twofish256</crypt> -> <filesystem config:type="symbol">swap</filesystem> -> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> -> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> After these steps you should have 3 formated "/" partitions and a swap. where Partition 1 will be used as "/" and Partition 4 as swap. Partition 2 & 3 are free for use. hth Hajo >>> John Clemens <jclemens(a)virtualiron.com> 08/17/05 5:13 pm >>> On Wed, 17 Aug 2005, Uwe Gansert wrote: > On Wednesday 17 August 2005 16:46, John Clemens wrote: > >> The only problem I've yet to solve is that the install >> pauses halfway through with the above error, making the user press ok to > > I've never seen that error or heard of it until now. Thanks for responding.. >> <partitioning config:type="list"> >> <drive> >> <device>/dev/sda</device> >> <initialize config:type="boolean">true</initialize> > > you can try to set <initialize ...>false</initialize> > or do you really need it? Err, I assumed initialize meant wipe the partition table and start from scratch.. I'll go back to the documentation and see what it really does.. http://www.suse.de/~nashif/autoinstallation/9.1/html/CreateProfile.Partitio… doesn't seem to mention it. what exactly does it do? It was a checkbox in the yast autoinstall program i used to create the file. After trying it, it didn't give the reread failure, which is a nice step forward; but it did give me a timed out error message saying "error, partitions are not contiguous". and then another one claiming there was an error setting up the partitions, and the dumped me back to the linuxrc menu. >> <use>1,4</use> > > why is that? local convention.. in our test environment we have OS's on partition 1-3 and swap on partition 4. so I want to tell SLES to use partition 1 for the OS, and 4 for swap, and ignore the part 2 and 3. maybe that's causing the above problem. Let me try a few things now that I'm getting further. Thanks for the help. john.c -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Incorporating SLES-SP2 into an AutoYast installation source?
by Michael T. Halligan 16 Aug '05

16 Aug '05

Can anybody recommend a guide as to how I'd go about incorporating SLES SP2 into a SLES9 repository? I'm about to image a number of servers, and ideally would have them all come up fully patched, and ready to go. -- Michael T. Halligan Chief Technology Officer ------------------- BitPusher, LLC http://www.bitpusher.com/ 1.888.9PUSHER 415.724.7998 (Mobile) 415.520.0876 (Fax)

2 3

Adding New Package to Install
by Sean Siemsen 16 Aug '05

16 Aug '05

What Im Trying to do: Adding a package "scli-1.06.16-20.i386.rpm" to the install. What Ive done so far: I am using AutoYast to install SuSE 9.2. I have copied the rpm to the path2CD/suse/i586 folder. Deleted MD5SUMS, ran 'md5sum * > MD5SUMS'. Then I backed up to the path2CD/suse folder and ran 'create_package_descr -x path2CD/suse/setup/descr/EXTRA_PROV' command to rebuild the package database. I also read somewhere about updating the INDEX.gz and ls-lR.gz files in the main folder. (Do I need to do this every time I add a package to my custom CD with these commands? ie. update MD5SUMS, INDEX.gz, and ls-lR.gz files?) --------- cd /suse_9.2 rm INDEX.gz ls-lR.gz ls – lR > ls-lR gzip ls-lR find . > INDEX gzip INDEX --------- Problem: When I run the install it says "Package scli-1.06.16-20.i386 not found on medium. Details- Err 11283:ERROR(Medium: file not found)" I have read through the previous postings and found a simular posting. I followed the same steps in the posting and received the same error. He was trying to put his packages in the noarch folder. It worked for him when he put them in the i586 folder. He wanted to know why it didnt work in the noarch folder and the poster said maybe that was because the rpms were not noarch. I noticed my rpm is a i386. Does this have anything to do with my problem? I also noticed it didnt say "Package scli-1.06.16-20.i386.rpm" (with the .rpm) Thanks Sean Siemsen

1 0

Multiple issues with autoyast.
by GrueMaster 15 Aug '05

15 Aug '05

I need to be able to make an autoinstall for installing a minimal OS on multiple systems for testing. We are testing multiple Linux distributions, along with other OS's, averaging 10 installs/day. I don't have much control over the server, so we have to install via FTP. Getting the autoyast config is not the problem (verified Our hardware varies greatly, and is usually very bleeding edge (just got a new Pentium D EE with dual SLI NVidia 6600's). We also have workstations and servers, all with different drive controllers, etc (IDE, SATA, SCSI). I need to have an auto script that will just nuke & pave the existing drive, install, and run our generic postinstall script. I have Redhat, Fedora, and Mandriva working fine (although the varied hardware creates issues). With Suse 9.3, I am really having a rough time. I have finally gotten past all the errors from xmllint, but the install still hangs on "Error while configuriing partitions. Try again". Nothing seems to indicate an issue in the y2log, with and without the debug boot option. To start, I just want to complete an install. Here's my basic.xml file (sans post-install script). I have also tried several auto scripts that I have found on this mailing list. Any help would be greatly appreciated. Tobin --------------------------------- Yahoo! Mail for Mobile Take Yahoo! Mail with you! Check email on your mobile phone.

2 3

using autoyast to install SLES8 and SLES9 on one machine
by André Weidemann 12 Aug '05

12 Aug '05

Hello list, I'm trying to install SLES8 and SLES9 on one machine. I'm starting with a SLES8 installation where all partitions are being created. (for both SLES8 and SLES9) The machine will have the following partitions: 2 x /boot 1 x swap 1 x extended 2 x / (root) 2 x /usr 2 x /var LVM1 LVM2 LMV3 The autoinstall for SLES8 creates all the above partitions and is running through the autoinstall process without any hassle. After this I'm trying to install SLES9 with autoyast on the same machine. Yast reads it's config and is starting with the partition process. Everything is set up so that yast should use all existing partitions and thus not create any new ones. I only set up 3 or 4 partitions to be formated. When the partition process starts, yast complains that the boot partition is not within the first 1024 cylinders although it ranges from 26-50. After this point yast is displaying the progress bar for setting up the partititions but the bar does not move a single percent. Has anyone else ever tried to do something similar? Any hints on what I can do to make the installation go past the partitioning? Thanx a lot in advance. André.

3 2

Re: [suse-autoinstall] Tracking an error during installation
by Mitko Haralanov 11 Aug '05

11 Aug '05

On Wed, 10 Aug 2005 09:14:17 +0200 "Hans-Joachim Ehlers" <HansJoachim.Ehlers(a)eumetsat.int> wrote: > 1) Set installation mode to text or press F2 on the initial boot > screen > Reason: During network installation of Suse 9.3 ( but booting from DVD > ) i have got every time a error message saying something about > ./var/...X11/.. missing > Solution is to use Textmode ( F2) or F5 but NOT F3(640*480 ) - F5 i > never testet. > > 2) > use a simple "default" XML so your autoyast entry should look like: > .../default Well, I found out something interesting today! I am pretty sure it is not the XML file that is the problem. I tried using previous revisions of the XML file (ones that I know work) and I get the same error. Could the problem be somewhere in the installer or kernel/initrd images? -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== I bet the human brain is a kludge. -- Marvin Minsky

1 1

Latest news from a Suse 9.3 Network installation ( no interface error message )
by Hans-Joachim Ehlers 11 Aug '05

11 Aug '05

After configuring the Section "Network Devices" - Netowork Card and starting the installation again: Error Message: ~ DHCP-Server can not be configured - no interface ~ LDAP Client can not be configured .. ~ Kerberos can not be configured .. The point is: I newer configured these Services. Taking a look into the xml file: These service has been added to the xml file by autoyast. Its looks like that they are just dummy entries BUT they are added before the Section <networking> subsection <interfaces> Its real fun to install Suse 9.3 Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 eMail : hansjoachim.ehlers(a)eumetsat.int iNet : www.eumetsat.de

3 2

Partioning in autoyast XML file changes from 9.1 to 9.3?
by Tom Scholl 11 Aug '05

11 Aug '05

Hello everybody, I've been trying to upgrade all our Suse 9.1 machines to 9.3 using autoyast, but the XML configuration is giving me a few headaches... Any light anyone could shed on this would be greatly appreciated :) For our 9.1 install, we had this for our partioning section: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <create config:type="boolean">false</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> </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">5</partition_nr> </partition> </partitions> </drive> </partitioning> Which worked as expected: didn't create any new partitions, just formatted & re-used hda1 and hda5 as root and swap respectively. Now, with the exact same section, it seems from the log file that hda1 is automatically used as a /boot partition, leaving no root partition. I don't want a seperate boot partition, and don't know how I can tell it not to do this. (If this is what it is doing). Thanks, Tom Scholl references: my autoyast XML file - http://www.tcm.phy.cam.ac.uk/~tws26/ay.xml 300K log file from autoyast - http://www.tcm.phy.cam.ac.uk/~tws26/messages

2 2

Partition Problems
by Sean Siemsen 11 Aug '05

11 Aug '05

I have read the archives and cannot find a simular problem. I want to create an auto-install CD that uses all available space on the disk. I want to create these partitions: swap - 2GB / - 6GB /boot - 2GB /home - max(The rest of the drive) ... its a 36GB SCSI. After the install i do a "df -h" to get these values for my partition. rootfs - 2.0G - / tmpfs - 2.0G - / /dev/loop0 - 155M - /mounts/instsys /dev/hdc - 340M - /var/adm/YaST/InstSrcManager/....... /dev/sda2 - 773M - /mnt /dev/sda3 - 259M - /mnt/boot /dev/sda4 - 3.1G - /mnt/home I noticed, however, that if before I boot from the CD, I run fdisk /dev/sda, and clear the partition table, THEN boot from the CD I get the partition sizes I want. In AutoYast I selected to initialize the drive, and to "Reuse all existing partitions". It is a requirement that I have no user interaction setting up these machines with SuSe, and I dont want to have to clear out the partition table before I boot with the install CD every time. Here is my partitioning section. Anyone see what I'm doing wrong? Is there a way to run fdisk and clear it out automatically before Yast probes the hard drives? I know the pre-install scripts run after the probe and the rules suggestion in previous postings do not work either. Thanks in advance. <partitioning config:type="list"> <drive> <device>/dev/sda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_type>primary</partition_type> <size>2GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>6GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>2GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/home</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning>

2 1

rules.xml
by Hans-Joachim Ehlers 11 Aug '05

11 Aug '05

Hi folk, i am back again. Given: ./autoinst/default ( default xml file for installation - with section for Hostname and IP ) ./autoinst/rules/rules.xml ./autoinst/host01.xml ( Contains Hostname and IP in a valid xml structure ) So far i have a valid and working rules.xml which will add the host01.xml to the /tmp during installation but it does not add the ./autoinst/default xml. So the installation will stop. I did not found any information about adding a default profile IF you are using a rules.xml Is there is any include directive or some kind of default in the rules.xml ? Right now i am using a second rule to include the default xml file 295$ cat rules.xml <?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> <custom1> <script> <![CDATA[ #!/bin/sh hostname=$( cat /proc/cmdline | tr " " "\n" | awk '{ if ( $1 == "hostname" ) print $2 }' FS="=" ) echo -n $hostname ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/@custom1@.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom1> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>default</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> tia Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 eMail : hansjoachim.ehlers(a)eumetsat.int iNet : www.eumetsat.de

2 1

<network_needed>
by Johan Hansson 11 Aug '05

11 Aug '05

Hi I'm currently setting up an autoyast environment running SLES9 SP2 ( x86_64 ). The autoyast server has the sources and configuration available via http. During the post-installation phase I discovered a problem. When running the post-install script I want to add an installation source for installation of my own supplemental packages. ( running /usr/bin/installation_sources -e -a http://myserver/supplemental ) To be able to fetch the post-install script I've used the <network_needed config:type="boolean">true</network_needed> which seems to bring the interface up, but for some reason it doesn't add the default gateway and when there is no gateway the script can't connect to the nameserver to resolve the hostname of the server that has the sources. installation_sources command fails. I don't want to use the IP-address when adding the installation_sources. Anyone have an idea of how to solve this? Johan

2 1

Re: [suse-autoinstall] Tracking an error during installation
by Hans-Joachim Ehlers 10 Aug '05

10 Aug '05

Hi Mitko, maybe you missed my first email. For debuging: 1) Set installation mode to text or press F2 on the initial boot screen Reason: During network installation of Suse 9.3 ( but booting from DVD ) i have got every time a error message saying something about ./var/...X11/.. missing Solution is to use Textmode ( F2) or F5 but NOT F3(640*480 ) - F5 i never testet. 2) use a simple "default" XML so your autoyast entry should look like: .../default hth Hajo >>> Mitko Haralanov <mitko(a)pathscale.com> 08/09/05 11:06 pm >>> On Mon, 8 Aug 2005 14:05:08 -0700 Mitko Haralanov <mitko(a)pathscale.com> wrote: > I looked at the log file and I did not see anything that stood > out. Just in case, I am attaching my xml file (slightly edited for > privacy). > > I also tried attaching the y2log file but the mailing list > rejected it since it was too big... I one more thing that could be the problem: on the ALT-F3 screen/console, there are the following messages: starting setctsid "showconsole" inst_setup yast error setting kbd mode: Invalid argument install program exit code is 137 Could this be the problem that needs to be solve? And if yes, how can I change the kbd mode? Changing the values for the <keyboard> parameter does not seem to help... -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== 98. What the hell!? --Top 100 things you don't want the sysadmin to say -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 eMail : hansjoachim.ehlers(a)eumetsat.int iNet : www.eumetsat.de

2 1

RE: [suse-autoinstall] Tracking an error during installation
by Meyers, Holger 09 Aug '05

09 Aug '05

This kind of generic error usually happens if the xml file is incorrect. Ether post your file or check /var/log/YaST2/y2log* of the installation system (ALT-F2 has a shell) for errors. Mit freundlichen Grüßen / kind regards SoftService GmbH Holger Meyers Consulting Tel 0211 977 09 69 Fax 0211 977 09 27 http://www.softservice.de > -----Original Message----- > From: Mitko Haralanov [mailto:mitko@pathscale.com] > Sent: Friday, August 05, 2005 6:38 PM > To: suse-autoinstall(a)suse.com > Subject: Re: [suse-autoinstall] Tracking an error during installation > > Still no ideas? Because of this problem, I am pretty > much stalled and I really need to get it going. Any help will > be appreciated!! > > Thanx > > On Thu, 4 Aug 2005 16:02:32 -0700 > Mitko Haralanov <mitko(a)pathscale.com> wrote: > > > On Thu, 4 Aug 2005 15:46:59 -0700 (PDT) Michael Marion > > <mmarion(a)qualcomm.com> wrote: > > > > > Assuming you're doing an nfs mount yourself in a script? > If so, add > > > the options -o ro,nolock after mount and it'll fix it. > > > > Unfortunately, this is not exactly the case! The > autoyast/kickstart > > process is done over nfs but I am not doing a manual nfs mount. The > > error message comes up as soon as the autoyast/kickstart process > > switches to the (pseudo-) graphical mode (presumably, when > it tried to > > get the kickstart xml file from the > > server) > > > > -- > > Mitko Haralanov > > mitko(a)pathscale.com > > http://www.pathscale.com > > > > ========================================== > > TRANSACTION CANCELLED - FARECARD RETURNED > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > > -- > Mitko Haralanov > mitko(a)pathscale.com > http://www.pathscale.com > > ========================================== > UNIX was half a billion (500000000) seconds old on > Tue Nov 5 00:53:20 1985 GMT (measuring since the time(2) epoch). > -- Andy Tannenbaum > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > >

2 2

Re: [suse-autoinstall] Tracking an error during installation
by Michael Marion 08 Aug '05

08 Aug '05

On 4 Aug, Mitko Haralanov wrote: > lockd: failed to open /var/lib/nfs/state: err=-2 > > Anyone have an idea why this would be showing up and whether it > is the problem? Assuming you're doing an nfs mount yourself in a script? If so, add the options -o ro,nolock after mount and it'll fix it. If it's autoyast.. not sure what to say as it should know better. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com "There are no significant bugs in our released software that any significant number of users want fixed." - Bill Gates in an interview with Focus magazine, Oct 23, 1995.

3 4

Tracking an error during installation
by Mitko Haralanov 08 Aug '05

08 Aug '05

I am trying to kickstart a machine using a kickstart xml file that I have use multiple times before. However, for some unknown reason this time around, I get an error message: "An error occured during the installation" Putting aside my admiration for how wonderfully helpful that error message actually is, I can't seem to find a way to figure out what is actually wrong so I can fix it. Could someone, please tell me where to look to find what actually went wrong? Thanx -- Mitko Haralanov mitko(a)pathscale.com http://www.pathscale.com ========================================== Any sufficiently advanced bug is indistinguishable from a feature. -- Rich Kulawiec

2 2

Re: [suse-autoinstall] Suse 9.3 Pro Network installation
by Hans-Joachim Ehlers 08 Aug '05

08 Aug '05

Hi Uwe, In manuel installation i have no problem. Could it be that suse copys a special amount of files during installation to the ramdisk ? Either way i will try a network installation with a swap disk of 2GB of size. BTW: Also i have set in the "info" file the option "textmode: 1" so i do not get these /var/..X11... does not exist cu Hajo >>> Uwe Gansert <ug(a)suse.de> 08/08/05 10:00 am >>> On Saturday 06 August 2005 02:11, Hans-Joachim Ehlers wrote: > Given: Boot from DVD , info file on floppy > Installation starts fine if i Press F5 before booting . Software is > getting installed but then after a while its slowes down until the > system looks like under 110% load. > > On the next run i swiched to a console and started top. It was quiet > nice to see how 500 MB of RAM and 1GB of swap space has been eaten like > sick. > > y2base has used about 200 MB ( 3 instances ) on the first and last look > today. If anyone can help i would appreciate it. which version auf SUSE Linux do you use? I never heard of that problem before. I assume you can do a manual installation without any problems? -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Suse 9.3 Pro Network installation
by Hans-Joachim Ehlers 08 Aug '05

08 Aug '05

Giving up for today. Given: Boot from DVD , info file on floppy Installation starts fine if i Press F5 before booting . Software is getting installed but then after a while its slowes down until the system looks like under 110% load. On the next run i swiched to a console and started top. It was quiet nice to see how 500 MB of RAM and 1GB of swap space has been eaten like sick. y2base has used about 200 MB ( 3 instances ) on the first and last look today. If anyone can help i would appreciate it. cu Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 eMail : hansjoachim.ehlers(a)eumetsat.int iNet : www.eumetsat.de

2 2

"Re: [suse-autoinstall] Tracking an error during installation"
by Hans-Joachim Ehlers 05 Aug '05

05 Aug '05

Hi folks, my first email to this list. I do not know how to enable tracking during installation but i have had a similar problem with Suse 9.3 Professional. My problem went away as soon as i pressed F5 ( 1024...) and THEN started the installation process. Maybe the X-Server does not like the low resolution ( Maybe still in text mode ? ) Anyway. If you are using remote boot i am stuck at this point. hth Hajo ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 eMail : hansjoachim.ehlers(a)eumetsat.int iNet : www.eumetsat.de

1 0

Using a dd image to install with AutoYaST
by Francois, Jean (J.L.) 05 Aug '05

05 Aug '05

I hope this turns out to be an easy question. I want to do the following: 1. Install a GOLD server with SLES9 SP2 2. shutdown the server, take out the drive and mount it in another server 3. do "dd if=/dev/sdb of=sles9sptinstall.img conv=sync" 4. Use that image to stage from AutoYaST 5. Have AutoYaST reconfigure network, hostname, etc. Now I have been trying to use the docs on Anas website and I am still having difficulty with the steps above #4 and getting this to work. If anyone can shed some light on what I am missing, point me to a FAQ, or give me a link to an archive where this has been discussed, it would be appreciated. I would prefer to use AutoYaST instead of something like g4l with homegrown scripts to accomplish this. thanks -- JLF Sends... Server Engineering/EE - Does the customer need a diskette drive? The x460 does not have a diskette drive. If a diskette drive is required, a USB diskette drive such as the IBM USB portable Diskette Drive (05K9276) can be used. http://www-1.ibm.com/esar/esarhome.nsf/getdoc?OpenForm&doc=PH8HPH8-137

2 1

Disappearing LDAP values in Pro 9.2 autoinstall
by Marlier, Ian 04 Aug '05

04 Aug '05

Hi, all -- I'm working on adding an LDAP Client configuration section to my autobuild scripts for SuSE Pro 9.2, and I'm having a funny little issue with disappearing values. Specifically, after the machine is built, LDAP authentication doesn't work. An LDAP user attempting to log in gets the message that his/her account doesn't exist. If I pull up YaST and look at the LDAP Client configuration section (under Network Services), the following values are selected: Use LDAP (this is correct) LDAP base DN: dc=example,dc=com (this is wrong) LDAP Server: 127.0.0.1 (this is wrong) LDAP TLS/SSL (this is wrong) Everything in the Advanced Configuration section is configured correctly. Wondering if anyone else has experienced this... The LDAP section of my rules is: <ldap> <base_config_dn>ou=ldapconfig,dc=subdomain,dc=studentuniverse,dc=com</ba se_config_dn> <bind_dn>cn=AnAdmin,dc=subdomain,dc=studentuniverse,dc=com</bind_dn> <create_ldap config:type="boolean">false</create_ldap> <file_server config:type="boolean">false</file_server> <ldap_domain>dc=subdomain,dc=studentuniverse,dc=com</ldap_domain> <ldap_server>10.0.0.2, 10.0.0.3</ldap_server> <ldap_tls config:type="boolean">false</ldap_tls> <ldap_v2 config:type="boolean">false</ldap_v2> <member_attribute>member</member_attribute> <nss_base_group></nss_base_group> <nss_base_passwd></nss_base_passwd> <nss_base_shadow></nss_base_shadow> <pam_password></pam_password> <start_ldap config:type="boolean">true</start_ldap> </ldap> Thanks, Ian

1 0

RE: [suse-autoinstall] rules.xml Example Files (SuSE 9.3)
by Ness, Todd 04 Aug '05

04 Aug '05

There was an example about a year ago... Hi, since several people requested the example set, I put it on the web. You can download it here: http://www.bio.ifi.lmu.de/~steiner/ayex.tgz dhcpd.conf - part for using pxelinux fstab.zassenhaus - example fstab to create partition profile info - specific info file for the initrd lilo-i386.xml - lilo profile lmu.xml - my standard profile makeInfo - put the info file into the SuSE initrd transferer by pxelinux makePartition - create a partition profile from an fstab part_zassenhaus_keep.xml - the partition profile created from the fstab.zassenhaus pxelinux.cfg - the pxelinux.cfg. Needs pxelinux.0, and "linux" and "initrd" from boot/loader/ rules.xml - put the profiles together. Have fun! 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. * -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Tuesday, August 02, 2005 2:18 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] rules.xml Example Files (SuSE 9.3) On Monday 01 August 2005 23:12, Charles Smith wrote: > Uwe Gansert wrote: > > what about: > >http://yast.suse.com/autoinstall/9.1/html/rulesandclass.html#rules > > > >the first "Simple rules file" should cover your needs (maybe with a > >"<continue config:type="boolean">true</continue>" for more rules to > > process. > > That's what I've been looking at, but again, I was wanting to provide > classes rather than complete profiles. It doesn't really explain the > syntax for doing that. a rule does not have to fetch a complete profile. You can fetch multiple parts of a profile by the use of multiple rules and those parts will be merged at the end to the complete profile (maybe that's not clear by the examples). If it makes you happy, put class_names into those - should work. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

RE: [suse-autoinstall] Antwort: Re: [suse-autoinstall] sles 9 installation Source in autoyast.xml [Virus checked]
by fraser_bailey＠agilent.com 03 Aug '05

03 Aug '05

Here's a script we use. It works through a template and replaces the values which it finds with values which the use types in. You will obviously need to modify your template of modify this script to match the values in your template, but you shoudl get the general idea. No warranty or support caveat emptor applies: #!/usr/bin/perl use Getopt::Long; $basedir = '/SuSE/tftpdir/suse'; (my $progname = $0) =~ s/.*\///; # basename $0 $useage = qq{ Summary: $progname creates the xml install configuration specifically for a host Example Command: Build XML for t13s1d2 in lab 13 $progname --hostname=t13s1d2 --ip=10.224.34.136 --subnet=255.255.255.192 --network=10.224.34.128 --broadcast=10.224.34.191 --gateway=10.224.34.129 --rel ease=C.08.10.00052 --template=dsp.xml This command will create 10.224.34.136.xml in $basedir for the install to us e once it's started. Options list --ip: IP address for the system to use once it's installed. --hostname: Host name for the system. --broadcast: Network broadcast address. --subnet: Subnet mask. --network: Base network address. --gateway: Default gateway. --release: The release version of the xml template to use. --template: The name of the template to use. --help: Show this help. }; if (not @ARGV) { warn $useage; exit 0; } GetOptions( 'ip=s' => \$ip, 'hostname=s' => \$hostname, 'broadcast=s' => \$broadcast, 'subnet=s' => \$subnet, 'network=s' => \$network, 'gateway=s' => \$gateway, 'release=s' => \$release, 'template=s' => \$template, 'help' => \$help ) or exit 1; # mandatory option check if ($help) { warn $useage; exit 0; } print "[ERROR] must specify --ip\n" unless $ip; print "[ERROR] must specify --hostname\n" unless $hostname; print "[ERROR] must specify --broadcast\n" unless $broadcast; print "[ERROR] must specify --subnet\n" unless $subnet; print "[ERROR] must specify --network\n" unless $network; print "[ERROR] must specify --gateway\n" unless $gateway; print "[ERROR] must specify --release\n" unless $release; print "[ERROR] must specify --template\n" unless $template; exit 0 unless ($ip and $hostname and $broadcast and $subnet and $network and $ga teway and $release and $template); # read the template into memory open(TEMPLATE, "<$basedir/$release/$template.xml") or die "[FATAL] unable to ope n $basedir/$release/$template.xml for reading: $!\n"; @template = <TEMPLATE>; close(TEMPLATE); # process the template and create the output file open(XML, ">$basedir/$ip.xml") or die "[FATAL] unable to open $basedir/$ip.xml f or writing\n"; foreach $line (@template) { if ($line =~ m#<hostname>\S+</hostname>#) { $line = "<hostname>$hostname</hostname>\n"; } if ($line =~ m#<broadcast>192.168.0.255</broadcast>#) { $line = "<broadcast>$broadcast</broadcast>\n"; } if ($line =~ m#<ipaddr>192.168.0.200</ipaddr>#) { $line = "<ipaddr>$ip</ipaddr>\n"; } if ($line =~ m#<netmask>255.255.255.0</netmask>#) { $line = "<netmask>$subnet</netmask>\n"; } if ($line =~ m#<network>192.168.0.0</network>#) { $line = "<network>$network</network>\n"; } if ($line =~ m#<gateway>192.168.0.254</gateway>#) { $line = "<gateway>$gateway</gateway>\n"; } if ($line =~ m#<user_password>shippingpassword</user_password>#) { $line = "<user_password>wackypassword</user_password>\n"; } print XML $line; } close(XML); print "[INFO] $basedir/$ip.xml created\n"; tsduser3:fraserb$ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

PAM Config using autoyast
by Tim Verhoeven 02 Aug '05

02 Aug '05

Hi, Is there a possibility to configure the pam configfiles using autoyast ? I would like to enable the pam_mkhomedir module for certain services and I prefer to avoid things like copying over files or playing with sed and co. I've searched a bit but I could not find anything usefull. Thanks, Tim -- Tim Verhoeven - dj(a)rootshell.be - 0479 / 88 11 83 /* This is total bullshit: */ linux-2.6.6/drivers/video/sis/init301.c

1 0

RE: [suse-autoinstall] rules.xml Example Files (SuSE 9.3)
by Ness, Todd 02 Aug '05

02 Aug '05

There was an example about a year ago... -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Tuesday, August 02, 2005 2:18 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] rules.xml Example Files (SuSE 9.3) On Monday 01 August 2005 23:12, Charles Smith wrote: > Uwe Gansert wrote: > > what about: > >http://yast.suse.com/autoinstall/9.1/html/rulesandclass.html#rules > > > >the first "Simple rules file" should cover your needs (maybe with a > >"<continue config:type="boolean">true</continue>" for more rules to > > process. > > That's what I've been looking at, but again, I was wanting to provide > classes rather than complete profiles. It doesn't really explain the > syntax for doing that. a rule does not have to fetch a complete profile. You can fetch multiple parts of a profile by the use of multiple rules and those parts will be merged at the end to the complete profile (maybe that's not clear by the examples). If it makes you happy, put class_names into those - should work. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nürnberg, Germany e-mail: uwe.gansert(a)suse.de, Tel: +49-(0)911-74053-0, Fax: +49-(0)911-74053-476, Web: http://www.suse.de -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

sles 9 installation Source in autoyast.xml [Virus checked]
by Matthias.Eble＠kaufland.de 02 Aug '05

02 Aug '05

Hi list, is it possible to set the url of the installation source in the autoyast xml file? I use kernel parameters like install=http://IP/sles9 autoyast=http://IP/sles9.xml for installation at the moment. The only use of autoyast=http://IP/sles9.xml would be nice. The automatic generation of the xml file didn't succeed. When I tried to generate a reference profile and activated the partitioning resource (I installed on LVM) no Partition configs were actually written. My solution was to copy the data from a former generated SuSE 9.3 xml file. Additionally i couldn't find a possibility to set the root password in the dialog. The username root is not permitted in the "Security and users" -> "edit and create" tab. So I also took the values from the 9.3 file, too. I installed recent patches yesterday: autoyast2-2.9.53-0.2 autoyast2-utils-2.9.45-0.2 autoyast2-installation-2.9.53-0.2 thank you matthias

2 3

rules.xml Example Files (SuSE 9.3)
by Charles Smith 02 Aug '05

02 Aug '05

Hello, I've been autoinstalling for a long time, but haven't been using the rules system. I would like to start, but am having trouble understanding how you write a rules file which has multiple rules that will match and return different class files, based on things like hardware specs and hostid netmask, and merge to a profile at the end. Can someone send me example rules file(s) which are at least somewhat similar? I'm having a hard time finding example files online that do similar to what I want. If I see enough example files I can figure it out. Basically, I want to do things like these: If hard drive is smaller than x, result class DiskSize / IDE_Small.class If hard drive is bigger than x, result class DiskSize / IDE_Large.class If hostid is C0A8000* result class Roles / Server.class If hostid is C0A8004* result class Roles / Workstation.class Is this possible, or do you have to write profiles which specify classes, and use the <profile> tag in the result? I've read all of nashif's autoinstall page for 9.1 page but I think I just need examples of more scenarios. Also, am I right in thinking that as of 9.2, you don't have to have separate profiles for 32 and 64 bit machines? Playing around with it, it seems to just figure it out on its own... Thanks in advance, -Charles

3 4

Auto detection of sound card
by Michael Blandford 01 Aug '05

01 Aug '05

Hello, I am trying to use autoyast to install SLES9 on a wide variety of hardware. Is there an easy way to have autoyast detect and configure the sound card without intervention? Thanks, Michael

2 1