Re: Squid CygWin enhancement

From: Guido Serassio <serassio@dont-contact.us>
Date: Fri, 27 Apr 2001 11:37:35 +0200

Hi,

Il 10.52 27/04/2001 Robert Collins ha scritto:
>--- Original Message -----
>From: "Guido Serassio" <serassio@libero.it>
>To: <squid-dev@squid-cache.org>
>Sent: Friday, April 27, 2001 5:39 PM
>Subject: Re: Squid CygWin enhancement
>
>
> > HI Robert,
> >
> > Il 00.25 27/04/2001 Robert Collins ha scritto:
> >
> > >If squid if compiled with cygwin support it links to cygwin1.dll.
>Thus
> > >you need cygwin.
> >
> > I have already verified that a CygWin program needs only cygwin1.dll
>to
> > run, so it enough copy it on system/system32 directory. My Windows
>2000
> > squid test platform don't have CygWin installed on it.
> > In squid.conf I changed the /usr/local/squid reference to c:/squid,
>and all
> > works fine. Please note the use of "/" instead "\", it's an internal
>WIN32
> > feature working fine on MS Visual C++ too.
>
>Cygwin _is_ cygwin1.dll. (That's all cygwin is - it's a
>libc/libm/libpthread for win32). The rest of the tools and so on are
>just a distribution.
>
>Suggestion: put cygwin1.dll in x:\cygwin\bin - for compatability should
>you ever decide to add more of cygwin to the machine. (cygwin uses
>global shared memory, which means that multiple cygwin1.dll's work about
>as well as a fish out of water (80+% of the problems reported with
>cygwin are because of copies in system32 :] ).

As the 99.99 % of the generic Windows problems are because there is a wrong
dll version on system 32 ..... (Thanks Bill ...)

> > >I'm suggesting that if you're on cygwin, try to parse
> > >/etc/resolve.conf - but dont require it :]. There's no urgency on
>this,
> > >I just don't think it should be merged to HEAD without this.
> >
> > Looking at the dns-internal.c, I had an idea:
> >
> > What about add a idnsParseWIN32Registry function and move its code to
>win32.c ?
>
>dns_internal is the right place for dns code I think. we shouldn't just
>lump all the win32 code in one place because it "win32 code". I.e.
>socket code will go in a comm module, disk code goes in a fs module. And
>so on.
>
>What might make sense is a idnsParseWin32Registry function in
>dns_internal.c. (Note: in the near future cygwin will probably generate
>resolve.conf on the fly from the registry :] - but we'll still need your
>code for future NT non-cygwin implementations.)

OK, I make this.

Bye

Guido

-
=======================================================
Serassio Guido
Via Albenga, 11/4 10134 - Torino - ITALY
Tel. : +39.011.610749
E-mail: serassio@interfree.it
            serassio@libero.it
WWW: http://serassio.interfree.it
Received on Fri Apr 27 2001 - 03:37:40 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:13:50 MST