October 2002 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: AW: [suse-autoinstall] applying patches
by Anas Nashif 09 Dec '02

09 Dec '02

* "Petersen, Jörg" <j.petersen(a)msh.de> [Oct 01. 2002 14:04]: > > > > For 8.1, which should be available by now, we have included > > a script to > > > do this. Format has changed and it is much more powerfull. > Just curious: what's the name of the script? > Thx, Jörg /usr/lib/YaST2/bin/create_package_descr Anas -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

4 3

Selecting an alternative kernel
by Neruda, Steve (SCI TW) 04 Nov '02

04 Nov '02

I'm building a configuration in which I need to use on of the alternate kernels supplied in the 8.1 distribution. I tried adding it as a package but it wound up installing both packages (k_smp and k_psmp). What is the correct way to specify what kernel package to load? SteveN

2 1

Initrd Creater
by Daniel.Rothmund＠geberit.com 31 Oct '02

31 Oct '02

When I install the system with autoyast , the initr File does not exist in the boot Partition ! Freundliche Grüsse Daniel Rothmund

3 4

Question about X11 configuration
by Alexander.Gehrig＠RSD.rohde-schwarz.com 31 Oct '02

31 Oct '02

hi i disable 3d-support but while auto-installation i get allways a request about it. <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> <resolution>1024x768</resolution> <start_x11 config:type="boolean">true</start_x11> <monitor> <display> <frequency config:type="integer">75</frequency> <height config:type="integer">768</height> <max_hsync config:type="integer">60</max_hsync> <max_vsync config:type="integer">75</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">50</min_vsync> </display> <monitor_device>1024X768@75HZ</monitor_device> <monitor_vendor>VESA</monitor_vendor> </monitor> </x11> Any ideas? bye Alexander

2 1

X problem explained
by Marcel Ritter 31 Oct '02

31 Oct '02

Hi again! I had some more test runs concerning my X problem: Here's what I figured out: X installation/configuration works fine - as long as you don't use VNC. Same setup with VNC failes to do any configuration, and does not even have the link /usr/X11R6/bin/X set ... As I like the VNC feature I'd like to use it - if possible with X configuration done automatically. Any hints? Ciao, Marcel ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

2 1

sendmail dependency problem
by Christian Stoltze 31 Oct '02

31 Oct '02

Hello, please can anybody help me in solving a rpm dependency problem in SuSE 8.1? I don't know why yast2 installs the package sendmail? In my selection list (need1.sel) which I attached to this mail, sendmail is not included. But any rpm in need1.sel requires sendmail. And I will be happy if I know the name of this rpm. I don't know the mechanism how yast2/rpm resolves the dependencies. Perhaps anybody can give me a good startpoint where I can read how I can check the dependencies with shell commands. What I have done so far is: get all tags for every rpm in the suse tree... $ RPMTAG_LIST=`rpm --querytags | sort` $ pkg=... $ for tag in $RPMTAG_LIST $ do echo "Flag $tag:" rpm -qp --queryformat "'%{$tag}'" $pkg done and search after sendmail and/or REQUIRE. Regards CS -- Christian Stoltze Computer Science, University of Constance (Lake Constance/SW-Germany) Email: Christian.Stoltze(a)uni-konstanz.de Voice: +49 (0)7531 88-4448 Fax: +49 (0)7531 88-3577

2 2

sendmail dependency problem 2
by Christian Stoltze 31 Oct '02

31 Oct '02

Sorry, I don't have attached need1.sel in my previous mail with subject "sendmail dependency problem". Hello, please can anybody help me in solving a rpm dependency problem in SuSE 8.1? I don't know why yast2 installs the package sendmail? In my selection list (need1.sel) which I attached to this mail, sendmail is not included. But any rpm in need1.sel requires sendmail. And I will be happy if I know the name of this rpm. I don't know the mechanism how yast2/rpm resolves the dependencies. Perhaps anybody can give me a good startpoint where I can read how I can check the dependencies with shell commands. What I have done so far is: get all tags for every rpm in the suse tree... $ RPMTAG_LIST=`rpm --querytags | sort` $ pkg=... $ for tag in $RPMTAG_LIST $ do echo "Flag $tag:" rpm -qp --queryformat "'%{$tag}'" $pkg done and search after sendmail and/or REQUIRE. Regards CS -- Christian Stoltze Computer Science, University of Constance (Lake Constance/SW-Germany) Email: Christian.Stoltze(a)uni-konstanz.de Voice: +49 (0)7531 88-4448 Fax: +49 (0)7531 88-3577

1 0

Autoyast2 Raid
by Daniel.Rothmund＠geberit.com 31 Oct '02

31 Oct '02

When I install des System with Raid Partitions. The System directly sync the raid Partition. The Performance of the Installation goes down . Have you any Idea ? Freundliche Grüsse Daniel Rothmund

1 0

create_package_descr problem
by Christian Stoltze 30 Oct '02

30 Oct '02

Hello, I am running into a problem after calling create_package_descr: Several rpms during auto-installation are not installed and the client cannot reboot. In the logfile /mnt/var/log/YaST2/y2logRPM of the client I see errors: ... devs-2002.9.4-9.i586.rpm failed execution of devs-2002.9.4-9 script failed, exit status 255 ... netcfg-2002.9.4-6.noarch.rpm failed execution of netcfg-2002.9.4-6 script failed, exit status 255 ... After copying the original files {packages,packages.DU,packages.de,packages.en} to suse/setup/descr the auto-installation succeeds. Has anybody a hint? I have diff'ed packages and packages.orig, but besides of the failing "+Aut: ... -Aut:" in the new file packages both files look identically. What I have done in detail on the installation server: 1) copy all data from DVD to a shared directory (/net/lin_suse8.1) # mount -o ro /cdrom && cd /cdrom && df -k . Filesystem 1k-blocks Used Available Use% Mounted on /dev/hdc 4481888 4481888 0 100% /media/cdrom # cp -a . /net/lin_suse8.1 # diff -r --brief . /net/lin_suse8.1 # cd / && umount /cdrom 2) I do not need the src tree # cd /net/lin_suse8.1/suse/src # du -sk . 1808706 . # rm *.src.rpm 3) I backup the descr directory # cd /net/lin_suse8.1/suse/setup/ # mv descr descr.orig # mkdir descr # cd descr.orig # cp -a . ../descr 4) I generate new package files # cd /net/lin_suse8.1/suse # /usr/lib/YaST2/bin/create_package_descr \ -d /net/lin_suse8.1/suse -l english -l german using settings: datadirs: /net/lin_suse8.1/suse languages: english,german output dir: ./setup/descr/ is not a directory: ignoring extra_provides: file /usr/share/autoinstall/EXTRA_PROV not found! .............................[...]... done processed 2844 packages now recoding to UTF-8: packages packages.DU packages.en packages.de Regards CS -- Christian Stoltze Computer Science, University of Constance (Lake Constance/SW-Germany) Email: Christian.Stoltze(a)uni-konstanz.de Voice: +49 (0)7531 88-4448 Fax: +49 (0)7531 88-3577

2 2

Edit a file while or after the installation
by Prengel, Ralf 30 Oct '02

30 Oct '02

I've to insert several entries after an installation in the crontab file. What s the best way to solve this problem? Thanks Ralf Prengel

2 1

RE: [suse-autoinstall] Edit a file while or after the installatio n
by Neruda, Steve (SCI TW) 30 Oct '02

30 Oct '02

I've always used "ed" scripts in Solaris jumpstart installations. It doesn't require a temp file and is highly scriptable. A little archaic and obtuse sometimes but very reliable once you get the hang of it. SteveN -----Original Message----- From: Prengel, Ralf [mailto:ralf.prengel@comline.de] Sent: Wednesday, October 30, 2002 3:17 AM To: 'suse-autoinstall(a)suse.com' Subject: [suse-autoinstall] Edit a file while or after the installation I've to insert several entries after an installation in the crontab file. What s the best way to solve this problem? Thanks Ralf Prengel -- 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] No kernel with 8.1
by Marcel Ritter 30 Oct '02

30 Oct '02

> > > y2logs would be helpfull here. > > > > I attached them and the autoyast.xml file. > > According to this file, the workaround I sent you is not included: > It should read Sorry - I was a bit in a hurry and changed report/confirm instead of general/mode/confirm. This fixed my problem with the missing kernel - and had some influence on my X setup: - now I don't even get the 640x480 default mode: X doesn't start, but XF86Config seems unmodified. But the link to /usr/X11R6/bin/X seems to be missing (was there before). Any hints? > Btw, you should always configure a base software selection. Did it! > Anas > -- > Anas Nashif <nashif(a)suse.com>, SuSE Linux AG > Montreal (Laval), Canada ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

1 0

my experience with autoinstall (for other beginners who found the documentation very cryptic)
by Sidney Elmer 30 Oct '02

30 Oct '02

Here is my experience with autoinstall, including questions that I was not able to find the answers to by looking in the documentation or the suse-install mailing list archive. Description of system: I want to install SuSE 8.0 on a cluster of dual PentiumIIIs over nfs. I set up the nfs server with the installation repository by copying the dvd that came with the distribution to the hard drive of the nfs server as described in the documentation. Suse8.0 was already installed on the nfs server. I also set up the configuration repository on the nfs server using the Autoinstall module for Yast2 to create the control files. I used the bootdisk image (/disks/bootdisk) from the dvd that came with the distribution as a template to create floppies which contained an info file and the initial networking information needed to connect to the nfs server. This required that I use the modules1 and modules3 disks in addition to the bootdisk, but I figured switching disks twice is a lot easier than compiling my own kernel (I am still a beginner). Step 1: Configure nfs server to export install repository. Made sure root install directory was entered in /etc/exports on nfs server: nfsserver:# cat /etc/exports $Install_root/ $target_ip(ro) Next, exported directory on nfs server: nfsserver:# /usr/sbin/exports -rv Enabled portmap service requests from $target_ip on the nfs server (following entry was put in /etc/hosts.allow on nfs server): nfsserver:# cat /etc/hosts.allow portmap:$target_ip Made sure nfs server was active (type command on nfs server): nfsserver:# /etc/rc.d/nfsserver start At this point, nfs server should be ready. Step 2: Create floppy disks containing the info file. I first copied the bootdisk from installation repository to a separate workstation hard drive and mounted it using loop device: workstation:# scp $user@nfsserver:$Install_root/disks/bootdisk . workstation:# mount -oloop bootdisk /mnt/bootdisk List the contents of the bootdisk: workstation:# ls /mnt/bootdisk total 1428 drwxr-xr-x 2 root root 512 Dec 31 1969 . drwxr-xr-x 5 root root 128 Sep 25 16:18 .. -r-xr-xr-x 1 root root 11912 Apr 3 2002 ldlinux.sys -rwxr-xr-x 1 root root 964815 Apr 3 2002 linux -rwxr-xr-x 1 root root 523 Apr 3 2002 message -rwxr-xr-x 1 root root 399010 Oct 2 18:14 small -rwxr-xr-x 1 root root 81988 Apr 3 2002 suselogo -rwxr-xr-x 1 root root 600 Oct 2 18:16 syslinux.cfg Here, I was confused to see a file called small instead of the expected initrd. No worries, it is the initial ram disk, just with a different name to confuse us. I modified both small and syslinux.cfg, but all other files were left untouched. First, I modified small. We need to add an info file to the root directory of this ram disk. Copy the file to the local directory, decompress it, and mount it using the loop device: workstation:# cp /mnt/bootdisk/small . workstation:# zcat small > small.tmp workstation:# mount -oloop small.tmp /mnt/small Create an info file and copy it to root directory of ram disk: workstation:# cat info insmod tulip #or the necessary network driver for your target machine. workstation:# cp info /mnt/small Unmount small.tmp, compress it, and replace new compressed ram disk on bootdisk: workstation:# umount /mnt/small workstation:# gzip -9 small.tmp workstation:# cp small.tmp.gz /mnt/bootdisk/small #make sure to overwrite old small file Next, I modified syslinux.cfg, umounted the newly created bootdisk, and copied the bootdisk to floppy: workstation:# cat /mnt/bootdisk/syslinux.cfg --snip-- label linux kernel linux append initrd=initrd ramdisk_size=65536 rw netdevice=eth0 \ server=x.x.x.a serverdir=$Install_root ip=x.x.x.b \ netmask=255.255.255.0 gateway=x.x.x.c nameserver=x.x.x.d \ autoyast=nfs://x.x.x.a/$Install_root/$control_file instmode=nfs --snip-- workstation:# umount /mnt/bootdisk workstation:# dd if=bootdisk of=/dev/fd0 At this point, the floppy now has all the information it needs for your target machine to connect to the nfs server. At this point, the control file is found and the installation initiated over nfs. Problems with creating boot floppy: The documentation in Section 5.2 gave me plenty of grief. First off, it wasn't immediately clear what was meant by the command line that linuxrc uses to detect an autoinstallation. It wasn't until after lots of time-consuming trial and error that I figured out that the command line refers the "append" entry in the syslinux.cfg file (see above). Once I figure this out, I thought I'd enter as little information on this "command line" as was needed and put everything else in the info file. Bad move on my part. After trying unsuccessfully for many, many times to get the networking information to work in the info file, I finally gave up the info file and decided to enter all the information on the "command line" in syslinux.cfg (see above). Voila, it worked like a charm. So the only information I ended up putting in the info file was the "insmod tulip" line (this was recognized by linuxrc, so I knew that it actually found and parsed t! he info file). There is no example in the documentation for what the entries in the info file should look like. Should they be like this?: ip=x.x.x.a server=x.x.x.b nameserver=x.x.x.c etc. or should they look like this?: ip x.x.x.a serever x.x.x.b nameserver x.x.x.c etc. or should they look like something else? Neither one of these syntaxes worked, so it must be entered some other way. But you wouldn't know what the syntax should be, because there are no examples of what it should look like. Could someone clue me in on this, please? So, once I decided to put this networking information in syslinux.cfg, the next major frustration surfaced. At this point, I was able to connect to the nfs server, but it couldn't find the control file. First, I tried to use nfs. The entry in syslinux.cfg looked like this -- autoyast=nfs://x.x.x.a:$Install_root. Once that didn't work, I tried using -- autoyast=default. Problems here as well (see below). It wasn't until later, when I was looking through the mailing list archives that I found an email explaining that he had also spent many hours of frustration trying to get nfs to recognize the control file, only to find that the documentation had a typo: the entry in syslinux.cfg should've looked like this -- autoyast= nfs://x.x.x.a/$Install_root. The colon should be a slash. This has since been changed in the documentation, but I hope you are fortunate to have the updated documentation so you don't spend hours before resorting to the mailing list archive. The problems I had with autoyast=default. Section 5.2 explains that the default behavior of yast2 is to look for a file named autoinst.xml in the root directory of the initial ram disk on the floppy, then in the root directory of the installation repository on the nfs server, then finally on the root directory of the floppy. Well, yast2 found the autoinst.xml file in the root directory of the installation repository, but it never found it at either place on the floppy. Could someone help me out on this? Of all the options for specifying the location of the control file, placing it in the root directory of the installation repository was the least desirable to me (I didn't want 100 or more control files in the root installation directory - what a mess!!). I was very happy I wasn't left with this last option when I found the solution to the nfs issue mentioned above. Still, I spent way too much time just getting yast2 to find a control file, anywhere, just because the doc u! mentation was either incorrect or unclear. Step 3: Create the control file. I used the autoinstall module for yast2 to create control files. The graphic user interface made creating the control file very easy (thank goodness, because everything else had been difficult so far). Overall, the documentation is helpful for this step, but there were a few issues or concerns that came up. First, my concerns. These didn't cause problems, but just seemed inconsistent. When I set up the partitioning plan, yast2 specified that the swap partition was to be created as a linux native filesystem. Here is a snippet from my control file: <partition> <crypt_fs config:type="boolean" >false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol" >swap</filesystem> <filesystem_id config:type="integer" >131</filesystem_id> <format config:type="boolean" >true</format> <mount>swap</mount> <size>1.0GB</size> <type>Linux native</type> </partition> I was concerned about this until I tested it and found out that the swap partition was working properly. This is an FYI. Next, I wrote a post-install script to add users to the system using useradd. One of the users has a capital letter as the first character in his username. The creation of the user account failed. Is this a limitation imposed by yast? I was able to create the user account containing capital letters in the username on the command line when I didn't go through yast. Again, this is not a major problem, just a minor inconvenience. Finally, there were three issues that are serious problems that I need help to solve. First, when specifying the location of the control file in syslinux.cfg, I had to give the explicit name of the control file rather than use the hex ip number convention. I would like to give the directory of the control file repository, then have yast figure out which control file to use based on the ip number of the target machine. I am not using DHCP, but am hard coding the ip number in the command line in syslinux.cfg. Does hex ip filename matching work only with DHCP? The documenation says that it works with nfs as well tftp. I called the name of the control file 1A2B3C4D (random hex numbers for illustration) but yast didn't recognize it for the machine with the given target ip number. I used capital hex digits like it says in the documentation. Does it require the .xml suffix? Any help would be appreciated. Second, I would like to configure my hosts.allow and hosts.deny configuration files within the autoinstall process. There was an email in the archives of the mailing list from a user who experienced the same problems that I had, but there were no posted solutions. I typed the xml directives in my control file as explained in Section 4.13, because there is no facility to add them from within yast2. When I loaded the control file back into yast2's configuration module, it changed the entries I had typed in to add /etc/hosts.allow. <config_file> was replaced by <listentry> and the <![CDATA[ directive was erased. I added the CDATA directives back in, but the whole section is completely ignored during installation. The /etc/hosts.allow and /etc/hosts.deny files are present as though I never even tried to modify them. Here is a snippet of the code: <files config:type="list" > <listentry> <file_contents><![CDATA[ sshd: x.x.x.a sshd: x.x.x.b sshd: x.x.x.c sshd: x.x.x.d sshd: x.x.x.e sshd: x.x.x.f ]]></file_contents> <file_path>/etc/hosts.allow</file_path> </listentry> <listentry> <file_contents><![CDATA[ ALL:ALL ]]></file_contents> <file_path>/etc/hosts.deny</file_path> </listentry> </files> Any suggestions on how to modify this, so that yast will actually write these configurations to /etc? Last of all, I would like to add an rpm file to the installation that is not present in the current distribution. I found an email similar to this in the mailing list archive, but the links that were given on the subject no longer existed. I would appreciate a section in the documentation on how to do this. This is what I tried to do. In the directory $Install_root/suse/setup/descr on the nfs server, there is a file, common.pkd, with entries for all the rpm packages in the installation. I added this entry to this file: ##----- gromacs ----- Filename: gromacs-3.1.4-1.i386.rpm RpmName: gromacs Series: custom InstPath: 01 /custom/ Size: 7581000 2735235 Buildtime: BuiltFrom: Flag: RpmGroup: Custom Copyright: AuthorName: Version: 3.1.4-1 Requires: libsfftw.so.2 libsrfftw.so.2 Provides: do_dssp editconf eneconv ffscan g_anaeig g_analyze g_angle g_bond g_bundle g_chi g_cluster g_clustsize g_confrms g_covar g_density g_dielectric g_dih g_dipoles g_disre g_dist g_dyndom g_enemat g_energy g_gyrate g_h2order g_hbond g_helix g_lie g_mdmat g_mindist g_morph g_msd g_nmeig g_nmens g_order g_potential g_rama g_rdf g_rms g_rmsdist g_rmsf g_rotacf g_saltbr g_sas g_sgangle g_sorient g_tcaf g_traj g_velacc genbox genconf genion genpr gmxcheck gmxdump grompp highway luck make_ndx mdrun mk_angndx ngmx pdb2gmx protonate tpbconv trjcat trjconv trjorder wheel x2top xpm2ps xrama I also created the directory, custom, in the $Install_root/suse directory. I placed the gromacs-3.1.4-1.i386.rpm file in this directory (custom). I also made sure the fftw package was installed. Also, in the custom directory, I added this file: nfsserver:# cat INDEX.english gromacs-3.1.4-1.i386.rpm: GROMACS molecular dynamics package Then, in the control file, I added an entry as directed in Section 4.6.3. Here is the snippet: <extra_packages> <package_location> custom </package_location> <packages config:type="list"> <package>gromacs</package> </packages> </extra_packages> The installation failed when it tried to install gromacs. This is the message I got: gromacs.rpm: file not found Do I need to add a flag to the entry in common.pkd? Other than that, I have no idea why it doesn't work. Any insights would be appreciated. I hope that this will be helpful to others who have also tried to use autoinstall, but ran into similar problems. Sid

3 6

RE: [suse-autoinstall] Edit a file while or after the installation
by Kugelberg, Thorsten 30 Oct '02

30 Oct '02

Hey, my suggestion would be: echo "bra" >> /etc/crontab Regards Thorsten -----Original Message----- From: Prengel, Ralf To: 'suse-autoinstall(a)suse.com' Sent: 30.10.2002 09:17 Subject: [suse-autoinstall] Edit a file while or after the installation I've to insert several entries after an installation in the crontab file. What s the best way to solve this problem? Thanks Ralf Prengel -- 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] Failure in confirm mode
by Holger Hellmuth 30 Oct '02

30 Oct '02

> This is no bug. And it is intended to work so. If you need the second > proposal page with misc. hardware then you mostly dont need the > autoinstallation at all! > > Anas Why? The misc. hardware selections are exactly the selections that change from PC to PC (because of differing hardware). Language and software selection on the other hand seem to be the parameters you really don't want to change when installing a group of PCs, i.e. they benefit the most from autoinstallation (especially the time-consuming software selection). When people ask about why the "load/save package selections" feature of previous suse versions is no more, they get the answer (not from Suse AFAIK, but from other list members) that autoinst fills that role now. Well, obviously this is not the case then. Holger.

4 3

GDT Raidcontroller problem
by Prengel, Ralf 30 Oct '02

30 Oct '02

Starting a normal installtion using the first Suse 8.1 CD works but using AutoYast (a modified Suse 8.1 Cd) stops with the message that there ist no space availiable. It seems as if the controller isn t recognized. Any hints?

1 0

autofind of destination partition
by Alexander.Gehrig＠RSD.rohde-schwarz.com 30 Oct '02

30 Oct '02

Hi all, I am looking for a solution for following problem: We build the linux and swap partitions with a seperated tool. Now autoyast2 should find the partions automaticly, the partions could be on device sda or hda. The partions have a different partitionnumber on each system. Is it possible to define only the partionstyp instead of device and partitionnumber to install suse 8.1? Any ideas? bye Alexander

1 0

SLES 8 IA64 / UL 1.0 Beta Autoyast2 question.
by Egan Ford 29 Oct '02

29 Oct '02

I just received my beta CDs today and am ready to attempt to setup autoyast2. I know kickstart very well, but am new to autoyast2. Q. In what order do I copy the CDs if I want to autoyast a IA64 SLES 8.0 install? Q. in what order do I copy the CDs if I want to autoyast a IA64 UL 1.0 install? Q. Where are the network boot images for IA64? and Q. Is Anas' autoyast2.pdf I printed from the Web today all the docs I need? Thanks.

2 1

No kernel with 8.1
by Marcel Ritter 29 Oct '02

29 Oct '02

Hi! I'm trying to get autoyast NFS installation working. But I've got 2 problems: 1. I'm installing the standard package selection, but after the install finished there's no kernel installed?!?! Is this intended? Do I need to add it to the packages? 2. My X11 configuration is totally ignored. All I get is the default 640x480 resolution with very few colors. Anyone else having this problem? Ciao, Marcel ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

2 3

Grub- password
by bernd.ronecker＠t-online.de 29 Oct '02

29 Oct '02

Hi, Is it possible to set a grub md5- password using the xml-file? Or do I have to create a post-install script? Regards Bernd

2 1

Failure in confirm mode
by Miguel Gómez 29 Oct '02

29 Oct '02

Hi, I'm trying to set up a partially automated installation CD, where several fixed parameters are taken from the profile and the rest are asked to the user during the installation process. I've included the following entries in my XML profile in order to use the "confirm" mode during automated installation: ... <mode> <upgrade config:type="boolean">false</upgrade> <confirm config:type="boolean">true</confirm> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> ... Everything works all right in the first part of the installation process: The XML is read and a confirmation page appears to let you make changes or configure the items that were not included in the profile. The problem comes in the second stage of the installation: There is no confirmation page during the configuration process, so only the items included in the profile are configured and there is no opportunity to make changes or configure additional devices. My questions are: Is this a bug in the automated installer or am I configuring something wrong? If it's a bug, is there any patch or upgrade to fix it? Thanks in advance, Miguel Gómez Rodríguez gomez(a)dit.upm.es

2 1

RE: [suse-autoinstall] Create boot CD for use with NFS Server but without DHCP?
by Kugelberg, Thorsten 29 Oct '02

29 Oct '02

Hello, 1) Put the info File onto the root of the floppy 2) Here you have different pssibilities! The easiest is to specify it like this: autoyast=file://suse/setup/descr/internet_cafe_BAC.xml This causes yast to look for the file internet_cafe_BAC.xml in the dir suse/setup/descr of the installation directory... other possibilities: have a look at http://www.suse.de/~nashif/autoinstall/8.0/html/invoking.html 3) Have never heard of that file! "isolinux.cfg"?! Or do you mean syslinux.cfg? That is mainly for Kernel append Parameters just like lilo.conf! (Please correct me if I am wrong) 4) You can just do the same as during an DHCP installation. Just add a few lines to the 'info' file. What you need is the IP, gateway, netmask and nameserver. Also have a look at : http://www.suse.de/~nashif/autoinstall/8.0/html/invoking.html -----Original Message----- From: Erik Soyez To: suse-autoinstall(a)suse.com Sent: 29.10.2002 08:33 Subject: [suse-autoinstall] Create boot CD for use with NFS Server but without DHCP? Good Day, I need to create my own boot CDs for three or four PCs. I need a completely unattended installation. AutoYast2, SuSE-8.0. I CANNOT USE DHCP: 1) Where do I put my "info" file (NFS Server, CD, initrd, ...)? 2) Where do I put my ".xml" file? 3) What do I put into "isolinux.cfg"? 4) How do I tell it not to use dhcp? I have tried about 30 different combinations now and it always says "Sending dhcp request to eth0".... Any ideas what I could be doing wrong? I would prefer a solution with identical CDs but that's not a requirement. Thank you very very much! Erik Soyez. P.S. I apologize, if some people get this Email twice due to technical problems. -- -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Create boot CD for use with NFS Server but without DHCP?
by Erik Soyez 29 Oct '02

29 Oct '02

Good Day, I need to create my own boot CDs for three or four PCs. I need a completely unattended installation. AutoYast2, SuSE-8.0. I CANNOT USE DHCP: 1) Where do I put my "info" file (NFS Server, CD, initrd, ...)? 2) Where do I put my ".xml" file? 3) What do I put into "isolinux.cfg"? 4) How do I tell it not to use dhcp? I have tried about 30 different combinations now and it always says "Sending dhcp request to eth0".... Any ideas what I could be doing wrong? I would prefer a solution with identical CDs but that's not a requirement. Thank you very very much! Erik Soyez. P.S. I apologize, if some people get this Email twice due to technical problems. --

1 0

grub problem with 8.1 nfs install?
by Jeff Martin 28 Oct '02

28 Oct '02

Greetings- I'm having a problem booting after an 8.1 install via nfs/pxeboot. Get the following message on boot: kernel (hd0,0)/vmlinuz root=/dev/hda2 ide=nodma init=linuxrc initrd (hd0,0)/initrd Error 15: File not found Press any key to continue... my xml script contains the following bootloader options under <install> <bootloader> <activate config:type="boolean">false</activate> <kernel_parameters>ide=nodma</kernel_parameters> <lba_support config:type="boolean">false</lba_support> <linear config:type="boolean">false</linear> <location>mbr</location> </bootloader> Is anyone else seeing this problem or have I screwed something up? I've tried with <activate config> as true....didn't help. removing the initrd (hd0,0)/initrd line has allowed me to boot the box after this error message. Any ideas would be appreciated. TIA, -Jeff

2 2

Find Partions
by Alexander.Gehrig＠RSD.rohde-schwarz.com 28 Oct '02

28 Oct '02

Hi All, is it possible to write a pre-script with the following features: - scanning the device sda / had for partions withe the partionsnumber 131 / 132 - enter this nubmer an devices in the installscript thanks bye Alexander

2 1

VNC + SSH
by Marcel Ritter 27 Oct '02

27 Oct '02

Hi! Is it possible to use SSH and VNC in parallel without user interaction? I tried UseSSH=1 and VNC=1 - but I get "run 'yast' to start the installation" and nothing happens until I log into the machine and start yast. I'd like to log into the machine to check the logs during installation, without having to type 'yast' at some point. TIA, Marcel ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

2 1

Post-Chroot Problem and SMP-Kernel-Bug
by Jens Kühnel 27 Oct '02

27 Oct '02

Hi *, first a thanks to Anas! You installer makes it a lot easier to setup a classroom. The grub-bootdisk is also excelent! No F*** Bootdisk compiling! :-) But I have a problem with the post-chroot script. I wrote an script to change the IP and a lot of other things. But the script is never started. I created the file with yast2 a couple of times or write it my one, but nothing helps! I´ve attached the autoinstall.xml. Another problem is the smpkernel. I think there is a bug with the eepro100 drivers. They don´t work with the smp kernel, the driver loads but there is no RX or TX. When I append "nosmp maxcpus=0" every thing works fine. The k_deflt kernel works good, too. I hope someone will help me with this problems. CU Jens

2 5

mysql
by Frank Kaldewey 27 Oct '02

27 Oct '02

Hallo, yast install mysql now I try to run mysql linux:/bin # mysql start ERROR 2002: Can 't connect to löcal MYSQL server throu socket' /var/lib/mysql/mysql.sock' (2) /var/lib/mysql is an emty foulder but I expect that yast creats files in that foulder Thx Frank

2 1

Problems with Suse 8.1 Autoinstall (conversion problems)
by Tobias Koeck 27 Oct '02

27 Oct '02

Hello Under Suse 8.0 Professional we have made an autoyast xml file. But under Suse 8.1 Pro it isn`t possible to import all options from the Suse 8.0 xml file. If we import the old xml file and saved it after the import, under the newer autoyast some of the options were gone. How can I easily convert the Suse 8.0 xml file to 8.1? Is there an included script, a file or an option in the new autoyast. Greerings and thanx Tobias

2 1

help with ftp install of 8.1
by Kevin Jackey 25 Oct '02

25 Oct '02

tried my best to verify that the server I was loading from (mirror.mcs.anl.gov) had mirrored 8.1, and it appeared to have done so. Re-transferred and burned the boot.iso cd, then ran the starttup and pointed it to /pub/suse/i386/8.1 (also tried /current). Still got the same effect where it puills up the installation program, I choose my settings, it scans for packages, then displays the "No base selection available" and "ERROR:No proposal" messages under the "SOFTWARE" selection item. Any ideas what I am doing wrong? Could someone that it worked for post their steps, and any ideas I might be able to follow? This is very frustrating! _________________________________________________________________ Unlimited Internet access -- and 2 months free! Try MSN. http://resourcecenter.msn.com/access/plans/2monthsfree.asp

2 1

Suse 7.2 & Ibm NetFinit 5000
by Joao Carlos 24 Oct '02

24 Oct '02

Hello I Am trying to install suse 7.2 on Ibm NetFinit 5000, however afert kernel load scsi modules and I try to start Installation, Suse do not access cdrom and show message 'could mount cdrom'. When I Try to load cdrom manual through menu 'Load Cdrom Driver' appears message. CDrom is already loaded! My Cdrom is a IDE - LG CRD8322B ATAPI My SCSI Driver is Ibm ServerRAID Somebody can help me. Joao

1 0

RE: [suse-autoinstall] Post-Chroot Problem and SMP-Kernel-Bug
by Kugelberg, Thorsten 24 Oct '02

24 Oct '02

Hey, >But I have a problem with the post-chroot script. I wrote an script to >change the IP and a lot of other things. But the script is never >started. I created the file with yast2 a couple of times or write it my >one, but nothing helps! >I´ve attached the autoinstall.xml. The xml file looks good to me... Are the scripts created under /var/adm/autoinstall/scripts? And if so, how do the logs look like? And what about the other scripts? are they executed? >Another problem is the smpkernel. I think there is a bug with the >eepro100 drivers. They don´t work with the smp kernel, the driver loads >but there is no RX or TX. When I append "nosmp maxcpus=0" every thing >works fine. The k_deflt kernel works good, too. We normally do not have such a Problem! Which kernel do you use in detail? Regards Thorsten

1 0

Antwort: [suse-autoinstall] Post-Chroot Problem and SMP-Kernel-Bug
by Michael.Jeromin＠mummert.de 24 Oct '02

24 Oct '02

Hi Jens, I don't know if this will help you, but have you realized that the chroot-scripts are now in a new section?! Since SuSE 8.1 they are in the scripts section and not as under 8.0 directly in the configure section. Another point is that they won't be executed in the new target file system but in the old root filesystem, if I remember our experiences well ... Hope this will help you !! Cheers, Michael Mit freundlichen Grüßen Michael Jeromin Consultant Integrated Business Consulting Mummert Consulting AG Tel.: 0179 / 4778310 Fax: 0251 / 98158 - 4634 Jens Kühnel <listuser@kue An: suse-autoinstall(a)suse.com hnel.org> Kopie: (Blindkopie: Michael Jeromin/mummert/de) Thema: [suse-autoinstall] Post-Chroot Problem and SMP-Kernel-Bug 24.10.02 09:09 Hi *, first a thanks to Anas! You installer makes it a lot easier to setup a classroom. The grub-bootdisk is also excelent! No F*** Bootdisk compiling! :-) But I have a problem with the post-chroot script. I wrote an script to change the IP and a lot of other things. But the script is never started. I created the file with yast2 a couple of times or write it my one, but nothing helps! I´ve attached the autoinstall.xml. Another problem is the smpkernel. I think there is a bug with the eepro100 drivers. They don´t work with the smp kernel, the driver loads but there is no RX or TX. When I append "nosmp maxcpus=0" every thing works fine. The k_deflt kernel works good, too. I hope someone will help me with this problems. CU Jens <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config=" http://www.suse.com/1.0/configns"> <configure> <nfs config:type="list"> <nfs_entry> <mount_point>/install</mount_point> <nfs_options>ro,wsize=8192,rsize=8192,soft,intr</nfs_options> <server_path>10.0.0.1:/install</server_path> </nfs_entry> </nfs> <scripts> <chroot-scripts config:type="list"> <script> <filename>ipaddress.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[# # (C) 2002 Jens Kuehnel spam(a)kuehnel.org # (just change the spam to my given name :-) # License GLP # # current IP to SuSE8-Configuration # takes current IP from the installation system and write it in the configfiles # hostname is taken from rev-lookup # cat > /etc/resolv.conf << EOF nameserver 10.0.0.1 search linux.foo domain linux.foo EOF #The ip Address is allready available ! :-) #IP=$(ifconfig eth0 | grep "inet addr" | cut -d : -f 2 | cut -d " " -f 1) echo $IP > /tmp/ipaddresse cat > /etc/sysconfig/network/ifcfg-eth0 <<EOF IPADDR=$IP NETMASK=255.0.0.0 NETWORK=10.0.0.0 BROADCAST=10.255.255.255 STARTMODE=onboot UNIQUE="1234" EOF host $IP | cut -d " " -f 5 | cut -d . -f -3 > /etc/HOSTNAME HOSTNAME=$(cat /etc/HOSTNAME) echo $HOSTNAME > /tmp/ipaddresse-hostname cat > /etc/hosts <<EOF # # hosts This file describes a number of hostname-to-address # mappings for the TCP/IP subsystem. It is mostly # used at boot time, when no name servers are running. # On small systems, this file can be used instead of a # "named" name server. # Syntax: # # IP-Address Full-Qualified-Hostname Short-Hostname # 127.0.0.1 localhost $IP $HOSTNAME EOF cat > /etc/sysconfig/network/routes << EOF default 10.0.0.1 - - EOF ]]> </source> </script> <script> <filename>you-infos.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ echo "ftp://10.0.0.1/pub/suse" > /etc/suseservers chattr +i /etc/suseservers cat > /etc/sysconfig/onlineupdate <<EOF # # While starting YOU ( YaST2-Online-Update ) the default ftp serverlist # will be updated by the call "wget" to www.suse.de. This list will be # stored under /etc/suseservers. # Set YAST2_LOADFTPSERVER to "no", if you do not want to reload the # ftp serverlist. # YAST2_LOADFTPSERVER="no" # # Registration code for business products # REG_CODE="" # # Registration password for business products # REG_PASSWORD="" # # User for used proxy # PROXY_USER="" # # Password for used proxy # PROXY_PASSWORD="" EOF ]]> </source> </script> <script> <filename>nettime.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[# # update Time from install and write to hardware-clock # ntpdate 10.0.0.1 hwclock --systohc ]]> </source> </script> </chroot-scripts> <post-scripts config:type="list"/> <pre-scripts config:type="list"/> </scripts> <security> <encryption>md5</encryption> </security> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <user_password>$1$hcZxkyzz$WPiSFiwbrSPEGfkln.G.w0</user_password> <username>root</username> </user> <user> <encrypted config:type="boolean">true</encrypted> <user_password>$1$CzzzYyzz$udBZLLbPuIHZoPJMaH9gc0</user_password> <username>linux</username> </user> </users> <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">true</enable_3d> <resolution>1024x768</resolution> <start_x11 config:type="boolean">false</start_x11> </x11> </configure> <install> <bootloader> <activate config:type="boolean">true</activate> <lba_support config:type="boolean">true</lba_support> <linear config:type="boolean">false</linear> <location>mbr</location> </bootloader> <general> <clock> <hwclock>localtime</hwclock> <timezone>Europe/Berlin</timezone> </clock> <keyboard> <keymap>german</keymap> </keyboard> <language>de_DE</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">true</forceboot> <interactive_boot config:type="boolean">false</interactive_boot> <reboot config:type="boolean">false</reboot> </mode> </general> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">131</partition_id> <size>200M</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>4000M</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">100</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">100</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">100</timeout> </warnings> </report> <software> <addons config:type="list"> <addon>Basis-Devel</addon> <addon>Basis-Sound</addon> <addon>Gnome</addon> <addon>Kde-Desktop</addon> <addon>Kde</addon> <addon>LAMP</addon> <addon>LDAP-Server</addon> <addon>Multimedia</addon> <addon>Network</addon> <addon>SuSE-Documentation</addon> <addon>X11</addon> </addons> <base>default</base> <packages config:type="list"> <package>mc</package> </packages> </software> </install> </profile> -- 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] Disable CANCEL Button
by Kugelberg, Thorsten 23 Oct '02

23 Oct '02

Hello, if I understood SuSE right, this is not possible! But in my opinion it is even more important to close the shells on tty2,5,6 and 9! I am doing this within my prescript: kill -9 $(ps -ef | grep bash | grep tty2 | grep -v grep | awk '{ print $2 }') kill -9 $(ps -ef | grep bash | grep tty5 | grep -v grep | awk '{ print $2 }') kill -9 $(ps -ef | grep bash | grep tty6 | grep -v grep | awk '{ print $2 }') kill -9 $(ps -ef | grep lsh | grep tty9 | grep -v grep | awk '{ print $2 }') not very nice but it works. Anas said that an option like 'noshells' will be implemented into yast. I really hope that there will be something for the cancel buttons. If I remember right, there was something like that with SuSE 7.x autoinstall... Regards Thorsten -----Original Message----- From: Joachim.Tork(a)gad.de To: suse-autoinstall(a)suse.com Sent: 22.10.2002 14:48 Subject: [suse-autoinstall] Disable CANCEL Button Hello everybody, I wonder if it is possible to diable the CANCEL button during installation. Does anybody know ? Joachim -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 3

RE: [suse-autoinstall] How to save package sets in suse 8.1?
by Kugelberg, Thorsten 23 Oct '02

23 Oct '02

Hallo, >I get the new package names (of an already installed 8.1 system) >with the command rpm: > ># rpm -qa | sed -e 's/-[0-9].*$//' > new_rpm_list.tmp just to make your life a little bir easier: RPM has the Option to give you the names of the installes packages. So you do not need the sed: 'rpm -qa --qf "%{NAME}\n"' Regards Thorsten

2 1

Tip: Using VNC with autoinstall
by Anas Nashif 23 Oct '02

23 Oct '02

Hi, We have vnc support during installation but I have never made any use of it till a couple of days ago and I found it very usefull when auto-installing remote machines. To enable vnc, enter vnc=1 VNCPassword=<some password> on the command line. The installer will then show a URL on the console which you can connect to using a java enabled browser. Now you can monitor the installation in the browser.. Regards, Anas -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

2 1

Disable CANCEL Button
by Joachim.Tork＠gad.de 22 Oct '02

22 Oct '02

Hello everybody, I wonder if it is possible to diable the CANCEL button during installation. Does anybody know ? Joachim

1 0

Speichern einer Konfiguration
by Claudia Goldbrunner 22 Oct '02

22 Oct '02

Hallo Wir haben vor ein paar Tagen SuSE 8.1 Prof installiert und dabei mit Erschrecken festgestellt, dass es nicht mehr moeglich ist, waehrend der Installation mit YAST die Konfiguration auf Diskette zu speichern um spaeter dann mit Hilfe dieser Diskette, auf anderen Rechnern die selbe Konfiguration installieren zu koennen. Versteckt sich diese Moeglichkeit jetzt irgendwo anders (nicht mehr im YAST) ? Ich kann mir fast nicht vorstellen, dass man dieses Feature nicht mehr integriert hat, da dass der Tod eines jeden admins ist, wenn er auf allen Rechnern die Packete von Hand installieren muss. Waere wirklich dankbar, wenn mir jemand verraten kann, was mit diesem Feature passiert ist. Gruss Claudia

2 1

How to save package sets in suse 8.1?
by "König, Oliver" 22 Oct '02

22 Oct '02

Hi, in suse 8.1 I can't find a simple feature of Yast2 in SuSE 8.0 in the menu "Install/Remove software" : "load/save package selections". Is there any possibility for that in SuSE 8.1. Since we have only few machines that are often configured quite differently, we'd like to install them by hand and simply copy the package selection set from another machine... Greetings ok ---------------------------------------------------- Oliver Koenig Center of Structure Technologies Institute of Mechanical Systems LEO C12 ETH Zurich CH-8092 Zurich Phone : +41 1 632 23 28 Fax : +41 1 632 17 02 Mail : okoenig(a)imes.mavt.ethz.ch WWW : http://www.imes.ethz.ch/st/ ----------------------------------------------------

2 1

Re: [suse-autoinstall] Manual steps on automated installation. And a BUG
by Holger Hellmuth 21 Oct '02

21 Oct '02

Hate to reply to my own mail, but I forgot to mention: The bug report is for vanilla Suse 8.1, but I haven't seen a patch on suse claiming to correct the problem, so I guess it still is a problem. Holger.

1 0

Re: [suse-autoinstall] Manual steps on automated installation. And a BUG
by Holger Hellmuth 21 Oct '02

21 Oct '02

> I'm trying to set up an automated installation CD for standalone PCs. With this CD I would like to perform some steps of the installation process manually There is an excellent article about autoinstall in the german magazine 'Linux-Magazin' 10/02 (just as a hint to german readers). To do some things manually you have to add the following to your autoinst.xml (if you don't know what that is, look at www.suse.de/~nashif/autoinstall) <general> <mode> <confirm config:type="boolean">true</confirm> </mode> </general> Language selection (in this example for Germany): <general> <hwclock>localtime</hwclock> <keyboard>german</keyboard> <language>de_DE</language> <timezone>Europe/Berlin</timezone> </general> BUT, there is a problem/bug. You can change the values of the first install-screen (i.e language, software installation, mouse) but you never get to see the second round where you specify root password, network device, sound etc. Instead you get a b/w barebones login screen, where you can login as root (with password empty). The hardware recognition will present you with some of the missing configuration choices, others, like root password and screen resolution configuration you have to start by yourself. After that reboot (or possibly reset X-server, didn't try that) to get the normal login screen. My guess is that confirm=true is ignored by the second stage installer. Holger.

1 0

Setup CUPS as Default
by Alexander.Gehrig＠RSD.rohde-schwarz.com 21 Oct '02

21 Oct '02

Hi what to do to install CUPS instead of BSD-Prinigsystem? bye Alex

1 0

Manual steps on automated installation
by Miguel Gómez 21 Oct '02

21 Oct '02

Hi, I'm trying to set up an automated installation CD for standalone PCs. With this CD I would like to perform some steps of the installation process manually (partitioning, package selection...) and others automatically (language and keyboard type selection, X configuration...). I have succeeded in doing so with SuSE 7.3, but it seems that with SuSE 8.0 you either make a full unattended installation or the system doesn't install at all. Is it possible to perform this kind of installation in SuSE 8? If so, how? In case it's not possible with SuSE 8.0, will it be possible with SuSE 8.1? Any help will be appreciated. Thanks in advance. Regards, Miguel Gómez Rodríguez gomez(a)dit.upm.es

1 0

autoyast and LVM
by "Petersen, Jörg" 18 Oct '02

18 Oct '02

Hello, I've problems to understand where to put "LVM Logical Volumes" in the XML-File Is <lvm config:type="list"> after <partitioning config:type="list"> or inside or where? In http://www.suse.de/~nashif/autoinstall/8.1/html/c300.html#AEN437 it seems indented - but in which context? Thank you very much... Jörg

1 0

RE: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: [suse-autoinstall] NFS Install
by Kugelberg, Thorsten 18 Oct '02

18 Oct '02

Hey, why don't you put up a webtool for example where you specify the hardware and it gives you the individual bootdisk back... Works fine for me!-) Regards Thorsten -----Original Message----- From: Alexander.Gehrig(a)RSD.rohde-schwarz.com To: suse-autoinstall(a)suse.com Sent: 18.10.2002 15:26 Subject: [suse-autoinstall] Antwort: RE: [suse-autoinstall] Antwort: [suse-autoinstall] NFS Install Hi Thorsten That's true to do this with only one disk, but only on special hardware. I am building an autoinstallation for many system with other hardware. This kind of autoinstallation needs more modules than on one disk avaiable, so you need more disks. bye Alex |--------+--------------------------------> | | "Kugelberg, Thorsten" | | | <thorsten.kugelberg@re| | | altech.de> | | | | | | 18.10.2002 10:23 | | | | |--------+--------------------------------> >----------------------------------------------------------------------- -----| | | | An: Alexander Gehrig/RSD@RSD | | Kopie: | | Thema: RE: [suse-autoinstall] Antwort: [suse-autoinstall] NFS | | Install | >----------------------------------------------------------------------- -----| Hallo, this is also possible with just one bootdisk! I am doing that... To make that possible, you have to mount the bootdisk loopback, and extrakt the initrd from it, unzip the initrd, mount it as well and copy all the modules you need into it. If you are a little bit lucky, it fits!-) Otherwise you have to build a new one... In the end you have to do everything in reverse order! (zip the initrd, copy it into the bootdisk... regards thorsten -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Antwort: Re: [suse-autoinstall] Antwort: [suse-autoinstall] NFS Install
by Alexander.Gehrig＠RSD.rohde-schwarz.com 18 Oct '02

18 Oct '02

hi i think the cd-solution is pretty good, but if you want to upload this image to a company-network for all administrator you have to make sure that all administrators have a cd-burner and you need licence for burner software (windows). bye Alex |--------+------------------------------> | | Rohit | | | <rohits(a)mahindrabt.c| | | om> | | | | | | 18.10.2002 10:44 | | | Bitte antworten an | | | "'rohit.sharma@iitbo| | | mbay.org'" | | | | |--------+------------------------------> >----------------------------------------------------------------------------| | | | An: Alexander Gehrig/RSD@RSD | | Kopie: | | Thema: Re: [suse-autoinstall] Antwort: [suse-autoinstall] NFS | | Install | >----------------------------------------------------------------------------| On Fri, 18 Oct 2002 Alexander.Gehrig(a)RSD.rohde-schwarz.com wrote: > I want to install my system via nfs booting from a floppy disk. If you have no problems with it, why not try to write boot.iso to a CD and use that? Longer life, no issues. Rohit -- (+91-22-692) 2101 D2, floor-3, Chand : SE : TLSI : 3578 SuSE 8.0 2.4-18-4GB on i686 : sendmail-8.9.3-42 : pine-4.44-121 rohit.sharma(a)iitbombay.org [maximus_two(a)yahoo.com] 9821394599(a)bplmobile.com ********************************************************* Disclaimer This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. ********************************************************* Visit us at http://www.mahindrabt.com

1 0

Antwort: RE: [suse-autoinstall] Antwort: [suse-autoinstall] NFS Install
by Alexander.Gehrig＠RSD.rohde-schwarz.com 18 Oct '02

18 Oct '02

Hi Thorsten That's true to do this with only one disk, but only on special hardware. I am building an autoinstallation for many system with other hardware. This kind of autoinstallation needs more modules than on one disk avaiable, so you need more disks. bye Alex |--------+--------------------------------> | | "Kugelberg, Thorsten" | | | <thorsten.kugelberg@re| | | altech.de> | | | | | | 18.10.2002 10:23 | | | | |--------+--------------------------------> >----------------------------------------------------------------------------| | | | An: Alexander Gehrig/RSD@RSD | | Kopie: | | Thema: RE: [suse-autoinstall] Antwort: [suse-autoinstall] NFS | | Install | >----------------------------------------------------------------------------| Hallo, this is also possible with just one bootdisk! I am doing that... To make that possible, you have to mount the bootdisk loopback, and extrakt the initrd from it, unzip the initrd, mount it as well and copy all the modules you need into it. If you are a little bit lucky, it fits!-) Otherwise you have to build a new one... In the end you have to do everything in reverse order! (zip the initrd, copy it into the bootdisk... regards thorsten

1 0

AutoYaST online documentation missing
by Kevin Ivory 18 Oct '02

18 Oct '02

The link from http://www.suse.de/~nashif/autoinstall/8.1/ to the HTML documentation http://www.suse.de/~nashif/autoinstall/8.1/autoyast-8.1/index.html is not found (Error 404) Kevin -- _ | Kevin Ivory | Tel: +49-551-3700000 |_ |\ | | Service Network GmbH | Fax: +49-551-3700009 ._|ER | \|ET | Bahnhofsallee 1b | mailto:Ivory@SerNet.de Service Network | 37081 Goettingen | http://www.SerNet.de/

2 1

RE: [suse-autoinstall] Antwort: [suse-autoinstall] NFS Install
by Kugelberg, Thorsten 18 Oct '02

18 Oct '02

Hello, this is also possible with just one bootdisk! I am doing that... To make that possible, you have to mount the bootdisk loopback, and extrakt the initrd from it, unzip the initrd, mount it as well and copy all the modules you need into it. If you are a little bit lucky, it fits!-) Otherwise you have to build a new one... In the end you have to do everything in reverse order! (zip the initrd, copy it into the bootdisk... regards thorsten -----Original Message----- From: Alexander.Gehrig(a)RSD.rohde-schwarz.com To: suse-autoinstall(a)suse.com Sent: 18.10.2002 10:02 Subject: [suse-autoinstall] Antwort: [suse-autoinstall] NFS Install hi Joachim, You can do this. Please read the greate manual from Anas Nashif for more informations. You need * 3 Disks ( Boot- / Module-Disks ). * A infofile ( on the last Module-Disk) or Lilo with Bootparameters * A NFS Server with * Installationdata * Profile bye Alexander |--------+-----------------------> | | Joachim.Tork@| | | gad.de | | | | | | 16.10.2002 | | | 14:08 | | | | |--------+-----------------------> >----------------------------------------------------------------------- -----| | | | An: suse-autoinstall(a)suse.com | | Kopie: (Blindkopie: Alexander Gehrig/RSD) | | Thema: [suse-autoinstall] NFS Install | >----------------------------------------------------------------------- -----| Hello, I want to install my system via nfs booting from a floppy disk. Is this possible, i mean is there a suitable initrd with everything needed in it, that fits on one disk together with the kernel. Best regards Joachim -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Antwort: [suse-autoinstall] NFS Install
by Alexander.Gehrig＠RSD.rohde-schwarz.com 18 Oct '02

18 Oct '02

hi Joachim, You can do this. Please read the greate manual from Anas Nashif for more informations. You need * 3 Disks ( Boot- / Module-Disks ). * A infofile ( on the last Module-Disk) or Lilo with Bootparameters * A NFS Server with * Installationdata * Profile bye Alexander |--------+-----------------------> | | Joachim.Tork@| | | gad.de | | | | | | 16.10.2002 | | | 14:08 | | | | |--------+-----------------------> >----------------------------------------------------------------------------| | | | An: suse-autoinstall(a)suse.com | | Kopie: (Blindkopie: Alexander Gehrig/RSD) | | Thema: [suse-autoinstall] NFS Install | >----------------------------------------------------------------------------| Hello, I want to install my system via nfs booting from a floppy disk. Is this possible, i mean is there a suitable initrd with everything needed in it, that fits on one disk together with the kernel. Best regards Joachim

1 0

NFS Install
by Joachim.Tork＠gad.de 16 Oct '02

16 Oct '02

Hello, I want to install my system via nfs booting from a floppy disk. Is this possible, i mean is there a suitable initrd with everything needed in it, that fits on one disk together with the kernel. Best regards Joachim

1 0

Swap partition with ftp install
by Robby Timmermans 16 Oct '02

16 Oct '02

Hello, I'm trying to instal SuSe 8.0 on a pentium75 with 40 Mb Ram. During the installation I get the message that a swap partition is needed and that I should give the location. Now the question(s): How can I create a swap partition so I can use it during the ftp installation ? And/or do I need to modify the installation disks ? All help is appreciated. Thanks and best regards, Robby Timmermans

2 1

profile not found (suse 8.1)
by Sven Crimmann 15 Oct '02

15 Oct '02

Hallo, I have createt a clone.xml with yast2 and renamed it to autoinst.xml. I put it on a floppy an done a reboot. Then I got the Message: profile for this maschine could not be found or retrieved. Did I forget something? Best, Sven -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup

1 0

AW: [suse-autoinstall] Problem with network interfaces (solved)
by Prengel, Ralf 11 Oct '02

11 Oct '02

Sorry, my mistake. The modulename is 3c and not 3C. i.A. Ralf Prengel Customer Services Comline AG Dortmund/Germany Fon +49 231 97575-157 Fax +49 231 97575-257 EMail ralf.prengel(a)comline.de für Supportanfragen EMail support(a)comline.de Fon +49 231 97575-904 Fax +49 231 97575-905 > -----Ursprüngliche Nachricht----- > Von: Prengel, Ralf [mailto:ralf.prengel@comline.de] > Gesendet: Freitag, 11. Oktober 2002 12:31 > An: suse-autoinstall(a)suse.com > Betreff: [suse-autoinstall] Problem with network interfaces > > > Normally I m using the eepro100 module for Intel-Nics and > everythings works. No I ve to use some 3Com card (module > 3C90x). Everythis works fine and the network works (ping etc. > ) without changing the xml file. The problem: After the first > reboot the network isn't reachable any longer allthough the > 3Com card is configured. > Solution: > Deleting eth0 and installing it again > Editing my xml-configuration-file doesn t help. > I changed the entry eepro100 into 3C90x. > > Hints? > > > i.A. > Ralf Prengel > Customer Services > Comline AG > Dortmund/Germany > Fon +49 231 97575-157 > Fax +49 231 97575-257 > EMail ralf.prengel(a)comline.de > > für Supportanfragen > EMail support(a)comline.de > Fon +49 231 97575-904 > Fax +49 231 97575-905 > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

1 0

Problem with network interfaces
by Prengel, Ralf 11 Oct '02

11 Oct '02

Normally I m using the eepro100 module for Intel-Nics and everythings works. No I ve to use some 3Com card (module 3C90x). Everythis works fine and the network works (ping etc. ) without changing the xml file. The problem: After the first reboot the network isn't reachable any longer allthough the 3Com card is configured. Solution: Deleting eth0 and installing it again Editing my xml-configuration-file doesn t help. I changed the entry eepro100 into 3C90x. Hints? i.A. Ralf Prengel Customer Services Comline AG Dortmund/Germany Fon +49 231 97575-157 Fax +49 231 97575-257 EMail ralf.prengel(a)comline.de für Supportanfragen EMail support(a)comline.de Fon +49 231 97575-904 Fax +49 231 97575-905

1 0

Solution post-script problem
by Johan De Wit 11 Oct '02

11 Oct '02

Hi all, The <post-script> section shoul reside in the <configure> subsection. The XML file is devided in a <install> and <configure> section. Parsing the xml file during installation gives no error if the <post-scripts> is included in the <install> section, but nothing will happen. If it is included in the <configure>, you will find something in the /var/adm/autoinstall dirs. Greetings Jo

1 0

earlier hda now hde
by Reimar Bauer 09 Oct '02

09 Oct '02

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I believe this is simple but I am to new to the auto installation so may be you can give me a tip. We have a few systems now with suse7.2 which we like to install with 8.x. In the old 7.2 the onboard raid controller was different from a standard ide controller. In 7.2 the harddisk is hda in 8.0 it is hde. If I set parameters for partionong sizes did I have to say where it should be e.g. hde? or is it possible to say I like to have the first harddisk the system found. I would prefer the last one this is more flexible. I don't found how to set it. Any ideas? best regards Reimar - -- Reimar Bauer Institut fuer Stratosphaerische Chemie (ICG-I) Forschungszentrum Juelich email: R.Bauer(a)fz-juelich.de - ------------------------------------------------------------------- ~ a IDL library at ForschungsZentrum Juelich ~ http://www.fz-juelich.de/icg/icg-i/idl_icglib/idl_lib_intro.html =================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE9pEYW5aOc3Q9hk/kRAs5lAKDAI2QkpBWRa9BfO0EsgCstqL06ZwCgu6s0 dePvQG3jbauuKuDmrLsOn40= =6c2+ -----END PGP SIGNATURE-----

3 2

RE: [suse-autoinstall] post-script problem
by Kugelberg, Thorsten 09 Oct '02

09 Oct '02

Hallo, have a look into the directory '/var/adm/autoinstall'! It should contain three subdirs. One is log, an other is scripts. If the file postinstall.sh exists inside the scrits directory, the part <post-scrips> is interpreted. Afterwards have a look at the logfiles, to find out what is wrong. Regards Thorsten -----Original Message----- From: Jeff Martin To: suse-autoinstall(a)suse.com Sent: 09.10.2002 15:16 Subject: [suse-autoinstall] post-script problem Anas, I've been using autoinstall with PXE to install SuSE 8.0 on machines in our test lab for a month or so. Everything was working great. Recently someone asked me to add another open-source package to the install (STAF, a test framework) and I thought the <post-scripts> tag would be a good place to do it. So I've been trying to test <post-scripts> by adding the following stanza to my xml script. .... <post-scripts config:type="list" > <script> <filename>postinstall.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh touch /tmp/test.txt ]]> </source> </script> </post-scripts> .... Nothing happens. The file isn't created and I haven't found anything in the logs to show a failure. Any ideas on what I'm doing wrong? Thanks in advance, Jeff Martin http://www-124.ibm.com/developerworks/oss/linux/ http://ltp.sf.net -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

post-script problem
by Jeff Martin 09 Oct '02

09 Oct '02

Anas, I've been using autoinstall with PXE to install SuSE 8.0 on machines in our test lab for a month or so. Everything was working great. Recently someone asked me to add another open-source package to the install (STAF, a test framework) and I thought the <post-scripts> tag would be a good place to do it. So I've been trying to test <post-scripts> by adding the following stanza to my xml script. .... <post-scripts config:type="list" > <script> <filename>postinstall.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/sh touch /tmp/test.txt ]]> </source> </script> </post-scripts> .... Nothing happens. The file isn't created and I haven't found anything in the logs to show a failure. Any ideas on what I'm doing wrong? Thanks in advance, Jeff Martin http://www-124.ibm.com/developerworks/oss/linux/ http://ltp.sf.net

1 0

PCMCIA
by Andreas Bank 04 Oct '02

04 Oct '02

Hi @ all. Yesterday i tryed to install SUSE 7.3 on my Laptop. But wenn the PCMCIA slots where scanned, my screen showed ...done and then : No reaktion any more!!!! (My PCMCIA slots are empty!!!!!) You cann help me?? Thx Andi

2 1

hda6 instead of hda1
by Prengel, Ralf 04 Oct '02

04 Oct '02

Allthough I configured AutoYast2 to use the hole disk the follwing is the result: hda 6 /boot hda 7 / instead of hda 1 /boot hda 3 / The system was a windows 2000 machine before. Ralf Prengel

2 1

Lilo doesn't get written in MBR
by Miguel Gómez 04 Oct '02

04 Oct '02

Hi, I'm trying to auto-install SuSE 8.0 keeping an existing Windows partition. The problem is that lilo doesn´t get written in the MBR although I specify the following configuration in the profile: <bootloader> <write_bootloader>true</write_bootloader> <lba_support config:type="boolean" >true</lba_support> <activate config:type="boolean" >true</activate> <linear config:type="boolean" >false</linear> <location>mbr</location> <parameters></parameters> </bootloader> I get an error saying that lilo couldn't be written in the MBR. Is there anything wrong in my profile's bootloader configuration? My second problem is that, although I set the "linear" tag to false, it gets written in the lilo.conf file. This causes an error when I run lilo because the "lba32" and "linear" tags are incompatible in the same lilo.conf file. Can anyone help, please? Regards, Miguel Gómez Rodríguez gomez(a)dit.upm.es

1 0

Booting from a floppy
by Jens Rathmann 03 Oct '02

03 Oct '02

Hi I just try this latest Autoyast, wondering why the docs say it's recommended not to use a simple boot disk to initiate the install. Seems there've to be some (large) packages on the initial boot media!? Could anyone explain why? I don't want to use a CD or another bigsize media to initiate. All the installation data should be available via nfs or ftp, so why is it needed (from the docs: "... is limited due to the size of the data a floppy can hold"). If it's really not possible how do I use Autoyast without any CD or PXE available at the client machines? Thanks in advance, Jens

2 1

AW: [suse-autoinstall] AutoYast Suse 8.1 Problems (solved)
by Prengel, Ralf 02 Oct '02

02 Oct '02

Sorry, I had an old webpage in my cache. It works after installing the new rpm-package . i.A. Ralf Prengel Customer Services Comline AG Dortmund/Germany Fon +49 231 97575-157 Fax +49 231 97575-257 EMail ralf.prengel(a)comline.de für Supportanfragen EMail support(a)comline.de Fon +49 231 97575-904 Fax +49 231 97575-905 > -----Ursprüngliche Nachricht----- > Von: Prengel, Ralf [mailto:ralf.prengel@comline.de] > Gesendet: Mittwoch, 2. Oktober 2002 12:40 > An: 'Anas Nashif' > Cc: suse-autoinstall(a)suse.com > Betreff: [suse-autoinstall] AutoYast Suse 8.1 Problems > > > Hallo, > > I ve problems using AutoYast Suse 8.1. > 1) > There is no longer an option to select series of software in Yast2 > 2) > Installing an new normal Minimal.system failes because the > bootmanger is installed but no kernel is installed on /boot > > > Hints? > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

1 0

AutoYast Suse 8.1 Problems
by Prengel, Ralf 02 Oct '02

02 Oct '02

Hallo, I ve problems using AutoYast Suse 8.1. 1) There is no longer an option to select series of software in Yast2 2) Installing an new normal Minimal.system failes because the bootmanger is installed but no kernel is installed on /boot Hints?

1 0