From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.135]) by sourceware.org (Postfix) with ESMTPS id AE90E3858002 for ; Mon, 2 Nov 2020 09:13:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org AE90E3858002 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cygwin.com Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=corinna-cygwin@cygwin.com Received: from calimero.vinschen.de ([24.134.7.25]) by mrelayeu.kundenserver.de (mreue011 [212.227.15.167]) with ESMTPSA (Nemesis) id 1N63mC-1kJx1A10X2-016Mfh for ; Mon, 02 Nov 2020 10:13:08 +0100 Received: by calimero.vinschen.de (Postfix, from userid 500) id C0896A80DDC; Mon, 2 Nov 2020 10:13:07 +0100 (CET) Date: Mon, 2 Nov 2020 10:13:07 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Cygwin-64 on W10-64 : the only game in town? Message-ID: <20201102091307.GA33165@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-Provags-ID: V03:K1:I20NdMUJDErWXy9eB3tdaukQpgiqxdIS+b81lhgDtqmPUsRzAAk 6HeaSqMXCQh5CpQzpcdTDaDgq+0SJzSyEdujMNNO2m9U+lGVBgB6ojCv5cVQcwHsyCFD0eI DP0VzSZDcIyO20ZWfAC47CG2kKQ+CqSQx2+VI5Sn64CS9h9IICL2qU9Zq0YYq6r9dKnrQcg m8n6YWc28IK86k1cpkSCg== X-UI-Out-Filterresults: notjunk:1;V03:K0:OQl4TeqfGHs=:AKbmazlUY78th9HgSt8P6o /TwqlnhQ+dSt3BEulJ4Mpjkat/I5b870XzrJ3RERidjZVg5GBtVD3M9haBhzVoGJO1WJ/6FO6 fSsinK+5V8/bKQ5Lm6fKHjOK3SwUCzMGWBItYDbqhg4MxdfQAlIoBYg3u9xuqp+9/MlEfbhvF AuYnX7SzbJgI9QG77oOKGBo43libmd/u7S+GRiR7hkDr8fBIbIhuk2xwPd11t4e+suVKCVR1k fgM9wbI8rtcG7hyEQ3AWzJqNjzuAIipIW3p7g9iDFlhyFq0yqP60y2L1APBbYboFPhyt9eJ2k oU9IZQmmmduou8KeZkBqLsGgxMSwV1xwpKSVmhAjUm7qe2xY1slvZvKhcksQrrQ9Fx8RO7u62 Ht2mIFwLViFDPgsO/VIF3tT0y5sxTw0aJndc+9S69n2zQTKyl4lO3kIoBJ43W+wZ6mKzALxOX m5HyBdJbYw== X-Spam-Status: No, score=-100.9 required=5.0 tests=BAYES_00, GOOD_FROM_CORINNA_CYGWIN, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NEUTRAL, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Nov 2020 09:13:11 -0000 On Nov 1 08:49, Fergus Daly via Cygwin wrote: > With W7 no longer supported, W10-32 supported but no longer provided > on new machines (Microsoft states that, "Beginning with Windows 10, > version 2004, all new Windows 10 systems will be required to use > 64-bit builds and Microsoft will no longer release 32-bit builds for > OEM distribution .. the weaker version of Windows 10 has several > limitations, like capping out at 3.2GB of RAM and less stringent > security measures") and the functionality of Cygwin-32 significantly > downplayed on Cygwin's own Home page, that really does leave Cygwin-64 > on W10-64 on 64-bit hardware as the sole recommended platform. Yes? Cygwin still runs on 32 bit and Windows versions down to Vista. However, since you're asking for a recommendation, some points: - The limited virtual address space of 32 bit processes is getting a big problem for a long time now. The more packages and the more DLLs the distro delivers, the less manageable the situation gets on 32 bit machines. This includes WOW64 on 64 bit. - time_t on 32 bit is 32 bit. The effort to change that is not managable, and it's not worth it, given that usage of 32 bit systems (including WOW64) is at less than 5%, and dropping. - Newer Cygwin features are partially unavailable (usually faked) on older Window versions due to missing API calls. - Cygwin running on Vista is not going away any time soon. The extra code required to support Vista (and W7, fwiw) is just a drop in the bucket, and ripping it out doesn't simplify the code noticably, as for XP. - The same can't be said for 32 bit. There's a lot of code involved, partially assembler code. Getting rid of that code is really an option at one point, what with Windows dropping 32 bit support... - Older Windows versions are increasingly getting insecure with Microsoft stopping updates. - Windows 10 is not exactly privacy-minded... Corinna