From: "Tevfik Karagülle" <tevfik@itefix.no>
To: <cygwin-licensing@cygwin.com>
Subject: Re: 1NIWGYC.DLL ??
Date: Fri, 16 Dec 2005 20:50:00 -0000 [thread overview]
Message-ID: <004801c60281$e7b6a020$2602a8c0@itefixb> (raw)
Thanks for your feedback. As long as I understand, what I intend to do does not violate Cygwin
licensing.
On Thu, Dec 15, 2005 at 06:35:24PM -0800, Brian Dessent wrote:
>Just renaming the DLL and registry keys is not enough to avoid
>conflicts with an existing cygwin1.dll. You will also have to modifiy
>the name of the shared memory region and all other shared objects.
Ok. Renaming DLLs, registry references and shared memory name
(cygwin1S4??) would be worth to try then.
>It seems like there is no benefit to this distribution if the user is
>running cygwin anyway. If they are running cygwin then they should just
>use the openssh that comes with cygwin.
I am not so sure about it. I am a dedicated cygwin user since early 90s.
However, I don't want to run an ssh daemon within my cygwin development
environment, where I might try/test many different things. What I want to is
to establish a secure channel to my machine remotely by using ssh daemon,
running its own limited and safe environment for the sake of security.
The same applies for an rsync environment where a crucial operation like a
remote backup can be initiated. I think those special environments require
their own setup.
>If this is really important, wouldn't it be better to work on providing
>a minimal openssh setup via a category in the current cygwin setup.exe?
That would be the best solution if it allows to establish separate environments.
>IMO, repackaging other people's stuff will usually lead to extra work
>for the repackager and confusion for the end user.
I believe that what I do does not complicate user's lives.
On the contrary, I suppose. Cygwin is a great solution.
Too great to be forced into one single environment.
>Cygwin is a community project. You can make changes if you're
>persuasive enough and if you have the proper skills.
My contribution (!) is next to nothing in comparison to the work cygwin
developers do for the cygwin development. I just try to add some more
convenience. That's all :-))
Best regards
Tev
next reply other threads:[~2005-12-16 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 20:50 Tevfik Karagülle [this message]
2005-12-18 17:10 ` Reini Urban
2005-12-18 19:01 ` Christopher Faylor
-- strict thread matches above, loose matches on Subject: below --
2005-12-19 12:20 Tevfik Karagülle
2005-12-16 2:19 Tevfik Karagülle
2005-12-16 2:57 ` Brian Dessent
2005-12-16 3:20 ` Christopher Faylor
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='004801c60281$e7b6a020$2602a8c0@itefixb' \
--to=tevfik@itefix.no \
--cc=cygwin-licensing@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).