RE: How about a TWIKI page?

2003-09-25 Thread Dawson, David W
Just wondering, but

Is the current "home of TWiki.Cygwin." at 
<>
what you are looking for?

Or are you looking for something different?

-David.
-
David Dawson
[EMAIL PROTECTED]
703-367-3885


-Original Message-
From: Marco Carnut [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, September 24, 2003 10:47 PM
To: [EMAIL PROTECTED]
Subject: RE: How about a TWIKI page?


Hi folks,

Mark Paulus wrote:

> Perhaps, instead of creating/adding all the issues that
> are coming up to the FAQ, how about running a
> TWIKI application, and linking it to the cygwin home page, 
> and then using that as cygwin's "expert system"?
> 
> Just a thought.

I'm for it. I can even volunteer to host it, or, if someone else has a
better place, install/maintain it.

Although I'm involved in writing a PKI-Enabled version of TWiki, I'd
reccomend using name-and-password for most users. Client certs, although
much more secure, are a pain to use in most browsers.

--Marco "Kiko" Carnut, CISSP
--Tempest Security Technologies -- www.tempest.com.br



--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/


--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



ACE/TAO under Cygwin (was: ORB)

2003-04-05 Thread Dawson, David W
I have been moderately successful in compiling ACE/TAO under Cygwin (Some
problems with cone of the Services, but my CORBA programs interoperate with
our Solaris-based TAO services (and other CORBA clients/servants) fine.

I encountered two problems with a couple of the definitions in the Cygwin
/usr/include files:

1) In limits.h, IOV_MAX is defined as (__INT_MAX__-1) (a *very* large
number).
The other UNIX systems I could examime set it to a much smaller value (like
1024).
The comment says this is the "/* Maximum number of iovcnt in a writev */".
Does Cygwin really support this many? Or is this just a convenient setting?

The reason for the question is that ACE (and TAO) define arrays for the full
number of supported IOV entries, and g++ chokes on an array of size
__INT_MAX__-1

(To set ACE/TAO to compile, I patched this value to 1024)

2) As a convenience (I suppose), math.h has a macro definition for log2.
This is not the case in any other math.h I have been able to examine and
causes a real problem in the development of a platform-independent "log2"
routine.

The problem is that the pre-processor replaces the string "log2" with it's
defined value without regard to context.  This means that while I can write
my own log() function (in my namespace, or course) I cannot write a log2
function -- it won't compile.

(To get ACE/TAO to compile, I patched math.h to remove this define.)

The real questions in this post are:
1) Should there a better value for IOV_MAX in limits.h
2) Should the (as far as I can tell) non-standard define for log2 be removed
(or replaced with a real log2 function?)
3) Should I just go away and be quiet?

Thanks,
-David.

-
David Dawson
[EMAIL PROTECTED]
703-367-3885


-Original Message-
From: Luc Hermitte [mailto:[EMAIL PROTECTED] 
Sent: Saturday, April 05, 2003 8:06 AM
To: [EMAIL PROTECTED]
Subject: Re: ORB


Hello,

* On Fri, Apr 04, 2003 at 05:07:50PM +0200, Vaillant Etienne
<[EMAIL PROTECTED]> wrote:
> I need a ORB for an application under Cygwin. I know Mico and Omniorb 
> but are there other ?

TAO may be -- based on the C++ library ACE.

I am not sure if it has been ported for Cygwin, but it is available on many
different systems -- unices, Windows, etc.

HTH,
-- 
Luc Hermitte

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

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



RE: GPL violations et al

2003-03-25 Thread Dawson, David W
Question (this will lead to my real question, later):

Are the "mirrors" also responsible for providing source for all packages
downloadable by the Cygwin setup.exe?
Most Cygwin packages offer a "Src" tarball available for download along with
the "Bin" package, but there are numerous (significant) exceptions.  For
many
distributed packages, the source is only available in CVS.  Is the "mirror"
obliged to provide (at minimum) a CVS snapshot (or whatever it might be
called)
(I'm not CVS literate) of the source used for the binary?

This is the real concern for me: while I will willingly provide source for
all
parts of Cygwin I distribute, I'm not sure were/how to get the *correct
version*
of the source for the binaries I downloaded via setup.exe.


Advice?

Is it acceptable for setup.exe to allow download of binaries for which the
correct source is not available *from the same source* ?


Thank you,
    -David.
-
David Dawson
david. w. dawson@ lmco. com
703-367-3885


-Original Message-
From: Christopher Faylor [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 25, 2003 1:38 PM
To: [EMAIL PROTECTED]
Subject: Re: GPL violations et al


On Tue, Mar 25, 2003 at 12:54:49PM -0500, Jim Drash wrote:
>A simple reading of the GPL text maks it clear that if you make use of
>GPL software you must provide the same to your "downstream" clients.
>Charles Wilson is correct.
>
>"Cease and desist" letters are the initial legal step.  However, all
>that needs to be done to avoid any legal action is to put the source on
>the "offending" web site.

Wow.  Could it be said any more clearly than this?

Thank you!

cgf

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

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