public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Felipe Vieira <fmv1992@gmail.com>
To: cygwin@cygwin.com
Subject: /bin/ gets deleted on error
Date: Thu, 13 Apr 2017 13:59:00 -0000	[thread overview]
Message-ID: <CAMZ6u3sxGACjd12x+_p75fX_dMDYLLj6KXOysq2T_iH6hoHNDw@mail.gmail.com> (raw)

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'.

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.

Nevertheless thanks for the great software. If it were not for you
guys I don't know how I could cope with Windows.

Best,

Felipe Vieira.

--
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 13:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13 13:59 Felipe Vieira [this message]
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
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=CAMZ6u3sxGACjd12x+_p75fX_dMDYLLj6KXOysq2T_iH6hoHNDw@mail.gmail.com \
    --to=fmv1992@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).