Re: aspell

[Gareth Pearce]

On 10/12/06, Gareth Pearce
I suspect you don't have nroff installed.  If that is not the 
problem,  it works for me -


That would be too easy.  I already check that and nroff is indeed 
installed.


As for "works for" you, I suspect that you have an old version of
aspell.  I am talking about 0.60.3 and the more recent stable 0.60.4
versions.   Please download 0.60.4 and try it and let me know how it
goes.
Ahh, I missed that you were using a version of aspell you built yourself 
as was implied by the newer version number.



--Gareth, somewhat vaguely present aspell maintainer being.


I appreciate your response and with your assistance we'll find the
cause and fix it and you can be the proud maintainer of new apsell,
0.60.4 that has a lot of great features and functionality.

See the vaguely present part; cygwin is a much lower priority on my todo 
list these days, so unless there is an issue with a released package 
which I am the maintainer for, I'm pretty much absent.
If I remember correctly, releasing a new aspell will require releasing a 
new aspell-en/aspell-de - and if I remember correctly, aspell-en doesn't 
even have a maintainer at the moment.


--Gareth, *may* take some time and look at updating his packages once 
nano 2.0 is released.



--
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: [ANNOUNCEMENT] Updated: vim-7.0.122-1

[Corinna Vinschen]

On Oct 12 22:08, Igor Peshansky wrote:
> On Thu, 12 Oct 2006, Corinna Vinschen wrote:
> > > So it looks like using mixed paths (cygpath -m) would be an easy way
> > > out of this for now.
> >
> > Naah, scratch that.  Creating a mount point for $SYSTEMROOT seems the
> > better solution.
> 
> I'll go with mixed case.  The mount point for $SYSTEMROOT will either have
> to be explicitly created, or it will need to be built into cygwin1.dll.
> In the former case, it's more hassle for the user; [...]

I think the idea here was that the base-file package would create the
mount point, if /WINDOWS doesn't exist already.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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: OT: tcsh and LS_COLORS (was: Problems with 'dircolors')

[Corinna Vinschen]

On Oct 12 12:41, Matthew Woehlke wrote:
> Eric Blake wrote:
> >Oh, by the way, if you use tcsh, be aware that it also uses the LS_COLORS
> >environment variable internally, but that it does not understand quite as
> >many options as ls does and gripes about what it doesn't understand, which
> >is why I had to patch the cygwin version of LS_COLORS to silence stderr
> >during the tcsh eval.  Hopefully, a newer release of tcsh will allow me to
> >remove that hack from coreutils.
> 
> That's all? I had to build a hand-patched tcsh across our platform list 
> because the unpatched sources *won't run* if tcsh doesn't understand 
> LS_COLORS. And some csh's have the same behavior. IOW you couldn't run 
> [t]csh *at all* with the newer LS_COLORS features.
> 
> Anyway, just wondering if you've also seen this and what if anything has 
> been done to Cygwin's tcsh to cope.

Nothing.  It's a bit weird that LS_COLORS is used by coreutils and tcsh,
but it's a generic problem on all platforms.  It will be solved upstream
one way or the other.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
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 fails to run .bat file with spaces in pathname and argument

[Buchbinder, Barry \(NIH/NIAID\) [E]]

* Johnathon Jamison (Wed, 11 Oct 2006 14:11:12 -0700)
> I am having some funny behavior.  If I have a .bat file that is in a 
> directory whose pathname contains a space, and an argument is given 
> to the .bat file that has a space in it, then the .bat file fails to
run.
> Instead, I get "'xxx' is not recognized as an internal or external 
> command, operable program or batch file." where xxx is the portion of 
> the complete path to the .bat file before the first space.
>
> I am not sure why this is occurring.  Any help would be appreciated.  
> I have more specific information and a sample run below.  If I have 
> left anything out, just ask.  In particular, I am not sure which 
> version numbers would be needed, or where to find (many of) them.

The problem is, at least in part, with cmd.  cmd /? says:

  If /C or /K is specified, then the remainder of the command line after
  the switch is processed as a command line, where the following logic
is
  used to process quote (") characters:

  1.  If all of the following conditions are met, then quote
characters
  on the command line are preserved:

  - no /S switch
  - exactly two quote characters
  - no special characters between the two quote characters,
where special is one of: &<>()@^|
  - there are one or more whitespace characters between the
the two quote characters
  - the string between the two quote characters is the name
of an executable file.

  2.  Otherwise, old behavior is to see if the first character is
  a quote character and if so, strip the leading character and
  remove the last quote character on the command line,
preserving
  any text after the last quote character.

Try using short names to get rid of the first set of quotes.  Short
names still work, at least on XP.  Compare
  c:\>dir docume~1
and
  c:\>dir "Documents and Settings"

To find out the short names,
  c:\>dir /x
Or one can guess (first 6 characters + "~" + "1", or a higher digit if
the 6 characters + "~1" is already used, + "." + first 3 characters of
the extension).

Try changing the batch file from
  echo %1
to
  echo %1 %2 %3 %4 %5 %6 %7 %8 %9
That should work by getting rid of the second set of quotes, at least if
the number of arguments is less than 10.

This, also, works

  /c> echo '"c:\Documents and Settings\BBuchbinder\test.bat" "hello
world"
  exit' | u2d | cmd /k
  c:\>"c:\Documents and Settings\BBuchbinder\test.bat" "hello world"

  c:\>echo "hello world"
  "hello world"

  c:\>exit

You can leave off the "/k", but you then get extraneous text from
cmd.exe as it loads.


--
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: shopt igncr not working

[Larry Hall (Cygwin)]

On 10/12/2006, Rob Walker wrote:
If you're referring to the performance gain realized, I think it could have 
been accomplished (if not as trivially) without breaking CRLF handling.  
This seems to be indicated in other posts, ones that talk about reworking 
line parsing.



I believe the response to this is .  In other
words, if your belief is strong enough and you have the knowledge to back up
that belief, you just need the persistence to follow through on all that to
show everyone your concrete ideas.  Since we've had allot of opinionated
discussions on topics like this from the uninformed or those who lack the
conviction to actually submit a patch to back up their point of view, it's
important to realize here that patches speak louder than words (hm, PSLTW -
acronym alert? ;-) )


Actually, though, I was asking about a bigger-picture strategy.  One that 
appears to be steering Cygwin away from interoperability of the past, 
towards a more rigid interpretation of what Cygwin's suitable uses are.  Do 
you have a set of guiding principles you consult when deciding the fate of 
Cygwin?  Who do you consider Cygwin's customers to be? 



The basic strategy is that in cases where decisions have to be made between
supporting Linux-like behavior or Windows conventions, err on the side
of Linux.  Since the tools are meant to support the Linux way of doing
things, it's important they do.  Otherwise people who are looking for and
expecting this behavior are left out.  They are the ones these tools are
built to support.  That said, support for various Windows ways and conventions
are supported by default and when they don't conflict with the above.  But
when there is a conflict, Linux-like behavior is the goal.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (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: Bash fails to run .bat file with spaces in pathname and argument

[Buchbinder, Barry \(NIH/NIAID\) [E]]

Buchbinder, Barry (NIH/NIAID) wrote:
> * Johnathon Jamison (Wed, 11 Oct 2006 14:11:12 -0700)
>> I am having some funny behavior.  If I have a .bat file that is in a
>> directory whose pathname contains a space, and an argument is given
>> to the .bat file that has a space in it, then the .bat file fails to
>> run. Instead, I get "'xxx' is not recognized as an internal or
>> external command, operable program or batch file." where xxx is the
>> portion of the complete path to the .bat file before the first space.
>> 
>> I am not sure why this is occurring.  Any help would be appreciated.
>> I have more specific information and a sample run below.  If I have
>> left anything out, just ask.  In particular, I am not sure which
>> version numbers would be needed, or where to find (many of) them.
> 
> The problem is, at least in part, with cmd.  cmd /? says:
> 
>   If /C or /K is specified, then the remainder of the command line
>   after the switch is processed as a command line, where the
>   following logic is used to process quote (") characters:
> 
>   1.  If all of the following conditions are met, then quote
>   characters on the command line are preserved:
> 
>   - no /S switch
>   - exactly two quote characters
>   - no special characters between the two quote characters,
> where special is one of: &<>()@^|
>   - there are one or more whitespace characters between the
> the two quote characters
>   - the string between the two quote characters is the name
> of an executable file.
> 
>   2.  Otherwise, old behavior is to see if the first character is
>   a quote character and if so, strip the leading character and
>   remove the last quote character on the command line,
>   preserving any text after the last quote character.

> Try using short names to get rid of the first set of quotes.  Short
>   names still work, at least on XP.  Compare c:\>dir docume~1
> and
>   c:\>dir "Documents and Settings"
> 
> To find out the short names,
>   c:\>dir /x
> Or one can guess (first 6 characters + "~" + "1", or a higher digit
> if the 6 characters + "~1" is already used, + "." + first 3
> characters of the extension).  
> 
> Try changing the batch file from
>   echo %1
> to
>   echo %1 %2 %3 %4 %5 %6 %7 %8 %9
> That should work by getting rid of the second set of quotes, at least
> if the number of arguments is less than 10. 
> 
> This, also, works
> 
>   /c> echo '"c:\Documents and Settings\BBuchbinder\test.bat" "hello
>   world" exit' | u2d | cmd /k
>   c:\>"c:\Documents and Settings\BBuchbinder\test.bat" "hello world"
> 
>   c:\>echo "hello world"
>   "hello world"
> 
>   c:\>exit
> 
> You can leave off the "/k", but you then get extraneous text from
> cmd.exe as it loads.

I forgot to include cd-ing into the directory with spaces, though it
does not work as I would expect

  /c> cd '/c/Documents and Settings'
  /c/Documents and Settings/BBuchbinder> cmd /c test Hello World

  c:\Documents and Settings\BBuchbinder>echo Hello
  Hello 

That was expected; the following is not.

  /c/Documents and Settings/BBuchbinder> cmd /c test "Hello World"

  c:\Documents and Settings\BBuchbinder>echo "Hello World"
  "Hello World"

Shouldn't the double quotes be stripped off before cmd sees them?

  /c/Documents and Settings/BBuchbinder> cmd /c test '"Hello World"'

  c:\Documents and Settings\BBuchbinder>echo "\"Hello
  "\"Hello

Why is the backslash being inserted to quote the second double quote and
why is the single quote being changed into a double quote?  (Not that I
really care.)

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

emacs hangs at start, or sometime later

[ahnkle]

hi,

I am having some problems with my emacs. I have 21.2-13 installed, and recently 
it started 
locking up after some time, from ~1 hour to 3-4 hours. The window would not 
repaint. The 
emacs process usage goes up to 50%, then close to 100%, until the process is 
killed.

Then I tried rebaseall. It just brok  emacs, emacs hung at startup. I have 
re-installed 21.2.13, and ncurses (mentioned in an old post), and X packages, 
and am back to
emacs running for 'some period', then locking up.

Any ideas about where next?

And another thing...
I tried building emacs 21.2-13 from source, and it doesn't work. So far there is

  * missing/corrupt file 'emacs.pif' in the emacs-21.2.tar.gz file
  * cygwin build/install script tries to call emacs at the end of make, but 
temacs.exe 
is the file 
  * static heap exhausted message

The source file emacs-21.2-13-src.tar.bz2 has a good md5sum.

regards,
ahnkle



--
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: [ANNOUNCEMENT] Updated: vim-7.0.122-1

[Igor Peshansky]

On Fri, 13 Oct 2006, Corinna Vinschen wrote:

> On Oct 12 22:08, Igor Peshansky wrote:
> > On Thu, 12 Oct 2006, Corinna Vinschen wrote:
> > > > So it looks like using mixed paths (cygpath -m) would be an easy way
> > > > out of this for now.
> > >
> > > Naah, scratch that.  Creating a mount point for $SYSTEMROOT seems the
> > > better solution.
> >
> > I'll go with mixed case.  The mount point for $SYSTEMROOT will either
> > have to be explicitly created, or it will need to be built into
> > cygwin1.dll. In the former case, it's more hassle for the user; [...]
>
> I think the idea here was that the base-file package would create the
> mount point, if /WINDOWS doesn't exist already.

Right.  That was in the part of my message you've snipped:

On Thu, 12 Oct 2006, Igor Peshansky wrote:
> [...] And if we make it the job of /etc/postinstall/base-files-mketc.sh,
> we're depriving the user of a scarce resource -- a mount table entry
> (unless we raise the limit, but then again it won't work for older
> versions).

I'm not very much in favor of silently creating unnecessary mount points.
There were cases where it was unavoidable (in the case of XWin fonts and
textmode mounts), but in this case an extra-mount-free solution exists.

I just checked the source, and apparently the limit on the number of mount
entries is 30, not 16 (as previously stated).  Given the fact that
/cygdrive/* mounts exist outside of this limit, the mount table entries
aren't as scarce a resource as I imagined.  My mount tables have skirted
15 or so entries, but never got close to 30.

However, the only possible advantage of having that mount would be if we
could then copy the symlinks to another installation and have them work
seamlessly.  Unfortunately, given that the files that the symlinks refer
to live at different paths relative to the windows directory on different
windows versions, this is not going to happen.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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: [ANNOUNCEMENT] Updated: vim-7.0.122-1

[Christopher Faylor]

On Fri, Oct 13, 2006 at 10:18:17AM -0400, Igor Peshansky wrote:
>On Thu, 12 Oct 2006, Igor Peshansky wrote:
>> [...] And if we make it the job of /etc/postinstall/base-files-mketc.sh,
>> we're depriving the user of a scarce resource -- a mount table entry
>> (unless we raise the limit, but then again it won't work for older
>> versions).
>
>I'm not very much in favor of silently creating unnecessary mount points.
>There were cases where it was unavoidable (in the case of XWin fonts and
>textmode mounts), but in this case an extra-mount-free solution exists.
>
>I just checked the source, and apparently the limit on the number of mount
>entries is 30, not 16 (as previously stated).  Given the fact that
>/cygdrive/* mounts exist outside of this limit, the mount table entries
>aren't as scarce a resource as I imagined.  My mount tables have skirted
>15 or so entries, but never got close to 30.

I don't know who said they were 16 but, if the number of mount points
was a real problem then increasing them would be a trivial change, as
opposed to hacking at cygwin's path handling to add YA special case.

>However, the only possible advantage of having that mount would be if we
>could then copy the symlinks to another installation and have them work
>seamlessly.  Unfortunately, given that the files that the symlinks refer
>to live at different paths relative to the windows directory on different
>windows versions, this is not going to happen.

There are other benefits to creating a mount point besides copying
between different installations.  In fact, I don't recall copying
between installations being raised in this thread.

I think that it is important to investigate using known techniques for
dealing with problems before suggesting semi-drastic modifications to
the Cygwin DLL.

And, as long as I'm here, let me remind everyone that no matter what
happens we are not going to be adding anything under /dev.

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: rxvt-unicode-X: package updates to allow building with its embedded perl interpreter enabled

[Charles Wilson]

[EMAIL PROTECTED] wrote:

To allow incremental search of the scrollback buffer with
rxvt-unicode, I recently rebuilt the package with the
--enable-perl option, to include the embedded perl
interpreter required for this feature.

A few changes to the build script and Makefiles were
necessary, because the perl-specific sections had not been
tweaked to be compatible with the sandbox-type package build
process used (.build/.inst/.sinst subdirs).


...


To the rxvt-unicode-X package maintainer:
I assume you made a conscious decision not to enable the
embedded perl interpreter, due to concerns of impacted
performance and/or added dependencies, but if I'm wrong,
please feel free to incorporate these changes.


Thanks...


In any case, it might be worthwhile incorporating all of the
changes, bar the "--enable-perl" option to the configure
script, so that the package will build cleanly if a user
wants to rebuild with this option.


This is what I will do.  I really don't want to require perl at this 
time, but I'm willing to make it easy for users to compile the package 
themselves with perl support.


Thanks,
Chuck

--
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: [ANNOUNCEMENT] Updated: vim-7.0.122-1

[Igor Peshansky]

On Fri, 13 Oct 2006, Christopher Faylor wrote:

> On Fri, Oct 13, 2006 at 10:18:17AM -0400, Igor Peshansky wrote:
> >On Thu, 12 Oct 2006, Igor Peshansky wrote:
> >> [...] And if we make it the job of /etc/postinstall/base-files-mketc.sh,
> >> we're depriving the user of a scarce resource -- a mount table entry
> >> (unless we raise the limit, but then again it won't work for older
> >> versions).
> >
> >I'm not very much in favor of silently creating unnecessary mount points.
> >There were cases where it was unavoidable (in the case of XWin fonts and
> >textmode mounts), but in this case an extra-mount-free solution exists.
> >
> >I just checked the source, and apparently the limit on the number of mount
> >entries is 30, not 16 (as previously stated).  Given the fact that
> >/cygdrive/* mounts exist outside of this limit, the mount table entries
> >aren't as scarce a resource as I imagined.  My mount tables have skirted
> >15 or so entries, but never got close to 30.
>
> I don't know who said they were 16 but, if the number of mount points
> was a real problem then increasing them would be a trivial change, as
> opposed to hacking at cygwin's path handling to add YA special case.

The problem is that it would not fix the older versions of Cygwin, which
would still have a smaller number of mount table entries.  However, I
wasn't proposing hacking on the DLL at all.

> >However, the only possible advantage of having that mount would be if we
> >could then copy the symlinks to another installation and have them work
> >seamlessly.  Unfortunately, given that the files that the symlinks refer
> >to live at different paths relative to the windows directory on different
> >windows versions, this is not going to happen.
>
> There are other benefits to creating a mount point besides copying
> between different installations.  In fact, I don't recall copying
> between installations being raised in this thread.
>
> I think that it is important to investigate using known techniques for
> dealing with problems before suggesting semi-drastic modifications to
> the Cygwin DLL.
>
> And, as long as I'm here, let me remind everyone that no matter what
> happens we are not going to be adding anything under /dev.

Ah, I see how what I said above could be misconstrued as an argument in
favor of fixed /cygdrive prefixes or filesystems under /dev.  I should
have been clearer -- the "extra-mount-free" solution I was referring to
was the use of mixed-case paths in base-files-mketc.sh (a 3-line change).
This keeps vim happy, and does not require any other changes to any part
of Cygwin.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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: OT: tcsh and LS_COLORS

[Matthew Woehlke]

Corinna Vinschen wrote:

On Oct 12 12:41, Matthew Woehlke wrote:

Eric Blake wrote:

Oh, by the way, if you use tcsh, be aware that it also uses the LS_COLORS
environment variable internally, but that it does not understand quite as
many options as ls does and gripes about what it doesn't understand, which
is why I had to patch the cygwin version of LS_COLORS to silence stderr
during the tcsh eval.  Hopefully, a newer release of tcsh will allow me to
remove that hack from coreutils.
That's all? I had to build a hand-patched tcsh across our platform list 
because the unpatched sources *won't run* if tcsh doesn't understand 
LS_COLORS. And some csh's have the same behavior. IOW you couldn't run 
[t]csh *at all* with the newer LS_COLORS features.


Anyway, just wondering if you've also seen this and what if anything has 
been done to Cygwin's tcsh to cope.


Nothing.  It's a bit weird that LS_COLORS is used by coreutils and tcsh,
but it's a generic problem on all platforms.  It will be solved upstream
one way or the other.


Right, I was just curious if Cygwin in particular had done anything 
about it. Thanks for the info.


--
Matthew
"What's Cygwin?" you ask.
'Tis mostly absurd software
Concerning hippos.


--
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: Updated: OpenSSH-4.4p1-1

[Charles Wilson]

Corinna Vinschen wrote:

On Oct 11 16:20, Wells, Roger K. wrote:

When I installed this my previous installation broke and now the sshd
server stops immediately when it is started.  Any hints will be
appreciated.
thanks


Maybe that's it: http://cygwin.com/ml/cygwin/2006-10/msg00250.html


This is bad.  Suppose I am a cygwin user on a machine to which I do not 
have Administrator privileges.  Until now, I could run a personal sshd 
on a unique port, and connect back to my windows box.  Now I can't -- 
because, as a non-Admin, I can't create the sshd user.  (and this use 
case is not a hypothetical; I do this on the job often)


I consider this a regression -- and what's worse, IMO the patch that 
imposed this new requirement is dead wrong.  Here's a fuller quote of 
the offending section of the changelog:


 - (djm) [sshd.c auth.c] Set up fakepw() with privsep uid/gid, so it can
   be used to drop privilege to; fixes Solaris GSSAPI crash reported by
   Magnus Abrante; suggestion and feedback dtucker@
   NB. this change will require that the privilege separation user must
   exist on all the time, not just when UsePrivilegeSeparation=yes

My translation: even when UsePrivilegeSeparation=no we are STILL going 
to use privsep.  And this misfeature will be imposed across all 
platforms, just to fix a crash on one platform when using one optional 
authentication component.


Not nice, not nice at all.

--
Chuck


--
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: shopt igncr not working

[Matthew Woehlke]

Rob Walker wrote:

Matthew Woehlke wrote:

Rob Walker wrote:
Saying cygwin's bash wasn't designed to handle CRLF is a lot like 
saying that cygwin's bash (as previously released all these years) 
wasn't designed to work with the rest of Windows.  This might 
actually be the case, but I don't understand the point.  If you don't 
want to work with Windows, why release for Windows?


Many, many other cross-platform products make allowances for CRLF 
(version control systems are a prime example) to maximize 
compatibility, and thereby their usefulness, on Windows.  Cygwin's 
recent changes (with make and bash) here has put a real crimp in my 
plans to depend on cygwin for a portable build environment.


Just curious, is there a goal or strategy that drives changes like this?


Speed?


I was actually asking a larger question.  There's obviously value in 
handling CRLF invisibly, and value in having speed.  When evaluating 
which is _more_ valuable, what are the inputs?


Clearly speed is valued over making CRLF work in binmode mounts, which 
was never supposed to be the case in the first place.


But seriously, dude.  If handling CRLF starts to approach in complexity 
what the rest of bash does, CRLF handling should probably be rewritten.


I believe that's what igncr *does*. IOW you already got this wish.

I think using 'igncr' should satisfy your complaints. If it doesn't, 
you need to tell use WHY (which, you'll notice, the OP failed to do).
So far, igncr hasn't worked for me either.  I think this is because I 
don't know how to use it.


This is the simple shell script I'd like to have work (lines separated 
by CRLF):


  #!/bin/bash
  echo helloworld

I have c:/tmp mounted at /tmp, where I put my test script (called 
helloworld.sh):


  [EMAIL PROTECTED]> pwd
  /tmp
  [EMAIL PROTECTED]> mount
  C:\Documents and Settings on /home type system (binmode)
  C:\apps\cygwin\bin on /usr/bin type system (binmode)
  C:\apps\cygwin\lib on /usr/lib type system (binmode)
  C:\apps\cygwin on / type system (binmode)
  C:\tmp on /tmp type system (binmode)
  A: on /a type system (binmode)
  C: on /c type system (binmode)
  D: on /d type system (binmode)

When I run this script, this is what I see (when run from the "Cygwin 
Bash Shell" DOS box):


  [EMAIL PROTECTED]> bash --version
  GNU bash, version 3.1.17(9)-release (i686-pc-cygwin)
  Copyright (C) 2005 Free Software Foundation, Inc.
  [EMAIL PROTECTED]> ./helloworld.sh
  hello world
  : command not foundne 3:


Ok, no surprises.


I also tried this way:

  [EMAIL PROTECTED]> bash -O igncr
  [EMAIL PROTECTED]> ./helloworld.sh
  hello world
  : command not foundne 3:


This won't work; shopts are not inherited. You'll need to set it on 
environment startup if you're going with this approach (check the 
archives for how).


I also tried editing the script (which I fear breaks it for non 3.x 
users of bash):


  #!/bin/bash -O igncr
  echo helloworld


Is there any chance 'which bash' is not /bin/bash or /usr/bin/bash? 
Otherwise this seems strange, but not being a shebang guru I cannot 
think of why it shouldn't work.


Did you try adding 'shopt igncr' to the script? This won't (shouldn't, 
at least!) break it for non-3.1-9 users (and if you stick a 2>/dev/null 
after it, won't print errors).



What does work for me is:

  [EMAIL PROTECTED]> bash -O igncr ./helloworld.sh
  hello world


Yup, that ought to work... Obviously it's not the best solution, though.

--
Matthew
"What's Cygwin?" you ask.
'Tis mostly absurd software
Concerning hippos.


--
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: Updated: OpenSSH-4.4p1-1

[Matthew Woehlke]

Charles Wilson wrote:

Corinna Vinschen wrote:

On Oct 11 16:20, Wells, Roger K. wrote:

When I installed this my previous installation broke and now the sshd
server stops immediately when it is started.  Any hints will be
appreciated.
thanks


Maybe that's it: http://cygwin.com/ml/cygwin/2006-10/msg00250.html


This is bad.  Suppose I am a cygwin user on a machine to which I do not 
have Administrator privileges.  Until now, I could run a personal sshd 
on a unique port, and connect back to my windows box.  Now I can't -- 
because, as a non-Admin, I can't create the sshd user.  (and this use 
case is not a hypothetical; I do this on the job often)


It sounds like this is a technique that would be usable on platforms 
other than Cygwin, as well.


I consider this a regression -- and what's worse, IMO the patch that 
imposed this new requirement is dead wrong.  Here's a fuller quote of 
the offending section of the changelog:



 - (djm) [sshd.c auth.c] Set up fakepw() with privsep uid/gid, so it can
   be used to drop privilege to; fixes Solaris GSSAPI crash reported by
   Magnus Abrante; suggestion and feedback dtucker@
   NB. this change will require that the privilege separation user must
   exist on all the time, not just when UsePrivilegeSeparation=yes


My translation: even when UsePrivilegeSeparation=no we are STILL going 
to use privsep.  And this misfeature will be imposed across all 
platforms, just to fix a crash on one platform when using one optional 
authentication component.


Not nice, not nice at all.


So you're taking it up with the ssh developers (or 'dtucker'), right?

--
Matthew
"What's Cygwin?" you ask.
'Tis mostly absurd software
Concerning hippos.


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

putenv changes not reflected by CW_SYNC_WINENV

[Brian Ford]

Just FYI for now in case anyone is interested enough to look.  I'll try
and make an STC, and possibly a patch when I have time to look further.
Thanks.

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



--
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: shopt igncr not working

[Matthew Woehlke]

http://cygwin.com/acronyms/#PPIOSPE, thanks!

Rob Walker wrote:

Matthew Woehlke wrote:

Rob Walker wrote:

Matthew Woehlke wrote:

Rob Walker wrote:
Many, many other cross-platform products make allowances for CRLF 
(version control systems are a prime example) to maximize 
compatibility, and thereby their usefulness, on Windows.  Cygwin's 
recent changes (with make and bash) here has put a real crimp in my 
plans to depend on cygwin for a portable build environment.


I think using 'igncr' should satisfy your complaints. If it doesn't, 
you need to tell use WHY (which, you'll notice, the OP failed to do).


So far, igncr hasn't worked for me either.  I think this is because I 
don't know how to use it.


This is the simple shell script I'd like to have work (lines 
separated by CRLF):


  #!/bin/bash
  echo helloworld

[snip]
I also tried editing the script (which I fear breaks it for non 3.x 
users of bash):


  #!/bin/bash -O igncr
  echo helloworld


Did you try adding 'shopt igncr' to the script? This won't (shouldn't, 
at least!) break it for non-3.1-9 users (and if you stick a

2>/dev/null after it, won't print errors).


A ha!  This form works in 3.1-9

   shopt -s igncr; #
   #!/bin/bash
   echo hello world


Hmm, that should be the second line, not the first (not sure but I would 
guess the shebang is ignored when it isn't first). Does it still work 
that way, or does bash get confused about the CR on the shebang line? 
(If the latter, I would say this is a real bug that needs to be 
addressed somehow, or maybe igncr should affect the invoking bash's 
handling of the shebang).



But it apparently _does_ break for non-3.1-9 users:

   [EMAIL PROTECTED]> ./helloworld.sh
   shopt: not found
   hello world
   [EMAIL PROTECTED]> bash --version
   GNU bash, version 2.05b.0(1)-release (i686-pc-cygwin)
   Copyright (C) 2002 Free Software Foundation, Inc.


It does? It looks like it did what it is supposed to do; gripe, and then 
correctly run the rest of the script. See my earlier suggestion about 
adding '2>/dev/null' after the 'shopt'.


--
Matthew
"What's Cygwin?" you ask.
'Tis mostly absurd software
Concerning hippos.


--
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 fails to run .bat file with spaces in pathname and argument

[Johnathon Jamison]

Buchbinder, Barry (NIH/NIAID) [E] wrote:


The problem is, at least in part, with cmd.  cmd /? says:

  If /C or /K is specified, then the remainder of the command line after
  the switch is processed as a command line, where the following logic
is
  used to process quote (") characters:

  1.  If all of the following conditions are met, then quote
characters
  on the command line are preserved:

  - no /S switch
  - exactly two quote characters
  - no special characters between the two quote characters,
where special is one of: &<>()@^|
  - there are one or more whitespace characters between the
the two quote characters
  - the string between the two quote characters is the name
of an executable file.

  2.  Otherwise, old behavior is to see if the first character is
  a quote character and if so, strip the leading character and
  remove the last quote character on the command line,
preserving
  any text after the last quote character.



This tells me that CreateProcess is not really at fault at all, but 
instead the fix is to create a different command line.  I can think of 
one of two things: (1) do not have a double quote as the first 
character, (2) if the program is quoted and there exists an argument 
quoted as well, replace ' ' with '^ ' everywhere in the program and add 
a '^' at the end of the program before the quote.



Try using short names to get rid of the first set of quotes.  Short
names still work, at least on XP.  Compare
  c:\>dir docume~1
and
  c:\>dir "Documents and Settings"

To find out the short names,
  c:\>dir /x
Or one can guess (first 6 characters + "~" + "1", or a higher digit if
the 6 characters + "~1" is already used, + "." + first 3 characters of
the extension).

Try changing the batch file from
  echo %1
to
  echo %1 %2 %3 %4 %5 %6 %7 %8 %9
That should work by getting rid of the second set of quotes, at least if
the number of arguments is less than 10.

This, also, works

  /c> echo '"c:\Documents and Settings\BBuchbinder\test.bat" "hello
world"
  exit' | u2d | cmd /k
  c:\>"c:\Documents and Settings\BBuchbinder\test.bat" "hello world"

  c:\>echo "hello world"
  "hello world"

  c:\>exit

You can leave off the "/k", but you then get extraneous text from
cmd.exe as it loads.



This is a lot of good info, especially since I generally do not use DOS. 
 Thank you.


Johnathon

--
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: shopt igncr not working

[Igor Peshansky]

On Fri, 13 Oct 2006, Matthew Woehlke wrote:

> http://cygwin.com/acronyms/#PPIOSPE, thanks!
>
> Rob Walker wrote:
> > Matthew Woehlke wrote:
> > > Rob Walker wrote:
> > > > Matthew Woehlke wrote:
> > > > > Rob Walker wrote:
> > > > > > Many, many other cross-platform products make allowances for CRLF
> > > > > > (version control systems are a prime example) to maximize
> > > > > > compatibility, and thereby their usefulness, on Windows.  Cygwin's
> > > > > > recent changes (with make and bash) here has put a real crimp in my
> > > > > > plans to depend on cygwin for a portable build environment.
> > > > >
> > > > > I think using 'igncr' should satisfy your complaints. If it doesn't,
> > > > > you need to tell use WHY (which, you'll notice, the OP failed to do).
> > > >
> > > > So far, igncr hasn't worked for me either.  I think this is because I
> > > > don't know how to use it.
> > > >
> > > > This is the simple shell script I'd like to have work (lines separated
> > > > by CRLF):
> > > >
> > > >   #!/bin/bash
> > > >   echo helloworld
> > > >
> > > > [snip]
> > > > I also tried editing the script (which I fear breaks it for non 3.x
> > > > users of bash):
> > > >
> > > >   #!/bin/bash -O igncr
> > > >   echo helloworld
> > >
> > > Did you try adding 'shopt igncr' to the script? This won't (shouldn't, at
> > > least!) break it for non-3.1-9 users (and if you stick a
> > > 2>/dev/null after it, won't print errors).
> >
> > A ha!  This form works in 3.1-9
> >
> >shopt -s igncr; #
> >#!/bin/bash
> >echo hello world
>
> Hmm, that should be the second line, not the first (not sure but I would guess
> the shebang is ignored when it isn't first). Does it still work that way, or
> does bash get confused about the CR on the shebang line? (If the latter, I
> would say this is a real bug that needs to be addressed somehow, or maybe
> igncr should affect the invoking bash's handling of the shebang).
>
> > But it apparently _does_ break for non-3.1-9 users:
> >
> >[EMAIL PROTECTED]> ./helloworld.sh
> >shopt: not found
> >hello world
> >[EMAIL PROTECTED]> bash --version
> >GNU bash, version 2.05b.0(1)-release (i686-pc-cygwin)
> >Copyright (C) 2002 Free Software Foundation, Inc.
>
> It does? It looks like it did what it is supposed to do; gripe, and then
> correctly run the rest of the script. See my earlier suggestion about adding
> '2>/dev/null' after the 'shopt'.

See , the part
that says "if you want your script to be portable"...
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

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

RE: How can I increase ulimit -n or open files limit to 65535 on cygwin?

[Buchbinder, Barry \(NIH/NIAID\) [E]]

Annie W. wrote:
> can someone point me on how to increase open file limit?
> Im stuck to 3200 on ulimit -n
> I already went thru my cygwin files and downloaded cygwin source code.
> I would appreciate the advice on how to change this limit?
> 
> I have already increased open file limits on redhat and other linux
> systems without any problems. 
> 
> Thank you
> Annie

I've no idea what sets ulimit's limits.  But that won't stop me from
suggesting some possibilities.  :-)

- ulimit is a bash builtin, so you might want to look at bash's code.
If bash is the problem, you might run under ash or another shell, though
not launched from bash.

- One possibility is that Windows limits the numbers of open files.
Have you looked into that?

Good luck.

--
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: emacs hangs at start, or sometime later

[Eric Twietmeyer]

 > -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of ahnkle
> Sent: Friday, October 13, 2006 6:57 AM
> To: cygwin@cygwin.com
> Subject: emacs hangs at start, or sometime later
> 
> hi,
> 
> I am having some problems with my emacs. I have 21.2-13 
> installed, and recently it started locking up after some 
> time, from ~1 hour to 3-4 hours. The window would not 
> repaint. The emacs process usage goes up to 50%, then close 
> to 100%, until the process is killed.
> 
> Then I tried rebaseall. It just brok  emacs, emacs hung at 
> startup. I have re-installed 21.2.13, and ncurses (mentioned 
> in an old post), and X packages, and am back to emacs running 
> for 'some period', then locking up.
> 
> Any ideas about where next?
> 
> And another thing...
> I tried building emacs 21.2-13 from source, and it doesn't 
> work. So far there is
> 
>   * missing/corrupt file 'emacs.pif' in the emacs-21.2.tar.gz file
>   * cygwin build/install script tries to call emacs at the 
> end of make, but temacs.exe 
> is the file
>   * static heap exhausted message
> 
> The source file emacs-21.2-13-src.tar.bz2 has a good md5sum.
> 
> regards,
> ahnkle
> 

I am also having this problem.  It was reported to this list back on 9
August, and some other people indicated they too are experiencing this.  I
had to revert back to a previous version of cygwin, 1.5.18, which I still
had installed on my box.  With that version this hang in emacs does not
occur.  However, this 1.5.18 version has the other problem which causes
cygwin based processes to hang if examined with Process Explorer, so I would
like to move to the latest version when possible.

If you are able to get any further information on what the cause may be or
how to work around it, I think many people would be grateful.  I will
continue to try updates to cygwin as they are made available, but I think in
the end it will require someone much more familiar than myself with the
internal workings of cygwin and debugging in this environment to track it
down.  Hopefully someone with that background will themselves run into the
hang and be able to debug it.

-Eric


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

ssh-agent not working with McAfee: a workaround with modified ssh-agent

[Tim Beuman]

Hi,

I made a modified version of ssh-agent so it can run under cygrunsrv
under the local system account. This seems to work fine without having
to disable or uninstall McAfee.

Note: this is not an official update. It is a version I made for my own
purposes but others might find it usable too.

Changes I made:
1) Added a -r flag which prevents ssh-agent from forking.
2) Replaced fprintf(stderr,...) with logit(...) for logging to the event
log when running under cygrunsrv.
3) Added a source file (ssh-agent-reg.c) which contains a routine to
register the SSH_AUTH_SOCK in the global environment variable list of
windows (through the windows registry).
4) Qualified all identity(key) accesses with the euid/egid as presented
when adding the key initially.
Reason: when running ssh-agent under the SYSTEM account, all keys are
potentially accessible for everyone (security issue). Solution: when
adding a key, the euid and egid as obtained from getpeereid() are stored
together with the key. All subsequent accesses to that stored key are
restricted to the user which added the key (based on the euid and egid
obtained using getpeereid()). This basically limits access to the keys
to their creators only.
5) Added TAILQ_FOREACH_SAFE macro to openbsd-compat/sys-queue.h (needed
to remove only the keys for the invoking user when using ssh-add -D).

Notes:
Changes 1 and 4 are conditional compiled using #ifdef __CYGWIN__/#endif.
Change 3 is based on a solution that Karl M posted earlier (subject:
"Re: how to make ssh-agent automatically").

The changes are based on the source code of openssh-4.4p1-1.

I have tested these modifications on a W2K machine only. The registry
functions should work for Windows 95 upwards (according to their
description on the Microsoft website) so potentially this modified
version should work under W95 an up also but I haven't verified that.


To install ssh-agent as service under cygrunsrv I use:

cygrunsrv -I ssh-agent -p /usr/bin/ssh-agent -a "-r" -o

To start the service:

either:

cygrunsrv -S ssh-agent

or:

net start ssh-agent


In my .bash_login I added:

ssh-add -l > /dev/null 2>&1
if [ $? -eq 1 ]; then
   ssh-add
fi


Attached the modified source files and the modified Makefile.

Tim

#ifdef __CYGWIN__
#define STRICT
#include 
#include "includes.h"
#include 
#include 
#include 
#include 
#include 
#include "log.h"

// MAX_PATH is defined as 260 in windef.h

int ssh_agent_reg(char *socket_name)
{
HKEYhKey;
DWORD   dwSize, dwReturnValue;
BYTEnValue[1024];
static CHAR RegPath[MAX_PATH] = "";
  LRESULT status;

strcpy(RegPath,
  "SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Environment");

if ((status = RegOpenKeyEx(
  HKEY_LOCAL_MACHINE,
  RegPath,
  0,
  KEY_SET_VALUE,
  &hKey
  )))
{
error("RegOpenKeyEx: %lu", (unsigned long)status);
return 1;
}

  strcpy(nValue, socket_name);
dwSize = strlen(nValue) + 1;

if ((status = RegSetValueEx(
  hKey,
  "SSH_AUTH_SOCK",
  0,
  REG_SZ,
  (BYTE *)nValue,
  dwSize
  )))
{
error("RegSetValueEx (SSH_AUTH_SOCK): %lu", (unsigned 
long)status);
return 1;
}

if ((status = RegCloseKey(
  hKey
  )))
{
error("RegCloseKey: %lu", (unsigned long)status);
return 1;
}

  SendMessageTimeout(
  HWND_BROADCAST,
  WM_SETTINGCHANGE,
  0,
  (LPARAM) "Environment",
  SMTO_ABORTIFHUNG,
  5000,
  &dwReturnValue
  );

return 0;
}
#endif

/* $OpenBSD: ssh-agent.c,v 1.152 2006/08/04 20:46:05 stevesk Exp $ */
/*
 * Author: Tatu Ylonen <[EMAIL PROTECTED]>
 * Copyright (c) 1995 Tatu Ylonen <[EMAIL PROTECTED]>, Espoo, Finland
 *All rights reserved
 * The authentication agent program.
 *
 * As far as I am concerned, the code I have written for this software
 * can be used freely for any purpose.  Any derived versions of this
 * software must be clearly marked as such, and if the derived work is
 * incompatible with the protocol description in the RFC file, it must be
 * called by a name other than "ssh" or "Secure Shell".
 *
 * Copyright (c) 2000, 2001 Markus Friedl.  All rights reserved.
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *notice, this list of conditions and the following disclaimer in the
 *documentation and/or other materials provided with the distribution.
 *
 * THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``A

ssh-agent not working with McAfee: a workaround with modified ssh-agent

[Tim Beuman]

Here is the missing Makefile (Makefile.txt).

Tim
# $Id: Makefile.in,v 1.282 2006/09/12 11:54:10 djm Exp $

# uncomment if you run a non bourne compatable shell. Ie. csh
#SHELL = /usr/bin/sh

AUTORECONF=autoreconf

prefix=/usr/local
exec_prefix=${prefix}
bindir=${exec_prefix}/bin
sbindir=${exec_prefix}/sbin
libexecdir=${exec_prefix}/libexec
datadir=${prefix}/share
mandir=${prefix}/share/man
mansubdir=man
sysconfdir=${prefix}/etc
piddir=/var/run
srcdir=.
top_srcdir=.

DESTDIR=

SSH_PROGRAM=${exec_prefix}/bin/ssh
ASKPASS_PROGRAM=$(libexecdir)/ssh-askpass
SFTP_SERVER=$(libexecdir)/sftp-server
SSH_KEYSIGN=$(libexecdir)/ssh-keysign
RAND_HELPER=$(libexecdir)/ssh-rand-helper
PRIVSEP_PATH=/var/empty
SSH_PRIVSEP_USER=sshd
STRIP_OPT=-s

PATHS= -DSSHDIR=\"$(sysconfdir)\" \
-D_PATH_SSH_PROGRAM=\"$(SSH_PROGRAM)\" \
-D_PATH_SSH_ASKPASS_DEFAULT=\"$(ASKPASS_PROGRAM)\" \
-D_PATH_SFTP_SERVER=\"$(SFTP_SERVER)\" \
-D_PATH_SSH_KEY_SIGN=\"$(SSH_KEYSIGN)\" \
-D_PATH_SSH_PIDDIR=\"$(piddir)\" \
-D_PATH_PRIVSEP_CHROOT_DIR=\"$(PRIVSEP_PATH)\" \
-DSSH_RAND_HELPER=\"$(RAND_HELPER)\"

CC=gcc
LD=gcc
CFLAGS=-g -O2 -Wall -Wpointer-arith -Wuninitialized -Wsign-compare 
CPPFLAGS=-I. -I$(srcdir)  $(PATHS) -DHAVE_CONFIG_H
LIBS=-lresolv -lcrypto -lz  /usr/lib/textmode.o -lcrypt
LIBSELINUX=
SSHDLIBS=
LIBEDIT=
LIBPAM=
LIBWRAP=
AR=/usr/bin/ar
AWK=gawk
RANLIB=ranlib
INSTALL=/usr/bin/install -c
PERL=/usr/bin/perl
SED=/usr/bin/sed
ENT=
XAUTH_PATH=/usr/X11R6/bin/xauth
LDFLAGS=-L. -Lopenbsd-compat/ 
EXEEXT=.exe

INSTALL_SSH_PRNG_CMDS=
INSTALL_SSH_RAND_HELPER=

TARGETS=ssh$(EXEEXT) sshd$(EXEEXT) ssh-add$(EXEEXT) ssh-keygen$(EXEEXT) 
ssh-keyscan${EXEEXT} ssh-keysign${EXEEXT} ssh-agent$(EXEEXT) scp$(EXEEXT) 
ssh-rand-helper${EXEEXT} sftp-server$(EXEEXT) sftp$(EXEEXT)

LIBSSH_OBJS=acss.o authfd.o authfile.o bufaux.o bufbn.o buffer.o \
canohost.o channels.o cipher.o cipher-acss.o cipher-aes.o \
cipher-bf1.o cipher-ctr.o cipher-3des1.o cleanup.o \
compat.o compress.o crc32.o deattack.o fatal.o hostfile.o \
log.o match.o md-sha256.o moduli.o nchan.o packet.o \
readpass.o rsa.o ttymodes.o xmalloc.o \
atomicio.o key.o dispatch.o kex.o mac.o uidswap.o uuencode.o misc.o \
monitor_fdpass.o rijndael.o ssh-dss.o ssh-rsa.o dh.o kexdh.o \
kexgex.o kexdhc.o kexgexc.o scard.o msg.o progressmeter.o dns.o \
entropy.o scard-opensc.o gss-genr.o

SSHOBJS= ssh.o readconf.o clientloop.o sshtty.o \
sshconnect.o sshconnect1.o sshconnect2.o

SSHDOBJS=sshd.o auth-rhosts.o auth-passwd.o auth-rsa.o auth-rh-rsa.o \
sshpty.o sshlogin.o servconf.o serverloop.o \
auth.o auth1.o auth2.o auth-options.o session.o \
auth-chall.o auth2-chall.o groupaccess.o \
auth-skey.o auth-bsdauth.o auth2-hostbased.o auth2-kbdint.o \
auth2-none.o auth2-passwd.o auth2-pubkey.o \
monitor_mm.o monitor.o monitor_wrap.o kexdhs.o kexgexs.o \
auth-krb5.o \
auth2-gss.o gss-serv.o gss-serv-krb5.o \
loginrec.o auth-pam.o auth-shadow.o auth-sia.o md5crypt.o \
audit.o audit-bsm.o platform.o

MANPAGES= scp.1.out ssh-add.1.out ssh-agent.1.out ssh-keygen.1.out 
ssh-keyscan.1.out ssh.1.out sshd.8.out sftp-server.8.out sftp.1.out 
ssh-rand-helper.8.out ssh-keysign.8.out sshd_config.5.out ssh_config.5.out
MANPAGES_IN = scp.1 ssh-add.1 ssh-agent.1 ssh-keygen.1 ssh-keyscan.1 ssh.1 
sshd.8 sftp-server.8 sftp.1 ssh-rand-helper.8 ssh-keysign.8 sshd_config.5 
ssh_config.5
MANTYPE = doc

CONFIGFILES=sshd_config.out ssh_config.out moduli.out
CONFIGFILES_IN=sshd_config ssh_config moduli

PATHSUBS= \
-e 's|/etc/ssh/ssh_prng_cmds|$(sysconfdir)/ssh_prng_cmds|g' \
-e 's|/etc/ssh/ssh_config|$(sysconfdir)/ssh_config|g' \
-e 's|/etc/ssh/ssh_known_hosts|$(sysconfdir)/ssh_known_hosts|g' \
-e 's|/etc/ssh/sshd_config|$(sysconfdir)/sshd_config|g' \
-e 's|/usr/libexec|$(libexecdir)|g' \
-e 's|/etc/shosts.equiv|$(sysconfdir)/shosts.equiv|g' \
-e 's|/etc/ssh/ssh_host_key|$(sysconfdir)/ssh_host_key|g' \
-e 's|/etc/ssh/ssh_host_dsa_key|$(sysconfdir)/ssh_host_dsa_key|g' \
-e 's|/etc/ssh/ssh_host_rsa_key|$(sysconfdir)/ssh_host_rsa_key|g' \
-e 's|/var/run/sshd.pid|$(piddir)/sshd.pid|g' \
-e 's|/etc/ssh/moduli|$(sysconfdir)/moduli|g' \
-e 's|/etc/ssh/sshrc|$(sysconfdir)/sshrc|g' \
-e 's|/usr/X11R6/bin/xauth|$(XAUTH_PATH)|g' \
-e 's|/var/empty|$(PRIVSEP_PATH)|g' \
-e 
's|/usr/bin:/bin:/usr/sbin:/sbin|/bin:/usr/sbin:/sbin:/usr/local/bin|g'

FIXPATHSCMD = $(SED) $(PATHSUBS)

all: $(CONFIGFILES) ssh_prng_cmds.out $(MANPAGES) $(TARGETS)

$(LIBSSH_OBJS): Makefile.in config.h
$(SSHOBJS): Makefile.in config.h
$(SSHDOBJS): Makefile.in config.h

.c.o:
$(CC) $(CFLAGS) $(CPPFLAGS) -c $<

LIBCOMPAT=openbsd-compat/libopenbsd-compat.a
$(LIBCOMPAT): always
(cd openbsd-compat && $(MAKE))
al

1.5.21-2 CYGWIN1.DLL Invalid Page Fault

[Charles Brockman]

I submit this information without the expectation that the problem will be fixed
if it is specific to the Windows 98 operating system.

When I run commands such as ls, man, pwd, bash, cat, df and find from an MS-DOS
prompt in the C:/CYGWIN directory they fail with the invalid page fault message:

LS caused an invalid page fault in
module CYGWIN1.DLL at 0167:6106bcf4.
Registers:
EAX=0074d008 CS=0167 EIP=6106bcf4 EFLGS=00010212
EBX= SS=016f ESP=0074f30c EBP=0074f5a4
ECX=0074f384 DS=016f ESI=0016 FS=5daf
EDX= ES=016f EDI=0074f5ec GS=
Bytes at CS:EIP:
89 30 e9 b9 fe ff ff 89 74 24 18 b8 c0 68 12 61
Stack dump:
        
      

The address of failure (0167:6106bcf4) is identical for all commands.

The file produced by cygcheck is attached.

--
Charles

Cygwin Configuration Diagnostics
Current System Time: Fri Oct 13 11:39:42 2006

Windows 98 SE Ver 4.10 Build  

Path:   C:\WINDOWS
C:\WINDOWS\COMMAND
C:\CYGWIN\BIN
C:\PROGRA~1\DOXYGEN\BIN

Output from C:\cygwin\bin\id.exe (nontsec)
UID: 678(Charles Brockman) GID: 544(all)
544(all)

Output from C:\cygwin\bin\id.exe (ntsec)
UID: 678(Charles Brockman) GID: 544(all)
544(all)

SysDir: C:\WINDOWS\SYSTEM
WinDir: C:\WINDOWS

Here's some environment variables that may affect cygwin:
CYGWIN = 'C:\CYGWIN'

Here's the rest of your environment variables:
TMP = 'C:\WINDOWS\TEMP'
TEMP = 'C:\WINDOWS\TEMP'
PROMPT = '$p$g'
winbootdir = 'C:\WINDOWS'
COMSPEC = 'C:\COMMAND.COM'
JAVA_HOME = 'C:\progra~1\java\j2re1.4.2_04'
windir = 'C:\WINDOWS'
BLASTER = 'A220 I5 D0'
CMDLINE = 'cygcheck -srhv '
POSIXLY_CORRECT = '1'

Scanning registry for keys with 'Cygnus' in them...
HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin\mounts v2
  (default) = '/cygdrive'
  cygdrive flags = 0x0022
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin\mounts 
v2\/usr/X11R6/lib/X11/fonts
  (default) = 0x000a
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin\mounts v2\/
  (default) = 'C:\cygwin'
  flags = 0x000a
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
  (default) = 'C:\cygwin/bin'
  flags = 0x000a
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
  (default) = 'C:\cygwin/lib'
  flags = 0x000a
HKEY_LOCAL_MACHINE\Software\Cygnus Solutions\Cygwin\Program Options

Listing available drives...
Drv Type  Size   Used Flags  Name
a:  fd N/AN/A
c:  hd  FAT32 8682Mb  85% CPUN   IBM 22GXP A
d:  hd  FAT32 8682Mb  87% CPUN   IBM 22GXP B
e:  cd N/AN/A

fd = floppy,  hd = hard drive,   cd = CD-ROM
net= Network Share,   ram= RAM drive,unk= Unknown
CP = Case Preserving, CS = Case Sensitive,   UN = Unicode
PA = Persistent ACLS, FC = File Compression, VC = Volume Compression

Mount entries: these map POSIX directories to your NT drives.
-NT-   -POSIX--Type-  -Flags-
C:\cygwin  /  system  binmode
C:\cygwin/bin  /usr/bin   system  binmode
C:\cygwin/lib  /usr/lib   system  binmode
.  /cygdrive  system  binmode,cygdrive

Looking to see where common programs can be found, if at all...
Not Found: awk
Not Found: bash
Not Found: cat
Not Found: cp
Not Found: cpp (good!)
Not Found: crontab
Found: C:\WINDOWS\COMMAND\find.exe
Not Found: gcc
Not Found: gdb
Not Found: grep
Not Found: kill
Not Found: ld
Not Found: ls
Not Found: make
Not Found: mv
Not Found: patch
Not Found: perl
Not Found: rm
Not Found: sed
Not Found: ssh
Not Found: sh
Not Found: tar
Not Found: test
Not Found: vi
Not Found: vim

Looking for various Cygwin DLLs...  (-v gives version info)
   48k 2003/08/09 C:\cygwin\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0
  "cygform7.dll" v0.0 ts=2003/8/9 2:25
   29k 2003/08/09 C:\cygwin\bin\cygmenu7.dll - os=4.0 img=1.0 sys=4.0
  "cygmenu7.dll" v0.0 ts=2003/8/9 2:25
   19k 2003/08/09 C:\cygwin\bin\cygpanel7.dll - os=4.0 img=1.0 sys=4.0
  "cygpanel7.dll" v0.0 ts=2003/8/9 2:24
   17k 2001/06/28 C:\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0
  "cyghistory4.dll" v0.0 ts=2001/1/6 20:34
  108k 2001/06/28 C:\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0
  "cygreadline4.dll" v0.0 ts=2001/1/6 20:34
   29k 2003/08/10 C:\cygwin\bin\cyghistory5.dll - os=4.0 img=1.0 sys=4.0
  "cyghistory5.dll" v0.0 ts=2003/8/10 16:16
  148k 2003/08/10 C:\cygwin\bin\cygreadline5.dll - os=4.0 img=1.0 sys=4.0
   

Re: FAQ ALERT Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1

[Joshua Daniel Franklin]

On 10/11/06, Christopher Faylor wrote:

Good point, Brian.  If anything qualifies as a FAQ, this certainly does.
Joshua, would you be willing to write something up about the philosophy
of MS-DOS and Cygwin?  Known gotchas would be a good thing to include,
even if they were only examples.


This looks like possibly just a generalized rewrite of
http://cygwin.com/faq/faq-nochunks.html#faq.using.accessing-drives

--
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: shopt igncr not working

[Rob Walker]

Matthew Woehlke wrote:

http://cygwin.com/acronyms/#PPIOSPE, thanks!

Rob Walker wrote:

Matthew Woehlke wrote:

Rob Walker wrote:

Matthew Woehlke wrote:

Rob Walker wrote:
Many, many other cross-platform products make allowances for CRLF 
(version control systems are a prime example) to maximize 
compatibility, and thereby their usefulness, on Windows.  
Cygwin's recent changes (with make and bash) here has put a real 
crimp in my plans to depend on cygwin for a portable build 
environment.


I think using 'igncr' should satisfy your complaints. If it 
doesn't, you need to tell use WHY (which, you'll notice, the OP 
failed to do).


So far, igncr hasn't worked for me either.  I think this is because 
I don't know how to use it.


This is the simple shell script I'd like to have work (lines 
separated by CRLF):


  #!/bin/bash
  echo helloworld

[snip]
I also tried editing the script (which I fear breaks it for non 3.x 
users of bash):


  #!/bin/bash -O igncr
  echo helloworld


Did you try adding 'shopt igncr' to the script? This won't 
(shouldn't, at least!) break it for non-3.1-9 users (and if you stick a

2>/dev/null after it, won't print errors).


A ha!  This form works in 3.1-9

   shopt -s igncr; #
   #!/bin/bash
   echo hello world


Hmm, that should be the second line, not the first (not sure but I 
would guess the shebang is ignored when it isn't first). Does it still 
work that way, or does bash get confused about the CR on the shebang 
line? (If the latter, I would say this is a real bug that needs to be 
addressed somehow, or maybe igncr should affect the invoking bash's 
handling of the shebang).
Yes, works if the second line too.  Thanks for your patience.  Here's a 
working version:


  #!/bin/bash
  shopt -s igncr 2>/dev/null; # please keep me on the second line, thanks
  echo hello world





But it apparently _does_ break for non-3.1-9 users:

   [EMAIL PROTECTED]> ./helloworld.sh
   shopt: not found
   hello world
   [EMAIL PROTECTED]> bash --version
   GNU bash, version 2.05b.0(1)-release (i686-pc-cygwin)
   Copyright (C) 2002 Free Software Foundation, Inc.


It does? It looks like it did what it is supposed to do; gripe, and 
then correctly run the rest of the script. See my earlier suggestion 
about adding '2>/dev/null' after the 'shopt'.
You're right, sorry about that.  The script succeeded in this case, too 
(returned 0).


-Rob


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

1.5.21: problem with xinetd permissions

[Eran Cohanim]

Hi,

I have been trying to setup xinetd in my windows xp pro computer under 
cygwin with no luck

(tried that in 3 different computers with the same result)
(I must mention that I did it in the past with success - had to redo it 
because of new installed OS

and new installed cygwin)

now from some reason I cant and the error I get is:

$ /etc/rc.d/init.d/xinetd start
Starting xinetd:   [  OK  ]
touch: cannot touch `/var/lock/subsys/xinetd': Permission denied

$ ls -la /var/lock/
total 0
drwxr-xr-x+ 3 SYSTEM root  0 Oct 12 20:05 .
drwxrwx---+ 9 eran   Users 0 Oct 12 20:05 ..
drwxr-xr-x+ 2 SYSTEM root  0 Oct 13 12:06 subsys

I installed all the neccesary packages for making it work

$ cygcheck -c | egrep "sysvinit|initscript|chkconfig|xinetd"
chkconfig   1.2.24h-1  OK
initscripts 0.9-1  OK
sysvinit2.84-4 OK
xinetd  2.3.9-1OK

and after that run:

init-config (answered no at both questions - tried even with yes answer on 
both questions)

xinetd-config (answered yes on both questions)

now I see all the relevant port listening but if I try them is say the below

$ netstat -aon | grep 23
 TCP0.0.0.0:23 0.0.0.0:0  LISTENING   3252

$ telnet localhost
Trying 127.0.0.1...
Connected to 172.0.0.1.
Escape character is '^]'.
Connection closed by foreign host.

I've searched for that problem in your newsgroups and found the below link 
(that was long time ago - see the date)


http://www.cygwin.com/ml/cygwin/2004-08/msg01109.html


please let me know how can i fix this
thanks ahead

Eran Cohanim 



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

Re: 1.5.21: problem with xinetd permissions

[Tim Beuman]

You are trying to start xinetd from user erin, which has no write 
permission on /var/lock/subsys (only read & execute). chmod 777 
/var/lock/subsys would probably help.


Tim

Eran Cohanim wrote:


Hi,

I have been trying to setup xinetd in my windows xp pro computer under 
cygwin with no luck

(tried that in 3 different computers with the same result)
(I must mention that I did it in the past with success - had to redo it 
because of new installed OS

and new installed cygwin)

now from some reason I cant and the error I get is:

$ /etc/rc.d/init.d/xinetd start
Starting xinetd:   [  OK  ]
touch: cannot touch `/var/lock/subsys/xinetd': Permission denied

$ ls -la /var/lock/
total 0
drwxr-xr-x+ 3 SYSTEM root  0 Oct 12 20:05 .
drwxrwx---+ 9 eran   Users 0 Oct 12 20:05 ..
drwxr-xr-x+ 2 SYSTEM root  0 Oct 13 12:06 subsys

I installed all the neccesary packages for making it work

$ cygcheck -c | egrep "sysvinit|initscript|chkconfig|xinetd"
chkconfig   1.2.24h-1  OK
initscripts 0.9-1  OK
sysvinit2.84-4 OK
xinetd  2.3.9-1OK

and after that run:

init-config (answered no at both questions - tried even with yes answer 
on both questions)

xinetd-config (answered yes on both questions)

now I see all the relevant port listening but if I try them is say the 
below


$ netstat -aon | grep 23
 TCP0.0.0.0:23 0.0.0.0:0  LISTENING   3252

$ telnet localhost
Trying 127.0.0.1...
Connected to 172.0.0.1.
Escape character is '^]'.
Connection closed by foreign host.

I've searched for that problem in your newsgroups and found the below 
link (that was long time ago - see the date)


http://www.cygwin.com/ml/cygwin/2004-08/msg01109.html


please let me know how can i fix this
thanks ahead

Eran Cohanim

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

1.5.21: file utils (ls, sed) do not read NTFS permissions on second NTFS IDE hard drive

[Chris Doherty]

cygcheck output attached.

Environment is Windows XP SP2, fully patched as of yesterday.
I used to have CopSSH installed; I decided to move to full cygwin and
sshd.  I uninstalled CopSSh, deleted all files related to it, removed
all cygwin and sshd related registry keys, rebooted and verified no
cygwin1.dll present anywhere on the system.

Installed via setup.

mkgroup and mkpasswd and post-install scripts appear to have run
successfully.  All cygwin programs appear to function properly when
manipulkating files on the C: drive.

However.

$ cd /cygdrive/d/shareaza/lib/books/fiction/deryni/

[EMAIL PROTECTED] /cygdrive/d/shareaza/lib/books/fiction/deryni
$ ls -l
total 9316
--+ 1    575066 Jul 17 07:13
Camber_01_-_Camber_of_Culdi.txt
--+ 1    814471 Jul 17 07:13
Camber_02_-_Saint_Camber.txt
--+ 1   1127615 Jul 17 07:13
Camber_03_-_Camber_the_Heretic.txt
--+ 1    444251 Jul 17 07:13
Deryni_01_-_Deryni_Rising.txt
--+ 1    516813 Jul 17 07:14
Deryni_02_-_Deryni_Checkmate.txt
--+ 1    778776 Jul 17 07:14 Deryni_03_-_High_Deryni.txt
--+ 1    908432 Jul 17 07:14
Heretic_01_-_Harrowing_of_Gwynedd.txt
--+ 1   1118049 Jul 17 07:14
Heretic_02_-_King_Javan_s_Year.txt
--+ 1    945530 Jul 17 07:14
Heretic_03_-_Bastard_Prince.txt
--+ 1    679969 Jul 17 07:14
Kelson_01_-_The_Bishops_Heir.txt
--+ 1    683546 Jul 17 07:14
Kelson_02_-_King_s_Justice.txt
--+ 1    925565 Jul 17 07:15
Kelson_03_-_Quest_for_St_Camber.txt

(Yes, I own real copies of all of these.  Getting them off shareaza
was easier than trying to OCR them myself.)

[EMAIL PROTECTED] /cygdrive/d/shareaza/lib/books/fiction/deryni
$ for i in * ;do cacls $i;done
d:\shareaza\lib\books\fiction\deryni\Camber_01_-_Camber_of_Culdi.txt
BUILTIN\Administrators:F

LUCIFER\chrisd:F

NT AUTHORITY\SYSTEM:F

d:\shareaza\lib\books\fiction\deryni\Camber_02_-_Saint_Camber.txt
BUILTIN\Administrators:F

LUCIFER\chrisd:F
 NT
AUTHORITY\SYSTEM:F

d:\shareaza\lib\books\fiction\deryni\Camber_03_-_Camber_the_Heretic.txt
BUILTIN\Administrators:F

LUCIFER\chrisd:F

NT AUTHORITY\SYSTEM:F

d:\shareaza\lib\books\fiction\deryni\Deryni_01_-_Deryni_Rising.txt
BUILTIN\Administrators:F

LUCIFER\chrisd:F
  NT
AUTHORITY\SYSTEM:F

d:\shareaza\lib\books\fiction\deryni\Deryni_02_-_Deryni_Checkmate.txt
BUILTIN\Administrators:F

LUCIFER\chrisd:F

NT AUTHORITY\SYSTEM:F

d:\shareaza\lib\books\fiction\deryni\Deryni_03_-_High_Deryni.txt
BUILTIN\Administrators:F

LUCIFER\chrisd:F
NT
AUTHORITY\SYSTEM:F

d:\shareaza\lib\books\fiction\deryni\Heretic_01_-_Harrowing_of_Gwynedd.txt
BUILTIN\Administrators:F


   LUCIFER\chrisd:F

   NT AUTHORITY\SYSTEM:F

d:\shareaza\lib\books\fiction\deryni\Heretic_02_-_King_Javan_s_Year.txt
BUILTIN\Administrators:F

LUCIFER\chrisd:F

NT AUTHORITY\SYSTEM:F

$

LUCIFER\chrisd:F

NT AUTHORITY\SYSTEM:F

d:\shareaza\lib\books\fiction\deryni\Kelson_01_-_The_Bishops_Heir.txt
BUILTIN\Administrators:F

LUCIFER\chrisd:F

NT AUTHORITY\SYSTEM:F

d:\shareaza\lib\books\fiction\deryni\Kelson_02_-_King_s_Justice.txt
BUILTIN\Administrators:F

LUCIFER\chrisd:F
   NT
AUTHORITY\SYSTEM:F

d:\shareaza\lib\books\fiction\deryni\Kelson_03_-_Quest_for_St_Camber.txt
BUILTIN\Administrators:F

 LUCIFER\chrisd:F

 NT AUTHORITY\SYSTEM:F

[EMAIL PROTECTED] /cygdrive/d/shareaza/lib/books/fiction/deryni
$ cp Deryni_01_-_Deryni_Rising.txt dr.txt

[EMAIL PROTECTED] /cygdrive/d/shareaza/lib/books/fiction/deryni
$ sed -i -e '/Deryni/d'  dr.txt
sed: can't read dr.txt: Permission denied

[EMAIL PROTECTED] /cygdrive/d/shareaza/lib/books/fiction/deryni
$ ls -la
total 9752
drwxrwx---+  2 chrisd   Administrators   0 Oct 13 18:53 .
d-+ 39   0 Sep 26 07:03 ..
--+  1  575066 Jul 17 07:13
Camber_01_-_Camber_of_Culdi.txt
--+  1  814471 Jul 17 07:13
Camber_02_-_Saint_Camber.txt
--+  1     1127615 Jul 17 07:13
Camber_03_-_Camber_the_Heretic.txt
--+  1  444251 Jul 17 07:13
Deryni_01_-_Deryni_Rising.txt
--+  1  516813 Jul 17 07:14
Deryni_02_-_Deryni_Checkmate.txt
--+  1  778776 Jul 17 07:14
Deryni_03_-_High_Deryni.txt
--+  1  908432 Jul 17 07:14
Heretic_01_-_Harrowing_of_Gwynedd.txt
--+  1     1118049 Jul 17 07:14
Heretic_02_-_King_Javan_s_Year.txt
--+  1  945530 Jul 17 07:14
Heretic_03

Re: FAQ ALERT Re: [ANNOUNCEMENT] Updated: vim-7.0.122-1

[Christopher Faylor]

On Fri, Oct 13, 2006 at 02:43:45PM -0700, Joshua Daniel Franklin wrote:
>On 10/11/06, Christopher Faylor wrote:
>>Good point, Brian.  If anything qualifies as a FAQ, this certainly does.
>>Joshua, would you be willing to write something up about the philosophy
>>of MS-DOS and Cygwin?  Known gotchas would be a good thing to include,
>>even if they were only examples.
>
>This looks like possibly just a generalized rewrite of
>http://cygwin.com/faq/faq-nochunks.html#faq.using.accessing-drives

I don't see much there which talks about the fact that not every
program will understand Windows paths correctly.

I think I have to write up a Cygwin philosophy page, too at some point
(with Corinna's input, of course), which tries to make clear that
modifying linux programs to work better with Windowisms is not a primary
goal of Cygwin.

cgf

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

Cygwin and Portaudio

[Hugh]

I can compile Portaudio in Cygwin, using shared and static libraries only.  That
is fine with me though.  I can build my sources using Cygwin, except whenever I
run the programme, I always require cygportaudio-2.dll.  Is there any possible
way to have the library information hard coded into the compile?  Am I asking
the wrong list?

Thankyou for your help.

Hugh


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

What happens the first time BASH is run?

[Tim Largy]

When running BASH for the first time after installing Cygwin, the
user's home directory is created, and .bashrc and other dotfiles are
copied into it. Where is this behavior controlled? Is it compiled into
BASH? If that is the case, what other scripts does BASH call upon to
set up the user's home directory?

Tim

--
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 happens the first time BASH is run?

[Tim Largy]

On 10/13/06, Tim Largy <[EMAIL PROTECTED]> wrote:

When running BASH for the first time after installing Cygwin, the
user's home directory is created, and .bashrc and other dotfiles are
copied into it. Where is this behavior controlled? Is it compiled into
BASH? If that is the case, what other scripts does BASH call upon to
set up the user's home directory?

Tim



Answering my own question: the existence check for the  home
directory, as well as it's creation, takes place in /etc/profile. How
I forgot this I do not know as I spotted it yesterday.

--
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 happens the first time BASH is run?

[Brian Dessent]

Tim Largy wrote:

> When running BASH for the first time after installing Cygwin, the
> user's home directory is created, and .bashrc and other dotfiles are
> copied into it. Where is this behavior controlled? Is it compiled into
> BASH? If that is the case, what other scripts does BASH call upon to
> set up the user's home directory?

Hard coding that into bash would be needlessly complex and a maintenance
nightmare.  Instead /etc/profile just copies them from /etc/skel if they
don't exist.

You probably also ought to the section of "man bash" titled INVOCATION.

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/

cywin shared dll

[Tom Lee]

Hello,

I copied all cygwin dll and *.exe to a different machine at c:\mycgwin where 
they have old

cygwin installed.

When I run grep.exe, it will complain that

" system shared memory version mismatch detected -
0x75BE0084/0x75BE009C.
This problem is probably due to using incompatible versions of the
cygwin  DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version.  The most recent version
*should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution.  Rebooting is also suggested if
you are unable to find another cygwin DLL.
"

is there a way I can set up an environment variable using mount or PATH 
setting

that will make cygwin grep.exe to search
c:\mycygwin first  before searching x:\cygwin\bin?

thanks.

tom

_
Search—Your way, your world, right now!  
http://imagine-windowslive.com/minisites/searchlaunch/?locale=en-us&FORM=WLMTAG



--
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 happens the first time BASH is run?

[René Berber]

Tim Largy wrote:

> When running BASH for the first time after installing Cygwin, the
> user's home directory is created, and .bashrc and other dotfiles are
> copied into it. Where is this behavior controlled? Is it compiled into
> BASH?[snip]

No, it's not compiled into bash.

Reading `man bash` probably answers this question but... what is happening 
every time bash starts is that it executes /etc/profile and every .sh script in 
/etc/profile.d; in the first one you'll find how it creates the $HOME 
directory, I don't think .bashrc is created or copied from anywhere, that one 
is the user's responsibility (same for .profile, .bash_profile, etc. which on 
Unix/Linux are created when the user account is created).
-- 
René Berber


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

Re: How can I increase ulimit -n or open files limit to 65535 on cygwin?

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Buchbinder, Barry (NIH/NIAID) [E] on 10/13/2006 2:31 PM:
> Annie W. wrote:
>> can someone point me on how to increase open file limit?
>> Im stuck to 3200 on ulimit -n

You can't :(

At least, not without patching cygwin (and that is supposing that windows
even provides the hooks to make it possible).  Bash's ulimit on cygwin is
pretty much read-only.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFMDfh84KuGfSFAYARAlPUAJwOSa+YTzX7HpXdo8tCTsuOORIctACgn14H
VCgn7506NFlcW8anw4o1SVI=
=5IDR
-END PGP SIGNATURE-

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

Re: 1.5.21: file utils (ls, sed) do not read NTFS permissions on second NTFS IDE hard drive

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Chris Doherty on 10/13/2006 5:15 PM:
> cygcheck output attached.
> 
> [EMAIL PROTECTED] /cygdrive/d/shareaza/lib/books/fiction/deryni
> $ ls -l
> total 9316
> --+ 1    575066 Jul 17 07:13

sounds like you need to run mkpasswd and mkgroups to update your
/etc/passwd and /etc/groups files.  Otherwise, cygwin can't parse the
permissions associated with the ACLs of those files.

Also, in the future, see if you can convince your mailer to attach
cygcheck output with a text mime type (some mailers do this if you rename
the extension to end in .txt); otherwise, I have to save your cygcheck to
disk rather than reading it inline.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFMDlS84KuGfSFAYARAty3AKCq1nbgwfevlxc+dVnnmtf1G1PDPQCfcy1o
ZbSoU68qPAxbTTJ70nfFXHA=
=xnC0
-END PGP SIGNATURE-

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

Re: Cygwin and Portaudio

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Hugh on 10/13/2006 5:14 PM:
> I can compile Portaudio in Cygwin, using shared and static libraries only.  
> That
> is fine with me though.  I can build my sources using Cygwin, except whenever 
> I
> run the programme, I always require cygportaudio-2.dll.  Is there any possible
> way to have the library information hard coded into the compile?  Am I asking
> the wrong list?

Welcome to dynamic libraries.  If you compile against a dll, then the dll
must be present to run the binary.  You can see if you can try and force a
static compile, but the result will be that your binary is bigger, and
that you no longer automatically pick up any library updates.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFMDml84KuGfSFAYARAinJAJ92Ej7hmgWL9vPV25P+42JMfzXrXACgsjB0
PTYFsenonw3vguA9cHXCHFs=
=97el
-END PGP SIGNATURE-

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

Reinstall libncurses7 after rebasing (was: emacs hangs at start, or sometime later)

[Sean M. Paus]

ahnkle wrote:
> hi,
> 
> I am having some problems with my emacs. I have 21.2-13 installed, and 
> recently it started 
> locking up after some time, from ~1 hour to 3-4 hours. The window would not 
> repaint. The 
> emacs process usage goes up to 50%, then close to 100%, until the process is 
> killed.
> 
> Then I tried rebaseall. It just brok  emacs, emacs hung at startup. I have 
> re-installed 21.2.13, and ncurses (mentioned in an old post), and X packages, 
> and am back to
> emacs running for 'some period', then locking up.
> 
> Any ideas about where next?

I encountered this problem over a year ago.  You need to reinstall
libncurses7.  That undoes the rebasing of it's dlls.  For some weird
reason (that no one is able to explain), rebasing libncurses7 dlls fixes
this problem.

I have narrowed down the problem in the emacs sources to an infinite
loop in morecore (gmalloc.c).  align(...) returns a pointer that is less
than _heapbase (which shouldn't ever happen) causing the do/while loop
that increases the new heap size to overflow newsize.  Since newsize is
an unsigned, overflowing sets the value to zero (0).  Multiplying 0 by 2
always results in 0 so the check to make sure the new size is sufficient
always fails.

I can only imagine why this is happening.  I assume that emacs's
implementation of malloc is not being initialized properly (if at all).
 Perhaps libncurses7.dll is doing something that makes emacs.exe think
it's implementation of malloc has been initialzed.  I tried breaking in
__malloc_initialize in gdb and never hit it.  I don't fully understand
what rebasing the dlls does, but it looks like it might have something
to do with the order they are loaded.  My best guess is that
libncurses7.dll is modifying variables used by emacs for memory allocation.

Hope this helps.

Sean



signature.asc
Description: OpenPGP digital signature

Re: What happens the first time BASH is run?

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to René Berber on 10/13/2006 6:03 PM:

http://cygwin.com/acronyms/#PCYMTWLL - thanks

> 
> I don't think .bashrc is created or copied from anywhere, that one is the 
> user's responsibility (same for .profile, .bash_profile, etc. which on 
> Unix/Linux are created when the user account is created).

Actually, cygwin includes base-files as one of its packages, and that
package includes enough scripts (including the default /etc/profile) to
copy .bashrc and other files from /etc/defaults/etc/skel to every new
user's home directory.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFMDo184KuGfSFAYARArRfAJ42TdBCMm9OJTlAUrtTGlDxX/keDQCbBYD+
SOGL92cVfxe0v7PdzfkruwA=
=MbSG
-END PGP SIGNATURE-

--
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: cywin shared dll

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Tom Lee on 10/13/2006 6:02 PM:
> Hello,
> 
> I copied all cygwin dll and *.exe to a different machine at c:\mycgwin
> where they have old
> cygwin installed.

That's the problem.  You should only ever have a single version of
cygwin1.dll installed anywhere on your system.  Delete the old copy, and
just put the new one on the path.

> 
> is there a way I can set up an environment variable using mount or PATH
> setting
> that will make cygwin grep.exe to search
> c:\mycygwin first  before searching x:\cygwin\bin?

Yes, you can adjust the PATH environment variable from the control panel,
but the bigger question you should be asking yourself is why not just have
a single installation of cygwin (your choice of c:\mycygwin or
x:\cygwin\bin) and not have to worry about which of the multiple copies
will be used.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFMDrK84KuGfSFAYARAgbdAKDXONcOBK+wT7t8ttrjgYaGL8loPgCgr6bE
mXj0qqhZbBNgljor7OjupXM=
=B7Dq
-END PGP SIGNATURE-

--
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 fails to run .bat file with spaces in pathname and argument

[Enrico Forestieri]

Sean Daley writes:

> Read further down that thread and you'll also see that people discovered some
> additional horrifying things about windows cmd.
> 
> http://sourceware.org/ml/cygwin/2004-09/msg00277.html

Referring to that old post, the following works:

C:\>cmd /c ""C:\Documents and Settings\test.bat" "Hello, world.""
"Hello, world."

Yes, quoting is quite weird with cmd.exe.

-- 
Enrico


--
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: cywin shared dll

[Tom Lee]

Hi Eric,

Thanks for your help.


That's the problem.  You should only ever have a single version of
cygwin1.dll installed anywhere on your system.  Delete the old copy, and
just put the new one on the path.


If I want to distribute one command for the end user to use and don't want 
to have
a full installation. Also, I don't know if the user has the cygwin 
pre-installed or not.



> is there a way I can set up an environment variable using mount or PATH
> setting
> that will make cygwin grep.exe to search
> c:\mycygwin first  before searching x:\cygwin\bin?

Yes, you can adjust the PATH environment variable from the control panel,
but the bigger question you should be asking yourself is why not just have
a single installation of cygwin (your choice of c:\mycygwin or
x:\cygwin\bin) and not have to worry about which of the multiple copies
will be used.


Are you sure PATH works?
In the PATH c:\mycgwin is ahead of system path and x:\cygwin\bin is even not 
in the path.

It still failed with the same error.

Tom

_
Try the new Live Search today!  
http://imagine-windowslive.com/minisites/searchlaunch/?locale=en-us&FORM=WLMTAG



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

Re: Cygwin and Portaudio

[Hugh]

Eric Blake  byu.net> writes:

> Welcome to dynamic libraries.  If you compile against a dll, then the dll
> must be present to run the binary.  You can see if you can try and force a
> static compile, but the result will be that your binary is bigger, and
> that you no longer automatically pick up any library updates.


Hi Eric,

Thankyou for your reply.  I compiled a static version of Portaudio and installed
it, but compiling my sources against Portaudio caused some errors to peak from
the Portaudio static sources.

I am most likely going to use the shared libraries, because then I can easily
update the libraries as needed.  Is that your recommendation?

Hugh



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

Re: 1.5.21: file utils (ls, sed) do not read NTFS permissions on second NTFS IDE hard drive

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

http://cygwin.com/acronyms/#PPIOSPE

According to Chris Doherty on 10/13/2006 9:02 PM:
>> sounds like you need to run mkpasswd and mkgroups to update your
>> /etc/passwd and /etc/groups files.  Otherwise, cygwin can't parse the
>> permissions associated with the ACLs of those files.
> 
> That isn't it.  That's one of the first things I checked ("setup
> appears to have run all the post-install scripts correctly").  The
> only odd thing I did was to change the group on chrisd from 513 (None)
> to 544 (Administrators).  But rerunning mkpasswd and mkgroup doesn't
> seem to help:
> 
> [EMAIL PROTECTED] ~
> $ mkpasswd -l > /etc/passwd
> 
> [EMAIL PROTECTED] ~
> $ mkgroup -l > /etc/group
> 
> [EMAIL PROTECTED] ~
> $ ls -la /cygdrive/d/shareaza/lib/books/fiction/deryni/
> total 9752
> drwxrwx---+  2 chrisd   Administrators   0 Oct 13 18:53 .
> d-+ 39   0 Sep 26 07:03 ..
> --+  1  575066 Jul 17 07:13
> Camber_01_-_Camber_of_Culdi.txt

What does getfacl say about the ACLs of these files and directories?

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFMGAq84KuGfSFAYARArDtAKDVE1KnEKNY0CbHda1lDesc/M3dEQCeLVWC
Ve5PYYDvfO3Bw6ggTNsHo5c=
=0MIx
-END PGP SIGNATURE-

--
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: cywin shared dll

[Eric Blake]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Tom Lee on 10/13/2006 8:56 PM:
> Hi Eric,
> 
> Thanks for your help.
> 
>> That's the problem.  You should only ever have a single version of
>> cygwin1.dll installed anywhere on your system.  Delete the old copy, and
>> just put the new one on the path.
> 
> If I want to distribute one command for the end user to use and don't
> want to have
> a full installation. Also, I don't know if the user has the cygwin
> pre-installed or not.

It sounds like you are setting yourself up to be a
http://cygwin.com/acronyms/#3PP.  Search the mailing list archives for
better ideas.  You are not the first to ask questions on how to portably
detect whether a random machine has cygwin installed; and the advice from
this list is if cygwin is already installed, DO NOT TRY to install a
second copy of cygwin1.dll.  Instead, inform the user if their installed
version is out of date and they need an upgrade to run your software.

> 
> Are you sure PATH works?
> In the PATH c:\mycgwin is ahead of system path and x:\cygwin\bin is even
> not in the path.
> It still failed with the same error.

Altering PATH does not help if a copy of cygwin1.dll is already loaded in
memory.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFMGkP84KuGfSFAYARAtxWAKCVkAJR/1UJYcBwbXZbUegEhSyCJwCfWvQH
YzXJAYHtLV2sxpsrRgR4mxc=
=a8h1
-END PGP SIGNATURE-

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

Re: 1.5.21: file utils (ls, sed) do not read NTFS permissions on second NTFS IDE hard drive

[Chris Doherty]

What does getfacl say about the ACLs of these files and directories?


getfacl seems equally confused:

[EMAIL PROTECTED] /cygdrive/d/shareaza/lib/books/fiction/deryni
$ for i in *.*;do getfacl $i;done
# file: Camber_01_-_Camber_of_Culdi.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: Camber_02_-_Saint_Camber.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: Camber_03_-_Camber_the_Heretic.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: Deryni_01_-_Deryni_Rising.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: Deryni_02_-_Deryni_Checkmate.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: Deryni_03_-_High_Deryni.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: Heretic_01_-_Harrowing_of_Gwynedd.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: Heretic_02_-_King_Javan_s_Year.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: Heretic_03_-_Bastard_Prince.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: Kelson_01_-_The_Bishops_Heir.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: Kelson_02_-_King_s_Justice.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: Kelson_03_-_Quest_for_St_Camber.txt
# owner: 
# group: 
user::---
user:chrisd:rwx
group::---
group:SYSTEM:rwx
group:Administrators:rwx
mask:rwx
other:---
# file: dr.txt
# owner: chrisd
# group: Administrators
user::---
group::---
mask:rwx
other:---

(Similar results for various other directories and files on D: showing
the same behaviour)

The only thing I can think of is that the D: drive was originally
formatted and mounted on a different install of WinXP SP2, but when I
brought it over to this machine I removed all the existing ACLs and
replaced them with ACLs using groups and users local to the current
install.  I'm thinking of backing up the drive and reformatting it
under this install to see if that does it.

--
Chris Doherty  --  cpdohert at gmail dot com
"In our time, it has generally been thought bad and unhealthy to
'repress' inhibitions. Spend a few days inside the new world of
personal blogs, however, and one might want to revisit the repression
issue.
~ Dan Henninger

--
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: zero byte /bin/bash file - what creates it?

[Tom Rodman]

On Wed 10/11/06 18:11 CDT cygwin@cygwin.com wrote:
> On Wed 10/11/06 18:07 EDT cygwin@cygwin.com wrote:
> > Are you untarring files into '/' and does that tar file have a '/bin/bash' 
> > file?
> 
> Thanks Larry. I was untarring to a subdir below root. I can check the
> tar archive, but I doubt it has a bash file w/"000" perms, even if it
> did I would expect that to end up below the sub-dir; this problem may
> have nothing to do w/tar- I was also fixing up perms in that subdir tree
> piping the already saved tar STDERR to a series of commands, and finally
> to "xargs chmod u+rw". I'm content to let this thread die ( I know I'm
> not supplying enough info ). If I unravel it I'll report back.

I can get the problem to happen at-will by running

  mkdir /home/bar; cd /home/bar
  tar zxf /tmp/foo.tar.gz # works fine/no problems
# foo.tar.gz has symbolic links in a subdir ( say "./myrestricted/bin" ) 
pointing to 
# /bin/bash, /bin/sed, /bin/perl, /bin/ls, /bin/mktemp, /bin/dir
# (I suspect some of these links are from various revs of cygwin, some of 
them years old)
  tar zxf /tmp/foo.tar.gz 
# 2nd untar creates zero byte files in /bin

Untarring to new empty dir does not cause any problems,
but untarring a 2nd time results in several zero byte files in /bin:

  ~ $ uname -a
  CYGWIN_NT-5.0 argon 1.5.21(0.156/4/2) 2006-07-30 14:21 i686 Cygwin
  ~ $ cd /bin
  /bin $ find . -maxdepth 1 -type f -empty
  ./bash
  ./dir
  ./less
  ./ls
  ./mktemp
  ./perl
  ./sed
  /bin $

tar seems to be following the pre-existing soft link on the file system,
and then writing to that target, instead of just replacing the soft
link on the file system.  

This approach does not have any problems:

  tar zUxf /tmp/foo.tar.gz

--
thanks,
Tom



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