From: "Larry W. Virden" <lvirden@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Has anyone collected a summary of cygwin vs Windows 7 64 bit outstanding issues?
Date: Wed, 23 May 2012 13:36:00 -0000 [thread overview]
Message-ID: <CAPRVdgTUuQSSLPs5tWU9eigqtKCmf+Ou5U__dcrH55tvfzzZ4w@mail.gmail.com> (raw)
We are trying to make use of cygwin in several ways on Windows 7
64-bit desktops.
One of the first things we have noticed is that there are a lot of
processes sitting on the desktop that appear to be related to cygwin
that we didn't see previously on 32 bit XP.
For instance, if we open a bash console, perform an ssh to another
machine, do some work, then close the window, the bash and ssh still
seem to be listed when we look at the windows 7 task manager.
So, not wanting to duplicate the fine efforts of those on this list
from the past few years. I googed for cygwin issues windows 7 64 bit,
but the 301,000 results were a bit overwhelming to contemplate reading
through to find unique issues that need to be addressed, and of course
may or may not reflect the state of the current distribution.
So before we start doing weeks of reading of threads, etc. I thought I
would ask whether someone has gathered this information together.
Thank you
--
Tcl - The glue of a new generation. http://wiki.tcl.tk/
Larry W. Virden
http://www.facebook.com/lvirden/
Even if explicitly stated to the contrary, nothing in this posting
should be construed as representing my employer's opinions.
--
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
next reply other threads:[~2012-05-23 13:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 13:36 Larry W. Virden [this message]
2012-05-23 14:16 ` Eliot Moss
2012-05-23 17:19 Bill Ross
2012-05-23 17:42 ` Eliot Moss
2012-05-23 17:54 Bill Ross
2012-05-23 18:47 ` Larry W. Virden
2012-05-23 19:13 Bill Ross
2012-05-23 20:11 ` marco atzeri
2012-05-24 11:25 ` Larry W. Virden
2012-05-26 21:35 ` Christopher Faylor
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=CAPRVdgTUuQSSLPs5tWU9eigqtKCmf+Ou5U__dcrH55tvfzzZ4w@mail.gmail.com \
--to=lvirden@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).