5 ms·
On Wed, 2010-04-07 at 14:12 +0000, Thomas Krause wrote: > The problem is, that you don't know this script is > dangerous before you executed it. Then you
by moe 17y ago
On Wed, 2010-04-07 at 14:12 +0000, Thomas Krause wrote:
> The problem is, that you don't know this script is
> dangerous before you executed it.
Then you should not execute it.
Scott
--
Scott James Remnant
<email address hidden>
Brilliant. Exactly what you want to hear when a seemingly innocent vendor init-script just erased your harddrive.
- noonespecial 17y agoA few comments down is a particularly rich response to this: So, just to clarify that: What you are basically saying is that the manpage stating > start JOB... > Requests that the named jobs be started. The status of the jobs will be output to standard output until > they are succesfully running, or in the case of tasks, until they have completed. should in fact be read as: "might either start the job or delete all your data, and we neither check, warn or document regarding this issue anywhere visibly"? Seriously?