Re: SUSE LINUX ifconfig - need permanent command

2006-08-02 Thread Rick Troth
Hans ... There is the LSB (Linux Standard Base). There are a lot of things specified in that. Not sure if 'netconfig' is in that lot of things or not. The major distributions existed before LSB. In absense of a standard, and for lack of such tools from the greater Linux community, the distribut

Re: SUSE LINUX ifconfig - need permanent command

2006-08-02 Thread Rick Troth
On Wed, 2 Aug 2006, Jim Vincent wrote: > Mppmmppthpfpp... ugh! Had to take my foot out of my mouth. Yes, I did > know Yast -can- be done, via a VNC connection right? The usual case I get > involved in is when the nic is DOA and I am doing it all via the 3270 > console. I stand humbly corrected

Re: SUSE LINUX ifconfig - need permanent command

2006-08-02 Thread Hans Rempel
ERVER with YaST2 also uses additional cycles and need to be installed/started to be used. Hans -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: August 2, 2006 3:50 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SUSE LINUX ifc

Re: SUSE LINUX ifconfig - need permanent command

2006-08-02 Thread Jim Vincent
Mppmmppthpfpp... ugh! Had to take my foot out of my mouth. Yes, I did know Yast -can- be done, via a VNC connection right? The usual case I get involved in is when the nic is DOA and I am doing it all via the 3270 console. I stand humbly corrected! I've been hanging around Troth too long ;-)

Re: SUSE LINUX ifconfig - need permanent command

2006-08-02 Thread Rich Smrcina
Why is that 'no dice' on S/390 Linux? I've used YaST alot to make network config changes on Linux on the mainframe. Jim Vincent wrote: Generally one would use yast to make network changes on a Linux server, but no dice on s390 Linux. The way I know works is to update the /etc/sysconfig/netwo

Re: SUSE LINUX ifconfig - need permanent command

2006-08-02 Thread Jim Vincent
Generally one would use yast to make network changes on a Linux server, but no dice on s390 Linux. The way I know works is to update the /etc/sysconfig/network/ifcfg-geth-bus-ccw-0.0. config file with the details you want to make permanent. ( is the nic device address on the guest). I d