November 2009 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] Feature request _ask_ for rules/class merging
by Martin Vogt 24 Nov '09

24 Nov '09

Hello, I would like to have the following feature: on the server I have some templates("rules") for different partitioning,software etc. But I like the user who installs the system to select these rules (instead of the automatic matching) During Autoyast, before the installation starts, a window should appear which shows all rules by Name and the user then clicks the rulenames which he wants to be applied to the autoyast.xml file. I know that there are "rules/classes" already and its possible to add <ask> dialogs during autoinstall. But I think its not possible to merge rules with an ask statement. regards, Martin -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 7

[opensuse-autoinstall] Avoid SaX during install
by Beat Rubischon 19 Nov '09

19 Nov '09

Hello! I see some troubles with SLES10sp2 and workstations containing two graphics cards. One Matrox is on board, a second Nvidia plugged into a PCIe slot. We need both of them as the first provides KVM over IP and the second one is attached to the local monitor where the user works. SaX called from the installer is able to configure the screen in the case where the Nvidia card is the primary in the BIOS. In the desired case where the Matrox card is the primary one, SaX hangs during the start of the X11 server. Is there any clean way to avoid the usage of SaX in a AutoYast installation? The last time I had this problem I removed all X11 related packages from the list of patterns and installed them afterwards in a script. It works, but it's quite ugly to maintain such a setup. Beat -- \|/ Beat Rubischon <beat(a)0x1b.ch> ( 0^0 ) http://www.0x1b.ch/~beat/ oOO--(_)--OOo--------------------------------------------------- Meine Erlebnisse, Gedanken und Traeume: http://www.0x1b.ch/blog/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] cups configuration for OpenSuse 11.1
by Hans-Joachim Ehlers 18 Nov '09

18 Nov '09

Hi, its looks like that on OS 11.1 cups aka the printer devices can not be configured. yast clone_system nor yast autoyast provide/give a printer configuration. According to bugzilla the problem is fixed in yast-printer v2.18 but I have 2.17 OS 11.1 Update state as of 2009/11/16 has version yast2-printer-2.17.48-2.5 which does not allow to configure the printer. BTW: Can I use the profile section from OS 10.3 installation since there the printer can be configured for autoyast. tia Hajo -- Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Eumetsat-Allee 1 64295, Darmstadt, Germany Tel : +49 6151 807-7307 mailto:hansjoachim.ehlers@eumetsat.int http://www.eumetsat.int

3 2

[opensuse-autoinstall] Failed nfs mount
by John Drury 17 Nov '09

17 Nov '09

Hi Guys The logs show that rpc.statd or -o nolock are the answer, I thought that using openSUSE 11.1 would not have this kind of problem. Both install and autoyast are getting there info from this server, which for testing only is allowing any of my subnets to nfs mount the folders. I will try the nolock option as rpc.statd is rather weak. Regards John Drury MBE IS Support Lion Gate Building Lion Gate Portsmouth PO1 3DJ 023 9284 2235 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] Hi Guys
by John Drury 17 Nov '09

17 Nov '09

Hi Guys This is my start of a post script which will be followed by an init script but I have fallen at the first hurdle. The Likewis files are not copied because the mount command does not work. Any ideas? <scripts> <post-scripts config:type="list"> <script> <filename>post.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[ #!/bin/sh echo "Running Post-install script" ### create release file touch /etc/uop-release ### enter latest release number echo "1.0" >> /etc/uop-release ### start network /etc/init.d/network restart /etc/init.d/portmap restart ### make mount point and mount folders mkdir /mnt/uop mount xxx.xxx.xxx.xxx:/data/suse11132 /mnt/uop mkdir /uop cp -R /mnt/uop/nfsexports/Likewise* /uop umount /mnt/uop ]]></source> </script> </post-scripts> Regards John Drury MBE IS Support Lion Gate Building Lion Gate Portsmouth PO1 3DJ 023 9284 2235 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] List of available Pattern
by Eduard Diner 13 Nov '09

13 Nov '09

Hi there, is there somewhere a list of all available <pattern> in SLES11? I want to include the 32-Bit-Runtime Environment. I have no idea how it has to be called in autoyast. Cheers, edy -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 5

[opensuse-autoinstall] <boot_mbr> vs. <location> and <loader_device>
by Frank Steiner 13 Nov '09

13 Nov '09

Hi, I'm trying to understand how the options <boot_mbr> <generic_mbr> <activate> <location> <loader_device> interact. On a x86_64 machine guess that I want /dev/sda3 to contain the bootloader and be activated, i.e. the MBR should stay clean from bootloader code. According to http://www.suse.de/~ug/autoyast_doc/CreateProfile.Bootloader.html I should set <global> <activate>true</activate> <generic_mbr>false</generic_mbr> <boot_mbr>false</boot_mbr> </global> But it ended up without /dev/sda3 activated (which is the / partition, containing /boot). I realized that we still had <loader_device>/dev/sda</loader_device> <location>mbr</location> in the bootloader section, too, so they seem to be contradictory. <location> and <loader_device> are not really documented on the web page. Can I just drop both? Would AY detect the root/boot partition automatically with the 3 global settings above? Or would I need <loader_device>/dev/sda3</loader_device> cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. * -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 7

[opensuse-autoinstall] keyboard layout X11
by Jochen Schaefer 10 Nov '09

10 Nov '09

Hi, I recently installed a sles10sp2 server via autoyast with keymap de-latin1-nodeadkeys. When starting X it changes to keymap us. responsible seems to be in xorg.conf: Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "us" Option "XkbModel" "microsoftpro" Option "XkbRules" "xfree86" EndSection Is there any tag in autoyast which I can use to have same keyboard layout at X and console? Thanks, Jochen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] minimal installation
by Dirk.Lohmann＠Bertelsmann.de 09 Nov '09

09 Nov '09

Hello List, we like to install SLES 10 (11) with autoyast. We need a minimal Installation. Ist tehre a comfortable way to say this in the xml File ? Dirk Lohmann Systemadministrator Linux

2 1

[opensuse-autoinstall] Using Opensuse 11.1 PAE Kernel
by Hans-Joachim Ehlers 05 Nov '09

05 Nov '09

VGFzazoNCk5ldHdvcmsgaW5zdGFsbGF0aW9uIG9mIE9wZW5TdXNlIDExLjEgd2l0aCBQQUUga2VybmVsIA0KDQpQcm9ibGVtOg0KSW4gdGhlIGF1dG9pbnN0LnhsbSB0aGUgc2VjdGlvbiBmb3IgdGhlIGtlcm5lbCBoYXMgYmVlbiBhZGRlZC4NCi4uLg0KICA8c29mdHdhcmU+DQogICAgPGtlcm5lbD5rZXJuZWwtcGFlPC9rZXJuZWw+DQogICAgPHBhY2thZ2VzIGNvbmZpZzp0eXBlPSJsaXN0Ij4NCi4uLi4NCg0KYnV0IGFmdGVyIGluc3RhbGxhdGlvbiB0aGUgZGVmYXVsdCBrZXJuZWwgYW5kIHRoZSBwYWUga2VybmVsIGFyZSBpbnN0YWxsZWQgYW5kIHRoZSBkZWZhdWx0IGtlcm5lbCBpcyB1c2VkIGFzIHRoZSBkZWZhdWx0Lg0KDQpBbmFseXNlOg0KSXQgbG9va3MgbGlrZSB0aGF0IHNpbmNlIG15IG5ldHdvcmsgYm9vdCBrZXJuZWwgaXMgdGhlICJkZWZhdWx0IiBrZXJuZWwgYW5kIG5vdCB0aGUgInBhZSIgdGhlIGRlZmF1bHQga2VybmVsIGdldHMgaW5zdGFsbGVkIGFzIHdlbGwuDQpUaHVzIHRoZSBxdWVzdGlvbjogU2luY2UgSSBhbSBub3QgYWJsZSB0byBmaW5kIHRoZSBQQUUga2VybmVsIG9uIHRoZSBJU08gaW1hZ2UgLSBjYW4gSSBzaW1wbHkgdXNlIHRoZSBwYWUga2VybmVsIGFuZCBpbml0cmQgZnJvbSBhIHN5c3RlbSBydW5uaW5nIHRoZSBwYWUga2VybmVsIGFuZCBwdXQgdGhhdCBvbmUgb24gbXkgYm9vdCBzZXJ2ZXIgPw0KDQp0aWENCkhham8NCg0KDQotLQ0KIEhhbnMtSm9hY2hpbSBFaGxlcnMNCiBVTklYIFN5c3RlbXMgRW5naW5lZXINCiBFVU1FVFNBVA0KIEV1bWV0c2F0LUFsbGVlIDENCiA2NDI5NSwgRGFybXN0YWR0LCBHZXJtYW55DQogVGVsIDogKzQ5IDYxNTEgODA3LTczMDcNCiBtYWlsdG86aGFuc2pvYWNoaW0uZWhsZXJzQGV1bWV0c2F0LmludA0KIGh0dHA6Ly93d3cuZXVtZXRzYXQuaW50DQoNCg0K-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.orgFor additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1