Martha, They're in /etc/init.d. Make sure you take a look at some of the other init scripts headers so you'll know what to put in yours to make sure it winds up in the right place in the startup order. I would have to say, though, that YaST should be able to do all this for you. I find it hard to imagine that SUSE would ship a distribution that couldn't do network startup correctly.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Martha McConaghy Sent: Tuesday, November 23, 2004 1:58 PM To: [EMAIL PROTECTED] Subject: Re: Problems with SLES 9 and guest lan Thanks for the help everyone, especially Neale! A variation of his script did the trick. modprobe qdio modprobe ccwgroup modprobe qeth echo 0.0.4000,0.0.4001,0.0.4002 >/sys/bus/ccwgroup/drivers/qeth/group echo VOSASW > /sys/bus/ccwgroup/drivers/qeth/0.0.4000/portname echo 1 > /sys/bus/ccwgroup/drivers/qeth/0.0.4000/online ifup hsi0 I still don't know why it stopped working, but it is nice to have the network connection again. While you are helping out a Linux neophyte, can you tell me where Suse puts boot scripts? I'm going to have to automate this script so the network connection comes up everytime I reboot. Martha ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
