From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 119138 invoked by alias); 25 May 2017 20:58:01 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 119118 invoked by uid 89); 25 May 2017 20:58:00 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.0 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=H*M:online, H*Ad:D*t-online.de, H*F:D*t-online.de, ssh-host-config X-HELO: mailout08.t-online.de Received: from mailout08.t-online.de (HELO mailout08.t-online.de) (194.25.134.20) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 25 May 2017 20:57:59 +0000 Received: from fwd19.aul.t-online.de (fwd19.aul.t-online.de [172.20.27.65]) by mailout08.t-online.de (Postfix) with SMTP id 4391E41C8EB4 for ; Thu, 25 May 2017 22:58:00 +0200 (CEST) Received: from [192.168.2.28] (Gh9cJoZOohvsWyQaMFCHNtzIyOPeTiMch0f5y71kiASQuJ38uOs4hhv1iK1N0+Og62@[91.59.24.141]) by fwd19.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1dDzpX-0i37kO0; Thu, 25 May 2017 22:57:59 +0200 Subject: Re: Problems with ssh-host-config and /var/run directory To: cygwin@cygwin.com References: <59272F87.9050300@faroul.de> From: =?UTF-8?Q?Hans-Bernhard_Br=c3=b6ker?= Message-ID: Date: Thu, 25 May 2017 21:11:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <59272F87.9050300@faroul.de> Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-05/txt/msg00419.txt.bz2 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