openSUSE Autoinstall June 2005

autoinstall@lists.opensuse.org

35 participants
49 discussions

Re: [suse-autoinstall] Additional Package & Silent install
by Michael Marion 01 Jul '05

01 Jul '05

On 30 Jun, Jan Kalcic wrote: > 1) I'm looking for a clear way to add additional packages to the installation server. I found a solution using the post script (wget && rpm) but it would really better and more handy to have them direclty into the AutoYaST software package database. Sort of difficult to get working.. but once you do, easy to keep updated and very slick integration. >From a previous answer I posted to the same question before: Look in the archives of this list for many threads on this, i.e. subjs: [suse-autoinstall] Custom install source for yast in SLES9 [suse-autoinstall] How can I regularly update the install repository? I should document my setup when I have a chance.. this comes up so often. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Joe: "I don't know, one minute we're spanking each other with meat, the next minute it got weird." --Wings

2 1

RE: [suse-autoinstall] Additional Package & Silent install
by Ness, Todd 30 Jun '05

30 Jun '05

1. requires the use of /usr/lib/YaST2/bin/create_package_descr you also have to edit selection files, md5sum files, selections, and directory.yast in the /pathtoinst/suse/setup/descr directory. 2. in the install section of your file there is a mode section set it to false <confirm config:type="boolean">false</confirm> -----Original Message----- From: Jan Kalcic [mailto:jkalcic@novell.com] Sent: Thursday, June 30, 2005 2:54 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Additional Package & Silent install Hi all, Few question about AutoYaST: 1) I'm looking for a clear way to add additional packages to the installation server. I found a solution using the post script (wget && rpm) but it would really better and more handy to have them direclty into the AutoYaST software package database. 2) During the installation on the target sysstem it's always asked to prompt yes to load the modules. Is there a way to make it silent? TIA, Jan Kalcic CNE, CLE, LPIC I Primary Support Engineer Novell Italy, Milan. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Additional Package & Silent install
by Jan Kalcic 30 Jun '05

30 Jun '05

Hi all, Few question about AutoYaST: 1) I'm looking for a clear way to add additional packages to the installation server. I found a solution using the post script (wget && rpm) but it would really better and more handy to have them direclty into the AutoYaST software package database. 2) During the installation on the target sysstem it's always asked to prompt yes to load the modules. Is there a way to make it silent? TIA, Jan Kalcic CNE, CLE, LPIC I Primary Support Engineer Novell Italy, Milan.

1 0

AW: [suse-autoinstall] 9.3 Pro can´t get autoinst.xml from floppy
by Götz Rieger 29 Jun '05

29 Jun '05

Hi Uwe, again thanks your high-speed responses. Goetz > -----Ursprüngliche Nachricht----- > Von: Uwe Gansert [mailto:ug@suse.de] > Gesendet: Dienstag, 28. Juni 2005 17:20 > An: suse-autoinstall(a)suse.com > Betreff: Re: [suse-autoinstall] 9.3 Pro can´t get autoinst.xml from > floppy > > > On Tuesday 28 June 2005 17:07, Götz Rieger wrote: > > > I´m trying to autoinstall a 9.3 Professional. The > > control file is named autoinst.xml and resides on a > > floppy, > > that's a bug. Use device://fd0/autoinst.xml instead. > > > -- > 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

9.3 Pro can´t get autoinst.xml from floppy
by Götz Rieger 28 Jun '05

28 Jun '05

Hi all, I´m trying to autoinstall a 9.3 Professional. The control file is named autoinst.xml and resides on a floppy, the boot medium is CD1. The whole setup works well with the 9.2 installation medium. When I use the 9.3 CD or DVD, I get the error "A profile for this maschine could not be found..." from YaST. And /var/log/YaST2/y2log shows many complaints about "mount point /media/floppy does not exist" or "[YCP] autoinstall/io.ycp:184 file /media/floppy/ autoinst.xml can´t be retrieved". Hm. If I watch the same autoinstall on 9.2, /media/floppy is created automagically, I would assume by some YaST-Modul... and /media/floppy/ autoinst.xml is found... Any ideas? Regards, Goetz

2 1

s390 / activating DASD
by Stefan Leippert 28 Jun '05

28 Jun '05

Hello list, autoinstall on LPAR is now working, but we still have one problem: We have to activate and select the target-DASD (direct access storage device) manually by yast, so a "complete without user input" install is only possible after selecting, activating and formating the dasd. The autoinst.xml-file will be loadad AFTER the DASD-configuration by yast, so there might be a way with a parameter into the parmfile. The parameter "DASD_Parameter=dasd=0.0.5f07" or "DASD_Parameter=dasd=5f07" didn't change anything. 5f07 is the ID of the DASD. Are there any other secret parameters for the parmfile to make them activate the DASD ? In all threads found in the internet this parameter is written like "DASD_Parameter=dasd=100-103" where I don't understand the "100-103". Any hint ? Maybe I only use a wrong ID or syntax. The next thing is the installed SSH-Server - There is no password for root set, the SSH-Access isn't possible until I logged in by HMC and set it by hand. I have already tried following lines in the autoinst.xml: <users config:type="list"> <user> <username>root</username> <user_password>XXXXX</user_password> <encrypted config:type="boolean">false</encrypted> </user> </users> But that didn't solve the problem. Thank you in advance ! Stefan Mit freundlichen Grüßen / Best regards Stefan Leippert Praktikant eServer Software System Evaluation and Test IBM Deutschland Entwicklung GmbH Schoenaicher Strasse 220 D-71032 Boeblingen mailto:leippert@de.ibm.com

1 0

Problems with YOU using a SLES9 Custom CD
by Fabiano Felix 27 Jun '05

27 Jun '05

Hi All, I make a Custom CD using SLES9, where I create new package description using only my package selection. I also updated kernel image that is used at installation process, using the same that are at SP1. All process works fine, and all services functions without any problem... but, when I try to do an On-line Update, I only can see SUSE-SLES packages. The most important packages are at SUSE-CORE selection (probably an inheritance from UnitedLinux CD's model...). I tried to add this update option using YaST2 (and copying from a "normal" SLES9 install), but I can't have success... Two questions: - Someone has some idea to correct this? - What's the best form to customize SLES9 CD's and don't have this problem again? (I believe that it have some relation with "media.N", "yast dir at CD root" and "contents" file...) With best regards, Fabiano Felix

1 0

Mounted paths under post-install script?
by Thorbjorn Jemander 27 Jun '05

27 Jun '05

Hi, I am doing a custom SuSE install DVD and I have included some extra software that needs to be installed during the post-install stage. However, what can I assume about mounts during the post-install script? Will the DVD be mounted, and if so, what is the mounting point? /media/dvd? I'm using SuSE Professional 9.3. Thanks in advance, ________________________________________________ Dr. Thorbjörn Jemander, Senior/RT Systems Expert Enea Epact AB, Teknikringen 8, Linköping, Sweden thje(a)epact.se, +46 13 465 58 67, www.epact.se

1 0

RE: [suse-autoinstall] autoinstall on s/390
by Stefan Leippert 24 Jun '05

24 Jun '05

For those who wanna try this also - Put the AUTOYAST-Paramter into the first line and yast gets the autoinst.xml-file or query for it, if it cannot get it on the given path. My parmfile: AUTOYAST=nfs://10.30.10.32:stefan/autoinst.xml ramdisk_size=65536 root=/dev/ram1 ro init=/linuxrc TERM=dumb IP_INTERFACE=qeth IP_ADDR=10.30.53.24 IP_NETMASK=255.255.0.0 IP_BROADCAST=10.30.255.255 IP_MTU=1500 IP_GATEWAY=10.30.10.32 IP_HOST=xxx READ_DEVNO=f618 WRITE_DEVNO=f619 DATA_DEVNO=f61a DASD_Parameter=dasd=5f07 INST_INFO=nfs INST_IP_ADDR=10.30.10.32 INST_IP_DIR=/distros/suse/SLES-9-s390/SUSE-SLES-Version-9/CD1 INST_PASSWORD=xxxx AUTOINSTALL=yes INST_SCREEN=VNC VNC_PASSWORD=xxxx Connection by VNC through SSH-Tunnel. Yast now just queries the DASD, and then runs in a loop in "Preparing System for automated installation". I think I have to check the autoinst.xml-file now, yast runs till "Preparing your harddisk" and then starts again with "Preparing System for automated installation". Mit freundlichen Grüßen / Best regards Stefan Leippert Praktikant eServer Software System Evaluation and Test IBM Deutschland Entwicklung GmbH Schoenaicher Strasse 220 D-71032 Boeblingen mailto:leippert@de.ibm.com

1 0

SLES9 autoinstall stops "Creating initrd ..."
by Djeezus 24 Jun '05

24 Jun '05

Hy all, I've seen this question posted before, I found some relates articles / posts on the web, but none with a proper solution ... everything goes fine up to the point where it's trying to create the "initrd" image on the client... The y2log doesn't show any errors related to "initrd" and I've double/tripple checked the autoinstall.pdf and made sure the nfs directory tree is OK ... I found some articles on the web about "Creating initrd ... " failures, but they stated this was an old SLES9 beta problem, which should be resolved by now. - The autoyast server : autoyast:~ # SPident CONCLUSION: ServicePack Level: SLES-9-i386-SP1 + "updates" => up-to-date autoyast:~ # ls -l /data/Sles9/ total 0 drwxr-xr-x 5 root root 240 May 12 15:22 . drwxr-xr-x 10 root root 232 Jun 23 00:19 .. lrwxrwxrwx 1 root root 19 May 12 15:21 boot -> sles9-i386/CD1/boot lrwxrwxrwx 1 root root 22 May 12 15:21 content -> sles9-i386/CD1/content lrwxrwxrwx 1 root root 26 May 12 15:21 control.xml -> sles9-i386/CD1/control.xml drwxr-xr-x 7 root root 168 May 12 15:17 core9-i386 lrwxrwxrwx 1 root root 22 May 12 15:21 media.1 -> sles9-i386/CD1/media.1 drwxr-xr-x 3 root root 72 May 12 15:17 sles9-i386 drwxr-xr-x 2 root root 104 Jun 22 12:08 yast Any thoughts / comments much appreciated; Bye, Gert PS : the same server also acts as YOU server for the other SLES9 installs (which were manually installed), and this works fine ...

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall June 2005