June 2003 - openSUSE Autoinstall - openSUSE Mailing Lists

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