December 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

re-visited YaST.firstboot question
by Michael Shannon 28 Dec '04

28 Dec '04

I know I've asked this once before, but I've spent some more time going through the scripts and still can't find out how to accomplish what I'm looking for (having the lan module run during Yast2.firstboot, without taking the default proposals) >From what I gather, if you use autoyast it does a few things to prep the system for the first. 1) creates the /var/lib/YaST2/runme_at_boot file and 2) creates the /etc/install.inf ... It does other stuff, but I'm not worried about that right now. When /etc/init.d/boot is run it checks for runme_at_boot and if that exists then /usr/lib/YaST2/bin/YaST2.firstboot runs and that starts /usr/lib/YaST2/bin/YaST2 installation continue This reads the /etc/install.inf file and the values there are used for the rest of the autoinstall. If I make Manual = 1 in /etc/install.inf, yast asks about the network modules, but never drops me to the yast2 lan module, it looks like it just accepts the proposal based on the autoyast=file///a.xml file. If I could force the lan module to run and not accept any defaults it would save me the hassle of having to generate new ssl certificates after running yast lan (host name changes). Thanks again, -m -----Original Message----- From: Michael Shannon [mailto:Michael.Shannon@infospace.com] Sent: Tuesday, December 21, 2004 2:42 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] YaST.firstboot question For a while we thought using DHCP with autoyast sounded like a good idea, but then we decided not to go that direction. I would really like YaST.firstboot to run the lan module on first boot, I've read through the scripts and its not very obvious to me how to make this happen. I've completely removed the lan configuration from autoyast.xml hoping that would force YaST.firstboot to run the lan module, but my efforts yielded very little fruit :( It looks like there might be something in the install.inf file that is telling YaST that the interface has been configured, is there a way around this? Thanks, -m -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

RE: [suse-autoinstall] NIC module confusion
by Suffin, Charles 23 Dec '04

23 Dec '04

Andreas, Regarding the configuration options that are available through XML: I've been using the DTD files that you can find in /usr/share/autoinstall/dtd/ These are the files that are used by the autoinstaller to verify the XML script. That, of course, presupposes that the DTD files themselves are complete -- i.e., that they have all the available options. I agree that a documented list of these things and what they mean (some are obvious, others perhaps not) would be useful. I'm intending to read the source soon to get a handle for how autoyast actually uses this stuff to control installation. -- charlie -----Original Message----- From: Andreas Octav [mailto:Andreas.Octav@anykey.de] Sent: Wednesday, December 22, 2004 6:26 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] NIC module confusion Hi folks, I´m having some trouble autoinstalling SLES9 on a HP Proliant DL 360. The box has a Broadcom GBit NIC onboard and I want to use it with the bcm5700 module. But autoyast doesn´t seem to care about the module information i entered in the xml control file. After finishing the installation my NIC uses the tg3 module. I configured the bcm5700 module for eth0 (and eth1) in the xml control file but it does not seem to work the way it should (i think). There is a module entry in the /etc/sysconfig/network/ifcfg-ethxxx files mentioning bcm5700. Also modifying the modprobe.conf (alias eth0 bcm5700) doesn´t do the job :-( By the way, i did not find any documentation about how to configure a finish-script when installing SLES9. Is there any information about this i overlooked? A complete list of all availlable xml tags would also be very helpful. The documentation at www.suse.com/~nashif doesn´t seem to reveal all the magic that lies in this product... Kind regards, Andreas Octav -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

NIC module confusion
by Andreas Octav 22 Dec '04

22 Dec '04

Hi folks, I´m having some trouble autoinstalling SLES9 on a HP Proliant DL 360. The box has a Broadcom GBit NIC onboard and I want to use it with the bcm5700 module. But autoyast doesn´t seem to care about the module information i entered in the xml control file. After finishing the installation my NIC uses the tg3 module. I configured the bcm5700 module for eth0 (and eth1) in the xml control file but it does not seem to work the way it should (i think). There is a module entry in the /etc/sysconfig/network/ifcfg-ethxxx files mentioning bcm5700. Also modifying the modprobe.conf (alias eth0 bcm5700) doesn´t do the job :-( By the way, i did not find any documentation about how to configure a finish-script when installing SLES9. Is there any information about this i overlooked? A complete list of all availlable xml tags would also be very helpful. The documentation at www.suse.com/~nashif doesn´t seem to reveal all the magic that lies in this product... Kind regards, Andreas Octav

1 0

Interacting with script-launched shell
by Suffin, Charles 22 Dec '04

22 Dec '04

Hi folks, I'm new to this autoinstall email forum, and I am currently learning and using the SuSE installation products. I hope I can participate here as I've seen some good information exchanged in the archives. I am doing some testing with SLES 9.0 on a standard Intel PC. While creating a pre-install script via autoyast's XML control file, I've put in the following lines so I can do some debugging. This was a clever suggestion that I found on Cambridge University's web site (thanks guys!): <source><![CDATA[#!/bin/bash exec /bin/bash -x ]]></source> I believe this should drop me into a bash shell, but if YaST is doing so I can't seem to interact with the shell at all. The console (running YaST in text mode) indicates that I am executing the pre-install script, so I suspect the shell is actually running, but I can't see any output from the shell at all. Ctrl-C seems to let me proceed, so perhaps the shell is taking input from my keyboard, but it is hard to tell. I have found that if I use ctrl-alt-<f2>, <f5>, <f6>, or <f9>, there appear to be shells already running on those alternate ttys which I can use for debugging. That's cool. However, I don't think they're related to the shell I'm starting in my script. Anyone know what I'm doing wrong? TIA. -- Charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590

2 1

RE: [suse-autoinstall] SCR problem
by Suffin, Charles 22 Dec '04

22 Dec '04

Brian, I'm not sure what is wrong with your script, but you can get access to a shell window during any of the three script environments (pre, chroot, post) by putting the following line at the top of your script: exec /bin/bash -x This pauses the autoinstall dead in its tracks until you kill the shell... Even though I have not figured out yet how to interact with *that* shell when it starts, what you *can* do is hit ctl-alt-F2 to get to a shell that's already running on ttyN. From there, you can run each of your commands manually and find out what's wrong. Hope that helps. -- Charlie -----Original Message----- From: Brian Corriveau [mailto:bcorriveau@cray.com] Sent: Monday, December 20, 2004 5:25 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] SCR problem How do I run this from the bash shell? (from clients/inst_finish.ycp) SCR::Write (.target.string, "/var/lib/YaST2/runme_at_boot", "") I want to try running this manually so I can understand why it is failing during autoinstallation. This is failing for my target, as are a couple other SCR commands. I can run the command from a chroot post-script to get the help output with: chroot /mnt /usr/lib/YaST2/servers/scr -h So the command seems to run somewhat, but for the runme_at_boot creation I get the Y2log error: 2004-12-18 02:34:13 <0> linux(3172) [liby2] Y2ProgramComponent.cc(launchExternall Program):292 Going to execute /usr/lib/YaST2/servers/scr with chroot /mnt 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(Scanner):107 Scanner settting builtinTable to 0x507d10 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(initTables):146 m_globalTT able 0x1776bb0 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(initTables):158 m_localTaable 0x52fd60 2004-12-18 02:34:13 <0> linux(519) [libycp] parser.yy(yyparse):284 ------------------------------------------- accept ------------------------------ -------------- 2004-12-18 02:34:13 <0> linux(519) [liby2] Y2ProgramComponent.cc(sendToExternal)) :377 Error writing to external program /usr/lib/YaST2/servers/scr: Couldn't sendd (`Write (.target.string, "/var/lib/YaST2/runme_at_boot", "")) (Broken pipe) 2004-12-18 02:34:13 <3> linux(519) [liby2] Y2ProgramComponent.cc(receiveFromExtee rnal):343 External program /usr/lib/YaST2/servers/scr died unexpectedly 2004-12-18 02:34:13 <3> linux(519) [Interpreter] scr:240 SCR::Write() did not reeturn a boolean So I'd like to understand what is wrong with my target's environment that this would fail. thanks, Brian -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

YaST.firstboot question
by Michael Shannon 21 Dec '04

21 Dec '04

For a while we thought using DHCP with autoyast sounded like a good idea, but then we decided not to go that direction. I would really like YaST.firstboot to run the lan module on first boot, I've read through the scripts and its not very obvious to me how to make this happen. I've completely removed the lan configuration from autoyast.xml hoping that would force YaST.firstboot to run the lan module, but my efforts yielded very little fruit :( It looks like there might be something in the install.inf file that is telling YaST that the interface has been configured, is there a way around this? Thanks, -m

1 0

SLES9 and modems
by Patrick B. O'Brien 20 Dec '04

20 Dec '04

What SLES9 util would I run to config my modem in my Dell PC? TIA.

1 0

Bug: network setup and Myrinet
by Karsten Petersen 19 Dec '04

19 Dec '04

Hi, I have a problem with SuSE 9.1 autoyast, a static network setup and Myrinet host adapters which are in the machines. My autoyast files have a network configuration that looks like this: <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>192.168.21.127</broadcast> <device>eth-0</device> <ipaddr>192.168.21.102</ipaddr> <netmask>255.255.255.224</netmask> <network>192.168.21.96</network> <startmode>onboot</startmode> </interface> </interfaces> There is no <modules> declaration in <networking>, just the above <interfaces>, <dns> and <routing>. But if a machine is installed with this configuration, the network setup ends up totally wrong: Autoyast assigns the given IP to the Myrinet interface - which is senseless because there is no driver loaded and Myrinet does not need an IP to work. This is because the hwinfo tool detects the Myrinet card and yast declares it to be a "netcard" named "myri". When autoyast goes to use the given interface setup, it calls SelectHW() which returns the first netcard: myri. Neither of the following attempts worked: - add another <interface> declaration in front of the eth-0 one - add a <modules> section - rename <device> to eth0 Fixing this in a postinstall script failed because the ifcfg-* files are only created afterwards. So now I am trying a postinstall script that patches the file /usr/share/YaST2/modules/NetworkDevices.ycp and runs ycpc afterwards. :-/ Does anyone have a better idea? Nevertheless I believe this is a bug - autoyast should just ignore the Myrinet card. A related problem is, that it seems impossible to exactly declare which device an interface configuration is for, without giving the MAC address in <device>. This is very impractical for large amounts of mostly identical machines. :-( It would be good if I could tell autoyast something like this: <interface> <device>eth0</device> ... </interface> And autoyast would then use this declaration for the kernels eth0 device, no matter what other devices are around or what MAC this device has. Best wishes Karsten Petersen -- Karsten Petersen email: petersen(a)megware.de HPC System Engineer phone: +49 - 3722 - 528 43 MEGWARE Computer GmbH home: www.megware.de Chemnitz / Germany

2 1

missing device nodes
by Rajiv Aaron Manglani 17 Dec '04

17 Dec '04

hello. we are seeing a problem with autoyast on 9.1 where device entries for hard drive partitions are missing. i mentioned it briefly in a pervious post: http://lists2.suse.com/archive/suse-autoinstall/2004-Nov/0050.html as an example of the problem, autoyast is going to install onto hda using hda1 as boot, hda2 as swap, hda3 as root. when trying to format the file systems, an error will come up saying that it could not format. we have found that the device entry for just that partition is missing, but `fdisk -l` shows all three partions on the disk. so /dev/hda1 and /dev/hda[3-9] exist, but /dev/hda2 does not. manually creating the device node (eg, `mknod /dev/hda2 b 3 2`) fixes the problem and autoyast can continue. anyone else see this? what can i do to further debug the problem?

1 0

yast-cd-creator and autoinstall on SuSE Linux 9.2
by Pierre Allix 17 Dec '04

17 Dec '04

Hi, I would like to know if we can find yast cd-creator and yast autoinstall on SuSE Linux 9.2 ? Thanks, Pierre

1 0