From owner-freebsd-current@FreeBSD.ORG Sun Apr 24 18:54:54 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3917106566B; Sun, 24 Apr 2011 18:54:54 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 8C22D8FC1B; Sun, 24 Apr 2011 18:54:54 +0000 (UTC) Received: from [127.0.0.1] (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.4/8.14.4) with ESMTP id p3OIsiEm011938; Sun, 24 Apr 2011 12:54:47 -0600 (MDT) (envelope-from scottl@samsco.org) Mime-Version: 1.0 (Apple Message framework v1084) From: Scott Long In-Reply-To: <20110423.183641.41662287.sthaug@nethelp.no> Date: Sun, 24 Apr 2011 12:54:44 -0600 Message-Id: <99424DD0-6ED9-42E8-A3D2-0376D444109A@samsco.org> References: <20110420203754.GM85668@acme.spoerlein.net> <4DAF46F8.9040004@FreeBSD.org> <20110423.183641.41662287.sthaug@nethelp.no> To: "sthaug@nethelp.no" X-Mailer: Apple Mail (2.1084) X-Spam-Status: No, score=-50.0 required=3.8 tests=ALL_TRUSTED,HTML_MESSAGE, T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on pooker.samsco.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-current@freebsd.org" , "mav@freebsd.org" Subject: Re: Switch from legacy ata(4) to CAM-based ATA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2011 18:54:54 -0000 On Apr 23, 2011, at 10:36 AM, sthaug@nethelp.no wrote: >> In other words, "ada" isn't the problem here, it's that we all still = think in terms of the 1980's when systems didn't autoconfigure and = device names were important hints to system functionality. That time = has thankfully passed, and it's time for us to catch up. >=20 > If this is important for disk type devices, why not also for network > type devices? Why don't we all use ethX like Linux does? I'd really like to see that as well, but there were strong disagreements = when I floated the idea 4 years ago. > Personally I *like* knowing something about the underlying type of > device and technology - but I can definitely see both sides of the > argument here. >=20 Indeed, there's nothing wrong with preserving access to the system = details for the use of administration, troubleshooting, and even mere = geeky knowledge. This isn't about taking power away from the = superusers, it's about making the system smart enough to handle common = situations reliably. I'm sure that there some among us who pine for the = good old days of manually configuring and linking a kernel, but it's = hard to argue that an auto-configured kernel isn't pretty darn = convenient most of the time. What I'm proposing is just the next step = in that process. Scott=