From: Charles Wilson <cwilson@ece.gatech.edu>
To: Roland Glenn McIntosh <roland@steeltorch.com>
Cc: cygwin@cygwin.com
Subject: Re: New Install May Have a Bug
Date: Fri, 16 Nov 2001 21:18:00 -0000 [thread overview]
Message-ID: <3C03E1E3.5010500@ece.gatech.edu> (raw)
In-Reply-To: <5.1.0.14.2.20011127133216.064a95d8@lnxmain>
Roland Glenn McIntosh wrote:
> Yes, i too noticed a few peculiarities, however i attributed them to
> a decision to change the default install of cygwin to a more
> minimal approach. Was this the case?
>
> I noticed that with the newer setup I have to specify that I want to
> install OpenSSH, less, and postgresql, possibly a few other things
> that used to be installed by "default"
Right -- because EVERYTHING was installed by default.
> and which I took for
> granted when running setup.exe on a new system. Also - since
> package moratorium is lifted, can cygipc be included, and marked as
> a dependency of postgresql (maybe once the RFC that was posed is
> answered)?
No, cygipc was excluded for other reasons, not just because of the
moratorium.
To work correctly, IPC functionality should be integrated into the core
cgywin. But, it is not possible to assign the copyright to Cygnus/Red
Hat because it was taken from the Linux kernel, originally, and is
covered by a multitude of different owners. (Yes, it's GPL -- but CORE
cygwin components, stuff that goes inside cgywin1.dll, must ALSO be
wholly assigned to Red Hat in addition to the GPLness).
So, we'd have to track down all of those old Linux developers and
convince them to turn over ownership of that portion of code to Red Hat.
Assuming we could find them all, I don't think they'd agree --
because that copyright assignment would also affect the current IPC code
in the LINUX kernel...
Therefore, the cygwin developers have chosen to redo IPC functionality
from scratch, and work is ongoing. This isn't as bad an idea as you
might think: even Ludovic Lange, the guy who originally grabbed the
Linux IPC stuff out of the Linux kernel to create cygipc, agrees that
this is the way to go. CygIPC supports a bare minimum of IPC -- just
enough so that Ludovic's original app worked -- and very little more.
If we start from scratch, we can do it better.
So, why not include cygipc as a non-integral package, like readline or
vim? Simply expediency. If we included it, we would lower the desire
of folks to help us with the "real" implementation. Therefore, we chose
to exclude cygIPC in order to prod folks to help out with the real
cygwin IPC implementation. (Although, cygIPC is not *disallowed* -- you
can still use it if you want, but you've got to get it from an external
site. We're not nazis).
Search the cygwin-developers mailing list for "cygwin daemon".
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
WARNING: multiple messages have this Message-ID
From: Charles Wilson <cwilson@ece.gatech.edu>
To: Roland Glenn McIntosh <roland@steeltorch.com>
Cc: cygwin@cygwin.com
Subject: Re: New Install May Have a Bug
Date: Tue, 27 Nov 2001 10:56:00 -0000 [thread overview]
Message-ID: <3C03E1E3.5010500@ece.gatech.edu> (raw)
Message-ID: <20011127105600.sDXRz9oykV96rkrxZfzBl7Nfg0IDTEBuaghuZ_Y3m_w@z> (raw)
In-Reply-To: <5.1.0.14.2.20011127133216.064a95d8@lnxmain>
Roland Glenn McIntosh wrote:
> Yes, i too noticed a few peculiarities, however i attributed them to
> a decision to change the default install of cygwin to a more
> minimal approach. Was this the case?
>
> I noticed that with the newer setup I have to specify that I want to
> install OpenSSH, less, and postgresql, possibly a few other things
> that used to be installed by "default"
Right -- because EVERYTHING was installed by default.
> and which I took for
> granted when running setup.exe on a new system. Also - since
> package moratorium is lifted, can cygipc be included, and marked as
> a dependency of postgresql (maybe once the RFC that was posed is
> answered)?
No, cygipc was excluded for other reasons, not just because of the
moratorium.
To work correctly, IPC functionality should be integrated into the core
cgywin. But, it is not possible to assign the copyright to Cygnus/Red
Hat because it was taken from the Linux kernel, originally, and is
covered by a multitude of different owners. (Yes, it's GPL -- but CORE
cygwin components, stuff that goes inside cgywin1.dll, must ALSO be
wholly assigned to Red Hat in addition to the GPLness).
So, we'd have to track down all of those old Linux developers and
convince them to turn over ownership of that portion of code to Red Hat.
Assuming we could find them all, I don't think they'd agree --
because that copyright assignment would also affect the current IPC code
in the LINUX kernel...
Therefore, the cygwin developers have chosen to redo IPC functionality
from scratch, and work is ongoing. This isn't as bad an idea as you
might think: even Ludovic Lange, the guy who originally grabbed the
Linux IPC stuff out of the Linux kernel to create cygipc, agrees that
this is the way to go. CygIPC supports a bare minimum of IPC -- just
enough so that Ludovic's original app worked -- and very little more.
If we start from scratch, we can do it better.
So, why not include cygipc as a non-integral package, like readline or
vim? Simply expediency. If we included it, we would lower the desire
of folks to help us with the "real" implementation. Therefore, we chose
to exclude cygIPC in order to prod folks to help out with the real
cygwin IPC implementation. (Although, cygIPC is not *disallowed* -- you
can still use it if you want, but you've got to get it from an external
site. We're not nazis).
Search the cygwin-developers mailing list for "cygwin daemon".
--Chuck
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-11-27 18:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 16:30 Mark Jones
2001-11-16 17:47 ` Charles Wilson
2001-11-16 21:09 ` Stephano Mariani
2001-11-16 22:53 ` Charles Wilson
2001-11-17 1:43 ` Stephano Mariani
2001-11-27 11:38 ` Stephano Mariani
2001-11-27 10:59 ` Charles Wilson
2001-11-17 17:37 ` Zdzislaw Sliwinski
2001-11-27 15:00 ` Zdzislaw Sliwinski
2001-11-27 10:45 ` Stephano Mariani
2001-11-27 10:33 ` Charles Wilson
2001-11-16 17:49 ` Roland Glenn McIntosh
2001-11-16 21:18 ` Charles Wilson [this message]
2001-11-27 10:56 ` Charles Wilson
2001-11-27 10:38 ` Roland Glenn McIntosh
2001-11-27 10:28 ` Mark Jones
2001-11-17 9:29 Mark Jones
2001-11-17 10:51 ` Charles Wilson
2001-11-17 13:44 ` Robert Collins
2001-11-17 15:52 ` Charles Wilson
2001-11-27 14:52 ` Charles Wilson
2001-11-27 14:26 ` Robert Collins
2001-11-27 13:27 ` Charles Wilson
2001-11-27 12:43 ` Mark Jones
2001-11-17 12:30 Gary R Van Sickle
2001-11-27 13:56 ` Gary R Van Sickle
2001-11-17 13:48 Heribert Dahms
2001-11-17 14:54 ` Robert Collins
2001-11-17 15:47 ` Charles Wilson
2001-11-17 17:33 ` Robert Collins
2001-11-27 14:56 ` Robert Collins
2001-11-27 14:51 ` Charles Wilson
2001-11-27 14:42 ` Robert Collins
2001-11-27 14:36 ` Heribert Dahms
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=3C03E1E3.5010500@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.com \
--cc=roland@steeltorch.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).