October 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Interactive option checked BEFORE scripts?
by Jesse Keating 25 May '05

25 May '05

I'm using the modified.xml method of dynamic autoinstall control files. One of the things I wanted dynamic was the interactive or not choice, controlled by: <mode> <confirm config:type="boolean">false</confirm> If this was set to true, it should be interactive. I have this being set in modified.xml, however it does not take effect. Is this option checked BEFORE the pre-scripts run? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

3 2

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

07 Dec '04

Hi Anas, Thanks for the help. I've made all the fixes you and Marcin Kurc 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.

3 6

Newbie requires help with autoinstall on 9.0 - no display!
by mark＠atoneassociates.com 04 Nov '04

04 Nov '04

Hi - I am a newbie to linux so please forgive my ignorance. I recently tried to install 9.0 on to my machine. Its set up as dual boot with windows 98. The windows works fine (well as god as it normally does). When I boot into Linux everything works fine I think but when I am meant to get a login screen the monitor goes blank and the on light flashes like the computer isn't communicating with it anymore. The computer still seems to work bcasue if I hit any key I get some sort of repsonse but I still can't see anything. During the installation I had a warning message about the graphics card an Nvidia. I read some stuff and saw that I need to download different drivers. The problem is of course that I don't have a system to work on (at least I don't know how to access it wihtout the monitor!). Can anyone help please? Do I need to reinstall differently? Thanks for your patience, Mark

2 1

Password not being set right
by Jesse Keating 30 Oct '04

30 Oct '04

I've got an issue where my password for root isn't being set right. Or at all for that matter. My autoinstall file has the following sections: <security> <console_shutdown>reboot</console_shutdown> <cracklib_dict_path>/usr/lib/cracklib_dict</cracklib_dict_path> <cwd_in_root_path>no</cwd_in_root_path> <cwd_in_user_path>no</cwd_in_user_path> <displaymanager_remote_access>no</displaymanager_remote_access> <enable_sysrq>yes</enable_sysrq> <fail_delay>3</fail_delay> <faillog_enab>yes</faillog_enab> <gid_max>60000</gid_max> <gid_min>101</gid_min> <kdm_shutdown>all</kdm_shutdown> <lastlog_enab>yes</lastlog_enab> <obscure_checks_enab>yes</obscure_checks_enab> <pass_max_days>99999</pass_max_days> <pass_max_len>12</pass_max_len> <pass_min_days>0</pass_min_days> <pass_min_len>5</pass_min_len> <pass_warn_age>7</pass_warn_age> <passwd_encryption>md5</passwd_encryption> <passwd_use_cracklib>yes</passwd_use_cracklib> <permission_security>secure</permission_security> <run_updatedb_as>nobody</run_updatedb_as> <uid_max>60000</uid_max> <uid_min>100</uid_min> </security> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <username>root</username> <user_password>$1$QyzzjhWY$/wFY11PqReGKyxDSydLgh.</user_password> <forename></forename> <surname></surname> </user> </users> However once my system installs, root has NO password. And furthermore, if I run yast2 on the installed system, it would appear that the password encription is set to DES rather than MD5. Is this just flatly ignored, and since my password is too long for DES I get no password instead? Please help me to understand what is going on here. -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

2 2

Network Config not used
by Jesse Keating 30 Oct '04

30 Oct '04

I have network config set up so that eth0 is setup for DHCP: <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain></domain> <hostname></hostname> <nameservers config:type="list"/> <searchlist config:type="list"/> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <module></module> <startmode>onboot</startmode> <wireless>no</wireless> </interface> </interfaces> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"/> </routing> </networking> However once the system is installed, running yast2 shows that NO network devices were configured, and I have no network. Is there something wrong with my script, or is this yet another SUSE bug? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

3 4

Packages failing to install
by Nicholas DeClario 28 Oct '04

28 Oct '04

Hey guys. I am using SLES9 and have setup a custom package selection in the installer. Pretty much in the suse/setup/descr directory I created another .sel file, linked it all in and it's working. I have a list of packages custom to that .sel file that install fine. However, I recently started adding packages to it that are for some reason not installing. These are packages that are already found in the suse CORE CDs. Some I added work fine, others do not. I added telnet and telnet-server to the list. Telnet installs fine, telnet-server does not. I have scanned the logs in /var/log/YaST and have not even found any references to the packages that are not getting installed. I don't understand why this is happening. Thanks, -Nick

3 4

RE: cd-creator "skipping" files?
by anders.g.karlsson＠seb.se 28 Oct '04

28 Oct '04

Hi again, thought I'd try again and see if anyone has any hints for me. Perhaps someone knows where I can start looking to find out which application or code is responsible for copying the correct initrd, linux kernel, isolinux.bin, isolinux.cfg and other system files into the correct directory structure from which the iso is then created. I have a hard time dechiphering the y2log to find the correct referenses. Any hint whatsoever would be appreciated. Regards, Anders K.

2 1

Creating a bootable CD with info file
by fraser_bailey＠agilent.com 27 Oct '04

27 Oct '04

Hi does anyone know how to create a bootable CD which includes an info file? linuxrc is supposed to look in the root directory of the initrd, but I can't figure out how to get it into the initrd and then rebuild the CD. I've tried the instructions at http://www.tcm.phy.cam.ac.uk/~mr349/suse/boot.html after having modified the boot/loader/initrd file but I get an isolinux checksum error when I boot the CD. All I have to show is about 15 unusable CDs! any help would be appreciated

2 1

cd-creator "skipping" files?
by anders.g.karlsson＠seb.se 27 Oct '04

27 Oct '04

Hi all, I'm having some serious difficulty getting my home-made SLES9 installation CD working. I used to be able to create a fully functioning iso image, but after I upgraded to the latest patches things have stopped working. I use the autoyast and cd-creator modules to create my xml configuration and the generating the iso. For some reason I'm suddenly not getting anything copied into my boot/loader directory. So, I'm missing the initrd, isolinux.bin, isolinux.cfg among others. This makes the y2mkiso fail of course. Am I missing some fundamental knowledge here? I'm using: yast2-cd-creator Version 2.9.11, Release 0.2 autoyast2 Version 2.9.45, Release 0.2 All insight to the matter is welcome. Regards, Anders Karlsson Network & Internet SEB IT Mobile phone +46 70 639 30 57 Office phone +46 8 639 30 57 Postal address R C5, 106 40 Stockholm Visiting address Rissneleden 110 E-mail anders.g.karlsson(a)seb.se www.seb.net > > >

1 0

Skips ntp.
by Miro Barby 25 Oct '04

25 Oct '04

Hi. My problem is when i do a Minimal installation based on the default Minimal.sel file The ntp section in my autoinst.xml works out fine. With the exact same autoinst.xml where only the software sel. is different, the entire ntp section is skipped.?? Only difference in autoinst.xml: <software> <base>easy</base> </software> <software> <base>Minimal</base> </software> Any ideas.. Thanks in advance Miro.

1 0

Alice with SuSE Linux 9.0
by Maverick-IT 24 Oct '04

24 Oct '04

Hello everybody, as I'm working in a big company, that also has a section for informatics it is my task to test and analyze the possibilities to install a Linux system with SuSE Linux 9.0 and ALICE. This is also my project for my exams, which I will do in the next months. So, this is very important to me. I really hope, that you can help me. My period for accomplishing this project begins on Wednesday, 3rd of November and I have to finish it on Friday, 3rd of December. I have informed myself a little bit about ALICE yet. I also have set up a work environment at home, so that I can test the system earlier. The documentation I found was from http://www.suse.de/~fabian/alice/. The problem I have lies with the fact, that this documentation was written by testing an earlier version of "alice.rpm" and SuSE Linux I think. For example on page 19 of this documentation there is the following command: "cp -r /usr/ lib/alice/samples alice".But in my rpm version of SuSE Linux 9.0 there is no folder called "Samples". I also can't do the next steps in this documentation. My questions are: "Is it possible to autoinstall a SuSE Linux 9.0 system only with ALICE?" "And if it is possible, does anybody have a documentation for this?" It would be very nice, if somebody could help me very fast, because my exams are dependent on this project. Yours, Marek Troschinski

2 1

autoinstall error logfiles?
by Chris Carpinello 21 Oct '04

21 Oct '04

Several sections of my autoinst.xml are being ignored (specifically, runlevels, users and groups). There's nothing in /var/log/YaST2 that indicates an error parsing autoinst.xml. The profile validates with and without DTD validation in YaST2. So, I'm wondering... Is there a logfile that contains error/parsing/execution messages related to an autoinstall profile? If there is, adding a top level section to http://www.suse.de/~nashif/autoinstall/9.1/html/index.html with this information would be welcome. - Chris

1 0

escaping characters in encrypted passwords necessary?
by Chris Carpinello 21 Oct '04

21 Oct '04

When specifying encrypted passwords in the <user_password> field, are there any regexp/shell characters that need to be escaped such as ".", "$" or the like? - Chris

1 0

YaST hanging from Firebird 1.5.1 RPM
by McKenna, Simon (RGH) 21 Oct '04

21 Oct '04

Hi, There seems to be a small issue with the install of Firebird 1.5.1 RPM using YaST. I have not seen this problem with any other RPM's installed via YaST. I tried posting to the Firebird support group first but got no response. >From a clean SuSE 9.1 Pro distribution (latest updates), if I install the FirebirdSS-1.5.1.4481-0.i686.rpm using YaST, right at the end of the install YaST appears to hang, and the only fix I've found is to kill the y2base process. Note that the Firebird install is successful, I can see the fbguard and fbserver processes, and can connect to the example db, and everything comes up fine after a restart, it's just YaST can't close itself after the install. Is anyone able to confirm/deny this problem? RPM is here: http://tinyurl.com/4sp9g (I tried both NPTL and non-NPTL) Also, I'm shifting my development environment from Windows to Linux, and am still very much feeling my way around, so can anyone please tell me if I should be using the NPTL version of Firebird with the SuSE 9.1 Pro distribution? (I found documentation stating SuSE 9 Enterprise uses NPTL, but not for 9.1 Pro) Thanks for any help. peace - si sshnug.com

1 0

SLES8/UL SP3 autoinstall CD create issue
by Jun Wang 20 Oct '04

20 Oct '04

Hi, I wanna create a customize SLES8/UL SP3 CD which include autoinst.xml and info file and could used for CD instmode automatic install. The problem i met was the size of SP3 CD is too large to fit in ISO9660 CD. Could any one told me the proper steps to create such CD? the steps I used as bellow: 1 loop mount the SP3 iso # mount -o loop SLES8-SP3.iso /media/cdrom 2 copy the content to a directory # mkdir -p /datashare/SLES8/UL/SP3 # cd /media/cdrom; cp -a . /datashare/SLES8/UL/SP3 when i run this command, the output give following error: cp: will not create hard link'/datashare/SLES8/UL/SP3/./i386/update/SuSE-SLES/8/patches'to directory'/datashare/SLES8/UL/SP3/./i386/update/UnitedLinux/1.0/patches' cp: will not create hard link'/datashare/SLES8/UL/SP3/./i386/update/SuSE-SLES/8/rpm'to directory'/datashare/SLES8/UL/SP3/./i386/update/UnitedLinux/1.0/rpm' cp: will not create hard link'/datashare/SLES8/UL/SP3/./i386/update/SuSE-SLES/8/scripts'to directory'/datashare/SLES8/UL/SP3/./i386/update/UnitedLinux/1.0/scripts' cp: will not create hard link'/datashare/SLES8/UL/SP3/./linux/suse/i386-sles8/install'to directory'/datashare/SLES8/UL/SP3/./linux/suse/i386-ul1/install' cp: will not create hard link'/datashare/SLES8/UL/SP3/./linux/suse/i386-sles8/y2update'to directory'/datashare/SLES8/UL/SP3/./linux/suse/i386-ul1/y2update' cp: will not create hard link'/datashare/SLES8/UL/SP3/./linux/suse/i386-sles8'to directory'/datashare/SLES8/UL/SP3/./linux/UnitedLinux/i386-sles8' cp: will not create hard link'/datashare/SLES8/UL/SP3/./linux/suse/i386-ul1'to directory'/datashare/SLES8/UL/SP3/./linux/UnitedLinux/i386-ul1' cp: will not create hard link'/datashare/SLES8/UL/SP3/./i386/update/SuSE-SLES/8/rpm/setup/descr' to directory'/datashare/SLES8/UL/SP3/./UnitedLinux/setup/descr' Best Regards, Wang Jun

2 1

rules and classes
by Kai Moeller 20 Oct '04

20 Oct '04

Hi there, i know, there are enough topics with the same question... I've see the answer of Anas, he said that the documentation is updatet, but i didn't find any new information about rules and classes. in my repository folder I created the folders rules/, /classes in the rules directory i put my rules.xml, that w0rks pretty good! I also put some class files in my classes folder (with subdir) and it works fine, too. But is it possible to merge some different configuration sections (which are saved in different files) like software.xml base.xml network.xml so that i could define a rule (check about the mac adress) or more rules to merge these 3 parts of control file to a new (master) controlfile? when i define a two rules like this: <rule> <disksize> <match>/dev/hda 1</match> <match_type>greater</match_type> </disksize> <result> <profile>base</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <mac> <match>000475fcedbf</match> <match_type>exact</match_type> </mac> <result> <profile>base.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> i want to merge the base.xml and network.xml (in my base.xml are no definitions about the network options) I tried these kind of config, it works, but without my network settings. So the autoinstall process didn't merge these files I know, that kind of solutions isn't the right way, but i didnt know better, please help me :o) Finally i want to create some rules (and/or) classes to have only 1 base controlfile and some network config templates with different settings for each machine. Thx best regards Kai Möller

1 0

[suse-autoinstall] Can anyone post some examples using rules and classes with custom attributes
by Anthony Staples 19 Oct '04

19 Oct '04

Hello, According to the autoinstall/autoyast doc (Chapter 6), there is a way in which to combine rules and classes to dynamically generate the control file. The doc is vague on exactly how to do this... Would someone be kind enough to post some examples of this, if you are doing it. Also, how do you combine the rules file and with shell scripts to use the available custom1-5 attributes? Thanks!!! Tony Staples astaples(a)humana.com The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

3 2

Even More Customizing of SLES9 Autoinstall
by J.L.Francois 18 Oct '04

18 Oct '04

I have been moving my SLES8 autoinstallation info and control files to SLES9 and attempting to make sure I don't miss anything. I have: 1. Read docs at http://www.suse.de/~nashif/autoinstall/9.1/html/ 2. Updated my info files and made the change to "netsetup" The one thing I am sure I am missing is a way to ask for a "temporary" root password for initial login. What we want to do in SLES9, which we had customized for us in SLES8, is ask the installer for a temporary root password upfront at the same time we collect data in netsetup. I'd really like to know if a method exists where *any* information can be collected and used to modify a configuration file with a postinstall script by reading data written to install.inf during the execution of my own custom pre-install scripts. What we have already done is create a post-install script that automatically expires the root password ( passwd -e ) so we don't have to have installations with default root passwords that are known and documented laying around the enterprise. Any hints, tips, suggestions would be welcome. -- Jean L. Francois - Enterprise OS (LINUX) Load Development and Integration Engineering Group - Linux Counter Registered User #8863 1994-12-13 06:39:24

2 1

Automated Configuration of System Backup
by tobias.mucke＠de.man-mn.com 18 Oct '04

18 Oct '04

Hi everybody, if I understand the AutoYaST concept of SuSE right, each YaST2 module should work together with a XML file containing its configuration. What about the module "System Backup". May I configure that using AutoYaST? Mit freundlichen Grüßen Tobias Mucke -------------------------------------------------------------------------------------------------- MAN Nutzfahrzeuge AG Informationssysteme Organisation (I) Dachauer Straße 667 D-80995 München Tel.: +49 (0) 89 1580 5269 Mail-Adresse: Tobias_Mucke(a)mn.man.de Internet-Adresse: http://www.man-trucks.com -------------------------------------------------------------------------------------------------- This message and any attachments are confidential and may be privileged or otherwise protected from disclosure. If you are not the intended recipient, please telephone or email the sender and delete this message and any attachment from your system. If you are not the intended recipient, you must not copy this message or attachment or disclose the contents to any other person.

1 0

Antwort: [suse-autoinstall] additional package requires/forcing installorder [FinanzIT: Viruscheck]
by Hartmut.Dunker＠finanzit.com 18 Oct '04

18 Oct '04

Hi Chris, we've also included thirdparty and own packages to our autoinstall. To force the required dependencies we add in the packages file under suse/setup/descr in the "+Req: -Req:" section the dependencies manually. That works fine for us. Cheers Hartmut Chris Carpinello <ccarpinello@lanc An: suse-autoinstall(a)suse.com ope.com> Kopie: Thema: [suse-autoinstall] additional package requires/forcing install order 15.10.2004 22:49 [FinanzIT: Viruscheck] I have several thirdparty RPMs included within an autoinstall package selection. However, the requires list for these RPMs is very minimal and the RPMs get installed before the (undefined) prerequisite packages are installed. (For example, binutils and awk aren't installed yet when these packages attempt to use "cp" and "awk" because "binutils" and "awk" aren't in the requires list.) Without repackaging these RPMs from scratch with a lot of guesswork (the spec file isn't available), what options do I have to force additional prerequisites on these RPMs? Or is there a way to specify that a given package should be installed "later" rather than "sooner" in the process? In essence, I'm looking for something akin to EXTRA_PROV for requires (an "EXTRA_REQ" if you will). - Chris -- 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 requires/forcing install order
by Chris Carpinello 15 Oct '04

15 Oct '04

I have several thirdparty RPMs included within an autoinstall package selection. However, the requires list for these RPMs is very minimal and the RPMs get installed before the (undefined) prerequisite packages are installed. (For example, binutils and awk aren't installed yet when these packages attempt to use "cp" and "awk" because "binutils" and "awk" aren't in the requires list.) Without repackaging these RPMs from scratch with a lot of guesswork (the spec file isn't available), what options do I have to force additional prerequisites on these RPMs? Or is there a way to specify that a given package should be installed "later" rather than "sooner" in the process? In essence, I'm looking for something akin to EXTRA_PROV for requires (an "EXTRA_REQ" if you will). - Chris

1 0

services runlevel information ignored
by Chris Carpinello 15 Oct '04

15 Oct '04

I'm attempting to configure various services in a SuSE 9.1-based autoinstall. The default runlevel is recognized. However, the runlevel settings for the services (below) are being ignored during the CD install. User error or known bug? - Chris <configure> ... <runlevels> <default>3</default> <services config:type="list"> <service> <service_name>xdm</service_name> <service_status>disable</service_status> </service> <service> <service_name>smbfs</service_name> <service_status>disable</service_status> </service> <service> <service_name>slurpd</service_name> <service_status>disable</service_status> </service> <service> <service_name>ldap</service_name> <service_status>disable</service_status> </service> <service> <service_name>gpm</service_name> <service_status>disable</service_status> </service> <service> <service_name>apache2</service_name> <service_status>disable</service_status> </service> <service> <service_name>nfs</service_name> <service_status>disable</service_status> </service> <service> <service_name>nfsboot</service_name> <service_status>disable</service_status> </service> <service> <service_name>network</service_name> <service_start>2 3</service_start> </service> <service> <service_name>xntpd</service_name> <service_start>2 3</service_start> </service> </services> </runlevels> ... </configure>

1 0

X configuration for install and installed system
by Jesse Keating 15 Oct '04

15 Oct '04

I would like some more info regarding X config. The documentation says "FIXME" which doesn't help much. Using the autoyast module of yast2, I can set the monitor settings, and default depth, but there doesn't seem to be a way to hardcode the video chip. I would like to hardcode the 'VESA' driver to be used for both the install and the installed system. Is there a way to do this? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

1 0

Include file stubs in control xml
by Jesse Keating 15 Oct '04

15 Oct '04

I have a need to include external xml stubs in my control xml. Ideally, these stubs will be generated during a pre-script, and later included for things like disk partitioning, package selection, X configuration, stuff like that. Basically I'm a Kickstart admin, and I've written a python script that examines a system and some install time arguments and generates the above things on the fly according to our internal formulas. I need to replicate this system for SUSE installs using autoyast. Is this possible? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

5 11

use value for disk partitioning to reuse only Linux partitions
by Jesse Keating 12 Oct '04

12 Oct '04

I'm looking for the actual value that goes between <use></use> when listing out my partitions that says "Use only the existing Linux partitions". I'm pretty sure it exists given that the documentation talks about it, however I haven't seen the value listed. -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

1 0

AW: [suse-autoinstall] Include file stubs in control xml
by Hollmann Frank 11 Oct '04

11 Oct '04

Hi, if SLES8 should be installed: rules don't work here. Frank Hollmann -----Ursprüngliche Nachricht----- Von: Martin Vidner [mailto:mvidner@suse.cz] Gesendet: Freitag, 8. Oktober 2004 10:23 An: Jesse Keating Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] Include file stubs in control xml On Thu, Oct 07, 2004 at 01:25:15PM -0700, Jesse Keating wrote: > I have a need to include external xml stubs in my control xml. > Ideally, these stubs will be generated during a pre-script, and later > included for things like disk partitioning, package selection, X > configuration, stuff like that. > > Basically I'm a Kickstart admin, and I've written a python script that > examines a system and some install time arguments and generates the > above things on the fly according to our internal formulas. I need to > replicate this system for SUSE installs using autoyast. Is this > possible? Hi Jesse, I think rules and classes could cover your needs: http://www.suse.de/~nashif/autoinstall/9.1/html/rulesandclass.html -- Martin Vidner, developer SuSE CR, s.r.o. e-mail: mvidner(a)suse.cz Drahobejlova 27 tel:+420-296542373 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Updating install packages
by Ryan Allen 08 Oct '04

08 Oct '04

I have a http server that holds all the packages off my SuSE 9.0 CDs for remote installs. Is there an easy, automated method to update all the packages found on: http://www.suse.com/us/private/download/updates/90_i386.html I want to: 1) download JUST the packages listed as needing updating 2) put them in the directory I set up on the server 3) remove the old packages The only way I see to do this is one file at a time, without a bit of perl development, of course. What's the easiest way of doing this? Thanks, Ryan

1 0

Re: [suse-autoinstall] ISO Creation - Single CD Install
by Johannes Klug 07 Oct '04

07 Oct '04

"Jonathon M. Robison" <jrobiso2(a)ford.com> wrote on 07.10.2004 17:40:51: > I think you have to mess with the media.X files. Those files tell > the installer what CD has the needed rpm files. I just got a new idea: I'll install from DVD next. That way, YaST thinks there's only one "cd", methinks. I'll report if this was successful or not. Yet this will be next tuesday, earliest. Regards, Johannes

1 0

ISO Creation - Single CD Install
by Johannes Klug 07 Oct '04

07 Oct '04

Hello, I just tried to create an ISO file of my custom AutoYaST autoinst.xml file. The ISO was created, I burned it, and it really started to install. But then the installer asked me for the second SuSE 9.0 CD-ROM. I thought AutoYaST would copy all necessary rpms to ONE cd ... How can I make it burn a SINGLE cd-rom suitable for installation? Mit freundlichen Gruessen / Best regards Johannes Klug

1 0

Re: [suse-autoinstall] SLES9 autoinstall hangs at creating initrd
by Carl Pecinovsky 05 Oct '04

05 Oct '04

I don't see anything wrong with the directory structure, but you might want to check the PDF against the instructions given in the the release notes (CD1\docu\RELEASE-NOTES.en.html) under the section called "Setting up an installation server for network installations". Also, you should post at least the last part of the y2log. -Carl > I just cant get my network install to see the core distribution files. > It installs the SLES Admin guide then goes to "Finishing Basic Installation" > and hangs at "Creating initrd..." > I've followed http://yast2.suse.com/multiplesource/multiplesource.pdf > as closely as possible. > > Here is my directory > > ls -ld * > lrwxrwxrwx 1 root root 22 Oct 5 11:03 boot -> > sles9-x86_64/CD1/boot/ > lrwxrwxrwx 1 root root 24 Oct 5 11:03 content -> > sles9-x86_64/CD1/content > lrwxrwxrwx 1 root root 28 Oct 5 11:04 control.xml > -> sles9-x86_64/CD1/control.xml > drwxr-xr-x 6 root root 4096 Oct 5 11:03 core9-x86_64 > lrwxrwxrwx 1 root root 25 Oct 5 11:04 media.1 -> > sles9-x86_64/CD1/media.1/ > drwxr-xr-x 3 root root 4096 Oct 5 11:03 sles9-x86_64 > drwxr-xr-x 2 root root 4096 Oct 5 11:27 yast > > ls core9-x86_64/ sles9-x86_64/ yast/ > core9-x86_64/: > CD1 CD2 CD3 CD4 > > sles9-x86_64/: > CD1 > > yast/: > instorder order > > > cat yast/order > /sles9-x86_64/CD1 /sles9-x86_64/CD1 > /core9-x86_64/CD1 /core9-x86_64/CD1 > > cat yast/instorder > /sles9-x86_64/CD1 > /core9-x86_64/CD1 > > I can attach my y2log if anyone wants to see it. > > > Thanks for any help > Aaron > > > > On Mon, 4 Oct 2004, Durk S. wrote: > > > Okay peeps, as I already concluded earlier, my installation source wasn't > > completely okay. After some corrections, the AutoYaST install went like it > > should. > > > > Durk > > > >> Hey thanks! > >> > >> I've already found that PDF file, but this saves me a bit reading! ;-) > >> > >> Let's see if I can make a working network install this time. :-) > >> > >> Durk > >> > >>> Hi! > >>> > >>> Your source should look a bit different. > >>> > >>> From /usr/share/doc/packages/yast2-instserver/network-install.pdf: > >>> > >>> LINUX Enterprise Server 9 CD1 = SLES CD1 > >>> > >>> LINUX Enterprise Server 9 CD2 = CORE CD1 > >>> LINUX Enterprise Server 9 CD3 = CORE CD2 > >>> LINUX Enterprise Server 9 CD4 = CORE CD3 > >>> LINUX Enterprise Server 9 CD5 = CORE CD4 > >>> LINUX Enterprise Server 9 CD6 = CORE CD5 > >>> > >>> . > >>> |-- sles9-i386 > >>> | |-- CD1 > >>> | |-- boot > >>> | |-- docu > >>> | |-- media.1 > >>> | |-- suse > >>> | `-- yast > >>> |-- core9-i386 > >>> | |-- CD1 > >>> | |-- CD2 > >>> | `-- CD3 > >>> |-- boot -> sles9-i386/CD1/boot > >>> |-- media.1 -> sles9-i386/CD1/media.1 > >>> |-- content -> sles9-i386/CD1/content > >>> |-- control.xml -> sles9-i386/CD1/control.xml > >>> `-- yast SLES9 Network Install > >>> > >>> You have to set up a multisource installation as described in the PDF. > >>> > >>> Best regards, > >>> Andreas > >>> > >>> On Thu, 30 Sep 2004, Durk S. wrote: > >>> > >>>> Addition: > >>>> > >>>> I did a test with a floppy (for the profile) and SLES 9 CDs (as > >>>> installation source)... This actually works! So there must be > >>>> something wrong with my NFS installation source... or configuration > >>>> to find that source. > >>>> > >>>> The structure of the source looks like this: > >>>> > >>>> sles9 > >>>> sles9/boot > >>>> sles9/boot/root > >>>> sles9/boot/directory.yast > >>>> sles9/boot/README > >>>> sles9/boot/modules1 > >>>> sles9/boot/modules2 > >>>> sles9/boot/modules3 > >>>> sles9/boot/modules4 > >>>> sles9/boot/modules5 > >>>> sles9/boot/LIESMICH > >>>> sles9/boot/rescuefloppy > >>>> sles9/boot/loader > >>>> sles9/boot/loader/linux > >>>> sles9/boot/loader/10240768.spl > >>>> sles9/boot/loader/06400480.spl > >>>> sles9/boot/loader/memtest > >>>> sles9/boot/loader/message > >>>> sles9/boot/loader/12801024.spl > >>>> sles9/boot/loader/isolinux.bin > >>>> sles9/boot/loader/isolinux.cfg > >>>> sles9/boot/loader/initrd > >>>> sles9/boot/loader/16001200.spl > >>>> sles9/boot/loader/14001050.spl > >>>> sles9/boot/loader/bootlogo > >>>> sles9/boot/loader/08000600.spl > >>>> sles9/boot/README.DOS > >>>> sles9/boot/rescue > >>>> sles9/boot/LIESMICH.DOS > >>>> sles9/boot/bootdsk1 > >>>> sles9/boot/bootdsk2 > >>>> sles9/boot/bootdsk3 > >>>> sles9/boot/modules1.txt > >>>> sles9/boot/modules2.txt > >>>> sles9/boot/modules3.txt > >>>> sles9/boot/modules4.txt > >>>> sles9/boot/modules5.txt > >>>> sles9/sles9-i386/CD1/... (contents of SLES 9 CD 1) > >>>> sles9/sles9-i386/CD2/... (contents of SLES 9 CD 2) > >>>> sles9/sles9-i386/CD3/... (contents of SLES 9 CD 3) > >>>> sles9/sles9-i386/CD4/... (contents of SLES 9 CD 4) > >>>> sles9/sles9-i386/CD5/... (contents of SLES 9 CD 5) > >>>> sles9/sles9-i386/CD6/... (contents of SLES 9 CD 6) > >>>> sles9/yast > >>>> sles9/yast/order > >>>> sles9/yast/instorder > >>>> sles9/content > >>>> sles9/media.1 > >>>> sles9/media.1/directory.yast > >>>> sles9/media.1/media > >>>> sles9/media.1/products > >>>> sles9/media.1/info.txt > >>>> > >>>> I'm still figuring out this issue. > >>>> > >>>> Durk > >>>> > >>>>> Hi there, > >>>>> > >>>>> I've got exactly the same problem with a HP DL360 G3 using a > >>>>> network AutoYaST2 install. > >>>>> > >>>>> The last lines of y2log: > >>>>> > >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Storage.ycp:1573 > >>>>> CheckForLvmRootFs root=$["detected_fs":`ext2, > >>>>> "device":"/dev/cciss/c 0d0p7", "fs_options":$[], "fsid":131, > >>>>> "mount":"/", "nr":7, > >>>>> "region":[516, 16917], "type":`logical, "used_fs":`ext2, "uuid":"7f > >>>>> ca98f4-1cf7-4862-81c0-93866245ea3d"] > >>>>> dev=$["disk":"/dev/cciss/c0d0", "nr":7] 2004-09-30 13:57:50 <1> > >>>>> linux(697) [YCP] Storage.ycp:1576 CheckForLvmRootFs ret=false > >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Misc.ycp:146 > >>>>> WriteYaSTInf($["Keytable":"us.map.gz", "Language":"en_US", > >>>>> "RebootMsg":" 0", "Root":"reboot"]) = Keytable: us.map.gz > >>>>> Language: en_US > >>>>> RebootMsg: 0 > >>>>> Root: reboot > >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Bootloader.ycp:316 Writing > >>>>> bootloader configuration > >>>>> 2004-09-30 13:57:50 <3> linux(697) [libscr] Bootloader.ycp:361 No > >>>>> SCR instance found > >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Initrd.ycp:269 > >>>>> Initrd::Write called, changed: true, list: ["cciss"] > >>>>> 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:294 No SCR > >>>>> instance found2004-09-30 13:57:50 <3> linux(697) [libscr] > >>>>> Initrd.ycp:296 No SCR instance found2004-09-30 13:57:50 <1> > >>>>> linux(697) [YCP] Initrd.ycp:304 Modules [] were added to initrd not > >>>>> using Initrd module > >>>>> 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:313 No SCR > >>>>> instance found2004-09-30 13:57:50 <1> linux(697) [YCP] > >>>>> Initrd.ycp:316 Writing modules cciss 2004-09-30 13:57:50 <3> > >>>>> linux(697) [libscr] Initrd.ycp:317 No SCR instance found2004-09-30 > >>>>> 13:57:50 <3> linux(697) [libscr] Initrd.ycp:318 No SCR instance > >>>>> found2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:323 No > >>>>> SCR instance found2004-09-30 13:57:50 <3> linux(697) [libscr] > >>>>> Initrd.ycp:326 No SCR instance found2004-09-30 13:57:50 <3> > >>>>> linux(736) [ui] > >>>>> YUI_widgets.cc(createRichText):857 Invalid arguments for the Label > >>>>> RichText: `RichText > >>>>> (`opt (`plainText), nil) > >>>>> 2004-09-30 13:57:50 <3> linux(736) [ui] > >>>>> YUI_widgets.cc(widgetWithId):2426 No widget with `id( `ok_help ) > >>>>> 2004-09-30 13:57:50 <3> linux(736) [libycp] Initrd.ycp:254 No > >>>>> widget with `id( `ok_help ) > >>>>> > >>>>> I hope there's a solution. > >>>>> > >>>>> Durk > >>>>> > >>>>>> Date: Wed, 29 Sep 2004 10:01:15 +0200 > >>>>>> Message-ID: > >>>>>> <CD998562990BEA4D98E5EE624E492B3A5B163E(a)SMCR030V.corp1.ad1.seb.net> > >>>>>> From: <anders.g.karlsson(a)seb.se> > >>>>>> Subject: [suse-autoinstall] SLES9 autoinstall hangs at creating > >>>>>> initrd > >>>>>> > >>>>>> > >>>>>> Hi, > >>>>>> > >>>>>> I've run into a problem when doing an autoinstall (SLES9) from a > >>>>>> CD that I created using the YaST2 tools. Everything runs smooth up > >>>>>> to the point where it is "Creating initrd...", at this point the > >>>>>> installation just hangs. I'm trying to install on an HP DL380 G3 > >>>>>> with the cciss hardware raid driver. Anyone has the same > >>>>>> experience? > >>>>>> > >>>>>> Regards, > >>>>>> Anders > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For > >>>>> additional commands, e-mail: suse-autoinstall-help(a)suse.com > >>>> > >>>> > >>>> > >>>> > >>>> > >>> > >>> -- > >>> Andreas Vetter > >>> Universitaet Wuerzburg, Theoretische Physik 1 > >>> Am Hubland, 97074 Wuerzburg, Deutschland / Germany > >>> > >>> -- > >>> To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > >>> For additional commands, e-mail: suse-autoinstall-help(a)suse.com > >> > >> > >> > >> > >> -- > >> To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > >> For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > > > > > >

2 1

RE: [suse-autoinstall] Automatic Installation in Secondary Drive
by Quayle, Bill 05 Oct '04

05 Oct '04

Just a couple of questions: Are you using SuSE 9.1 Professional? Are you booting off of the cdrom/dvd for the install? I've done many dual (and triple) boot installations, and it's always given me the option of resizing my XP install... When I know I'm going to dual boot a machine, I load XP first, but manually partition the drive into a "C" and "D" drive. XP only uses the "C" drive for the install, so when it's time to load SuSE, I destroy the "D" partition, and use this space for swap and /. -----Original Message----- From: avt022(a)student.uit.no [mailto:avt022@student.uit.no] Sent: Tue 10/5/2004 9:44 AM To: Quayle, Bill Cc: suse-autoinstall(a)suse.com Subject: RE: [suse-autoinstall] Automatic Installation in Secondary Drive Thanks for such a quick reply :D I tried what you suggest but YaSt didn't give me an option. It was either deleting my XP partition or not installing SuSe 9.1 at all... That's why I want to do it in a different harddrive... I'm afraid of messing things up with XP again. I have used a lot of time recovering my system and files and I don't want to do it again :) Do you have any suggestions on what the problem could be? thanks. I really appreciate it. > There should be no reason to use the USB drive. SuSE 9.1 and XP should > have no trouble sharing a 30 Gb drive. When installing SuSE, you will > reach a step early in the installation process that suggests resizing your > XP NTFS partition, then mounting that partition under SuSE as /windows/C. > When booting your laptop, the SuSE bootloader (grub) will present you > with a choice to either boot XP or XP. From XP, you won't be able to > see your SuSE install, but from SuSE, you will have *read only* access > to XP, as noted above. > > Hope this helps.... > > > > -----Original Message----- > From: avt022(a)student.uit.no [mailto:avt022@student.uit.no] > Sent: Tue 10/5/2004 8:35 AM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] Automatic Installation in Secondary Drive > > Hi, > > I originally tried to install SuSe 9.1 and Windows XP in the same hard > drive (30 GB). It seemed too complicated for me to make the partitions > since Win XP (NFTS) occupied the whole disk... So I gave it a shot with > only SuSe 9.1 in that drive for a couple of days. But it gave me too much > trouble with my hardware. I had gotten something working just before > something else stopped functioning... I use too many hardware applications > and I can't be too patient. > > But I anyways want to give SuSe 9.1 a chance now that I have bought it. > > Is it possible to install SuSe 9.1 in an external LaCie P2 hard drive that > connects to my laptop through a USB cable? I'm thinking of buying such a > hard drive, but only if Linux can be installed there. How does the > computer boot into Linux then if I have Windows XP still in my main drive? > Would this ruin something in Windows? > > Which steps should I follow to guarantee that I can switch with no > problems > between the main and external drive from one OS to the other? > > I need a step by step 'Howto' on this. > Thanks. > > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > >

1 0

Re: [suse-autoinstall] SLES9 autoinstall hangs at creating initrd
by Durk S. 05 Oct '04

05 Oct '04

Hi there, I've got exactly the same problem with a HP DL360 G3 using a network AutoYaST2 install. The last lines of y2log: 2004-09-30 13:57:50 <1> linux(697) [YCP] Storage.ycp:1573 CheckForLvmRootFs root=$["detected_fs":`ext2, "device":"/dev/cciss/c 0d0p7", "fs_options":$[], "fsid":131, "mount":"/", "nr":7, "region":[516, 16917], "type":`logical, "used_fs":`ext2, "uuid":"7f ca98f4-1cf7-4862-81c0-93866245ea3d"] dev=$["disk":"/dev/cciss/c0d0", "nr":7] 2004-09-30 13:57:50 <1> linux(697) [YCP] Storage.ycp:1576 CheckForLvmRootFs ret=false 2004-09-30 13:57:50 <1> linux(697) [YCP] Misc.ycp:146 WriteYaSTInf($["Keytable":"us.map.gz", "Language":"en_US", "RebootMsg":" 0", "Root":"reboot"]) = Keytable: us.map.gz Language: en_US RebootMsg: 0 Root: reboot 2004-09-30 13:57:50 <1> linux(697) [YCP] Bootloader.ycp:316 Writing bootloader configuration 2004-09-30 13:57:50 <3> linux(697) [libscr] Bootloader.ycp:361 No SCR instance found 2004-09-30 13:57:50 <1> linux(697) [YCP] Initrd.ycp:269 Initrd::Write called, changed: true, list: ["cciss"] 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:294 No SCR instance found2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:296 No SCR instance found2004-09-30 13:57:50 <1> linux(697) [YCP] Initrd.ycp:304 Modules [] were added to initrd not using Initrd module 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:313 No SCR instance found2004-09-30 13:57:50 <1> linux(697) [YCP] Initrd.ycp:316 Writing modules cciss 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:317 No SCR instance found2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:318 No SCR instance found2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:323 No SCR instance found2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:326 No SCR instance found2004-09-30 13:57:50 <3> linux(736) [ui] YUI_widgets.cc(createRichText):857 Invalid arguments for the Label RichText: `RichText (`opt (`plainText), nil) 2004-09-30 13:57:50 <3> linux(736) [ui] YUI_widgets.cc(widgetWithId):2426 No widget with `id( `ok_help ) 2004-09-30 13:57:50 <3> linux(736) [libycp] Initrd.ycp:254 No widget with `id( `ok_help ) I hope there's a solution. Durk > Date: Wed, 29 Sep 2004 10:01:15 +0200 > Message-ID: > <CD998562990BEA4D98E5EE624E492B3A5B163E(a)SMCR030V.corp1.ad1.seb.net> > From: <anders.g.karlsson(a)seb.se> > Subject: [suse-autoinstall] SLES9 autoinstall hangs at creating initrd > > > Hi, > > I've run into a problem when doing an autoinstall (SLES9) from a CD that > I created using the YaST2 tools. Everything runs smooth up to the point > where it is "Creating initrd...", at this point the installation just > hangs. I'm trying to install on an HP DL380 G3 with the cciss hardware > raid driver. Anyone has the same experience? > > Regards, > Anders

4 7

adding installation sources in/after auto-install
by lists.suse.com＠afdelingp.dk 05 Oct '04

05 Oct '04

Hi, Is it possible to set up installation sources for a host, either in the auto- install or after it (eg. in a post-install script)? As far as I can see, it is only possible using YaST's interface, which requires user interaction. Best regards, Morten -- Morten K. Poulsen <lists.suse.com(a)afdelingp.dk> http://www.afdelingp.dk/

2 2

RE: [suse-autoinstall] Automatic Installation in Secondary Drive
by avt022＠student.uit.no 05 Oct '04

05 Oct '04

Thanks for such a quick reply :D I tried what you suggest but YaSt didn't give me an option. It was either deleting my XP partition or not installing SuSe 9.1 at all... That's why I want to do it in a different harddrive... I'm afraid of messing things up with XP again. I have used a lot of time recovering my system and files and I don't want to do it again :) Do you have any suggestions on what the problem could be? thanks. I really appreciate it. > There should be no reason to use the USB drive. SuSE 9.1 and XP should > have no trouble sharing a 30 Gb drive. When installing SuSE, you will > reach a step early in the installation process that suggests resizing your > XP NTFS partition, then mounting that partition under SuSE as /windows/C. > When booting your laptop, the SuSE bootloader (grub) will present you > with a choice to either boot XP or XP. From XP, you won't be able to > see your SuSE install, but from SuSE, you will have *read only* access > to XP, as noted above. > > Hope this helps.... > > > > -----Original Message----- > From: avt022(a)student.uit.no [mailto:avt022@student.uit.no] > Sent: Tue 10/5/2004 8:35 AM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] Automatic Installation in Secondary Drive > > Hi, > > I originally tried to install SuSe 9.1 and Windows XP in the same hard > drive (30 GB). It seemed too complicated for me to make the partitions > since Win XP (NFTS) occupied the whole disk... So I gave it a shot with > only SuSe 9.1 in that drive for a couple of days. But it gave me too much > trouble with my hardware. I had gotten something working just before > something else stopped functioning... I use too many hardware applications > and I can't be too patient. > > But I anyways want to give SuSe 9.1 a chance now that I have bought it. > > Is it possible to install SuSe 9.1 in an external LaCie P2 hard drive that > connects to my laptop through a USB cable? I'm thinking of buying such a > hard drive, but only if Linux can be installed there. How does the > computer boot into Linux then if I have Windows XP still in my main drive? > Would this ruin something in Windows? > > Which steps should I follow to guarantee that I can switch with no > problems > between the main and external drive from one OS to the other? > > I need a step by step 'Howto' on this. > Thanks. > > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > >

1 0

RE: [suse-autoinstall] Automatic Installation in Secondary Drive
by Quayle, Bill 05 Oct '04

05 Oct '04

There should be no reason to use the USB drive. SuSE 9.1 and XP should have no trouble sharing a 30 Gb drive. When installing SuSE, you will reach a step early in the installation process that suggests resizing your XP NTFS partition, then mounting that partition under SuSE as /windows/C. When booting your laptop, the SuSE bootloader (grub) will present you with a choice to either boot XP or XP. From XP, you won't be able to see your SuSE install, but from SuSE, you will have *read only* access to XP, as noted above. Hope this helps.... -----Original Message----- From: avt022(a)student.uit.no [mailto:avt022@student.uit.no] Sent: Tue 10/5/2004 8:35 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Automatic Installation in Secondary Drive Hi, I originally tried to install SuSe 9.1 and Windows XP in the same hard drive (30 GB). It seemed too complicated for me to make the partitions since Win XP (NFTS) occupied the whole disk... So I gave it a shot with only SuSe 9.1 in that drive for a couple of days. But it gave me too much trouble with my hardware. I had gotten something working just before something else stopped functioning... I use too many hardware applications and I can't be too patient. But I anyways want to give SuSe 9.1 a chance now that I have bought it. Is it possible to install SuSe 9.1 in an external LaCie P2 hard drive that connects to my laptop through a USB cable? I'm thinking of buying such a hard drive, but only if Linux can be installed there. How does the computer boot into Linux then if I have Windows XP still in my main drive? Would this ruin something in Windows? Which steps should I follow to guarantee that I can switch with no problems between the main and external drive from one OS to the other? I need a step by step 'Howto' on this. Thanks. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Automatic Installation in Secondary Drive
by avt022＠student.uit.no 05 Oct '04

05 Oct '04

Hi, I originally tried to install SuSe 9.1 and Windows XP in the same hard drive (30 GB). It seemed too complicated for me to make the partitions since Win XP (NFTS) occupied the whole disk... So I gave it a shot with only SuSe 9.1 in that drive for a couple of days. But it gave me too much trouble with my hardware. I had gotten something working just before something else stopped functioning... I use too many hardware applications and I can't be too patient. But I anyways want to give SuSe 9.1 a chance now that I have bought it. Is it possible to install SuSe 9.1 in an external LaCie P2 hard drive that connects to my laptop through a USB cable? I'm thinking of buying such a hard drive, but only if Linux can be installed there. How does the computer boot into Linux then if I have Windows XP still in my main drive? Would this ruin something in Windows? Which steps should I follow to guarantee that I can switch with no problems between the main and external drive from one OS to the other? I need a step by step 'Howto' on this. Thanks.

1 0

yast2-utils rpm
by Brad Hudson 05 Oct '04

05 Oct '04

Does anyone know wher I can get the yast2-utils rpm for SLES9? I've seen this bundle referenced many times on this list, but it is not installed with SLES9, even when all package selections are made.

2 1

SUSE 9.1 and SLES9 autoyast bug
by Dax Kelson 03 Oct '04

03 Oct '04

I have a chrooted postinstall script that works fine on SLES8 and SL9.0 but not SL9.1 and SLES9. The bug is that any changes done to the /etc/password and /etc/shadow files are lost. The two things I have tried: useradd -m -p '$1$J1n.X/QK$hj1vaqARqf.O/RWisMGRn1' visitor ..... echo 'visitor:x:1000:100::/home/visitor:/bin/bash' >> /etc/passwd echo 'visitor:$1$J1n.X/QK$hj1vaqARqf.O/RWisMGRn1:12686:0:99999:7:::' >> /etc/shadow cp -a /etc/skel /home/visitor chown -R visitor /home/visitor chgrp -R users /home/visitor In either case, the commands complete with no errors, but when the system comes up after the install is all finished, I have the following: # ls -al /home total 2 drwxr-xr-x 4 root root 96 Sep 25 12:53 . drwxr-xr-x 22 root root 512 Sep 25 06:52 .. drwxr-xr-x 7 guru users 568 Sep 25 12:53 guru drwxr-xr-x 7 1000 users 568 Sep 25 06:44 visitor ^^^^ Note the how just the UID is listed. This is futher proof that chown command did work correctly in the postinstall script, ie, when chown ran, the visitor account was in the /etc/passwd file. And there is no visitor line in the /etc/password and /etc/shadow file.

2 2

determining HTTP or NFS or CD install
by Ryan Allen 03 Oct '04

03 Oct '04

Hi list! I've got a complete working installation system with autoyast - but only if it's being served by NFS (after PXE boot the client) or on a burned CD. The problem is, because of limitation with the network in our office, we have to use HTTP after PXE booting. I have some chroot install scripts that copy over a few .tgz files off the NFS server (or the CD) and un-tar them in a post install script. With HTTP, "cp" doesn't work, and I have to do an HTTP GET. I'd like to have one autoyast.xml file handle all three situations. So my questions are: 1) Is there a way to determine which type of installation is taking place during chroot script environment? (is it CD or PXE/NFS or PXE/HTTP?) 2) If it is HTTP, how does one obtain the server address, and the path to the root of the install tree during chroot Much appreciation for any help I can get! Thanks, -- Ryan

2 1