From owner-freebsd-questions@FreeBSD.ORG Sun Apr 1 22:50:44 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B339A106566C for ; Sun, 1 Apr 2012 22:50:44 +0000 (UTC) (envelope-from freebsd-questions@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 6071F8FC0A for ; Sun, 1 Apr 2012 22:50:44 +0000 (UTC) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.182]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.unitedinsong.com.au (Postfix) with ESMTPSA id EDADD5C22 for ; Mon, 2 Apr 2012 09:04:18 +1000 (EST) Message-ID: <4F78DBC2.5060800@herveybayaustralia.com.au> Date: Mon, 02 Apr 2012 08:50:42 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111109 Thunderbird/7.0.1 MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4F7798D0.7000404@a1poweruser.com> <4F77A360.9080601@herveybayaustralia.com.au> <4F77A6CA.50406@a1poweruser.com> <20120401143541.4d7d186f@gumby.homeunix.com> <4F786796.5010903@FreeBSD.org> <20120401105933.4c6a9d77@scorpio> <4F7873E8.4030106@herveybayaustralia.com.au> <20120401122947.15e715a5@scorpio> <4F78D492.3050605@herveybayaustralia.com.au> <20120401184135.317e52eb@scorpio> In-Reply-To: <20120401184135.317e52eb@scorpio> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Access to Time Warner cable network X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Apr 2012 22:50:44 -0000 On 04/02/12 08:41, Jerry wrote: > On Mon, 02 Apr 2012 08:20:02 +1000 > Da Rock articulated: > >> Both networking in FreeBSD _and_ Winblows can be difficult at times. >> My point is that Winblows is not some magical fairy that can make >> everything better. It doesn't. It quite often gets it wrong, and when >> it does its a b**ch to fix- especially now with the newer versions; >> it just just gets harder and harder to fix. And (forget your phd) >> considering both myself and the other tech have _Microsoft_ certs and >> I topped in networking in that same certification thats saying >> something, do you think? > A degree != practical knowledge. The only thing you are telling me is > that you are a failure with no practical knowledge of what you are > doing. You display an obvious disdain for the OS, so how can you even > pretend to be objective? That is like me going on a jury with a > predisposed hated of the defendant. Guess how that is going to turn > out. It is like me putting together model planes. I hate model planes > and end up destroying them and conversely blaming the destruction on > the planes. It is exactly what you are doing. > > You obviously are a failure at networking in a Microsoft environment, > so go back to whatever it is that you are semi capable of doing, which > will also save your employer monies spent on time wasted. Unless of > course this happens to be your own unit, in which case run down the > block and find a 12 year old and have him/her fix it for you. > Given that the other tech in question asked me to help him, and he is a Winblows nut like yourself, I think this premise can be dismissed out of hand. I won't even bother to qualify the rest, I wouldn't want to ruin your delusion.