public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: PATCH: rm MessageBox() (was: Virus that deletes everything under c:/cygwin?)
Date: Mon, 28 Mar 2011 22:30:00 -0000	[thread overview]
Message-ID: <20110328223018.GC12793@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4D90FF7F.9010500@etr-usa.com>

On Mon, Mar 28, 2011 at 03:37:03PM -0600, Warren Young wrote:
>On 3/28/2011 11:07 AM, Dante Allegria wrote:
>> --- On Mon, 3/28/11, Damon Register<damon.w.register@lmco.com>  wrote:
>>
>> No, turns out it was because someone committed this into the nightly build scripts:
>>     rm -rf $(DOES_NOT_EXIST)/*
>>
>> <sigh>  Should cygwin's rm have some built-in safeguards for this? :)
>
>I'd like to propose a patch adding a series of MessageBox()es to 
>Cygwin's unlink(2) syscall to make it ask "Are you sure?" then "Are you 
>really sure?" then "Are you really really double-dog sure?" every time 
>you try to remove a file.
>
>Additionally, I propose adding a patch to rm(1) so that if you give -r, 
>it will activate UAC on Vista/7 systems before doing any work, because 
>everyone loves it when the screen dims and you get yet another dialog 
>you must okay before the system will do anything else.
>
>I will start this work on April 1, if there are no objections.

We look forward to the final product.  Make sure that you sign an
assignment with RedHat since this will be a substantial amount of work.
But, it is obviously valuable work since it brings CygWin further down
the path towards being a true GUI and everyone knows that's a good
thing.

cgf

      reply	other threads:[~2011-03-28 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <468547.38757.qm@web52801.mail.re2.yahoo.com>
2011-03-28 21:37 ` Warren Young
2011-03-28 22:30   ` Christopher Faylor [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110328223018.GC12793@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --cc=cygwin-talk@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).