April 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

Scripting dirinstall?
by Teun 25 Feb '07

25 Feb '07

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

3 2

FYI: adding own RPMs to a SLES10 inst. source
by Uwe Gansert 06 Jul '06

06 Jul '06

Hi, here is a small documentation how to add own RPMs to a SLES10/SL10.1 installation source. To create a tree with RPMs in parallel of your other installation source, use at least version 20060418 of create_update_source.sh from my SUSE Homepage (http://www.suse.de/~ug). The latest autoyast2-utils RPM will contain that script too. You can find documentation on how to use that script on my homepage. After you have created the tree with your own RPMS, you have two options· to tell autoyast about that new installation source. Either in the autoyast profile like this: > <add-on> > <add_on_products config:type="list"> > <listentry> > <media_url>http://192.168.66.1/SLES10/updates</media_url> > <product>SuSE-Linux-Updates</product> > <product_dir>/</product_dir> > </listentry> > </add_on_products> > </add-on> You can do that with the autoyast UI on SLES10/SL10.1 too. Or another option is to create a file called "add_on_products" on the main installation source. So it looks like this (the "updates" directory was created by the script): > #:/space/SLES10 # tree -L 1 > . > |-- ARCHIVES.gz > |-- COPYING > |-- COPYING.de > |-- COPYRIGHT > |-- COPYRIGHT.de > |-- ChangeLog > |-- INDEX.gz > |-- LICENSE.TXT > |-- NEWS > |-- README > |-- README.BETA > |-- README.BETA.DOS > |-- README.DOS > |-- add_on_products > |-- boot > |-- content > |-- control.xml > |-- directory.yast > |-- docu > |-- dosutils > |-- gpg-pubkey-0dfb3188-41ed929b.asc > |-- gpg-pubkey-1d061a62-427a396f.asc > |-- gpg-pubkey-307e3d54-44201d5d.asc > |-- gpg-pubkey-3d25d3d9-36e12d04.asc > |-- gpg-pubkey-9c800aca-40d8063e.asc > |-- ls-lR.gz > |-- media.1 > |-- pubring.gpg > |-- suse > `-- updates > > #:/space/SLES10 # cat add_on_products > http://192.168.66.1/SLES10/updates With that file on the installation source, you don't need to specify the additional installation sources in the autoyast profile. You can mix those two options. So it's possible to specify one installation source in the autoyast profile and another one in the "add_on_products"-file. The "add_on_products"-file is not supported by autoyast in RC1 but will be with later versions. I hope that helps. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, 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

1 2

instserver in pre SUSE-10.0 distros
by Jochen Schaefer 26 Apr '06

26 Apr '06

Hi list, have a question regarding the instserver setup since opensuse/SUSE 10.1 Beta releases. Until know it was quite easy to setup an instserver with a "stream" directory and mounted isos. I mostly used following setup: ls -ls <http-install-source> media -> /inst/suse/media content -> media/SUSE-PROF/9/i386/CD1/content control.xml -> media/SUSE-PROF/9/i386/CD1/control.xml media.1 -> media/SUSE-PROF/9/i386/CD1/media.1 boot yast driverupdate -> xxx directory.yast I could loop-mount the isos to the media-dir (CD1 to CDX) and everything worked fine. When I pointed the installdir to http://my_installserver_/http-install-source AutoYast found all CD's, the additional media.x Dirs, setup/description files, RPM's and other. Since the 10.x Releases this setup does not work for me anymore. I now have to copy all CD's in one directory. Yast looks for media.1 .. media.x in this directory If Autoyast does not find the directories suse, media.{2,3,4,5} then it will stop to work. This directories where not required until now. The autoyast routines in initrd seem to have changed. This design does not allow me to work with loop mounted isos. I could work with unionfs to go round this but that would more complicate the setup. Does anybody know how to get it working like the old fashion? Thanks, Jochen -- Jochen Schaefer Senior Consultant Integrated Services Novell GmbH Mobil: +49(0)1735876969 E-mail: jschaef(a)novell.com Address: Duesseldorf , 40470, Germany Noerdlicher Zubringer 9-11 http://www.novell.com

2 4

A very basic partitioning problem
by Rainer Krienke 19 Apr '06

19 Apr '06

Hello, I habe a suse10.1 system and I am trying to do an autoinstall on it. This works if there are no linux partitions on it but it fails when I do the auto install the second time, so there are already linux partitions (boot, swap, /) in place. In the autoyast file I said: <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <use>linux</use> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">ext2</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> <size>64M</size> </partition> ... </partitions> </drive> </partitioning> As far as I understood the documentation <use>linux</use> should delete all linux specific partitions or reuse them. What I get is during "Create parrtition plans" an error box simply saying "Error while configuring partitions. Try again". However this does not tell me what autoyast thinks is wrong. I looked in /var/adm/autoinstall/logs/ but this directory is still empty. Does anyone know how to get more information what went wrong or why autoyast fails to drop the existing linux partitions and create new ones? Thanks Rainer -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: krienke(a)uni-koblenz.de, Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html ---------------------------------------------------------------------------

3 6

Adding driver to repository
by Johan Kielbaey 19 Apr '06

19 Apr '06

Hello, Is it possible to add a driver to the SLES9 repository without altering the driverupdate? The problem: To be able to install an IBM x306m I need to use an updatedisk for the RAID controller (module= adp94xx). To automate this I added the driver to the driverupdate. On an IBM x306m this works fine. However using the same driverupdate on an IBM x346 it also loads the adp94xx module, while it doesn't need it since the RAID controller is different. Besides the adp94xx it also detects and loads the correct module (ips). When rebooting the x346 it hangs after the message "proc unmounted. Please stand by while rebooting the system...". When I press CTRL-ALT-DEL it shows the message "shutdown: warning: cannot open /var/run/shutdown.pid". Whenever I unload the adp94xx module on the x346 reboot goes fine. However the module is loaded again after reboot so i'd have to add scripts that will remove the module after each reboot or so. I can think of some ways to fix this with scripting, but the cleanest way is to add drivers to the repository and let the installer of SLES detect and configure the hardware. Thanks, Johan Met vriendelijke groeten - Kind regards, Johan johankielbaey(a)yahoo.com

2 1

create_package_desc (warnings and different packages)
by Martin Vogt 13 Apr '06

13 Apr '06

Hello list, another feature in the file create_package_desrc on beta9: >create_package_descr -d ../suse -d ../../CD2/suse -d ../../CD3/suse -d ../../CD4/suse -d ../../CD5/suse -x >setup/descr/EXTRA_PROV > > >find: warning: you have specified the -maxdepth option after a non-option argument -name, but options are not positional >(-maxdepth affects tests specified before it as well as those specified after it). Please specify options before other >arguments. The warning is actually only a warning: >processed 2648 packages >now recoding to UTF-8: packages packages.DU packages.en Seems ok. But what worries me, is that the packages on beta9 and the newly created differs in size: packages bytes: 2424016 packages.beta9 bytes: 2883689 The diff of 400k is rather big.... I will try a testinstallation now. Martin

1 4

RE : [suse-autoinstall] A very basic partitioning problem
by COMBERNOUS Fabien 13 Apr '06

13 Apr '06

Lo, > -----Message d'origine----- > De : Uwe Gansert [mailto:ug@suse.de] > Envoyé : jeudi 13 avril 2006 16:28 > À : suse-autoinstall(a)suse.com > Objet : Re: [suse-autoinstall] A very basic partitioning problem > > > On Thursday 13 April 2006 15:51, Rainer Krienke wrote: > > > The partitioning is: > ... > > The partitioning section of the autoyast file is: > > both looks good. I don't see anything wrong. > I tried your profile on a disk with a very similar > partitioning and it works fine here. with SLES9 SP1, I encountred a similar problem on ia64 arch with the following partitioning section (see bellow). Our workaround is to start install without any partions on drives. Note : I don't remembre is we encountred the case on i386 arch. BR. <partitioning config:type="list"> <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</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>512mb</size> </partition> <partition> <filesystem config:type="symbol">fat</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot/efi</mount> <partition_id config:type="integer">259</partition_id> <partition_type>primary</partition_type> <size>200mb</size> </partition> <partition> <lvm_group>vgroot</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>20gb</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdc</device> <partitions config:type="list"> <partition> <lvm_group>vga</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>14000mb</size> </partition> <partition> <lvm_group>vgb</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_type>primary</partition_type> <size>25gb</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/vgroot</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>root</lv_name> <mount>/</mount> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <lv_name>swap</lv_name> <mount>swap</mount> <size>4gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>opt</lv_name> <mount>/opt</mount> <size>512mb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>var</lv_name> <mount>/var</mount> <size>2gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>home</lv_name> <mount>/home</mount> <size>1gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>tmp</lv_name> <mount>/tmp</mount> <size>1gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>usr</lv_name> <mount>/usr</mount> <size>2gb</size> </partition> </partitions> <pesize>32M</pesize> <use>all</use> </drive> <drive> <device>/dev/vga</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>a1</lv_name> <mount>/a1</mount> <size>14000mb</size> </partition> </partitions> <pesize>32M</pesize> <use>all</use> </drive> <drive> <device>/dev/vgb</device> <is_lvm_vg config:type="boolean">true</is_lvm_vg> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>b1</lv_name> <mount>/b1</mount> <size>10gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>b2</lv_name> <mount>/b2</mount> <size>10gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <lv_name>b3</lv_name> <mount>/b3</mount> <size>4800mb</size> </partition> </partitions> <pesize>32M</pesize> <use>all</use> </drive> </partitioning>

1 0

SLES9 on z/VM, autoyast and <dasd> section
by Kai Dusek 12 Apr '06

12 Apr '06

Dear all, We're trying to setup an SLES9 SP3 system on a z/VM guest with autoyast. We would like to pre-defined an autoinst.xml file. It looks like the <dasd>...</dasd> section is mandatory since autoyast does not get the dasd hardware settings "on the fly". Unfortunately we don't know the mdisk id a priori, so that we currently are modifying the autoinst.xml file manually for every system with a different mdisk id. Replacing the autoinst.xml file with a new one during the pre-installation step (as described in the SLES documentation) does not work since hardware detection is done before pre-installation. Simply omiting the <dasd>...</dasd> section did not work since yast stops working after hardware detection since it does not detect any disk to install the system on. I tried to add a dasd= (resp. DASD=) parameter to the parmfile but it doesn't help detecting the disks. Does anybody know what we could do to omit that <dasd>...</dasd> section from the autoinst.xml file? Can we specify the mdisk id in that section with a placeholder? Or has it really to be hardcoded in the autoinst.xml file? [...] <dasd> <devices config:type="list"> <listentry> <channel_id>0.0.0150</channel_id> <diag config:type="boolean">false</diag> <format config:type="boolean">true</format> </listentry> </devices> </dasd> [...] Mit freundlichen Gruessen/Kind regards Kai Dusek

2 3

127.0.0.2 where does it come from? (argh)
by Martin Vogt 11 Apr '06

11 Apr '06

Hello List, I think its related to autoyast but I'm not sure. In /etc/hosts The last line ist always: ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 ^^^^^^^^^^^^^^^^^^ And not hostname after that. Does anyone have the same entry? Martin

2 3

autoyast on suse 10.1 beta9 x86_84
by Martin Vogt 11 Apr '06

11 Apr '06

Hello, I have an autoyast installation from the beta9 CD ISOs. The x86 works fine. Same applied to x86_64 leaves me with a nearly empty menu.lst for grub. Only the xen kernel is installed. Is this a know bug in beta9? At least I would say this is a serious bug.... Martin

2 1