openSUSE Autoinstall December 2011

autoinstall@lists.opensuse.org

5 participants
6 discussions

by John Willis

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

9 years, 5 months

[opensuse-autoinstall] autoyast with multiple LVM Volume Groups

by big beer

Hello, I'm trying to have autoyast setup some LVM volume groups. I can get things setup with a single volume group, but if try to add 2 volume groups I seem to be running into some issue. I'm using the following xml inside the partitioning section to setup the PVs and add to the volume groups. . . . <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <lvm_group>firstvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdc</device> <partitions config:type="list"> <partition> <lvm_group>secondvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> . . . The problem is that both disks are configured as PVs in the same VG. Both sdb and sdc will be added to firstvg and secondvg will not exist. Am I trying this wrong or am I hitting some sort of bug? thanks -- bigbeer -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

9 years, 8 months

[opensuse-autoinstall] 12.1, autoyast and systemd

by 686f6c6d

Hi, here's the problems I ran into. They all seem to be related to systemd, but I did not want to hijack the other thread, although this one might solve the other problem, too. 1. The final kexec/reboot is not executed. Both <final_reboot config:type="boolean">false</final_reboot>, meaning kexec will be used, and <final_reboot config:type="boolean">true</final_reboot> have no effect at all[0]. This also means that... 2. Init-Services (<runlevel>) defined in autoyast are not started/stopped, so, f.e., no ssh keys are generated. (This also results in a lot of subsequent errors in our setup.) To fix this, just include: <software> <remove-packages config:type="list"> <package>systemd-sysvinit</package> </remove-packages> </software> This way, sysvinit-init will be installed and used. When can we expect autoyast to support systemd? [0]: Once you do a manual reboot (if you happen to have access other than ssh to the machine), the machine will do the autoyast kexec/reboot after that. -- Kind regards/Mit freundlichen Grüßen Christopher 'm4z' Holm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 10 months

[opensuse-autoinstall] Setting up printers with autoyast

by Patrick Begou

I'm a new to autoyast (2 weeks). I've setup an install procedure for my hosts but I still fail to setup properly the printer. I have a "lpadmin" and a "lpoptions" commands working when run as root after the final reboot. I've setup a post-scripts to do this automaticaly but it always fail with: "lpadmin: Unable to connect to server: Connection refused" Even if my post-script requires network and start cupsd. <post-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <filename>imprimantes</filename> <network_needed config:type="boolean">true</network_needed> <notification>Please wait while setting up printers ...</notification> <interpreter>shell</interpreter> <source><![CDATA[ #!/bin/sh service cups start lpadmin -p laser5M -m manufacturer-PPDs/hplip/hp-laserjet_4050_series-ps.ppd.gz -u allow:all -L "Salle A116" -v socket://batA1-most1.hmg.inpg.fr.:9100 -E lpoptions -d laser5M -o PageSize=A4 -o HPOption_Duplexer=True -o InstalledMemory=36MB -o HPOption_Tray3=True -o HPOption_Disk=HardDisk -o Duplex=DuplexNoTumble ]]> </source> </script> </post-scripts> Any suggestion is welcome. Patrick -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

10 years, 2 months

[opensuse-autoinstall] opensuse 12.1 welcome screen

by Pierre Girard

Hello, I'm making an autoyast configuration for 12.1 and when the install is complete I get a grey login screen with a clock on it which is not what I get when I do a manual install. I started yast on a machine and looked into the sysconfig editor and put the same options I saw in the « display manager » and « window manager » sections. The only thing what got written out is this part (I assume because the other options are default). <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>DISPLAYMANAGER</sysconfig_key> <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path> <sysconfig_value>kdm</sysconfig_value> </sysconfig_entry> </sysconfig> There must be something I' missing somewhere, but I can't find it. Any clues? Thanks. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

10 years, 5 months

[opensuse-autoinstall] autoyast-Profile causes yast-Segfault

by Daniel Spannbauer

Hello, strange problem: I have a autoyast-xml-File (made from a set of xml-sniplets) which causes a Segfault of yast2 when I load that profile in yast2-Auto-Installation-Module. YaST got signal 11 at YCP file Profile.ycp:88 /sbin/yast2: line 423: 31763 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS System is openSuSE 11.4, autoyast2-installation-2.20.9-1.2.1, autoyast2-2.20.9-1.2.1, Can I check the validity of the profile without Yast? Regards Daniel -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

10 years, 5 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall December 2011