openSUSE Autoinstall December 2005

autoinstall@lists.opensuse.org

24 participants
25 discussions

by Teun

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

15 years, 2 months

Problem with AutoInstallRules.ycp and merge.xslt

by Luzian Scherrer

Hello, I think there is a typo in AutoInstallRules.ycp (version 1.34.4.9 that comes with SLES9 SP2): the xsltproc to merge classes is called with the following param there (line 733): --param dontmerge \"'package, addon'\" and I'm quite sure that it sould be: --param dontmerge \"'package'\" --param dontmerge2 \"'addon'\" The result of this typo is that neither <package> nor <addon> are correctly aggregated, which is the desired effect I believe and I also hope. Quick demonstration: idhpb02:/ # cat /tmp/a.xml <?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> <software> <addons config:type="list"> <addon>addon-A</addon> </addons> <packages config:type="list"> <package>package-A</package> </packages> </software> </install> </profile> idhpb02:/ # cat /tmp/b.xml <?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> <software> <addons config:type="list"> <addon>addon-B</addon> </addons> <packages config:type="list"> <package>package-B</package> </packages> </software> </install> </profile> Calling it the wrong way: idhpb02:/ # xsltproc --novalid --param replace "'false'" --param dontmerge "'package, addon'" --param with "'/tmp/b.xml'" /usr/share/ autoinstall/xslt/merge.xslt /tmp/a.xml <?xml version="1.0"?> <ns1:profile xmlns:ns1="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns="http:// www.suse.com/1.0/yast2ns"> <ns1:install> <ns1:software> <ns1:addons config:type="list"> <ns1:addon>addon-B</ns1:addon> </ns1:addons> <ns1:packages config:type="list"> <ns1:package>package-B</ns1:package> </ns1:packages> </ns1:software> </ns1:install> </ns1:profile> Calling it the (as I think) right way: idhpb02:/ # xsltproc --novalid --param replace "'false'" --param dontmerge "'package'" --param dontmerge2 "'addon'" --param with "'/ tmp/b.xml'" /usr/share/autoinstall/xslt/merge.xslt /tmp/a.xml <?xml version="1.0"?> <ns1:profile xmlns:ns1="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns" xmlns="http:// www.suse.com/1.0/yast2ns"> <ns1:install> <ns1:software> <ns1:addons config:type="list"> <ns1:addon>addon-A</ns1:addon><ns1:addon>addon-B</ns1:addon> </ns1:addons> <ns1:packages config:type="list"> <ns1:package>package-A</ns1:package><ns1:package>package-B</ ns1:package> </ns1:packages> </ns1:software> </ns1:install> </ns1:profile> Could this be fixed? Or is it already known and possibly a workaround in existance? Thanks in advance, -Luzian

16 years, 2 months

Module cd creator

by Rodrigo_Albert_Fedosi

It is possible install the Yast module "cd creator" of the Suse enterprise server in the Suse professional. If it will go as I do? Att. Rodrigo Albert Fedosi Suporte TI Tel: (31) 3419-8854 Fax: (31) 3419-8803 rodrigo(a)bhz.jamef.com.br www.jamef.com.br

16 years, 4 months

Updating drivers and dealing with patches in AutoYast

by aquajtk-suse＠yahoo.com

Hello, I'm having 3 questions : 1. I've tried to install SLES9 SP2 on an IBM x306 however i was having problems with the installation cuz it did not recognize the raid controller and it showed both physical drives instead of the logical drive. I had to manually install this server using a driver update disk. Needless to say, but i also want to automatically deploy SLES9 SP2 on this server. I've checkout this document : http://mirror.mcs.anl.gov/suse-people/hvogel/Update-Media-HOWTO/Update-Medi… It states that i will need to put a file 'driverupdate' in the root of my repository. (I assume that's the driver update disk image i can download from IBM's support site). How can i use several update disks if they all should be named 'driverupdate'? 2. Say I have an http repository which contains the installation sources for SLES9 SP2. One day Novell releases a critical security patch and I'd like to integrate this patch in my repository so i don't need to install these patches after installing a server. Is there a way to do this (besides doing this with post-install scripts that just run rpm-commands)? Replacing the package in the repository won't work i think, cuz (if i'm not wrong) there is a list of packages on the install sources. 3. Currently i'm using a file in pxelinux.cfg which contains references to the kernel- and initrdimage and also the linuxrc command line parameters. AutoYasts documentation mentiones an info file that contains these parameters. Where do i place such an info file? Can i combine the info file and the command line parameters? eg i could put all parameters that are not unique for a given server in the info file and then put the server specific option in the file in pxelinux.cfg. Thanks a lot! Johan

16 years, 4 months

Possible bug with LVM and <size>max</size>

by Luzian Scherrer

Hello, The size-part of this controlfile-section doesn't work with SuSE 10.0 AutoYaST: <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <lv_name>root</lv_name> <mount>/</mount> <size>max</size> </partition> However, when I change 'max' to an absolute size (like '4096MB') it works. Defining the size as 'max' did work with SLES 9 SP2 AutoYaST. Is this a feature? ;) PS: Is this mailing-list the correct place to submit AutoYaST bugs or is there a bug-tracking system? Thanks, -Luzian

16 years, 4 months

How can I use a320raid instead of aic79xx after autoyast-installation

by ?

I'm trying to install SLES9 SP2 x86_64 on an IBM x346 machine(HostRAID is enabled, in this mode, system should use a320raid) via autoyast, but every time system uses aic79xx instead of a320raid after installation. I've added following section into autoyast config file: <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>INITRD_MODULES</sysconfig_key> <sysconfig_path>kernel</sysconfig_path> <sysconfig_value>reiserfs a320raid</sysconfig_value> </sysconfig_entry> </sysconfig> and <initrd_modules config:type="list"> <module>a320raid</module> </initrd_modules> The entry "INITRD_MODULES" in /etc/sysconfig/kernel have been created correctly by above sections after installation: ... # INITRD_MODULES="reiserfs a320raid" ... But system still used aic79xx: c79l1ms01:/etc/sysconfig # lsmod Module Size Used by floppy 73296 0 ipv6 317432 12 freq_table 13952 0 af_packet 33676 0 joydev 19584 0 sg 51128 0 st 51236 0 sr_mod 26788 0 tg3 96004 0 hw_random 14504 0 ehci_hcd 39300 0 uhci_hcd 41376 0 evdev 19072 0 usbcore 132984 4 ehci_hcd,uhci_hcd subfs 17664 2 dm_mod 69344 0 reiserfs 264688 1 aic79xx 267032 2 sd_mod 30208 3 scsi_mod 144000 5 sg,st,sr_mod,aic79xx,sd_mod I added a chroot script to create an initrd: ... sed -i 's/INITRD_MODULES.*/INITRD_MODULES=\"a320raid reiserfs\"/' /etc/sysconfig/kernel mkinitrd ... But after installation, system still used aic79xx, though a320raid has been loaded in: c79l1ms01:/etc/sysconfig # lsmod ... a320raid 377656 0 reiserfs 264688 1 aic79xx 267032 2 sd_mod 30208 3 scsi_mod 144000 6 sg,st,sr_mod,a320raid,aic79xx,sd_mod Actually, I think the initrd in /boot was created as I wished, but it seems system did not use this ramdisk at the first time system booted. And after I rebooted machine again, a320raid was loaded correctly: c79l1ms01:/etc/sysconfig # lsmod ... a320raid 377656 2 reiserfs 264688 1 sd_mod 30208 3 scsi_mod 144000 6 sg,st,sr_mod,a320raid,sd_mod Does anyone know which initrd system uses at the first time system boots? And how can I let system use a320raid at the first boot? _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/

16 years, 4 months

RE: [suse-autoinstall] merging autoyast and yast2

by Schumacher, Gordon

# From: Jordi Massaguer Pla [mailto:jordi.massaguer@opentrends.net] # Sent: Thursday, December 22, 2005 4:46 AM # To: suse-autoinstall(a)suse.com # Subject: [suse-autoinstall] merging autoyast and yast2 # # Hi! # I would like to install a system with some defaults, like the user # management, but let the user select some other stuff, like the software. # # How could this be achieved? There is a "confirm" option which lets the user confirm that everything is the way they want it before the installation proceeds. The XML looks like this: <mode> <confirm config:type="boolean">true</confirm> </mode> I forget where that is in the autoyast module though. If this is set to true, the user can change things. Be it noted that bad things will happen if the user changes the partitioning without also changing the GRUB config to match, and such things.

16 years, 4 months

merging autoyast and yast2

by Jordi Massaguer Pla

Hi! I would like to install a system with some defaults, like the user management, but let the user select some other stuff, like the software. How could this be achieved? I tried writing the users section of the autoinst.xml into the control.xml in a custom CD, but seemed not to work at all. Any idea will be very welcome, thanks, jordi

16 years, 4 months

Adding a custom package to auto-install / IP/DNS info

by Sean.Gilley＠huntington.com

I'm having trouble finding the answers I need. After doing a lot of searching I still can't quite figure out what needs to be done. Here's my situation. I have a box installed as an SLES 9 load server. I let yast copy the CDs, and yast places each CD into a different directory under the main directory. My goal is to be able to insert a CD in a machine, give it an IP address and gateway information, then walk away and have everything installed automatically. I've got it partially working. I've created a load file which works just fine to load the exact packages from the SLES distribution; now I need to be able to load one or more additional, customized packages that I've created. Can anyone point me a document that leads me, step by step, through the process to do this? The only things I've been able to find are difficult to follow and not always applicable because they aren't for SLES distributions. The other issue is that though it installs using the IP and GW I typed in, it doesn't keep the IP/GW and use them for the installed machine's IP and GW. Can anyone tell me what I need to do to pass the IP/GW info on through the install process? Oh, and finally, as a bit of extra icing on my cake, I'd like to change some of the function key text and functions and haven't been able to find that anywhere on the disk. Can someone point me to where that is or how it can be changed? Thanks, Sean. -- Sean L. Gilley IS Technical Specialist Huntington National Bank 614-331-9468, 614-374-7573 (mobile) sean.gilley(a)huntington.com

16 years, 5 months

pre-script + /tmp/profile/modified.xml modification

by jaiber john

>From a recent thread I found that I can modify autoyast.xml in /tmp/profile through pre-script and save it as /tmp/profile/modified.xml so that autoyast re-reads the modified information (dynamically generated partition info). Will this technique work for SLES9 autoinstall? I found a reference to this only in the SLES10 autoinstall manual. Thanks!

16 years, 5 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall December 2005