George H. Yeager wrote:
>
> George:
>
> I have not accomplished this yet (permanently). I have been on RR with SuSE
> 6.0. You just have to set up your IP/Mask/DNS info and go.
Did that using YaST.
> You'll
> eventually need a DHCPCD package (free).
Why do I need the daemon? Don't I just need the client?
> Look around the web to find it.
>
OK - I'll bite. Why did it work flawlessly when I rebooted
several times? Doing the math, the DHCP client said it
got a lease for 1800 minutes, which is 10 hours. That's
about when the whole system collapsed. Why would eth1
(the non-DHCP'd interface) suddenly lose its routing?
When I got to the machine (two reboots later), the dummy
interface had eth0's parameters, eth0 was 0.0.0.0, and
eth1 was OK (192.168.1.254). Total weirdness - never saw
the likes with RedHat's DHCP. OBTW - RedHat's distribution
of Gnome LinuxConf has YaST begging for mercy (and I thought
YaST was cool compared to Red Hat's control-panel).
The DHCP client I was using is the one on the SuSE website.
SuSE makes an awesome workstation, but I can't get it
to route for beans.
Anyway, being the money-grubbing capitalist republican that
I am, I'm going to focus on where the money is, and in the
US,
RedHat's got the ticket. At least I can acknowledge whose
slave I am.
> It is available with good installation instructions.
The one that Lenz pointed me to has excellent instructions.
> I'll see if I can find
> them this evening.
That's ok. Red Hat's working fine. Thanks anyway.
George
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
