Re: Cygwin and firewalls

[Andrew Schulman]

>> Why is this a Cygwin question?  A firewall is a firewall.  Network
>> applications, both Cygwin and non-Cygwin, have to deal with it.  I don't
>> know what a Cygwin-hostile firewall would look like.
> 
> Cygwin uses sockets to implement many of its functions, such as IPC.
> Some overzealous firewalls install themselves deeply into the winsock
> stack (I believe it's called 'layered service provider' API) and install
> hooks throughout.  This can cause things to break if the firewall
> implementation is not done properly and without bugs, or causes the
> semantics of socket operations to change.  See for example, the threads
> about crappy VPN clients causing cygwin programs to hang, or the
> Zonealarm firewall causing the X11 server to hang at startup.  Sadly the
> archives are littered with examples of poorly written firewall-type
> software that causes things to break, so it's not such a stupid
> question.

OK, thanks.  Learn something new every day.



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

Re: How to write minimal program using GD library

[Brian Dessent]

Siegfried Heintze wrote:

> It works! My problem was that I was running the program (via bash) from the
> emacs compile command.
> 
> I wonder why the path is not set up correctly when I use emacs to create a
> subprocess? The path is setup correctly when I click on the Cygwin prompt.
> 
> I think emacs specifies bash.exe -- perhaps that is the problem. Do I have
> to specify cygwin.bat?

When you run cygwin.bat, that starts a login shell.  When you start bash
from emacs, that is just a regular shell, not a login shell.  The
difference matters as to which files bash reads (e.g. /etc/profile,
~/.bashrc, ~/.profile, etc.)  Read "man bash" section INVOCATION.  If
some aspect of the PATH is only set in the profile then it will only
occur for login shells.  Though normally once an environment variable is
set, it is inherited in subshells, so I don't know why your PATH is not
inherited correctly.  The default set of startup scripts that comes with
Cygwin should be correct in terms of having a correct PATH set for you,
even in subshells, but it's possible you stumbled upon a situation where
something needs to be fixed.

You will have to investigate the contents of your startup files and the
manner in which emacs invokes the shell in order to find out why.  It
could also have to do with the fact that emacs probably launches /bin/sh
by default (not bash), which has its own rules for which startup files
to read (e.g. sh does not know about ~/.bashrc.)  I can't really tell
you more off-hand because a) I have long since modified most of my
startup files and b) I don't use emacs.  You'll have to trace it through
to find out what's going on.  You might add a "set +x" to the top of all
such files to make them print out the commands as they're being
executed.

> I'd also like to make this compile with msvc using the MSVC version of the
> gd library I downloaded from boutell.com. I guess I'll send email to him as
> the web site suggests unless someone can suggests a forum to post in.

I don't know anything about that, sorry.  It's off-topic for this list.

Brian

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

RE: How to write minimal program using GD library

[Siegfried Heintze]

Thanks Brian,
It works! My problem was that I was running the program (via bash) from the
emacs compile command.

I wonder why the path is not set up correctly when I use emacs to create a
subprocess? The path is setup correctly when I click on the Cygwin prompt.

I think emacs specifies bash.exe -- perhaps that is the problem. Do I have
to specify cygwin.bat?

Below is the contents of Cygwin.bat. It does not look like it sets up any
environment variables to me. Why is Cygwin.bat important?

I'd also like to make this compile with msvc using the MSVC version of the
gd library I downloaded from boutell.com. I guess I'll send email to him as
the web site suggests unless someone can suggests a forum to post in.

Siegfried
Cygwin.bat:
@echo off

C:
chdir C:\cygwin\bin

bash --login -i


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

Re: bash page fault on Win98SE when running non-Cygwin programs

[Christopher Faylor]

On Sat, Jun 18, 2005 at 12:05:03PM -0400, irwin wrote:
>On Fri, 17 Jun 2005 21:49:39 -0400, Christopher Faylor wrote:
>>Corinna managed to narrow down the problem with 16-bit programs so
>>there will be a fix in the next snapshot (and eventually in 1.5.18) but
>>without specific information about failing 32-bit programs there will
>>be no fix forthcoming for that problem.  Since all of cygwin consists
>>of 32-bit programs, this problem cannot be too prevalent.
>
>As it turns out, the 32-bit program that I thought was causing the
>problem was actually running a a very old EMX (remember EMX?) binary,
>which was the real culprit.  My apologies for the misdirection.

EMX?  Wow.  Yes, I do vaguely remember this.  Thanks for clarifying
this.  I was mildly worried that there was still another harder-to-find
bug lurking there.

>>Please try the 2005-Jun-18 snapshot when it eventually shows up at
>>.
>
>The cygwin1 DLL in this snapshot has fixed the problem, at least for
>the 16-bit programs I have tried.  My thanks to you and Corinna.
>
>>In case it isn't obvious, this is a Windows 98/Me bug, not a Cygwin
>>bug.  That hardly matters, since we still have to deal with it, but I
>>thought I should mention this fact in the interests of full disclosure.
>
>A Windows bug?  I'm shocked.  Shocked!

I know! It was such a rare occurrence for Windows 9x that I just had to
mention it.  :-)

Thanks for verifying that this is fixed.

cgf

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

Re: bash page fault on Win98SE when running non-Cygwin programs

[irwin]

On Fri, 17 Jun 2005 21:49:39 -0400, Christopher Faylor wrote:
>Corinna managed to narrow down the problem with 16-bit programs so there
>will be a fix in the next snapshot (and eventually in 1.5.18) but
>without specific information about failing 32-bit programs there will be
>no fix forthcoming for that problem.  Since all of cygwin consists of
>32-bit programs, this problem cannot be too prevalent.

As it turns out, the 32-bit program that I thought was causing the problem was
actually running a a very old EMX (remember EMX?) binary, which was the real
culprit. My apologies for the misdirection.

>Please try the 2005-Jun-18 snapshot when it eventually shows up at
>.

The cygwin1 DLL in this snapshot has fixed the problem, at least for the 16-bit
programs I have tried. My thanks to you and Corinna.

>In case it isn't obvious, this is a Windows 98/Me bug, not a Cygwin bug.
>That hardly matters, since we still have to deal with it, but I thought
>I should mention this fact in the interests of full disclosure.

A Windows bug? I'm shocked. Shocked!

/Irwin Meisels
irwinm at rogers dot com

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

Re: 1.5.17: problem building GNU screen

[Christopher Faylor]

On Sat, Jun 18, 2005 at 07:10:08AM -0400, Andrew Schulman wrote:
>> I found a problem building GNU screen on cygwin 1.5.17.
>> Invoking ./configure leads to produce below error message.
>> 
>>>rm: cannot remove `conftext.exe': Permission denied.
>
>IIRC I encountered this problem during the test for a broken FIFO
>implementation.  As it turns out, Cygwin's FIFO implementation is
>broken (http://cygwin.com/ml/cygwin-apps/2005-04/msg00163.html), but
>the test in configure doesn't detect this.  So, my solution was just to
>remove this test from the configure script and set fifo= .  This also
>solved the leftover process problem.  Try applying the attached patch,
>and rerunning configure.

The fifo implementation has improved since that time however:

http://cygwin.com/ml/cygwin-announce/2005-04/msg00035.html

IMO, the posted check for fifos is flawed in that it assumes that
writing to a fifo will not block if there is no reader on the fifo.
That's not true for cygwin.

cgf

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

Re: Cygwin and firewalls

[Christopher Faylor]

On Sat, Jun 18, 2005 at 07:03:32AM -0400, Andrew Schulman wrote:
>> I am wondering if there is a firewall that coexists with Cygwin well.
>>IIRC, there were complaints about Norton software and about some other
>>firewalls too.  What would you recommend me?
>>
>>I ask because I've never had to use firewall before (my home box is
>>behind NAT in a secure network) and I have no experience with Windows
>>firewalls.  I've just bought a laptop and a firewall seems to be
>>necessary in this case.
>
>Why is this a Cygwin question?  A firewall is a firewall.  Network
>applications, both Cygwin and non-Cygwin, have to deal with it.  I
>don't know what a Cygwin-hostile firewall would look like.

Some firewalls don't work well with Cygwin.  This has been reported here
many times and has been mentioned in the cygwin-xfree mailing list on
almost a daily basis.

cgf

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

profiling

[Daniel Walter]

Are there any profilers that can be used with cygwin that can trace the call
stack every time they take a sample?  gprof is not very useful for problems
that involve overcalling optimized functions.

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

Re: POSIX devices

[Bengt-Arne Fjellner]

Oliver Vecernik wrote:
> Bengt-Arne Fjellner schrieb:
>> [...]
>> so you get windows disk number. cygwin /ev/sdX disksize and partition size
>> plus a good guess of what filesystem it has. NOT always perfect.
>> The partition number is the the same as Y in /dev/sdXY
>> Hope this helps.
>
> This was exaclty the tool I was looking for. Thank you very much. But
> shouldn't it be part of ls?
>
> Oliver
>
Well not in ls thats standardized what it should do and please reply to the list
instead.

-- 
Bengt-Arne Fjellner
0910-58 53 69



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

Re: Cygwin and firewalls

[Brian Dessent]

Andrew Schulman wrote:

> Why is this a Cygwin question?  A firewall is a firewall.  Network
> applications, both Cygwin and non-Cygwin, have to deal with it.  I don't
> know what a Cygwin-hostile firewall would look like.

Cygwin uses sockets to implement many of its functions, such as IPC. 
Some overzealous firewalls install themselves deeply into the winsock
stack (I believe it's called 'layered service provider' API) and install
hooks throughout.  This can cause things to break if the firewall
implementation is not done properly and without bugs, or causes the
semantics of socket operations to change.  See for example, the threads
about crappy VPN clients causing cygwin programs to hang, or the
Zonealarm firewall causing the X11 server to hang at startup.  Sadly the
archives are littered with examples of poorly written firewall-type
software that causes things to break, so it's not such a stupid
question.

Brian

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

Greets! I offer you full base of accounts with passwords of mail server yahoo.com. Here is archive with small part of it. You can see that all information is real. If you want to buy full base, please reply me...

[jbruder]

Good offer.

***
 ** Attachment demo.exe was infected with  virus,
 ** attachment part was removed.
 ***


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

Re: 1.5.17: problem building GNU screen

[Andrew Schulman]

> I found a problem building GNU screen on cygwin 1.5.17.
> Invoking ./configure leads to produce below error message.
> 
>>rm: cannot remove `conftext.exe': Permission denied.

IIRC I encountered this problem during the test for a broken FIFO
implementation.  As it turns out, Cygwin's FIFO implementation is broken
(http://cygwin.com/ml/cygwin-apps/2005-04/msg00163.html), but the test in
configure doesn't detect this.  So, my solution was just to remove this
test from the configure script and set fifo= .  This also solved the
leftover process problem.  Try applying the attached patch, and rerunning
configure.

Also, a test package of screen is available.  You may find it easier just to
run it instead.  See http://cygwin.com/ml/cygwin/2005-06/msg00608.html for
a recent update.

Good luck,
Andrew.

diff -ur screen-4.0.2.orig/configure screen-4.0.2/configure
--- screen-4.0.2.orig/configure 2003-12-05 08:46:54.0 -0500
+++ screen-4.0.2/configure  2005-05-02 10:30:20.0 -0400
@@ -4156,206 +4156,15 @@
 fi
 rm -f conftest.$ac_objext conftest$ac_exeext conftest.$ac_ext
 
-{ echo "$as_me:$LINENO: checking fifos..." >&5
-echo "$as_me: checking fifos..." >&6;}
-if test "$cross_compiling" = yes; then
-  { { echo "$as_me:$LINENO: error: cannot run test program while cross 
compiling
-See \`config.log' for more details." >&5
-echo "$as_me: error: cannot run test program while cross compiling
-See \`config.log' for more details." >&2;}
-   { (exit 1); exit 1; }; }
-else
-  cat >conftest.$ac_ext <<_ACEOF
-#line $LINENO "configure"
-/* confdefs.h.  */
-_ACEOF
-cat confdefs.h >>conftest.$ac_ext
-cat >>conftest.$ac_ext <<_ACEOF
-/* end confdefs.h.  */
-
-#include 
-#include 
-#include 
-
-#ifndef O_NONBLOCK
-#define O_NONBLOCK O_NDELAY
-#endif
-#ifndef S_IFIFO
-#define S_IFIFO 001
-#endif
-
-char *fin = "/tmp/conftest$$";
-
-main()
-{
-  struct stat stb;
-#ifdef FD_SET
-  fd_set f;
-#else
-  int f;
-#endif
-
-  (void)alarm(5);
-#ifdef POSIX
-  if (mkfifo(fin, 0777))
-#else
-  if (mknod(fin, S_IFIFO|0777, 0))
-#endif
-exit(1);
-  if (stat(fin, &stb) || (stb.st_mode & S_IFIFO) != S_IFIFO)
-exit(1);
-  close(0);
-#ifdef __386BSD__
-  /*
-   * The next test fails under 386BSD, but screen works using fifos.
-   * Fifos in O_RDWR mode are only used for the BROKEN_PIPE case and for
-   * the select() configuration test.
-   */
-  exit(0);
-#endif
-  if (open(fin, O_RDONLY | O_NONBLOCK))
-exit(1);
-  if (fork() == 0)
-{
-  close(0);
-  if (open(fin, O_WRONLY | O_NONBLOCK))
-   exit(1);
-  close(0);
-  if (open(fin, O_WRONLY | O_NONBLOCK))
-   exit(1);
-  if (write(0, "TEST", 4) == -1)
-   exit(1);
-  exit(0);
-}
-#ifdef FD_SET
-  FD_SET(0, &f);
-#else
-  f = 1;
-#endif
-  if (select(1, &f, 0, 0, 0) == -1)
-exit(1);
-  exit(0);
-}
-
-_ACEOF
-rm -f conftest$ac_exeext
-if { (eval echo "$as_me:$LINENO: \"$ac_link\"") >&5
-  (eval $ac_link) 2>&5
-  ac_status=$?
-  echo "$as_me:$LINENO: \$? = $ac_status" >&5
-  (exit $ac_status); } && { ac_try='./conftest$ac_exeext'
-  { (eval echo "$as_me:$LINENO: \"$ac_try\"") >&5
-  (eval $ac_try) 2>&5
-  ac_status=$?
-  echo "$as_me:$LINENO: \$? = $ac_status" >&5
-  (exit $ac_status); }; }; then
-  echo "- your fifos are usable" 1>&6
- fifo=1
-else
-  echo "$as_me: program exited with status $ac_status" >&5
-echo "$as_me: failed program was:" >&5
-sed 's/^/| /' conftest.$ac_ext >&5
 
-( exit $ac_status )
+# Cygwin patch:
+# Cygwin's fifo implementation is broken; see
+# http://cygwin.com/ml/cygwin-apps/2005-04/msg00163.html.
+# Unfortunately, the "broken fifo implementation test" that was in this 
+# script doesn't detect this, so just short-circuit the whole thing here.
+echo "$as_me: checking fifos..." >&6
 echo "- your fifos are not usable" 1>&6
-
-fi
-rm -f core core.* *.core gmon.out bb.out conftest$ac_exeext 
conftest.$ac_objext conftest.$ac_ext
-fi
-rm -f /tmp/conftest*
-
-if test -n "$fifo"; then
-{ echo "$as_me:$LINENO: checking for broken fifo implementation..." >&5
-echo "$as_me: checking for broken fifo implementation..." >&6;}
-if test "$cross_compiling" = yes; then
-  { { echo "$as_me:$LINENO: error: cannot run test program while cross 
compiling
-See \`config.log' for more details." >&5
-echo "$as_me: error: cannot run test program while cross compiling
-See \`config.log' for more details." >&2;}
-   { (exit 1); exit 1; }; }
-else
-  cat >conftest.$ac_ext <<_ACEOF
-#line $LINENO "configure"
-/* confdefs.h.  */
-_ACEOF
-cat confdefs.h >>conftest.$ac_ext
-cat >>conftest.$ac_ext <<_ACEOF
-/* end confdefs.h.  */
-
-#include 
-#include 
-#include 
-#include 
-
-#ifndef O_NONBLOCK
-#define O_NONBLOCK O_NDELAY
-#endif
-#ifndef S_IFIFO
-#define S_IFIFO 001
-#endif
-
-char *fin = "/tmp/conftest$$";
-
-main()
-{
-  struct timeval tv;
-#ifdef FD_SET
-  fd_set f;
-#else
-  int f;
-#endif
-
-#ifdef POSIX
-  if (mkfifo(fin, 0600))
-#else
-  if (mknod(fin, S_IFIFO|0600, 0))
-#endif
-exit(1);
-  close(0);
-  if (o

Re: Cygwin and firewalls

[Andrew Schulman]

> I am wondering if there is a firewall that coexists with Cygwin well.
> IIRC, there were complaints about Norton software and about some other
> firewalls too. What would you recommend me?
> 
> I ask because I've never had to use firewall before (my home box is behind
> NAT in a secure network) and I have no experience with Windows firewalls.
> I've just bought a laptop and a firewall seems to be necessary in this
> case.

Why is this a Cygwin question?  A firewall is a firewall.  Network
applications, both Cygwin and non-Cygwin, have to deal with it.  I don't
know what a Cygwin-hostile firewall would look like.




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