RE: Graduate Student needs help/information.

[Ross Boulet]

> On Mon, Feb 14, 2005 at 08:59:37PM -0600, Nick Leeson
> wrote:
> >Hello All,
> >I am a graduate student researching the Open Source
> Development Model.
> >For my emperical study, I need a list of core cygwin
> developers and/or
> >maintainers. I would use this list to parse through the
> messages in
> >the mailing lists and compute statistics of interest. Can
> someone
> >provide me a pointer to where I can get this list.
> Usually this list
> >is found in the  MAINTAINERS file in the sources, but I
> could not find
> >any such file. I downloaded the sources via CVS but it
> was not of much
> >help.Can somebody help me?  I would really appreciate.
> 
> http://cygwin.com/who.html
> 
> cgf
> 
There are a couple of bad links on the above referenced
page.  The "free software projects" in the 6th paragraph and
the "GNUPro Toolkit" link in the last paragraph don't work
for me.

Ross

--

I was going to buy a copy of "The Power of Positive
Thinking," and then I thought: What the hell good would that
do? 




--
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: insensitive case problem in latest cygwin

[Jason Taylor]

Funny.  I've routinely used cygwin to rename the files from my digital
camera before uploading them just using a mv command.  I'm on a NTFS
file system under both Windows 2000 and Win XP and, before this latest
version of cygwin the mv worked fine.  (obviously the problem isn't
limited to mv)

Now I get:

[EMAIL PROTECTED] ~
$ touch AAA

[EMAIL PROTECTED] ~
$ mv AAA aaa
mv: `AAA' and `aaa' are the same file

[EMAIL PROTECTED] ~
$ uname -a
CYGWIN_NT-5.1 jasont-laptop 1.5.12(0.116/4/2) 2004-11-10 08:34 i686
unknown unknown Cygwin
.

Since it sounds like it is uncommon to have filenames that are case
sensitive under cygwin I'll just assume it won't work and script
around it.

Thanks,
  Jason


On Mon, 14 Feb 2005 13:45:04 -0500 (EST), Igor Pechtchanski
<[EMAIL PROTECTED]> wrote:
> On Mon, 14 Feb 2005, Jason Taylor wrote:
> 
> > windows xp
> > The current version of cygwin seems to ignore case in the filesystem.
> > if you open a cygwin bash shell and type
> >
> > touch AAA
> > mv AAA aaa
> >
> > it says that 'AAA' and 'aaa' are the same filename and doesn't change
> > the filename.
> 
> That's the behavior I've gotten for as long as I can remember, which
> prompted me to write this useful script:
> --- BEGIN /usr/local/bin/mvv ---
> #!/bin/sh
> /bin/mv "${1%%/}" "${1%%/}-$$" && mv "${1%%/}-$$" "${2%%/}"
>  END /usr/local/bin/mvv 
> 
> > When I run cygwin setup and go back to the 'prev' version the mv
> > command changes the name of the file like it has in previous versions.
> 
> Very strange.  What version was the 'prev' version?
> 
> > Sorry I can't get version numbers right now but it's Valentine's day.
> >  - jason
> 
> Oh, and neither 'uname -a' nor 'cygcheck -svr' run on Valentine's day?
> Why, that's just MEAN! :-)
>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!
> 
> "The Sun will pass between the Earth and the Moon tonight for a total
> Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT
>

--
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: Re: Graduate Student needs help/information.

[Christopher Faylor]

On Mon, Feb 14, 2005 at 10:29:46PM -0600, Nick Leeson wrote:
>Thank you Chris for your reply. May I consider the people mentioned in
>the webpage
>>http://cygwin.com/who.html
>as the official maintainers ? I had a feeling that this webpage was
>kind of informal, but then I can be wrong!!

cygwin.com is the definitive source for information on the cygwin
project.  That's why I pointed you there.

There are just two official maintainers of the cygwin DLL.  The other
contributors to the DLL are volunteers who require approval from me or
Corinna before checking anything in.

OTOH, if by "cygwin" you mean more than just the cygwin DLL and want to
include the list of all of the package maintainers as well, then, no,
that list does not include those people.  You can find who supports what
by perusing the cygwin-announce archives.  We don't publish a list of
all of the package maintainers.

If none of the above makes any sense to you then, presumably, you have
more research to do about how things work around here.  The cygwin web
site should have all of the information that you need.

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: Re: Graduate Student needs help/information.

[Nick Leeson]

Thank you Chris for your reply. May I consider the people mentioned in
the webpage
>http://cygwin.com/who.html
as the official maintainers ? I had a feeling that this webpage was
kind of informal, but then I can be wrong!!
-Nick

--
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: Graduate Student needs help/information.

[Christopher Faylor]

On Mon, Feb 14, 2005 at 08:59:37PM -0600, Nick Leeson wrote:
>Hello All,
>I am a graduate student researching the Open Source Development Model.
>For my emperical study, I need a list of core cygwin developers and/or
>maintainers. I would use this list to parse through the messages in
>the mailing lists and compute statistics of interest. Can someone
>provide me a pointer to where I can get this list. Usually this list
>is found in the  MAINTAINERS file in the sources, but I could not find
>any such file. I downloaded the sources via CVS but it was not of much
>help.Can somebody help me?  I would really appreciate.

http://cygwin.com/who.html

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/

Graduate Student needs help/information.

[Nick Leeson]

Hello All,
I am a graduate student researching the Open Source Development Model.
For my emperical study, I need a list of core cygwin developers and/or
maintainers. I would use this list to parse through the messages in
the mailing lists and compute statistics of interest. Can someone
provide me a pointer to where I can get this list. Usually this list
is found in the  MAINTAINERS file in the sources, but I could not find
any such file. I downloaded the sources via CVS but it was not of much
help.Can somebody help me?  I would really appreciate.

-Nick

--
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: FW: sshd "ssh_exchange_identification: Connection closed by remote host" until restarted

[David Christensen]

Tom Rodman wrote:
...
> 823973892 [main] sshd 1376 fork_copy: linked dll data/bss pass 0
> failed,
>  0x45E000..0x45F250, done 0, windows pid 2448, Win32 error 487
>  238 [main] sshd 804 fork_copy: linked dll data/bss pass 0
> failed,
>  0x33E000..0x33F250, done 0, windows pid 3516, Win32 error 487

Hmmm...  I seem to recall the cure for Cygwin fork() failure is rebaseall:

[EMAIL PROTECTED]:~$ net stop sshd
The CYGWIN sshd service is stopping.
The CYGWIN sshd service was stopped successfully.

[EMAIL PROTECTED]:~$ net stop exim
The Exim Mail Transfer Agent service is stopping.
The Exim Mail Transfer Agent service was stopped successfully.

[EMAIL PROTECTED]:~$ net stop cron
The Cron daemon service is stopping.
The Cron daemon service was stopped successfully.

[EMAIL PROTECTED]:~$ rebaseall
[EMAIL PROTECTED]:~$


Restart.  Test sshd, cron, and exim -- everything works!


Thanks!

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: What has changed in cygwin's memory access?

[Charles D. Russell]

I wrote:
Using a version of cygwin installed around April of '03 I could increase 
the stack size with  gcc flag -Wl,--stack to 256 Mb, but now, on the 
same machine (512 Mb RAM, Windows XP Pro) I can get only 150 Mb using a 
recent cygwin download. What has changed in memory usage since April '03?
_

I reinstalled the prior version of cygwin but cannot duplicate the 
behavior I observed before. (Still having problems with g77, too.)  
Could this be related to upgrading Windows XP to SP2?

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

Re: Bash error in quote handling

[Arthur I Schwarz]

Igor;

Thank your for your explanation.

art




  
  Igor  
  
  Pechtchanski To:  Arthur I Schwarz 
<[EMAIL PROTECTED]>  
  <[EMAIL PROTECTED] cc:  cygwin@cygwin.com 

  .edu>Subject: Re: Bash error in quote 
handling  

  
  02/14/2005 03:02  
  
  PM
  
  Please respond
  
  to cygwin 
  

  

  



On Mon, 14 Feb 2005, Arthur I Schwarz wrote:

> I think this is an error?

Huh?  What is?  What exactly are the commands you're trying to run?  What
exactly is the output?  What is wrong with the output?

Let me try to guess (below):

>  a. star="*"; echo $star
>  b. star=*;   echo $star

You're saying that the above commands produce the contents of the
directory, and that this is correct.

>  c. star='*'; echo $star
>  d. star=\*;  echo $star

The above commands produce the contents of the directory, and you think
this is incorrect (should be a literal "*").

>  e. star='\*'; echo $star
>  f. star="\*"; echo $star

The above commands produce the string "\*", and you think it should be
"*".

AFAIK, the above is all expected behavior.

The first four commands (a.-d.) set the variable "star" to the same exact
value, namely, the literal "*".  When the shell sees $star, it expands the
contents of it (which is a "*" wildcard), so you get the contents of the
directory.  The manner of quoting you used when assigning the value of the
variable is irrelevant.

If you want echo to produce a literal "*", use 'echo "$star"' (double
quotes to allow variable substitution but prevent shell expansion).

Frankly, at the moment I can't think of a reason why the last two commands
produce "\*" (it's not a nullglob issue, as I first thought).  I'm
reasonably sure it's also expected, but I'll investigate the actual reason
later.
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!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT




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

Re: Bash error in quote handling

[Igor Pechtchanski]

On Mon, 14 Feb 2005, Arthur I Schwarz wrote:

> I think this is an error?

Huh?  What is?  What exactly are the commands you're trying to run?  What
exactly is the output?  What is wrong with the output?

Let me try to guess (below):

>  a. star="*"; echo $star
>  b. star=*;   echo $star

You're saying that the above commands produce the contents of the
directory, and that this is correct.

>  c. star='*'; echo $star
>  d. star=\*;  echo $star

The above commands produce the contents of the directory, and you think
this is incorrect (should be a literal "*").

>  e. star='\*'; echo $star
>  f. star="\*"; echo $star

The above commands produce the string "\*", and you think it should be
"*".

AFAIK, the above is all expected behavior.

The first four commands (a.-d.) set the variable "star" to the same exact
value, namely, the literal "*".  When the shell sees $star, it expands the
contents of it (which is a "*" wildcard), so you get the contents of the
directory.  The manner of quoting you used when assigning the value of the
variable is irrelevant.

If you want echo to produce a literal "*", use 'echo "$star"' (double
quotes to allow variable substitution but prevent shell expansion).

Frankly, at the moment I can't think of a reason why the last two commands
produce "\*" (it's not a nullglob issue, as I first thought).  I'm
reasonably sure it's also expected, but I'll investigate the actual reason
later.
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!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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

Bash error in quote handling

[Arthur I Schwarz]

I think this is an error?

 star="*"
 echo $star  ==  looks good
 star=*
 echo $star  ==  looks good

 star='*'
 echo $star  ==  shouldn't this be *?
 star=\*
 echo $star  ==  shouldn't this be *?
 star='\*'
 echo $star  == \* shouldn't this be *?
 star="\*"
 echo $star  == \* shouldn't this be *?

bash 2.0.5b
Cygwin 1.5.9-1


--
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: insensitive case problem in latest cygwin

[Igor Pechtchanski]

On Mon, 14 Feb 2005, Mark Paulus wrote:

> On Mon, 14 Feb 2005 13:45:04 -0500 (EST), Igor Pechtchanski wrote:
>
> >On Mon, 14 Feb 2005, Jason Taylor wrote:
>
> >> windows xp
> >> The current version of cygwin seems to ignore case in the filesystem.
> >> if you open a cygwin bash shell and type
> >>
> >> touch AAA
> >> mv AAA aaa
> >>
> >> it says that 'AAA' and 'aaa' are the same filename and doesn't change
> >> the filename.
>
> >That's the behavior I've gotten for as long as I can remember,
> >[snip]
>
> H
>
> My understanding of Windows implementation of Filesystems
> is that they MIGHT preserve case, but they are not Case
> sensitive.  Which is apparently what lead to the whole thing
> about creating managed filesystems, which not only preserve
> case, but are also Case Sensitive (as opposed to case
> sensitive).  I would be really shocked if your mv AAA aaa worked
> on an unmanaged filesystem, and if it did, could you verify what
> kind of filesystem you are working on?

I hope you're asking the original poster, as I've never claimed that "mv
AAA aaa" worked for me (quite the opposite, in fact).
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!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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

mkfs.jffs2 for Windows

[Brandon S Johnson]

Hello,

I have been searching the mailing lists and the web for a version of 
mkfs.jffs2 that will run on Windows.  I do not believe one is available, 
as the version available at 
http://cygwin.mirrors.pair.com/jffs2/mkfs.jffs2  appears to be a Linux 
executable.  Is there a version for cygwin that runs on a Windows 
platform?  Thanks in advance for any help you can provide.

Best Regards,

Brandon Johnson




--
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: snapshots are breaking shred

[Eric Blake]

Corinna Vinschen  cygwin.com> writes:
> > With coreutils 5.3.0-2 and various snapshots, I am seeing regressions in 
shred(1)caused by cygwin changes:
> 
> As far as fsync is affected, I don't see how that could ever fail, except
> the Windows call fails for some reason.  The fsync code hasn't changed
> for quite some time.

I found what is causing this.  Coreutils shred uses the following code:
int dir_fd = open (dir, O_WRONLY | O_NOCTTY);
if (dir_fd < 0)
  dir_fd = open (dir, O_RDONLY | O_NOCTTY);
...
fsync (dir_fd);

POSIX requires that open fail with EISDIR on open with O_WRONLY or O_RDWR on a 
directory, and you implemented that in a patch on Jan 6.  So with 1.5.12, shred 
got a writeable fd from the first open, but with snapshots after Jan 6 it has 
only a readable fd from the second open.  But fsync() is implemented with 
FlushFileBuffers, which requires write access to the handle it is about to 
flush, so it now fails with EACCES.

I don't know if it is better to patch open_fs() to additionally grant 
GENERIC_WRITE access when opening directories as O_RDONLY (since that is the 
only way to open a directory), or to patch fsync() to temporarily grant write 
access to a directory for the duration of the flush.  But it is a definite 
regression from 1.5.12 that should be fixed.

I also think that fsync() could be patched to return EINVAL on non-directory 
file descriptors that were opened as O_RDONLY, rather than performing a failed 
FlushFileBuffers and getting EACCES, as a closer match to the errors allowed by 
POSIX.  http://www.opengroup.org/onlinepubs/009695399/functions/fsync.html

--
Eric Blake



--
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: insensitive case problem in latest cygwin

[Mark Paulus]

H

My understanding of Windows implementation of Filesystems 
is that they MIGHT preserve case, but they are not Case
sensitive.  Which is apparently what lead to the whole thing
about creating managed filesystems, which not only preserve
case, but are also Case Sensitive (as opposed to case 
sensitive).  I would be really shocked if your mv AAA aaa worked
on an unmanaged filesystem, and if it did, could you verify what
kind of filesystem you are working on?

On Mon, 14 Feb 2005 13:45:04 -0500 (EST), Igor Pechtchanski wrote:

>On Mon, 14 Feb 2005, Jason Taylor wrote:

>> windows xp
>> The current version of cygwin seems to ignore case in the filesystem.
>> if you open a cygwin bash shell and type
>>
>> touch AAA
>> mv AAA aaa
>>
>> it says that 'AAA' and 'aaa' are the same filename and doesn't change
>> the filename.

>That's the behavior I've gotten for as long as I can remember, which
>prompted me to write this useful script:
>--- BEGIN /usr/local/bin/mvv ---
>#!/bin/sh
>/bin/mv "${1%%/}" "${1%%/}-$$" && mv "${1%%/}-$$" "${2%%/}"
> END /usr/local/bin/mvv 

>> When I run cygwin setup and go back to the 'prev' version the mv
>> command changes the name of the file like it has in previous versions.

>Very strange.  What version was the 'prev' version?

>> Sorry I can't get version numbers right now but it's Valentine's day.
>>  - jason

>Oh, and neither 'uname -a' nor 'cygcheck -svr' run on Valentine's day?
>Why, that's just MEAN! :-)
>   Igor
>-- 
>   http://cs.nyu.edu/~pechtcha/
>  |\  _,,,---,,_   [EMAIL PROTECTED]
>ZZZzz /,`.-'`'-.  ;-;;,_   [EMAIL PROTECTED]
> |,4-  ) )-,_. ,\ (  `'-'  Igor Pechtchanski, Ph.D.
>'---''(_/--'  `-'\_) fLa.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

>"The Sun will pass between the Earth and the Moon tonight for a total
>Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

>--
>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: Packages question

[Joshua Daniel Franklin]

On Mon, 14 Feb 2005 18:37:36 +, Christopher Benson-Manica  wrote:
> I'm trying to figure out which Cygwin packages correspond to the
> sgml-common and xml-common Redhat packages.  Does the OpenSP package
> encompass both of these packages, or do I need to install some
> additional packages?

There's just a different packaging scheme, they don't really correspond.
OpenSP has some of stuff, xsltproc has some, and some just isn't packaged
for Cygwin.

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

Re: cygwin SFTP utilities? and another question

[Joshua Daniel Franklin]

On Sun, 13 Feb 2005 22:58:06 + (UTC), Christopher Thomas  wrote:
> Also, because of my lack of knowledge in this enviromnet, I have no idea what
> I can do with cygwin. I find traversing the realm os cygwin.com very hard as
> most of it is way over my head.
> 
> Is there some "beginners" information that I can get on cygwin and what I can
> do with what I installed or what I can install. I followed the very basic
> installation instructions to achieve being able to use the SFTP server.

Cygwin is not really meant to be a teaching tool for Unix-like systems, so I can
see why you might find the website confusing. However, there are a lot of good 
tutorials about learning Unix out there. I would recommend searching the web
for "new to unix" or "unix tutorial" for the very basics with a couple caveats:

1. Ignore anything about logging in
2. Ignore anything about installing packages (you know how to use
setup.exe already)
2. Ignore most things about mounting filesystems (use 'mount --help' instead)


For more advanced topics, you might try getting some Oreilly books and trying
things out. Learn some python or perl. Build some simple packages from source.
Have fun!

--
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: insensitive case problem in latest cygwin

[Igor Pechtchanski]

On Mon, 14 Feb 2005, Jason Taylor wrote:

> windows xp
> The current version of cygwin seems to ignore case in the filesystem.
> if you open a cygwin bash shell and type
>
> touch AAA
> mv AAA aaa
>
> it says that 'AAA' and 'aaa' are the same filename and doesn't change
> the filename.

That's the behavior I've gotten for as long as I can remember, which
prompted me to write this useful script:
--- BEGIN /usr/local/bin/mvv ---
#!/bin/sh
/bin/mv "${1%%/}" "${1%%/}-$$" && mv "${1%%/}-$$" "${2%%/}"
 END /usr/local/bin/mvv 

> When I run cygwin setup and go back to the 'prev' version the mv
> command changes the name of the file like it has in previous versions.

Very strange.  What version was the 'prev' version?

> Sorry I can't get version numbers right now but it's Valentine's day.
>  - jason

Oh, and neither 'uname -a' nor 'cygcheck -svr' run on Valentine's day?
Why, that's just MEAN! :-)
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!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

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

Packages question

[Christopher Benson-Manica]

I'm trying to figure out which Cygwin packages correspond to the
sgml-common and xml-common Redhat packages.  Does the OpenSP package
encompass both of these packages, or do I need to install some
additional packages?

-- 
Christopher Benson-Manica
ataru(at)sdf.lonestar.org

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

insensitive case problem in latest cygwin

[Jason Taylor]

windows xp

The current version of cygwin seems to ignore case in the filesystem.

if you open a cygwin bash shell and type

touch AAA
mv AAA aaa

it says that 'AAA' and 'aaa' are the same filename and doesn't change
the filename.

When I run cygwin setup and go back to the 'prev' version the mv
command changes the name of the file like it has in previous versions.

Sorry I can't get version numbers right now but it's Valentine's day.

 - jason

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

mkpasswd -d generates an error: [31] A device attached to the system is not functioning.

[Weiqi Gao]

Hi,

I'm getting the following error when I run "mkpasswd -l -d > /etc/passwd":

mkpasswd: [31] A device attached to the system is not functioning.

Where do I look for a explanation or a fix or a workaround to the problem?

We just went through some big changes here at work, the details of
which I know little.  All I've heard is that we are using Samba
instead of Windows now.

Thanks,
-- 
Weiqi Gao (éäå)
[EMAIL PROTECTED]
http://www.weiqigao.com/blog/

--
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: recommendations for 3rd party distributors?

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of Dick Repasky
> Sent: 14 February 2005 14:55

> Every so often a query surfaces about cygwin dll version 
> compatibility.
> What would be useful is a set of recommendations that can be 
> used by 3rd 
> party distributors of the cygwin dll to minimize the chance 
> of version 
> collisions with installed instances of cygwin and with other 
> 3rd party 
> software that is distributed with cygwin dlls.  Everyone 
> should benefit 
> from a set of recommendations: 

  Here is that set of recommendations, in full:

1)  Don't distribute your software with the cygwin dll; tell your users to
install their own cygwin environments using http://cygwin.com/setup.exe instead.

2)  That's all.

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: Installation problem on win XP SP2

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of John Morrison (Cygwin)
> Sent: 13 February 2005 10:39

[cygwin-apps snipped; this is _not_ a packaging issue]

> It is...
> 
> @ base-files
> sdesc: "A set of important system configuration and setup files"
> ldesc: "A set of important system configuration and setup files"
> category: Base
> requires: ash coreutils findutils sed grep
> 
> You *must* have deselected it some how, 


  Looking at the cygcheck output Young posted, I would have thought that *this*
bit:

--
Path:   C:\Program Files\ESTsoft\ALZip\
C:\Program Files\ESTsoft\ALZip\
--

can't be helping any, either..  Young, if that's really your PATH setting, I
don't understand how your computer could be working at all.  Try resetting your
path to 

C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem 

and re-running setup to reinstall cygwin.

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: recommendations for 3rd party distributors?

[Christopher Faylor]

On Mon, Feb 14, 2005 at 09:54:41AM -0500, Dick Repasky wrote:
>Every so often a query surfaces about cygwin dll version compatibility.
>What would be useful is a set of recommendations that can be used by 3rd 
>party distributors of the cygwin dll to minimize the chance of version 
>collisions with installed instances of cygwin and with other 3rd party 
>software that is distributed with cygwin dlls.  Everyone should benefit 
>from a set of recommendations: cygwin users will have fewer problems,
>3rd party distributors will have fewer problems, and cygwin mailing list 
>subscribers will have less mail.
>
>After searching the mailing list archives and finding Igor Pechtchanski's 
>post (http://www.cygwin.com/ml/cygwin/2003-10/msg00605.html), reading the 
>source code, tinkering and testing, I've come up with a list.  I ask 
>readers of the cygwin mailing list for comments and suggestions.  Are 
>there errors in the list that I do not see?  Do you have suggestions for 
>improving the list?
>
>The recommendations are:
>
>  1) Use a distinctly named shared memory area in the cygwin dll.
>  2) Use a distinctly named registry key for storing cygwin file system
> mount points.
>  3) Identify the origin of the cygwin dll in the cygwin dll.

Your archive searching couldn't have been too comprehensive if you think
we want to get into ways of doing this.

There are no recommendations for changing the cygwin dll.

>These changes work under the conditions that I have tested them.
>Comments?  Suggestions?

You haven't done much testing if you think those will work.  You seem to
have missed command line interactions.

If you are a 3rd party distributor, you should check for existing
installations of the dll.  If the existing version of cygwin DLL is the
same or newer than the one you want to use, then notify the user that
there is already a version on the system and that you will not be
installing a new version.

Otherwise, install your version in a standard location so that it will
survive being upgraded if a user decides to upgrade.

And, of course, unless this is a distribution which is internal to your
organization, remember to offer the user the source code to whatever
application you're providing to them.

I work for a company which distributes cygwin in the way that I've
outlined and, to the best of my knowledge, we have not had any problems
with this technique.

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/

[ANNOUNCEMENT] New_package:_Unicode_text_editor_mined_2000

[towo]

Mined 2000 - a powerful text editor with extensive Unicode and CJK
support is now available as a cygwin package.


Quoted below:
* The original release announcement.
* The mined overview.
* Link to the mined home page and download information for the 
  original source package.
(As this is the first cygwin package for mined, I am leaving out the 
overview of changes from this mail.)


To install mined on cygwin, run the cygwin setup program, 
in the "Select Packages" menu, open the "Editors" category and 
select the mined package.




 ANNOUNCEMENT

 mined 2000 release 10
 (January 2005)

Mined is a powerful text editor with a comprehensive and easy-to-use 
user interface and fast, small-footprint behaviour.

It was the first editor that provided Unicode support in a 
plain-text terminal.
It now has both extensive Unicode and CJK support offering many 
specific features and covering special cases that other editors 
are not aware of (like auto-detection features and automatic handling 
of terminal variations, or Han character information).
And basically, it is an editor tailored to efficient editing 
of plain text documents and programs, with features and interactive 
behaviour designed for this purpose.


Mined is now co-hosted at sourceforge and has a mailing list 
which can be subscribed at





Mined Overview

Good interactive features
* Intuitive user interface
* Logical and consistent concept of navigating and editing text 
  (without ancient line-end handling limitations or insert/append
confusion)
* Supports various control styles:
  Editing with command control, function key control, or menu control
  Navigation by cursor keys, control keys, mouse or scrollbar
* Comprehensive menus (driven by keyboard or mouse)
* "HOP" key paradigm doubles the number of navigation functions 
  that can be most easily reached and remembered by 
  intuitively amplifying the associated function
* Immediate adjustment if the window size is changed, in any 
  state of interaction

Versatile character encoding support
* Extensive Unicode support, including double-width and combining
characters,
  script highlighting, 
  various methods of character input support 
  (mapped keyboard input methods, mnemonic and numeric input),
  supporting CJK, Vietnamese, Hebrew, Arabic, and other scripts
* Support of bidirectional terminals, Arabic ligature joining
* East Asian character set support: handling of major CJK encodings 
  (including GB18030 and full EUC-JP with combining characters) 
  in either Unicode terminal or CJK terminal
* Support for a variety of 8 bit encodings (mapped to Unicode) 
  (with combining characters for Vietnamese and Thai)
* Support of CJK input methods by enhanced keyboard 
  mapping including multiple choice mappings (handled by a pick list
menu);
  characters in the pick list being sorted by relevance of Unicode
ranges
* Han character information with description and pronunciation
* Auto-detection of text character encoding, edits files with 
  mixed character encoding sections (e.g. mailboxes),
  transparent handling of UTF-16 encoded files
* Auto-detection of UTF-8 / CJK terminal mode and detailed features
  (like different Unicode width and combining data versions)
* Encoding support tested with:
  xterm, mlterm, hanterm, cxterm, rxvt, linux console

Many useful text editing capabilities
* Many text editing features, e.g. paragraph wrapping, 
  auto-indentation and back-tab, 
  smart quotes (with quotation marks style selection and auto-detection)

  and smart dashes
* Search and replacement patterns can have multiple lines
* Cross-session paste buffer (copy/paste between multiple 
  - even subsequent or remote - invocations of mined)
* Marker stack for quick return to previous text positions
* Multiple paste buffers (emacs-style)
* Program editing features, HTML support and syntax highlighting, 
  identifier and function definition search, also across files; 
  structure input support
* Text and program layout features; auto-indentation and 
  undent function (back-tab), numbered item justification
* Systematic text and file handling safety, avoiding loss of data
* Visible indications of special text contents 
  (TAB characters, different line-end types, character 
  codes that cannot be displayed in the current mode)
* Full binary transparent editing with visible indications 
  (illegal UTF-8 or CJK, mixed line end types, NUL characters, ...)
* Print function that works in all text encodings
* Optional emacs command mode

Small-footprint operation and portability
* Plain text mode (terminal) operation, supporting wide range of
terminals
* Instant start-up
* Runs on many platforms: Unix (Linux/Sun/HP/BSD/Mac and more),

recommendations for 3rd party distributors?

[Dick Repasky]

Every so often a query surfaces about cygwin dll version compatibility.
What would be useful is a set of recommendations that can be used by 3rd 
party distributors of the cygwin dll to minimize the chance of version 
collisions with installed instances of cygwin and with other 3rd party 
software that is distributed with cygwin dlls.  Everyone should benefit 
from a set of recommendations: cygwin users will have fewer problems,
3rd party distributors will have fewer problems, and cygwin mailing list 
subscribers will have less mail.

After searching the mailing list archives and finding Igor Pechtchanski's 
post (http://www.cygwin.com/ml/cygwin/2003-10/msg00605.html), reading the 
source code, tinkering and testing, I've come up with a list.  I ask 
readers of the cygwin mailing list for comments and suggestions.  Are 
there errors in the list that I do not see?  Do you have suggestions for 
improving the list?

The recommendations are:
  1) Use a distinctly named shared memory area in the cygwin dll.
  2) Use a distinctly named registry key for storing cygwin file system
 mount points.
  3) Identify the origin of the cygwin dll in the cygwin dll.
These recommendations require that the cygwin dll code be modified and that
the dll be recompiled.
  1) The name of the shared memory area is set in
  winsup/cygwin/include/cygwin/version.h. Change the value of the
  constant CYGWIN_VERSION_DLL_IDENTIFIER to something unique.
  Currently, it is "cygwin1".  You might change it to "acmeapp1".
  It is best to follow cygwin naming conventions: retain the number
  that is at the end of the current cygwin name.
  2) The name of the registry key tree that is used to store information
 about cygwin is also set in
 winsup/cygwin/include/cygwin/version.h. Change the value of
 the constant CYGWIN_INFO_CYGNUS_REGISTRY_NAME to something unique.
 Currently, it is "Cygnus Solutions". You might change it to
 "ACME Inc".
  3) Identifying information is included in the dll from constants
 that are defined in winsup/cygwin/include/cygwin/version.h.
 Identify your organization as the origin of the cygwin dll
 by adding a line that defines the constant
 CYGWIN_INFO_DLL_ORIGIN.  An appropriate define might be:
 #define CYGWIN_INFO_DLL_ORIGIN "www.acme.com"
 . Don't use the form "http://www.acme.com"; because it won't
 survive internal editing.
These changes work under the conditions that I have tested them. Comments? 
Suggestions?

Thanks,
Dick Repasky
-
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/

[C++ : Comparative performance] Copying files: input to output

[Alex Vinokur]

// ===
// C/C++ Program Performance Measurement
// ---
// Simple C/C++ Perfometer: Copying files (Version CF-3.0)
// ===


Tests have been performed for GNU g++/gpp compiler in
* Cygwin,
* Mingw32 interface,
* DJGPP


Links:
--
http://thread.gmane.org/gmane.comp.lang.c++.perfometer/89

http://permalink.gmane.org/gmane.comp.lang.c++.perfometer/93
http://permalink.gmane.org/gmane.comp.lang.c++.perfometer/89

http://groups-beta.google.com/group/perfo/browse_frm/thread/380ffe8e8143bb6c/e08f36ebdf45b4f3



// %
//
//Testsuites
//--
//C-01  : C-Functions getc() and putc()
//C-02  : C-Functions fgetc() and fputc()
//C-03  : C-Functions fread() and fwrite() - with const size buffer
//C-04  : C-Functions fread() and fwrite() - with max size buffer
//unix_C_05 : UNIX system call mmap // For Cygwin only
//CPP-01: istream::operator>> and ostream::operator<<
//CPP-02: streambuf::sbumpc() and streambuf::sputc()
//CPP-03: streambuf::sbumpc() and ostream::operator<<
//CPP-04: ifstream::rdbuf(), ofstream::rdbuf() and ostream::operator<<
//CPP-05: istream::read() and ostream::write() - with const size buffer
//CPP-06: istream::read() and ostream::write(), std::ostringstream, 
ostream::operator<< - with const buffer
//CPP-07: istream::readsome() and ostream::write() - with const size 
buffer
//CPP-08: istream::read() and ostream::write() - with max size buffer
//CPP-09: std::getline, std::ostringstream, ostream::operator<<
//CPP-10: istream::getline, std::ostringstream, ostream::operator<<
//CPP-11: istream::get(char) and ostream::put
//CPP-12: istream::get(char*, streamsize) , ostream::operator<< - with 
const size buffer
//CPP-13: istream::get(streambuf&)  and std::streambuf, 
ostream::operator<<
//CPP-14: std::istream_iterator, std::ostream_iterator and std::copy
//CPP-15: std::istreambuf_iterator, std::ostreambuf_iterator and 
std::copy
//CPP-16: std::istreambuf_iterator, std::ostreambuf_iterator and 
std::transform
//CPP-17: std::vector and std::copy
//
// %



-- 
 Alex Vinokur
 email: alex DOT vinokur AT gmail DOT com
 http://mathforum.org/library/view/10978.html
 http://sourceforge.net/users/alexvn







--
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: Joining

[Brian Dessent]

Godfrey Kyedza wrote:
> 
> Hi!
> 
> Wish to join the group
> 
> Godfrey

Join what?

The mailing list?  http://cygwin.com/cygwin/lists.html#available-lists
Contribute a package?  http://cygwin.com/setup.html
Patch cygwin code?  http://cygwin.com/contrib.html

All of this is outlined on the web site.

Brian

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

Joining

[Godfrey Kyedza]

Hi!
Wish to join the group
Godfrey
Technical Advisor - IT
Koncepts Unlimited
22B Nakasero Road, Nakasero - Kampala
Tel. +256 71 566 340 (Cell) +256 41 255 629 (Office) +256 41 566 340 (Home)

--
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: hyperthreading fix try #2

[Jason Tishler]

On Sun, Feb 13, 2005 at 12:09:21PM -0500, Christopher Faylor wrote:
> On Mon, Feb 14, 2005 at 01:17:03AM +1000, Nick Coghlan wrote:
> >Nick Coghlan wrote:
> >Command lines looked like (with thread and file counts filled in): $
> >python /lib/python2.4/test/test_threadedtempfile.py -t  -f
> >
> >
> >The results weren't particularly deterministic, beyond a general
> >'more threads, more files' -> 'more likely to hang'. 10 & 10 seemed
> >to do it fairly effectively although even that would occasionally
> >succeed (the default is 20 & 20).
> >
> >When it *did* hang, it was with a number of threads successfully
> >opening their files on an iteration, with the remainder of the
> >threads locking up attempting to open a new temporary file. The next
> >time around, the remaining threads would hang while attempting to
> >open the temporary file.
> >
> >The main script hangs because it is waiting for the threads to
> >terminate.
> 
> Is this a regression?

I don't know.

> Was this also problem with 1.5.12?

AFAICT, no.

However, another threaded regression test hung in 1.5.12 as indicated in
the README:

Under XP Pro SP1, Cygwin 1.5.12-1, ntsec, and NTFS, Cygwin Python
passes all tests except for following:

...
test_threaded_import (occasionally hangs)

So, maybe I was just "lucky" test_threadedtempfile did not hang when I
ran the regression test especially since it hung under 1.5.10-3.

Jason

-- 
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D  8784 1AFD E4CC ECF4 8EF6

--
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: scponly for chrooted sftp server in cygwin

[Christian Weinberger]

> > [snip]
> > and I really had to specify liberty.a manually in the Makefile:
> >
> > scponly: scponly.o helper.o
> > ${CC} ${CFLAGS} ${DEFS} -o $   scponly.o helper.o
/usr/lib/libiberty.a
> 
> FWIW, the "approved" way of doing this is
> 
>   ${CC} ${CFLAGS} ${DEFS} -o $   scponly.o helper.o -L/usr/lib 
> -liberty
> 
> HTH,
>   Igor

Thank you Igor!

I was quite sure that my solution was a bit crappy.



--
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: setup.exe fails

[a12]

Hello Brian,
Thank you for your reply.
Following your hints I:
- stopped & deactivated sshd service in Control Panel
- started setup.exe
- changed from Keep to Reinstall for all components
and setup.exe worked as expected.
Eventually I activated & started the sshd service in Control Panel.
Once again thank you very for your prompt & accurate reponse.
Brian Dessent wrote:
a12 wrote:

HOME.org = `C:\'
HOMEDRIVE = `C:'
HOMEPATH = `\Documents and Settings\magr40'
Odd that you don't have $HOME set...

k 2004/09/05 .\cygwin1.dll - os=4.0 img=1.0 sys=4.0
 "cygwin1.dll" v0.0 ts=2004/9/5 5:17
   Cygwin DLL version info:
   DLL version: 1.5.11
   DLL epoch: 19
   DLL bad signal mask: 19005
   DLL old termios: 5
   DLL malloc env: 28
   API major: 0
   API minor: 116
   Shared data: 4
   DLL identifier: cygwin1
   Mount registry: 2
   Cygnus registry name: Cygnus Solutions
   Cygwin registry name: Cygwin
   Program options name: Program Options
   Cygwin mount registry name: mounts v2
   Cygdrive flags: cygdrive flags
   Cygdrive prefix: cygdrive prefix
   Cygdrive default prefix:
   Build date: Sat Sep 4 23:17:09 EDT 2004
   Shared id: cygwin1S4

Okay, you've got cygwin1.dll v1.5.11 here...

Warning: There are multiple cygwin1.dlls on your path
I think that is due to you running cygcheck from your /usr/bin
directory, in which case cygcheck gets confused and sees it twice, since
/usr/bin and . are both in the path.  The cygcheck logic could be a
little improved here.

cygwin   1.5.12-1
However, setup seems to think that you have v1.5.12 of the dll
installed.  Try running setup, put everything at "keep", then go to just
the 'cygwin' package itself and select "reinstall".  That ought to get
the latest cygwin dll on your system, then you can run setup again a
second time and let it upgrade whatever other packages need updating. 
There are still some bugs in setup where updating both the main cygwin
dll and other packages at the same time causes it to get confused, I'm
not sure if you hit one of those cases or not.

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


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