From owner-freebsd-current Sat Oct 24 16:38:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15833 for freebsd-current-outgoing; Sat, 24 Oct 1998 16:38:22 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from luomat.peak.org (port-56-ts2-gnv.da.fdt.net [209.212.132.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15828 for ; Sat, 24 Oct 1998 16:38:20 -0700 (PDT) (envelope-from luomat@luomat.peak.org) Message-Id: <199810242337.TAA01175@ocalhost> Content-Type: text/plain MIME-Version: 1.0 In-Reply-To: From: Timothy J Luoma Date: Sat, 24 Oct 1998 19:37:40 -0400 To: freebsd-current@FreeBSD.ORG Subject: Re: How To Fixup A New Install -- Trivial Importance References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Author: User MAT Date: Sat, 24 Oct 1998 13:47:11 +0000 (GMT) ID: > I was very impressed that this worked so easily (you have to run > the Windows Cable-Modem software first to get the IP/gateway/DNS > via DHCP, once you have theses values, the cable-modem doesn't > care). FWIW Comcast@Home gave me the information I needed to install w/out my having to run Windows. @Home Unix customers are wise to report themselves as Mac users -- Mac's DHCP apparently doesn't work well w/ @Home, so if they ever need to change your settings, they supposedly inform Mac folks ahead of time. (@Home's policy is basically that the IP won't change unless they have to renumber your entire node, so it is "static" for 99% of the people). But there's a list for Unix@Home folks if anyone is interested in more of that... TjL, who had a cable modem for a year, then moved to a new place where they don't exist yet :-(((((( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message