This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: Thread TITTTL'd! <cygwin-talk at cygwin dot com>
- Date: Thu, 12 Oct 2006 11:28:24 -0400
- Subject: Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1
- References: <20061012145226.GG8323@calimero.vinschen.de> <026401c6ee0f$3ad3b170$a501a8c0@CAM.ARTIMI.COM> <20061012151603.GH8323@calimero.vinschen.de>
- Reply-to: cygwin-talk at cygwin dot com
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
On Thu, Oct 12, 2006 at 05:16:03PM +0200, Corinna Vinschen wrote:
>On Oct 12 16:01, Dave Korn wrote:
>>On 12 October 2006 15:52, Corinna Vinschen wrote:
>>>Naah, scratch that. Creating a mount point for $SYSTEMROOT seems the
>>>better solution.
>>
>>Imagine the fun if someone decided to try and uninstall cygwin by
>>running "rm -rf /" :)
>
>The user is either a non-privileged user, or (s)he will gain some
>interesting new experience in what happens on Linux in the same
>situation.
I wouldn't be against the concept of augmenting Cygwin to allow a
read-only mount. If the systemroot was mounted read-only then
"rm -rf /" wouldn't work unless the user tried hard to work around
it.
As a meta-issue, I really think that people are getting a little too
quick on the TITTTL trigger. There's nothing talkish about speculating
end-user issues.
cgf