public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Problems with ssh-host-config and /var/run directory
Date: Thu, 25 May 2017 21:11:00 -0000	[thread overview]
Message-ID: <cf99f43c-d6da-5660-0a78-c479dbb68ebb@t-online.de> (raw)
In-Reply-To: <59272F87.9050300@faroul.de>

Am 25.05.2017 um 21:24 schrieb Henning Peters:
> Hi,
> 
> I switched from 32bit to 64 bis a week ago, moved "cygwin" to "cygwin32" and
> reinstalled from scratch into a new "cygwin" directory.

I don't think that was a good strategy.  Cygwin does use some registry 
entries pointing to absolute paths, i.e. you cannot just move a cygwin 
installation around and expect it to still work, just like that.  That 
means your 32-bit Cygwin installation is now most likely quite broken, 
and I won't even speculate on the possible havoc running the orphaned 
32-bit tools will cause in the 64-bit install now occupying their place.

Just installing the 64-bit version to a new, aptly named folder 
cygwin64, would have been both simpler, and more likely to work.


--
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-05-25 20:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 20:58 Henning Peters
2017-05-25 21:11 ` Hans-Bernhard Bröker [this message]
2017-05-25 23:04 ` Brian Inglis
2017-05-26  7:51   ` Brian Inglis
     [not found]   ` <59289C75.2020307@faroul.de>
2017-05-27  8:17     ` Brian Inglis

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=cf99f43c-d6da-5660-0a78-c479dbb68ebb@t-online.de \
    --to=hbbroeker@t-online.de \
    --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).