DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 491AkiJt3407047 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=dBTSHdGs X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7B56F38449D0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1727779603; bh=temFUDVFPEf5bfGY/kmD8LgyjhBs1hdv7EJs6N+tBO8=; h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=dBTSHdGsLz8fIaShkttr0fvMuj2zsVXEDANg2iogK+XChLv1+iDNwUUhCB58k6y7w Bsbosw1EEKPht9q5M7LK3aaIovzZgjwn+tI13yS5NNgih5532yuh+RCFM7/Z/R2ji5 HX3HViTEYfttV7kpzuQDvPKn1B7Xyj5o3IN8Z+qY= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 5259E38449D0 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 5259E38449D0 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1727779579; cv=none; b=M4LgE4NS0ZJ6j1VaLvjAEtb/0fWpRP6Ae/NUyRolbjbRGpzF+reCWf9jmQv/DrDLO02J3cwrMoqxVzG22y5eTgn7YrelVxq5u6JsGjJ5CTbOpMYs/TnC2oAkaoovtVq39HaxExVJhOS3wdxwS+DNxGg3ixHBoDEE3A7MYlKCsJY= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1727779579; c=relaxed/simple; bh=/PDREC4TKWhtZWjbT2naULuDl6MdfDFmh2T7+QqVves=; h=DKIM-Signature:MIME-Version:From:Date:Message-ID:Subject:To; b=H9KIrzd5lWf5OB/tEhvCogMp08coSX4qzR5m3OLy6eBOmoDoKcNT/6fBe8+YYs8Zyh6Bstgkowp2GuBkrGydlUZwLmkmL2qMSrf/rMs68cW/bSDT/0nkbkI2Z9XEYwTSr7KmL1BRDw6UnB46ixVp6doQjK3NK2s4SA+7jjdU2dM= ARC-Authentication-Results: i=1; server2.sourceware.org X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727779576; x=1728384376; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=/PDREC4TKWhtZWjbT2naULuDl6MdfDFmh2T7+QqVves=; b=kQPynTbyZ9X59XSqD3D6cnq2Zy5yO5ctQIorSFaP/34hjmTWBqglqft88DaxJWT2e1 QKTCEMcVqvQ0AZv5ETYYyKXsRtihnKggN2mN2ANz04Moc76wmcNSZgBu5FdUtqWJJsio V7aznsQPe+X05+SijreApCZdJpeKKz6WlPSiGEkCM+3GyObuJ1D2+OA6qCk4yEu/Qrat YqUqwKKYBL2ewoJAYEkgHe4W3/ne5gaYqnr6nJyUtyjTojBxLjzYJ+NsT8BbDJ+M+HsG lVXKSryBVy/jWoYo8ys40qY+GqGDts0Zb9mCD4+9QllFOX//LLkAqP6uxJ70AMPgKHgR hnhg== X-Gm-Message-State: AOJu0Yz+YZ9S4URBKooDFXPF3AH+A/JTtKyKTKLZWTPD7euAxQp/tHGq Bd5uNKNZFh/uL75eiaMMpz/lmDdiKX7ZF36foK1gEwBEP9WpN2PA+X9w5JCG1XlzVFRYz/8mBKi btwl+KubigZBAhLrh7ETwWPazRWDAUA== X-Google-Smtp-Source: AGHT+IGIoObPSqAcfAiZBLRKczepFqxHwdEWCk3yt1Xt7BGUS1e075GGbhFvAsufe6heqTULYG5PQkVCBR7pmflokR0= X-Received: by 2002:a17:90b:ed3:b0:2c9:61ad:dcd9 with SMTP id 98e67ed59e1d1-2e0b8ea881cmr16998734a91.27.1727779575766; Tue, 01 Oct 2024 03:46:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 1 Oct 2024 12:45:39 +0200 Message-ID: Subject: Re: [EXTERNAL] Re: Cygwin 3.6 x86/32bit builds for Windows 10/ARM64 x86 emulation? To: "cygwin AT cygwin DOT com" X-Spam-Status: No, score=-0.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: Mark Liam Brown via Cygwin Reply-To: Mark Liam Brown Content-Type: text/plain; charset="utf-8" Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 491AkiJt3407047 On Sun, Sep 29, 2024 at 10:12 AM Radek Barton wrote: > > Hello Mark. > > I am working on Cygwin/MSYS2 Arm64 port though this is something that could not be > delivered in matter of months. Can you please describe your use/business case more > in detail to help up understand the priorities? Why is MSYS2 32bit or, e.g. WSL, not > working for you? WSL has a couple of problems for us: - WSL is far too big (many GB), Cygwin's core parts (cygwin1.dll) is small (10MB, full useable cygwin can be reduced to 40MB) - WSL cannot be deployed as part of a product, i.e. Cygwin can be bundled with a product or project, WSL is completely independent - WSL consumes lots of main memory even if not in use, Cygwin is just another Windows DLL - WSL requires separate admin skills, so it is much more expensive for an IT department - WSL is actually a VM with an OS, so it generates CVE which needs to be handled - WSL apps cannot communicate with Windows apps - WSL is buggy. The 9p filesystem network provider keeps crashing for us if you try to access SMB or NFS shares - WSL is not stable for end-user systems. It needs to be bootet, you need to wait until its finished booting, and if you don't shut it down it will corrupt its own filesystem. Permanent headaches with this damn thing Compare this to Cygwin, which is just another Windows DLL, fast and easy to deploy and use, and the Windows admins are not permanently angry about it Mark -- IT Infrastructure Consultant Windows, Linux -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple