public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "L. A. Walsh" <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: Windows Subsystem for Linux starts to compete with Cygwin?
Date: Sat, 29 Oct 2016 17:16:00 -0000	[thread overview]
Message-ID: <58143E02.6010507@tlinx.org> (raw)
In-Reply-To: <0b3de073-1be5-248b-19b3-26827947607e@yandex.ru>

Evgeny Grin wrote:
> A lot of?
> I don't know many... correction.. any GNU/Linux tools that works badly
> with \n newlines.
---
	All the tools in linux and current MacOS use
1 character to indicate end of line.  It is only windows that has
a problem.
 
>>> Is Cygwin still better for something?
---
	The GUI that you said was broken on WSL...
	Also, does WSL work in SafeMode?  Nope.
	Cygwin does.  Does WSL work in PE mode?  Nope.
	Cygwin does.  Damn, WSL is a pretty lame solution at this
point.


>> Did they fixed the user mappings?
> 
> I don't know as I didn't have any problem with it.
---
	Do you have a domain?  Oh, that's right MS, doesn't
support users having domains, and unless you have a Professional
version of Windows, they crippled the client to not work w/Domains.

	So does your copy of windows work in a domain? (a home
domain, BTW -- we aren't talking businesses).


> Do you mean, that Windows itself is a problem?
> Or version 10 of Windows is a problem? Anyway, all Windows users will
> use Windows 10 (or successors) sooner or later.
> So it's only the beginning of the story.
---
	You haven't been keeping in touch w/linux lately.
It's really that all users will use "systemd" -- oh... wait,
that's a reimplementation of the windows "services" daemon.  So,
you might be right... ;-)

--
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

  parent reply	other threads:[~2016-10-29  6:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26 22:59 Evgeny Grin
2016-10-27  1:04 ` Duncan Roe
2016-10-27 14:46   ` Evgeny Grin
2016-10-27 17:10   ` Erik Soderquist
2016-10-27 14:42 ` Andrey Repin
2016-10-27 15:32   ` Evgeny Grin
2016-10-29  6:24     ` Andrey Repin
2016-10-29 17:16     ` L. A. Walsh [this message]
2016-10-29 18:18       ` Brian Inglis
2016-10-31 14:52       ` Andrey Repin

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=58143E02.6010507@tlinx.org \
    --to=cygwin@tlinx.org \
    --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).