From owner-freebsd-current@FreeBSD.ORG Fri Oct 28 23:37:35 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 3FA01106564A for ; Fri, 28 Oct 2011 23:37:35 +0000 (UTC) (envelope-from ken@mthelicon.com) Received: from hercules.mthelicon.com (unknown [IPv6:2001:49f0:2023::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0A3B88FC0A for ; Fri, 28 Oct 2011 23:37:34 +0000 (UTC) Received: from PortaPegIII (hydra.fletchermoorland.co.uk [78.33.209.59]) (authenticated bits=0) by hercules.mthelicon.com (8.14.5/8.14.3) with ESMTP id p9SNb3qQ017425; Fri, 28 Oct 2011 23:37:03 GMT (envelope-from ken@mthelicon.com) From: "Pegasus Mc Cleaft" To: "'Lyndon Nerenberg \(VE6BBM/VE7TFX\)'" , , References: <4EAB2D38.4040200@feral.com> In-Reply-To: Date: Sat, 29 Oct 2011 00:37:04 +0100 Message-ID: <003101cc95ca$80ec8b60$82c5a220$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcyVwzP4Ifu52GYTQ/ixpGafLGo9RQABRrEQ Content-Language: en-gb X-Spam-Status: No, score=0.9 required=15.0 tests=BAYES_00,DOS_OUTLOOK_TO_MX, FSL_HELO_NON_FQDN_1 autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on hercules.mthelicon.com Cc: 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: Fri, 28 Oct 2011 23:37:35 -0000 >> The linux hdparm program is so paranoid about this that you have to = use=20 >> extra arguments like "--yes-really-destroy-my-disk-drive" to do this. > >I concur. Loudly. The ability to brick your hardware is just too >large to not make people go through the "I tell you three times" >dance. It's not like people will do this often enough that the >pain will be fatal. And if it is, they ought to be bright enough to >know how to automate the process. > >--lyndon Hi Lyndon and group,=20 I tend to disagree that there should be such argument antics employed to protect an operation such as this. Being root should be the = only 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 = not added on the command line, however.=20 To me, the only difference between borking a drive because of bad firmware and typing "rm -rf *" from root is about =A340. You still lose = at least a day rebuilding/restoring everything. IMHO Peg