September 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] SuSE 9.1 network interface naming schema problem
by fschuett 16 Sep '04

16 Sep '04

Am Mittwoch, 15. September 2004 17:16 schrieb Mike Rose: > Hi, > > We just disliked the mac address naming convention so did this in our > post_install script (and a few other things): > Thank you both for your help. Bye, Frank Schütte > On Wed, 15 Sep 2004, Jonathon M. Robison wrote: > > The old naming schema can be restored manually. Just re-name the files. > > I cannot recall if you have to edit anything in /etc/sysconfig/hardware > > (files which point to hardware addresses, etc.) or > > edit /etc/modules.conf. It's been a while since I did it, but now mine > > are ifcfg-eth0 and ifcfg-eth1. > > > > --Jonathon Robison > > > > On Wed, 2004-09-15 at 12:44 +0200, fschuett wrote: > > > Hallo, > > > > > > for several similar machines I used to autoinstall just one machine and > > > copy the installed system to the others. For some reasons this is in my > > > environment less work than to autoinstall every machine. > > > > > > In 9.1 the naming schema for the first ethernet device changed from > > > "eth0" to "eth-id-<MAC address>". > > > Since the MAC address is unique for each machine, the copied systems > > > don't recognize their network interface. > > > > > > Does anybody know a possibility to restore the old naming schema or > > > correct the problem maybe by running a post-install script? > > >

1 0

AW: WG: [suse-autoinstall] installing SLES8 using autoyast and wi thou tany user interaction
by Lenz, Fabian 16 Sep '04

16 Sep '04

How can I use Service Pack 3 in the Installation process? I use the multiple source installation with service pack 3, described in the documentation. But nothing changed. Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de Intranet: http://ttc.telekom.de/ -----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet: Montag, 13. September 2004 17:51 An: Lenz, Fabian Cc: suse-autoinstall(a)suse.com Betreff: Re: WG: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction You need to use Service Pack 3 to fix this. Anas Lenz, Fabian wrote: > > Fabian Lenz > > Azb Fachinformatiker für Systemintegration > Deutsche Telekom AG > Telekom Training > BBi Koblenz > Hausadresse: Blücherstr. 6-8, 56073 Koblenz > Postanschrift: Postfach 9100, 56065 Koblenz > Telefon (mobil): +49 (160) 3565851 > E-Mail: mailto:Fabian.Lenz@telekom.de > Intranet: http://ttc.telekom.de/ > > -----Ursprüngliche Nachricht----- > Von: Lenz, Fabian > Gesendet: Montag, 13. September 2004 14:00 > An: 'Kohrs, Steven' > Betreff: AW: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction > > Hello! > > I have the same problem and the EULA is pop up bevor i can install! > I have the xml-Tags included, but nothing changed! > <general> > ... > <mode> > <confirm config:type="boolean">false</confirm> > <reboot config:type="boolean">false</reboot> > </mode> > ... > </general> > > What can I do? > Some people said I have to re-spool the CD, but what do they mean with re-spool??? > > Fabian Lenz > > Azb Fachinformatiker für Systemintegration > Deutsche Telekom AG > Telekom Training > BBi Koblenz > Hausadresse: Blücherstr. 6-8, 56073 Koblenz > Postanschrift: Postfach 9100, 56065 Koblenz > Telefon (mobil): +49 (160) 3565851 > E-Mail: mailto:Fabian.Lenz@telekom.de > Intranet: http://ttc.telekom.de/ > > -----Ursprüngliche Nachricht----- > Von: Kohrs, Steven [mailto:skohrs@fnni.com] > Gesendet: Freitag, 14. Mai 2004 15:47 > An: jochen.kirn(a)daimlerchrysler.com > Cc: suse-autoinstall(a)suse.com > Betreff: Re: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction > > On Fri, 2004-05-14 at 01:41, jochen.kirn(a)daimlerchrysler.com wrote: > >> >> >>Hi everyone, >> >>I'm currently creating an autoyast.xml file for an unattended >>installation >>of SLES8 (using PXE). >>so far everything went fine, except after the software rpms are >>installed a >>window pops up (textmode) >>telling me that the boot loader was succesfully written to disc which >>I >>have to approve by clicking ok. >> >>I guess there is a way (xml-tag) to perform a complete and silent >>installation without any user interaction > > > > Jochen, > > I believe this is what you're looking for: > > <general> > ... > <mode> > <confirm config:type="boolean">false</confirm> > <reboot config:type="boolean">false</reboot> > </mode> > ... > </general> > > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

FW: Need to know if autoinstall can solve a problem for me
by Greg Wallace 15 Sep '04

15 Sep '04

I am brand new to this list. I'm hoping autoinstall can help me with a problem I'm having. I am trying to migrate from SuSE 8.1 Pro to SuSE 9.0 Pro. The conversion goes fine, and everything works afterward (well there is one minor glitch, but that's something I can work on as I have time). My major concern, however, is being able to recover from a major system crash. I tried to go on from 9.0 to 9.1 and had problems. I had backed up 9.0, so I figured all I would have to do would be to re-install 9.0 out of the box, recover my backup, and I'd be right back in business in 9.0. Well, it didn't work that way. Many things that had been working when I did the conversion from 8.1 to 9.0 no longer worked when I did the recovery. I ended up having to restore my 8.1 installation to get a working system back. My suspicion is that the out of the box install of 9.0 installs some packages that the 8.1 to 9.0 conversion process didn't install. I'm thinking that, during the conversion, SuSE could see from what I had that certain packages would conflict and so made necessary adjustments. During the recovery, since SuSE had nothing to go on during that initial out of the box install, it put some packages on there that were incompatible with what I had in my backup. So, when I recovered the backup, I had a mishmash situation with the packages and that's why certain things would no longer function. Of course, all of this is speculation on my part, but I can't think of any logical reason why a conversion would work just fine but an out of the box install followed by a recovery would not. So, that's what brought me to this list. I'm hoping this installation problem is something that autoinstall could help resolve. What I would like to do is simply point to my backup during the initial install and say "only install the packages that are in this backup, no more and no less". My hope is that this is exactly the type of thing that autoinstall would handle. I notice that my backups generate an autoinstall list in addition to the file containing the actual backup data. I'm thinking this file must be usable somehow in an autoinstall process to instruct SuSE as to the particular packages that need to be loaded for the installation. I also suspect that there may be different degrees of autoinstall, all the way from being able to simply push a button (so to speak) and have the entire install take place to variations where part of the install is manual and part is automated. The main thing I want to automate is the package part. If I have to intervene during other parts of the installation, that's no big deal. Of course, if the amount of effort needed to get everything fully automated is not that much greater, then I would (of course) be interested in that also. Am I on the right track in thinking that this is right up autoinstall's alley (so to speak)? Could some sort of a basic autoinstall procedure take care of what I'm trying to get done here? Any help greatly appreciated. Yours truly, Greg Wallace

1 0

64 or 32??
by Patrick B. O'Brien 15 Sep '04

15 Sep '04

What command can I issue telling me if I'm a 64 or 32 bit?

4 3

SuSE 9.1 network interface naming schema problem
by fschuett 15 Sep '04

15 Sep '04

Hallo, for several similar machines I used to autoinstall just one machine and copy the installed system to the others. For some reasons this is in my environment less work than to autoinstall every machine. In 9.1 the naming schema for the first ethernet device changed from "eth0" to "eth-id-<MAC address>". Since the MAC address is unique for each machine, the copied systems don't recognize their network interface. Does anybody know a possibility to restore the old naming schema or correct the problem maybe by running a post-install script? Bye, Frank Schütte fschuett(a)gymnasium-himmelsthuer.de

3 2

SuSE 9.1 SSH Network Install fails
by werbung＠kuhnle.net 15 Sep '04

15 Sep '04

Hi, I am trying to do a network install with SuSE 9.1 on a headless (and keyboardless) machine. After inital booting and ssh login, yast displays the following error message: unicode_start skipped on /dev/pts/0 No keyboard detected. Trying to connect via serial interface /dev/ttyS0. On your terminal computer start the user interface with y2base "serial(115200):/dev/ttyS0" qt --auto-fonts or y2base "serial(115200):/dev/ttyS1" qt --auto-fonts or start the YaST2 menu by typing "yast2" and select YaST2/Remote Install This is because yast calls hwinfo, which sets "Keyboard: 0" in /etc/install.inf, causing YaST2 to fail at the following section: if [ ! "$update" -a "$Keyboard" = "0" -a ! "$Braille" -a "$NOTISERIES" != 0 -a "$NOTHVCCONSOLE" != 0 -a "$HOSTTYPE" != "s390" -a "$HOSTTYPE" != "s390x" -a -z "$Console" ] ; then log "no keyboard?" echo "No keyboard detected. Trying to connect via serial interface /dev/ttyS0." ... fi Is there any workaround/fix? Regards, Jochen

3 10

Setting a default root password
by Nicholas DeClario 13 Sep '04

13 Sep '04

Hey guys. During my auto install I want a default root password to be put in place. I checked numberous documentation and searched quite a bit and couldn't come up with anything. I was going to just do something like 'echo "password" | passwd root --stdin' in a post-install script but the 'passwd' included in SuSE does not support the --stdin option I've seen in the past. I would prefer not to hack up passwd to add this functionality as well. Am I missing something obvious? Is there anyway this can be done? Any help would be appreciated. Thanks, -Nick

5 6

WG: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction
by Lenz, Fabian 13 Sep '04

13 Sep '04

Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de Intranet: http://ttc.telekom.de/ -----Ursprüngliche Nachricht----- Von: Lenz, Fabian Gesendet: Montag, 13. September 2004 14:00 An: 'Kohrs, Steven' Betreff: AW: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction Hello! I have the same problem and the EULA is pop up bevor i can install! I have the xml-Tags included, but nothing changed! <general> ... <mode> <confirm config:type="boolean">false</confirm> <reboot config:type="boolean">false</reboot> </mode> ... </general> What can I do? Some people said I have to re-spool the CD, but what do they mean with re-spool??? Fabian Lenz Azb Fachinformatiker für Systemintegration Deutsche Telekom AG Telekom Training BBi Koblenz Hausadresse: Blücherstr. 6-8, 56073 Koblenz Postanschrift: Postfach 9100, 56065 Koblenz Telefon (mobil): +49 (160) 3565851 E-Mail: mailto:Fabian.Lenz@telekom.de Intranet: http://ttc.telekom.de/ -----Ursprüngliche Nachricht----- Von: Kohrs, Steven [mailto:skohrs@fnni.com] Gesendet: Freitag, 14. Mai 2004 15:47 An: jochen.kirn(a)daimlerchrysler.com Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] installing SLES8 using autoyast and withou tany user interaction On Fri, 2004-05-14 at 01:41, jochen.kirn(a)daimlerchrysler.com wrote: > > > > Hi everyone, > > I'm currently creating an autoyast.xml file for an unattended > installation > of SLES8 (using PXE). > so far everything went fine, except after the software rpms are > installed a > window pops up (textmode) > telling me that the boot loader was succesfully written to disc which > I > have to approve by clicking ok. > > I guess there is a way (xml-tag) to perform a complete and silent > installation without any user interaction Jochen, I believe this is what you're looking for: <general> ... <mode> <confirm config:type="boolean">false</confirm> <reboot config:type="boolean">false</reboot> </mode> ... </general> -- Sincerely, Steve Kohrs Distributed Systems 402.633.7058 This email and any files attached with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error delete this message and notify the sender at 402-341-0500. If you are not the named recipient you should not disseminate, distribute or copy this email or any attachment.

2 1

xml2hostconf + kickstart = autoyast ?
by Erik Sjölund 13 Sep '04

13 Sep '04

Just wanted to drop a note about a somewhat related project. http://xml2hostconf.sourceforge.net ( GPL-licensed ) It is used to generate kickstart files for RedHat/Fedora. And it generates RPMs consisting of configuration files. Autoyast have the Classes/Rules system. Xml2hostconf tries to solve the same problem with RPM dependencies and "kickstart-groups". Some differences: * autoyast is SUSE specific, xml2hostconf is RedHat/Fedora-specific ( I don't know if it is possible to modify xml2hostconf to generate some autoyast configuration ) * xml2hostconf, is not only used for things at install time. When it generates configuration RPMs, already installed systems will also get them by way of yum or apt-get. This means you don't have to reinstall a system to get the new configuration files! * xml2hostconf lacks the "Rules" functionality of autoyast. There is no such rule processing at install time. The configuration for each host is generated in advance. * xml2hostconf lacks a gui. * xml2hostconf lacks most of the "configuration and installation options" of autoyast ( http://www.suse.de/~nashif/autoinstallation/9.1/html/configuration.html ). xml2hostconf only handles what a kickstart file can do. The rest is left to the system administrator to put in post-install scripts and in generated configuration RPMs. Comments? cheers, Erik Sjölund

3 2

no space left doing autoinstall, etc...
by Noprianto 13 Sep '04

13 Sep '04

Hi all :) I am new to SUSE and have to learn about AutoInstall. I am very surprised with this facility :) I have configured control file ( i have it on NFS server, and reachable). Then, i create 3 bootdisk (because my target ws has no CDROM and bootrom). Booting was succeed. Everything from uncompresing kernel was fine. But, problem started when the install systems created device. Install system prints a lot of: /dev/xxx mknod xxx... /dev/xxx no space left after it, it prints someting like: SUSE Install System v.1.6.19 and hang out. I dont know whats happening. My target client has only 32 Megs of RAM. Is it the cause of that error? This is kernel cmdline for my target ws: i chose manual instalation as type: autoyast=nfs://192.168.0.1/PUB/SUSEINSTALL MEM=32 Am i doing something incorrect or all problems are caused by insufficient RAM of my ws? Thanks for reading this :) BTW, can anyone share with me procedure doing autoinstallation? - create control file and save it somewhere accesible - turn on ws and choose (manual) instalation - set the command line autoyast=<location_of_control_file> - what else - what else - what else My last question : - what is happening if i have not set some values in autoyast configuration? For example, what will happened if i have not set the soundcard device of ws? Will it autodetected or just left not detected? Thanks all :) Any comment is appreciated... Nop __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail

2 1