From owner-freebsd-current@FreeBSD.ORG Sat Oct 29 00:39:13 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 2D9F91065672 for ; Sat, 29 Oct 2011 00:39:13 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id E36A68FC16 for ; Sat, 29 Oct 2011 00:39:12 +0000 (UTC) Received: by ggnq2 with SMTP id q2so5482689ggn.13 for ; Fri, 28 Oct 2011 17:39:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=cUYfdUpqHq03DD20sJkWyJ1JmTDcC/xgU6MVunMjQek=; b=L4BZztUS9DiSZ13F5vLVKSFsj3Qhf0eOja5wHL9FEWdmKemiUQ693MZRJ9eFFIf54/ NCjuLrSh4xLiHvoMqYlT38l6SCj+7XqlAqcI0lUZRsy1+lp3Yq6JSz6jqTMKcTrRKia8 SJmwrSD7zSnTjw0Zc18UgTXwon1hiH0D22M/Q= MIME-Version: 1.0 Received: by 10.182.7.10 with SMTP id f10mr1101942oba.56.1319848752108; Fri, 28 Oct 2011 17:39:12 -0700 (PDT) Received: by 10.182.122.33 with HTTP; Fri, 28 Oct 2011 17:39:12 -0700 (PDT) In-Reply-To: <003101cc95ca$80ec8b60$82c5a220$@com> References: <4EAB2D38.4040200@feral.com> <003101cc95ca$80ec8b60$82c5a220$@com> Date: Fri, 28 Oct 2011 17:39:12 -0700 Message-ID: From: Garrett Cooper To: Pegasus Mc Cleaft Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: mj@feral.com, freebsd-current@freebsd.org, "Lyndon Nerenberg \(VE6BBM/VE7TFX\)" Subject: Re: Adding disk firmware programming capability to camcontrol 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: Sat, 29 Oct 2011 00:39:13 -0000 On Fri, Oct 28, 2011 at 4:37 PM, Pegasus Mc Cleaft wrot= e: >>> The linux hdparm program is so paranoid about this that you have to use >>> extra arguments like "--yes-really-destroy-my-disk-drive" to do this. >> >>I concur. Loudly. =A0The ability to brick your hardware is just too >>large to not make people go through the "I tell you three times" >>dance. =A0It's not like people will do this often enough that the >>pain will be fatal. =A0And if it is, they ought to be bright enough to >>know how to automate the process. >> >>--lyndon > > Hi Lyndon and group, > > =A0 =A0 =A0 =A0I tend to disagree that there should be such argument anti= cs > employed to protect an operation such as this. Being root should be the o= nly > protection needed (of course, that's only my opinion). I don=92t want to = have > to look up in a man page what magic token I need to add to prove to the > utility that I understand the consequences of what I am about to do. I > personally wouldn't mind a simple "Are you sure?" if the magic token is n= ot > added on the command line, however. > > =A0 =A0 =A0 =A0To me, the only difference between borking a drive because= of bad > firmware and typing "rm -rf *" from root is about =A340. =A0You still los= e at > least a day rebuilding/restoring everything. Unfortunately not backs up their systems on a regular basis. Having an interactive prompt with a loud warning like many vendor tools provide today with a non-interactive override option is sufficient. That being said, camcontrol doesn't understand the concept of interactive vs non-interactive use, so it seems like its design would need to be redone if you go this route. Thanks, -Garrett