Date: Sat, 29 Oct 2011 00:37:04 +0100 From: "Pegasus Mc Cleaft" <ken@mthelicon.com> To: "'Lyndon Nerenberg \(VE6BBM/VE7TFX\)'" <lyndon@orthanc.ca>, <mj@feral.com>, <freebsd-current@freebsd.org> Subject: RE: Adding disk firmware programming capability to camcontrol Message-ID: <003101cc95ca$80ec8b60$82c5a220$@com> In-Reply-To: <a6ce5a46de726137f158b145db65f691@orthanc.ca> References: <4EAB2D38.4040200@feral.com> <a6ce5a46de726137f158b145db65f691@orthanc.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
>> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003101cc95ca$80ec8b60$82c5a220$>