I stripped the /etc/modules.conf down to one line too.. alias eth0 lcs
...it had a bunch of alias statements that did not apply to me... and I thought having these multiple statements in modules.conf was a problem in my earlier RH installs...but I could be mistaken...?? Dave > Jammie, > > The "read_conf" command was brain-fade on my part. I should not have > included it. > > If you did not do this: > echo chandev=lcs0,0x0202,0x0203,0,1 > /proc/chandev > then I don't know why the "ifup eth0" command did not generate any error > messages. Writing something to /proc/chandev will allow you to dynamically > define your device and start using it. One other thing that I forgot > (sorry) was to do the insmod for your lcs module. _Then_ do the ifup eth0, > followed by an ifconfig to see if it came online. If it fails, a "dmesg | > tail" might provide some information as to why it didn't. > > I would say that until you can dynamically get your eth0 working, that you > should leave zipl.conf alone. Then, you can use vi to update it correctly. > That is, unless you want to learn some ed/sed commands. :( > > Finally, the "HOST=s390.rh-kfbs.com:eth0:172.16.1.164:1500" stuff is _not_ > something you want to put into /etc/zipl.conf (or anywhere else). That is > an installation script parameter only. >
