Re: Windows 7, cygwin > 3.1.4 symlink issue

[Ken Brown via Cygwin]

On 9/17/2020 4:27 PM, Roland Roberts wrote:

On 8/24/2020 5:43 PM, Roland Roberts wrote:
I have one machine, a company machine which makes it hard to post details, 
which is running Windows 7. We run cygwin as our development environment for 
Java, but Java is installed as a Windows program. The scripts that do the 
builds are bash scripts that pull down updated code from svn, then run unit 
tests. All of the cygwin bits work fine, but when Java is launched to run the 
unit tests, it runs into problems with reading files that were created as 
symlinks in cygwin. Note that this does *not* happen with cygwin 3.1.4, but 
does with higher versions (up through 3.1.7).


Possibly related, the permissions on installed files is odd if I roll back 
from > 3.1.4 to 3.1.4. The files that were updated with the later version 
can't be deleted. The permissions on, for example, an Emacs upgraded under 
3.1.6 or 3.1.7 show "Unknown User" when I downgrade just cygwin and I can't 
run it. I have to upgrade cygwin, uninstall Emacs, downgrade cygwin then 
reinstall.


Other users in the company have had their machines upgraded/replaced with 
Windows 10 and don't seem to have this issue. Eventually, mine will be 
replaced as well, but in the meantime, later versions of cygwin can't be used.


Okay, I have no idea what form of dyslexia struck me when I wrote all those 
version numbers, but I've edited the above since it wasn't 1.x but 3.1.x


Starting with Cygwin 3.1.5, Cygwin changed its default method of creating
symlinks.  They are now special reparse points known as "WSL symlinks" on 
systems that support reparse points.


If you create such a symlink in Cygwin > 3.1.4 and then roll back to an earlier 
version, Cygwin won't recognize the file type.  (But Windows 10 with WSL will 
recognize it.)


If you're using tools that don't work with the new style of symlink, you can use 
the CYGWIN environment variable to change the way Cygwin creates symlinks.


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

Re: Windows 7, cygwin > 3.1.4 symlink issue

[Roland Roberts]

On 8/24/2020 5:43 PM, Roland Roberts wrote:
I have one machine, a company machine which makes it hard to post 
details, which is running Windows 7. We run cygwin as our development 
environment for Java, but Java is installed as a Windows program. The 
scripts that do the builds are bash scripts that pull down updated 
code from svn, then run unit tests. All of the cygwin bits work fine, 
but when Java is launched to run the unit tests, it runs into problems 
with reading files that were created as symlinks in cygwin. Note that 
this does *not* happen with cygwin 3.1.4, but does with higher 
versions (up through 3.1.7).


Possibly related, the permissions on installed files is odd if I roll 
back from > 3.1.4 to 3.1.4. The files that were updated with the later 
version can't be deleted. The permissions on, for example, an Emacs 
upgraded under 3.1.6 or 3.1.7 show "Unknown User" when I downgrade 
just cygwin and I can't run it. I have to upgrade cygwin, uninstall 
Emacs, downgrade cygwin then reinstall.


Other users in the company have had their machines upgraded/replaced 
with Windows 10 and don't seem to have this issue. Eventually, mine 
will be replaced as well, but in the meantime, later versions of 
cygwin can't be used.


Okay, I have no idea what form of dyslexia struck me when I wrote all 
those version numbers, but I've edited the above since it wasn't 1.x but 
3.1.x


roland

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

Re: Windows 7 update broke Cygwin X?

[Achim Gratz]

Joshua Hoke writes:
> I tried following directions from
> https://cygwin.com/ml/cygwin/2015-07/msg00448.html for debugging with
> strace and it seems there is an exception occurring inside a Trend
> Micro DLL, causing XWin.exe to exit silently.

YMMV, but while Trend Micro was inflicted upon us @work, I have never
been able to run anything even moderately complex (especially something
having their own DLLs), much less Cygwin, without excepting the install
directory from their "real time scan" engine at least.  This went so far
that the official support solution was to have a directory excepted by
default and having people to re-install whatever software they had
problems with there (besides all those software packages that were
installed there by default because they were already known not to work
otherwise).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

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

Re: Windows 7 update broke Cygwin X?

[Joshua Hoke]

On Fri, Sep 9, 2016 at 1:17 PM, Joshua Hoke  wrote:
> On Fri, Sep 9, 2016 at 12:42 PM, Marco Atzeri  wrote:
>> On 09/09/2016 18:03, Joshua Hoke wrote:
>>> After a recent Windows update, I am unable to start Cygwin's X server
>>> anymore. I tried updating to the latest Cygwin by running setup again,
>>> /usr/bin/rebaseall and rebooting. There are no obvious errors from the
>>> X server if I run /usr/bin/startxwin from a Cygwin console, but it
>>> seems to exit after 20 seconds or so:

I tried following directions from
https://cygwin.com/ml/cygwin/2015-07/msg00448.html for debugging with
strace and it seems there is an exception occurring inside a Trend
Micro DLL, causing XWin.exe to exit silently. At this point I don't
consider it a problem with Cygwin/X anymore, except that possibly it
should exit with a non-zero exit status. I am using a different X
server at the moment as a workaround.

--
Joshua Hoke

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

Re: Windows 7 update broke Cygwin X?

[Joshua Hoke]

On Fri, Sep 9, 2016 at 12:42 PM, Marco Atzeri  wrote:
> On 09/09/2016 18:03, Joshua Hoke wrote:
>>
>> Hi,
>>
>> After a recent Windows update, I am unable to start Cygwin's X server
>> anymore. I tried updating to the latest Cygwin by running setup again,
>> /usr/bin/rebaseall and rebooting. There are no obvious errors from the
>> X server if I run /usr/bin/startxwin from a Cygwin console, but it
>> seems to exit after 20 seconds or so:
>>
>> $ date; /usr/bin/startxwin; date
>> Fri, Sep 09, 2016 12:00:58 PM
>>
>> Welcome to the XWin X Server
>> Vendor: The Cygwin/X Project
>> Release: 1.18.4.0
>> OS: CYGWIN_NT-6.1-WOW 3QGH462 2.6.0(0.304/5/3) 2016-08-31 14:27 i686
>> OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64)
>> Package: version 1.18.4-1 built 2016-07-22
>
>
> works fine for me. Same configuration
>
>>
>> Any ideas about what how to fix or troubleshoot this? I use it all the
>> time and it worked before this update.
>>
>
> Problem reports:   http://cygwin.com/problems.html
>
> please provide the cygcheck.out as attachement

Please find attached cygcheck.out (redacted some environment
variables, a network share and local Windows groups) and also
XWin.0.log (though it appears the same as stdout in this case).

Note "this update" in my previous email could be unclear, I meant to
refer to the Windows update installed this morning. Looking at the
update history it appears that includes:

Update for Windows 7 for x64-based Systems (KB3177723): 2016 — Egypt cancels DST
Update for Windows 7 for x64-based Systems (KB3172605): July 2016
update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
Update for Windows 7 for x64-based Systems (KB3161102): Update for
Windows Journal component removal
Windows Malicious Software Removal Tool x64 - August 2016 (KB890830)
Update for Windows 7 for x64-based Systems (KB3179573): August 2016
update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1

Thanks in advance for any help.


cygcheck.out
Description: Binary data


XWin.0.log
Description: Binary data
--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Windows 7 update broke Cygwin X?

[Marco Atzeri]

On 09/09/2016 18:03, Joshua Hoke wrote:

Hi,

After a recent Windows update, I am unable to start Cygwin's X server
anymore. I tried updating to the latest Cygwin by running setup again,
/usr/bin/rebaseall and rebooting. There are no obvious errors from the
X server if I run /usr/bin/startxwin from a Cygwin console, but it
seems to exit after 20 seconds or so:

$ date; /usr/bin/startxwin; date
Fri, Sep 09, 2016 12:00:58 PM

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.18.4.0
OS: CYGWIN_NT-6.1-WOW 3QGH462 2.6.0(0.304/5/3) 2016-08-31 14:27 i686
OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64)
Package: version 1.18.4-1 built 2016-07-22


works fine for me. Same configuration



Any ideas about what how to fix or troubleshoot this? I use it all the
time and it worked before this update.



Problem reports:   http://cygwin.com/problems.html

please provide the cygcheck.out as attachement

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

Re: Windows 7 sshd can only login as cyg_server

[Bernd Prager]

On 8/25/14 11:49 AM, Larry Hall (Cygwin) wrote:

On 08/25/2014 07:00 AM, Corinna Vinschen wrote:

On Aug 25 12:51, Corinna Vinschen wrote:

On Aug 22 17:24, Larry Hall (Cygwin) wrote:

On 08/22/2014 04:44 PM, Corinna Vinschen wrote:

snip


I solved it:

It turned out, that my Windows domain policy was updating local policies 
in a way, that the local cyg_server account lost his group membership to 
the group 'Administrators' every time I log into my Windows 7.


I have to fix that every time before I start sshd.

I wrote a little python script that does the whole thing. In case 
someone wants to reuse it, enjoy:


#!/usr/bin/python
# -*- coding utf-8 -*-

import win32net
import win32serviceutil

user = cyg_server
group = Administrators

# make sure sshd user is in admin group
data = [ {domainandname : user} ]
mem, tot, res  = win32net.NetLocalGroupGetMembers(None, group, 1)

inGroup = False
for item in mem:
if (item['name']) == user:
inGroup = True
break

if not inGroup:
win32net.NetLocalGroupAddMembers(None, Administrators, 3, data)

# restart sshd
win32serviceutil.RestartService(sshd)



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

Re: Windows 7 sshd can only login as cyg_server

[Corinna Vinschen]

On Aug 22 17:24, Larry Hall (Cygwin) wrote:
 On 08/22/2014 04:44 PM, Corinna Vinschen wrote:
 
 snip
 
 That's what I meant.  Do you have a non-admin account for testing
 a login?
 
 I can only make a local non-admin user.  If I use that, it is just
 returning Permission denied after I enter the password.  I guess I'll
 have to fiddle with it a little more to see if I can figure out why that
 is.  But that seems tangential to the issue reported.

But your effect doesn't sound good either.

 If I try using the cyg_server account (yuck, I feel filthy! ;-) ), I get
 kicked out the same way as reported minus the message about chown.  That's
 as close as I've gotten and, of course, it's exactly opposite what was
 reported.

Right.  But the default setup of the cyg_server account in /etc/passwd
is to start /bin/false as login shell.  Did you change that to /bin/bash?

 Today I confused myself a lot by trying it (I'm using a domain cyg_server
 account for years so it was a bit of hacking) and I was able to login
 with a domain admin account but not with a normal domain account.
 
 That's with a local cyg_server running the service?
 
 Yes, sorry for not being clearer.  That was the hacky part.  It required
 to change the domain policy and stuff like that.
 
 OK, so this sounds similar to what I'm seeing with my domain account and
 with a local cyg_server running sshd.  I'm _shocked_.
 
 I didn't manage to debug this further.  However, what I never encounter is
 a chown(/dev/ptyX,...) Permission denied message.
 
 Yeah, me neither.  That's... special. ;-)
 
 ...and a bit incomprehensible :(
 
 Indeed.  Maybe the OP has an actual file for the pseudo /dev/pty1 file?  If
 so, maybe the permissions on the file are getting in the way??

That would be one good idea but I think that's not very likely.
Cygwin's device handling wouldn't notice the file and call all
the internal functions for ptys instead.  This includes chown,
which on ptys is a change of the ACL of four synchronization objects
representing the pty.


Corinna

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


pgpSe8nHME4Z9.pgp
Description: PGP signature

Re: Windows 7 sshd can only login as cyg_server

[Corinna Vinschen]

On Aug 25 12:51, Corinna Vinschen wrote:
 On Aug 22 17:24, Larry Hall (Cygwin) wrote:
  On 08/22/2014 04:44 PM, Corinna Vinschen wrote:
  
  snip
  
  That's what I meant.  Do you have a non-admin account for testing
  a login?
  
  I can only make a local non-admin user.  If I use that, it is just
  returning Permission denied after I enter the password.  I guess I'll
  have to fiddle with it a little more to see if I can figure out why that
  is.  But that seems tangential to the issue reported.
 
 But your effect doesn't sound good either.

Did you create a passwd entry?  I just set up a machine for testing
with a local cyg_server account, and I can login with local accounts
just fine.  It's the domain accounts which fail.  In my case bash simply
hangs for some reason I have yet to figure out.

If I use the domain cyg_server account, I can login with domain accounts
as well as local accounts, independent of their admin-ness.


Corinna

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


pgpaUTHS1r35D.pgp
Description: PGP signature

Re: Windows 7 sshd can only login as cyg_server

[Larry Hall (Cygwin)]

On 08/25/2014 06:51 AM, Corinna Vinschen wrote:

snip


I can only make a local non-admin user.  If I use that, it is just
returning Permission denied after I enter the password.  I guess I'll
have to fiddle with it a little more to see if I can figure out why that
is.  But that seems tangential to the issue reported.


But your effect doesn't sound good either.


Indeed.


If I try using the cyg_server account (yuck, I feel filthy! ;-) ), I get
kicked out the same way as reported minus the message about chown.  That's
as close as I've gotten and, of course, it's exactly opposite what was
reported.


Right.  But the default setup of the cyg_server account in /etc/passwd
is to start /bin/false as login shell.  Did you change that to /bin/bash?


Right.  No I didn't.  I believe my half-finished thought was to suggest the
OP had done this to get the connection with cyg_server to work.  Don't we
have that mind-reading plugin for the list working yet?  It would help
allot. ;-)

snip


Indeed.  Maybe the OP has an actual file for the pseudo /dev/pty1 file?  If
so, maybe the permissions on the file are getting in the way??


That would be one good idea but I think that's not very likely.
Cygwin's device handling wouldn't notice the file and call all
the internal functions for ptys instead.  This includes chown,
which on ptys is a change of the ACL of four synchronization objects
representing the pty.


Yeah, I had experimented a little with this idea myself to see if I could
prove that this would have any effect but I couldn't (as you suggest)...

--
Larry

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

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

Re: Windows 7 sshd can only login as cyg_server

[Larry Hall (Cygwin)]

On 08/25/2014 07:00 AM, Corinna Vinschen wrote:

On Aug 25 12:51, Corinna Vinschen wrote:

On Aug 22 17:24, Larry Hall (Cygwin) wrote:

On 08/22/2014 04:44 PM, Corinna Vinschen wrote:

snip


That's what I meant.  Do you have a non-admin account for testing
a login?


I can only make a local non-admin user.  If I use that, it is just
returning Permission denied after I enter the password.  I guess I'll
have to fiddle with it a little more to see if I can figure out why that
is.  But that seems tangential to the issue reported.


But your effect doesn't sound good either.


Did you create a passwd entry?  I just set up a machine for testing
with a local cyg_server account, and I can login with local accounts
just fine.  It's the domain accounts which fail.  In my case bash simply
hangs for some reason I have yet to figure out.


Well I'm not sure I would expect a hang necessarily, unless it was trying
to interact with the PDC in some degenerate way.  But refusing connections
from domain user accounts in this configuration makes sense to me.
Obviously, there are more alternatives than I'm aware of here though...

Ugh!  I thought I had created a password entry for my local non-admin user
but I didn't.  Once I did that, I was able to ssh in using that user (and
password) just fine with the local cyg_server account.  So I think we
can chalk this failure up to user-error. ;-)


If I use the domain cyg_server account, I can login with domain accounts
as well as local accounts, independent of their admin-ness.


Yeah, I wish I could created domain accounts of either or both types to try.
But I suppose in the end, I may just be confirming that the domain I'm
working in is...odd.  The behaviour you describe is exactly what I would
expect.  The behaviour I'm seeing with my domain (as well as local admin)
user being able to connect with only a local cyg_server seems a bit odd to
me.  But I suppose even if it is a generic loophole, one could consider
it a feature. ;-)

--
Larry

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

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

Re: Windows 7 sshd can only login as cyg_server

[Corinna Vinschen]

On Aug 21 15:16, Bernd Prager wrote:
 I just installed cygwin on Windows 7 and configured sshd with
 ssh-host-config.
 I checked all the permission and everything seems to be fine.
 
 I can connect as local user cyg_server but not as myself (a standard
 Windows 7 domain user).
 I am asked for a password and then I get:
 
 debug3: packet_send2: adding 48 (len 61 padlen 19 extra_pad 64)
 debug2: we sent a password packet, wait for reply
 debug1: Authentication succeeded (password).
 Authenticated to localhost ([127.0.0.1]:22).
 debug1: channel 0: new [client-session]
 debug3: ssh_session2_open: channel_new: 0
 debug2: channel 0: send open
 debug1: Requesting no-more-sessi...@openssh.com
 debug1: Entering interactive session.
 debug2: callback start
 debug2: fd 3 setting TCP_NODELAY
 debug3: packet_set_tos: set IP_TOS 0x10
 debug2: client_session2_setup: id 0
 debug2: channel 0: request pty-req confirm 1
 debug2: channel 0: request shell confirm 1
 debug2: callback done
 debug2: channel 0: open confirm rwindow 0 rmax 32768
 debug1: channel 0: free: client-session, nchannels 1
 debug3: channel 0: status: The following connections are open:
   #0 client-session (t4 r0 i0/0 o0/0 fd 4/5 cc -1)
 
 Connection to localhost closed by remote host.
 
 In the Windows I see the error event:
 
 sshd: PID 2968: fatal: chown(/dev/pty1, 124683, 10513) failed: Permission
 denied
 
 Can anybody help?

I'll have to test this, but as a start, can you try to setup 
cyg_server as a domain account?  See
https://cygwin.com/faq/faq.html#faq.using.sshd-in-domain


Corinna

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


pgpeAAzXh709C.pgp
Description: PGP signature

Re: Windows 7 sshd can only login as cyg_server

[Larry Hall (Cygwin)]

On 08/22/2014 09:06 AM, Corinna Vinschen wrote:

On Aug 21 15:16, Bernd Prager wrote:

I just installed cygwin on Windows 7 and configured sshd with
ssh-host-config.
I checked all the permission and everything seems to be fine.

I can connect as local user cyg_server but not as myself (a standard
Windows 7 domain user).
I am asked for a password and then I get:

debug3: packet_send2: adding 48 (len 61 padlen 19 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
Authenticated to localhost ([127.0.0.1]:22).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Requesting no-more-sessi...@openssh.com
debug1: Entering interactive session.
debug2: callback start
debug2: fd 3 setting TCP_NODELAY
debug3: packet_set_tos: set IP_TOS 0x10
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug2: channel 0: request shell confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
   #0 client-session (t4 r0 i0/0 o0/0 fd 4/5 cc -1)

Connection to localhost closed by remote host.

In the Windows I see the error event:

sshd: PID 2968: fatal: chown(/dev/pty1, 124683, 10513) failed: Permission
denied

Can anybody help?


I'll have to test this, but as a start, can you try to setup
cyg_server as a domain account?  See
https://cygwin.com/faq/faq.html#faq.using.sshd-in-domain


I know this is a contradictory report but logging in (pubkey) with my domain
user account and local cyg_server actually works fine.  I know. I'm
surprised too. ;-)  This is W7 Enterprise and Cygwin 64-bit.


--
Larry

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

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

Re: Windows 7 sshd can only login as cyg_server

[Corinna Vinschen]

On Aug 22 13:23, Larry Hall (Cygwin) wrote:
 On 08/22/2014 09:06 AM, Corinna Vinschen wrote:
 On Aug 21 15:16, Bernd Prager wrote:
 I just installed cygwin on Windows 7 and configured sshd with
 ssh-host-config.
 I checked all the permission and everything seems to be fine.
 
 I can connect as local user cyg_server but not as myself (a standard
 Windows 7 domain user).
 I am asked for a password and then I get:
 
 debug3: packet_send2: adding 48 (len 61 padlen 19 extra_pad 64)
 debug2: we sent a password packet, wait for reply
 debug1: Authentication succeeded (password).
 Authenticated to localhost ([127.0.0.1]:22).
 debug1: channel 0: new [client-session]
 debug3: ssh_session2_open: channel_new: 0
 debug2: channel 0: send open
 debug1: Requesting no-more-sessi...@openssh.com
 debug1: Entering interactive session.
 debug2: callback start
 debug2: fd 3 setting TCP_NODELAY
 debug3: packet_set_tos: set IP_TOS 0x10
 debug2: client_session2_setup: id 0
 debug2: channel 0: request pty-req confirm 1
 debug2: channel 0: request shell confirm 1
 debug2: callback done
 debug2: channel 0: open confirm rwindow 0 rmax 32768
 debug1: channel 0: free: client-session, nchannels 1
 debug3: channel 0: status: The following connections are open:
#0 client-session (t4 r0 i0/0 o0/0 fd 4/5 cc -1)
 
 Connection to localhost closed by remote host.
 
 In the Windows I see the error event:
 
 sshd: PID 2968: fatal: chown(/dev/pty1, 124683, 10513) failed: Permission
 denied
 
 Can anybody help?
 
 I'll have to test this, but as a start, can you try to setup
 cyg_server as a domain account?  See
 https://cygwin.com/faq/faq.html#faq.using.sshd-in-domain
 
 I know this is a contradictory report but logging in (pubkey) with my domain
 user account and local cyg_server actually works fine.  I know. I'm
 surprised too. ;-)  This is W7 Enterprise and Cygwin 64-bit.

Is your domain account an admin or a non-admin account?  Today I
confused myself a lot by trying it (I'm using a domain cyg_server
account for years so it was a bit of hacking) and I was able to login
with a domain admin account but not with a normal domain account.  I
didn't manage to debug this further.  However, what I never encounter is
a chown(/dev/ptyX,...) Permission denied message.


Corinna

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


pgptGCOQ27jSf.pgp
Description: PGP signature

Re: Windows 7 sshd can only login as cyg_server

[Larry Hall (Cygwin)]

On 08/22/2014 04:19 PM, Corinna Vinschen wrote:

On Aug 22 13:23, Larry Hall (Cygwin) wrote:

On 08/22/2014 09:06 AM, Corinna Vinschen wrote:

On Aug 21 15:16, Bernd Prager wrote:

I just installed cygwin on Windows 7 and configured sshd with
ssh-host-config.
I checked all the permission and everything seems to be fine.

I can connect as local user cyg_server but not as myself (a standard
Windows 7 domain user).
I am asked for a password and then I get:

debug3: packet_send2: adding 48 (len 61 padlen 19 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
Authenticated to localhost ([127.0.0.1]:22).
debug1: channel 0: new [client-session]
debug3: ssh_session2_open: channel_new: 0
debug2: channel 0: send open
debug1: Requesting no-more-sessi...@openssh.com
debug1: Entering interactive session.
debug2: callback start
debug2: fd 3 setting TCP_NODELAY
debug3: packet_set_tos: set IP_TOS 0x10
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug2: channel 0: request shell confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
   #0 client-session (t4 r0 i0/0 o0/0 fd 4/5 cc -1)

Connection to localhost closed by remote host.

In the Windows I see the error event:

sshd: PID 2968: fatal: chown(/dev/pty1, 124683, 10513) failed: Permission
denied

Can anybody help?


I'll have to test this, but as a start, can you try to setup
cyg_server as a domain account?  See
https://cygwin.com/faq/faq.html#faq.using.sshd-in-domain


I know this is a contradictory report but logging in (pubkey) with my domain
user account and local cyg_server actually works fine.  I know. I'm
surprised too. ;-)  This is W7 Enterprise and Cygwin 64-bit.


Is your domain account an admin or a non-admin account?


It is a member of local Administrators.


Today I confused myself a lot by trying it (I'm using a domain cyg_server
account for years so it was a bit of hacking) and I was able to login
with a domain admin account but not with a normal domain account.


That's with a local cyg_server running the service?


I didn't manage to debug this further.  However, what I never encounter is
a chown(/dev/ptyX,...) Permission denied message.


Yeah, me neither.  That's... special. ;-)


--
Larry

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

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

Re: Windows 7 sshd can only login as cyg_server

[Corinna Vinschen]

On Aug 22 16:30, Larry Hall (Cygwin) wrote:
 On 08/22/2014 04:19 PM, Corinna Vinschen wrote:
 On Aug 22 13:23, Larry Hall (Cygwin) wrote:
 On 08/22/2014 09:06 AM, Corinna Vinschen wrote:
 On Aug 21 15:16, Bernd Prager wrote:
 sshd: PID 2968: fatal: chown(/dev/pty1, 124683, 10513) failed: Permission
 denied
 
 Can anybody help?
 
 I'll have to test this, but as a start, can you try to setup
 cyg_server as a domain account?  See
 https://cygwin.com/faq/faq.html#faq.using.sshd-in-domain
 
 I know this is a contradictory report but logging in (pubkey) with my domain
 user account and local cyg_server actually works fine.  I know. I'm
 surprised too. ;-)  This is W7 Enterprise and Cygwin 64-bit.
 
 Is your domain account an admin or a non-admin account?
 
 It is a member of local Administrators.

That's what I meant.  Do you have a non-admin account for testing
a login?

 Today I confused myself a lot by trying it (I'm using a domain cyg_server
 account for years so it was a bit of hacking) and I was able to login
 with a domain admin account but not with a normal domain account.
 
 That's with a local cyg_server running the service?

Yes, sorry for not being clearer.  That was the hacky part.  It required
to change the domain policy and stuff like that.

 I didn't manage to debug this further.  However, what I never encounter is
 a chown(/dev/ptyX,...) Permission denied message.
 
 Yeah, me neither.  That's... special. ;-)

...and a bit incomprehensible :(


Corinna

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


pgpeDVyRj5fFa.pgp
Description: PGP signature

Re: Windows 7 sshd can only login as cyg_server

[Larry Hall (Cygwin)]

On 08/22/2014 04:44 PM, Corinna Vinschen wrote:

snip


That's what I meant.  Do you have a non-admin account for testing
a login?


I can only make a local non-admin user.  If I use that, it is just
returning Permission denied after I enter the password.  I guess I'll
have to fiddle with it a little more to see if I can figure out why that
is.  But that seems tangential to the issue reported.

If I try using the cyg_server account (yuck, I feel filthy! ;-) ), I get
kicked out the same way as reported minus the message about chown.  That's
as close as I've gotten and, of course, it's exactly opposite what was
reported.


Today I confused myself a lot by trying it (I'm using a domain cyg_server
account for years so it was a bit of hacking) and I was able to login
with a domain admin account but not with a normal domain account.


That's with a local cyg_server running the service?


Yes, sorry for not being clearer.  That was the hacky part.  It required
to change the domain policy and stuff like that.


OK, so this sounds similar to what I'm seeing with my domain account and
with a local cyg_server running sshd.  I'm _shocked_.


I didn't manage to debug this further.  However, what I never encounter is
a chown(/dev/ptyX,...) Permission denied message.


Yeah, me neither.  That's... special. ;-)


...and a bit incomprehensible :(


Indeed.  Maybe the OP has an actual file for the pseudo /dev/pty1 file?  If
so, maybe the permissions on the file are getting in the way??


--
Larry

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

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

Re: windows 7 cygwin/XWin session dies

[Jon TURNEY]

On 22/04/2014 11:00, Arnaud Caubel wrote:
 I run my cygwin/XWin.exe session on Windows 7 Professional and this session
 dies when I iconify it during some time (let'say 20 min).
 I think the problem is not to iconify it but more to not do anything.
 It is very uncomfortable because I have to relaunch it every time I do
 something else (emails, internet,...) more than about 20 minutes...
 I do not understand why the X session crashes...
 Could anyone help me ?
 
 It seems there is something with : XDM: Alive response indicates session
 dead, declaring session dead but I do not know which parameter I have to
 change to modify this behaviour... 

 Release: 1.9.2.0 (10902000)
 Build Date: 2010-11-03

This is quite an old version.  While I am not aware of any fixes in this area,
you might like to try with the current version.

 [  6240.102] XDM: Alive response indicates session dead, declaring session 
 dead

This means I sent an XDMCP keepalive for the current session to the XDM
server, but it's response said that the session wasn't alive.

One question I have is if your machine running XWin is idle, and going into a
sleep state before this problem occurs?

If that is the case, that may be the problem, as XDM will, by default,
periodically test if it can contact the display and declare the session dead
if that fails.

If your display manager is XDM, that can be turned off by setting the
DisplayManager.DISPLAY.pingInterval resource to 0. Other display managers may
have similar settings.

Alternatively, you could arrange for sleeping to be suspended while the X
server is running (It seems on Win7 or later you can use powercfg
-requestsoverride to prevent sleep while a specified program is running, or
there are several simple utilities available which prevent suspend while they
are running)

If that is not the case, the XDM logs on the XDM host might be informative, if
you have access to them.  Failing that, you could use wireshark or similar to
monitor the XDMCP protocol interactions.

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

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

Re: Windows 7 64 Bit flashes DOSBox visible on Desktop when using run-1.3.0 or run2-0.4.2 to start Cygwin commands

[Marco Atzeri]

On 28/01/2014 10:37, dyle wrote:

Hi *,

[this is my 2nd email ... got myself some mailing-list registration
problems as well ... sorry for the noise]

I try to start cygwin commands without a DOS-Box as suggested by run and
run2. To no avail. I see the CMD-Window (DOS-Box) flashing up (and down
again). I tried cygwin and cygwin64 on a Windows 7 64Bit machine.

The command does complete successful (e.g. just a #!/bin/sh CR ls -1 |
wc -l  count_file.txt) but I cannot help perceiving the opening and
immediate closing of the DOSBox window. Running a series of such commands
in a loop would render my Windows desktop into a stroboscope.


if you need to run a series of command, why don't you use
the mintty terminal ?
I do not understand what are you trying to achieve with run,
it seems the wrong tool for your example.

If you want to put a stop just before closing the scripts,
just add a read
#!/bin/sh CR ls -1 |  wc -l  count_file.txt CR read

and it will wait a Return before completing the script and
closing the window.


Also I looked up the cygwin (and winsup) sources but was not lucky to find
any code or run or run2. And there's no reference whatsoever in
/usr/share/doc/run and /usr/share/doc/run2 on where to *obtain* the sources
for these packages. They do not seem to be included in the regular cygwin
CVS.


use setup do download the source package.
All sources are available on Select Packages window,
forth column is called Scr ?

Check the box, it will be deployed in /usr/src



I do not know what I'm doing wrong, since Google tells me it should work
without popping up a DOS-Box window.

Could anyone please post me some advice (or tell me where to obtain the
sources)?


Thx,
Oliver




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

Re: Windows 7 64 Bit flashes DOSBox visible on Desktop when using run-1.3.0 or run2-0.4.2 to start Cygwin commands

[dyle]

Hi,

On Tue, 28 Jan 2014 12:15:31 +0100, Marco Atzeri marco.atz...@gmail.com
wrote:
 On 28/01/2014 10:37, dyle wrote:
 Hi *,
...
 if you need to run a series of command, why don't you use
 the mintty terminal ?

The User should not get any Window at all. Not even a mintty.

 I do not understand what are you trying to achieve with run,
 it seems the wrong tool for your example.
 
 If you want to put a stop just before closing the scripts,
 just add a read
 #!/bin/sh CR ls -1 |  wc -l  count_file.txt CR read
 
 and it will wait a Return before completing the script and
 closing the window.

The problem is not the too-fast closing of the window but its opening in
the first place. The script above is a mere example.

 Also I looked up the cygwin (and winsup) sources but was not lucky to
 find
 any code or run or run2. And there's no reference whatsoever in
 /usr/share/doc/run and /usr/share/doc/run2 on where to *obtain* the
 sources
 for these packages. They do not seem to be included in the regular
cygwin
 CVS.
 
 use setup do download the source package.
 All sources are available on Select Packages window,
 forth column is called Scr ?
 
 Check the box, it will be deployed in /usr/src

GREAT! Thank you Marco!

With this I see, that the error is clearly at run2_gpl.c at line 350ff:

   if (bUseMessageOnlyWorkaround)
 {
   if (!bHaveConsole)
 {
   AllocConsole ();
   bHaveConsole = TRUE;
   SetParent ((*GetConsoleWindowFP) (), HWND_MESSAGE);
 }
 }
   else if (!bHaveConsole)
 {
   bHaveConsole = run2_setup_invisible_console ();
 }


For Windows 7 the bUseMessageOnlyWorkaround is always TRUE and as I do not
have a Console Window yet the AllocConsole() function of Win32 API is
called.

This pops up a Console Window. A DOS-BOX. And there is no help to this.
Windows 7 just goes on, fires up a Window and places a cmd-prompt inside
it. Right in your face. :(

If I comment this line with

   // AllocConsole ();

then my scripts do work as expected: No DOS-BOX window pops up. Yeee!

Though stdout, stderr might be messy then. I might run in other troubles,
since there's a reason for this call. But so far this ok for me (yet).


Thx,
Oliver

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

Re: Windows 7 64 Bit - Mounting Network Drives

[Andrey Repin]

Greetings, Damian Harty!

 Can you please do the following commands in order (native windows console
 preferred, but not necessary): 
 net use

 % net use
 New connections will be remembered.


 Status   Local RemoteNetwork

 
 ---
 Unavailable  H:\\brt1itssrv003\homes\daharty
Microsoft Windows Network
 Unavailable  Z:\\wym1itsnas001\cae3\adams_db
 Microsoft Windows Network
 The command completed successfully.

That's somewhat normal in certain network setups, but only until you first
access the network drive in Explorer.

 subst

 % subst

 %

 cd /cygdrive/h

 % cd /cygdrive/h
 /cygdrive/h: No such file or directory.

 explorer H:\\

 (opens the drive correctly)

The thing should now work as normal, but...

 Close the window in either case. net use; subst; cd /cygdrive/h (does it 
 work now?)

2nd lap exactly reproduces the results of the first lap.

That sad to know...
I'm, unfortunately, out of ideas.
Perhaps,
cygcheck -srv
would shed some light.

 Also, a crucial moment - do you use a terminal session, or your machine is
 physically present at the place, and you are logging to its desktop as
 normal?

 I am sat at the laptop keyboard running the laptop in question. I log into
 its Windows desktop in the normal fashion. 

 So, to recap:

 - Windows can see the networked drives just fine.
 - Cygwin knows about them but declares them unavailable.

 Since I don't know what I don't know, I am unable to fashion a precision
 question to proceed further, except to ask what stands between me and the
 ability to make the network drives available from within cygwin?


--
WBR,
Andrey Repin (anrdae...@yandex.ru) 26.01.2014, 10:11

Sorry for my terrible english...


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

Re: Windows 7 64 Bit - Mounting Network Drives

[Andrey Repin]

Greetings, Frank Redeker!

 (SNIP)

 $ ls -ld /?/*
 ls: cannot access /?/*: No such file or directory
 
 $ ls -ld /a/*
 drwxr-xr-x 1 AnrDaemon -  0 Jun 26  2012 /a/Android
 drwxr-xr-x 1 AnrDaemon -  0 Nov  5 10:58 /a/InfoTxt
 drwxr-xr-x 1 AnrDaemon -  0 Jun 12  2012 /a/Mac
 drwxr-xr-x 1 AnrDaemon -  0 Sep  2  2009 /a/Story
 
 $ ls -ld /z/*
 drwxr-xr-x 1 AnrDaemon -  0 Nov  7 00:16 /z/bin
 -rw-r--r-- 1 AnrDaemon -   2390 May 30  2012 /z/ca.cer
 drwxr-xr-x 1 AnrDaemon -  0 Feb 28  2011 /z/crontabs
 
 A: and Z: are network drives, indeed.
 The C in your /cygdrive/ (and the /cygdrive itself) are just folders you
 created for some random reason.
 They shouldn't be there.
 
 I'm somewhat confused about your statement above. Is /cygdrive/ no
 longer used as default mount point?

It does. However,

 [C:\Games\Ja2-NO]$ cat /etc/fstab
 # For a description of the file format, see the Users Guide
 # http://cygwin.com/cygwin-ug-net/using.html#mount-table
 
 # This is default anyway:
 # none /cygdrive cygdrive binary,posix=0,user 0 0
 none/ cygdrive  binary,posix=0,noacl0   0
 C:/home /home bind  binary,posix=0,noacl0   0
 W:/ /var/run  bind  binary,posix=0,noacl0   0
 
 [C:\Games\Ja2-NO]$

 In my OOTB installation (CYGWIN_NT-6.1-WOW64 MAR 1.7.25(0.270/5/3)
 2013-08-31 20:39 i686 Cygwin) I have the following.

 $ ls -l /cygdrive/
 total 92
 drwxrwxrwx+ 1  None 0 Dec 19 13:46 b
 d-+ 1 TrustedInstaller TrustedInstaller 0 Jan 16 11:11 c
 drwx--+ 1 SYSTEM   SYSTEM   0 Jan 15 10:15 d

No comments. Could be a difference between host OS.

CYGWIN_NT-5.1 daemon2 1.7.26(0.271/5/3) 2013-11-29 11:25 i686 Cygwin


--
WBR,
Andrey Repin (anrdae...@yandex.ru) 26.01.2014, 10:16

Sorry for my terrible english...


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

Re: Windows 7 64 Bit - Mounting Network Drives

[Andrey Repin]

Greetings, Damian Harty!

 I've just realised that in my new place of employment, my Windows 7 64 Bit
 laptop isn't seeing the network drives under cygwin the way it used to by
 magic in my old place of employment.

 I can mount them using, amazingly, the mount command - or make this
 permanent in the /etc/fstab file: 

 H:   /cygdrive/h ntfs binary 0 0
 Z:   /cygdrive/z ntfs binary 0 0

 I can test that it works:

 % mount
 C:/cygwin/bin on /usr/bin type ntfs (binary,auto)
 C:/cygwin/lib on /usr/lib type ntfs (binary,auto)
 C:/cygwin on / type ntfs (binary,auto)
 H: on /cygdrive/h type unknown (binary)
 Z: on /cygdrive/z type unknown (binary)
 C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)

 ...which is lovely, except that it doesn't work as advertised:

 % cd /cygdrive
 % ls
 c

 %

 Q1: Is there something else I need to do after mounting it?

No.

 Q2: Why doesn't it automatically mount the network drives?

It does.

$ ls -ld /?/*
ls: cannot access /?/*: No such file or directory

$ ls -ld /a/*
drwxr-xr-x 1 AnrDaemon -  0 Jun 26  2012 /a/Android
drwxr-xr-x 1 AnrDaemon -  0 Nov  5 10:58 /a/InfoTxt
drwxr-xr-x 1 AnrDaemon -  0 Jun 12  2012 /a/Mac
drwxr-xr-x 1 AnrDaemon -  0 Sep  2  2009 /a/Story

$ ls -ld /z/*
drwxr-xr-x 1 AnrDaemon -  0 Nov  7 00:16 /z/bin
-rw-r--r-- 1 AnrDaemon -   2390 May 30  2012 /z/ca.cer
drwxr-xr-x 1 AnrDaemon -  0 Feb 28  2011 /z/crontabs

A: and Z: are network drives, indeed.
The C in your /cygdrive/ (and the /cygdrive itself) are just folders you
created for some random reason.
They shouldn't be there.

 I looked at the FAQs and googled and googled, all I got were repated
 descriptions of the mount command, having read all of them I am still
 missing something.

 Thanks in advance,

 Damian
 CONFIDENTIAL: The information contained in this email communication is

Please remove this crap from list mails, thank you.


--
WBR,
Andrey Repin (anrdae...@yandex.ru) 24.01.2014, 15:02

Sorry for my terrible english...


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

RE: Windows 7 64 Bit - Mounting Network Drives

[Damian Harty]

  Q2: Why doesn't it automatically mount the network drives?

 It does.

Thank you for your constructive reply. We can go around the It does/doesn't 
loop for some time, if you like.

While it may do on your machine, it is of course entirely possible that, sat at 
my machine, I am unable to access network drives through the file system as I 
have done previously.

Forgive me for attempting to drill into it by, for example, attempting to cd 
/cygdrive/h and receiving an error message.

I urge you not to reply messages that you feel are beneath you; it saves 
everybody's time, not least yours.

 Please remove this crap from list mails, thank you.

I have no control over it. Please feel free to simply ignore it.

 Sorry for my terrible english...

It's not the English that's the problem, it's the basic rudeness. Perhaps this 
is not as helpful place as I thought.

Damian
CONFIDENTIAL: The information contained in this email communication is 
confidential information intended only for the use of the addressee. 
Unauthorized use, disclosure or copying of this communication is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please notify us immediately by return email and destroy all copies of 
this communication, including all attachments.

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

Re: Windows 7 64 Bit - Mounting Network Drives

[Andrey Repin]

Greetings, Damian Harty!

  Q2: Why doesn't it automatically mount the network drives?

 It does.

 Thank you for your constructive reply. We can go around the It
 does/doesn't loop for some time, if you like. 

 While it may do on your machine, it is of course entirely possible that, sat
 at my machine, I am unable to access network drives through the file system
 as I have done previously.  

 Forgive me for attempting to drill into it by, for example, attempting to
 cd /cygdrive/h and receiving an error message.

That's a different question, of course.
Can you please do the following commands in order (native windows console
preferred, but not necessary):

net use; subst; cd /cygdrive/h
(The CD should return an error, relog if it doesn't)
explorer H:\\ (would that open the drive corectly? Close the window in either 
case.)
net use; subst; cd /cygdrive/h (does it work now?)

Also, a crucial moment - do you use a terminal session, or your machine is
physically present at the place, and you are logging to it's desktop as
normal?


--
WBR,
Andrey Repin (anrdae...@yandex.ru) 24.01.2014, 16:21

Sorry for my terrible english...


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

Re: Windows 7 64 Bit - Mounting Network Drives

[Frank Redeker]

Hallo Andrey Repin,

On 24.01.2014 12:10, Andrey Repin wrote:

 (SNIP)

 $ ls -ld /?/*
 ls: cannot access /?/*: No such file or directory
 
 $ ls -ld /a/*
 drwxr-xr-x 1 AnrDaemon -  0 Jun 26  2012 /a/Android
 drwxr-xr-x 1 AnrDaemon -  0 Nov  5 10:58 /a/InfoTxt
 drwxr-xr-x 1 AnrDaemon -  0 Jun 12  2012 /a/Mac
 drwxr-xr-x 1 AnrDaemon -  0 Sep  2  2009 /a/Story
 
 $ ls -ld /z/*
 drwxr-xr-x 1 AnrDaemon -  0 Nov  7 00:16 /z/bin
 -rw-r--r-- 1 AnrDaemon -   2390 May 30  2012 /z/ca.cer
 drwxr-xr-x 1 AnrDaemon -  0 Feb 28  2011 /z/crontabs
 
 A: and Z: are network drives, indeed.
 The C in your /cygdrive/ (and the /cygdrive itself) are just folders you
 created for some random reason.
 They shouldn't be there.
 
I'm somewhat confused about your statement above. Is /cygdrive/ no
longer used as default mount point?

In my OOTB installation (CYGWIN_NT-6.1-WOW64 MAR 1.7.25(0.270/5/3)
2013-08-31 20:39 i686 Cygwin) I have the following.

$ ls -l /cygdrive/
total 92
drwxrwxrwx+ 1  None 0 Dec 19 13:46 b
d-+ 1 TrustedInstaller TrustedInstaller 0 Jan 16 11:11 c
drwx--+ 1 SYSTEM   SYSTEM   0 Jan 15 10:15 d
d-+ 1 TrustedInstaller TrustedInstaller 0 Jan 15 10:15 e
drwxrwxrwx+ 1 SYSTEM   SYSTEM   0 Jan 15 10:15 f
drwxrwxrwx+ 1   0 Sep 17 12:37 g
drwxrwxrwx+ 1 Administrators    0 Sep 30 10:59 h
drwxrwxrwx  1   0 Jan 20 14:42 o
drwxrwxrwx  1   0 Dec 17 13:04 p
drwxrwxrwx+ 1   0 Jan 21 17:10 t
drwxr-xr-x  1   0 Jan  8 11:19 u
drwxr-xr-x  1   0 Nov 24  2011 w
drwxrwxrwx  1   0 Jan 20 14:14 z

$ mount
D:/Program_Files_32/cygwin/bin on /usr/bin type ntfs (binary,auto)
D:/Program_Files_32/cygwin/lib on /usr/lib type ntfs (binary,auto)
D:/Program_Files_32/cygwin on / type ntfs (binary,auto)
B: on /cygdrive/b type ntfs (binary,posix=0,user,noumount,auto)
C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto)
D: on /cygdrive/d type ntfs (binary,posix=0,user,noumount,auto)
E: on /cygdrive/e type ntfs (binary,posix=0,user,noumount,auto)
F: on /cygdrive/f type ntfs (binary,posix=0,user,noumount,auto)
G: on /cygdrive/g type ntfs (binary,posix=0,user,noumount,auto)
H: on /cygdrive/h type ntfs (binary,posix=0,user,noumount,auto)
O: on /cygdrive/o type smbfs (binary,posix=0,user,noumount,auto)
P: on /cygdrive/p type smbfs (binary,posix=0,user,noumount,auto)
T: on /cygdrive/t type ntfs (binary,posix=0,user,noumount,auto)
U: on /cygdrive/u type smbfs (binary,posix=0,user,noumount,auto)
W: on /cygdrive/w type smbfs (binary,posix=0,user,noumount,auto)
Z: on /cygdrive/z type smbfs (binary,posix=0,user,noumount,auto)

$ cat /etc/fstab
# For a description of the file format, see the Users Guide
# http://cygwin.com/cygwin-ug-net/using.html#mount-table

# This is default anyway:
# none /cygdrive cygdrive binary,posix=0,user 0 0


Mit freundlichen Grüßen / Best Regards

Frank Redeker


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

RE: Windows 7 64 Bit - Mounting Network Drives

[Damian Harty]

 Can you please do the following commands in order (native windows console 
 preferred, but not necessary):
 net use

% net use
New connections will be remembered.


Status   Local RemoteNetwork


---
Unavailable  H:\\brt1itssrv003\homes\daharty
   Microsoft Windows Network
Unavailable  Z:\\wym1itsnas001\cae3\adams_db
Microsoft Windows Network
The command completed successfully.

 subst

% subst

%

 cd /cygdrive/h

% cd /cygdrive/h
/cygdrive/h: No such file or directory.

 explorer H:\\

(opens the drive correctly)

 Close the window in either case. net use; subst; cd /cygdrive/h (does it work 
 now?)

   2nd lap exactly reproduces the results of the first lap.

 Also, a crucial moment - do you use a terminal session, or your machine is 
 physically present at the place, and you are logging to its desktop as normal?

I am sat at the laptop keyboard running the laptop in question. I log into its 
Windows desktop in the normal fashion.

So, to recap:

- Windows can see the networked drives just fine.
- Cygwin knows about them but declares them unavailable.

Since I don't know what I don't know, I am unable to fashion a precision 
question to proceed further, except to ask what stands between me and the 
ability to make the network drives available from within cygwin?


CONFIDENTIAL: The information contained in this email communication is 
confidential information intended only for the use of the addressee. 
Unauthorized use, disclosure or copying of this communication is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please notify us immediately by return email and destroy all copies of 
this communication, including all attachments.

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

Re: Windows 7 64 Bit - Mounting Network Drives

[Corinna Vinschen]

On Jan 24 09:53, Damian Harty wrote:
 O learned Denizens,
 
 I'm best described as a feverish fumbler rather than some sort of expert. 
 However, I have been around the block a few times but now I find myself 
 feeling like a newbie again.
 
 I've just realised that in my new place of employment, my Windows 7 64 Bit 
 laptop isn't seeing the network drives under cygwin the way it used to by 
 magic in my old place of employment.
 
 I can mount them using, amazingly, the mount command - or make this 
 permanent in the /etc/fstab file:
 
 H:   /cygdrive/h ntfs binary 0 0
 Z:   /cygdrive/z ntfs binary 0 0

Don't do that.  The /cygdrive prefix is the default POSIX path prefix
for drives mounted by Windows.  Any drive X: is automatically available
as /cygdrive/x.  You can change the cygdrive prefix in /etc/fstab (I'm
using /mnt, for instance), but you can't manually mount stuff under the
cygdrive prefix path.  Ths *is* documented:

  http://cygwin.com/cygwin-ug-net/using.html#cygdrive

Remove the above mount points, exit your Cygwin shells, and try
again.  If the H and Z drives still don't show up under your /cygdrive
prefix, they are probably not really mounted in your Windows session.


Corinna

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


pgpaCUx93nhbJ.pgp
Description: PGP signature

RE: Windows 7 64 Bit - Mounting Network Drives

[Damian Harty]

 Remove the above mount points, exit your Cygwin shells, and try again.  If 
 the H and Z drives still don't show up under your /cygdrive prefix, they are 
 probably not really mounted in your Windows session.

OK, so back to where I started. A virginal /etc/fstab once more.

Windows Explorer readily shows drives H: and Z:. That looks like they are 
really mounted to me, but I wouldn't know what constitutes a rigorous test or 
even what the definition of really mounted actually is.

I read quite a lot of the documentation, but I am out of practice reading unix 
documentation these days.

When I plug in a USB drive, Windows immediately mounts it as E: and Cygwin can 
see it no problem.

Damian



CONFIDENTIAL: The information contained in this email communication is 
confidential information intended only for the use of the addressee. 
Unauthorized use, disclosure or copying of this communication is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please notify us immediately by return email and destroy all copies of 
this communication, including all attachments.

Re: Windows 7 64 Bit - Mounting Network Drives

[tednolan]

In message a85cced36f59429ab961dec7c79b4...@bl2pr02mb449.namprd02.prod.outlook
.comyou write:

Windows Explorer readily shows drives H: and Z:. That looks like they
are reall y mounted to me, but I wouldn't know what constitutes a
rigorous test or even w hat the definition of really mounted actually
is.


My experience with cygwin is that if I can open a DOS command window and
successfully do:

dir k:

Drive k will be accessible as /cygdrive/k

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

RE: Windows 7 64 Bit - Mounting Network Drives

[Damian Harty]

If I run net use from a simple DOS prompt (Windows\system32\cmd.exe) I get:

H:\net use
New connections will be remembered.

Status   Local RemoteNetwork


---
OK   H:\\brt1itssrv003\homes\daharty
Microsoft Windows Network
OK   Z:\\wym1itsnas001\cae3\adams_db
Microsoft Windows Network
The command completed successfully.

Note the drive it starts from, by the way - the one that may or may not be 
really mounted. The same thing a moment later from a brand new Cygwin shell 
produces:

% net use
New connections will be remembered.

Status   Local RemoteNetwork


---
Unavailable  H:\\brt1itssrv003\homes\daharty
Microsoft Windows Network
Unavailable  Z:\\wym1itsnas001\cae3\adams_db
Microsoft Windows Network
The command completed successfully.

Diagnostic instructions welcome...

Damian

CONFIDENTIAL: The information contained in this email communication is 
confidential information intended only for the use of the addressee. 
Unauthorized use, disclosure or copying of this communication is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please notify us immediately by return email and destroy all copies of 
this communication, including all attachments.

RE: Windows 7 64 Bit - Mounting Network Drives

[Damian Harty]

 My experience with cygwin is that if I can open a DOS command window and 
 successfully do:

dir k:

 Drive k will be accessible as /cygdrive/k

*Until now* that has been my experience also...

Check this out for curiouser and curiouser:

Start a command shell from inside Cygwin:

 % /cygdrive/c/Windows/System32/cmd.exe
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

Then run net use

C:\cygwin\home\dahartynet use
net use
New connections will be remembered.

Status   Local RemoteNetwork


---
Unavailable  H:\\brt1itssrv003\homes\daharty
Microsoft Windows Network
Unavailable  Z:\\wym1itsnas001\cae3\adams_db
Microsoft Windows Network
The command completed successfully.

C:\cygwin\home\daharty

The Cygwin icon (installed by the installer and nothing to do with me) has the 
following properties:

C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico -t Cygwin -

If at the DOS prompt I run, say, c:\cygwin\bin\tcsh.exe -l and try net use 
then all is in order with that command. This is a minty issue; I need not to be 
using mintty.

Damian




CONFIDENTIAL: The information contained in this email communication is 
confidential information intended only for the use of the addressee. 
Unauthorized use, disclosure or copying of this communication is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please notify us immediately by return email and destroy all copies of 
this communication, including all attachments.

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

Re: Windows 7 64 Bit - Mounting Network Drives

[Corinna Vinschen]

On Jan 24 15:10, Damian Harty wrote:
  My experience with cygwin is that if I can open a DOS command window and 
  successfully do:
 
 dir k:
 
  Drive k will be accessible as /cygdrive/k
 
 *Until now* that has been my experience also...
 
 Check this out for curiouser and curiouser:
 
 Start a command shell from inside Cygwin:
 
  % /cygdrive/c/Windows/System32/cmd.exe
 Microsoft Windows [Version 6.1.7601]
 Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 
 Then run net use
 
 C:\cygwin\home\dahartynet use
 net use
 New connections will be remembered.
 
 Status   Local RemoteNetwork
 
 
 ---
 Unavailable  H:\\brt1itssrv003\homes\daharty
 Microsoft Windows Network
 Unavailable  Z:\\wym1itsnas001\cae3\adams_db
 Microsoft Windows Network
 The command completed successfully.
 
 C:\cygwin\home\daharty
 
 The Cygwin icon (installed by the installer and nothing to do with me) has 
 the following properties:
 
 C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico -t Cygwin -
 
 If at the DOS prompt I run, say, c:\cygwin\bin\tcsh.exe -l and try net use 
 then all is in order with that command. This is a minty issue; I need not to 
 be using mintty.

Are you starting mintty as admin?  That might explain it.

Corinna

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


pgpbe8BfRjeno.pgp
Description: PGP signature

RE: Windows 7 64 Bit - Mounting Network Drives

[Damian Harty]

 Are you starting mintty as admin?  That might explain it.

I'm not observing a difference between running mintty as normal and 
right-clicking and doing run as administrator. If that wasn't what you were 
asking, then I apologise.

It seems if I start a cmd shell standalone and run c:\cygwin\bin\tcsh.exe -l 
then it works. If I put C:\Windows\System32\cmd.exe /K C:\cygwin\bin\tcsh.exe 
-l into the properties box and start it, then it fails.

At this point, I am fully baffled but at least I have a workaround - start the 
shell from the windows command prompt.

Damian
CONFIDENTIAL: The information contained in this email communication is 
confidential information intended only for the use of the addressee. 
Unauthorized use, disclosure or copying of this communication is strictly 
prohibited and may be unlawful. If you have received this communication in 
error, please notify us immediately by return email and destroy all copies of 
this communication, including all attachments.

Re: Windows 7 64 Bit - Mounting Network Drives

[Christopher Faylor]

On Fri, Jan 24, 2014 at 11:31:16AM +, Damian Harty wrote:
On Fri, Jan 24, 2014 at 03:10:41PM +0400, Andrey Repin wrote:
Please remove this crap from list mails, thank you.

I have no control over it.  Please feel free to simply ignore it.

Sorry but this disclaimer is against site policy.  I've added it to the
disclaimer block for sourceware.org so you won't be able to use it in
any future messages.

cgf

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

Re: Windows 7 64 Bit - Mounting Network Drives

[Larry Hall (Cygwin)]

On 1/24/2014 6:31 AM, Damian Harty wrote:

Please remove this crap from list mails, thank you.

I have no control over it. Please feel free to simply ignore it.


Actually, you're lucky your email wasn't bounced back to you because of
this.  It's site policy to not allow such disclaimers.  See the FAQ entry
on this policy here:

  https://sourceware.org/lists.html#disclaimer-bounce

The fact that your email wasn't bounced for not complying with this
policy isn't a tacit acceptance of your email as a special case.
If you have no ability to remove the disclaimer, you'll need to use
another email service to communicate with lists on sourceware.org.

--
Larry

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

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

RE: Windows 7 64 Bit - Mounting Network Drives

[Lavrentiev, Anton (NIH/NLM/NCBI) [C]]

BTW, there is a type there, IMO:

  http://cygwin.com/cygwin-ug-net/using.html#cygdrive

quote
  none /cygdrive cygdrive binary 0 0
  D:   /cygdrive/d somefs text 0 0
will not make file access using the /mnt/d path prefix suddenly using textmode
/quote

The sentence after the fstab excerpt should have referred to /cygdrive/d, not
to /mnt/d (alternatively, the excerpt should have used /mnt instead
of /cygdrive throughout).

HTH,

Anton Lavrentiev
Contractor NIH/NLM/NCBI

Re: Windows 7 64 Bit - Mounting Network Drives

[Damian Harty]

  Please remove this crap from list mails, thank you.
  I have no control over it. Please feel free to simply ignore it.
 
 Actually, you're lucky your email wasn't bounced back to you because of this. 
  It's site policy to not allow such disclaimers.   See the FAQ entry on this 
 policy here:
 
    https://sourceware.org/lists.html#disclaimer-bounce

I have seen it now that it has been pointed out. I have changed email addresses 
in order to comply with The Rules, having first being addressed by a rude 
adolescent and then told how lucky I am not to have my emails bounced. I humbly 
acknowledge Your Authority.

What a splendid example of a warm community this is and how much I yearn to 
participate. If only there were some factual knowledge of the matter at hand, 
too, it would be ideal in many respects.

And the pigs began to look like men. (George Orwell)

The bottom line is that cygwin used to work for me and now it doesn't. I've 
expended a reasonable amount of effort attempting to describe/get round the 
problem but now I've lost interest. A large part of that is because I asked 
politely and was treated very rudely. I subscribe to a number of fora and such 
behaviour is by no means inevitable, however it does appear to be the default 
here. 

How disappointing, but not in the least bit life-changing, of course. Utterly 
unimportant in the grand scheme of things.

Whatever. (Alicia Silverstone).


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

Re: Windows 7 64 Bit - Mounting Network Drives

[Alexander Kriegisch]

Dear community,

I have read this conversation and am honestly shocked about the way Damian 
(whom I do not know, BTW) was greeted in response to his initial question. I 
have noticed several times that too often here talk is about compliance to a 
string of rules and acronyms anyone daring to post here must have read in order 
not to annoy the rulers of this list. While I respect the time and dedication 
of every expert here and know how much it sucks having to read badly phrased 
subjects, badly asked questions and so forth, I think there is no need to be 
condescending. I see a lot of lecturing here. Some questions are ignored 
altogether for reasons their authors do not even know.

I like Cygwin, I want to thank every helpful and dedicated person here for 
their expertise and patience, but anyway, I have had enough and am going to 
unsubscribe from this list.

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

Re: Windows 7 64 Bit - Mounting Network Drives

[Christopher Faylor]

On Fri, Jan 24, 2014 at 05:27:32PM +, Damian Harty wrote:
  Please remove this crap from list mails, thank you.
  I have no control over it. Please feel free to simply ignore it.

Actually, you're lucky your email wasn't bounced back to you because of
this.  It's site policy to not allow such disclaimers.
See the FAQ entry on this policy here:

 ? ?https://sourceware.org/lists.html#disclaimer-bounce

I have seen it now that it has been pointed out.  I have changed email
addresses in order to comply with The Rules, having first being
addressed by a rude adolescent and then told how lucky I am not to have
my emails bounced.  I humbly acknowledge Your Authority.

What a splendid example of a warm community this is and how much I
yearn to participate.  If only there were some factual knowledge of the
matter at hand, too, it would be ideal in many respects.

And the pigs began to look like men. (George Orwell)

Freedom is the right to tell people what they do not want to hear.
(George Orwell)

The bottom line is that cygwin used to work for me and now it doesn't.
I've expended a reasonable amount of effort attempting to describe/get
round the problem but now I've lost interest.  A large part of that is
because I asked politely and was treated very rudely.  I subscribe to a
number of fora and such behaviour is by no means inevitable, however it
does appear to be the default here.?

You owe me an apology.  (Cole Oyl, Popeye)

How disappointing, but not in the least bit life-changing, of course.
Utterly unimportant in the grand scheme of things.

Whatever. (Alicia Silverstone).

I was just totally clueless. (Alicia Silverstone)

FYI, you are coming across as ungrateful for the help provided by six
people (one of which was a Cygwin lead) in this thread.

Pragmatically speaking, focusing (in two messages) on one non-English
speaker's use of the word crap, disregarding the help that he and
others provided, and then going into full bombast mode, is not an
effective way to achieve support.  Perhaps that's fine with you because
you don't plan on sullying our mailing list again but I just thought I
should make that clear.  References:

http://cygwin.com/problems.html
http://www.catb.org/~esr/faqs/smart-questions.html
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html

Also, some more warmth: It is likely that if you choose to reply in the
tone of the above that you will be redirected to the cygwin-talk mailing
list.  Ranting is allowed there.  Not so much here.

cgf
--
Christopher Faylor  spammer? - aaas...@sourceware.org
Cygwin Co-Project Leaderaaas...@duffek.com

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

Re: Windows 7 64 Bit - Mounting Network Drives

[Corinna Vinschen]

On Jan 24 15:58, Damian Harty wrote:
  Are you starting mintty as admin?  That might explain it.
 
 I'm not observing a difference between running mintty as normal and 
 right-clicking and doing run as administrator. If that wasn't what you were 
 asking, then I apologise.
 
 It seems if I start a cmd shell standalone and run c:\cygwin\bin\tcsh.exe 
 -l then it works. If I put C:\Windows\System32\cmd.exe /K 
 C:\cygwin\bin\tcsh.exe -l into the properties box and start it, then it 
 fails.
 
 At this point, I am fully baffled but at least I have a workaround - start 
 the shell from the windows command prompt.

But that should really not be necessary.  There's no reason that
starting from a Windows console shows the drives as OK but starting
mintty shows them as Unavailable.  The drives are user token bound, and
the user token in the mintty window is the same as the token in the a
console window.

Just for testing, did you try to access the drives from mintty?

I mean, assuming you start mintty, what happens if you do this (and only
this) after starting it:

  $ net use
  $ id
  $ ls /cygdrive/h
  $ net use


Corinna

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


pgpgXj7F85CLC.pgp
Description: PGP signature

Re: Windows 7 64 Bit - Mounting Network Drives

[Larry Hall (Cygwin)]

On 1/24/2014 12:27 PM, Damian Harty wrote:




Please remove this crap from list mails, thank you.

I have no control over it. Please feel free to simply ignore it.



Actually, you're lucky your email wasn't bounced back to you because
of  this.  It's site policy to not allow such disclaimers.  See the FAQ
entry on this policy here:

https://sourceware.org/lists.html#disclaimer-bounce


I have seen it now that it has been pointed out. I have changed email
addresses in order to comply with The Rules, having first being addressed by
a rude adolescent and then told how lucky I am not to have my emails
bounced. I humbly acknowledge Your Authority.


It's not my Authority.  It's the authority of those running the site
you're addressing.  I think you've misjudged the point of my posting though.
My goal was to keep you from facing difficulty with any future posts and
the rest of us from these content-free disclaimers if/when they slipped
through.  If that caused your feelings to be hurt then you've misinterpreted
what I wrote.  There was no negative energy coming from my end.

--
Larry

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

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

Re: windows 7 : files permission problem

[pfx]

Le 20/03/2013 20:01, Andrey Repin a écrit :

#
# Why cygwin doesn't display posix permissions ?
#

Because the ACL set on the file do not match any POSIX permissions. The
presence of extended attributes (like ACL) is indicated by + at the end of
POSIX permission byte.
OK, I must re-read the documentation ! 
(http://cygwin.com/cygwin-ug-net/ntsec.html)


[...]

Any idea ?

As a general rule, if you are going to mix Cygwin and native tools, let
windows handle file permissions (noacl mount option), and you'll not see
such issues again.

Indeed, this fixes my problem.
Many thanks

But it seems to me that we always mix native and windows tools. I wonder 
why 'noacl' is not a default mount option ?



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

Re: windows 7 : files permission problem

[Eric Blake]

On 03/21/2013 02:17 AM, pfx wrote:
 But it seems to me that we always mix native and windows tools. I wonder
 why 'noacl' is not a default mount option ?

Because noacl is not posix-like, and other people (like myself) do NOT
mix native tools, and prefer that cygwin be as posix-like as possible by
default, and that explicitly changing things is your way of
acknowledging that some of the posix expectations are lost in order to
gain interoperability with non-free software.

-- 
Eric Blake   eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org



signature.asc
Description: OpenPGP digital signature

Re: windows 7 : files permission problem

[Andrey Repin]

Greetings, pfx!

 Hi,

 when I use 'cp -R' to copy files, I can't access to the target file (I 
 have no permission on the target files)

 I reproduce this problem with a fresh install of windows 7 and cygwin
 my account is a user account (not admin)

 from a DOS box, I create c:\test\d1\d2\test.txt

C:\md test
C:\cd test
C:\testmd d1
C:\testmd d1\d2
C:\testecho test  d1\d2\test.txt

 from the cygwin console

 $ cd /cygdrive/c/test/
 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ ll
 total 0
 d-+ 1 patrick None 0 Mar 20 17:18 d1
 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ ll d1/
 total 0
 d-+ 1 patrick None 0 Mar 20 17:18 d2
 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ ll d1/d2/
 total 1
 --+ 1 patrick None 7 Mar 20 17:18 test.txt

 #
 # Why cygwin doesn't display posix permissions ?
 #

Because the ACL set on the file do not match any POSIX permissions. The
presence of extended attributes (like ACL) is indicated by + at the end of
POSIX permission byte.

 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ cat d1/d2/test.txt
 test

 #
 # I have no permission on d1/d2/test.txt, but I can 'CAT' it
 #

Oh, indeed, you DO have permissions. Else you would not be able to cat it.

 #
 # now, I copy the ./d1/* to ./win
 #
 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ mkdir sub

 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ cp -R d1/* sub/

 #
 # no more posix file permission
 #
 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ ll sub/
 total 0
 d-+ 1 patrick None 0 Mar 20 17:21 d2

 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ ll sub/d2/
 total 1
 -- 1 patrick None 7 Mar 20 17:21 test.txt

And here is the fine, that have no permissions set whatsoever.

 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ cat sub/d2/test.txt
 cat: sub/d2/test.txt: Permission denied
 #
 # but now I can acces the file from cygwin
 #

Doesn't looks like so...

 I return to the DOS box

C:\testtype sub\d2\test.txt
 Access is denied.

 I can't read the file from windows

You can't read it from both places. At least, not until you launch either
console from a superadmin account. And stop referring to console as DOS box,
that's just wrong.

 Of course, I have no problem with cygwin with my XP computer

 Any idea ?

As a general rule, if you are going to mix Cygwin and native tools, let
windows handle file permissions (noacl mount option), and you'll not see
such issues again.

 more tech info :

 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ getfacl.exe .
 # file: .
 # owner: patrick
 # group: None
 user::---
 group::---
 group:root:rwx
 group:SYSTEM:rwx
 group:Users:r-x
 mask:rwx
 other:---
 default:user::---
 default:group::---
 default:group:root:rwx
 default:group:SYSTEM:rwx
 default:group:Users:r-x
 default:mask:rwx
 default:other:---


 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ getfacl.exe d1/d2/test.txt
 # file: d1/d2/test.txt
 # owner: patrick
 # group: None
 user::---
 group::---
 group:root:rwx
 group:SYSTEM:rwx
 group:Users:r-x
 mask:rwx
 other:---


 patrick@WIN-K396JDQPSD0 /cygdrive/c/test
 $ getfacl.exe sub/d2/test.txt
 # file: sub/d2/test.txt
 # owner: patrick
 # group: None
 user::---
 group::---
 mask:rwx
 other:---


 $ cygcheck -s
 [...]
 Windows 7 Home Basic N Ver 6.1 Build 7601 Service Pack 1
 Running under WOW64 on AMD64
 [...]
 Output from C:\dev\cygwin\bin\id.exe
 UID: 1005(patrick) GID: 513(None)
 513(None)  545(Users)
 [...]
  Cygwin DLL version info:
  DLL version: 1.7.17


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



--
WBR,
Andrey Repin (anrdae...@freemail.ru) 20.03.2013, 22:53

Sorry for my terrible english...


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

Re: Windows 7, cron, permissions

[Guy Harrison]

Hi Marco,

Sorry. I believed it best to post all available details. The key problem is 
this message..

Access Denied. Administrator permissions are needed to use the selected 
options. Use an administrator command prompt to complete these tasks.

On Monday 28 May 2012 16:59:45 marco atzeri wrote:
 On 5/28/2012 4:11 PM, Guy Harrison wrote:
  Hi Folks,
 
  The actual fault lies in 'cj-defrag' where 'cjx' mails the output
  of 'cj-defrag'. 'cj-defrag' calls a child script 'sd-defrag' and
  all 'sd-defrag' does is call df.exe. The single line at the bottom
  simplifies the problem: do a quick defrag of the E: drive.

 [cut]

 please rewind and try to explain your problem so that anyone that
 has no clue of your problem could follow you. I already had headache
 after the first sentences.

 Did you notice that your mail was the supposed 1st mail of a
 chain and we have no background of your experience..

TIA
Guy

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

Re: Windows 7, cron, permissions

[marco atzeri]

On 5/28/2012 4:11 PM, Guy Harrison wrote:


Hi Folks,

The actual fault lies in 'cj-defrag' where 'cjx' mails the output
of 'cj-defrag'. 'cj-defrag' calls a child script 'sd-defrag' and
all 'sd-defrag' does is call df.exe. The single line at the bottom
simplifies the problem: do a quick defrag of the E: drive.

[cut]

please rewind and try to explain your problem so that anyone that
has no clue of your problem could follow you. I already had headache
after the first sentences.

Did you notice that your mail was the supposed 1st mail of a
chain and we have no background of your experience..

Problem reports:   http://cygwin.com/problems.html


TIA
Guy


Regards
Marco



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

Re: Windows 7 x64 - Postinstall script errors - Cygwin V 1.7.9-1

[Mark Geisert]

Robert Miles writes:
 How do you switch to the new startup.exe?  Every time I try to use the 
 Cygwin startup.exe, it tells me it has found a new file that might not 
 be compatible with the startup.exe I'm using, but does not give enough 
 useful information on how to switch to a newer version.

You've gone off-subject but here's a quick answer.  It's setup.exe not
startup.exe.  You can pick up the most current one at the same place you likely
picked up the original, on the Cygwin home page http://cygwin.com/ .

Look on that page for a link to setup.exe .  Click that link.  That'll pull the
current setup.exe onto your machine.  Put it in the same location you put the
original setup.exe.  Now when you click on the Cygwin Setup icon on your
desktop, assuming you've got that icon, you'll be running the most current
setup.exe.  Piece of cake.
HTH,

..mark

--
Denied.  Denied like a Bank of Ponzi credit card.  -- Get Fuzzy


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

Re: Windows 7 x64 - Postinstall script errors - Cygwin V 1.7.9-1

[Robert Miles]

On 2/3/2012 12:01 PM, Tim Prince wrote:

 On 02/03/2012 12:39 PM, Carbonera, Carlos wrote:


Problem 1. I am not able to install Cygwin on Windows 7 x64. I get 
the following errors at the end of the installation:



Postinstall script errors

Upon finishing the installation, I do not obtain the CYGWIN icon on 
my desktop as I requested, and the only two applications that appear 
on my All Programs/Cygwin folder are related to the application 
urxvtc-X.exe.




Problem 2: I cannot find the application that starts the X-Server.  I 
found the CYGWIN.bat file and created a shortcut on my desktop. The 
CYGWIN bash application seems to be working.




  I am using startxwin to start the X-Server; is this the the 
recommended method?




Did you use the current startup.exe recommended on cygwin.com?
startxwin works for me, but it's messy with lots of warnings.  The new 
installation should give you an xwin icon on the startup menu. which 
puts a menu icon in the hidden icons, with xserver among the selections.


How do you switch to the new startup.exe?  Every time I try to use the 
Cygwin startup.exe, it tells me it has found a new file that might not 
be compatible with the startup.exe I'm using, but does not give enough 
useful information on how to switch to a newer version.


--

Robert Miles

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

Re: Windows 7 x64 - Postinstall script errors - Cygwin V 1.7.9-1

[Tim Prince]

 On 02/03/2012 12:39 PM, Carbonera, Carlos wrote:


Problem 1. I am not able to install Cygwin on Windows 7 x64. I get the 
following errors at the end of the installation:


Postinstall script errors 



Upon finishing the installation, I do not obtain the CYGWIN icon on my desktop as I 
requested, and the only two applications that appear on my All 
Programs/Cygwin folder are related to the application urxvtc-X.exe.



Problem 2: I cannot find the application that starts the X-Server.  I found the 
CYGWIN.bat file and created a shortcut on my desktop. The CYGWIN bash 
application seems to be working.



  I am using startxwin to start the X-Server; is this the the recommended 
method?



Did you use the current startup.exe recommended on cygwin.com?
startxwin works for me, but it's messy with lots of warnings.  The new 
installation should give you an xwin icon on the startup menu. which 
puts a menu icon in the hidden icons, with xserver among the selections.


--
Tim Prince


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

Re: Windows 7 packages

[Christopher Faylor]

On Thu, Dec 01, 2011 at 08:34:25PM -0600, i...@kalani.com wrote:
What packages do you need to get the latest version of Cygwin running  
on Windows 7?

There are no special packages required to get Cygwin running on any
OS after Windows 2000.

cgf

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

Re: Windows 7 packages

[Christopher Faylor]

On Thu, Dec 01, 2011 at 10:57:03PM -0500, Christopher Faylor wrote:
On Thu, Dec 01, 2011 at 08:34:25PM -0600, i...@kalani.com wrote:
What packages do you need to get the latest version of Cygwin running  
on Windows 7?

There are no special packages required to get Cygwin running on any
OS after Windows 2000.

And, just to be clearer: You don't need any special package to get
Cygwin running on anything.  Just install it and it runs.

cgf

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

RE: Windows 7 Ultimate 64bit installation error and python

[Gerald Baggett]

win dows 7 ultimate 64 bit system eror when trying to install cygwin
with all packages
C:\Users\JackieC:\cygwin\etc\postinstall\xinetd.sh
Welcome to Git (version 1.7.7.1-preview20111027)


Run 'git help git' to display the help index.
Run 'git help command' to display help for specific commands.
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/chargen-dgram':
No such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/chargen-stream':
No such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/daytime-dgram':
No such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/daytime-stream':
No such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/discard-dgram':
No such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/discard-stream':
No such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/echo-dgram': No
such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/echo-stream': No
such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/ftp-sensor': No
such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/services': No
such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/tcpmux-server':
No such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/time-dgram': No
such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/time-stream': No
such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.conf': No such file
or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/sysconfig/xinetd': No such
file or directory
C:\cygwin\etc\postinstall\xinetd.sh: line 92: /usr/bin/xinetd-config:
No such file or directory

C:\Users\JackieC:\cygwin\etc\postinstall\inetutils.sh
The filename, directory name, or volume label syntax is incorrect.

C:\Users\JackieC:\cygwin\etc\postinstall\inetutils.sh
Welcome to Git (version 1.7.7.1-preview20111027)


Run 'git help git' to display the help index.
Run 'git help command' to display help for specific commands.
/usr/bin/cp: cannot stat `/etc/defaults/etc/ftpusers': No such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/ftpwelcome': No such file
or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/inetd.conf': No such file
or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/shells': No such file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/syslog.conf': No such file
or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/ftpd': No such
file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/talk': No such
file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/telnet': No such
file or directory
/usr/bin/cp: cannot stat `/etc/defaults/etc/xinetd.d/uucp': No such
file or directory
C:\cygwin\etc\postinstall\inetutils.sh: line 62: /usr/bin/iu-config:
No such file or directory
C:\cygwin\etc\postinstall\inetutils.sh: line 65:
/usr/bin/syslogd-config: No such file or directory

C:\Users\Jackie

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

Re: Windows 7 Ultimate 64bit installation error and python

[Corinna Vinschen]

On Nov 11 02:18, Gerald Baggett wrote:
 Package: Unknown package
 inetutils.sh exit code 1
 xinetd.sh exit code 1
 
 
 
 $ repo init -u g...@github.com:LiquidSmoothROMs/android_vendor_liquid.git
       0 [main] python 6780 C:\cygwin\bin\python.exe: *** fatal error -
 unable to remap \\?\C:\cygwin\lib\python2.6\lib-dynload\select.dll to
 same addr
 ess as parent: 0x38 != 0x3F

Try rebaseall.  See /usr/share/doc/rebase/README.


Corinna

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

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

Re: Windows 7 Ultimate 64bit installation error and python

[Gerald Baggett]

Try rebaseall.  See /usr/share/doc/rebase/README.


Corinna

I have already tried that already and this is the results to even that

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

Re: Windows 7 Ultimate 64bit installation error and python

[Corinna Vinschen]

On Nov 11 06:16, Gerald Baggett wrote:
 Try rebaseall.  See /usr/share/doc/rebase/README.
 
 
 Corinna
 
 I have already tried that already and this is the results to even that

0x38 or 0x3F are pretty weird addresses for a DLL.  This
should only happen, if a DLL isn't rebased, or if DLLs collide.

What rebase package version did you use?  If you used the latest 4.0.1,
you can call `rebase -s -i'.  This prints the list of DLLs which have
been rebased in the latest run, together with their default load
addresses and size.  If adjacent DLLs collide, `rebase -s -i' will print
an asterisk right after the size at the end of the line.  Search for
select.dll and see if it collides with another DLL.  If so, run
rebaseall again.


Corinna

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

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

Re: Windows 7? Two different versions of a file depending on how it is accessed

[Andrew Hancock]

Sorry, this thread has been superseded by Divergent file system
contents, Cygwin versus Windows 7
(http://article.gmane.org/gmane.os.cygwin/127335).  During the thick
of troubleshooting, I lost track of the fact that I posted this
earlier understanding of the problem.

On Sun, Jun 26, 2011 at 10:40 AM, Andrew Hancock andymhanc...@gmail.com wrote:
 I am seeing two different versions of a file depending on how I access
 it.  Specifically, the file C:\Program Files (x86)\Vim\_vimrc uses
 plain text to provide startup specifications for the text editor gvim.
  This is the standalone installation for Windows, not the one the one
 that comes with Cygwin.  However, that is just the problem context.
 The real issue is that I see two different versions of that file.  The
 first version is the original one that came with the installation.  I
 modified it by adding the lines:

   set guioptions-=m
   set guioptions-=T

 I got a warning that the file is read-only.  It isn't according
 read-only to ls -l, but I thought that the discrepancy must have
 been due to Windows 7's more complicated security (which I haven't
 completely figured out).  I forced the save with w!, tested it by
 restarting gvim, and found that the settings did not take.  I wondered
 whether the file actually contained the above two lines that I added.

 It turns out that it depends on how the file is accessed.  If I access
 the file using notepad or windows-based gvim, the two added lines are
 not present (same thing if I use Windows's more from cmd.exe).  On
 the other hand, if I access the file using vim or less from cygwin's
 bash shell, the two added lines *are* present.  After googling about
 different versions of files on Windows 7, I found that one possible
 cause might be the backups that the OS makes.  However, I confirmed
 that this particular file has no backups.

 Right now, I am not sure whether this is a Windows 7 problem or a
 cygwin problem (or more likely, an interaction between them).  Can
 anyone suggest a next possible course of action?  I don't want to
 force both copies to be the same by simply editting the file using the
 Windows-base gvim.  This hides a problem that will doubtlessly come
 back and cause great grief.


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

Re: Windows 7: stat /cygdrive/D/nosuchfile yields garbage

[Larry Hall (Cygwin)]

On 5/18/2011 9:57 PM, Keith Thompson wrote:

I'm using Cygwin (version 1.7.9-1 of cygwin1.dll) on Windows 7
on a Dell laptop.  Cygwin is installed in C:\cygwin.

I should mention that I have a second Cygwin installation on
the same laptop; it's in C:\apps\cygwin, and has version 1.7.5-1
of cygwin1.dll.  I understand that having more than one Cygwin
installation on a Windows box is not supported, and if that's likely
to be the cause of this problem I won't complain.  But if anyone
else has seen similar behavior with a supported configuration,
it should probably be looked into further.


I cannot reproduce this with either 1.7.9 or 1.7.5 (different machines
though).  In my case, I cannot stat /cygdrive/d or anything under it
unless there is media in the drive.

$ stat /cygdrive/d
stat: cannot stat `/cygdrive/d': No such file or directory

--
Larry

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

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

Re: Windows 7: stat /cygdrive/D/nosuchfile yields garbage

[Keith Thompson]

Larry Hall wrote:
 On 5/18/2011 9:57 PM, Keith Thompson wrote:
  I'm using Cygwin (version 1.7.9-1 of cygwin1.dll) on Windows 7
  on a Dell laptop.  Cygwin is installed in C:\cygwin.
  
  I should mention that I have a second Cygwin installation on
  the same laptop; it's in C:\apps\cygwin, and has version 1.7.5-1
  of cygwin1.dll.  I understand that having more than one Cygwin
  installation on a Windows box is not supported, and if that's likely
  to be the cause of this problem I won't complain.  But if anyone
  else has seen similar behavior with a supported configuration,
  it should probably be looked into further.
 
 I cannot reproduce this with either 1.7.9 or 1.7.5 (different machines
 though).  In my case, I cannot stat /cygdrive/d or anything under it
 unless there is media in the drive.
 
 
 $ stat /cygdrive/d
 stat: cannot stat `/cygdrive/d': No such file or directory

The problem went away after a reboot.  Hooray Windows!

-- 
Keith Thompson (The_Other_Keith) k...@mib.org  http://www.ghoti.net/~kst
Nokia
We must do something.  This is something.  Therefore, we must do this.
-- Antony Jay and Jonathan Lynn, Yes Minister

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

Re: Windows 7 and file ownership

[Steve Thompson]

On Sat, 1 Jan 2011, Steve Thompson wrote:

On Win7, a DIR /Q on a mapped share similarly shows an owner of 
BUILTIN\Administrators, but a stat or a ls -ln in a cygwin bash shell 
always shows a uid of 544 and a gid of 545, _no matter who_ the logged-in 
user or the actual file ownership.


Ah, as always, I worked for two days on this and then found the solution
five minutes after posting. Using noacl in /etc/fstab was the answer.

-s

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

Re: Windows 7 Aero mode issue again (follow up)

[Eliot Moss]

A little more on the 20101026 snapshot on my Windows 7
64-bit setup ...

Previous versions would sometimes cause a repaint of
the entire screen, that even earlier versions did not
do.  (My user reaction was: That's a weird and
unnexessary screen repaint.)

These repaints would sometimes end by putting some
other, non-X, window on top, such as Adobe Acrobat.

The 20101026 snapshot, with it less aggressive use
of calls, seems to have eliminated those undesirable
behaviors, while also fixing the DWM issue I was
having.  So, thought you'd want to know; good job!

-- Eliot

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

Re: Windows 7 Aero mode issue again

[Jon TURNEY]

On 26/10/2010 23:58, Eliot Moss wrote:

Ok, here's a first email about *some* symptoms ...

If I run the latest installed XWin, or this one:
ftp://cygwin.com/pub/cygwinx/XWin.20101026-git-6105a1d4e1e137f0.exe.bz2

without -resize and then sleep and unsleep the
laptop, X does not paint anything but the cursor
and keyboard events do not seem to go to the
(invisible) windows. I have to kill the server
and all the X jobs. I will now proceed to the
other tests you suggested ...


Hmmm... I don't think you've mentioned this before.

I assume this is a regression from 1.8.0 (before -resize was added), as we 
used to survive a hibernate cycle?



You're probably right about earlier version being
sensitive to whether -resize was given. I had
forgotten about that dependency of behavior.


On 27/10/2010 00:15, Eliot Moss wrote:
 Ok ... the 20101026 snapshot works properly with -resize and
 -engine 1 set: DWM does not go away or get complained about
 if I sleep then unsleep. Yay!

Good.

Just to point out this isn't specific to the snapshot, though, -engine 1 
should workaround the problem in all cases.


I guess this confirms that it is a problem with our use of directdraw and a 
hibernate cycle. (as the workaround forces XWin to use the shadow GDI drawing 
engine rather than the shadow directdraw drawing engine)


However, I can't see what is wrong with XWin's use of ddraw.  We never try to 
draw directly to the primary surface (which is what causes DWM to be shut 
down), so why it thinks we are during a hibernate or resume is obscure.


It would probably be a good idea to test with some other ddraw application 
over a hibernate, to confirm this is a problem with XWin and not with the 
intel video drivers, but I'm not sure what other ddraw application is similar 
enough to make this a valid test (The simple tests in dxdiag probably wouldn't 
prove anything)


 I did notice one little thing: its log file seems to go to
 /var/log/XWin.0.log rather than /var/log/xwin/XWin.0.log.

I hadn't updated the script I use to build snapshots.  Thanks for pointing 
this out, I've now corrected that.


 I include the -logverbose 3 output for you, and the stderr.

Sorry, I was a little unclear.  If you are still interested in pursing this, a 
log without -engine 1 and with -logverbose 3 would be most helpful.  If you 
could annotate it to show at approximately what timestamp the suspend and 
resume occurred, that would be even better.


--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

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

Re: Windows 7 Aero mode issue again

[Jon TURNEY]

On 24/10/2010 00:00, Eliot Moss wrote:

Dear Jon -- The latest xorg and dlls, posted in the last
day, consistently cause my Window 7 64-bit laptop to drop
out of Aero mode if I put it in sleep mode and then wake
it up. Here are the .log file and the stderr output.


Sorry, I'm not quite sure what you are telling me here.

It is that you still have the same problem with 1.9.0-2 as with 1.8.2-1? 
(which is unfortunately unsurprising, as I haven't done anything to fix it)


--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

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

Re: Windows 7 Aero mode issue again

[Eliot Moss]

On 10/26/2010 9:09 AM, Jon TURNEY wrote:

On 24/10/2010 00:00, Eliot Moss wrote:

Dear Jon -- The latest xorg and dlls, posted in the last
day, consistently cause my Window 7 64-bit laptop to drop
out of Aero mode if I put it in sleep mode and then wake
it up. Here are the .log file and the stderr output.


Sorry, I'm not quite sure what you are telling me here.

It is that you still have the same problem with 1.9.0-2 as with 1.8.2-1? (which 
is unfortunately
unsurprising, as I haven't done anything to fix it)


Yes ... but it seems that the problem *had* gone away
for a while, with a version I directly downloaded
that you had pointed me to ...

Regards -- Eliot

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

Re: Windows 7 Aero mode issue again

[Jon TURNEY]

On 26/10/2010 14:55, Eliot Moss wrote:

On 10/26/2010 9:09 AM, Jon TURNEY wrote:

On 24/10/2010 00:00, Eliot Moss wrote:

Dear Jon -- The latest xorg and dlls, posted in the last
day, consistently cause my Window 7 64-bit laptop to drop
out of Aero mode if I put it in sleep mode and then wake
it up. Here are the .log file and the stderr output.


Sorry, I'm not quite sure what you are telling me here.

It is that you still have the same problem with 1.9.0-2 as with 1.8.2-1?
(which is unfortunately
unsurprising, as I haven't done anything to fix it)


Yes ... but it seems that the problem *had* gone away
for a while, with a version I directly downloaded
that you had pointed me to ...


Hmm, confused.

[1] seems to say that the 20100923-git-2172af4d1ea713f1 snapshot still has 
that issue, although your later emails suggest it goes away if you don't use 
-resize (which is expected)


You might like to try if adding '-engine 1' to the Xserver options works 
around the problem.


Anyhow, I've fixed a logic error which meant we were doing rather more stuff 
than we needed to for WM_DISPLAYCHANGE in windowed mode (and perhaps the intel 
driver is being a bit hypersensitive about that, causing it to shut down DWM), 
and added a bit more debug logging.  Could you try the snapshot at [2] with 
'-logverbose 3', please.



[1] http://cygwin.com/ml/cygwin-xfree/2010-09/msg00065.html
[2] ftp://cygwin.com/pub/cygwinx/XWin.20101026-git-6105a1d4e1e137f0.exe.bz2

--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

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

Re: Windows 7 Aero mode issue again

[Eliot Moss]

Ok, here's a first email about *some* symptoms ...

If I run the latest installed XWin, or this one:
ftp://cygwin.com/pub/cygwinx/XWin.20101026-git-6105a1d4e1e137f0.exe.bz2

without -resize and then sleep and unsleep the
laptop, X does not paint anything but the cursor
and keyboard events do not seem to go to the
(invisible) windows.  I have to kill the server
and all the X jobs.  I will now proceed to the
other tests you suggested ...

You're probably right about earlier version being
sensitive to whether -resize was given.  I had
forgotten about that dependency of behavior.

Regards -- Eliot Moss

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

Re: Windows 7 Aero mode issue again

[Eliot Moss]

Ok ... the 20101026 snapshot works properly with -resize and
-engine 1 set: DWM does not go away or get complained about
if I sleep then unsleep.  Yay!

I did notice one little thing: its log file seems to go to
/var/log/XWin.0.log rather than /var/log/xwin/XWin.0.log.

I include the -logverbose 3 output for you, and the stderr.

Regards, and thanks for continuing to work with me on this!

-- Eliot

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.9.0.0 (1090)
Snapshot: 20101026-git-6105a1d4e1e137f0

XWin was started with the following command line:

/usr/bin/X :0 -unixkill -clipboard -multimonitors -resize -engine 1
 -logverbose 3 -auth /home/Eliot/.serverauth.5448

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 1280 h 800
winInitializeDefaultScreens - native DPI x 96 y 96
[597661.030] OsVendorInit - Creating default screen 0
[597661.030] winInitializeScreens - 1
[597661.030] winInitializeScreen - 0
[597661.030] winValidateArgs - Returning.
[597661.030] (II) xorg.conf is not supported
[597661.030] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more 
information
[597661.030] LoadPreferences: /home/Eliot/.XWinrc not found
[597661.030] LoadPreferences: Loading /etc/X11/system.XWinrc
[597661.030] LoadPreferences: Done parsing the configuration file...
[597661.030] winGetDisplay: DISPLAY=:0.0
[597661.030] winDetectSupportedEngines - Windows NT/2000/XP
[597661.062] winDetectSupportedEngines - DirectDraw installed
[597661.062] winDetectSupportedEngines - Allowing PrimaryDD
[597661.062] winDetectSupportedEngines - DirectDraw4 installed
[597661.062] winDetectSupportedEngines - Returning, supported engines 001f
[597661.062] winScreenInit - dwWidth: 1280 dwHeight: 800
[597661.062] winSetEngine - Using user's preference: 1
[597661.062] winScreenInit - Using Windows display depth of 32 bits per pixel
[597661.062] winCreateBoundingWindowWindowed - User w: 1280 h: 800
[597661.062] winCreateBoundingWindowWindowed - Current w: 1280 h: 800
[597661.062] winGetWorkArea - Original WorkArea: 0 0 770 1280
[597661.062] winGetWorkArea - Virtual screen is 1280 x 800
[597661.062] winGetWorkArea - Virtual screen origin is 0, 0
[597661.062] winGetWorkArea - Primary screen is 1280 x 800
[597661.062] winGetWorkArea - Adjusted WorkArea for multiple monitors: 0 0 770 
1280
[597661.062] winAdjustForAutoHide - Original WorkArea: 0 0 770 1280
[597661.062] winAdjustForAutoHide - Adjusted WorkArea: 0 0 770 1280
[597661.062] winCreateBoundingWindowWindowed - WindowClient w 1264 h 732 r 1264 
l 0 b 732 t 0
[597661.062] winWindowProc - WM_ACTIVATEAPP
[597661.077] winWindowProc - WM_SIZE - new client area w: 1264 h: 732
[597661.077] winCreateBoundingWindowWindowed -  Returning
[597661.077] winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 800 
depth: 32
[597661.077] winAllocateFBShadowGDI - Dibsection width: 1280 height: 800 depth: 
32 size image: 4096000
[597661.077] winAllocateFBShadowGDI - Created shadow stride: 1280
[597661.077] winFinishScreenInitFB - Masks: 00ff ff00 00ff
[597661.077] winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 
d 24 bpp 32
[597661.077] winRandRInit ()
[597661.077] winCreateDefColormap - Deferring to fbCreateDefColormap ()
[597661.077] winFinishScreenInitFB - returning
[597661.077] Screen 0 added at virtual desktop coordinate (0,0).
[597661.077] winScreenInit - returning
[597661.077] winGenerateAuthorization - GenerateAuthorization success!
AuthDataLen: 16 AuthData: ¥ºFÕ%FU®Û#ññ
[597661.077] InitOutput - Returning.
[597661.077] MIT-SHM extension disabled due to lack of kernel support
[597661.093] XFree86-Bigfont extension local-client optimization disabled due to lack of shared 
memory support in the kernel

[597661.155] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so
[597661.155] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[597661.171] [dix] Could not init font path element /usr/share/fonts/OTF/, 
removing from list!
[597661.686] winPointerWarpCursor - Discarding first warp: 640 400
[597661.686] winSendKeyEvent: dwKey: 69, fDown: 1, nEvents 0
[597661.686] winSendKeyEvent: dwKey: 69, fDown: 0, nEvents 0
[597661.686] (--) 8 mouse buttons found
[597661.686] (--) Setting autorepeat to delay=500, rate=31
[597661.686] (--) Windows keyboard layout: 0409 (0409) US, type 4
[597661.686] (--) Found matching XKB configuration English (USA)
[597661.686] (--) Model = pc105 Layout = us Variant = none Options = 
none
[597661.686] Rules = base Model = pc105 Layout = us Variant = none Options = 
none
[597661.686] winBlockHandler - Releasing pmServerStarted
[597661.686] winBlockHandler - pthread_mutex_unlock () returned
[597661.701] winProcEstablishConnection - Hello
[597661.966] winInitClipboard ()
[597661.966] winClipboardProc - Hello
[597661.966] DetectUnicodeSupport - Windows NT/2000/XP
[597661.966] winProcEstablishConnection - winInitClipboard returned.

Re: Windows 7 file permissions and ls -l

[Vorfeed Canal]

I see this problem too. I believe something wrong is with cygwin1.dll.
I'm not sure about your case, but in my case these are all files
created by regular Windows (non-cygwin) programs. The owner does not
get any special rights in my version of Windows 7! Instead the
pseudo-group Authenticated User gets all the rights.

Very annoying: if the cygwin program just tries to do the operation it
succeeds, but if the program calls stat and checks the permissions it
believes it has no rights at all and refuses to work.

Easy to fix from outside of cygwin (without admin rights), but I've
found no way to do this from inside of cygwin if you have no
administrator access :-(

On Fri, May 14, 2010 at 4:43 PM, Greg Mo gregm...@hotmail.com wrote:
 I have an odd occurrence on my Win 7 x64 system with Cygwin 1.7.5.

 When I create files, I may set the permissions to 644 or 755.  However, after
 a period of time, I went to edit one of those files in vi and it said that the
 file is read-only.  I did an ls -l and was shocked to find that many of the
 directories have been changed to d- and files to --, which I
 did not do.  The only way that I can change those permissions is to open an
 rxvt/bash window in administrator mode and then chmod, even though I am listed
 as the owner.

 I don't see a pattern to which files get changed and which are left alone.

 Is anyone else having this windoze automagic permission change scenario and
 does anyone know what to do to stop it?


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

Re: Windows 7

[Brian Wilson]

I stand (actually I'm sitting) corrected. :)

The reason I deleted the .sh script was because it would never run to 
completion on subsequent installs.  I also forgot to add that I went though 
and selected reinstall for all my packages to avoid the problem you pointed 
out.  It took a while, but everything is working for me. 

Sincerely,

Brian S. Wilson
===
Home: (678) 376-9258   Cell: (678) 232-9357 wil...@ds.net
===

-- Original Message ---
From: Larry Hall (Cygwin) reply-to-list-only...@cygwin.com
To: cygwin@cygwin.com
Sent: Sun, 31 Jan 2010 20:13:03 -0500
Subject: Re: Windows 7

 On 01/29/2010 08:45 PM, Brian Wilson wrote:
  I had a similar problem upgrading on XP.  I think my issue was related to 
a
  heap space allocation issue which prevents the shell from running during 
the
  installation.  I found that failed installations left shell processes 
running,
  but not doing anything useful.
 
  Check the documentation as I believe there is a fix for the heap space 
issue.
  In my case, I killed these useless shells and that allowed the Cygwin bash
  shell to start up with out heap space errors.  I cleaned out the
  /etc/postinstall directory by removing any shell scripts (rm *.sh) and
  rerunning the setup.  Cygwin installed okay for me after that.
 
 There's no reason to remove postinstall scripts and, in fact, very 
 good reason to not do so - your installation could be incomplete.  
 If things are working for you and you have no complaints, there's no 
 reason to revisit this issue but in case others reading this thread 
 thought this would be a good thing to try, I wanted something on 
 record that would recommend against it.
 
 -- 
 Larry Hall  http://www.rfk.com
 RFK Partners, Inc.  (508) 893-9779 - RFK Office
 216 Dalton Rd.  (508) 893-9889 - FAX
 Holliston, MA 01746
 
 _
 
 A: Yes.
   Q: Are you sure?
   A: Because it reverses the logical flow of conversation.
   Q: Why is top posting annoying in email?
 
 --
 Problem reports:   http://cygwin.com/problems.html
 FAQ:   http://cygwin.com/faq/
 Documentation: http://cygwin.com/docs.html
 Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
--- End of Original Message ---

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

Re: Windows 7

[Larry Hall (Cygwin)]

On 01/29/2010 08:45 PM, Brian Wilson wrote:

I had a similar problem upgrading on XP.  I think my issue was related to a
heap space allocation issue which prevents the shell from running during the
installation.  I found that failed installations left shell processes running,
but not doing anything useful.

Check the documentation as I believe there is a fix for the heap space issue.
In my case, I killed these useless shells and that allowed the Cygwin bash
shell to start up with out heap space errors.  I cleaned out the
/etc/postinstall directory by removing any shell scripts (rm *.sh) and
rerunning the setup.  Cygwin installed okay for me after that.


There's no reason to remove postinstall scripts and, in fact, very good reason
to not do so - your installation could be incomplete.  If things are working for
you and you have no complaints, there's no reason to revisit this issue but in
case others reading this thread thought this would be a good thing to try, I
wanted something on record that would recommend against it.

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

_

A: Yes.
 Q: Are you sure?
 A: Because it reverses the logical flow of conversation.
 Q: Why is top posting annoying in email?

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

Re: Windows 7

[Brian Wilson]

I had a similar problem upgrading on XP.  I think my issue was related to a 
heap space allocation issue which prevents the shell from running during the 
installation.  I found that failed installations left shell processes running, 
but not doing anything useful.  

Check the documentation as I believe there is a fix for the heap space issue.  
In my case, I killed these useless shells and that allowed the Cygwin bash 
shell to start up with out heap space errors.  I cleaned out the 
/etc/postinstall directory by removing any shell scripts (rm *.sh) and 
rerunning the setup.  Cygwin installed okay for me after that.

Hope this helps.

Sincerely,

Brian S. Wilson
-- Original Message ---
From: Gregg Levine gregg.drw...@gmail.com
To: cygwin@cygwin.com
Sent: Thu, 28 Jan 2010 12:50:53 -0500
Subject: Re: Windows 7

 On Thu, Jan 28, 2010 at 12:49 PM, Dave Korn 
 dave.korn.cyg...@ wrote:
  On 28/01/2010 06:28, Hirokazu Miura wrote:
  I am having problems in installing cygwin on a HP Pavilion 64bits 
platform.
 
   HP tend to ship their boxes with a ton of irritating and semi-useless 
stuff
  preinstalled.  Check if anything you have on the box is listed on BLODA:
 
  http://cygwin.com/faq/faq.using.html#faq.using.bloda
 
     cheers,
       DaveK
 
 Hello!
 I agree!
 This Dell Inspirion 1545 arrived wearing a heck of a lot of useless
 items, including their chosen Anti-virus programs.
 
 I strongly suggest you go through that list of items on the FAQ, and
 see if anything on your system matches it.
 
 Following it, then simply choose the steps that work for you. The one
 Eliot suggests in fact is how I normally proceed in point of fact.
 
 -
 Gregg C Levine gregg.drw...@gmail.com
 This signature was once found posting rude messages in English in 
 the Moscow subway.
 
 --
 Problem reports:   http://cygwin.com/problems.html
 FAQ:   http://cygwin.com/faq/
 Documentation: http://cygwin.com/docs.html
 Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
--- End of Original Message ---


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

Re: Windows 7

[Rance Hall]

On Thu, Jan 28, 2010 at 12:28 AM, Hirokazu Miura
hiromi...@sbcglobal.net wrote:
 I am having problems in installing cygwin on a HP Pavilion 64bits platform.
 Every attempt to install cygwin gets stuck before completion, every time
 at random location.  I have installed cygwin on various windows XP
 platforms at my work and cygwin is one of the most important system for me.

 I have access to internet through ATT DSL service at home.

 Do you think my problem is due to Windows 7 or DSL connection to the
 mirror site ?

 Do you know if anyone sells a CD/DVD from which I could install cygwin
 directly ?

 Hiro Miura



I have cygwin installed on a 64bit windows 7 hp pavilion and its
running just fine.  Ive run the installer several times (to catch
updates, etc) never a problem.

So I don't think thats your problem.


As to your comment about a DVD, not very likely since the setup.exe is
a windows tool and the rest changes fast enough that a printed DVD
would be obsolete before being shipped.


However, you can become a local mirror of cygwin and then tell your
copy of setup to install from a local path rather than an internet
path.

Several people (not me) use this method because they have several
installs of cygwin to update and they are trying to be good
netizens.

HTH

Rance

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

Re: Windows 7

[Eliot Moss]

It also occurs to me that you could try doing the
install in the two alternatives step that setup
offers (if you have not already tried this):

1) download only; then
2) install from the downloaded files

I do this all the time, in case a network
connection drops or whatever. Of course you
may have already tried it ...

Best wishes -- Eliot Moss

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

Re: Windows 7

[Dave Korn]

On 28/01/2010 06:28, Hirokazu Miura wrote:
 I am having problems in installing cygwin on a HP Pavilion 64bits platform.

  HP tend to ship their boxes with a ton of irritating and semi-useless stuff
preinstalled.  Check if anything you have on the box is listed on BLODA:

http://cygwin.com/faq/faq.using.html#faq.using.bloda

cheers,
  DaveK

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

Re: Windows 7

[Gregg Levine]

On Thu, Jan 28, 2010 at 12:49 PM, Dave Korn dave.korn.cyg...@ wrote:
 On 28/01/2010 06:28, Hirokazu Miura wrote:
 I am having problems in installing cygwin on a HP Pavilion 64bits platform.

  HP tend to ship their boxes with a ton of irritating and semi-useless stuff
 preinstalled.  Check if anything you have on the box is listed on BLODA:

 http://cygwin.com/faq/faq.using.html#faq.using.bloda

    cheers,
      DaveK

Hello!
I agree!
This Dell Inspirion 1545 arrived wearing a heck of a lot of useless
items, including their chosen Anti-virus programs.

I strongly suggest you go through that list of items on the FAQ, and
see if anything on your system matches it.

Following it, then simply choose the steps that work for you. The one
Eliot suggests in fact is how I normally proceed in point of fact.

-
Gregg C Levine gregg.drw...@gmail.com
This signature was once found posting rude messages in English in the
Moscow subway.

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

RE: Windows 7 Pro - rxvt launch errors

[Jim Garrison]

I moved aside c:\cygwin and reinstalled from scratch.  The problem seems to 
have cured itself, but I did nothing different on the second install.  Oh 
well...

-Original Message-
From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of Jim 
Garrison
Sent: Monday, January 18, 2010 4:22 PM
To: cygwin@cygwin.com
Subject: Windows 7 Pro - rxvt launch errors

Installed Cygwin on Friday 1/15/2010 on a brand-new Windows 7 Pro system (Core 
I7 940, 4 cores, 12GB memory).  When launching rxvt (native) I'm getting errors 
like 

  0 [main] bash 3920 child_copy: linked dll data write copy failed, 
0x3BD000..0x3C14A4, done 0, windows pid 6348, Win32 error 487
3903794 [main] bash 3920 child_copy: linked dll data write copy failed, 
0x3BD000..0x3C14A4, done 0, windows pid 6348, Win32 error 487 11677290 [main] 
bash 3920 fork: child -1 - died waiting for longjmp before initialization, 
retry 0, exit code 0xC005, errno 11
18309793 [main] bash 3920 child_copy: linked dll data write copy failed, 
0x3BD000..0x3C14A4, done 0, windows pid 6348, Win32 error 487
27757938 [main] bash 5560 fork: child -1 - died waiting for longjmp before 
initialization, retry 0, exit code 0xC005, errno 11
33009668 [main] bash 5560 fork: child -1 - died waiting for longjmp before 
initialization, retry 0, exit code 0xC005, errno 11
39143098 [main] bash 5560 fork: child -1 - died waiting for longjmp before 
initialization, retry 0, exit code 0xC005, errno 11
47331605 [main] bash 5560 fork: child -1 - died waiting for longjmp before 
initialization, retry 0, exit code 0xC005, errno 11

There are a bunch of these, but eventually it gets to a command prompt.  The 
next time I start an rxvt I'll only see one or two errors before it gets to a 
command prompt.  I did a rebaseall as recommended in the readme, without any 
effect (actually, it increases the number of errors seen the next time an rxvt 
is launched).

Here's the command line I'm using:

C:\cygwin\bin\rxvt.exe -display :0 -fn Lucida Console-14 -tn 
rxvt-cygwin-native -ls -sr -sl 1 -e /bin/bash --login

1) When run manually from a CMD.EXE command prompt no errors occur, but it 
takes anywhere from 3 to 10 seconds from the time the rxvt window appears to 
when the command prompt is ready.  

2) When the exact same command is run from a Windows shortcut, I get one or two 
dll data write copy failed errors, which display in the rxvt window.

3) When run in XP SP3 Compatibility mode (from the shortcut) it never gets to 
the command prompt and no errors are displayed.  The window cannot be closed 
and the process must be killed from TaskManager or ProcessExplorer.

4) Removing the -display and -tn options (which I didn't use on XP SP3) have no 
effect

5) Behavior is generally different from invocation to invocation; usually it's 
just the number of errors, but in some cases I get the following error in the 
CMD window

  0 [main] rxvt 7104 C:\cygwin\bin\rxvt.exe: *** fatal error - unable to 
remap C:\cygwin\bin\libW11.DLL to same address as parent: 0x4B != 0x5D

At which point the rxvt window freezes and the process must be killed.

Other errors I've seen

  1 [main] bash 6240 C:\cygwin\bin\bash.exe: *** fatal error - couldn't 
allocate heap, Win32 error 487, base 0xCA, top 0xCF, reserve_size 
323584, allocsize 327680, page_const 4096


Cygcheck.out is attached -- Suggestions?




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

Re: Windows 7 RC1 and Cygwin 1.7

[Jon TURNEY]

4) In multiwindow, if two programs overlap, then Aero Peek will show 
the correct shape for each window but the contents of one window 
superimposed on the other in their stacking order.


Yes, I've seen the same behaviour with the TaskSwitchXP alt+tab 
replacement.
This is a consequence of the way multiwindow mode is currently 
implemented: everything is drawn onto a shadow framebuffer, and then 
areas from that are drawn into native windows when they are exposed.  
This means that we can only correctly draw the contents of the X window 
at the top of the Z-order stack (as this may be occluding other X 
windows).  There are probably solutions to this.


Forgive me for being rather too terse, but I am not sure what those solutions 
might be.  I think those solutions involve using the rootless extension 
(perhaps) or composite (definitely) to gain access to the bitmap for each 
window independently.



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

Re: Windows 7 RC1 and Cygwin 1.7

[Jon TURNEY]

Yaakov (Cygwin/X) wrote:

On 15/05/2009 15:13, Jim Reisert AD1C wrote:

I have installed Windows 7 RC1 (64-bit) as well as Cygwin 1.7,
including the Xorg stuff in the Cygwin setup-1.7.exe file


Same here.  I have also noticed the following issues:

1) In multiwindow mode, all X programs are considered as one wrt taskbar 
buttons.  Nothing really new there, but it's more noticeable now that 
the default is Always combine, hide labels.  When combined, the icon 
shown is that of the first program launched, which is obviously 
inaccurate if several different X programs are running.


If a windowed X server is launched, it shows as one window with the X 
icon (as expected), which will be grouped together with X programs 
running multiwindow on a different DISPLAY.  Pinning that X icon to the 
taskbar has the same effect.


It would be preferable to force ungrouping (or grouping by program in 
multiwindow, if possible), but if that's not possible, the X icon should 
represent the group no matter which program launched first.


It doesn't seem to be clearly documented how the taskbar makes these 
decisions: if it's based on the executable, the window class or name or some 
hints associated with it.  It would be neat if we could set things up so that 
the X windows group in the same way as native windows, but I'm not aware of a 
way to do that...


The shell interface ITaskbarList() seems completely inadequate for this purpose.


2) It would be nice to port the tray icon menu to the new Jump List.

3) With Aero in multiwindow, fbpanel (in Ports) has a large border 
around the panel.  IIRC there was a slight border in XP, but it's much 
larger and more noticeable with Aero.


4) In multiwindow, if two programs overlap, then Aero Peek will show the 
correct shape for each window but the contents of one window 
superimposed on the other in their stacking order.


Yes, I've seen the same behaviour with the TaskSwitchXP alt+tab replacement.
This is a consequence of the way multiwindow mode is currently implemented: 
everything is drawn onto a shadow framebuffer, and then areas from that are 
drawn into native windows when they are exposed.  This means that we can only 
correctly draw the contents of the X window at the top of the Z-order stack 
(as this may be occluding other X windows).  There are probably solutions to this.



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

Re: Windows 7 RC1 and Cygwin 1.7

[Yaakov (Cygwin/X)]

On 15/05/2009 15:13, Jim Reisert AD1C wrote:

I have installed Windows 7 RC1 (64-bit) as well as Cygwin 1.7,
including the Xorg stuff in the Cygwin setup-1.7.exe file


Same here.  I have also noticed the following issues:

1) In multiwindow mode, all X programs are considered as one wrt taskbar 
buttons.  Nothing really new there, but it's more noticeable now that 
the default is Always combine, hide labels.  When combined, the icon 
shown is that of the first program launched, which is obviously 
inaccurate if several different X programs are running.


If a windowed X server is launched, it shows as one window with the X 
icon (as expected), which will be grouped together with X programs 
running multiwindow on a different DISPLAY.  Pinning that X icon to the 
taskbar has the same effect.


It would be preferable to force ungrouping (or grouping by program in 
multiwindow, if possible), but if that's not possible, the X icon should 
represent the group no matter which program launched first.


2) It would be nice to port the tray icon menu to the new Jump List.

3) With Aero in multiwindow, fbpanel (in Ports) has a large border 
around the panel.  IIRC there was a slight border in XP, but it's much 
larger and more noticeable with Aero.


4) In multiwindow, if two programs overlap, then Aero Peek will show the 
correct shape for each window but the contents of one window 
superimposed on the other in their stacking order.


Anyone else testing 7RC1?


Yaakov
Cygwin/X

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

Re: Windows 7 RC1 and Cygwin 1.7

[Corinna Vinschen]

Hi Ben,

sorry for the late response.  That's what vacation does to you :}

On May 19 21:04, richardvo...@gmail.com wrote:
 On Sat, May 16, 2009 at 4:41 AM, Corinna Vinschen
  As for the console windows popping up, thats a generic bug in the new
  console code in W7, affecting 32 and 64 bit versions.  For some reason
  the AllocConsole call does not honor the fact that the application
  switched to another active WindowStation.  Thus, console windows which
  are meant to be hidden in another, hidden WindowStation, are wrongly
  created on the desktop of the original, visible WindowStation.
 
  I reported this bug upstream as well, but unfortunately I got the reply
  that this bug won't be fixed in this Windows release.  I'm still trying
  to convince Microsoft that this is a serious problem, though.
 
 Corinna,
 
 Do you have a link to a bug report on Connect?  I'll upvote it.

https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=443006SiteID=647

I don't know if upvoting will help, but it's worth a try, I guess.

 And should I download the latest release in order to validate this, or
 are there testing builds?  I haven't installed Cygwin on my 64-bit
 Win7RC box yet but I need to, can't use any computer long without an
 ssh client.

The problem is independent of any Cygwin release and actually independent
of Cygwin at all.  The above Connect issue even contains a bare Win32
testcase in source code.

 Are there any other bugs you'd like validated and upvoted?  I'm not

Well, there's this issue:
https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=445558SiteID=647
The reply I got indicates that it's not yet clear if it will get a fix,
though it's easy to reproduce.  I don't think it's *very* critical, but
I don't like the idea that a process tree can lose handles when the
close-on-exec flag is set for console file descriptors.

My other open issues are:

https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=447597SiteID=647
Marked as resolved but I can still reproduce in the latest build.

https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=447443SiteID=647
Has been fixed but introduces a new bug which I'm going to report today
or tomorrow.  A file not found on an NFS share now reports the wrong
error code STATUS_OBJECT_PATH_NOT_FOUND instead of STATUS_NO_SUCH_FILE
in the latest build.  That's bad for Cygwin.  But I still have to verify
on a 32 bit system before I file the issue.

https://connect.microsoft.com/feedback/ViewFeedback.aspx?FeedbackID=442994SiteID=647
is still heavily worked on.

 exactly sure how to reproduce that issue you found with the cost to
 access directories on NTFS increasing exponentially with nesting
 level well repro might not be hard but pinpointing MS-provided

This is an old issue I reported as one of my MSDN cases.  Given that it
only occurs on NT kernels of the 5.x series and has been fixed in the
6.0 kernel, there won't be a fix for that.  I already pulled it through
all instances.

 After all, what's MVP status good for if not telling 'em they broke
 valuable cygwin stuff.

Right :)


Thanks,
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://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

Re: Windows 7 RC1 and Cygwin 1.7

[Ravenik]

Corinna Vinschen-2 wrote:
 
 As for the console windows popping up, thats a generic bug in the new
 console code in W7, affecting 32 and 64 bit versions.  For some reason
 the AllocConsole call does not honor the fact that the application
 switched to another active WindowStation.  Thus, console windows which
 are meant to be hidden in another, hidden WindowStation, are wrongly
 created on the desktop of the original, visible WindowStation.
 
 I reported this bug upstream as well, but unfortunately I got the reply
 that this bug won't be fixed in this Windows release.  I'm still trying
 to convince Microsoft that this is a serious problem, though.
 

If there is any possibility for us to support this request to Microsoft,
then let us now. I  use Cygwin  1.5.25-15 and have the same problem with
the console windows popping up in W7 RC. Really annoying. Hope they will
correct it before final release. I look forward to hearing about this
problem solved or a workaround. Meanwhile I consider reverting to Vista
which doesn't have this bug.
-- 
View this message in context: 
http://www.nabble.com/Windows-7-RC1-and-Cygwin-1.7-tp23566592p23765787.html
Sent from the cygwin-xfree mailing list archive at Nabble.com.


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

Re: Windows 7 RC1 and Cygwin 1.7

[Ravenik]

I have found this option to send feedback to MS from W7 RC x64:
C:\Windows\System32\rundll32.exe FeedbackTool.dll,ShowWizard
Maybe we should us it to send info about a bug, however I am not sure if
they care, and don't know what sort of fedback on to choose. 
-- 
View this message in context: 
http://www.nabble.com/Windows-7-RC1-and-Cygwin-1.7-tp23566592p23771256.html
Sent from the cygwin-xfree mailing list archive at Nabble.com.


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

Re: Windows 7 RC1 and Cygwin 1.7

[Jim Reisert AD1C]

The two empty DOS windows are conhost.exe sessions, according to Task Manager.

- Jim

On Fri, May 15, 2009 at 2:13 PM, Jim Reisert AD1C
jjreis...@alum.mit.edu wrote:

 I have installed Windows 7 RC1 (64-bit) as well as Cygwin 1.7,
 including the Xorg stuff in the Cygwin setup-1.7.exe file

 I can start the X server OK, as well as xterm and xemacs.

 When I start an xterm by right-clicking on the X server icon in the
 system tray, in addition to the Xterm windows, I also get what appears
 to be two empty DOS windows - one with xwin.exe in the window title,
 one with xterm.exe in the window title.  When I close the xterm, those
 two DOS windows also disappear.

 Can anyone speculate why this is happening?

 The system is running a clean install of all this new stuff.

-- 
Jim Reisert AD1C/Ø, jjreis...@alum.mit.edu, http://www.ad1c.us

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

Re: Windows 7 RC1 and Cygwin 1.7

[richardvo...@gmail.com]

On Sat, May 16, 2009 at 4:41 AM, Corinna Vinschen
corinna-cyg...@cygwin.com wrote:
 On May 15 23:18, Christopher Faylor wrote:
 On Fri, May 15, 2009 at 01:22:23PM -0700, Mike Ayers wrote:
 P.S.  That was speculation.  Hopefully someone will have a real answer
 soon.

 This was already discussed in the main cygwin list.  There is a
 workaround in the latest version of Cygwin 1.7.x.

 http://cygwin.com/ml/cygwin/2009-05/msg00477.html

 That's not a workaround for the problem with consoles popping up, but a
 workaround for a W7 x64 specific problem.  There's a bug in the W7 x64
 console code (which appears to be mostly rewritten in W7 anyway) which
 breaks DLL initialization in child processes which have no copy of the
 original console handles from console startup anymore.  This bug has been
 reported upstream and is marked as being resolved, which hopefully
 means it will be fixed in the final W7 release.

 As for the console windows popping up, thats a generic bug in the new
 console code in W7, affecting 32 and 64 bit versions.  For some reason
 the AllocConsole call does not honor the fact that the application
 switched to another active WindowStation.  Thus, console windows which
 are meant to be hidden in another, hidden WindowStation, are wrongly
 created on the desktop of the original, visible WindowStation.

 I reported this bug upstream as well, but unfortunately I got the reply
 that this bug won't be fixed in this Windows release.  I'm still trying
 to convince Microsoft that this is a serious problem, though.

Corinna,

Do you have a link to a bug report on Connect?  I'll upvote it.

And should I download the latest release in order to validate this, or
are there testing builds?  I haven't installed Cygwin on my 64-bit
Win7RC box yet but I need to, can't use any computer long without an
ssh client.

Are there any other bugs you'd like validated and upvoted?  I'm not
exactly sure how to reproduce that issue you found with the cost to
access directories on NTFS increasing exponentially with nesting
level well repro might not be hard but pinpointing MS-provided
code as the problem vs antivirus or just about anything else might not
be the easiest thing.  This new AllocConsole window station thing
seems a lot more straightforward.

After all, what's MVP status good for if not telling 'em they broke
valuable cygwin stuff.

Ben Voigt
(http://mvp.support.microsoft.com/profile/Voigt)

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

Re: Windows 7 RC1 and Cygwin 1.7

[Corinna Vinschen]

On May 15 23:18, Christopher Faylor wrote:
 On Fri, May 15, 2009 at 01:22:23PM -0700, Mike Ayers wrote:
 P.S.  That was speculation.  Hopefully someone will have a real answer
 soon.
 
 This was already discussed in the main cygwin list.  There is a
 workaround in the latest version of Cygwin 1.7.x.
 
 http://cygwin.com/ml/cygwin/2009-05/msg00477.html

That's not a workaround for the problem with consoles popping up, but a
workaround for a W7 x64 specific problem.  There's a bug in the W7 x64
console code (which appears to be mostly rewritten in W7 anyway) which
breaks DLL initialization in child processes which have no copy of the
original console handles from console startup anymore.  This bug has been
reported upstream and is marked as being resolved, which hopefully
means it will be fixed in the final W7 release.

As for the console windows popping up, thats a generic bug in the new
console code in W7, affecting 32 and 64 bit versions.  For some reason
the AllocConsole call does not honor the fact that the application
switched to another active WindowStation.  Thus, console windows which
are meant to be hidden in another, hidden WindowStation, are wrongly
created on the desktop of the original, visible WindowStation.

I reported this bug upstream as well, but unfortunately I got the reply
that this bug won't be fixed in this Windows release.  I'm still trying
to convince Microsoft that this is a serious problem, though.


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://x.cygwin.com/docs/
FAQ:   http://x.cygwin.com/docs/faq/

RE: Windows 7 RC1 and Cygwin 1.7

[Mike Ayers]

 From: cygwin-xfree-ow...@cygwin.com 
 [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Jim Reisert AD1C
 Sent: Friday, May 15, 2009 1:13 PM

 I have installed Windows 7 RC1 (64-bit) as well as Cygwin 1.7,
 including the Xorg stuff in the Cygwin setup-1.7.exe file
 
 I can start the X server OK, as well as xterm and xemacs.
 
 When I start an xterm by right-clicking on the X server icon in the
 system tray, in addition to the Xterm windows, I also get what appears
 to be two empty DOS windows - one with xwin.exe in the window title,
 one with xterm.exe in the window title.  When I close the xterm, those
 two DOS windows also disappear.
 
 Can anyone speculate why this is happening?

Speculate?  Heck, yeah!

1)  Microsoft has decided it doesn't like Cygwin.  Those terminal 
windows are waiting for you to walk away so they can eat the xterms.

2)  Space aliens are messing with you.  They want to know if you have a 
juicy brain before they decide whether to eat it.

3)  Housing prices will continue to rise at 20% per annum.

Huh?!  You want *sane* speculation?  Are you sure that's not an 
oxymoron?  How about:

1)  The interface for detaching a program from its console window has 
changed slightly in Windows 7.  A slight code change will be needed.  In the 
meantime the console windows are harmless - setting the shortcut to run 
minimized should keep them off the screen if still in the program bar.


HTH,

Mike

P.S.  That was speculation.  Hopefully someone will have a real answer soon.

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

Re: Windows 7 RC1 and Cygwin 1.7

[Christopher Faylor]

On Fri, May 15, 2009 at 01:22:23PM -0700, Mike Ayers wrote:
P.S.  That was speculation.  Hopefully someone will have a real answer
soon.

This was already discussed in the main cygwin list.  There is a
workaround in the latest version of Cygwin 1.7.x.

http://cygwin.com/ml/cygwin/2009-05/msg00477.html

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