May 2007 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] SuSE 10.1 + Converting from dhcp to static IP
by King, Richard (CE1 UNIX Admin) 04 May '07

04 May '07

***Sending Message again, first message didn't seem to go through*** SuSE Version: 10.1 Install Method: PXEBOOT/DHCP Hello Everyone! I was wondering if anyone had any suggestions on how-to convert from dhcp-boot to static IP during the autoyast install? Questions: 1) Should converting from dhcp-boot to static IP take place during pre-scripts, or post-scripts? 2) When the install is initiated with dhcp, what file holds the network/dhcp information during the install process? 3) Would it be practical to use commands such as ifconfig and netstat to get the network information, and write to the /etc/sysconfig/network/ifcfg-eth-id-$MAC and /etc/sysconfig/network/routes files? Observations: I have noticed if a client is using dhcp, the package "NetworkManager" is installed, and will manage the network settings for eth0. However, if a client is using dhcp/NetworkManager, the NTP & NIS services will fail to start during bootup. If I manually change the network settings to static, NTP & NIS will start during bootup. Any help with this would be greatly appreciated. My best to you -- Rick King This is what I have in the network section of my control file. <networking> <nfs_server> <nfs_exports config:type="list"> <nfs_export> <allowed config:type="list"> <allowed_clients>@lab_nis(rw,sync)</allowed_clients> </allowed> <mountpoint>/local</mountpoint> </nfs_export> </nfs_exports> <start_nfsserver config:type="boolean">true</start_nfsserver> </nfs_server> <dhcp_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <hostname>AUTO</hostname> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

[opensuse-autoinstall] Overview of autoyast process
by Simon Crute 04 May '07

04 May '07

Hi All, Despite using autoyast for years and knowing it quite well, I still get confused at exactly what point various scripts run at, and when yast reboots at. I think I've nearly got it, but I'd welcome someone looking over this list, and correcting it where it's wrong. [* rules file is downloaded and processed * one of more profile fragments are downloaded and merged] OR [* the full profile is downloaded.] * any pre scripts are ran * Ask commands are ran and user interaction runs. * installation confirmation screen is shown. * 1st part of the installation starts * chroot=false chroot scripts are ran. * installer chroots into the new system. * chroot=true chroot scripts run. * yast configures the system * post install scripts run At this point, I'm confused. When are post install scripts with network_needed=true and network_needed=false ran, what is the difference in the environments they run it ? * system reboots * init scripts run I also need to look at classes and figure out how they fit into the picture. As I understand it right now, they are similar to a #include in that they cause AY to merge a new profile in if the current profice has a class definition in it. Thanks. -- Simon Crute IS&T. Bracknell. UK. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] SuSE 10.1 + Converting from dhcp to static IP
by King, Richard (CE1 UNIX Admin) 04 May '07

04 May '07

SuSE Version: 10.1 Install Method: PXEBOOT/DHCP Hello Everyone! I was wondering if anyone had any suggestions on how-to convert from dhcp-boot to static IP during the autoyast install? Questions: 1) Should converting from dhcp-boot to static IP take place during pre-scripts, or post-scripts? 2) When the install is initiated with dhcp, what file holds the network/dhcp information during the install process? 3) Would it be practical to use commands such as ifconfig and netstat to get the network information, and write to the /etc/sysconfig/network/ifcfg-eth-id-$MAC and /etc/sysconfig/network/routes files? Observations: I have noticed if a client is using dhcp, the package "NetworkManager" is installed, and will manage the network settings for eth0. However, if a client is using dhcp/NetworkManager, the NTP & NIS services will fail to start during bootup. If I manually change the network settings to static, NTP & NIS will start during bootup. Any help with this would be greatly appreciated. My best to you -- Rick King This is what I have in the network section of my control file. <networking> <nfs_server> <nfs_exports config:type="list"> <nfs_export> <allowed config:type="list"> <allowed_clients>@lab_nis(rw,sync)</allowed_clients> </allowed> <mountpoint>/local</mountpoint> </nfs_export> </nfs_exports> <start_nfsserver config:type="boolean">true</start_nfsserver> </nfs_server> <dhcp_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <hostname>AUTO</hostname> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> -- 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] Install problems on HP DL380 G5
by dbellis＠mmm.com 04 May '07

04 May '07

Hello everyone, I am having the following problem when trying to install SLES9 sp3 on a HP DL380 G5. I do not have the problem under SLES10. Your computer does not fulfill all requirements for a graphical installation.There is less than 96MB memory or the X server could not be started. As a fallback,the text front-end of YaST will guide you through the installation.This front-end offers the same functionality as the graphical one,but the screens differ from those in the manual. It looks like some other people have had the same issue, but I couldnt' find a posted solution. http://forums1.itrc.hp.com/service/forums/bizsupport/questionanswer.do?thre… Any help would be greatly appreciated. David Bellis -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

[opensuse-autoinstall] verifying the profile
by Rich 03 May '07

03 May '07

i tried to verify a profile according to this page : http://www.suse.com/~ug/autoyast_doc/Profile.DTD.html this failed on sles 10 : /usr/share/YaST2/schema/autoyast/rng/partitioning.rng:263: element define: Relax-NG parser error : Some defines for label needs the combine attribute Relax-NG schema /usr/share/YaST2/schema/autoyast/rng/profile.rng failed to compile am i doing something completely incorrectly ? -- Rich -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] Post-Scripts Not Working
by King, Richard (CE1 UNIX Admin) 02 May '07

02 May '07

SuSE: 10.1 Hello All! I've been trying to run 2 post-scripts, and it appears they are not working. I'll I am trying to is modify 2 files, /etc/passwd & /etc/shadow. This is what I have in the autoyast file: <scripts> <post-scripts config:type="list"> <script> <debug config:type="boolean">false</debug> <feedback config:type="boolean">false</feedback> <filename>nispasswd</filename> <interpreter>shell</interpreter> <location></location> <network_needed config:type="boolean">false</network_needed> <source><![CDATA[cat /etc/passwd | sed 's/+::::::/+::0:0:::/g'] >> /etc/passwd.tmp mv /etc/passwd.tmp /etc/passwd ]]></source> </script> <script> <debug config:type="boolean">false</debug> <feedback config:type="boolean">false</feedback> <filename>nisshadow</filename> <interpreter>shell</interpreter> <location></location> <network_needed config:type="boolean">false</network_needed> <source><![CDATA[cat /etc/shadow | sed 's/+/+::0:0:0::::/g'] >> /etc/shadow.tmp mv /etc/shadow.tmp /etc/shadow ]]></source> </script> </post-scripts> </scripts> As you can see, I am just trying to edit the passwd & shadow files. These scripts are within the <profile></profile> tags. Can someone help me understand why these post scripts are not working? Is there a better way to edit these files? My best to you, -- Rick King -- 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] Removal of Packages
by King, Richard (CE1 UNIX Admin) 02 May '07

02 May '07

SuSE Version: 10.1 Greetings All! I am currently testing a install image for SuSE 10.1. In the control file, I have the following entry to remove software packages: <remove-packages config:type="list"> <package>kdegames3</package> <package>xmoto</package> <package>bsd-games</package> <package>freeciv</package> <package>frozen-bubble</package> <package>supertux</package> <package>knights</package> <package>enigma</package> <package>autofs</package> </remove-packages> The install went fine, however, the packages that I want removed, were installed. I have the remove-packages section within the <software></software> tag. Anything else I am missing? My best to you, -- Rick King -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

[opensuse-autoinstall] Preferred installation source
by Lars Stavholm 02 May '07

02 May '07

Does anyone know of a way to tell autoyast to select packages from a specific installation source? I've got my addons installation source setup and it works just fine. However, I've built my own rpm for nagios version 2.9, whereas the suse (10.2) installation contains nagios version 2.5. The version 2.5 is always installed when selected. How do I tell autoyast that I want the 2.9 from my addons? Despite the fact that my rpm is newer, autoyast always selects the 2.5 version from the stock suse 10.2 kit instead of my own addons. I've got an updates addon setup as well, working just fine and I keep it updated. I've noticed that if autoyast finds a newer package in my updates addon, it will select the newer one. But not when from my other addon. Why? It feels like I'm missing something here. Setup is: suse-10.2 suse-10.2/addons suse-10.2/updates Any ideas appreciated /Lars Stavholm -- 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] GPT partitions on install?
by Michael T. Halligan 02 May '07

02 May '07

Is there a way to set a partition through the Yast2 partitioner as having a GPT label? Even better, is it possible to make autoyast create a gpt label on a device before it installs onto it? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1