public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: /bin/ gets deleted on error
Date: Thu, 13 Apr 2017 15:47:00 -0000	[thread overview]
Message-ID: <7d4285f6-f408-ebf0-f61c-e2c9a667b646@gmail.com> (raw)
In-Reply-To: <3aaa073a-efe6-1a06-047f-dd6ec144ce8e@gmail.com>

Decrypted message -

On 4/13/2017 10:02 AM, cyg Simple wrote:
> On 4/13/2017 9:29 AM, Marco Atzeri wrote:
>>
>>
>> On 13/04/2017 15:13, Felipe Vieira wrote:
>>> Dear cygwin mailing list,
>>>
>>> For the second time this week my /bin/ folder gets obliterated on an
>>> error during normal usage. It is equivalent of doing the infamous "rm
>>> -rf  /bin" .
>>>
>>> 1) I would like to know if there is a log for cygwin somewhere so I
>>> can be more useful in specifying what happened.
>>>
>>> 2) My 'specs' are: windows 7 64 bits with cygwin64 . I wonder if
>>> cygwin64 is considered 'stable'.
>>
>> extremely stable
>>
> 
> Yes, all that I use.
> 
>>
>>> From what I recall the terminal was spamming messages containing the
>>> words "fork" , "-1" and some others which I don't recall. And what I
>>> did was trying to run a normal zsh script.
>>>
>>> I am not able to tell exactly what I did on both occasions to trigger
>>> this behavior.
>>
>> any history file on your home directory ?
>>
> 
> Don't forget to check the BLODA on your system, e.g. virus protection
> software.
> 

-- 
cyg Simple

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2017-04-13 14:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 13:59 Felipe Vieira
2017-04-13 14:02 ` Adam Dinwoodie
2017-04-13 14:03 ` Marco Atzeri
2017-04-13 14:24   ` cyg Simple
2017-04-13 15:47     ` cyg Simple [this message]
2017-04-13 18:43 ` L A Walsh
2017-04-13 18:48   ` Dan Kegel
2017-04-13 23:00     ` Brian Inglis
2017-04-14 15:49       ` cyg Simple
2017-04-15  2:45         ` Norton Allen
2017-04-19 15:20 ` Gerrit Haase
2017-04-18 12:37 Felipe Vieira

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=7d4285f6-f408-ebf0-f61c-e2c9a667b646@gmail.com \
    --to=cygsimple@gmail.com \
    --cc=cygwin@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).