June 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

cannot use keyboard other than language
by Michal Kubecek 06 Oct '03

06 Oct '03

I have a problem with automatic installation of SuSE Linux 8.1 and 8.2. I need to select czech language but english (US) keyboard map. Generated XML file contains <keyboard> <keymap>english-us</keymap> </keyboard> <language>cs_CZ</language> but the system is installed with czech keyboard map anyway. Is there a way to use czech language but english-US keyboard map? Michal Kubecek

4 6

reread partitions
by Lars Stavholm 02 Jul '03

02 Jul '03

Hi all, does anyone know of a way to make autoyast reread the partition table(s) after (or at the end of) a pre-script execution? I'm trying to remove the current partitions, if any, using "parted", which succeeds. However, I'm guessing that autoyast already has a pretty good idea of the current partition plan based on a partition table(s) read prior to my usage of "parted"? R/Lars S

2 4

Does anyone know of a command line XML merge?
by Lars Stavholm 01 Jul '03

01 Jul '03

Does anyone know of a command line XML merge? Something simple like "xmlmerge file1.xml file2.xml ..." I know of the Classes feature in autoyast2, and Anas wrote in some previous posting about Offline usage of the Classes feature. However, the posting does not mention how to accomplish this. R -- Lars.Stavholm(a)telcotec.se

2 1

Autoinstallation Process under suse8.2
by Axel Schmidat 01 Jul '03

01 Jul '03

hi@all, I would like to install a lot of clients with suse8.2 automatical and I use the autoyast. My configuration is summarized in a window when I´m starting the process, but I will deactivate this for a full automatic installation. Who can help me? Thx a lot Axel

2 1

two problems with autoinstall (scripts and grub)
by Frank Schuette 01 Jul '03

01 Jul '03

Hallo, I use SuSE 8.2 for autoinstallation with the upgrade by Anas installed. 1. The installed client is configured to use grub with the gfxmenu option. This is definitely in the xml file, but in the installation the file message is missing and so is the gfxmenu line in the menu.lst file. 2. My post installation scripts do contain a lot of empty lines. This is no problem, the scripts are executed correctly. I do make use of classes, and the xml file is merged from 5 different class files. I can send the class files and the merged file, if necessary. Does anyone experience similar problems or have any hints for me. Bye -- Frank Schütte Gymnasium Himmelsthür fschuett(a)gymnasium-himmelsthuer.de

2 1

is an autoinstall repository built with links possible?
by Richard Bos 01 Jul '03

01 Jul '03

The following situation: Copied the cd's to harddisk. An install of this repository is succesfull. In this case the mounted directory is: /ftp/distrib/suse82/base On the same machine suse's updates are being mirrored into: /ftp/distrib/suse82/updates >From the 2 directories (base and updates) I've created a "latest" repository, using relative links. Path to that directory is: /ftp/distrib/suse82/latest. However, during installation the directory /ftp/distrib/suse82/latest is mounted and for this reason the links made in that directory are going nowhere. The directories updates and base are not visible. A solution is to copy all the files. But is it possible to have suse mount /ftp/distrib/suse82/ but to use the path /ftp/distrib/suse82/latest?? Looking forward to suggestion. -- Richard Bos Without a home the journey is endless

2 1

Re-inventing the Wheel
by Robison, Jonathon (M.) 01 Jul '03

01 Jul '03

I recognize that this problem has probably been tackled before, but I also recognize that there's probably a one line answer, too. I have duplicated all the SuSE 8.2 CD's to an apache server and made them available via http. What I want to end up with is a Floppy disk I can give out that people can boot to install SuSE. They need to be able to do all configuration as they normally would, EXCEPT that I want it to use MY list of rpm packages to install. I can make an .sel file and place it with the others in the http server (I think) but what I need is a boot floppy that will let folks configure for their hardware, including partitioning, etc. but enforce my package list on their install. In RH, I would just make a normal boot floppy, create/modify the ks.cfg, and the ks.cfg would list the packages but not much else, forcing the system to ask about anything not listed. It seems a little less straight-forward in SuSE. Pointers on how to, or url's with existing HOWTO docs would be greatly appreciated! Jonathon M. Robison Linux Integration Analyst Strategic Infrastructure Engineering 313-323-9529

2 1

RE: [suse-autoinstall] rules
by Robert Alonso 01 Jul '03

01 Jul '03

OK, after running YOU, I found that the updated autoyast2-installation package indeed has the rules.dtd file. But looking over the file led me to a new question: what is <operator>? From looking through /usr/share/YaST2/modules/AutoInstallRules.ycp, I found it can either take "and" or "or". This leads me to think that the prerequisites for a <result> can be conditional. I haven't seen this documented anywhere there. Anas, is this functional? If so, how does one use it? Thanks, Robert > -----Original Message----- > From: Robert Alonso > Sent: Friday, June 27, 2003 10:48 AM > To: 'suse-autoinstall(a)suse.com' > Subject: [suse-autoinstall] rules > > > Is there a DTD for the rules file? The examples reference > "/usr/share/autoinstall/dtd/rules.dtd" but that file does not exist. > Also, I doubt it but is there any functionality for if-then-else? > <continue> isn't powerful enough for what I'd like to do. > > Thanks, > Robert > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

2 1

SuSE 8.2 Prof installation of devs-2003.3.14-1 : rm: command not found
by Fred Mobach 01 Jul '03

01 Jul '03

Hello List, While my configuration of autoyast in SuSE Linux 8.1 works perfectly an annoying RAID controller in a Dell server forced me to upgrade to 8.2. Normal installation from the SuSE CD's works like a charm. However, autoyast (adapted to the 8.2 rpm's like coreutils) returns errormessages during installation : - SuSE 8.2 Professional via autoyast - installation of devs-2003.3.14-1 - Error messages : - var/tmp/rpm-tmp.<PID>: line <n>: rm: command not found (line = 5 and 8) I checked (on tty2) and indeed most programs in /mnt/bin and /mnt/usr/bin are failing. I think the interesting part of the autoinstall.xml is : <software> <addons config:type="list"/> <base>Minimal</base> <packages config:type="list"> <package>SuSEfirewall2</package> <package>aaa_base</package> <package>aaa_skel</package> <package>acl</package> <package>acpid</package> <package>alsa</package> <package>apt</package> <package>apt-devel</package> <package>ash</package> <package>at</package> <package>attr</package> <package>autoyast2-installation</package> <package>bash</package> <package>bc</package> <package>bind9-utils</package> <package>bindutil</package> <package>bootsplash</package> <package>bootsplash-theme-SuSE</package> <package>bzip2</package> <package>compat</package> <package>coreutils</package> Remarks : - xmllint does not signal errors - the collection of packages includes all rpm's contained in the minimal installtion + some additional packages No need to tell you that after failure of devs installation the resulting system is not in working condition. ;-) If you find it useful I can put the autoinstall.xml (404 lines) on the web. -- Fred Mobach - fred(a)mobach.nl - postmaster(a)mobach.nl Systemhouse Mobach bv - The Netherlands - since 1976 website : http://fred.mobach.nl There's nothing remarkable about it. All one has to do is hit the right keys at the right time and the instrument plays itself. - J.S. Bach

3 4

RE: [suse-autoinstall] Does anyone have a working xml setup using lvm and raid-1?
by Voss Stefan 30 Jun '03

30 Jun '03

Hi, I think someone on this list had already pointed out why my suggestion (dd ... of=/dev/hda ...) does not work: The lvm and raid data are not stored in the mbr of the disks but at the beginning of partitions /dev/hda2 and /dev/hdc2. You could try dd if=/dev/zero of=/dev/hda2 bs=512 count=2 dd if=/dev/zero of=/dev/hdc2 bs=512 count=2 or raidstop /dev/md0 in a pre-script to get rid of existing raid data. Regards, Stefan Voss -----Original Message----- From: Lars Stavholm To: Voss Stefan Cc: suse-autoinstall(a)suse.com Sent: 6/29/2003 1:11 PM Subject: Re: [suse-autoinstall] Does anyone have a working xml setup using lvm and raid-1? Stefan, many thanks! My inst setup now works with both raid and lvm. However, nothing's perfect, so I have one problem left now and I'm wondering if you might have the answer to this one: I adapted a script published a while back on this list to remove any previous logical volumes. That script is executed as a "pre-script" and works just fine for repeated installations on a system. As I've now added the raid portion, I get the following error message when I try to install on a system that already has a raid setup: "Cannot create the RAID /dev/md0". I have a fieling that the problem is similar to the one with the logical volumes. I also tried a pre-script containing the following two commands (suggested by yourself in an earlier posting) without any success: dd if=/dev/zero of=/dev/hda bs=512 count=2 # primary master dd if=/dev/zero of=/dev/hdc bs=512 count=2 # secondary master If I remove the partitions (using e.g. DOS fdisk) prior to the installation, the subsequent automated installation works just fine. Hints, anyone: how to remove the raid setup in a pre-script? R/Lars S Voss Stefan wrote: > Hi, > > we use the standard autoyast2-installation-2.7.18-1 package from > SuSE Prof 8.2 for the installations. The xml file was originally > created with autoyast2-2.7.19-0 but only the partition information. > The raid and lvm info was added manually. > > Regards, > Stefan Voss > > > -----Original Message----- > From: Lars Stavholm > To: suse-autoinstall(a)suse.com > Sent: 6/25/2003 7:48 PM > Subject: RE: [suse-autoinstall] Does anyone have a working xml setup using > lvm and raid-1? > > Might I ask what version of autoyast2 you're using? > R/Lars > > On Wed, 25 Jun 2003, Voss Stefan wrote: > >>Hi, >> >>yes, the following works for me. We have two discs hda and hdb. >>On each disc two partitions are created. A small linux partition >>(50 MB, /dev/hda1 resp. /dev/hdb1) and a big raid partition (/dev/hda2 >>resp. /dev/hdb2). /dev/hda2 and /dev/hdb2 are both added to the raid1 >>device /dev/md0. /dev/md0 is then taken as physical volume into volume >>group systemvg. The logical volumes containing the file systems > > (including > >>/ and swap) are created from this volume group. >> >>The small partitions /dev/hda1 and /dev/hdb2 have the file systems > > /boot > >>resp. >>/boot_backup. >> >>[...] > > > -- Lars.Stavholm(a)telcotec.se Telcotec AB phone: +46 (0)31 7020640 Lerumsv. 29 mobile: +46 (0)705 606498 424 90 Olofstorp fax: +46 (0)31 7020617 Sweden

2 1

RE: [suse-autoinstall] Does anyone have a working xml setup using lvm and raid-1?
by Voss Stefan 29 Jun '03

29 Jun '03

Hi, we use the standard autoyast2-installation-2.7.18-1 package from SuSE Prof 8.2 for the installations. The xml file was originally created with autoyast2-2.7.19-0 but only the partition information. The raid and lvm info was added manually. Regards, Stefan Voss -----Original Message----- From: Lars Stavholm To: suse-autoinstall(a)suse.com Sent: 6/25/2003 7:48 PM Subject: RE: [suse-autoinstall] Does anyone have a working xml setup using lvm and raid-1? Might I ask what version of autoyast2 you're using? R/Lars On Wed, 25 Jun 2003, Voss Stefan wrote: > > Hi, > > yes, the following works for me. We have two discs hda and hdb. > On each disc two partitions are created. A small linux partition > (50 MB, /dev/hda1 resp. /dev/hdb1) and a big raid partition (/dev/hda2 > resp. /dev/hdb2). /dev/hda2 and /dev/hdb2 are both added to the raid1 > device /dev/md0. /dev/md0 is then taken as physical volume into volume > group systemvg. The logical volumes containing the file systems (including > / and swap) are created from this volume group. > > The small partitions /dev/hda1 and /dev/hdb2 have the file systems /boot > resp. > /boot_backup. > > [...]

2 1

glibc version i586 and i686 conflict
by sytse 28 Jun '03

28 Jun '03

Hi, I'm making a cd with autoyast, using the 'create iso' option. This works fine on the same kind of system (which is a mini-itx board with a via c3 cpu) If I take the cd to other systems, the installation fails because the i686 glibc version is not included on the cd (the i586 version however is on the cd). So I have a couple of questions: - Is it possible to include both glibc versions on the install cd? - Is there a way around this? - What is the logic that determines if the i686 or i586 version is installed? Can this same problem occur for other packages? (I think not, because glibc seems to be the only package in the i686 directory, but I'd like to hear this from an expert too...) Thanks, Sytse

1 1

rules
by Robert Alonso 27 Jun '03

27 Jun '03

Is there a DTD for the rules file? The examples reference "/usr/share/autoinstall/dtd/rules.dtd" but that file does not exist. Also, I doubt it but is there any functionality for if-then-else? <continue> isn't powerful enough for what I'd like to do. Thanks, Robert

1 0

RE: [suse-autoinstall] Does anyone have a working xml setup using lvm and raid-1?
by Voss Stefan 25 Jun '03

25 Jun '03

Hi, yes, the following works for me. We have two discs hda and hdb. On each disc two partitions are created. A small linux partition (50 MB, /dev/hda1 resp. /dev/hdb1) and a big raid partition (/dev/hda2 resp. /dev/hdb2). /dev/hda2 and /dev/hdb2 are both added to the raid1 device /dev/md0. /dev/md0 is then taken as physical volume into volume group systemvg. The logical volumes containing the file systems (including / and swap) are created from this volume group. The small partitions /dev/hda1 and /dev/hdb2 have the file systems /boot resp. /boot_backup. ... <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>50MB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <raid_name>/dev/md0</raid_name> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdb</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/boot_backup</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>50MB</size> </partition> <partition> <crypt_fs config:type="boolean">false</crypt_fs> <crypt_key></crypt_key> <format config:type="boolean">false</format> <raid_name>/dev/md0</raid_name> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <raid config:type="list"> <raid_device> <device_name>/dev/md0</device_name> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock config:type="boolean">true</persistent_superblock> <raid_type>raid1</raid_type> <chunk_size>32</chunk_size> <lvm_group>systemvg</lvm_group> <mount /> <format config:type="boolean">false</format> </raid_device> </raid> <lvm config:type="list"> <lvm_group> <lvm_name>systemvg</lvm_name> <pesize>4M</pesize> <logical_volumes config:type="list"> <lv> <lv_name>lvroot</lv_name> <lv_size>1000mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/</lv_mount> </lv> <lv> <lv_name>lvswap</lv_name> <lv_size>2000mb</lv_size> <lv_mount>swap</lv_mount> </lv> <lv> <lv_name>lvusr</lv_name> <lv_size>3000mb</lv_size> <lv_fs>reiser</lv_fs> <lv_mount>/usr</lv_mount> </lv> </logical_volumes> </lvm_group> </lvm> ... Regards, Stefan -----Original Message----- From: Lars Stavholm To: suse-autoinstall(a)suse.com Sent: 6/24/2003 9:10 PM Subject: [suse-autoinstall] Does anyone have a working xml setup using lvm and raid-1? Does anyone have a working xml file (for SuSE 8.2) using lvm and raid-1? -- Lars.Stavholm(a)telcotec.se -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Does anyone have a working xml setup using lvm and raid-1?
by Lars Stavholm 24 Jun '03

24 Jun '03

Does anyone have a working xml file (for SuSE 8.2) using lvm and raid-1? -- Lars.Stavholm(a)telcotec.se

1 0

Problem with autoyast and NIS / NFS Client Installation
by Hartmut Hering 24 Jun '03

24 Jun '03

I have a problem installing a client with autoyast2 as a NIS and NFS Client. After Installation all seems to work fine. All User/Accounts are there (so it looks like NIS works) but I can't login as a user. After trying to log in I get the message: "No write Access to $HOME directory (/). That looks like a configuration-error in the NFS-Client. But I think that my configuration/File is OK. After that error I logged in as "root" and obened the Yast2-Control-Center. There I clicked Network Devices / NFS-Client and at once on the Finish-Button. Then I got the Message: "The entered Values will be written now. Do you really want to use the new settings?" (strange! what new settings? There were made no new settings. I opened the NFS-Client Configuration and closed it without doing anything...). After clicking "Yes" I was able to login as another User. What can I do, to make it work DIRECTLY after the automatic Installation? Here is the NIS/NFS Part of my XML-Script. Maybe I did something wrong... <nfs config:type="list"> <nfs_entry> <mount_point>/home</mount_point> <nfs_options>defaults</nfs_options> <server_path>faui49:/home</server_path> </nfs_entry> <nfs_entry> <mount_point>/proj/i4embedded</mount_point> <nfs_options>defaults</nfs_options> <server_path>faui49:/proj/i4embedded</server_path> </nfs_entry> <nfs_entry> <mount_point>/tftpboot</mount_point> <nfs_options>defaults</nfs_options> <server_path>faui49:/tftpboot</server_path> </nfs_entry> </nfs> <nis> <nis_broadcast config:type="boolean">false</nis_broadcast> <nis_broken_server config:type="boolean">false</nis_broken_server> <nis_by_dhcp config:type="boolean">false</nis_by_dhcp> <nis_domain>private.informatik.uni-erlangen.de</nis_domain> <nis_local_only config:type="boolean">false</nis_local_only> <nis_options></nis_options> <nis_other_domains config:type="list"/> <nis_servers config:type="list"> <nis_server>192.168.34.2</nis_server> </nis_servers> <start_autofs config:type="boolean">true</start_autofs> <start_nis config:type="boolean">true</start_nis> </nis> Hartmut Hering Friedrich Alexander Universitaet Erlangen

1 0

RE: [suse-autoinstall] post-install script question
by Hirayama, Pat 21 Jun '03

21 Jun '03

Thanks. I could do that, but, say, I have the same configuration file setup for 10 different XML files. And I want to make a change. I have to remember to duplicate that change in each of the XML files. It'd be much easier if I make the change to one file, and let the script copy it for me. That's why I'm trying to get this to work -- I had it working perfectly using <files> before.... -p -----Original Message----- From: Volkmar Glauche [mailto:glauche@uke.uni-hamburg.de] Sent: Tuesday, June 17, 2003 11:43 PM To: Hirayama, Pat Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] post-install script question On Tue, 17 Jun 2003, Hirayama, Pat wrote: > Greetings, > > So, I've been trying to have autoyast use a post install shell script to > mount an NFS share and copy various configuration files onto the newly setup > server. (SuSE Linux Professional 8.2) > > Thanks to Anas' help, I've gotten to the point that the script is copied > over and is executed ... but it doesn't work. > > The script looks something like this: > > #! /bin/sh > mount -a > cp /mnt/suse/autoyast/files/common/syslog.conf /etc/syslog.conf > cp /mnt/suse/autoyast/files/common/motd /etc/motd > ... > I don't know why your script may fail. But if you just want to get your own configuration files in place there is (at least with 8.1) the <files> section where you can place file contents as CDATA in you autoyast config file like this ... <configure> <files config:type="list"> <file> <file_contents> <![CDATA[ #here goes your file contents ]]> </file_contents> <file_path>/my_path/my_name</file_path> </file> ... </files> ... Volkmar -- Volkmar Glauche Department of Neurology E-Mail glauche(a)uke.uni-hamburg.de UKE Hamburg Phone 49(0)40-42803-5781 Martinistr. 52 Fax 49(0)40-42803-9955 20246 Hamburg

3 2

Autoinstall diskless client configurations?
by Ross Parker 18 Jun '03

18 Jun '03

Hi, I'd like to be able to set up a master system with multiple copies of SuSE for diskless clients. Most of the clients will have identical hardware, some may be different. Is it possible to use autoyast to manage the creation/configuration of the diskless clients file systems? This needs to be done in advance - i.e. I need to set up the client directory structures before the clients are booted. Thanks! Ross -- Ross Parker OctigaBay Systems Corp. phone: 604-484-2265 fax: 604-484-2221 cell: 604-817-3500

1 0

where to put the <init><info_file> tags?
by Richard Bos 18 Jun '03

18 Jun '03

Hello, According to the documentation file: file:/usr/share/doc/packages/autoyast2/x1144.html It should be possible to include linuxrc information in the autoinst.xml file, with the <init><info_file> tags (from the docu): .... <install> .... <init> <info_file> <![CDATA[ # # Don't remove the following line: # start_linuxrc_conf # According to the dtd the following tags may be included in the <install> tag: profile.dtd:<!ELEMENT install ( bootloader?, general?, lvm?, partitioning?, raid?, report?, software? )> The <init> tag is not part of that. A grep of "init" in the dtd's does not reveal an "init" tag either. Does this mean that this <init><info_file> combo is not supported (anymore), or should the errors reported by xmllint be ignored? (the info_file tag seems missing to of the dtd). I think that I may need this concept to specify the nfs server ip address, netmask, etc or should this be done using a different config mechanism? -- Richard Bos Without a home the journey is endless

1 0

Command line variables
by Steve Schneider 18 Jun '03

18 Jun '03

What about a new command line variables autoyast=cdrom:/<path> ? It seems, that autoyast suse 8.2 isnt recognising, that it was booting from an self-made cdrom. it doesnt looks for the config file specified with autoyast=file:/<path> on the booted cdrom. only autoyast=device://<device>/<file> is another solution, but how can we set the bootcdrom <device> automaticaly on the fly? -- MFG Steve Schneider

1 0

Cloned machine
by Robison, Jonathon (M.) 18 Jun '03

18 Jun '03

In order to make a Bill of Materials for the many folks in my office who want to try SuSE 8.2, I made an xml file using the "Clone this machine" feature. Unfortunately, many folks want to duel boot, or have different boot and partition requirements. Can I just remove the boot section (the one that defines grub and it's settings) and the <partitions> sections, and add the <confirm>? I'd really like for the system to ask them everything except the package listing, if possible. Can anyone suggest an easy way to go from my cloned autoinst.xml to that desired end state? Jonathon M. Robison

2 1

Socket Errors
by Robison, Jonathon (M.) 18 Jun '03

18 Jun '03

Anyone have any idea why the Online Update would be telling me "Socket Error: 110" when trying to get the list of mirrors from www.suse.de/cgi-bin/suseservers.cgi ? Jonathon M. Robison Linux Integration Analyst Strategic Infrastructure Engineering 313-323-9529

1 0

RE: [suse-autoinstall] post-install script question
by Hirayama, Pat 18 Jun '03

18 Jun '03

They appear to be in good shape. I can login afterwards. -p -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tuesday, June 17, 2003 11:46 PM To: Hirayama, Pat Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] post-install script question Hi, Thats really strange. Are the files /etc/passwd and /etc/shadow in good shape after installation? I will try to reproduce that. Anas Hirayama, Pat wrote: > Greetings, > > So, I've been trying to have autoyast use a post install shell script to > mount an NFS share and copy various configuration files onto the newly setup > server. (SuSE Linux Professional 8.2) > > Thanks to Anas' help, I've gotten to the point that the script is copied > over and is executed ... but it doesn't work. > > The script looks something like this: > > #! /bin/sh > mount -a > cp /mnt/suse/autoyast/files/common/syslog.conf /etc/syslog.conf > cp /mnt/suse/autoyast/files/common/motd /etc/motd > ... > > So, when 'mount -a' runs, I get the error message: mount: only root can do > that > > Anas Nashif has told me that post install scripts run as root. And, I've > added a whoami command into this shell script, and it confirms that the > process is running as root. > > When the server is up afterwards, I can run the script just fine. Of > course, I'd prefer not to have to do that. :-) > > Any suggestions would be appreciated. > > Thanks! > -p > > > Pat Hirayama > IT / Server Operations > Fred Hutchinson Cancer Research Center > phirayam(a)fhcrc.org > > >

1 0

NIS configuration in control file
by Fermín Galán 18 Jun '03

18 Jun '03

Hello everyone, I'm trying to configure NIS client in autoinstallations usign the fragment shown at documentation (in using SuSE 8.1) in my control file: <nis> <nis_broadcast config:type="boolean">true</nis_broadcast> <nis_broken_server config:type="boolean">true</nis_broken_server> <nis_domain>test</nis_domain> <nis_local_only config:type="boolean">true</nis_local_only> <nis_servers config:type="list"> <nis_server>nisserver</nis_server> </nis_servers> <start_autofs config:type="boolean">true</start_autofs> <start_nis config:type="boolean">true</start_nis> </nis> I would like to know what is the exact effect (i.e, how modifies the NIS-related files under /etc) of the tags: - nis_broadcast - nis_broken_server - nis_local_only - start_autofs - start_nis Additionally, any pointer to SuSE 8.1 specific NIS client-server configuration (appart the generic Linux NIS HOWTO) is welcome. Thanks in advance! ------- Fermín

2 1

post-install script question
by Hirayama, Pat 18 Jun '03

18 Jun '03

Greetings, So, I've been trying to have autoyast use a post install shell script to mount an NFS share and copy various configuration files onto the newly setup server. (SuSE Linux Professional 8.2) Thanks to Anas' help, I've gotten to the point that the script is copied over and is executed ... but it doesn't work. The script looks something like this: #! /bin/sh mount -a cp /mnt/suse/autoyast/files/common/syslog.conf /etc/syslog.conf cp /mnt/suse/autoyast/files/common/motd /etc/motd ... So, when 'mount -a' runs, I get the error message: mount: only root can do that Anas Nashif has told me that post install scripts run as root. And, I've added a whoami command into this shell script, and it confirms that the process is running as root. When the server is up afterwards, I can run the script just fine. Of course, I'd prefer not to have to do that. :-) Any suggestions would be appreciated. Thanks! -p Pat Hirayama IT / Server Operations Fred Hutchinson Cancer Research Center phirayam(a)fhcrc.org

3 2

FW: Help required in creating custom selection package
by Pramodh G N 17 Jun '03

17 Jun '03

Hi all, I had posted this query few days back, but didn't get any help. Can anybody please point out what I am missing here? ================================================================================ I am trying to build a customized SUSE distribution with a set of rpm's which is different from the default SLES distribution. I have gone through the documentation but it doesn't clearly say how to create a *.sel file without using any of the .sel files provided by the SLES CD. My requirement is to create a distribution depending on the customers requirement and generate a my.sel file, using which a distribution will be created. can somebody point out the steps to be followed for accomplishing this task. ================================================================================ Thanks in Advance Pramodh **************************Disclaimer************************************ Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. ***************************************************************************

1 0

Using classes under SuSE 8.2
by Thomas Necker 17 Jun '03

17 Jun '03

Sorry, but I just can't figure out how classes are supposed to work under SuSE 8.2. When I use the AutoYast module to add a class to the current configuration, it just says: "This class doesn't contain profiles" Shouldn't I be able here to select a XML file previously put in /var/lib/autoinstall/classes that can then be merged to the final XML file? Thanks for your help. Bye, Thomas

3 2

AutoYaST and scripts question
by Hirayama, Pat 16 Jun '03

16 Jun '03

Greetings, If I want to copy some files from another server as part of a post installation script to be executed by autoyast, do I need to verify that networking is working at the beginning of the script, or can I assume that I can just NFS mount the directory in question and copy the subsequent files over? Thanks, -p Pat Hirayama IT / Server Operations Fred Hutchinson Cancer Research Center phirayam(a)fhcrc.org

1 0

.xml config on cdrom failed
by Steve Schneider 16 Jun '03

16 Jun '03

i created my own boot cdrom with an .xml config file in /. i told autoyast via grub where to retrieve the config file. but autoyast is prompting for the location of the config file! setting manual parameter in the dialogbox dont work. its suse 8.2 Any help? -- MFG Steve Schneider

1 0

autoyast vnc
by Martin Schmiderer 16 Jun '03

16 Jun '03

Hi *, how can i enable vnc in my xml configurationfile??? I now to do that in the way of install (in debug-mode) but i want to do it with autoyast from my xml-file. Thanx for help, regards Martin -- ________________________________creating IT solutions Martin Schmiderer science + computing ag IT-Services Hagellocher Weg 71-75 phone +49 7071 9457 225 72070 Tuebingen, Germany fax +49 7071 9457 211 www.science-computing.de

1 1

Help required in creating custom selection package
by Pramodh G N 16 Jun '03

16 Jun '03

Hi all, I am trying to build a customized SUSE distribution with a set of rpm's which is different from the default SLES distribution. I have gone through the documentation but it doesn't clearly say how to create a *.sel file without using any of the .sel files provided by the SLES CD. My requirement is to create a distribution depending on the customers requirement and generate a my.sel file, using which a distribution will be created. can somebody point out the steps to be followed for accomplishing this task. Thanks in Advance Pramodh **************************Disclaimer************************************ Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited. ***************************************************************************

1 0

merging classes without AutoYaST
by Michal Kubecek 15 Jun '03

15 Jun '03

Is it possible to merge class files into a control file "manually", ie without AutoYaST? I tried to use xsltproc and XSLT stylesheet I found in /usr/share/autoinstall/xslt/merge.xslt. xsltproc cannot find DTD files since the paths in XML headers are /usr/share/autoinstall but DTD files are in /usr/share/autoinstall/dtd. Even after linking DTD's into /usr/share/autoinstall the result looks different from what I get with AutoYaST. Michal Kubecek

2 1

Re: [suse-autoinstall] error .. packages not available during iso creation
by Richard Bos 14 Jun '03

14 Jun '03

Op donderdag 12 juni 2003 23:38, schreef sytse: > repository in autoyast means the place where your XML files will be stored. > > Did you do the 'change source of installation' in yast2? After changing the "source of installation" in yast package manager most of the pkgs were found. May I state that the verbosity of the error msg is not enough, should this be considered as a bug (perhaps the documentation should say something about it)? Shouldn't it be possible to provide the source of installation via "autoinstall -> file -> preferences -> "source of installation", this would intuitive. At this moment I selected Minimal.sel for the packages, in the process of creating the ISO 2 pkgs are missing. There is however no list with pkgs that are missing, not in yast on screen neither in the log file. I found a file called .../log/YaST2/badlist, that states that k_athlon should be removed from the list.source of installation [1]. How can I determine which pkgs are missing, I have mapped the Minimal.sel file with the packages file as well as with the installed rpms (and vice versa), but so clause sofar. Is this a bug too, or do I overlook something trivial?? I just continued here creating the iso. Yast stated it was about to write iso image (small window). There is however no progress meter (I know now), it was just doing nothing.... I aborted the process after minutes of waiting. Analysis of the log file revealed that there was lack of disk space. Which is very well possible as my /tmp filesystem is only 100MB. No problem, I extended the filesystem with lvm to 850 MB and started the ISO process once more. This time it finished successfully. May I propose that yast-autoinstall checks the disk space availability at some smart points? E.g. during the rpm copy process, after writing the iso skeleton, and before the creation of the iso image? In my case with the Minimal.sel selection 2x 210 MB is necessary. BTW: and it possible to link the rpms into the skeleton directory. This would save a lot of diskspace and is probably faster too... (With the default package selection more than 850 MB is needed to create the iso skeleton, so I should extend /tmp once more). I hope not to offend anyone, with this feedback! I just noticed these things and though to let you (most likely Anas ;) know. > On Thursday 12 June 2003 23:32, Richard Bos wrote: > > Op donderdag 12 juni 2003 22:57, schreef Richard Bos: > > > in the process of creating an iso image, autoyast checks the package > > > availality, in my case this check fails. That's probably due to an > > > incorrect repository setup. Can someone enlighten me, what the correct > > > setup should be. The error message I get is "498 packages not > > > available". > > > > > > I just choose a "default" system, no other pkgs have been added. > > > > Forgot to mention that I use SuSE-8.2. The system is installed from CD. > > The repository has been set to ....suse82/base/ as well as > > suse82/base/suse using "File -> prefereneces". -- Richard Bos Without a home the journey is endless [1] badlist: linux01:/var/log/YaST2 # cat badlist 2 packages failed Name: k_deflt Edition: 2.4.20-62 From-Input-List: yes Conflicts-With: k_athlon conflicts with k_deflt, k_deflt conflicts with k_athlon Remove-To-Solve-Conflict: k_athlon Name: k_smp Edition: 2.4.20-62 From-Input-List: yes Conflicts-With: k_athlon conflicts with k_smp, k_smp conflicts with k_athlon Remove-To-Solve-Conflict: k_athlon y2log: 2003-06-13 11:52:49 <3> hvslinux01(7918) [Interpreter] autoinstall/iso.ycp:157 [WFM] variable tok is not declared 2003-06-13 11:52:49 <3> hvslinux01(7918) [Interpreter] autoinstall/iso.ycp:157 [WFM] variable tok is not declared 2003-06-13 11:52:58 <3> hvslinux01(7918) [Interpreter] modules/HTML.ycp:116 cant add this type to string 2003-06-13 11:52:58 <3> hvslinux01(7918) [Interpreter] modules/HTML.ycp:116 cant add this type to string

4 8

pxelinux.0
by Florian Letz 14 Jun '03

14 Jun '03

Hi, I read the script again and again, but I didn't get it. Where do you get the file pxelinux.0 from? And what does it contain? With friendly greetings. Flo

2 1

Documentation Issues
by Tobias_Mucke＠mn.man.de 13 Jun '03

13 Jun '03

Hi everybody, last few days I had some nasty problems with the configuration in autoinst.xml. The major problem was that some part of the documentation is false or inactual. I used the Book "AutoYast2 Automatic Linux Installation und Configuration with YaST2" Revision 0.9. So be aware always to use the newest documentation available, which is right now Version 1.1! By the way, how often are there changes in xml tags? In 0.9 it was e.g. <network> now it is <networking>. Is there a validating parser, which can validate autoinst.xml? 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.

3 2

Antwort: [suse-autoinstall] Antwort: Re: [suse-autoinstall] Antwort: Re: [suse-autoinstall] Autoyast and LVM Update
by Tobias_Mucke＠mn.man.de 13 Jun '03

13 Jun '03

Hi, Sorry. Last script had some bugs and was posted without many tests. Here is the update. Any comments are greatly appreciated. <scripts> <pre-scripts config:type="list"> <script> <filename>/vgremove.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ insmod lvm-mod vgscan vgs=`echo /dev/vg_*` for vg in $vgs do if [ -d $vg ] then vgchange -a y $vg lvs=`ls $vg` for lv in $lvs do i=`basename $lv` if [ $lv != "group" ] then lvremove -f $vg/$lv fi done vgchange -a n $vg vgremove $vg done ]]> </source> </script> </pre-scripts> </scripts> 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 -------------------------------------------------------------------------------------------------- Diese Mitteilung sowie eventuelle Anhänge sind vertraulich und können privilegiert oder auf andere Weise gegen Weitergabe geschützt sein. Sollten Sie nicht der beabsichtigte Empfänger sein, bitte rufen oder mailen Sie den Absender an und löschen Sie diese Mitteilung sowie eventuelle Anhänge aus Ihrem System. Sind Sie nicht der beabsichtigte Empfänger, dürfen Sie diese Mitteilung bzw. die Anhänge weder kopieren noch an andere Personen weitergeben.

2 1

SuSE-8.2 & autoinstall
by Mikhail Terekhov 13 Jun '03

13 Jun '03

Hi, I'm trying to learn autoyast on my up to date SuSE-8.2 box and currently I'm stuck with the following problems: 1. When I save my configuration in a file, yast puts wrong path to the profile.dtd. It puts <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/profile.dtd"> instead of <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> If I correct this path then xmllint complains: my_clone_printer_only.xml:6: validity error: No declaration for attribute type of element cups_installation <cups_installation config:type="integer">0</cups_installation> ^ my_clone_printer_only.xml:6: validity error: No declaration for element cups_installation <cups_installation config:type="integer">0</cups_installation> ^ my_clone_printer_only.xml:7: validity error: No declaration for attribute type of element database <database config:type="symbol">foomatic</database> ^ my_clone_printer_only.xml:7: validity error: No declaration for element database <database config:type="symbol">foomatic</database> ^ my_clone_printer_only.xml:11: validity error: No declaration for attribute type of element accepting <accepting config:type="boolean">true</accepting> .... .... 2. When I try to clone my system and select to clone only printer settings and save to a file then yast clones and writes to the file everything - software, network, printers, e.t.c. But when I select to clone everyting including software it clones and saves all but software. Please help. What am I missing there? Regards, Mikhail

3 5

Re: [suse-autoinstall] User and Groups
by Tobias_Mucke＠mn.man.de 13 Jun '03

13 Jun '03

Thanks for this hint. Unfortunately I'am using SLES8 and it seems that it doesn't support these tags. Anybody any experiences with <groups>. Which version of autoyast do I need. Is there an update for SLES8. Thanks in advance. Have a nice weekend. 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

User and Groups
by Tobias_Mucke＠mn.man.de 13 Jun '03

13 Jun '03

Hi, I wan't to create Users and Groups at the end of installation. But each of these users must have his own primary group with a customized gid. I never found a tag to create groups. Isn't there any? Thanks for help. 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.

2 1

Re: [suse-autoinstall] Updating YaST2 in installation repository
by Helge C. Rutz 13 Jun '03

13 Jun '03

Hello, can you please describe how to force already installed systems to use the new packages from the updated repository? As long as the clients use there old lokal package desriptions, I run into source not found errors when trying to install additional packages that were updated. Thanks Helge Rutz University of Karlsruhe Anas Nashif wrote > >Hi, > > >Yes, It is just as you described below. > > >Anas > > >Fermín Galán wrote: >> Hello everyone, >> >> I have read in the online documentation >> available that bugs of the autoinstallation >> system (enable_3d, password in clear text, ...) >> can be solved updating yast2 related >> RPMs (yast2, autoyast2, yast2-x11, etc). >> >> I would like to know wheter the updating processes >> is as simple as the addition of customized packages: >> delete the old RPM file in the repository, copy the >> updated one to the same directory (noarch, i586, >> etc.) and runing >> >> cd <repository>/suse >> /usr/lib/YaST2/bin/create_package_descr >> >> to update the packet database. >> >> I'm using/installing SuSE 8.1. >> >> Thanks in advance! >> >> ------- >> Fermín >> fermin.galan(a)agora-2000.com >> Agora Systems, S.A. >>

1 0

Antwort: Re: [suse-autoinstall] Antwort: Re: [suse-autoinstall] Autoyast and LVM
by Tobias_Mucke＠mn.man.de 13 Jun '03

13 Jun '03

Hi it is me again. Andreas Matthieu send me a little pre-script, which would delete LVM data of a specific vg. I added some code, so that it should now be possible do delete all vgs. Here it is. <scripts> <pre-scripts config:type="list"> <script> <filename>/vgremove.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[ vgs=`ls /dev/vg_*` insmod lvm-mod vgscan for vg in $vgs do if [ -d $vg ] then vgchange -a y $vg lvs=`ls $vg` for lv in $lvs do i=`basename $lv` if [ $lv != "group" ] then lvremove -f $vg/$lv fi done vgchange -a n $vg vgremove $vg done ]]> </source> </script> </pre-scripts> </scripts> 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 -------------------------------------------------------------------------------------------------- Stefan Weigel <sw@global-linxs. An: "Andreas Rother" <Andreas.Rother(a)eplus.de> de> Kopie: suse-autoinstall(a)suse.com Thema: Re: [suse-autoinstall] Antwort: Re: [suse-autoinstall] Autoyast and LVM 12.06.2003 13:11 Bitte antworten an sw Hi! Maybe this would work: >From the documentation (http://www.suse.de/~nashif/autoinstall/8.1/html/c326.html#AEN690): Pre-Install Scripts Executed before YaST2 does any real change of the system (Before partitioning ~~~~~ and package installation) So, make such a script and do a: vgscan vgchange -a y lvremove /dev/myvg/mvlv lv remove /dev/myvg/mylv2 [..] vgchange -a n vgremove myvg If you have different systems with different vg's/lv's, then you could write a script which does these steps automaticly (get the lv/vg from the output from vgscan & lvscan). Best regards Stefan Am Donnerstag, 12. Juni 2003 08:47 schrieb Andreas Rother: > Hi, > > we have the same problem here with SLES8. Our Workaround is to have an > additional autoyast-config without LVM, so we wipe out any lvm information > on the disks, before we install the server. > > Of course it would be nicer, if this bug would be solved ;-) > > Kind regards > Andreas Rother > UNIX-Systemadministration -- __________________________________________ stefan weigel administration global linxs gmbh knowledge interaction romanstrasse 16 80639 munich - germany www.global-linxs.com tel.: +49(0)89. 189 336- 61 fax.: +49(0)89. 189 336- 99 email: sw(a)global-linxs.com __________________________________________ -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com Diese Mitteilung sowie eventuelle Anhänge sind vertraulich und können privilegiert oder auf andere Weise gegen Weitergabe geschützt sein. Sollten Sie nicht der beabsichtigte Empfänger sein, bitte rufen oder mailen Sie den Absender an und löschen Sie diese Mitteilung sowie eventuelle Anhänge aus Ihrem System. Sind Sie nicht der beabsichtigte Empfänger, dürfen Sie diese Mitteilung bzw. die Anhänge weder kopieren noch an andere Personen weitergeben.

1 0

Antwort: RE: [suse-autoinstall] Antwort: Re: [suse-autoinstall] Autoyast a nd LVM
by Tobias_Mucke＠mn.man.de 13 Jun '03

13 Jun '03

Not really, because lvm stores it data in the vgda which is located on the pvs not in the mbr. To delete these you have to execute dd if=/dev/zero of=/dev/hd*, but this could take a long time depending on space of the harddisk. 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 -------------------------------------------------------------------------------------------------- Voss Stefan <stefan.voss@itel An: "'suse-autoinstall(a)suse.com '" <suse-autoinstall(a)suse.com> lium.com> Kopie: Thema: RE: [suse-autoinstall] Antwort: Re: [suse-autoinstall] Autoyast a nd LVM 12.06.2003 15:06 Hi, if pre scripts are executed even before partinioning maybe one can use dd if=/dev/zero of=/dev/hdx bs=512 count=2 to wipe out any lvm or raid info from the harddisks Regards, Stefan Voss -----Original Message----- From: Stefan Weigel To: Andreas Rother Cc: suse-autoinstall(a)suse.com Sent: 6/12/2003 1:11 PM Subject: Re: [suse-autoinstall] Antwort: Re: [suse-autoinstall] Autoyast and LVM Hi! Maybe this would work: >From the documentation (http://www.suse.de/~nashif/autoinstall/8.1/html/c326.html#AEN690): Pre-Install Scripts Executed before YaST2 does any real change of the system (Before partitioning ~~~~~ and package installation) So, make such a script and do a: vgscan vgchange -a y lvremove /dev/myvg/mvlv lv remove /dev/myvg/mylv2 [..] vgchange -a n vgremove myvg If you have different systems with different vg's/lv's, then you could write a script which does these steps automaticly (get the lv/vg from the output from vgscan & lvscan). Best regards Stefan Am Donnerstag, 12. Juni 2003 08:47 schrieb Andreas Rother: > Hi, > > we have the same problem here with SLES8. Our Workaround is to have an > additional autoyast-config without LVM, so we wipe out any lvm information > on the disks, before we install the server. > > Of course it would be nicer, if this bug would be solved ;-) > > Kind regards > Andreas Rother > UNIX-Systemadministration -- __________________________________________ stefan weigel administration global linxs gmbh knowledge interaction romanstrasse 16 80639 munich - germany www.global-linxs.com tel.: +49(0)89. 189 336- 61 fax.: +49(0)89. 189 336- 99 email: sw(a)global-linxs.com __________________________________________ -- 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 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

error .. packages not available during iso creation
by Richard Bos 12 Jun '03

12 Jun '03

in the process of creating an iso image, autoyast checks the package availality, in my case this check fails. That's probably due to an incorrect repository setup. Can someone enlighten me, what the correct setup should be. The error message I get is "498 packages not available". I just choose a "default" system, no other pkgs have been added. I now have: ....suse82/base/suse/setup/descr/packages ....suse82/base/suse/i586/ ....suse82/base/suse/i686/ ....suse82/base/suse/noarch/ ....suse82/base/suse/src/ Should this be okay (that's how I mirrored it from the ftp server)? (I used the packages database as is (the mirrored one)). I tried the following setup as well: ....suse82/base/setup/descr/packages ....suse82/base/suse/i586/ ....suse82/base/suse/i686/ ....suse82/base/suse/noarch/ ....suse82/base/suse/src/ here I used a package database created by create_...._...._packages I'm still getting the ".. packages not available" (it's in iso.ycp). Should I try: ....suse82/base/suse/setup/descr/packages ....suse82/base/suse/<all pkgs> I hope someone can give a push in the back to get me on speed. -- Richard Bos Without a home the journey is endless

1 1

autoyast always asks for enabling 3d-hardware support
by stefan sokoll 12 Jun '03

12 Jun '03

hi during autoinstall i have to do user interaction for deciding if i like to have 3d-hardware support for my graphics card enabled - how can i avoid that? my x11 configuration: <x11> <color_depth config:type="integer">16</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> #### i've already defined it here: <enable_3d config:type="boolean">true</enable_3d> <monitor> <monitor_device>unknown model</monitor_device> <monitor_vendor>unknown vendor</monitor_vendor> </monitor> <resolution>1024x768</resolution> <start_x11 config:type="boolean">true</start_x11> </x11> thanks, stefan --------------------------------- Gesendet von http://mail.yahoo.de Mit freenetDSL jetzt so schnell wie günstig durchstarten! Bereits in vielen Ortnetzen verfügbar. Mehr Info: dsl.freenet.de.

2 1

RE: [suse-autoinstall] Antwort: Re: [suse-autoinstall] Autoyast a nd LVM
by Voss Stefan 12 Jun '03

12 Jun '03

Hi, if pre scripts are executed even before partinioning maybe one can use dd if=/dev/zero of=/dev/hdx bs=512 count=2 to wipe out any lvm or raid info from the harddisks Regards, Stefan Voss -----Original Message----- From: Stefan Weigel To: Andreas Rother Cc: suse-autoinstall(a)suse.com Sent: 6/12/2003 1:11 PM Subject: Re: [suse-autoinstall] Antwort: Re: [suse-autoinstall] Autoyast and LVM Hi! Maybe this would work: >From the documentation (http://www.suse.de/~nashif/autoinstall/8.1/html/c326.html#AEN690): Pre-Install Scripts Executed before YaST2 does any real change of the system (Before partitioning ~~~~~ and package installation) So, make such a script and do a: vgscan vgchange -a y lvremove /dev/myvg/mvlv lv remove /dev/myvg/mylv2 [..] vgchange -a n vgremove myvg If you have different systems with different vg's/lv's, then you could write a script which does these steps automaticly (get the lv/vg from the output from vgscan & lvscan). Best regards Stefan Am Donnerstag, 12. Juni 2003 08:47 schrieb Andreas Rother: > Hi, > > we have the same problem here with SLES8. Our Workaround is to have an > additional autoyast-config without LVM, so we wipe out any lvm information > on the disks, before we install the server. > > Of course it would be nicer, if this bug would be solved ;-) > > Kind regards > Andreas Rother > UNIX-Systemadministration -- __________________________________________ stefan weigel administration global linxs gmbh knowledge interaction romanstrasse 16 80639 munich - germany www.global-linxs.com tel.: +49(0)89. 189 336- 61 fax.: +49(0)89. 189 336- 99 email: sw(a)global-linxs.com __________________________________________ -- 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] Autoyast and LVM
by Andreas Rother 12 Jun '03

12 Jun '03

Hi, we have the same problem here with SLES8. Our Workaround is to have an additional autoyast-config without LVM, so we wipe out any lvm information on the disks, before we install the server. Of course it would be nicer, if this bug would be solved ;-) Kind regards Andreas Rother UNIX-Systemadministration -- Andreas Rother - E-Plus Mobilfunk GmbH & Co. KG Division Operations - System & Application Management - Systems Operation & Services - Open Systems Phone : unbekannt / Fax : unbekannt / Mobile : unbekannt Anas Nashif <nashif(a)suse.de> 06.06.2003 18:35 An: Tobias_Mucke(a)mn.man.de Kopie: suse-autoinstall(a)suse.com Thema: Re: [suse-autoinstall] Autoyast and LVM Hi, What release are using? 8.1? SLES? 8.2? Anas Tobias_Mucke(a)mn.man.de wrote: > Hi everybody, > > I'm using Autoyast and LVM together successfully during the first > installation. But when I try a second installation on the same node, yast2 > says that Volume Groups allready exist and doesn't format the lvols. > > Can I force YaST to create pvs ignoring that they are already in a vg? > > Thanks for help. > > > > Mit freundlichen Grüßen > > Tobias Mucke > > -------------------------------------------------------------------------------------------------- -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Help on Apache2 and PHP4 in SuSE Pro 8.2
by Anders Norrbring 10 Jun '03

10 Jun '03

Hi everybody! I'm trying to install Apache2 together with PHP4 and phpMyAdmin on my new SuSE Pro 8.2 server, but so far - no luck.. I use the standard installation options in Yast2 when I do a absolute fresh install on the computer and I've got the "Auto check dependencies" on. So, I thought all was well after marking up Apache2, PHP4 and phpMyAdmin and correlating modules as suggested by Yast2. But no... The server doesn't even understand that PHP4 is installed after what it seems to me, if I try to access a .php page, it insists on sending me the page as a download file instead of interpreting it and sending the output. Does anyone know the reason/solution to this, or is it a clear case of calling support? Later, Anders Norrbring Norrbring Consulting

2 1

RE: [suse-autoinstall] SuSE-8.2 & autoinstall
by Robison, Jonathon (M.) 10 Jun '03

10 Jun '03

In regards to my earlier problem - The yast system backup function appears to lock up if the drive does not have room to write the backup. Perhaps an added line in the scripts to monitor disk availability and pop up a "gotta abort - not enough room" message? Jonathon M. Robison Linux Integration Analyst Strategic Infrastructure Engineering 313-323-9529 -----Original Message----- From: Mikhail Terekhov [mailto:terekhov@emc.com] Sent: Tuesday, June 10, 2003 3:47 PM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] SuSE-8.2 & autoinstall Anas Nashif wrote: > Hi, > A new version with a fixed DTD will be provided soon. Can you please > Anas, Thanks for the information, any estimate when it will be available? Regards, Mikhail -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Platform Questions
by Volker.Wiegand＠t-online.de 10 Jun '03

10 Jun '03

Hi, I have two questions, maybe I can get some help here :-) 1.) Can I use AutoYaST for z/Linux in the same way as for Intel? 2.) Assuming I want to target SLES8 z/Linux production servers, can I use an 8.2 Pro as the development / repository server? What would I have to observe? Kind regards Volker Wiegand

2 1

Problems with reporting
by Stefan Weigel 10 Jun '03

10 Jun '03

Hi! I have one problem left within my autoinstallation process. When all RPM's are installed, lilo is written into the bootsector. After that a message pops up with "Sucessfully written into Bootsector [..]". The pop up needs to be confirmed with a click on the OK button. That's strange to me. I've read about the default should be show all errors/warnings/messages with a timeout of 10 seconds even if I don't have a <report> section in my autoinst.xml. I've also made a <report> section (see below) but without any postive result. So, can anybody give me a hint about this prob ? Btw.: I am using the latest autoyast packages with the latest update image (y2update.gz) on floppy. Part of my autoinst.xml: [..] <install> <bootloader> <activate config:type="boolean">false</activate> <initrd_modules config:type="list"> <listentry>DAC960</listentry> <listentry>lvm-mod</listentry> <listentry>ext3</listentry> </initrd_modules> <lba_support config:type="boolean">true</lba_support> <linear config:type="boolean">false</linear> <location>mbr</location> </bootloader> <report> <messages> <show>true</show> <timeout>5</timeout> <log>true</log> </messages> <errors> <show>true</show> <timeout>5</timeout> <log>true</log> </errors> <warnings> <show>true</show> <timeout>5</timeout> <log>true</log> </warnings> </report> [..] Best regards Stefan -- __________________________________________ stefan weigel administration global linxs gmbh knowledge interaction romanstrasse 16 80639 munich - germany www.global-linxs.com tel.: +49(0)89. 189 336- 61 fax.: +49(0)89. 189 336- 99 email: sw(a)global-linxs.com __________________________________________

3 3