Re: UNC Pathname Handling within Applications

[Thorsten Haude]

Hi,

* Christopher Faylor wrote (2004-07-17 03:50):
>I don't understand why it matters that the first message would be
>deleted since you can't predict if the message would be directly to you
>or to the cygwin list.  However, please don't enlighten me since I can
>live with not knowing.  More importantly, your personal email
>preferences and my ignorance of same are really off-topic here.

I explained that point before, but since you also seem to deprecate
personal communication (and even make this point clear), I won't
follow up on that.


Thorsten
-- 
He who receives an idea from me, receives instruction himself without lessening
mine; as he who lights his taper at mine, receives light without darkening me.
- Thomas Jefferson


pgpa5DNrftJKT.pgp
Description: PGP signature

Re: ssmtp man page (Was: Re: sending email from cygwin)

[Christopher Faylor]

On Fri, Jul 16, 2004 at 09:53:44PM -0400, Igor Pechtchanski wrote:
>On Fri, 16 Jul 2004, Christopher Faylor wrote:
>
>> On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote:
>> >On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote:
>> >> This is a usability issue.  It's hard enough to teach people to type:
>> >>
>> >>   man 
>> >>
>> >> teaching them to type:
>> >>
>> >>   more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y
>> >
>> >I'm partial to:
>> >
>> >   cygcheck -l ssmtp|fgrep README|xargs less
>> >
>> >myself.  Works for other packages, too.
>>
>> Hey, nice use of tools.  Can we get a gold star here for a clever use of
>> utilities?  This is something that I'll be using myself in the future.
>
>You sure can.  Just for the archives, though (not to downplay the original
>achievement), this will also display any other READMEs contained in the
>package.  If you only want the Cygwin-specific one, this incantation might
>be more appropriate:
>
>cygcheck -l ssmtp|grep "doc/Cygwin/.*README"|xargs less

Thanks for the clarification.

--
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: ssmtp man page (Was: Re: sending email from cygwin)

[Igor Pechtchanski]

On Fri, 16 Jul 2004, Christopher Faylor wrote:

> On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote:
> >On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote:
> >> This is a usability issue.  It's hard enough to teach people to type:
> >>
> >>man 
> >>
> >> teaching them to type:
> >>
> >>more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y
> >
> >I'm partial to:
> >
> >   cygcheck -l ssmtp|fgrep README|xargs less
> >
> >myself.  Works for other packages, too.
>
> Hey, nice use of tools.  Can we get a gold star here for a clever use of
> utilities?  This is something that I'll be using myself in the future.
>
> cgf

You sure can.  Just for the archives, though (not to downplay the original
achievement), this will also display any other READMEs contained in the
package.  If you only want the Cygwin-specific one, this incantation might
be more appropriate:

cygcheck -l ssmtp|grep "doc/Cygwin/.*README"|xargs less

HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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: UNC Pathname Handling within Applications

[Christopher Faylor]

On Fri, Jul 16, 2004 at 11:32:56PM +0200, Thorsten Haude wrote:
>Hi,
>
>* Christopher Faylor wrote (2004-07-16 23:19):
>>On Fri, Jul 16, 2004 at 09:55:49PM +0200, Thorsten Haude wrote:
>>>* Larry Hall wrote (2004-07-16 21:19):
>>>Your email client *sets* Mail-Followup-To, so it must be pretty crappy
>>>to ignore it on inbound mail.
>>
>>This field is added by the ezmlm software that is used to manage our
>>mailing lists.
>
>Ah, so he is just ignoring good advice given by the list software.
>Thanks for clarifying that.
>
>Sorry Larry, your mailer is not crappy.

You must have forgotten.  He said his mailer does not honor this header
not that he, personally, is ignoring it.

Larry said that he would try to avoid sending you an extra copy in the
future and he has explained the reason for his email habits.  You don't
have to agree with his reasons but continuing to carp at him is
pointless.

>>>I've never seen an MDA recipe that deletes the *first* mail of an
>>>identical set.  It's rather hard to do, too, since the MDA would have
>>>to remember where that first mail went.
>>
>>More things in heaven and earth, Horatio?
>>
>> From the procmailex manpage:
>>
>>   If  you are subscribed to several mailinglists and people cross-post to
>>   some of them, you usually receive several  duplicate  mails  (one  from
>>   every  list).   The following simple recipe eliminates duplicate mails.
>>   It tells formail to keep an 8KB cache file in which it will  store  the
>>   Message-IDs  of  the most recent mails you received.  Since Message-IDs
>>   are guaranteed to be unique for every new mail, they are ideally suited
>>   to  weed  out  duplicate mails.  Simply put the following recipe at the
>>   top of your rcfile, and no duplicate mail will get past it.
>>
>>:0 Wh: msgid.lock
>>| formail -D 8192 msgid.cache
>
>I don't intend to install procmail to test this, but are you sure that
>this recipe deletes the *first* of the two mails? From the manpage, it
>looks like the second mail would be removed.

You're right.  It doesn't delete the first.  I didn't think you really
meant to delete the first message since that seemed to imply some kind
of precognitive ability -- how could a program ever know when there are
potentially N copies of a message being sent?  I guess you could delay
every email message delivery for an hour or so to make sure that you've
gotten them all but that isn't foolproof.

I don't understand why it matters that the first message would be
deleted since you can't predict if the message would be directly to you
or to the cygwin list.  However, please don't enlighten me since I can
live with not knowing.  More importantly, your personal email
preferences and my ignorance of same are really off-topic here.

Perhaps most importantly, shouldn't you be hard at work on Nedit now
that you know that there is no way for cygwin to reach inside the
program and stop the Nedit path handling software from deleting needed
double slashes?

Hmm.  Maybe there's a market there.  If we could develop that
precognitive mail software, how hard would developing a DLL that
telepathically changed the program flow of path handling software be?

*pause*

Nuts.  psychicsoftware.com is already taken.

--
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: ssmtp man page (Was: Re: sending email from cygwin)

[Christopher Faylor]

On Fri, Jul 16, 2004 at 02:25:32PM -0700, Yitzchak Scott-Thoennes wrote:
>On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote:
>> This is a usability issue.  It's hard enough to teach people to type:
>> 
>>  man 
>> 
>> teaching them to type:
>> 
>>  more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y
>
>I'm partial to:
> 
>   cygcheck -l ssmtp|fgrep README|xargs less
>
>myself.  Works for other packages, too.

Hey, nice use of tools.  Can we get a gold star here for a clever use of
utilities?  This is something that I'll be using myself in the future.

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: Problem with echo in tcsh 6.13.00-2 in Cygwin 1.5.10 (fwd)

[David Mastronarde]

On Fri, 16 Jul 2004, David Mastronarde wrote:

> On Mon, 12 Jul 2004, David Mastronarde wrote:
> 
> > 
> > The latest version of tcsh has a problem with the built-in echo.
> > When echo is used to write to a file from within a script, and then the
> > script runs a program that attempts to open the file, the program is not
> > able to open the file.
> > 
> > The attachment has a sample program, fortopen.f, which gave the problem 
> > when compiled with the Intel Fortran compiler.  A C program using
> > fopen did not show the problem.  The problem also does not occur when the
> > program is compiled with g77 under Cygwin.  The executable made the tar 
> > file too large for your mail program, so it is not included.  (Please 
> > tell me a better email address to use if you need it from me.)
> > 
> > The script echotest uses echo to write to a file, then runs fortopen which 
> > tries to open the file.  It does it first with echo piped to cat, and with 
> > /bin/echo, which do not fail, then it does it with the built-in echo, 
> > which fails with permission denied.
> > 
> > The problem occurs only with tcsh 6.13, not tcsh 6.12 (see two output 
> > files).
> > 
> > I am running Windows XP SP1.
> > 
> > Thanks.
> > 
> > David Mastronarde
> > 
> Me too.  I've build your test application and ran it under tcsh 6.13.00
> and I had no problem with it:
> 
> $ uname -a
> CYGWIN_NT-5.1 cathi 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown 
> unknown Cygwin
> $ echo $version
> tcsh 6.13.00 (Astron) 2004-05-19 (i386-intel-posix) options 
> 8b,nls,dl,al,kan,rh,color,dspm
> $ g77 -o fortopen fortopen.f
> $ ls -l
> total 82
> -rw-r--r--1 corinna  root17151 Jul 12 22:10 cygcheck.out
> -rw-r--r--1 corinna  root  515 Jul 12 22:13 echoout.6.12
> -rw-r--r--1 corinna  root  746 Jul 12 22:15 echoout.6.13
> -rwxr-xr-x1 corinna  root  363 Jul  8 23:10 echotest
> -rwxr-xr-x1 corinna  root60868 Jul 12 23:08 fortopen.exe
> -rwxr-xr-x1 corinna  root  372 Jul  8 22:56 fortopen.f
> -rw-r--r--1 corinna  root   12 Jul 12 23:12 tempfile
> $ ./echotest 
> Trying with echo pipe to cat
> 000 061 040 060 040 060 040 061 040 060 040 060 012
> 014
> -rw-r--r--1 corinna  root   12 Jul 12 23:26 tempfile
>  File Opened OK
> Trying with /bin/echo
> 000 061 040 060 040 060 040 061 040 060 040 060 012
> 014
> -rw-r--r--1 corinna  root   12 Jul 12 23:26 tempfile
>  File Opened OK
> Trying with built-in echo
> 000 061 040 060 040 060 040 061 040 060 040 060 012
> 014
> -rw-r--r--1 corinna  root   12 Jul 12 23:26 tempfile
>  File Opened OK
> $
> 
> 
> Corinna
> 

I already indicated that the problem will not appear when the program is 
compiled with g77.  I would be glad to send you the program compiled with 
the Intel compiler, but a statically linked version of even such a simple 
program is 245K and only compresses to 115K, so I was not able to send it 
to this list.  Is there another address that will accept this file?

David


--
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: UNC Pathname Handling within Applications

[Thorsten Haude]

Hi,

* Christopher Faylor wrote (2004-07-16 23:19):
>On Fri, Jul 16, 2004 at 09:55:49PM +0200, Thorsten Haude wrote:
>>* Larry Hall wrote (2004-07-16 21:19):
>>Your email client *sets* Mail-Followup-To, so it must be pretty crappy
>>to ignore it on inbound mail.
>
>This field is added by the ezmlm software that is used to manage our
>mailing lists.

Ah, so he is just ignoring good advice given by the list software.
Thanks for clarifying that.

Sorry Larry, your mailer is not crappy.


>>I've never seen an MDA recipe that deletes the *first* mail of an
>>identical set.  It's rather hard to do, too, since the MDA would have
>>to remember where that first mail went.
>
>More things in heaven and earth, Horatio?
>
> From the procmailex manpage:
>
>   If  you are subscribed to several mailinglists and people cross-post to
>   some of them, you usually receive several  duplicate  mails  (one  from
>   every  list).   The following simple recipe eliminates duplicate mails.
>   It tells formail to keep an 8KB cache file in which it will  store  the
>   Message-IDs  of  the most recent mails you received.  Since Message-IDs
>   are guaranteed to be unique for every new mail, they are ideally suited
>   to  weed  out  duplicate mails.  Simply put the following recipe at the
>   top of your rcfile, and no duplicate mail will get past it.
>
> :0 Wh: msgid.lock
> | formail -D 8192 msgid.cache

I don't intend to install procmail to test this, but are you sure that
this recipe deletes the *first* of the two mails? From the manpage, it
looks like the second mail would be removed.


Thorsten
-- 
The smart way to keep people passive and obedient is to
strictly limit the spectrum of acceptable opinion, but
allow very lively debate within that spectrum.
- Noam Chomsky


pgpGKNxIGm8kp.pgp
Description: PGP signature

RE: Whack-a-Mole: Purging Cygnus from Registry

[Buchbinder, Barry (NIH/NIAID)]

At Friday, July 16, 2004 11:45 AM, Todd Curry wrote:
> Corinna,
> 
> This is purely a cygwin question: this particular XP machine *had*
> cygwin installed, and I must remove it before installing any
> backuppc-related-repackagings-of-cygwinue software gets installed.
> 
> Thanks,
> 
> Todd
> (still whacking moles)

I took a brief look at the BackupPC pages.  It looks like BackupPC mainly a
Perl script and that the parts of cygwin that it installs is what it needs
to run on Windows.  So another way to use it might be to figure out what in
Cygwin BackupPC installs/needs to run, install those Cygwin packages, and
then move the unique BackupPC components to your Cygwin installation.  That
way you could have both BackupPC ("an incredible piece of backup software")
and Cygwin (another incredible piece of software).  :-)

- Barry
 
> -Original Message-
> From: Corinna Vinschen
> Sent: Fri, 16 Jul 2004 14:56:33 +0200
> Subject: Re: Whack-a-Mole: Purging Cygnus from Registry
> 
> On Jul 16 05:46, Todd Curry wrote:
>> I'm using an rsyncd package that uses its own version of cygwin, and
>> does not play nice when installed on a machine with Cygwin.  It is
>> part of BackupPC, which is turning out to be an incredible piece of
>> backup software.
> 
> Please ask for support in the backupPC mailing lists.  This mailing
> list is for support of the official Cygwin net release from
> http://cygwin.com/ only.
> 
> 
> Corinna
> 
> --
> Corinna Vinschen  Please, send mails regarding Cygwin
> to Cygwin Co-Project Leader
> Red Hat, Inc.
> 
> --
> 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/

--
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: ssmtp man page (Was: Re: sending email from Cygwin)

[Yitzchak Scott-Thoennes]

On Fri, Jul 16, 2004 at 12:01:03PM +1000, luke.kendall wrote:
> This is a usability issue.  It's hard enough to teach people to type:
> 
>   man 
> 
> teaching them to type:
> 
>   more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y

I'm partial to:
 
   cygcheck -l ssmtp|fgrep README|xargs less

myself.  Works for other packages, too.

--
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: UNC Pathname Handling within Applications

[Christopher Faylor]

On Fri, Jul 16, 2004 at 09:55:49PM +0200, Thorsten Haude wrote:
>* Larry Hall wrote (2004-07-16 21:19):
>Your email client *sets* Mail-Followup-To, so it must be pretty crappy
>to ignore it on inbound mail.

This field is added by the ezmlm software that is used to manage our
mailing lists.

>I've never seen an MDA recipe that deletes the *first* mail of an
>identical set.  It's rather hard to do, too, since the MDA would have
>to remember where that first mail went.

More things in heaven and earth, Horatio?

 From the procmailex manpage:

   If  you are subscribed to several mailinglists and people cross-post to
   some of them, you usually receive several  duplicate  mails  (one  from
   every  list).   The following simple recipe eliminates duplicate mails.
   It tells formail to keep an 8KB cache file in which it will  store  the
   Message-IDs  of  the most recent mails you received.  Since Message-IDs
   are guaranteed to be unique for every new mail, they are ideally suited
   to  weed  out  duplicate mails.  Simply put the following recipe at the
   top of your rcfile, and no duplicate mail will get past it.

  :0 Wh: msgid.lock
  | formail -D 8192 msgid.cache


--
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: UNC Pathname Handling within Applications

[Thorsten Haude]

Hi,

* Larry Hall wrote (2004-07-16 22:29):
>At 03:55 PM 7/16/2004, you wrote:
Actually, I wonder what possible reasons could exist to send every
mail twice, and even by default. I haven't checked, but I guess you
cannot subscribe this list or any other write-only, so in what
possible situation would the second mail enhance communication?
>>>
>>>You guessed wrong.
>>
>>Please tell me how I activate the write-only subscription.
>
>
>
>You don't need to be subscribed to the Cygwin list to send email to it.
>See .

I referred to that fact in the part you generously snipped.


>Unless you have some further pertinent point to make on this inquiry, I 
>think we're done with this thread.

You don't figure to be a guy caring about points.


Thorsten
-- 
There must be a parallel universe where Starbucks sells cocaine in dilute,
controlled, taxed doses, but where (crack) caffiene is sniffed and smoked
in huge binges, and smuggled in by evil Columbian cartels.
- Rogerborg


pgpqBr5U6TOlF.pgp
Description: PGP signature

Re: UNC Pathname Handling within Applications

[Igor Pechtchanski]

On Fri, 16 Jul 2004, Thorsten Haude wrote:

> Please tell me how I activate the write-only subscription.

See .
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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: UNC Pathname Handling within Applications

[Larry Hall]

At 03:55 PM 7/16/2004, you wrote:




>>>Actually, I wonder what possible reasons could exist to send every
>>>mail twice, and even by default. I haven't checked, but I guess you
>>>cannot subscribe this list or any other write-only, so in what
>>>possible situation would the second mail enhance communication?
>>
>>You guessed wrong.
>
>Please tell me how I activate the write-only subscription.
>



You don't need to be subscribed to the Cygwin list to send email to it.
See .

Unless you have some further pertinent point to make on this inquiry, I 
think we're done with this thread.   Been nice talking with you. 


Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746 


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

mail command as a script

[Patrick Samson]

Based on the post of jerzy szczudłowski
(thanks jerzy :), I made an enhanced version
for a mail-mailx replacement.
It is done as a bash script.

I just want to post the script on the list
for whoever needs such a feature, as I did.

To the ssmtp package maintainer:
How about considering to include such a script,
as a bonus, to the package?

---
Usage: mail [OPTION] to-addr[,to-addr]
Simple mailx mail implementation, based on ssmtp.
No interactive mode, no syntax checking, recipient
address must be the last parameter.

  -e   do not send empty mail
  -v   verbose mode
  -a headeradditional headers
  -s subject
  -c cc-addr   cc recipients
  -b bcc-addr  bcc recipients




__
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail

mail
Description: mail
--
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: UNC Pathname Handling within Applications

[Thorsten Haude]

Hi,

* Shankar Unni wrote (2004-07-16 20:36):
>Thorsten Haude wrote:
>
>>The path is also displayed at various places. The user might be
>>surprised to see surplus slashes.
>
>[Starting to drift OT, sorry..]
>
>Who's generating the surplus slashes? Is this because of trailing "/" in 
>paths, and you're internally compositing names somehow?

Yes, we never cared for that because we weren't aware of this leading
slash thing. (I wasn't at least, and never heard about it before.) So
we have to check all internals for problems.

There will probably also be problems with the toolkit.


>I thought the only names you would *show* to the user would be the names 
>of editor buffers, etc., something which the user has already specified 
>explicitly anyway. It's not like you're saying "nedit myfile", and 
>you're searching all over the filesystem to locate myfile..

The filename is used in several parts of the application. I expect
some of them to make false assumptions about leading slashes.


>I.e. if you're doing "prefix + basename", then the only normalization 
>should be between prefix and basename (i.e. strip trailing slashes (any 
>kind) from prefix, and append a "known slash" and basename).
>
>You shouldn't be doing any further normalization (e.g. /x/../y -> /y or 
>any such), because if it *is* a synthesized name, then there's great 
>value in knowing *how* the name was synthesized. Normalizing it loses 
>this information.

These are the things we have to think about, yes.


Thorsten
-- 
Getting a thrill out of some stupid quote is a sign of idiocy.
- turmeric


pgpsvoXmiJuU1.pgp
Description: PGP signature

Re: UNC Pathname Handling within Applications

[Thorsten Haude]

Hi,

* Larry Hall wrote (2004-07-16 21:19):
>At 02:13 PM 7/16/2004, you wrote:
>>I sent the sollowing message to Larry via private mail:
>
>Sorry.  Everything I post to the list I want to be on the list.

I expected that to be a misconfiguration of some kind, now you say you
do that on purpose. It's your choice to prefer discussions on the
list, but I it's highly annoying to send people off to some
non-existing address that you not even own.


>If you would like to continue this or some other discussion off-list,
>reply to the list and let me know that's the direction you want to go.

What other loops have I got to jump through trying to communicate with
you? If you force this discussion on the list by avoiding to open
other means of communication, that's what you get.


>(and continuing it much beyond this is likely getting OT so that
>would make sense)>

Which is exactly the reason I wanted to take this off-list. Your
Reply-To antics is what prevented it.


>>I think the Reply-To header is quite unfit for that.
>>
>>For once, it it mungled often enough that I had to check with every
>>list whether I could use it or not.
>
>OK, it is not munged by this list.

Yeah, but I don't want to check every time somebody insists to send me
every mail twice.


>>Instead I use the Mail-Followup-To header as described here:
>>http://cr.yp.to/proto/replyto.html
>
>So you do.  I guess my email client doesn't honor that.

Your email client *sets* Mail-Followup-To, so it must be pretty crappy
to ignore it on inbound mail.


>>>Depending on the software you use, you may find that you can easily
>>>filter out duplicates too.
>>
>>That wouldn't be entirely satisfactory either for two reasons:
>>- The list mail would usually arrive second and be destroyed. That
>>leaves not-list messages in my list folder.
>>- I might be lead to think that it *is* a personal reply (like this
>>one) and answer personally where a list answer might be more
>>approppriate.
>
>People do this with their email clients directly or through the help
>of procmail.

People do *what* with Procmail? I've never seen an MDA recipe that
deletes the *first* mail of an identical set. It's rather hard to do,
too, since the MDA would have to remember where that first mail went.


>>>I don't second-guess the implied intent of posters to whom I respond
>>>by editing the recipient list but my email client automatically
>>>honors when "reply-to" is set.  Most do.  I'd recommend setting it
>>>when you correspond with this list or any that you subscribe to.
>>
>>Actually, I wonder what possible reasons could exist to send every
>>mail twice, and even by default. I haven't checked, but I guess you
>>cannot subscribe this list or any other write-only, so in what
>>possible situation would the second mail enhance communication?
>
>You guessed wrong.

Please tell me how I activate the write-only subscription.


>That's exactly why I use reply-to-all.  You don't have to be
>subscribed to the list to post to it.

Ok, so find a way to identify these so that you don't have to send
each mail out twice by default. If these people do not care enough to
subscribe, why should you care to accomodate them?


>(well I would have called my suggestions but what's semantics between
>friends ;-) )

Yeah, let's discuss our knowledge of the english language. Is there
any lower point you could have made?


Thorsten
-- 
Guns don't protect freedom, people protect freedom.


pgp34lAOzOPkT.pgp
Description: PGP signature

Re: Bad protocol 'tcp' with perl/lwp module connections

[Igor Pechtchanski]

On Fri, 16 Jul 2004, Dirk Fokken, Cross Development wrote:

> Running a cgi script like the following from the command line works
> pretty fine.
>
> Running the same script from within the browser result in an error
> message like:
>
> http://192.168.0.5/cgi-bin/lwp.cgi
> > 500 Can't connect to search.cpan.org:80 (Bad protocol 'tcp')
>
> The sample script:
> --
> #!/usr/bin/perl -w
>
> use CGI qw(:standard);
>
> print header();
>
>   # Create a user agent object
>   use LWP::UserAgent;
>   $ua = LWP::UserAgent->new;
>   $ua->agent("MyApp/0.1 ");
>
>   # Create a request
>   my $req = HTTP::Request->new(POST => 'http://search.cpan.org/search');
>   $req->content_type('application/x-www-form-urlencoded');
>   $req->content('query=libwww-perl&mode=dist');
>
>   # Pass request to the user agent and get a response back
>   my $res = $ua->request($req);
>
>   # Check the outcome of the response
>   if ($res->is_success) {
>   print $res->content;
>   }
>   else {
>   print $res->status_line, "\n";
>   }
> --
>
> System versions are:
>
> Cygwin DLL version info:
> DLL version: 1.5.10
>
> on
>
> Windows 2000 Professional Ver 5.0 Build 2195
>
>  + Apache/1.3.29
>
> Many thanks for help.
>
> Kind regards,
> Dirk

You already posted this (or something close enough to it):
.
It was replied to: .

Please attach the output of "cygcheck -svr" on your system.  Also, please
show the output of "ls -l /etc/protocols", preferably from the two
invocations of the script.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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: bad interpreter

[Igor Pechtchanski]

On Fri, 16 Jul 2004, David J Jones wrote:

> I do not know what I have setup incorrecty:
> Looking over the list I have learned and made sure both ash and bash are
> both in the /bin/ directory and seem to have been installed correctly.
>
> If I run a script with the initial heading of:
>
> #! /bin/bash
>
> I get this error:
>
> bash-2.05b$ ./Test
> bash: ./Test: /bin/bash: bad interpreter: No such file or directory
> bash-2.05b$
>
> If I change the initial heading in my script to this
>
> #! /cygwin/bin/bash
>
> It works.
>
> Can someone please tell me what I have set up incorrectly?
>
> Thank you, hopefully I have given enough examples this time and feel
> this is a specific question.

Please read and follow the Cygwin problem reporting guidelines at
, in particular the part about attaching
(as an uncompressed text *attachment*) the output of "cygcheck -svr" on
your machine.

A WAG: sounds like your mounts are screwed up, but the output requested
above should show this.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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: UNC Pathname Handling within Applications

[Larry Hall]

At 02:13 PM 7/16/2004, you wrote:
>Hi,
>
>I sent the sollowing message to Larry via private mail:


Sorry.  Everything I post to the list I want to be on the list.  So only
the list version got through.  I guess you figured that out by now.  If
you would like to continue this or some other discussion off-list (and 
continuing it much beyond this is likely getting OT so that would make 
sense), reply to the list and let me know that's the direction you want
to go.  I'll then reply to you directly and we can finish up off list.


>- - - Schnipp - - -
>Hi Larry,
>
>please don't use tofu mails. http://www.vranx.de/mail/tofu.html


Ah-huh.


>* Larry Hall wrote (2004-07-16 17:41):
>>The best way to insure that you get only one copy of any response from the
>>list is to set your reply-to to point to the list.
>
>I think the Reply-To header is quite unfit for that.
>
>For once, it it mungled often enough that I had to check with every
>list whether I could use it or not.


OK, it is not munged by this list.


>Second, the Reply-To header has a different purpose. If would eg. post
>to the list from a mobile phone, I would want a way to ensure that I
>don't get the entire list on this mobile, accumulating huge costs.
>Reply-To ist that way.


Sorry, you've left this a bit vague.  If you're implying that you want 
to get a reply on your mobile and that that address is different than 
the one you subscribed to the list with, I agree.  But that doesn't seem
to be particularly pertinent other than its a way that Reply-To can be 
used. 


>Third, Reply-To is a much stronger way to redirect replies. If this
>mail would have been sent to the list, I might set the Reply-To header
>to indicate that further discussion should be done off-list.


That's fine, if that's what you want.



>Instead I use the Mail-Followup-To header as described here:
>http://cr.yp.to/proto/replyto.html
>


So you do.  I guess my email client doesn't honor that. :-(  Sorry about 
that.  Well, looks like we're at a bit of an impasse here then until one 
of us makes a change, unless I *always* remember to edit my replies to you
(not likely unfortunately).


>>Depending on the software you use, you may find that you can easily
>>filter out duplicates too.
>
>That wouldn't be entirely satisfactory either for two reasons:
>- The list mail would usually arrive second and be destroyed. That
>leaves not-list messages in my list folder.
>- I might be lead to think that it *is* a personal reply (like this
>one) and answer personally where a list answer might be more
>approppriate.


People do this with their email clients directly or through the help
of procmail.  Obviously, there are ways to address your concerns, though
I'm not suggesting that this is what you need to do.  Just that it is an
option for you as a way to deal with those who can't or won't honor your 
settings/requests.


>>I don't second-guess the implied intent of posters to whom I respond
>>by editing the recipient list but my email client automatically
>>honors when "reply-to" is set.  Most do.  I'd recommend setting it
>>when you correspond with this list or any that you subscribe to.
>
>Actually, I wonder what possible reasons could exist to send every
>mail twice, and even by default. I haven't checked, but I guess you
>cannot subscribe this list or any other write-only, so in what
>possible situation would the second mail enhance communication?


You guessed wrong.  That's exactly why I use reply-to-all.  You don't have 
to be subscribed to the list to post to it.


>So my recommendation to you, O wise one, is to just skip the second
>mail, reply to the list *or* in personal way as preferred for a
>particular mail and be done with it.


OK, fair recommendation, considering I had ones for you (well I would have
called my suggestions but what's semantics between friends ;-) ).  Just 
like you, I have reasons for replying as I do and they have served me well 
on this list low these many years.  I don't plan on changing them.  I 
have added "followup-to" to my list of important features that my next
email client has, once I make a switch though.  Thanks for the pointer to
that.



--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746 


--
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: ssmtp man page (Was: Re: sending email from Cygwin)

[Igor Pechtchanski]

On Fri, 16 Jul 2004, Corinna Vinschen wrote:

> On Jul 16 12:01, luke.kendallcisra.canon.com.au wrote:
> > On 15 Jul, Corinna Vinschen wrote:
> > >  > Incidentally is it appropriate to include Cygwin-port-specific
> > >  > information in a man page?
> > >
> > >  Well, from a user perspective it might be cool, but IMHO the original
> > >  man page shouldn't be changed, unless it's a change which should be
> > >  send upstream anyway.  We have the Cygwin specific documentation in
> > >  /usr/share/doc/Cygwin (resp. /usr/doc/Cygwin in earlier releases) for
> > >  a long time now.  It should be not too hard to ask users to look there
> > >  for Cygwin specific docs.
> > >
> > >  Corinna
> >
> > Can you think of a way of incorporating the material in the man page
> > that would be palatable upstream?  How do you think people would feel
> > about a section "PORTABILITY" or "NOTES" or even "WINDOWS" or "CYGWIN"?
>
> I have no idea.  That's something you would have to ask the upstream
> maintainer.  But the first question is if the Cygwin maintainer likes
> the idea.
>
> > The above question is relevant to a patch for the ssmtp man page.  If
> > ssmtp uses ssmtp-config on most platforms it works on, then I can just
> > write a patch that includes both fixes.
>
> ssmtp-config is a Cygwin specific script.
>
> > This is a usability issue.  It's hard enough to teach people to type:
> >
> > man 
> >
> > teaching them to type:
> >
> > more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y
>
> Don't make it overly complicated.  `less /usr/share/doc/Cygwin/ssmtp*'
> is enough.  And telling people that /usr/share/doc/Cygwin contains
> Cygwin specific README files isn't that hard, really.
>
> Corinna

Yep, nice choice of words here. *Telling* them is definitely not hard.
Getting them to do it before sending questions to the list is. :-)

Actually, there's an interesting point in this thread.  Would it be a good
idea to have a reference to the Cygwin-specific README in the manpages for
every Cygwin package that has one (say, in the SEE ALSO section)?  I know
that most maintainers prefer the upstream manpages in their pristine
state, and don't like making the Cygwin-specific patches larger, but this
might actually save some bandwidth on the list.

Another possible place to mention the Cygwin-specific READMEs is in the
"man cygwin" page. :-)

Perhaps this is more appropriate for cygwin-apps now...
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
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: cygrunsrv -S sshd - Access is denied.

[Dick Repasky]

Baurjan,

Thanks! Changing ownership and permissions didn't do it. I had to 
set an appropriate facl.

Dick


On Fri, 16 Jul 2004, Baurjan Ismagulov wrote:

> Hello Dick,
> 
> On Fri, Jul 16, 2004 at 10:21:27AM -0500, Dick Repasky wrote:
> > -rwxr-x---1 rrepasky Users  277504 Apr 19 15:19 /usr/sbin/sshd*
> 
> Seems that your sshd is not executable by SYSTEM. You might want to
> check also the DLLs used by sshd (cygwin1, cygz, cygcrypto-0.9.7 on my
> system).
> 
> With kind regards,
> Baurjan.
> 
> --
> 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/
> 

-

Dick Repasky
Bioinformatics Support
UITS Cubicle 101.08
Indiana University
USA

[EMAIL PROTECTED]

--
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: UNC Pathname Handling within Applications

[Shankar Unni]

Thorsten Haude wrote:
The path is also displayed at various places. The user might be
surprised to see surplus slashes.
[Starting to drift OT, sorry..]
Who's generating the surplus slashes? Is this because of trailing "/" in 
paths, and you're internally compositing names somehow?

I thought the only names you would *show* to the user would be the names 
of editor buffers, etc., something which the user has already specified 
explicitly anyway. It's not like you're saying "nedit myfile", and 
you're searching all over the filesystem to locate myfile..

If the name is something the user is already specifying as a relative or 
absolute path, then there's no need to further normalize them.

If you *do* ever show to the user a path that nedit has composed itself 
(say, some property display, like "where is the foobar package that is 
automatically loaded?"), then the right thing is to only normalize *at 
the point where you do the composition*.

I.e. if you're doing "prefix + basename", then the only normalization 
should be between prefix and basename (i.e. strip trailing slashes (any 
kind) from prefix, and append a "known slash" and basename).

You shouldn't be doing any further normalization (e.g. /x/../y -> /y or 
any such), because if it *is* a synthesized name, then there's great 
value in knowing *how* the name was synthesized. Normalizing it loses 
this information.

--
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: UNC Pathname Handling within Applications

[Thorsten Haude]

Hi,

I sent the sollowing message to Larry via private mail:

- - - Schnipp - - -
Hi Larry,

please don't use tofu mails. http://www.vranx.de/mail/tofu.html

* Larry Hall wrote (2004-07-16 17:41):
>The best way to insure that you get only one copy of any response from the
>list is to set your reply-to to point to the list.

I think the Reply-To header is quite unfit for that.

For once, it it mungled often enough that I had to check with every
list whether I could use it or not.

Second, the Reply-To header has a different purpose. If would eg. post
to the list from a mobile phone, I would want a way to ensure that I
don't get the entire list on this mobile, accumulating huge costs.
Reply-To ist that way.

Third, Reply-To is a much stronger way to redirect replies. If this
mail would have been sent to the list, I might set the Reply-To header
to indicate that further discussion should be done off-list.


Instead I use the Mail-Followup-To header as described here:
http://cr.yp.to/proto/replyto.html


>Depending on the software you use, you may find that you can easily
>filter out duplicates too.

That wouldn't be entirely satisfactory either for two reasons:
- The list mail would usually arrive second and be destroyed. That
leaves not-list messages in my list folder.
- I might be lead to think that it *is* a personal reply (like this
one) and answer personally where a list answer might be more
approppriate.


>I don't second-guess the implied intent of posters to whom I respond
>by editing the recipient list but my email client automatically
>honors when "reply-to" is set.  Most do.  I'd recommend setting it
>when you correspond with this list or any that you subscribe to.

Actually, I wonder what possible reasons could exist to send every
mail twice, and even by default. I haven't checked, but I guess you
cannot subscribe this list or any other write-only, so in what
possible situation would the second mail enhance communication?


So my recommendation to you, O wise one, is to just skip the second
mail, reply to the list *or* in personal way as preferred for a
particular mail and be done with it.


Thorsten
--
As we enjoy great advantages from the inventions of others we should
be glad of an opportunity to serve others by any invention of ours,
and this we should do freely and generously.
- Benjamin Franklin
- - - Schnapp - - -


In an ironic twist I got this reply from the list manager:
- - - Schnipp - - -
Hi! This is the ezmlm program. I'm managing the
[EMAIL PROTECTED] mailing list.

This is a generic help message. The message I received wasn't sent to
any of my command addresses.


--- Administrative commands for the cygwin list ---

I can handle administrative requests automatically. Please
DO NOT SEND THEM TO THE LIST ADDRESS! If you do, I will not
see them and other subscribers will be annoyed. Instead, send
your message to the correct command address:


To subscribe to the list, send a message to:
   <[EMAIL PROTECTED]>

To remove your address from the list, send a message to:
   <[EMAIL PROTECTED]>

Send mail to the following for info and FAQ for this list:
   <[EMAIL PROTECTED]>
   <[EMAIL PROTECTED]>

Similar addresses exist for the digest list:
   <[EMAIL PROTECTED]>
   <[EMAIL PROTECTED]>

To get messages 123 through 145 (a maximum of 100 per request), mail:
   <[EMAIL PROTECTED]>

To get an index with subject and author for messages 123-456 , mail:
   <[EMAIL PROTECTED]>

They are always returned as sets of 100, max 2000 per request,
so you'll actually get 100-499.

To receive all messages with the same subject as message 12345,
send an empty message to:
   <[EMAIL PROTECTED]>

The messages do not really need to be empty, but I will ignore
their content. Only the ADDRESS you send to is important.

You can start a subscription for an alternate address,
for example "[EMAIL PROTECTED]", just add a hyphen and your
address (with '=' instead of '@') after the command word:
<[EMAIL PROTECTED]>

To stop subscription for this address, mail:
<[EMAIL PROTECTED]>

In both cases, I'll send a confirmation message to that address. When
you receive it, simply reply to it to complete your subscription.

If despite following these instructions, you do not get the
desired results, please contact my owner at
[EMAIL PROTECTED] Please be patient, my owner is a
lot slower than I am ;-)

--- Enclosed is a copy of the request I received.

(...)
- - - Schnapp - - -


Thorsten
-- 
As we enjoy great advantages from the inventions of others we should
be glad of an opportunity to serve others by any invention of ours,
and this we should do freely and generously.
- Benjamin Franklin


pgpEQy8y8cWdl.pgp
Description: PGP signature

RE: Whack-a-Mole: Purging Cygnus from Registry

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of Todd Curry
> Sent: 16 July 2004 18:13
> To: [EMAIL PROTECTED]
> Subject: Re: Whack-a-Mole: Purging Cygnus from Registry
> 
> 
> Larry, Max, Dave,
> 
> Thanks!  There were 26 instances of cygwin1.dll on the machine.  


  A new cygwin-list world record!


cheers, 
  DaveK
-- 
Can't think of a witty .sigline today


--
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: Whack-a-Mole: Purging Cygnus from Registry

[Todd Curry]

Larry, Max, Dave,
Thanks!  There were 26 instances of cygwin1.dll on the machine.  When 
removed, rebooted, and regedited, the registry is now 100% free of 
moles!

Thanks again,
Todd
-Original Message-
From: Larry Hall <[EMAIL PROTECTED]>
To: Todd Curry <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
Sent: Fri, 16 Jul 2004 11:52:51 -0400
Subject: Re: Whack-a-Mole: Purging Cygnus from Registry
At 11:45 AM 7/16/2004, you wrote:
Corinna,
This is purely a cygwin question: this particular XP machine *had* 
cygwin
installed, and I must remove it before installing any 
backuppc-related-repackagings-of-cygwinue
software gets installed.

OK, so find all the cygwin1.dlls left on your system and delete them.  
Like
others said, if something is using cygwin1.dll, you'll get a complaint 
the
next time you boot at least.  You can then track down and eradicate all 
those
things.  For the official Cygwin release, if you installed any services 
that
are configured to run automatically at boot up, you need to uninstall 
these.
Then just delete the Cygwin directory.  If no other products on your 
system
run Cygwin, that would remove Cygwin from your system (you can remove 
the
registry entries manually if you like).  That's all that's required.  
See
 if you have not already for 
the
official word.


--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746
--
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/

Re: Whack-a-Mole: Purging Cygnus from Registry

[Larry Hall]

At 11:45 AM 7/16/2004, you wrote:
>Corinna,
>
>This is purely a cygwin question: this particular XP machine *had* cygwin installed, 
>and I must remove it before installing any backuppc-related-repackagings-of-cygwinue 
>software gets installed.


OK, so find all the cygwin1.dlls left on your system and delete them.  Like
others said, if something is using cygwin1.dll, you'll get a complaint the
next time you boot at least.  You can then track down and eradicate all those
things.  For the official Cygwin release, if you installed any services that
are configured to run automatically at boot up, you need to uninstall these.
Then just delete the Cygwin directory.  If no other products on your system
run Cygwin, that would remove Cygwin from your system (you can remove the 
registry entries manually if you like).  That's all that's required.  See
 if you have not already for the 
official word.



--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
838 Washington Street   (508) 893-9889 - FAX
Holliston, MA 01746 


--
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: UNC Pathname Handling within Applications

[Larry Hall]

Thorsten,

The best way to insure that you get only one copy of any response from the 
list is to set your reply-to to point to the list.  Depending on the software
you use, you may find that you can easily filter out duplicates too.  I don't
second-guess the implied intent of posters to whom I respond by editing the
recipient list but my email client automatically honors when "reply-to" is 
set.  Most do.  I'd recommend setting it when you correspond with this list or any 
that you subscribe to.

Larry

PS - I've edited the recipient list in this case for you, given your stated
preference.


At 08:06 AM 7/16/2004, you wrote:
>Hi,
>
>please send me every mail only once. Thanks.
>
>* Larry Hall wrote (2004-07-16 04:21):
>>At 07:30 PM 7/15/2004, you wrote:
>>>* Shankar Unni wrote (2004-07-16 00:52):
Thorsten Haude wrote:
>- Is there any standard way to approach this problem? Has it come up
>before in other applications?

I don't know why you are even trying to normalize the paths like this. 
Just hand the thing off to the OS. Usually, both the user and the OS 
know what it is they are trying to do.
>>>
>>>The path is also displayed at various places. The user might be
>>>surprised to see surplus slashes.
>>
>>Better that they be surprised and have things work than be surprised and
>>complain when things don't work.  Don't shield them from the reality of the
>>real world.  It's a learning experience and depriving them of that won't
>>help anyone.
>
>I think some people might see the surprising path, *think* the
>software is broken and stop using it. Another problem ist the toolkit.
>
>I agree that the leading extra slash should be supported, but it might
>not be as easy as it sounds.
>
>
>>That ends the philosophy lesson for today.  Please go back to your homes
>>now and meditate on this. ;-)
>
>Thank you, O wise one!
>
>
>Thorsten
>-- 
>As we enjoy great advantages from the inventions of others we should
>be glad of an opportunity to serve others by any invention of ours,
>and this we should do freely and generously.
>- Benjamin Franklin


--
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: Whack-a-Mole: Purging Cygnus from Registry

[Todd Curry]

Corinna,
This is purely a cygwin question: this particular XP machine *had* 
cygwin installed, and I must remove it before installing any 
backuppc-related-repackagings-of-cygwinue software gets installed.

Thanks,
Todd
(still whacking moles)
-Original Message-
From: Corinna Vinschen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sent: Fri, 16 Jul 2004 14:56:33 +0200
Subject: Re: Whack-a-Mole: Purging Cygnus from Registry
On Jul 16 05:46, Todd Curry wrote:
I'm using an rsyncd package that uses its own version of cygwin, and
does not play nice when installed on a machine with Cygwin.  It is 
part
of BackupPC, which is turning out to be an incredible piece of backup
software.
Please ask for support in the backupPC mailing lists.  This mailing
list is for support of the official Cygwin net release from
http://cygwin.com/ only.
Corinna
--
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader  mailto:[EMAIL PROTECTED]
Red Hat, Inc.
--
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/

Re: cygrunsrv -S sshd - Access is denied.

[Baurjan Ismagulov]

Hello Dick,

On Fri, Jul 16, 2004 at 10:21:27AM -0500, Dick Repasky wrote:
> -rwxr-x---1 rrepasky Users  277504 Apr 19 15:19 /usr/sbin/sshd*

Seems that your sshd is not executable by SYSTEM. You might want to
check also the DLLs used by sshd (cygwin1, cygz, cygcrypto-0.9.7 on my
system).

With kind regards,
Baurjan.

--
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: gcc 3.3.1-3 runtime error: static data storage size

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of Christopher Faylor
> Sent: 16 July 2004 15:16

> >Yes, I see.  Yhe problem is the default stack size on cygwin 
> (2 MB), you
> >can increase it.
> >
> >$ gcc -o aa -Wl,--stack,8388608 aa.c
> >
> >$ ./aa
> >ok
> >
> >$ cat aa.c
> >#define NXY 7000
> >
> >int xy[NXY][NXY];
> >main(){
> >printf("ok\n");
> >}
> 
> Why would the stack size affect a global variable?
> 
> cgf

  It's a problem in Cygwin's startup code, triggered purely by the size of
the common section.

(gdb) bt
#0  pinfo::init(int, unsigned long, void*) (this=0x610f59e4, n=4012, flag=1,
in_h=0x0) at ../../../../src/winsup/cygwin/pinfo.cc:198
#1  0x61071a32 in set_myself(int, void*) (pid=1, h=0x0) at
../../../../src/winsup/cygwin/pinfo.cc:66
#2  0x61071b84 in pinfo_init(char**, int) (envp=0x0, envc=0) at
../../../../src/winsup/cygwin/pinfo.cc:93
#3  0x61005b74 in dll_crt0_1(char*) () at
../../../../src/winsup/cygwin/dcrt0.cc:785
#4  0x6100614b in _dll_crt0 () at ../../../../src/winsup/cygwin/dcrt0.cc:942

(gdb) 


  It turns out that pinfo::init has this chunk of code:

195   procinfo = (_pinfo *) MapViewOfFileEx (h, access, 0,
0, 0, mapaddr);
196   ProtectHandle1 (h, pinfo_shared_handle);
197 
-   198   if ((procinfo->process_state & PID_INITIALIZING) &&
(flag & PID_NOREDIR)
199   && cygwin_pid (procinfo->dwProcessId) !=
procinfo->pid)
200 {
-   201   release ();
-   202   set_errno (ENOENT);
-   203   return;
204 }

  And the SEGV happens when we attempt to test (procinfo->process_state &
PID_INITIALIZING) because procinfo is NULL, meaning the MapViewOfFileEx call
must have failed  let's just see how it gets called

procinfo = (_pinfo *) MapViewOfFileEx (h, access, 0, 0, 0, mapaddr);

(gdb) print/x h
$2 = 0x730

(gdb) print/x access
$3 = 0x6

(gdb) print/x mapaddr
$4 = 0x40

Ok, what's handle 0x730?

  730: Section   \BaseNamedObjects\cygwin1S4.cygpid.4076

and the return value after stepping over the function call?

(gdb) print $eax
$6 = 0

Hmm, so what's the actual error?

(gdb) info breakpoints
Num Type   Disp Enb AddressWhat
1   breakpoint keep y   0x00401072 in main at aa.c:5
2   breakpoint keep y   0x61071eee in pinfo::init(int, unsigned long,
void*) at ../../../../src/winsup/cygwin/pinfo.cc:195

(gdb) 

(gdb) set $eip=0x77f5f5d4
(gdb) disass $eip $eip+12
Dump of assembler code from 0x77f5f5d4 to 0x77f5f5e0:
0x77f5f5d4 :  mov%fs:0x18,%eax
0x77f5f5da :  mov0xfb0(%eax),%eax
End of assembler dump.

(gdb) stepi
No symbol "procinfo" in current context.
Cannot access memory at address 0x4

0x77f5f5da in ntdll!RtlGetLastWin32Error () from ntdll.dll

(gdb) print/x $eax
$6 = 0x7ffde000

(gdb) stepi
No symbol "procinfo" in current context.
Cannot access memory at address 0x4

0x77f5f5e0 in ntdll!RtlGetLastWin32Error () from ntdll.dll

(gdb) print $eax
$7 = 0

(gdb) 

  Hmm.  How strange.  The last Win32 error code is zero.

  However, it seems to be a variant of the
can't-map-the-shared-heap-at-the-same-address-in-the-child-process bug,
presumably because the huge common section occupies that address range, and
the lack of a NULL-pointer test on the return from MapViewOfFileEx leads to
the SEGV.  But I can't say for sure that that is what was going on; I didn't
actually verify the process space layout was as I guess.  And I don't know
why there wasn't an error return code either.

cheers, 
  DaveK
-- 
Can't think of a witty .sigline today


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

cygrunsrv -S sshd - Access is denied.

[Dick Repasky]

Hello,

I'm having difficulty with sshd on an Windows XP system.  It worked fine
for months and then failed after upgrading to OpenSSH_3.8.1p1. 
The command cygrunsrv fails with the error 

   cygrunsrv: Error starting a service: StartSevervice: Win32 error 5: Access is denied

I did a number of things and then decided to start again from scratch.

1) Removed the openssh cygwin package.
   Removed sshd as a service (using cygrunsrv -R)
   Deleted sshd from /etc/passwd
   Removed /var/empty
   Removed /etc/ssh*

2) Installed cygwin openssh package
   Ran ssh-host-config -y
   ssh-user-config

   ssh-host-config and ssh-user-config worked without error.
   cygrunsrv -S sshd bombs with same error

   Both CYGWIN=tty ntsec and CYGWIN=ntsec produce the same results.

Relevant permissions as set up by ssh-host-config:

/etc/hosts/ssh*

-rwxr-x---1 SYSTEM   None 1159 Jul 16 08:38 ssh_config*
-rw---1 SYSTEM   None  668 Jul 16 08:38 ssh_host_dsa_key
-rw-r--r--1 SYSTEM   None  609 Jul 16 08:38 ssh_host_dsa_key.pub
-rw---1 SYSTEM   None  534 Jul 16 08:38 ssh_host_key
-rw-r--r--1 SYSTEM   None  338 Jul 16 08:38 ssh_host_key.pub
-rw---1 SYSTEM   None  887 Jul 16 08:38 ssh_host_rsa_key
-rw-r--r--1 SYSTEM   None  229 Jul 16 08:38 ssh_host_rsa_key.pub
-rw-r--r--1 SYSTEM   None 2487 Jul 16 08:38 sshd_config

/var/empty (set by ssh-host-config)

drwxr-xr-x+   2 SYSTEM   root0 Jul 16 08:38 /var/empty/

sshd perms (as installed by cygwin)

-rwxr-x---1 rrepasky Users  277504 Apr 19 15:19 /usr/sbin/sshd*

/usr/sbin/sshd --version
OpenSSH_3.8.1.1p1, OpenSSL 0.9.76 17 Mar 2004

passwd entry

sshd:unused_by_nt/2000/xp:1004:513:sshd 
privsep,U-AMPHISPIZA\sshd,S-1-5-21-839522115-117609710-725345543-1004:/var/empty:/bin/false


Output of strace cygrunsrv -S sshd >> ~/tocygwin.sshd 2>&1 (can't see anything
  interesting here, but you might)

**
Program name: F:\cygwin\bin\cygrunsrv.exe (1148)
App version:  1005.9, api: 0.112
DLL version:  1005.10, api: 0.116
DLL build:2004-05-25 22:07
OS version:   Windows NT-5.1
Heap size:402653184
Date/Time:2004-07-16 09:08:35
**
  459 827 [main] cygrunsrv 1148 environ_init: 0xA050008: !::=::\
   65 892 [main] cygrunsrv 1148 environ_init: 0xA050250: !F:=F:\cygwin\bin
   65 957 [main] cygrunsrv 1148 environ_init: 0xA050268: 
ALLUSERSPROFILE=F:\Documents and Settings\All Users
   651022 [main] cygrunsrv 1148 environ_init: 0xA0502A0: APPDATA=F:\Documents and 
Settings\rrepasky\Application Data
   661088 [main] cygrunsrv 1148 environ_init: 0xA0502E0: 
COMMONPROGRAMFILES=F:\Program Files\Common Files
   651153 [main] cygrunsrv 1148 environ_init: 0xA050318: COMPUTERNAME=AMPHISPIZA
   641217 [main] cygrunsrv 1148 environ_init: 0xA050338: 
COMSPEC=F:\WINDOWS\system32\cmd.exe
   661283 [main] cygrunsrv 1148 environ_init: 0xA050360: CVS_RSH=/bin/ssh
   651348 [main] cygrunsrv 1148 parse_options: ntsec 1
   631411 [main] cygrunsrv 1148 parse_options: returning
   341445 [main] cygrunsrv 1148 environ_init: 0xA050378: CYGWIN=ntsec
   651510 [main] cygrunsrv 1148 getwinenv: can't set native for HOME= since no 
environ yet
   711581 [main] cygrunsrv 1148 mount_info::conv_to_posix_path: conv_to_posix_path 
(F:\cygwin\home\rrepasky, no-keep-rel, no-add-slash)
   471628 [main] cygrunsrv 1148 normalize_win32_path: F:\cygwin\home\rrepasky = 
normalize_win32_path (F:\cygwin\home\rrepasky)
   441672 [main] cygrunsrv 1148 mount_info::conv_to_posix_path: /home/rrepasky = 
conv_to_posix_path (F:\cygwin\home\rrepasky)
   951767 [main] cygrunsrv 1148 win_env::add_cache: posix /home/rrepasky
   341801 [main] cygrunsrv 1148 win_env::add_cache: native 
HOME=F:\cygwin\home\rrepasky
   341835 [main] cygrunsrv 1148 posify: env var converted to HOME=/home/rrepasky
   621897 [main] cygrunsrv 1148 environ_init: 0xA0503C8: HOME=/home/rrepasky
   651962 [main] cygrunsrv 1148 environ_init: 0xA050518: HOMEDRIVE=F:
   632025 [main] cygrunsrv 1148 environ_init: 0xA050530: HOMEPATH=\Documents and 
Settings\rrepasky
   662091 [main] cygrunsrv 1148 environ_init: 0xA050560: HOSTNAME=amphispiza
   632154 [main] cygrunsrv 1148 environ_init: 0xA050578: LOGONSERVER=\\AMPHISPIZA
  1612315 [main] cygrunsrv 1148 environ_init: 0xA050598: MAKE_MODE=unix
   652380 [main] cygrunsrv 1148 environ_init: 0xA0505B0: 
MANPATH=/usr/man:/usr/share/man:/usr/X11R6/man
   642444 [main] cygrunsrv 1148 environ_init: 0xA0505E8: NUMBER_OF_PROCESSORS=2
   632507 [main] cygrunsrv 1148 environ_init: 0xA050608: OLDPWD=/home/rrepasky
   652572 [main] cygrunsrv 1148 environ_init: 0xA050628: OS=Windows_NT
   652637 [main] cygrunsrv 1148 getwinenv: can't set native for PATH= since no 
environ yet
   392676 [main] cygrunsrv 1148 nor

Re: gcc 3.3.1-3 runtime error: static data storage size

[Gerrit P. Haase]

Christopher wrote:

> On Fri, Jul 16, 2004 at 10:36:23AM +0200, Gerrit P. Haase wrote:
>>Pietro schrieb:
>>
>>> Gerrit,
>>
>>> I think you just did:
>>
>>> the program should print "ok" upon executing and it didn't. if you debug,
>>> say, with insight, aa.exe will bail before reaching the printf statement,
>>> generating a segmentation violation signal.
>>
>>> let me know. thanks for looking into it.
>>
>>> Pietro
>>
>>> On Fri, 16 Jul 2004, Gerrit P. Haase wrote:
>>
 Pietro wrote:

 > I have the following example to propose:
 > /** aa.c **/
 > #define NXY 5000
 > #define NXY 7000
 > int xy[NXY][NXY];
 > main(){
 > printf("ok\n");
 > }

 > This will work when NXY=5000, but will generate a SIGSEV exception before
 > reaching the first statement when NXY=7000.

 > The array in the faulty case is 187MB. The gcc documentation gives 2GB as
 > the limit for having to switch to dynamic allocation. Any fixes? or
 > relevant compiler options possibly available?

 I cannot reproduce it on my W2K Professional box:


 $ cat aa.c
 #define NXY 7000

 int xy[NXY][NXY];
 main(){
 printf("ok\n");
 }

 $ gcc -o aa aa.c

 $ ./aa.exe

 Gerrit
 --
 =^..^=
 http://nyckelpiga.de/donate.html

>>
>>Yes, I see.  Yhe problem is the default stack size on cygwin (2 MB), you
>>can increase it.
>>
>>$ gcc -o aa -Wl,--stack,8388608 aa.c
>>
>>$ ./aa
>>ok
>>
>>$ cat aa.c
>>#define NXY 7000
>>
>>int xy[NXY][NXY];
>>main(){
>>printf("ok\n");
>>}

> Why would the stack size affect a global variable?

I don't know.  In this case it seems to work when I define the stack
with 8MB and it doesn't work when I use the default stack settings.


Gerrit
-- 
=^..^= http://nyckelpiga.de/donate.html


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

bad interpreter

[David J Jones]

I do not know what I have setup incorrecty:
Looking over the list I have learned and made sure both ash and bash are
both in the /bin/ directory and seem to have been installed correctly.

If I run a script with the initial heading of:

#! /bin/bash

I get this error:

bash-2.05b$ ./Test
bash: ./Test: /bin/bash: bad interpreter: No such file or directory
bash-2.05b$

If I change the initial heading in my script to this

#! /cygwin/bin/bash

It works.

Can someone please tell me what I have set up incorrectly?

Thank you, hopefully I have given enough examples this time and feel this is
a specific question.



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

Bad protocol 'tcp' with perl/lwp module connections

[Dirk Fokken, Cross Development]

Running a cgi script like the following from the command line works pretty fine.

Running the same script from within the browser result in an error message like:

http://192.168.0.5/cgi-bin/lwp.cgi
> 500 Can't connect to search.cpan.org:80 (Bad protocol 'tcp')

The sample script:
--
#!/usr/bin/perl -w

use CGI qw(:standard);
 
print header();

  # Create a user agent object
  use LWP::UserAgent;
  $ua = LWP::UserAgent->new;
  $ua->agent("MyApp/0.1 ");

  # Create a request
  my $req = HTTP::Request->new(POST => 'http://search.cpan.org/search');
  $req->content_type('application/x-www-form-urlencoded');
  $req->content('query=libwww-perl&mode=dist');

  # Pass request to the user agent and get a response back
  my $res = $ua->request($req);

  # Check the outcome of the response
  if ($res->is_success) {
  print $res->content;
  }
  else {
  print $res->status_line, "\n";
  }
--

System versions are:

Cygwin DLL version info:
DLL version: 1.5.10

on 

Windows 2000 Professional Ver 5.0 Build 2195

 + Apache/1.3.29 

Many thanks for help.

Kind regards,

Dirk


--
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: mmap bug on Windows 9x

[Corinna Vinschen]

On Jul 16 09:12, Anton Ertl wrote:
> Anton Ertl wrote:
> > 
> > On Windows 9x/ME different calls to mmap sometimes produce the same
> > address (without that memory being unmapped in the meantime, at least
> > not by application code).
> 
> You find a condensed test program below.
> 
> On Windows ME with cygwin1.dll 1.5.10 it outputs:
> 
> try mmap($0, $4, ..., MAP_ANON, ...); success, address=$833ca000
> try mmap($8340b000, $4, ..., MAP_ANON, ...); success, address=$833ca000
> 
> Note that the result addresses are the same.

Thanks for the testcase!  Wow, I'm impressed.  Three serious bug reports
in two days which all had a simple testcase(tm) attached! 

*Sob*, I'm moved to tears.

Anyway, I found the cause of that problem.  For some reason (moon phase
or so) the mmap code didn't marked pages as used when running under 9x/Me.
This could only be observed under a specific condition of mmapping
anonymous private pages.

I've applied a fix to the repository.  Should be in the next developers
snapshot from http://cygwin.com/snapshots/


Thanks for the report,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader  mailto:[EMAIL PROTECTED]
Red Hat, Inc.

--
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: Whack-a-Mole: Purging Cygnus from Registry

[Corinna Vinschen]

On Jul 16 10:21, Christopher Faylor wrote:
> On Fri, Jul 16, 2004 at 05:46:59AM -0700, Todd Curry wrote:
> >I'm using an rsyncd package that uses its own version of cygwin, and 
> >does not play nice when installed on a machine with Cygwin.  It is part 
> >of BackupPC, which is turning out to be an incredible piece of backup 
> >software.
> 
> **cgf wakes up after ten minutes of being in a deep coma shock
> 
> Wow.  An free software project which uses cygwin and actually includes
> the source code for cygwin.  Whoopee!

Yup, I saw that, too.  It was actually the first thing I checked for.
But I still don't like the idea of projects providing their own Cygwin
DLL.  It would be the same if the project provides their Linux binary
package together with a Linux kernel.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader  mailto:[EMAIL PROTECTED]
Red Hat, Inc.

--
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: coredump on kill

[Christopher Faylor]

On Fri, Jul 16, 2004 at 02:37:23PM -0800, Carlo Florendo y Flora wrote:
>Hello,
>
>Upon invoking the following command, I get a coredump:
>
>/usr/bin/kill --list
>
>By the way, "kill -l" (bash built-in) works.
>
>Attached is cygcheck's output and the dump itself.
>
>Does anyone know of a workaround?

Use kill.exe from a snapshot.  This bug was fixed on 2004-05-27 and the fix will
be in the next version of cygwin.

http://cygwin.com/snapshots/

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: Whack-a-Mole: Purging Cygnus from Registry

[Christopher Faylor]

On Fri, Jul 16, 2004 at 05:46:59AM -0700, Todd Curry wrote:
>I'm using an rsyncd package that uses its own version of cygwin, and 
>does not play nice when installed on a machine with Cygwin.  It is part 
>of BackupPC, which is turning out to be an incredible piece of backup 
>software.

**cgf wakes up after ten minutes of being in a deep coma shock

Wow.  An free software project which uses cygwin and actually includes
the source code for cygwin.  Whoopee!

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

[OT] RE: COM Port Question

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of Tester Field
> Sent: 16 July 2004 14:58

> Thank you for your response. I was wondering if there
> any way of testing whether the device attached to
> COM1, is receiving any data. I have done ls-al
> /dev/com1 and I see the file. However, how can I
> verify that the device attached is receiving any data.
> Any idea? Any utilities provided to monitor the serial
> port?
> 
> --Mona


  It isn't cygwin, but what you want is Portmon from www.sysinternals.com,
which does just that.


cheers, 
  DaveK
-- 
Can't think of a witty .sigline today


--
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: gcc 3.3.1-3 runtime error: static data storage size

[Christopher Faylor]

On Fri, Jul 16, 2004 at 10:36:23AM +0200, Gerrit P. Haase wrote:
>Pietro schrieb:
>
>> Gerrit,
>
>> I think you just did:
>
>> the program should print "ok" upon executing and it didn't. if you debug,
>> say, with insight, aa.exe will bail before reaching the printf statement,
>> generating a segmentation violation signal.
>
>> let me know. thanks for looking into it.
>
>> Pietro
>
>> On Fri, 16 Jul 2004, Gerrit P. Haase wrote:
>
>>> Pietro wrote:
>>>
>>> > I have the following example to propose:
>>> > /** aa.c **/
>>> > #define NXY 5000
>>> > #define NXY 7000
>>> > int xy[NXY][NXY];
>>> > main(){
>>> > printf("ok\n");
>>> > }
>>>
>>> > This will work when NXY=5000, but will generate a SIGSEV exception before
>>> > reaching the first statement when NXY=7000.
>>>
>>> > The array in the faulty case is 187MB. The gcc documentation gives 2GB as
>>> > the limit for having to switch to dynamic allocation. Any fixes? or
>>> > relevant compiler options possibly available?
>>>
>>> I cannot reproduce it on my W2K Professional box:
>>>
>>>
>>> $ cat aa.c
>>> #define NXY 7000
>>>
>>> int xy[NXY][NXY];
>>> main(){
>>> printf("ok\n");
>>> }
>>>
>>> $ gcc -o aa aa.c
>>>
>>> $ ./aa.exe
>>>
>>> Gerrit
>>> --
>>> =^..^= http://nyckelpiga.de/donate.html
>>>
>
>Yes, I see.  Yhe problem is the default stack size on cygwin (2 MB), you
>can increase it.
>
>$ gcc -o aa -Wl,--stack,8388608 aa.c
>
>$ ./aa
>ok
>
>$ cat aa.c
>#define NXY 7000
>
>int xy[NXY][NXY];
>main(){
>printf("ok\n");
>}

Why would the stack size affect a global variable?

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: COM Port Question

[Tester Field]

Thank you for your response. I was wondering if there
any way of testing whether the device attached to
COM1, is receiving any data. I have done ls-al
/dev/com1 and I see the file. However, how can I
verify that the device attached is receiving any data.
Any idea? Any utilities provided to monitor the serial
port?

--Mona



--- Brian Ford <[EMAIL PROTECTED]> wrote:
> On Thu, 15 Jul 2004, Tester Field wrote:
> 
> > Hi,
> >  
> > I have installed Cygwin on a Dell PC with windows
> > 2000, and I am trying to sent AT command to an
> > external modem attached on COM1.
> >  
> > My questions are:
> >  
> > 1) What do I need to do for cygwin to recognize
> COM1?
> 
> Nothing :-).
> 
> > 2) Is there a utility provided for the purposes.
> 
> Not sure.
>   
> > My ultimate goal is to send SMS message using
> Kannel
> > and a GSM modem. I understand this is not the
> right
> > place of Kannel questions, however I will like to
> ask
> > for help on Cygwin recognizing COM1 port.
> >
> > I appreciate any assistance that you might
> provide.
> > Also, I have searched google without success. If
> any
> > document that provides assistance, please provide
> me a
> > link. Again, I appreciate any assistance you might
> > provide.
> >  
> Did you look here?
> 
>
http://cygwin.com/cygwin-ug-net/using-specialnames.html#AEN825
>   
> HTH
> 
> -- 
> Brian Ford
> Senior Realtime Software Engineer
> VITAL - Visual Simulation Systems
> FlightSafety International
> the best safety device in any aircraft is a
> well-trained pilot...
> 
> --
> 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/
> 
> 




__
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail

--
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: coredump on kill

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of Brian Ford
> Sent: 16 July 2004 14:43

> On Fri, 16 Jul 2004, Carlo Florendo y Flora wrote:
> 
> > Hello,
> >
> > Upon invoking the following command, I get a coredump:
> >
> > /usr/bin/kill --list
> >
> > By the way, "kill -l" (bash built-in) works.
> >
> > Attached is cygcheck's output and the dump itself.
> >
> > Does anyone know of a workaround?
> >
> 
> I do ;-).
> 
> http://sources.redhat.com/ml/cygwin/2004-05/msg00918.html


  I can confirm it works fine in current cvs!


cheers, 
  DaveK
-- 
Can't think of a witty .sigline today


--
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: Whack-a-Mole: Purging Cygnus from Registry

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of Todd Curry
> Sent: 16 July 2004 13:47

> I'm using an rsyncd package that uses its own version of cygwin, and 
> does not play nice when installed on a machine with Cygwin.  
> It is part 
> of BackupPC, which is turning out to be an incredible piece of backup 
> software.
> 
> So, I've got one Windows XP machine that is seemingly possessed -- I 
> have removed the cygwin dir, have triple-checked running 
> processes and 
> services and don't see anything that I *think* is Cygwin related.
> 
> But here is the kicker:  no matter how (or how many) times I 
> purge the 
> "Cygnus Solutions" entries from the XP registry, they come right back 
> -- something is re-creating them.  I delete the keys, start 
> it back up, 
> and there is Cygnus again.  It is truly bizarre!
> 
> What should I check to make sure there are no processes or services 
> running?  Somebody give me the "paranoid" / overkill options here.

  Use the windows task manager to make sure, if you like, or something like
process explorer from www.sysinternals.com

> Second, if that should fail, does anyone know what 
> specifically creates 
> the registry entries?  Can we work backwards from there to find the 
> culprit?

  IIUIC the cygwin dll recreates them if they're missing any time a cygwin
app fires up.

  If you really can't find a running task, that suggests that it's some
service that's been installed with cygrunsrv.  What was that you were saying
about an rsyncd?  What does the output of "net start" show you?


cheers, 
  DaveK
-- 
Can't think of a witty .sigline today


--
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: COM Port Question

[Brian Ford]

On Thu, 15 Jul 2004, Tester Field wrote:

> Hi,
>  
> I have installed Cygwin on a Dell PC with windows
> 2000, and I am trying to sent AT command to an
> external modem attached on COM1.
>  
> My questions are:
>  
> 1) What do I need to do for cygwin to recognize COM1?

Nothing :-).

> 2) Is there a utility provided for the purposes.

Not sure.
  
> My ultimate goal is to send SMS message using Kannel
> and a GSM modem. I understand this is not the right
> place of Kannel questions, however I will like to ask
> for help on Cygwin recognizing COM1 port.
>
> I appreciate any assistance that you might provide.
> Also, I have searched google without success. If any
> document that provides assistance, please provide me a
> link. Again, I appreciate any assistance you might
> provide.
>  
Did you look here?

http://cygwin.com/cygwin-ug-net/using-specialnames.html#AEN825
  
HTH

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...

--
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: Whack-a-Mole: Purging Cygnus from Registry

[Max Bowsher]

Todd Curry wrote:
> I'm using an rsyncd package that uses its own version of cygwin, and
> does not play nice when installed on a machine with Cygwin.  It is part
> of BackupPC, which is turning out to be an incredible piece of backup
> software.
>
> So, I've got one Windows XP machine that is seemingly possessed -- I
> have removed the cygwin dir, have triple-checked running processes and
> services and don't see anything that I *think* is Cygwin related.
>
> But here is the kicker:  no matter how (or how many) times I purge the
> "Cygnus Solutions" entries from the XP registry, they come right back
> -- something is re-creating them.  I delete the keys, start it back up,
> and there is Cygnus again.  It is truly bizarre!
>
> What should I check to make sure there are no processes or services
> running?  Somebody give me the "paranoid" / overkill options here.
>
> Second, if that should fail, does anyone know what specifically creates
> the registry entries?  Can we work backwards from there to find the
> culprit?

Corinna Vinschen wrote:
> This mailing
> list is for support of the official Cygwin net release from
> http://cygwin.com/ only.

What Corinna said, but since it sounds like you are *trying* to use official
Cygwin but being thwarted by BackupPC's bundle, I thought I'd suggest a few
things.

Potentially, anything using the cygwin1.dll could be creating the keys. Try
removing *all* copies of the DLL, removing the keys, rebooting, and see if
you get and "failed to find required DLL" popups.

If not, they are being re-created by some custom piece of BackupPC. Ask on
their mailing lists.

Max.


--
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: coredump on kill

[Brian Ford]

On Fri, 16 Jul 2004, Carlo Florendo y Flora wrote:

> Hello,
>
> Upon invoking the following command, I get a coredump:
>
> /usr/bin/kill --list
>
> By the way, "kill -l" (bash built-in) works.
>
> Attached is cygcheck's output and the dump itself.
>
> Does anyone know of a workaround?
>

I do ;-).

http://sources.redhat.com/ml/cygwin/2004-05/msg00918.html

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...

--
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: UNC Pathname Handling within Applications

[Corinna Vinschen]

On Jul 16 15:10, Thorsten Haude wrote:
> Hi,
> 
> * Corinna Vinschen wrote (2004-07-16 15:01):
> >even if I repeat other postings, please note that double slashes are
> >absolutely fine according to the standards.  Leading double slashes may
> >have a special meaning on POSIX implementations and the *well* *known*
> >Windows specific meaning is an UNC path for accessing network (CIFS)
> >shares.  Honestly, there should be no surprise in that fact to users
> >of your software.  If you really want to mangle file names in your
> >application instead of just leaving them alone, then your application
> >should honor that fact, to be *portable*.
> >
> >This isn't us being mean, as usual, that's just fact.
> 
> I already agreed that it should be supported, so what's missing?

Erm... nothing, apparently.  I must have misinterpreted your posting.

Sorry,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader  mailto:[EMAIL PROTECTED]
Red Hat, Inc.

--
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: UNC Pathname Handling within Applications

[Thorsten Haude]

Hi,

* Corinna Vinschen wrote (2004-07-16 15:01):
>even if I repeat other postings, please note that double slashes are
>absolutely fine according to the standards.  Leading double slashes may
>have a special meaning on POSIX implementations and the *well* *known*
>Windows specific meaning is an UNC path for accessing network (CIFS)
>shares.  Honestly, there should be no surprise in that fact to users
>of your software.  If you really want to mangle file names in your
>application instead of just leaving them alone, then your application
>should honor that fact, to be *portable*.
>
>This isn't us being mean, as usual, that's just fact.

I already agreed that it should be supported, so what's missing?


Thorsten
-- 
The man who does not read good books has no
advantage over the man who cannot read them.
- Mark Twain


pgpSZPnlCbLZc.pgp
Description: PGP signature

Re: maintaner of gcc

[Sam Steingold]

> * Gerrit P. Haase <[EMAIL PROTECTED]> [2004-07-16 00:58:04 +0200]:
>
> Sam schrieb:
>
>>> * Gerrit P. Haase <[EMAIL PROTECTED]> [2004-07-15 15:24:45 +0200]:
>>>
>>> What is wrong with 3.3.x release series?  Are there any serious bugs?
>>> Are there issues (for you)?  Why do you need 3.4.x?
>
>> g++ 3.3 cannot compile CLISP.
>> it is alleged that g++ 3.4 can.
>
>> (either version of gcc can compile CLISP, but g++ compile is necessary
>> for some extra bug detection).
>
>
> Which version exactly?  Is this also true for 3.3.4?  How do you build
> the packages for the Cygwin release?

Any gcc (2.95, 3.0, 3.1, 3.2, 3.3, 3.4) can compile CLISP, that's how I
build packages, that's how it is supposed to work.
Building with g++ is a way to detect internal CLISP errors, not build
production executables.


g++ 3.3 cannot build CLISP due to a bug in g++.
this bug is allegedly fixed in 3.4.

-- 
Sam Steingold (http://www.podval.org/~sds) running w2k
  
 
(let((a'(list'let(list(list'a(list'quote a)))a)))`(let((a(quote ,a))),a))

--
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: UNC Pathname Handling within Applications

[Corinna Vinschen]

On Jul 16 14:06, Thorsten Haude wrote:
> I think some people might see the surprising path, *think* the
> software is broken and stop using it. Another problem ist the toolkit.
> 
> I agree that the leading extra slash should be supported, but it might
> not be as easy as it sounds.

Thorsten,

even if I repeat other postings, please note that double slashes are
absolutely fine according to the standards.  Leading double slashes may
have a special meaning on POSIX implementations and the *well* *known*
Windows specific meaning is an UNC path for accessing network (CIFS)
shares.  Honestly, there should be no surprise in that fact to users
of your software.  If you really want to mangle file names in your
application instead of just leaving them alone, then your application
should honor that fact, to be *portable*.

This isn't us being mean, as usual, that's just fact.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader  mailto:[EMAIL PROTECTED]
Red Hat, Inc.

--
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: Whack-a-Mole: Purging Cygnus from Registry

[Corinna Vinschen]

On Jul 16 05:46, Todd Curry wrote:
> I'm using an rsyncd package that uses its own version of cygwin, and 
> does not play nice when installed on a machine with Cygwin.  It is part 
> of BackupPC, which is turning out to be an incredible piece of backup 
> software.

Please ask for support in the backupPC mailing lists.  This mailing
list is for support of the official Cygwin net release from
http://cygwin.com/ only.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader  mailto:[EMAIL PROTECTED]
Red Hat, Inc.

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

Whack-a-Mole: Purging Cygnus from Registry

[Todd Curry]

I'm using an rsyncd package that uses its own version of cygwin, and 
does not play nice when installed on a machine with Cygwin.  It is part 
of BackupPC, which is turning out to be an incredible piece of backup 
software.

So, I've got one Windows XP machine that is seemingly possessed -- I 
have removed the cygwin dir, have triple-checked running processes and 
services and don't see anything that I *think* is Cygwin related.

But here is the kicker:  no matter how (or how many) times I purge the 
"Cygnus Solutions" entries from the XP registry, they come right back 
-- something is re-creating them.  I delete the keys, start it back up, 
and there is Cygnus again.  It is truly bizarre!

What should I check to make sure there are no processes or services 
running?  Somebody give me the "paranoid" / overkill options here.

Second, if that should fail, does anyone know what specifically creates 
the registry entries?  Can we work backwards from there to find the 
culprit?

Thanks much,
Todd
--
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/

Svwgv Imm.E`diate Acc_ess To Va~.l1um..X.A`_nax..Bu-.spar.. 0ve_-rnite To Your D_`00r

[jude fontenot]

canon beheersers bedrinkt


Can.`a'`da dr,`ugs & fast shi_.ppi~ng

K ` R http://tq.q.cnhptz.com/29/


A friend gave me the number of a lady across town who worked at home doing
alterations. I was desperate and willing to try anything, so I decided to
give her a call.
How many of us get snowballed by what a man says to us? All those sweet
nothings he whispers, the perfect comment at the perfect moment, and the
feelings those words give us. But how many of us actually put more weight or
at least equal weight on what they display for actions? I¡¯d venture to say
not many of us. 
frambuesa6murria02zorito,subvertir navajada.  


--
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: UNC Pathname Handling within Applications

[Thorsten Haude]

Hi,

please send me every mail only once. Thanks.

* Larry Hall wrote (2004-07-16 04:21):
>At 07:30 PM 7/15/2004, you wrote:
>>* Shankar Unni wrote (2004-07-16 00:52):
>>>Thorsten Haude wrote:
- Is there any standard way to approach this problem? Has it come up
before in other applications?
>>>
>>>I don't know why you are even trying to normalize the paths like this. 
>>>Just hand the thing off to the OS. Usually, both the user and the OS 
>>>know what it is they are trying to do.
>>
>>The path is also displayed at various places. The user might be
>>surprised to see surplus slashes.
>
>Better that they be surprised and have things work than be surprised and
>complain when things don't work.  Don't shield them from the reality of the
>real world.  It's a learning experience and depriving them of that won't
>help anyone.

I think some people might see the surprising path, *think* the
software is broken and stop using it. Another problem ist the toolkit.

I agree that the leading extra slash should be supported, but it might
not be as easy as it sounds.


>That ends the philosophy lesson for today.  Please go back to your homes
>now and meditate on this. ;-)

Thank you, O wise one!


Thorsten
-- 
As we enjoy great advantages from the inventions of others we should
be glad of an opportunity to serve others by any invention of ours,
and this we should do freely and generously.
- Benjamin Franklin


pgppd4EowdbIM.pgp
Description: PGP signature

Re: [BUG] mprotect() on Windows NT 5+

[Corinna Vinschen]

On Jul 15 23:10, Xavier Joubert wrote:
> Selon Corinna Vinschen:
> >   I've checked in a fix, so that mprotect tests for
> > the original protection mode of the first page in the area, and uses
> > READWRITE or WRITECOPY, whichever matches the original protection.
> 
> Whow! That's amazing! I didn't expect to get a reply today. Even less a fix
> commited to CVS. If all bugs last only 51 minutes in Cygwin, this software will
> quickly become perfect!
> 
> Thanks _a lot_ Corinna !

You're welcome. 

Simple testcases like yours make bug fixing way easier *hint*


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader  mailto:[EMAIL PROTECTED]
Red Hat, Inc.

--
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: ssmtp man page (Was: Re: sending email from Cygwin)

[Corinna Vinschen]

On Jul 16 12:01, [EMAIL PROTECTED] wrote:
> On 15 Jul, Corinna Vinschen wrote:
> >  > Incidentally is it appropriate to include Cygwin-port-specific  
> >  > information in a man page? 
> >   
> >  Well, from a user perspective it might be cool, but IMHO the original 
> >  man page shouldn't be changed, unless it's a change which should be 
> >  send upstream anyway.  We have the Cygwin specific documentation in 
> >  /usr/share/doc/Cygwin (resp. /usr/doc/Cygwin in earlier releases) for 
> >  a long time now.  It should be not too hard to ask users to look there 
> >  for Cygwin specific docs. 
> >   
> >   
> >  Corinna 
> 
> Can you think of a way of incorporating the material in the man page
> that would be palatable upstream?  How do you think people would feel
> about a section "PORTABILITY" or "NOTES" or even "WINDOWS" or "CYGWIN"?

I have no idea.  That's something you would have to ask the upstream
maintainer.  But the first question is if the Cygwin maintainer likes
the idea.

> The above question is relevant to a patch for the ssmtp man page.  If
> ssmtp uses ssmtp-config on most platforms it works on, then I can just
> write a patch that includes both fixes.

ssmtp-config is a Cygwin specific script.

> This is a usability issue.  It's hard enough to teach people to type:
> 
>   man 
> 
> teaching them to type:
> 
>   more /usr/share/doc/Cygwin/ssmtp-0.x.y/README.ssmtp-0.x.y

Don't make it overly complicated.  `less /usr/share/doc/Cygwin/ssmtp*'
is enough.  And telling people that /usr/share/doc/Cygwin contains
Cygwin specific README files isn't that hard, really.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Co-Project Leader  mailto:[EMAIL PROTECTED]
Red Hat, Inc.

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

[ANNOUNCEMENT] New package: cppunit-1.9.14-1

[Harold L Hunt II]

The package 'cppunit' is now available with the Cygwin
distribution.

Description
===
CppUnit is a C++ unit testing framework.  It started its life as a port 
of JUnit to C++ by Michael Feathers.

--
Harold Hunt

***

To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.

If you have questions or comments, please send them to the Cygwin
mailing list at: [EMAIL PROTECTED] .

   *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

[EMAIL PROTECTED]

If you need more information on unsubscribing, start reading here:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.

***


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

[ANNOUNCEMENT] Updated: distcc-2.16-1

[Harold L Hunt II]

The distcc-2.16-1 package has been updated in the Cygwin distribution.

Changes
===
1) Resync with upstream release.

--
Harold Hunt

***

To update your installation, click on the "Install Cygwin now" link on
the http://cygwin.com/ web page.  This downloads setup.exe to your
system.  Then, run setup and answer all of the questions.

If you have questions or comments, please send them to the Cygwin
mailing list at: [EMAIL PROTECTED] .

   *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***

If you want to unsubscribe from the cygwin-announce mailing list, look
at the "List-Unsubscribe: " tag in the email header of this message.
Send email to the address specified there.  It will be in the format:

[EMAIL PROTECTED]

If you need more information on unsubscribing, start reading here:

http://sources.redhat.com/lists.html#unsubscribe-simple

Please read *all* of the information on unsubscribing that is available
starting at this URL.

***


--
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: gcc 3.3.1-3 runtime error: static data storage size

[Gerrit P. Haase]

Pietro schrieb:

> Gerrit,

> I think you just did:

> the program should print "ok" upon executing and it didn't. if you debug,
> say, with insight, aa.exe will bail before reaching the printf statement,
> generating a segmentation violation signal.

> let me know. thanks for looking into it.

> Pietro

> On Fri, 16 Jul 2004, Gerrit P. Haase wrote:

>> Pietro wrote:
>>
>> > I have the following example to propose:
>> > /** aa.c **/
>> > #define NXY 5000
>> > #define NXY 7000
>> > int xy[NXY][NXY];
>> > main(){
>> > printf("ok\n");
>> > }
>>
>> > This will work when NXY=5000, but will generate a SIGSEV exception before
>> > reaching the first statement when NXY=7000.
>>
>> > The array in the faulty case is 187MB. The gcc documentation gives 2GB as
>> > the limit for having to switch to dynamic allocation. Any fixes? or
>> > relevant compiler options possibly available?
>>
>> I cannot reproduce it on my W2K Professional box:
>>
>>
>> $ cat aa.c
>> #define NXY 7000
>>
>> int xy[NXY][NXY];
>> main(){
>> printf("ok\n");
>> }
>>
>> $ gcc -o aa aa.c
>>
>> $ ./aa.exe
>>
>> Gerrit
>> --
>> =^..^= http://nyckelpiga.de/donate.html
>>

Yes, I see.  Yhe problem is the default stack size on cygwin (2 MB), you
can increase it.

$ gcc -o aa -Wl,--stack,8388608 aa.c

$ ./aa
ok

$ cat aa.c
#define NXY 7000

int xy[NXY][NXY];
main(){
printf("ok\n");
}


Gerrit
-- 
=^..^=


--
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: mmap bug on Windows 9x

[Anton Ertl]

Anton Ertl wrote:
> 
> On Windows 9x/ME different calls to mmap sometimes produce the same
> address (without that memory being unmapped in the meantime, at least
> not by application code).

You find a condensed test program below.

On Windows ME with cygwin1.dll 1.5.10 it outputs:

try mmap($0, $4, ..., MAP_ANON, ...); success, address=$833ca000
try mmap($8340b000, $4, ..., MAP_ANON, ...); success, address=$833ca000

Note that the result addresses are the same.

On Windows 2000 with cygwin1.dll 1.3.22 it outputs:

try mmap($0, $4, ..., MAP_ANON, ...); success, address=$64
try mmap($681000, $4, ..., MAP_ANON, ...); success, address=$68

i.e., non-overlapping memory ranges, as it should.

I believe that this is a problem that both cygwin1.dlls have on
Windows ME/9x (and not on NT/2K/XP), not something arising from the
difference between cygwin versions (we see a problem that probably
arises from this bug also with the Gforth-for-Windows package that
includes cygwin1.dll 1.3.22).

- anton

Here's the test program (compile and run with "gcc -O main.c; ./a):
-
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#ifndef STANDALONE
#include 
#endif
#include 
#include 
#include 
#include 
#ifndef STANDALONE
#include 
#endif

int debug=1;
#define HAVE_MMAP
typedef char *Address;
typedef int Cell;
int pagesize=4096;

static Address next_address=0;
void after_alloc(Address r, Cell size)
{
  if (r != (Address)-1) {
if (debug)
  fprintf(stderr, "success, address=$%lx\n", (long) r);
if (pagesize != 1)
  next_address = (Address)(Cell)r)+size-1)&-pagesize)+2*pagesize); /* leave 
one page unmapped */
  } else {
if (debug)
  fprintf(stderr, "failed: %s\n", strerror(errno));
  }
}

#ifndef MAP_FAILED
#define MAP_FAILED ((Address) -1)
#endif
#ifndef MAP_FILE
# define MAP_FILE 0
#endif
#ifndef MAP_PRIVATE
# define MAP_PRIVATE 0
#endif
#if !defined(MAP_ANON) && defined(MAP_ANONYMOUS)
# define MAP_ANON MAP_ANONYMOUS
#endif

#if defined(HAVE_MMAP)
static Address alloc_mmap(Cell size)
{
  Address r;

#if defined(MAP_ANON)
  if (debug)
fprintf(stderr,"try mmap($%lx, $%lx, ..., MAP_ANON, ...); ", (long)next_address, 
(long)size);
  r = mmap(next_address, size, PROT_EXEC|PROT_READ|PROT_WRITE, MAP_ANON|MAP_PRIVATE, 
-1, 0);
#else /* !defined(MAP_ANON) */
  /* Ultrix (at least) does not define MAP_FILE and MAP_PRIVATE (both are
 apparently defaults) */
  static int dev_zero=-1;

  if (dev_zero == -1)
dev_zero = open("/dev/zero", O_RDONLY);
  if (dev_zero == -1) {
r = MAP_FAILED;
if (debug)
  fprintf(stderr, "open(\"/dev/zero\"...) failed (%s), no mmap; ", 
  strerror(errno));
  } else {
if (debug)
  fprintf(stderr,"try mmap($%lx, $%lx, ..., MAP_FILE, dev_zero, ...); ", 
(long)next_address, (long)size);
r=mmap(next_address, size, PROT_EXEC|PROT_READ|PROT_WRITE, MAP_FILE|MAP_PRIVATE, 
dev_zero, 0);
  }
#endif /* !defined(MAP_ANON) */
  after_alloc(r, size);
  return r;  
}
#endif

int main(int argc, char **argv, char **env)
{
  debug=1;
  alloc_mmap(0x4);
  alloc_mmap(0x4);
  exit(0);
}

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