From owner-freebsd-chat@FreeBSD.ORG Tue Nov 25 19:27:34 2003 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35A1616A4CE for ; Tue, 25 Nov 2003 19:27:34 -0800 (PST) Received: from mail.blarg.net (zoot.blarg.net [206.124.128.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1A0B43FB1 for ; Tue, 25 Nov 2003 19:27:30 -0800 (PST) (envelope-from abowhill@blarg.net) Received: from kosmos.my.net (12-230-212-176.client.attbi.com [12.230.212.176]) by mail.blarg.net (Postfix) with ESMTP id 0573133CA3; Tue, 25 Nov 2003 19:26:26 -0800 (PST) Received: from kosmos.my.net (localhost [127.0.0.1]) by kosmos.my.net (8.12.10/8.12.10) with ESMTP id hAPFS1j1040389; Tue, 25 Nov 2003 07:28:01 -0800 (PST) (envelope-from kosmos@kosmos.my.net) Received: (from kosmos@localhost) by kosmos.my.net (8.12.10/8.12.10/Submit) id hAPFS0GN040388; Tue, 25 Nov 2003 07:28:00 -0800 (PST) (envelope-from kosmos) Date: Tue, 25 Nov 2003 07:28:00 -0800 From: Allan Bowhill To: Erik Trulsson Message-ID: <20031125152800.GA40176@kosmos.my.net> Mail-Followup-To: Erik Trulsson , freebsd-chat@freebsd.org References: <20031027200046.33CF516A4DB@hub.freebsd.org> <20031027214510.GA52000@kosmos.mynet> <20031027223648.GC1004@zi025.glhnet.mhn.de> <20031028000708.GA52155@kosmos.mynet> <20031028004319.GF1004@zi025.glhnet.mhn.de> <20031125072702.GG340@freepuppy.bellavista.cz> <20031125064404.GA38625@kosmos.my.net> <20031125193010.GB67289@freepuppy.bellavista.cz> <20031125094426.GA39119@kosmos.my.net> <20031125222426.GA3585@falcon.midgard.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031125222426.GA3585@falcon.midgard.homeip.net> User-Agent: Mutt/1.4.1i X-URL: http://www.blarg.net/~abowhill/ cc: freebsd-chat@freebsd.org Subject: Re: Bug in ports howto question X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2003 03:27:34 -0000 [I brought this message to freebsd-chat, becuase the discussion is off- topic for -ports] On 0, Erik Trulsson wrote: :On Tue, Nov 25, 2003 at 01:44:26AM -0800, Allan Bowhill wrote: :> On 0, Roman Neuhauser wrote: : : :> :> :> > The skill sets are mutually exclusive. :> :> : :> :> : aha. you can't possess skill in both skiing and driving. the skill :> :> : sets are mutually exclusive. eh? :> :> :> :> Yep. Skiiing is not driving, and driving is not skiiing. :> :> They require mutually exclusive skill sets. :> : :> : Perhaps it's just my poor English (ESL speaker here, beware!) but :> : doesn't "exclude" imply "to prevent the other from existing"? At :> : least the online Merriam-Webster would make me believe so. :> :> No. It just means they are separate entities, not dependent on one :> another. You could argue systems administration depends on you ability :> to program. You could also argue it doesn't. My problem is with the :> definition of systems administration. : :Wrong. If two things are mutually exclusive that does mean that you :can have either the one, or the other, but not both at the same time. I am not disagreeing with that. But time is peripheral to the argument. Minus time, skill set A is not skill set B. :I can't imagine any situation in which two skill sets could be mutually :exclusive, since that would mean that knowing one set of skills would :actually prevent you from knowing the other set of skills, which would :be very strange indeed. : :(Knowing how to ski does not prevent you from knowing how to drive, and :knowing how to drive does not prevent from knowing how to ski, thus :they are not mutually exclusive skills.) Knowing one set of skills does not necessarily preclude knowlege of the other. In fact, one often complements the other. But that is ouside the scope of the argument. :What you apparently tried to convey was that the skill sets are :"completely separate", "non-overlapping", or "independent of each :other". None of which is equivalent to "mutually exclusive". The following (from a probablility text at Rice) might suffice for the sake of this question. http://www.ruf.rice.edu/~lane/hyperstat/A132677.html "Two events are mutually exclusive if it is not possible for both of them to occur. For example, if a die is rolled, the event "getting a 1" and the event "getting a 2" are mutually exclusive since it is not possible for the die to be both a one and a two on the same roll. The occurrence of one event "excludes" the possibility of the other event." Can you agree with this? Minus time, you should be able to see that the skill sets of system administration skills and programming are mutually exclusive. The two activities are so distinct, that you cannot do both at the same time. You can be a sysadmin with great programming skills. But when you write code to automate systems administration tasks, you are programming. You can be a programmer with great system administration skills. But when you format a drive, write firewall rules, configure software, monitor services and vendor equipment, etc., you are doing systems administration. : :Here endeth todays English lesson. : I think this problem has more to do with communication than with English. -- Allan Bowhill abowhill@blarg.net Never put off till tomorrow what you can avoid all together.