September 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

RE: [suse-autoinstall] Setting a default root password
by Ness, Todd 08 Sep '04

08 Sep '04

The most simple solution on the older SuSE 8 versions is to do a postinstall script with a perl command to insert the proper encrypted password into the shadow file. /usr/bin/perl -pi -e 's#^root:.*$#root:<your pw here>:12415:0:10000::::#' /etc/shadow If it has been fixed in the newer versions there is xml code to support setting the password. <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>your pw here</user_password> <username>root</username> </user> </users> -----Original Message----- From: Nicholas DeClario [mailto:nick@demandred.dyndns.org] Sent: Wednesday, September 08, 2004 2:43 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Setting a default root password 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 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Fwd: [suse-autoinstall] Installing with Fibre attached drive onto local scsi device
by Aaron Amauba 08 Sep '04

08 Sep '04

OK, once again let me know if I shouldnt post this here. Im still a noob I got back to this and it turned out to be a simple fix after I did some digging. the qla2300 module needed to come after the scsi module in /etc/sysconfig/kernel I changed INITRD_MODULES="scsi_mod sd_mod cdrom ide-cd qla2300 mptscsih reiserfs" to INITRD_MODULES="scsi_mod sd_mod cdrom ide-cd mptscsih qla2300 reiserfs" then mkinitrd and replace the initrd and linux in the boot/loader directory on my installation media (Which was a NFS mount) After the installation was completed, the system came up ok. Maybe all this is in the doc's somewhere, but I never did find it. Anyone know where its at or have any links I should look at? Note: forwarded message attached. --------------------------------- Do you Yahoo!? Win 1 of 4,000 free domain names from Yahoo! Enter now.

1 0

LPRng installation problem
by Henrik Schmidt 07 Sep '04

07 Sep '04

Network autoinstall with PXE of SuSE 9.1 : I use autoinstall to install LPRng instead of CUPS for various reasons. It works fine but locks up as soon as I want to use kprinter. I can fix calling KDE print manager and setting the print system from CUPS to LPRng *for each user* manually. Is it possible to set a system variable in config.xml for autoyast during install to avoid doing it by hand ? Why is the print manager set to CUPS by default without CUPS being installed at all ? Henrik -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs(a)ks.informatik.uni-kiel.de

1 0

[Fwd: Re: [suse-autoinstall] Additional rpm packages are not found on media? (error 11283)]
by Stephan A. Rickauer 03 Sep '04

03 Sep '04

Hard to believe, but it works! Thanks Jan. However, it would be really helpful to know, why it has to be i586 and not "noarch". Furthermore, I'd like to specify my own subdirs, like "uni" or something similar ... isn't that possible? Stephan A. Rickauer ---------------------------- Institut für Neuroinformatik IT-Koordinator Universität / ETH Zürich Winterthurerstr. 190 CH-8057 Zürich Tel: +41 1 635 30 50 Sek: +41 1 635 30 52 Fax: +41 1 635 30 53 http://www.ini.unizh.ch ------------------------ Jan-Marc Pilawa wrote: > Schon probiert die rpms in i586 abzulegen? Meine habe ich dort angelegt und > genau das getan, was in der Mail beschrieben stand. > > Mit freundlichen Gruessen / Sincerely > > Jan Pilawa > -------- Original Message -------- Subject: Re: [suse-autoinstall] Additional rpm packages are not found on media? (error 11283) Date: Thu, 8 Jul 2004 14:22:12 +0200 From: Jan-Marc Pilawa <j.pilawa(a)tu-bs.de> Organization: Rechenzentrum To: Stephan A. Rickauer References: <40ED38D7.7020101(a)ini.phys.ethz.ch> Schon probiert die rpms in i586 abzulegen? Meine habe ich dort angelegt und genau das getan, was in der Mail beschrieben stand. Mit freundlichen Gruessen / Sincerely Jan Pilawa -- + Kontakt ----------------------------------------------------+ + Systembetreuung Rechenzentrum TU Braunschweig + + Hans-Sommer-Str. 65, D-38092 Braunschweig + + Tel: +49 531 391-5548 E-Mail: j.pilawa(a)tu-bs.de ____________+

3 6

PXE install fails with SCSI disks
by Steve Glines 03 Sep '04

03 Sep '04

I’m building a PXE install lab for SUSE and other flavors of Linux. The DHCP and tftp servers are working. Note: I can fully install Red Hat from this lab but SUSE (SLES9 rc5) shows the following symptoms: 1. a cdrom install on the target system runs to completion in graphics mode. System is an HP PC with SCSI disk. 2. PXE install runs in non X-window mode (text) and fails to load scsi controllers – cannot find any disks. Fails even when modules are manually added. Here is the content of /tftpboot/pxelinux.cfg/default: default suse prompt 1 display boot.msg timeout 200 label redhat kernel redhat.kernel append initrd=redhat.root ramdisk_size=65536 label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536\ install=http://10.0.3.11/suse/CD1/ The file suse.kernel was copied from /boot/loader/linux in CD1 while suse.root was taken from /boot/loader/initrd in the same CD. I copied the contents of each CD into their own directories – I have CD1 – CD6 in the directory specified by http://10.0.3.11/suse/CD[1-6]. My test target system is a Celeron with 256MB Ram and an IDE disk; this setup fully installs SLES9. The only material change from this to the production lab is that the target system in the production lab has a SCSI disk and 1GB of ram. Help! Please Cheers -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part.

2 1

Re: [suse-autoinstall] PXE install fails with SCSI disks
by Steve Glines 03 Sep '04

03 Sep '04

Hi Marcin, Thanks for the help. I've made the fixes you suggested but the system still refuses to see the scsi disks. Here is the data. The target system is an HP Proliant ML350 G3 with a single 40GB SCSI disk. The script shown in sles9/CD1/docu/RELEASE-NOTES.en.html doesn't work so I've modified it thus (feel free to reuse it): #From the top directory umask 0 mkdir -p sles9/CD1 # now copy the contents of SLES CD1 into this directory echo "Mount CD1" read x mount /dev/cdrom sleep 10 cp -r /cdrom/* sles9/CD1 eject mkdir -p core9/CD1 # now copy the contents of SLES CD2 into this directory echo "Mount CD2" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD1 eject mkdir -p core9/CD2 # now copy the contents of SLES CD3 into this directory echo "Mount CD3" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD2 eject mkdir -p core9/CD3 # now copy the contents of SLES CD4 into this directory echo "Mount CD4" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD3 eject mkdir -p core9/CD4 now copy the contents of SLES CD5 into this directory echo "Mount CD5" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD4 eject mkdir -p core9/CD5 now copy the contents of SLES CD6 into this directory echo "Mount CD6" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD5 eject ln -s sles9/CD1/boot boot ln -s sles9/CD1/content content ln -s sles9/CD1/control.xml control.xml ln -s sles9/CD1/media.1 media.1 mkdir -p yast echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/instorder echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/order --------------------------------- After PXE booting the system stalls when it can't find a hard disk. When I look in /var/log/boot.log I find: kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter errorno=2 If I run "/sbin/modprobe -s -k scsi_hostadapter" directly from a shell I get "Kernel requires old modprobe no /sbin/modprobe.old." ------------------------------------------- Here is the current line from my default file: label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536 \ install=http://10.0.3.11/suse ---------------------------------------------- Here is the output of "find . -type d": . ./sles9 ./sles9/CD1 ./sles9/CD1/SLES-LICENSE ./sles9/CD1/SLES-LICENSE/cz ./sles9/CD1/SLES-LICENSE/de ./sles9/CD1/SLES-LICENSE/en_US ./sles9/CD1/SLES-LICENSE/es ./sles9/CD1/SLES-LICENSE/fr ./sles9/CD1/SLES-LICENSE/it ./sles9/CD1/SLES-LICENSE/nl ./sles9/CD1/SLES-LICENSE/pl ./sles9/CD1/SLES-LICENSE/pt_BR ./sles9/CD1/boot ./sles9/CD1/boot/loader ./sles9/CD1/docu ./sles9/CD1/docu/de ./sles9/CD1/docu/en ./sles9/CD1/docu/es ./sles9/CD1/docu/fr ./sles9/CD1/docu/HOWTOs ./sles9/CD1/docu/it ./sles9/CD1/docu/ja ./sles9/CD1/docu/ko ./sles9/CD1/docu/pt_BR ./sles9/CD1/docu/zh_CN ./sles9/CD1/dosutils ./sles9/CD1/dosutils/dparam ./sles9/CD1/dosutils/ext2tool ./sles9/CD1/dosutils/ext2tool/ext2fs ./sles9/CD1/dosutils/ext2tool/linux ./sles9/CD1/dosutils/ext2tool/src ./sles9/CD1/dosutils/ext2tool/sys ./sles9/CD1/dosutils/fips ./sles9/CD1/dosutils/fips/fips15 ./sles9/CD1/dosutils/fips/fips15/restorrb ./sles9/CD1/dosutils/fips/fips15/source ./sles9/CD1/dosutils/fips/fips20 ./sles9/CD1/dosutils/fips/fips20/restorrb ./sles9/CD1/dosutils/fips/fips20/source ./sles9/CD1/dosutils/gtar109 ./sles9/CD1/dosutils/gzip ./sles9/CD1/dosutils/install ./sles9/CD1/dosutils/lfn ./sles9/CD1/dosutils/loadlin ./sles9/CD1/dosutils/loadlin/doc ./sles9/CD1/dosutils/loadlin/src ./sles9/CD1/dosutils/ltools ./sles9/CD1/dosutils/pkunzip ./sles9/CD1/dosutils/putty ./sles9/CD1/dosutils/rawrite ./sles9/CD1/dosutils/rawwritewin ./sles9/CD1/dosutils/tightvnc ./sles9/CD1/dosutils/untgz ./sles9/CD1/dosutils/weirdx ./sles9/CD1/dosutils/weirdx/config ./sles9/CD1/dosutils/xfs186 ./sles9/CD1/dosutils/xfs32-11 ./sles9/CD1/dosutils/zipzp715 ./sles9/CD1/media.1 ./sles9/CD1/suse ./sles9/CD1/suse/i586 ./sles9/CD1/suse/noarch ./sles9/CD1/suse/nosrc ./sles9/CD1/suse/setup ./sles9/CD1/suse/setup/descr ./sles9/CD1/suse/src ./sles9/CD1/yast ./sles9/CD1/yast/core9 ./sles9/CD1/yast/core9/media.1 ./sles9/CD1/yast/core9/suse ./sles9/CD1/yast/core9/suse/setup ./sles9/CD1/yast/core9/suse/setup/descr ./core9 ./core9/CD1 ./core9/CD1/media.1 ./core9/CD1/suse ./core9/CD1/suse/i586 ./core9/CD1/suse/i686 ./core9/CD1/suse/noarch ./core9/CD1/suse/setup ./core9/CD1/suse/setup/descr ./core9/CD2 ./core9/CD2/media.2 ./core9/CD2/suse ./core9/CD2/suse/i586 ./core9/CD2/suse/i686 ./core9/CD2/suse/noarch ./core9/CD3 ./core9/CD3/media.3 ./core9/CD3/suse ./core9/CD3/suse/i586 ./core9/CD3/suse/i686 ./core9/CD3/suse/noarch ./core9/CD3/suse/src ./core9/CD4 ./core9/CD4/media.4 ./core9/CD4/suse ./core9/CD4/suse/nosrc ./core9/CD4/suse/src ./core9/CD5 ./core9/CD5/media.5 ./core9/CD5/suse ./core9/CD5/suse/nosrc ./core9/CD5/suse/src ./yast Marcin Kurc wrote: > > for graphical install you can say 'textmode=0' after 'install*' > please send me your 'default' file and output of 'find . -type d' in the > suse top directory > > > > thanks, > > Marcin Kurc > Linux Impact Team > Novell, Inc > > (973) 493-6235 > >>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 3:37 pm >>> > Thanks - I missed that one and was following the instructions that came > with SUSE 9.1 Pro. It still boots into the non-X format via PXE and X > when I do a CDROM install. Is there a way to make it boot into Graphics > mode. The lab I'm building is supposed to simulate the experience of > installing via CDROM. By the way this is going to go into HP's main > learning lab. The Red Hat version is being used 30-50 times a day. > > Now I'm getting "Network error 404 not found." > > Cheers > Steve > > Marcin Kurc wrote: > >> >>it is not a problem with PXE, your installation tree is not configured >>correctly >>You should either use SLES9 system to build the tree or configure it >>according to the docu/RELEASE-NOTES.en.html which can be found on cd #1 >> >>Also, you need to point you install to top dir not CD1 i.e. >>'install=_/http://10.0.3.11/suse/_' >> >> >> >>thanks, >> >>Marcin Kurc >>Linux Impact Team >>Novell, Inc >> >>(973) 493-6235 >> >>>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 2:30 pm >>> >>I’m building a PXE install lab for SUSE and other flavors of Linux. >> >>The DHCP and tftp servers are working. Note: I can fully install Red Hat >>from this lab but SUSE (SLES9 rc5) shows the following symptoms: >> >>1.a cdrom install on the target system runs to completion in graphics >>mode. System is an HP PC with SCSI disk. >>2.PXE install runs in non X-window mode (text) and fails to load scsi >>controllers – cannot find any disks. Fails even when modules are >>manually added. >> >>Here is the content of /tftpboot/pxelinux.cfg/default: >> >>default suse >>prompt 1 >>display boot.msg >>timeout 200 >> >>label redhat >> kernel redhat.kernel >> append initrd=redhat.root ramdisk_size=65536 >> >>label suse >> kernel suse.kernel >> append initrd=suse.root ramdisk_size=65536\ >>install=http://10.0.3.11/suse/CD1/ >> >>The file suse.kernel was copied from /boot/loader/linux in CD1 while >>suse.root was taken from /boot/loader/initrd in the same CD. >> >>I copied the contents of each CD into their own directories – I have CD1 >> – CD6 in the directory specified by http://10.0.3.11/suse/CD[1-6]. >> >>My test target system is a Celeron with 256MB Ram and an IDE disk; this >>setup fully installs SLES9. The only material change from this to the >>production lab is that the target system in the production lab has a >>SCSI disk and 1GB of ram. -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part.

1 0

Changing kernel in the install distribution. How?
by Ermanno Polli 03 Sep '04

03 Sep '04

Hi, I asked this question on the suse-linux-e list, but I had no answer. The reason for asking what is in the subject line is I've found my motherboard is no longer supported by SuSE. The last version I was able to install was the 8.0. Trying to install the 8.2 cause a hang just after the "loading kernel" window after having hit the "install" menu item in the installation. So I built a kernel from the sources (2.4.20) but I'm not able to upgrade all the 8.0 packages. I downloaded the 8.2 distribution to disk and I tried to point YOU to that directory, but YOU refused it (Unable to mount or something). So I'm wondering if I could "build" an install CD with *my* kernel, instead of the SuSE supplied one. Is it possible? What are the passes to achive this goal? Thank you very much. Ermanno Polli INFN-LNF

1 0

X11 configuration, SLES8
by Oliver Schwabedissen 02 Sep '04

02 Sep '04

Hello, I have a problem with configuring X11 when installing SLES8. I want to configure X11, but don't want KDE to start when the server comes up. So I configured runlevel 3 and X11 like this: [...] <runlevels> <default>3</default> </runlevels> <x11> <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">false</enable_3d> <monitor> <display> <max_hsync config:type="integer">60</max_hsync> <max_vsync config:type="integer">60</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">30</min_vsync> </display> <monitor_device>1024X768@60HZ</monitor_device> <monitor_vendor>LCD</monitor_vendor> </monitor> <resolution>1024x768</resolution> <start_x11 config:type="boolean">false</start_x11> </x11> </configure> However, when autoinstall finishes the system boots to runlevel 5, which is now also the default runlevel in /etc/inittab. Why does autoyast ignore my configured runlevel? Doesn't <start_x11 config:type="boolean">false</start_x11> mean that X11 should not be started automatically? I'm starting installation by booting from SP3 CD1 with an info file on floppy. It then connects to the installation server through NFS. Oliver -- Superg�nstige DSL-Tarife + WLAN-Router f�r 0,- EUR* Jetzt zu GMX wechseln und sparen http://www.gmx.net/de/go/dsl

1 1

Multiple Versions on one Installationserver
by Brigitte Warnecke-Schaer 02 Sep '04

02 Sep '04

Hello, I'm new to autoyast and it's configurationsystem. I wondered if/how it is possible to install different Version e.g. SLES 9 SuSE 9.0 and 9.1 Pro from 1 Installationserver. How can I bulid a class in which I can Specfy thefor example the Path of the Version I'd like to install. I couldn't find anything about that in the Documentation. Thanks for your help. -- Best regards Brigitte Warnecke-Schaer

2 1

Re: [suse-autoinstall] PXE install fails with SCSI disks
by Marcin Kurc 01 Sep '04

01 Sep '04

it is not a problem with PXE, your installation tree is not configured correctly You should either use SLES9 system to build the tree or configure it according to the docu/RELEASE-NOTES.en.html which can be found on cd #1 Also, you need to point you install to top dir not CD1 i.e. 'install=http://10.0.3.11/suse' thanks, Marcin Kurc Linux Impact Team Novell, Inc (973) 493-6235 >>>Steve Glines <sglines(a)is-cs.com> 09/01/04 2:30 pm >>> I'm building a PXE install lab for SUSE and other flavors of Linux. The DHCP and tftp servers are working. Note: I can fully install Red Hat from this lab but SUSE (SLES9 rc5) shows the following symptoms: 1.a cdrom install on the target system runs to completion in graphics mode. System is an HP PC with SCSI disk. 2.PXE install runs in non X-window mode (text) and fails to load scsi controllers * cannot find any disks. Fails even when modules are manually added. Here is the content of /tftpboot/pxelinux.cfg/default: default suse prompt 1 display boot.msg timeout 200 label redhat kernel redhat.kernel append initrd=redhat.root ramdisk_size=65536 label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536\ install=http://10.0.3.11/suse/CD1/ The file suse.kernel was copied from /boot/loader/linux in CD1 while suse.root was taken from /boot/loader/initrd in the same CD. I copied the contents of each CD into their own directories * I have CD1 * CD6 in the directory specified by http://10.0.3.11/suse/CD[1-6]. My test target system is a Celeron with 256MB Ram and an IDE disk; this setup fully installs SLES9. The only material change from this to the production lab is that the target system in the production lab has a SCSI disk and 1GB of ram. Help! Please Cheers -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0