public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [cygwin] Re: Mandatory ASLR breaks Cygwin - Windows 10
Date: Tue, 25 Aug 2020 15:49:20 -0600	[thread overview]
Message-ID: <c4363555-3a68-0972-17e7-e30dfa473023@SystematicSw.ab.ca> (raw)
In-Reply-To: <bd42ad69-6955-801c-5708-8847abcef71a@cs.umass.edu>

On 2020-08-25 09:56, Eliot Moss wrote:
> Meanwhile, WSL version 2 runs under a hypervisor and thus implements its own
> fork directly, giving speeds more like Linux (a _lot_ faster). Hence it is
> clear that the Windows OS team do not intend to support fork - they'd just say
> "use a hypervisor".

Good advice which I took, and find running a lightweight distro in a VM gets
near native performance, without worrying about what MS "Linux" or Windows does
or supports, plus you can use multiple processes, with X and all services,
without limits other than those applied to the VM:

"Those who do not understand Unix are condemned to reinvent it, poorly."
	-- Henry Spencer

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]

      reply	other threads:[~2020-08-25 21:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 14:16 Alexandria Cortez
2020-08-25 14:34 ` Eliot Moss
2020-08-25 14:36   ` Alexandria Cortez
2020-08-25 15:13     ` Brian Inglis
2020-08-25 15:25       ` [cygwin] " Jason Pyeron
2020-08-25 15:56         ` Eliot Moss
2020-08-25 21:49           ` Brian Inglis [this message]

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=c4363555-3a68-0972-17e7-e30dfa473023@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).