Re: 1.7 installation failed (on network drive?)
On Dec 21 21:10, Thomas Wolff wrote: [resending without attachments which got spam-blocked] Corinna Vinschen schrieb: On Dec 18 16:08, Thomas Wolff wrote: Corinna Vinschen schrieb: On Dec 18 11:57, Corinna Vinschen wrote: On Dec 17 17:31, Corinna Vinschen wrote: I applied a patch which falls back to opening/creating the file/dir without WRITE_DAC if the first call failed. That's not quite optimal but it works. Please check out the latest from CVS and test in your scenario. For me it works now on the share as well as on local drives. The downside is that it will not create any POSIX-like permissions on the share. I'm just creating another solution which allows to give normal POSIX permissions to the files, just like on a local drive. I applied tha patch to CVS. The NtCreateFile call now gets the POSIX-like ACL to create the file immediately with the correct permissions. Please give it a try. I can do that on Monday, hope it's sufficient. Both setup.exe versions of Friday work! Great, thanks. And with both network drives. There were a number of Permission denied messages in some of the screen logs, mostly during postinstall of terminfo. Probably the fruitless attempts to chmod something. That's the result of the unfortunate Change permissions on the share. Another result is that Cygwin applications running under a non-admin account will not be able to create files with arbitrary POSIX permissions at all, since Cygwin sets permissions differently than setup.exe to allow inheritable permissions. And there was a failed attempt to create H:\/setup.log in one of them (last instance of \/ or \\ after transformation). I see why that happens. I'll fix it. Thanks for testing, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
[resending without attachments which got spam-blocked] Corinna Vinschen schrieb: On Dec 18 16:08, Thomas Wolff wrote: Corinna Vinschen schrieb: On Dec 18 11:57, Corinna Vinschen wrote: On Dec 17 17:31, Corinna Vinschen wrote: I applied a patch which falls back to opening/creating the file/dir without WRITE_DAC if the first call failed. That's not quite optimal but it works. Please check out the latest from CVS and test in your scenario. For me it works now on the share as well as on local drives. The downside is that it will not create any POSIX-like permissions on the share. I'm just creating another solution which allows to give normal POSIX permissions to the files, just like on a local drive. I applied tha patch to CVS. The NtCreateFile call now gets the POSIX-like ACL to create the file immediately with the correct permissions. Please give it a try. I can do that on Monday, hope it's sufficient. Both setup.exe versions of Friday work! Great, thanks. And with both network drives. There were a number of Permission denied messages in some of the screen logs, mostly during postinstall of terminfo. And there was a failed attempt to create H:\/setup.log in one of them (last instance of \/ or \\ after transformation). If it's interesting, I can provide additional information about security properties of the affected drives and dirs. Kind regards, Thomas
Re: 1.7 installation failed (on network drive?)
On Dec 17 17:31, Corinna Vinschen wrote: I applied a patch which falls back to opening/creating the file/dir without WRITE_DAC if the first call failed. That's not quite optimal but it works. Please check out the latest from CVS and test in your scenario. For me it works now on the share as well as on local drives. The downside is that it will not create any POSIX-like permissions on the share. I'm just creating another solution which allows to give normal POSIX permissions to the files, just like on a local drive. Be aware that this share is really a problem. The permissions given on it are not common. You can create a file with the desired permissions, but you will never be able to change the permissions afterwards. THis is a flaw in the sharing permission handling if the user has only Change permissions but not Full Control. Your admin should change that and rather fix the permissions in the share's ACL. Even Microsoft recommends that. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
On Dec 18 11:57, Corinna Vinschen wrote: On Dec 17 17:31, Corinna Vinschen wrote: I applied a patch which falls back to opening/creating the file/dir without WRITE_DAC if the first call failed. That's not quite optimal but it works. Please check out the latest from CVS and test in your scenario. For me it works now on the share as well as on local drives. The downside is that it will not create any POSIX-like permissions on the share. I'm just creating another solution which allows to give normal POSIX permissions to the files, just like on a local drive. I applied tha patch to CVS. The NtCreateFile call now gets the POSIX-like ACL to create the file immediately with the correct permissions. Please give it a try. Be aware that this share is really a problem. The permissions given on it are not common. You can create a file with the desired permissions, but you will never be able to change the permissions afterwards. THis is a flaw in the sharing permission handling if the user has only Change permissions but not Full Control. Your admin should change that and rather fix the permissions in the share's ACL. Even Microsoft recommends that. This problem persists, of course. Only your admin can change it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
Corinna Vinschen schrieb: On Dec 18 11:57, Corinna Vinschen wrote: On Dec 17 17:31, Corinna Vinschen wrote: I applied a patch which falls back to opening/creating the file/dir without WRITE_DAC if the first call failed. That's not quite optimal but it works. Please check out the latest from CVS and test in your scenario. For me it works now on the share as well as on local drives. The downside is that it will not create any POSIX-like permissions on the share. I'm just creating another solution which allows to give normal POSIX permissions to the files, just like on a local drive. I applied tha patch to CVS. The NtCreateFile call now gets the POSIX-like ACL to create the file immediately with the correct permissions. Please give it a try. I can do that on Monday, hope it's sufficient. Be aware that this share is really a problem. The permissions given on it are not common. You can create a file with the desired permissions, but you will never be able to change the permissions afterwards. THis is a flaw in the sharing permission handling if the user has only Change permissions but not Full Control. Your admin should change that and rather fix the permissions in the share's ACL. Even Microsoft recommends that. This problem persists, of course. Only your admin can change it. I seem to remember that I have full access on this H: drive, according to the properties menu, in contrast to another drive which had the same problem, but I'll check again. Thomas
Re: 1.7 installation failed (on network drive?)
On Dec 18 16:08, Thomas Wolff wrote: Corinna Vinschen schrieb: On Dec 18 11:57, Corinna Vinschen wrote: On Dec 17 17:31, Corinna Vinschen wrote: I applied a patch which falls back to opening/creating the file/dir without WRITE_DAC if the first call failed. That's not quite optimal but it works. Please check out the latest from CVS and test in your scenario. For me it works now on the share as well as on local drives. The downside is that it will not create any POSIX-like permissions on the share. I'm just creating another solution which allows to give normal POSIX permissions to the files, just like on a local drive. I applied tha patch to CVS. The NtCreateFile call now gets the POSIX-like ACL to create the file immediately with the correct permissions. Please give it a try. I can do that on Monday, hope it's sufficient. Well, it works for me :) Be aware that this share is really a problem. The permissions given on it are not common. You can create a file with the desired permissions, but you will never be able to change the permissions afterwards. THis is a flaw in the sharing permission handling if the user has only Change permissions but not Full Control. Your admin should change that and rather fix the permissions in the share's ACL. Even Microsoft recommends that. This problem persists, of course. Only your admin can change it. I seem to remember that I have full access on this H: drive, according to the properties menu, in contrast to another drive which had the same problem, but I'll check again. If I set the permissions on the share to Full Control, I can't reproduce the problem anymore. In fact, if you check in the security tab in the file properties, you can change the permissions of files owned by you as usual. Onl;y in case of the share permissions set to Change I can reproduce this. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
On Dec 17 02:12, Thomas Wolff wrote: I took an extra drive to the lab this afternoon, with no good results. [...] mkdir:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f filemanip:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f\setup-2.ini mkdir:NtCreateFile - C022 This appears to be the actual start of the desaster. The problem is that the above alone gives us no clue about the real reason for the access denied error. It's quite puzzeling that there's no log from NTSecurity::SetPosixPerms(), so setting the permissions worked fine, apparently. Here's what we need next: - Who are you (Windows user and primary group name)? - Output of `cacls D:\' - In GDB, set a breakpoint on mkdir_p and stop right at the point above, *before* NtCreateFile gets called. - What are the permission bits given to the mkdir_p call above? - Output of `cacls D:\cygwin17p' right before the NtCreateFile call. - Output of `cacls D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f' right after the NtCreateFile call but *before* the call to nt_sec.SetPosixPerms(). - Output of `cacls D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f' right after the nt_sec.SetPosixPerms() call. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
Corinna Vinschen wrote: On Dec 17 02:12, Thomas Wolff wrote: I took an extra drive to the lab this afternoon, with no good results. [...] mkdir:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f filemanip:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f\setup-2.ini mkdir:NtCreateFile - C022 This appears to be the actual start of the desaster. I guess I should have made clear that the trace of the filename comes *after* the trace of the status in my logs, sorry. So in this log, it's: mkdir:NtCreateFile - C022 \??\H:\cygwin17\etc\setup Anyway, this complies with the fact that's it's the network drive H: giving the problems, not D: which is a local drive. So I think I should apply all your instructions to H:\cygwin17\etc\setup, or to H:\cygwin17p in the reverse test case: mkdir:NtCreateFile - C022 \??\H:\cygwin17p The problem is that the above alone gives us no clue about the real reason for the access denied error. It's quite puzzeling that there's no log from NTSecurity::SetPosixPerms(), so setting the permissions worked fine, apparently. That's quite clear because after return status C0*22, SetPosixPerms will not be called as it is guarded by if (NT_SUCCESS (status)) Maybe I'll be able to test again tomorrow. What about the option to use mkdir (the normal one from libc) rather than NtCreateFile? I think there were some considerations about assigning backup flags but maybe that's not needed for directories? Thomas Here's what we need next: - Who are you (Windows user and primary group name)? - Output of `cacls D:\' - In GDB, set a breakpoint on mkdir_p and stop right at the point above, *before* NtCreateFile gets called. - What are the permission bits given to the mkdir_p call above? - Output of `cacls D:\cygwin17p' right before the NtCreateFile call. - Output of `cacls D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f' right after the NtCreateFile call but *before* the call to nt_sec.SetPosixPerms(). - Output of `cacls D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f' right after the nt_sec.SetPosixPerms() call. Corinna
Re: 1.7 installation failed (on network drive?)
On Dec 17 12:17, Thomas Wolff wrote: Corinna Vinschen wrote: On Dec 17 02:12, Thomas Wolff wrote: I took an extra drive to the lab this afternoon, with no good results. [...] mkdir:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f filemanip:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2fftp-stud.hs-esslingen.de%2fpub%2fMirrors%2fsources.redhat.com%2fcygwin%2f\setup-2.ini mkdir:NtCreateFile - C022 This appears to be the actual start of the desaster. I guess I should have made clear that the trace of the filename comes *after* the trace of the status in my logs, sorry. So in this log, it's: mkdir:NtCreateFile - C022 \??\H:\cygwin17\etc\setup No, that was quite clear. I just got out of sync when reading the log output. Anyway, this complies with the fact that's it's the network drive H: giving the problems, not D: which is a local drive. So I think I should apply all your instructions to H:\cygwin17\etc\setup, or to H:\cygwin17p in the reverse test case: mkdir:NtCreateFile - C022 \??\H:\cygwin17p Just keep everything as it is. The problem is that you get a C022, STATUS_ACCESS_DENIED. I can only reprocude this if I really have no right to create a directory. Has the H:\cygwin17 directory been created at all? If so, we should examine the cacls for this dir just like the cacls for H:\ itself. Hmm. [...time passes...] Hang on, there's another possible reason for STATUS_ACCESS_DENIED. Mkdir_p calls NtCreateFile to create the directory with STANDARD_RIGHTS_ALL rights. This includes WRITE_DAC and WRITE_OWNER rights. Especially the last one could be a problem for a non-admin user. Could you please try to replace STANDARD_RIGHTS_ALL with SYNCHRONIZE | WRITE_DAC | READ_CONTROL If that works, we're done. If that doesn't work, try SYNCHRONIZE | READ_CONTROL If that works, you will see failure log output from SetPosixPerms(). Either way, this might be the entire problem here. If the first expression works, we should be able to use it as is. If only the second expression works, we have to do some admin/non-admin conditional. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
On Dec 17 14:09, Corinna Vinschen wrote: Has the H:\cygwin17 directory been created at all? If so, we should examine the cacls for this dir just like the cacls for H:\ itself. Hmm. [...time passes...] Hang on, there's another possible reason for STATUS_ACCESS_DENIED. Mkdir_p calls NtCreateFile to create the directory with STANDARD_RIGHTS_ALL rights. This includes WRITE_DAC and WRITE_OWNER rights. Especially the last one could be a problem for a non-admin user. Could you please try to replace STANDARD_RIGHTS_ALL with SYNCHRONIZE | WRITE_DAC | READ_CONTROL If that works, we're done. If that doesn't work, try SYNCHRONIZE | READ_CONTROL If that works, you will see failure log output from SetPosixPerms(). Either way, this might be the entire problem here. If the first expression works, we should be able to use it as is. If only the second expression works, we have to do some admin/non-admin conditional. Good news. I can finally reproduce the problem. Digging deeper now... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
Corinna Vinschen wrote: On Dec 17 14:09, Corinna Vinschen wrote: Has the H:\cygwin17 directory been created at all? If so, we should examine the cacls for this dir just like the cacls for H:\ itself. No, it hasn't. For some ACLs, see below. Hmm. [...time passes...] Hang on, there's another possible reason for STATUS_ACCESS_DENIED. Mkdir_p calls NtCreateFile to create the directory with STANDARD_RIGHTS_ALL rights. This includes WRITE_DAC and WRITE_OWNER rights. Especially the last one could be a problem for a non-admin user. I looked up what these two mean and in fact it sounds like the problem; I had previously sent the output of getfacl on the drive directories and on directories manually created there, don't know if that helps: Also here is the output of getfacl for directories on the two network drives I had tried: # file: /cygdrive/h # owner: Administratoren # group: user::rwx user:wolff:rwx group::--- group:SYSTEM:rwx mask:rwx other:--- default:user::rwx default:user:Administratoren:rwx default:user:wolff:rwx default:group:SYSTEM:rwx default:mask:rwx # file: /cygdrive/h/cygwin # owner: wolff # group: Domänen-Benutzer user::rwx group::--- group:root:rwx group:SYSTEM:rwx mask:rwx other:--- default:user::rwx default:user:wolff:rwx default:group:root:rwx default:group:SYSTEM:rwx default:mask:rwx # file: /cygdrive/t/TGI # owner: Administratoren # group: user::rwx group::--- group:SYSTEM:rwx group:Benutzer:r-x mask:rwx other:--- default:user::rwx default:user:Administratoren:rwx default:group:SYSTEM:rwx default:group:Benutzer:r-x default:mask:rwx # file: /cygdrive/t/TGI/cygwin # owner: Administratoren # group: user::rwx group::--- group:SYSTEM:rwx group:Benutzer:r-x mask:rwx other:--- default:user::rwx default:user:Administratoren:rwx default:group:SYSTEM:rwx default:group:Benutzer:r-x default:mask:rwx Also, speaking of ACLs and pondering about possible effects of their inheritance, it comes to my mind that it might make a difference whether to create H:\cygwin in a mounted H: drive or H:\mydir\cygwin so I'll try that next time. Could you please try to replace STANDARD_RIGHTS_ALL with SYNCHRONIZE | WRITE_DAC | READ_CONTROL If that works, we're done. If that doesn't work, try SYNCHRONIZE | READ_CONTROL If that works, you will see failure log output from SetPosixPerms(). Either way, this might be the entire problem here. If the first expression works, we should be able to use it as is. If only the second expression works, we have to do some admin/non-admin conditional. Good news. I can finally reproduce the problem. Digging deeper now... Great, so I'll wait. Concerning time until release, if you want me to test something tomorrow morning that's OK, if you want me to test something today, please provide compiled debug versions somewhere on the net as I cannot compile it here. Thomas
Re: 1.7 installation failed (on network drive?)
On Dec 17 14:38, Corinna Vinschen wrote: On Dec 17 14:09, Corinna Vinschen wrote: Has the H:\cygwin17 directory been created at all? If so, we should examine the cacls for this dir just like the cacls for H:\ itself. Hmm. [...time passes...] Hang on, there's another possible reason for STATUS_ACCESS_DENIED. Mkdir_p calls NtCreateFile to create the directory with STANDARD_RIGHTS_ALL rights. This includes WRITE_DAC and WRITE_OWNER rights. Especially the last one could be a problem for a non-admin user. Could you please try to replace STANDARD_RIGHTS_ALL with SYNCHRONIZE | WRITE_DAC | READ_CONTROL If that works, we're done. If that doesn't work, try SYNCHRONIZE | READ_CONTROL If that works, you will see failure log output from SetPosixPerms(). Either way, this might be the entire problem here. If the first expression works, we should be able to use it as is. If only the second expression works, we have to do some admin/non-admin conditional. Good news. I can finally reproduce the problem. Digging deeper now... It turned out that even the WRITE_DAC access can result in an access denied error on a share if the user is not an admin user, even though the file is owned by the creator. This can also be observed when you open the file's properties dialog and visit the security tab. While you can press the Edit... button (it's not grayed out) you can not edit the DACL despite being the owner of the file. Go figure! I applied a patch which falls back to opening/creating the file/dir without WRITE_DAC if the first call failed. That's not quite optimal but it works. Please check out the latest from CVS and test in your scenario. For me it works now on the share as well as on local drives. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
Corinna Vinschen schrieb: On Dec 11 12:52, Thomas Wolff wrote: Corinna Vinschen wrote: #define STATUS_OBJECT_PATH_NOT_FOUND ((NTSTATUS)0xC03AL) #define STATUS_OBJECT_PATH_SYNTAX_BAD ((NTSTATUS)0xC03BL) However, before the fatal error occurs, it's just STATUS_ACCESS_DENIED in both cases. ... Starting cygwin install, version 2.662 filemanip:NtCreateFile - C03B This one might be the actual problem. What's the actual path given to NtCreateFile (in uname)? Does it contain slashes maybe? There is \??\/var and occasional double and triple backslashes; I wonder what \?? means. See new log files attached. Thomas sh-3.2$ ./setup.exe Starting cygwin install, version 2.662 filemanip:NtCreateFile - C03B \??\h:\\\setup.rc filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\setup.rc io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\last-cache filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\last-cache io_stream_cygfile: fopen(/etc/setup/last-cache) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\last-action filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\last-action io_stream_cygfile: fopen(/etc/setup/last-action) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\net-method filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\net-method io_stream_cygfile: fopen(/etc/setup/net-method) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\net-proxy-host filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\net-proxy-host io_stream_cygfile: fopen(/etc/setup/net-proxy-host) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\net-proxy-port filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\net-proxy-port io_stream_cygfile: fopen(/etc/setup/net-proxy-port) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\last-mirror filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\last-mirror io_stream_cygfile: fopen(/etc/setup/last-mirror) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\extrakeys filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\extrakeys io_stream_cygfile: fopen(/etc/setup/extrakeys) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\chooser_window_settings filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\chooser_window_settings io_stream_cygfile: fopen(/etc/setup/chooser_window_settings) failed 2 No such file or directory Current Directory: h:\ User has NO backup/restore rights Could not open Service control manager source: network install root: H:\cygwin17 binary user filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\installed.db io_stream_cygfile: fopen(/etc/setup/installed.db) failed 2 No such file or directory mkdir:NtCreateFile - C034 \??\/var mkdir:NtCreateFile - C033 \??\ Selected local directory: D:\cygwin17p mkdir:NtCreateFile - 0 \??\D:\cygwin17p net: Direct filemanip:NtCreateFile - C03B \??\h:\\\mirrors-lst filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\mirrors-lst io_stream_cygfile: fopen(/etc/setup/mirrors-lst) failed 2 No such file or directory Cached mirror list unavailable get_url_to_membuf http://cygwin.com/mirrors.lst getUrlToStream http://cygwin.com/mirrors.lst site: http://linux.rz.ruhr-uni-bochum.de/download/cygwin/ get_url_to_membuf http://linux.rz.ruhr-uni-bochum.de/download/cygwin//setup-2.bz2 getUrlToStream http://linux.rz.ruhr-uni-bochum.de/download/cygwin//setup-2.bz2 get_url_to_membuf http://linux.rz.ruhr-uni-bochum.de/download/cygwin//setup-2.bz2.sig getUrlToStream http://linux.rz.ruhr-uni-bochum.de/download/cygwin//setup-2.bz2.sig mkdir:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f filemanip:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f\setup-2.ini mkdir:NtCreateFile - C022 \??\H:\cygwin17\etc\setup filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\timestamp io_stream_cygfile: fopen(/etc/setup/timestamp) failed 2 No such file or directory filemanip:NtCreateFile - C022 \??\H:\cygwin17\etc\setup\timestamp io_stream_cygfile: fopen(/etc/setup/timestamp) failed 13 Permission denied mkdir:NtCreateFile - C03A \??\D:\cygwin17p\http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f\release-2\alternatives mkdir:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f\release-2 mkdir:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f\release-2\alternatives get_url_to_file http://linux.rz.ruhr-uni-bochum.de/download/cygwin//release-2/alternatives/alternatives-1.3.30c-10.tar.bz2
Re: 1.7 installation failed (on network drive?)
Corinna Vinschen schrieb: On Dec 11 12:52, Thomas Wolff wrote: Corinna Vinschen wrote: #define STATUS_OBJECT_PATH_NOT_FOUND ((NTSTATUS)0xC03AL) #define STATUS_OBJECT_PATH_SYNTAX_BAD ((NTSTATUS)0xC03BL) However, before the fatal error occurs, it's just STATUS_ACCESS_DENIED in both cases. ... Starting cygwin install, version 2.662 filemanip:NtCreateFile - C03B This one might be the actual problem. What's the actual path given to NtCreateFile (in uname)? Does it contain slashes maybe? There is \??\/var and occasional double and triple backslashes; I wonder what \?? means. See new log files attached. Thomas sh-3.2$ ./setup.exe Starting cygwin install, version 2.662 filemanip:NtCreateFile - C03B \??\h:\\\setup.rc filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\setup.rc io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\last-cache filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\last-cache io_stream_cygfile: fopen(/etc/setup/last-cache) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\last-action filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\last-action io_stream_cygfile: fopen(/etc/setup/last-action) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\net-method filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\net-method io_stream_cygfile: fopen(/etc/setup/net-method) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\net-proxy-host filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\net-proxy-host io_stream_cygfile: fopen(/etc/setup/net-proxy-host) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\net-proxy-port filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\net-proxy-port io_stream_cygfile: fopen(/etc/setup/net-proxy-port) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\last-mirror filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\last-mirror io_stream_cygfile: fopen(/etc/setup/last-mirror) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\extrakeys filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\extrakeys io_stream_cygfile: fopen(/etc/setup/extrakeys) failed 2 No such file or directory filemanip:NtCreateFile - C03B \??\h:\\\chooser_window_settings filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\chooser_window_settings io_stream_cygfile: fopen(/etc/setup/chooser_window_settings) failed 2 No such file or directory Current Directory: h:\ User has NO backup/restore rights Could not open Service control manager source: network install root: H:\cygwin17 binary user filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\installed.db io_stream_cygfile: fopen(/etc/setup/installed.db) failed 2 No such file or directory mkdir:NtCreateFile - C034 \??\/var mkdir:NtCreateFile - C033 \??\ Selected local directory: D:\cygwin17p mkdir:NtCreateFile - 0 \??\D:\cygwin17p net: Direct filemanip:NtCreateFile - C03B \??\h:\\\mirrors-lst filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\mirrors-lst io_stream_cygfile: fopen(/etc/setup/mirrors-lst) failed 2 No such file or directory Cached mirror list unavailable get_url_to_membuf http://cygwin.com/mirrors.lst getUrlToStream http://cygwin.com/mirrors.lst site: http://linux.rz.ruhr-uni-bochum.de/download/cygwin/ get_url_to_membuf http://linux.rz.ruhr-uni-bochum.de/download/cygwin//setup-2.bz2 getUrlToStream http://linux.rz.ruhr-uni-bochum.de/download/cygwin//setup-2.bz2 get_url_to_membuf http://linux.rz.ruhr-uni-bochum.de/download/cygwin//setup-2.bz2.sig getUrlToStream http://linux.rz.ruhr-uni-bochum.de/download/cygwin//setup-2.bz2.sig mkdir:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f filemanip:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f\setup-2.ini mkdir:NtCreateFile - C022 \??\H:\cygwin17\etc\setup filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\timestamp io_stream_cygfile: fopen(/etc/setup/timestamp) failed 2 No such file or directory filemanip:NtCreateFile - C022 \??\H:\cygwin17\etc\setup\timestamp io_stream_cygfile: fopen(/etc/setup/timestamp) failed 13 Permission denied mkdir:NtCreateFile - C03A \??\D:\cygwin17p\http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f\release-2\alternatives mkdir:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f\release-2 mkdir:NtCreateFile - 0 \??\D:\cygwin17p\http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f\release-2\alternatives get_url_to_file http://linux.rz.ruhr-uni-bochum.de/download/cygwin//release-2/alternatives/alternatives-1.3.30c-10.tar.bz2
Re: 1.7 installation failed (on network drive?)
Thomas Wolff wrote: Current Directory: h:\ User has NO backup/restore rights Could not open Service control manager source: network install root: H:\cygwin17 binary user filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\installed.db io_stream_cygfile: fopen(/etc/setup/installed.db) failed 2 No such file or directory mkdir:NtCreateFile - C034 \??\/var mkdir:NtCreateFile - C033 \??\ Urgh! We can't convert a relative path to a dosdevices path like /that/! cheers, DaveK
Re: 1.7 installation failed (on network drive?)
On Dec 15 15:33, Dave Korn wrote: Thomas Wolff wrote: Current Directory: h:\ User has NO backup/restore rights Could not open Service control manager source: network install root: H:\cygwin17 binary user filemanip:NtCreateFile - C03A \??\H:\cygwin17\etc\setup\installed.db io_stream_cygfile: fopen(/etc/setup/installed.db) failed 2 No such file or directory mkdir:NtCreateFile - C034 \??\/var mkdir:NtCreateFile - C033 \??\ Urgh! We can't convert a relative path to a dosdevices path like /that/! Sure, that's not supposed to happen. I'm already looking into that. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
Thomas Wolff wrote: Dave Korn wrote: Thomas Wolff wrote: Selected local directory: H:\cygwin17p1 mkdir:NtCreateFile - C022 mbox note: Couldn't create directory H:\cygwin17p1, sorry. (Is drive full or read-only?) So that's coming from here: status = NtCreateFile (dir, STANDARD_RIGHTS_ALL | FILE_LIST_DIRECTORY, attr, io, NULL, FILE_ATTRIBUTE_DIRECTORY, FILE_SHARE_VALID_FLAGS, FILE_CREATE, FILE_DIRECTORY_FILE | FILE_SYNCHRONOUS_IO_NONALERT | FILE_OPEN_FOR_BACKUP_INTENT, NULL, 0); Interesting. Does it possibly succeed if you remove the FILE_OPEN_FOR_BACKUP_INTENT flag? Unfortunately not. Any other flags I might remove? Nah, here's what to do. You have no problem creating directories on this share otherwise, right? So start up sysinternals filemon, set it to filter on cygwin17, then in a cmd.exe shell window run mkdir \?\H:\cygwin17p2, then run setup.exe and let it try and create H:\cygwin17p1, then let's compare the logs for those two events and see what flags each call was using. cheers, DaveK
Re: 1.7 installation failed (on network drive?)
On Dec 15 15:25, Thomas Wolff wrote:
Corinna Vinschen schrieb:
On Dec 11 12:52, Thomas Wolff wrote:
Corinna Vinschen wrote:
#define STATUS_OBJECT_PATH_NOT_FOUND ((NTSTATUS)0xC03AL)
#define STATUS_OBJECT_PATH_SYNTAX_BAD ((NTSTATUS)0xC03BL)
However, before the fatal error occurs, it's just
STATUS_ACCESS_DENIED in both cases.
...
Starting cygwin install, version 2.662
filemanip:NtCreateFile - C03B
This one might be the actual problem. What's the actual path given
to NtCreateFile (in uname)? Does it contain slashes maybe?
There is \??\/var and occasional double and triple backslashes; I
wonder what \?? means.
\?? is a shortcut for the DOS device subdirectory in the native NT
namespace. C:\foo in DOS is \??\C:\foo in native NT speak.
\\server\share in DOS is \??\UNC\server\share.
The problem is that the native NT namespace does not recognize / as
path separator anymore. So / must be converted to \ before calling
native NT functions. Multiple backslashes are also not allowed, the
path must be normalized already. This is all the job of the caller.
Try the below patch, please. I installed to an H:\cygwin directory
fresh from scratch and it worked fine for me. I'm wondering what bugs
will remain for you. Please note that a couple of the no such file or
directory style messages are a result of setup trying to find the
setting files (like setup.rc) from a former run. If they don't exist
yet, you get these No such file messages, but they are not important.
Corinna
Index: filemanip.cc
===
RCS file: /cvs/cygwin-apps/setup/filemanip.cc,v
retrieving revision 2.26
diff -u -p -r2.26 filemanip.cc
--- filemanip.cc3 Jun 2009 08:16:21 - 2.26
+++ filemanip.cc15 Dec 2009 16:14:45 -
@@ -183,12 +183,12 @@ backslash(const std::string s)
}
wchar_t tfx_chars[] = {
- 0, 1, 2, 3, 4, 5, 6, 7,
- 8, 9, 10, 11, 12, 13, 14, 15,
- 16, 17, 18, 19, 20, 21, 22, 23,
- 24, 25, 26, 27, 28, 29, 30, 31,
- 32, '!', 0xf000 | '', '#', '$', '%', '', 39,
- '(', ')', 0xf000 | '*', '+', ',', '-', '.', '\\',
+ 0, 0xf001, 0xf002, 0xf003, 0xf004, 0xf005, 0xf006, 0xf007,
+ 0xf008, 0xf009, 0xf00a, 0xf00b, 0xf00c, 0xf00d, 0xf00e, 0xf00f,
+ 0xf010, 0xf011, 0xf012, 0xf013, 0xf014, 0xf015, 0xf016, 0xf017,
+ 0xf018, 0xf019, 0xf01a, 0xf01b, 0xf01c, 0xf01d, 0xf01e, 0xf01f,
+ ' ', '!', 0xf000 | '', '#', '$', '%', '', 39,
+ '(', ')', 0xf000 | '*', '+', ',', '-', '.', '\\',
'0', '1', '2', '3', '4', '5', '6', '7',
'8', '9', 0xf000 | ':', ';', 0xf000 | '', '=', 0xf000 | '', 0xf000 | '?',
'@', 'A', 'B', 'C', 'D', 'E', 'F', 'G',
Index: UserSettings.cc
===
RCS file: /cvs/cygwin-apps/setup/UserSettings.cc,v
retrieving revision 2.14
diff -u -p -r2.14 UserSettings.cc
--- UserSettings.cc 28 Jun 2009 16:40:22 - 2.14
+++ UserSettings.cc 15 Dec 2009 16:14:45 -
@@ -62,12 +62,15 @@ UserSettings::extend_table (ssize_t i)
table[i] = NULL;
}
+#define isslash(c) ((c) == '\\' || (c) == '/')
+
io_stream *
UserSettings::open_settings (const char *filename, std::string pathname)
{
pathname = file://;
pathname += cwd;
- pathname += //;
+ if (!isslash (cwd[cwd.size () - 1]) !isslash (filename[0]))
+pathname += /;
pathname += filename;
io_stream *f = io_stream::open(pathname, rt);
if (!f)
Index: localdir.cc
===
RCS file: /cvs/cygwin-apps/setup/localdir.cc,v
retrieving revision 2.31
diff -u -p -r2.31 localdir.cc
--- localdir.cc 8 Dec 2009 22:26:44 - 2.31
+++ localdir.cc 15 Dec 2009 16:14:45 -
@@ -81,7 +81,7 @@ LocalDirSetting::save ()
else
{
theLog-clearFiles();
- mkdir_p (0, /var/log, 01777);
+ mkdir_p (0, cygpath (/var/log).c_str (), 01777);
theLog-setFile (LOG_BABBLE, cygpath (/var/log/setup.log.full), false);
theLog-setFile (0, cygpath (/var/log/setup.log), true);
}
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
Re: 1.7 installation failed (on network drive?)
2009/12/15 Corinna Vinschen: \?? is a shortcut for the DOS device subdirectory in the native NT namespace. C:\foo in DOS is \??\C:\foo in native NT speak. \\server\share in DOS is \??\UNC\server\share. Shouldn't that be '\\?' rather than '\??' though? http://en.wikipedia.org/wiki/Path_%28computing%29#Uniform_Naming_Convention Andy
Re: 1.7 installation failed (on network drive?)
On Dec 15 16:27, Andy Koppe wrote: 2009/12/15 Corinna Vinschen: \?? is a shortcut for the DOS device subdirectory in the native NT namespace. C:\foo in DOS is \??\C:\foo in native NT speak. \\server\share in DOS is \??\UNC\server\share. Shouldn't that be '\\?' rather than '\??' though? No. \\?\ is the Win32 prefix for long pathnames. Internally it will be translated to \??\ before calling the native NT functions. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
Dave Korn wrote: Thomas Wolff wrote: Selected local directory: H:\cygwin17p1 mkdir:NtCreateFile - C022 mbox note: Couldn't create directory H:\cygwin17p1, sorry. (Is drive full or read-only?) So that's coming from here: status = NtCreateFile (dir, STANDARD_RIGHTS_ALL | FILE_LIST_DIRECTORY, attr, io, NULL, FILE_ATTRIBUTE_DIRECTORY, FILE_SHARE_VALID_FLAGS, FILE_CREATE, FILE_DIRECTORY_FILE | FILE_SYNCHRONOUS_IO_NONALERT | FILE_OPEN_FOR_BACKUP_INTENT, NULL, 0); Interesting. Does it possibly succeed if you remove the FILE_OPEN_FOR_BACKUP_INTENT flag? Unfortunately not. Any other flags I might remove? Also I noticed: parameter 5, AllocationSize, should be an int, while NULL is a pointer. Thomas
Re: 1.7 installation failed (on network drive?)
On Dec 11 12:52, Thomas Wolff wrote: Corinna Vinschen wrote: #define STATUS_OBJECT_PATH_NOT_FOUND ((NTSTATUS)0xC03AL) #define STATUS_OBJECT_PATH_SYNTAX_BAD ((NTSTATUS)0xC03BL) However, before the fatal error occurs, it's just STATUS_ACCESS_DENIED in both cases. What we need is this: Build a debug version of setup (you need gcc-3 for that since the -mno-cygwin option is still used), start it under GDB, and set a breakpoint to filemanip.cc:468. GDB will break there if an error gets triggered. Examine what status codes are returned. See /usr/include/w32api/ddk/ntstatus.h what status code that is. I also ran it with gdb and could just see the same status code that' also in my trace log; don't know if there's any other gdb-retrieved information you'd like to see. That might give us some clue. The only vague idea what you could try else is to remove the FILE_OPEN_REPARSE_POINT flag from the NtCreateFile call and see if it works without that. That makes no difference, I tried both versions. The flag is only used in filemanip.cc anyway while the problem occurs in mkdir.cc. Hope this helps a little bit, maybe at least for coming up with further debug instructions. Thomas Starting cygwin install, version 2.662 filemanip:NtCreateFile - C03B This one might be the actual problem. What's the actual path given to NtCreateFile (in uname)? Does it contain slashes maybe? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
On Dec 14 16:21, Thomas Wolff wrote: Dave Korn wrote: Thomas Wolff wrote: Selected local directory: H:\cygwin17p1 mkdir:NtCreateFile - C022 mbox note: Couldn't create directory H:\cygwin17p1, sorry. (Is drive full or read-only?) So that's coming from here: status = NtCreateFile (dir, STANDARD_RIGHTS_ALL | FILE_LIST_DIRECTORY, attr, io, NULL, FILE_ATTRIBUTE_DIRECTORY, FILE_SHARE_VALID_FLAGS, FILE_CREATE, FILE_DIRECTORY_FILE | FILE_SYNCHRONOUS_IO_NONALERT | FILE_OPEN_FOR_BACKUP_INTENT, NULL, 0); Interesting. Does it possibly succeed if you remove the FILE_OPEN_FOR_BACKUP_INTENT flag? Unfortunately not. Any other flags I might remove? Also I noticed: parameter 5, AllocationSize, should be an int, while NULL is a pointer. AllocationSize is a PLARGE_INTEGER. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
I wrote: Dave Korn wrote: Thomas Wolff wrote: Selected local directory: H:\cygwin17p1 mkdir:NtCreateFile - C022 mbox note: Couldn't create directory H:\cygwin17p1, sorry. (Is drive full or read-only?) So that's coming from here: status = NtCreateFile (dir, STANDARD_RIGHTS_ALL | FILE_LIST_DIRECTORY, attr, io, NULL, FILE_ATTRIBUTE_DIRECTORY, FILE_SHARE_VALID_FLAGS, FILE_CREATE, FILE_DIRECTORY_FILE | FILE_SYNCHRONOUS_IO_NONALERT | FILE_OPEN_FOR_BACKUP_INTENT, NULL, 0); Interesting. Does it possibly succeed if you remove the FILE_OPEN_FOR_BACKUP_INTENT flag? Unfortunately not. Any other flags I might remove? Also I noticed: parameter 5, AllocationSize, should be an int, while NULL is a pointer. Sorry, it's a pointer to int, I didn't see the P before on the MS doc page with its tiny font...
Re: 1.7 installation failed (on network drive?)
Corinna Vinschen wrote: Thomas, On Dec 7 17:09, Thomas Wolff wrote: I've tested the network installation with last Saturday's update of setup-1.7.exe and unfortunately, the problem remains. However, I can add a screen log after calling setup from mintty for the case that setup cannot even store its log anywhere (attached). Don't know if that helps. Apparently setup-1-7.exe cannot create directories (including the top package directory) on that network NFTS drive, although all other tools can easily create them. Despite cgf's point this should not delay the 1.7.1 release, may I suggest once more (and I'm not adding this to the 1.7.1 release date thread) that while the release is being delayed anyway due to other discussions, we might as well try to resolve this. Personally, I can do with a workaround; I'm just trying to help avoid trouble with other users complaining after the release... Thomas I just had another look into this and unfortunately I still can't reproduce it. What I see in your log output is the fact that ... hang on ... io_stream_cygfile: fopen(/etc/setup/timestamp) failed 13 Permission denied io_stream_cygfile: fopen(/var/run/utmp) failed 13 Permission denied io_stream_cygfile: fopen(/etc/setup/alternatives.lst.gz) failed 13 Permission denied [etc] So the fopen calls fail. fopen in setup is actually a call to nt_wfopen in filemanip.cc. If you could take a look, it's not a very complicated function. The general idea is to call NtCreateFile with FILE_OPEN_FOR_BACKUP_INTENT rights to allow an admin to install without permission trouble. As you can see, the error handling (lines 466ff) is somewhat oversimplified. You get a Permission denied as a fallback error if none of the path-related errors is triggered. Unfortunately we don't know the exact status code returned by NtCreateFile and I have no real idea what the problem might be. I have traced the status values returned by NtCreateFile (with printf actually), see the screen logs attached. I pasted in the popup error messages where they occurred. There is a bunch of the following NtCreateFile problems in the log: #define STATUS_ACCESS_DENIED ((NTSTATUS)0xC022L) #define STATUS_OBJECT_NAME_INVALID ((NTSTATUS)0xC033L) #define STATUS_OBJECT_NAME_NOT_FOUND ((NTSTATUS)0xC034L) #define STATUS_OBJECT_PATH_NOT_FOUND ((NTSTATUS)0xC03AL) #define STATUS_OBJECT_PATH_SYNTAX_BAD ((NTSTATUS)0xC03BL) However, before the fatal error occurs, it's just STATUS_ACCESS_DENIED in both cases. What we need is this: Build a debug version of setup (you need gcc-3 for that since the -mno-cygwin option is still used), start it under GDB, and set a breakpoint to filemanip.cc:468. GDB will break there if an error gets triggered. Examine what status codes are returned. See /usr/include/w32api/ddk/ntstatus.h what status code that is. I also ran it with gdb and could just see the same status code that' also in my trace log; don't know if there's any other gdb-retrieved information you'd like to see. That might give us some clue. The only vague idea what you could try else is to remove the FILE_OPEN_REPARSE_POINT flag from the NtCreateFile call and see if it works without that. That makes no difference, I tried both versions. The flag is only used in filemanip.cc anyway while the problem occurs in mkdir.cc. Hope this helps a little bit, maybe at least for coming up with further debug instructions. Thomas Starting cygwin install, version 2.662 filemanip:NtCreateFile - C03B filemanip:NtCreateFile - C03A io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory filemanip:NtCreateFile - C03B filemanip:NtCreateFile - C03A io_stream_cygfile: fopen(/etc/setup/last-cache) failed 2 No such file or directory filemanip:NtCreateFile - C03B filemanip:NtCreateFile - C03A io_stream_cygfile: fopen(/etc/setup/last-action) failed 2 No such file or directory filemanip:NtCreateFile - C03B filemanip:NtCreateFile - C03A io_stream_cygfile: fopen(/etc/setup/net-method) failed 2 No such file or directory filemanip:NtCreateFile - C03B filemanip:NtCreateFile - C03A io_stream_cygfile: fopen(/etc/setup/net-proxy-host) failed 2 No such file or directory filemanip:NtCreateFile - C03B filemanip:NtCreateFile - C03A io_stream_cygfile: fopen(/etc/setup/net-proxy-port) failed 2 No such file or directory filemanip:NtCreateFile - C03B filemanip:NtCreateFile - C03A io_stream_cygfile: fopen(/etc/setup/last-mirror) failed 2 No such file or directory filemanip:NtCreateFile - C03B filemanip:NtCreateFile - C03A io_stream_cygfile: fopen(/etc/setup/extrakeys) failed 2 No such file or directory filemanip:NtCreateFile - C03B filemanip:NtCreateFile - C03A io_stream_cygfile: fopen(/etc/setup/chooser_window_settings) failed 2 No such file or directory Current Directory: h:\ User has NO backup/restore rights Could not open Service control manager
Re: 1.7 installation failed (on network drive?)
Thomas Wolff wrote: Selected local directory: H:\cygwin17p1 mkdir:NtCreateFile - C022 mbox note: Couldn't create directory H:\cygwin17p1, sorry. (Is drive full or read-only?) So that's coming from here: status = NtCreateFile (dir, STANDARD_RIGHTS_ALL | FILE_LIST_DIRECTORY, attr, io, NULL, FILE_ATTRIBUTE_DIRECTORY, FILE_SHARE_VALID_FLAGS, FILE_CREATE, FILE_DIRECTORY_FILE | FILE_SYNCHRONOUS_IO_NONALERT | FILE_OPEN_FOR_BACKUP_INTENT, NULL, 0); Interesting. Does it possibly succeed if you remove the FILE_OPEN_FOR_BACKUP_INTENT flag? cheers, DaveK
Re: 1.7 installation failed (on network drive?)
Corinna Vinschen wrote: cvs -d :pserver:anon...@cygwin.com:/cvs/cygwin-apps setup CC=gcc-3 configure make 'CFLAGS=-g' So I don't need to switch set-gcc-default-3.sh, thanks. Actually, I already checked out and compiled (after installing a bunch of dependencies) over night after cgf's pointer to http://sources.redhat.com/cygwin-apps/setup.html. However, I didn't include the -g flag, assuming that leaving out the final 'strip' step might suffice. Only because the default CFLAGS has -g in it; if you do need to override it, you must specifiy -g yourself. The important thing here is to avoid the default -O2 flag. It makes debugging a lot harder. I'd recommend using CFLAGS='-g3 -O0' myself. It's worth having the debug info level turned right up. FTR, I configure like this: $ ./configure -C --disable-shared --host=i686-pc-mingw32 \ --build=i686-pc-cygwin CC=gcc-3 -mno-cygwin CXX=g++-3 -mno-cygwin CC_FOR_TARGET=gcc-3 -mno-cygwin CC_FOR_BUILD=gcc-3 -mno-cygwin \ CXX_FOR_TARGET=g++-3 -mno-cygwin --disable-shared I need to go back and check whether all of those are strictly necessary, but I did find gcc-4 kept creeping back into my builds without them. IIRC, the gpg-error lib needs to run a generator exe during the build, and I figured we should probably build that as a mingw exe too, hence the _FOR_BUILD settings. I'm not sure if the FOR_TARGET settings are needed still, I wasn't systematic in testing this, just kept adding settings until gcc-4 stopped showing up in the build logs. cheers, DaveK
Re: 1.7 installation failed (on network drive?)
On Thu, Dec 10, 2009 at 08:19:50PM +, Dave Korn wrote: Corinna Vinschen wrote: cvs -d :pserver:anon...@cygwin.com:/cvs/cygwin-apps setup CC=gcc-3 configure make 'CFLAGS=-g' So I don't need to switch set-gcc-default-3.sh, thanks. Actually, I already checked out and compiled (after installing a bunch of dependencies) over night after cgf's pointer to http://sources.redhat.com/cygwin-apps/setup.html. However, I didn't include the -g flag, assuming that leaving out the final 'strip' step might suffice. Only because the default CFLAGS has -g in it; if you do need to override it, you must specifiy -g yourself. The important thing here is to avoid the default -O2 flag. It makes debugging a lot harder. I'd recommend using CFLAGS='-g3 -O0' myself. It's worth having the debug info level turned right up. Don't you need to use CXXFLAGS for setup since it's c++? cgf
Re: 1.7 installation failed (on network drive?)
Christopher Faylor wrote: On Thu, Dec 10, 2009 at 08:19:50PM +, Dave Korn wrote: Corinna Vinschen wrote: cvs -d :pserver:anon...@cygwin.com:/cvs/cygwin-apps setup CC=gcc-3 configure make 'CFLAGS=-g' So I don't need to switch set-gcc-default-3.sh, thanks. Actually, I already checked out and compiled (after installing a bunch of dependencies) over night after cgf's pointer to http://sources.redhat.com/cygwin-apps/setup.html. However, I didn't include the -g flag, assuming that leaving out the final 'strip' step might suffice. Only because the default CFLAGS has -g in it; if you do need to override it, you must specifiy -g yourself. The important thing here is to avoid the default -O2 flag. It makes debugging a lot harder. I'd recommend using CFLAGS='-g3 -O0' myself. It's worth having the debug info level turned right up. Don't you need to use CXXFLAGS for setup since it's c++? Boh. Yes. Thinko. CFLAGS only useful if you wanted to debug autoload or the crypto libs. cheers, DaveK
Re: 1.7 installation failed (on network drive?)
On Dec 8 18:21, Thomas Wolff wrote: Corinna Vinschen schrieb: So the fopen calls fail. fopen in setup is actually a call to nt_wfopen in filemanip.cc. If you could take a look, it's not a very complicated function. The general idea is to call NtCreateFile with FILE_OPEN_FOR_BACKUP_INTENT rights to allow an admin to install without permission trouble. As you can see, the error handling (lines 466ff) is somewhat oversimplified. You get a Permission denied as a fallback error if none of the path-related errors is triggered. Unfortunately we don't know the exact status code returned by NtCreateFile and I have no real idea what the problem might be. What we need is this: Build a debug version of setup (you need gcc-3 for that since the -mno-cygwin option is still used), start it under GDB, and set a breakpoint to filemanip.cc:468. GDB will break there if an error gets triggered. Examine what status codes are returned. See /usr/include/w32api/ddk/ntstatus.h what status code that is. OK; since setup is not a cygwin package, where would I get the sources in the first place? And is there a README telling me how to build a debug version (make debug?)? Basically: cvs -d :pserver:anon...@cygwin.com:/cvs/cygwin-apps setup CC=gcc-3 configure make 'CFLAGS=-g' Then I assume I'd use the gdb commands break and print (sorry, not familiar with gdb)? Yes. In case I don't get it compiled, maybe you could prepare two debug versions (with/w/o the change below) and send them to me? I could take an extra trip to that lab tomorrow for testing. Well, yes, but there's very little reason that you shouldn't get it build. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
Corinna Vinschen wrote: On Dec 8 18:21, Thomas Wolff wrote: Corinna Vinschen schrieb: ... Build a debug version of setup (you need gcc-3 for that since the -mno-cygwin option is still used), start it under GDB, and set a breakpoint to filemanip.cc:468. GDB will break there if an error gets triggered. Examine what status codes are returned. See /usr/include/w32api/ddk/ntstatus.h what status code that is. OK; since setup is not a cygwin package, where would I get the sources in the first place? And is there a README telling me how to build a debug version (make debug?)? Basically: cvs -d :pserver:anon...@cygwin.com:/cvs/cygwin-apps setup CC=gcc-3 configure make 'CFLAGS=-g' So I don't need to switch set-gcc-default-3.sh, thanks. Actually, I already checked out and compiled (after installing a bunch of dependencies) over night after cgf's pointer to http://sources.redhat.com/cygwin-apps/setup.html. However, I didn't include the -g flag, assuming that leaving out the final 'strip' step might suffice. In case I don't get it compiled, maybe you could prepare two debug versions (with/w/o the change below) and send them to me? I could take an extra trip to that lab tomorrow for testing. Well, yes, but there's very little reason that you shouldn't get it build. Kind of... I did the small change you suggested and ran make again for a second test build, and guess what happens? It's compiling *everything* again all over; that's not quite the purpose of make, is it? So is it really useful to go over and do the test after that's finished, or do I need to recompile two more full times with -g? Thomas
Re: 1.7 installation failed (on network drive?)
On Dec 9 11:52, Thomas Wolff wrote: Corinna Vinschen wrote: On Dec 8 18:21, Thomas Wolff wrote: Corinna Vinschen schrieb: ... Build a debug version of setup (you need gcc-3 for that since the -mno-cygwin option is still used), start it under GDB, and set a breakpoint to filemanip.cc:468. GDB will break there if an error gets triggered. Examine what status codes are returned. See /usr/include/w32api/ddk/ntstatus.h what status code that is. OK; since setup is not a cygwin package, where would I get the sources in the first place? And is there a README telling me how to build a debug version (make debug?)? Basically: cvs -d :pserver:anon...@cygwin.com:/cvs/cygwin-apps setup CC=gcc-3 configure make 'CFLAGS=-g' So I don't need to switch set-gcc-default-3.sh, thanks. Actually, I already checked out and compiled (after installing a bunch of dependencies) over night after cgf's pointer to http://sources.redhat.com/cygwin-apps/setup.html. However, I didn't include the -g flag, assuming that leaving out the final 'strip' step might suffice. The important thing here is to avoid the default -O2 flag. It makes debugging a lot harder. In case I don't get it compiled, maybe you could prepare two debug versions (with/w/o the change below) and send them to me? I could take an extra trip to that lab tomorrow for testing. Well, yes, but there's very little reason that you shouldn't get it build. Kind of... I did the small change you suggested and ran make again for a second test build, and guess what happens? It's compiling *everything* again all over; that's not quite the purpose of make, is it? Not exactly. And doesn't happen for me. Are you sure you're not having a timestamp problem due to running two machines on asynchronous times, one to build, one providing the storage? Are you not using NTP? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
Thomas, On Dec 7 17:09, Thomas Wolff wrote: I've tested the network installation with last Saturday's update of setup-1.7.exe and unfortunately, the problem remains. However, I can add a screen log after calling setup from mintty for the case that setup cannot even store its log anywhere (attached). Don't know if that helps. Apparently setup-1-7.exe cannot create directories (including the top package directory) on that network NFTS drive, although all other tools can easily create them. Despite cgf's point this should not delay the 1.7.1 release, may I suggest once more (and I'm not adding this to the 1.7.1 release date thread) that while the release is being delayed anyway due to other discussions, we might as well try to resolve this. Personally, I can do with a workaround; I'm just trying to help avoid trouble with other users complaining after the release... Thomas I just had another look into this and unfortunately I still can't reproduce it. What I see in your log output is the fact that ... hang on ... io_stream_cygfile: fopen(/etc/setup/timestamp) failed 13 Permission denied io_stream_cygfile: fopen(/var/run/utmp) failed 13 Permission denied io_stream_cygfile: fopen(/etc/setup/alternatives.lst.gz) failed 13 Permission denied [etc] So the fopen calls fail. fopen in setup is actually a call to nt_wfopen in filemanip.cc. If you could take a look, it's not a very complicated function. The general idea is to call NtCreateFile with FILE_OPEN_FOR_BACKUP_INTENT rights to allow an admin to install without permission trouble. As you can see, the error handling (lines 466ff) is somewhat oversimplified. You get a Permission denied as a fallback error if none of the path-related errors is triggered. Unfortunately we don't know the exact status code returned by NtCreateFile and I have no real idea what the problem might be. What we need is this: Build a debug version of setup (you need gcc-3 for that since the -mno-cygwin option is still used), start it under GDB, and set a breakpoint to filemanip.cc:468. GDB will break there if an error gets triggered. Examine what status codes are returned. See /usr/include/w32api/ddk/ntstatus.h what status code that is. That might give us some clue. The only vague idea what you could try else is to remove the FILE_OPEN_REPARSE_POINT flag from the NtCreateFile call and see if it works without that. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
Corinna Vinschen schrieb: Thomas, On Dec 7 17:09, Thomas Wolff wrote: I've tested the network installation with last Saturday's update of setup-1.7.exe and unfortunately, the problem remains. However, I can add a screen log after calling setup from mintty for the case that setup cannot even store its log anywhere (attached). Don't know if that helps. Apparently setup-1-7.exe cannot create directories (including the top package directory) on that network NFTS drive, although all other tools can easily create them. Despite cgf's point this should not delay the 1.7.1 release, may I suggest once more (and I'm not adding this to the 1.7.1 release date thread) that while the release is being delayed anyway due to other discussions, we might as well try to resolve this. Personally, I can do with a workaround; I'm just trying to help avoid trouble with other users complaining after the release... Thomas I just had another look into this and unfortunately I still can't reproduce it. What I see in your log output is the fact that ... hang on ... io_stream_cygfile: fopen(/etc/setup/timestamp) failed 13 Permission denied io_stream_cygfile: fopen(/var/run/utmp) failed 13 Permission denied io_stream_cygfile: fopen(/etc/setup/alternatives.lst.gz) failed 13 Permission denied [etc] So the fopen calls fail. fopen in setup is actually a call to nt_wfopen in filemanip.cc. If you could take a look, it's not a very complicated function. The general idea is to call NtCreateFile with FILE_OPEN_FOR_BACKUP_INTENT rights to allow an admin to install without permission trouble. As you can see, the error handling (lines 466ff) is somewhat oversimplified. You get a Permission denied as a fallback error if none of the path-related errors is triggered. Unfortunately we don't know the exact status code returned by NtCreateFile and I have no real idea what the problem might be. What we need is this: Build a debug version of setup (you need gcc-3 for that since the -mno-cygwin option is still used), start it under GDB, and set a breakpoint to filemanip.cc:468. GDB will break there if an error gets triggered. Examine what status codes are returned. See /usr/include/w32api/ddk/ntstatus.h what status code that is. OK; since setup is not a cygwin package, where would I get the sources in the first place? And is there a README telling me how to build a debug version (make debug?)? Then I assume I'd use the gdb commands break and print (sorry, not familiar with gdb)? In case I don't get it compiled, maybe you could prepare two debug versions (with/w/o the change below) and send them to me? I could take an extra trip to that lab tomorrow for testing. Thomas That might give us some clue. The only vague idea what you could try else is to remove the FILE_OPEN_REPARSE_POINT flag from the NtCreateFile call and see if it works without that.
Re: 1.7 installation failed (on network drive?)
On Tue, Dec 08, 2009 at 06:21:00PM +0100, Thomas Wolff wrote: OK; since setup is not a cygwin package, where would I get the sources in the first place? And is there a README telling me how to build a debug version (make debug?)? If you google setup.exe source code the first hit should answer these questions. http://sources.redhat.com/cygwin-apps/setup.html cgf
Re: 1.7 installation failed (on network drive?)
I've tested the network installation with last Saturday's update of setup-1.7.exe and unfortunately, the problem remains. However, I can add a screen log after calling setup from mintty for the case that setup cannot even store its log anywhere (attached). Don't know if that helps. Apparently setup-1-7.exe cannot create directories (including the top package directory) on that network NFTS drive, although all other tools can easily create them. Despite cgf's point this should not delay the 1.7.1 release, may I suggest once more (and I'm not adding this to the 1.7.1 release date thread) that while the release is being delayed anyway due to other discussions, we might as well try to resolve this. Personally, I can do with a workaround; I'm just trying to help avoid trouble with other users complaining after the release... Thomas I wrote: Corinna Vinschen schrieb: On Nov 25 18:30, Dave Korn wrote: Thomas Wolff wrote: Corinna Vinschen wrote: Are you sure the share permissions are sufficient? In contrast to the 1.5 setup, the 1.7 setup tries to create files and directories with explicit ACLs. On the H: drive, I have full access according to the Windows properties dialog. On the T: drive, I don't, but I have read and write permissions of course. However, missing rights to modify ACLs might indeed by the issue here. 100%. In usual *nix terms, however, I have sufficient rights to do anything I need, so I think setup.exe might want to be more fault-tolerant here (and issue more precise error hints), esp. if setting ACLs fails. Need better error handling, it should fall back to whatever it does on FAT systems. The files and directories are created with default ACLs. The POSIX-like permissions are set afterwards. It does not matter to setup if setting the POSIX-like permissions fails. However, if anything didn't work in there, you should see this in the setup log. Here is some additional information, and log files attached. If I try local package dir D:\cygwin17 and network root dir H:\cygwin17, I get the error unable to extract /etc ... (H:\cygwin17 has not even been created, if I do that manually and repeat, there is no change) since there is no root dir and sub-dirs created, there is also no log file (or could I have redirected it with setup-1.7.exe?) If I try network package dir H:\cygwin17 and local root dir D:\cygwin17, manual creation of H:\cygwin17 is necessary, and I get that other error; two log files for this case are attached. Also here is the output of getfacl for directories on the two network drives I had tried: # file: /cygdrive/h # owner: Administratoren # group: user::rwx user:wolff:rwx group::--- group:SYSTEM:rwx mask:rwx other:--- default:user::rwx default:user:Administratoren:rwx default:user:wolff:rwx default:group:SYSTEM:rwx default:mask:rwx # file: /cygdrive/h/cygwin # owner: wolff # group: Domänen-Benutzer user::rwx group::--- group:root:rwx group:SYSTEM:rwx mask:rwx other:--- default:user::rwx default:user:wolff:rwx default:group:root:rwx default:group:SYSTEM:rwx default:mask:rwx # file: /cygdrive/t/TGI # owner: Administratoren # group: user::rwx group::--- group:SYSTEM:rwx group:Benutzer:r-x mask:rwx other:--- default:user::rwx default:user:Administratoren:rwx default:group:SYSTEM:rwx default:group:Benutzer:r-x default:mask:rwx # file: /cygdrive/t/TGI/cygwin # owner: Administratoren # group: user::rwx group::--- group:SYSTEM:rwx group:Benutzer:r-x mask:rwx other:--- default:user::rwx default:user:Administratoren:rwx default:group:SYSTEM:rwx default:group:Benutzer:r-x default:mask:rwx Hope this helps. Thomas sh-3.2$ ./setup-1.7.exe Starting cygwin install, version 2.661 io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory io_stream_cygfile: fopen(/etc/setup/last-cache) failed 2 No such file or directory io_stream_cygfile: fopen(/etc/setup/last-action) failed 2 No such file or directory io_stream_cygfile: fopen(/etc/setup/net-method) failed 2 No such file or directory io_stream_cygfile: fopen(/etc/setup/net-proxy-host) failed 2 No such file or directory io_stream_cygfile: fopen(/etc/setup/net-proxy-port) failed 2 No such file or directory io_stream_cygfile: fopen(/etc/setup/last-mirror) failed 2 No such file or directory io_stream_cygfile: fopen(/etc/setup/extrakeys) failed 2 No such file or directory io_stream_cygfile: fopen(/etc/setup/chooser_window_settings) failed 2 No such file or directory Current Directory: d:\ User has NO backup/restore rights Could not open Service control manager source: from cwd root: H:\cygwin17a binary user io_stream_cygfile: fopen(/etc/setup/installed.db) failed 2 No such file or directory Selected local directory: d:\cygwin17 Found ini file - d:\cygwin17/http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f/setup-2.ini io_stream_cygfile:
Re: 1.7 installation failed (on network drive?)
Corinna Vinschen schrieb: On Nov 25 18:30, Dave Korn wrote: Thomas Wolff wrote: Corinna Vinschen wrote: Are you sure the share permissions are sufficient? In contrast to the 1.5 setup, the 1.7 setup tries to create files and directories with explicit ACLs. On the H: drive, I have full access according to the Windows properties dialog. On the T: drive, I don't, but I have read and write permissions of course. However, missing rights to modify ACLs might indeed by the issue here. 100%. In usual *nix terms, however, I have sufficient rights to do anything I need, so I think setup.exe might want to be more fault-tolerant here (and issue more precise error hints), esp. if setting ACLs fails. Need better error handling, it should fall back to whatever it does on FAT systems. The files and directories are created with default ACLs. The POSIX-like permissions are set afterwards. It does not matter to setup if setting the POSIX-like permissions fails. However, if anything didn't work in there, you should see this in the setup log. Here is some additional information, and log files attached. If I try local package dir D:\cygwin17 and network root dir H:\cygwin17, I get the error unable to extract /etc ... (H:\cygwin17 has not even been created, if I do that manually and repeat, there is no change) since there is no root dir and sub-dirs created, there is also no log file (or could I have redirected it with setup-1.7.exe?) If I try network package dir H:\cygwin17 and local root dir D:\cygwin17, manual creation of H:\cygwin17 is necessary, and I get that other error; two log files for this case are attached. Also here is the output of getfacl for directories on the two network drives I had tried: # file: /cygdrive/h # owner: Administratoren # group: user::rwx user:wolff:rwx group::--- group:SYSTEM:rwx mask:rwx other:--- default:user::rwx default:user:Administratoren:rwx default:user:wolff:rwx default:group:SYSTEM:rwx default:mask:rwx # file: /cygdrive/h/cygwin # owner: wolff # group: Domänen-Benutzer user::rwx group::--- group:root:rwx group:SYSTEM:rwx mask:rwx other:--- default:user::rwx default:user:wolff:rwx default:group:root:rwx default:group:SYSTEM:rwx default:mask:rwx # file: /cygdrive/t/TGI # owner: Administratoren # group: user::rwx group::--- group:SYSTEM:rwx group:Benutzer:r-x mask:rwx other:--- default:user::rwx default:user:Administratoren:rwx default:group:SYSTEM:rwx default:group:Benutzer:r-x default:mask:rwx # file: /cygdrive/t/TGI/cygwin # owner: Administratoren # group: user::rwx group::--- group:SYSTEM:rwx group:Benutzer:r-x mask:rwx other:--- default:user::rwx default:user:Administratoren:rwx default:group:SYSTEM:rwx default:group:Benutzer:r-x default:mask:rwx Hope this helps. Thomas 2009/11/26 14:34:10 Starting cygwin install, version 2.656 2009/11/26 14:34:10 io_stream_cygfile: fopen(/etc/setup/setup.rc) failed 2 No such file or directory 2009/11/26 14:34:10 io_stream_cygfile: fopen(/etc/setup/last-cache) failed 2 No such file or directory 2009/11/26 14:34:10 io_stream_cygfile: fopen(/etc/setup/last-action) failed 2 No such file or directory 2009/11/26 14:34:10 io_stream_cygfile: fopen(/etc/setup/net-method) failed 2 No such file or directory 2009/11/26 14:34:10 io_stream_cygfile: fopen(/etc/setup/net-proxy-host) failed 2 No such file or directory 2009/11/26 14:34:10 io_stream_cygfile: fopen(/etc/setup/net-proxy-port) failed 2 No such file or directory 2009/11/26 14:34:10 io_stream_cygfile: fopen(/etc/setup/last-mirror) failed 2 No such file or directory 2009/11/26 14:34:10 io_stream_cygfile: fopen(/etc/setup/extrakeys) failed 2 No such file or directory 2009/11/26 14:34:10 io_stream_cygfile: fopen(/etc/setup/chooser_window_settings) failed 2 No such file or directory 2009/11/26 14:34:10 Current Directory: H:\ 2009/11/26 14:34:10 User has NO backup/restore rights 2009/11/26 14:34:10 Could not open Service control manager 2009/11/26 14:34:12 source: network install 2009/11/26 14:34:16 root: D:\cygwin17 binary user 2009/11/26 14:34:16 io_stream_cygfile: fopen(/etc/setup/installed.db) failed 2 No such file or directory 2009/11/26 14:34:20 Selected local directory: H:\cygwin17 2009/11/26 14:34:20 Could not change dir to H:\cygwin17: Das System kann die angegebene Datei nicht finden. [0002] 2009/11/26 14:34:30 net: Direct 2009/11/26 14:34:30 io_stream_cygfile: fopen(/etc/setup/mirrors-lst) failed 2 No such file or directory Cached mirror list unavailable get_url_to_membuf http://cygwin.com/mirrors.lst getUrlToStream http://cygwin.com/mirrors.lst 2009/11/26 14:34:36 site: http://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin/ get_url_to_membuf http://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin//setup-2.bz2 getUrlToStream http://ftp-stud.hs-esslingen.de/pub/Mirrors/sources.redhat.com/cygwin//setup-2.bz2 get_url_to_membuf
Re: 1.7 installation failed (on network drive?)
ext Corinna Vinschen wrote: On Nov 24 18:21, Thomas Wolff wrote: I tried this installation to a network drive on one machine again with last week's new setup.exe, which didn't solve the problem as Corinna had assumed, but with more detailed test results: The machine runs Windows XP Professional, drvies H: and T: are normal Windows mounts or NFTS network drives. I started setup-1.7.exe from a command line after explicitly clearing PATH completely. 1. attempt, root dir T:\cygwin17, package dir H:\cygwin17: --- Fehler --- Could not change dir to H:\cygwin17: Das System kann die angegebene Datei nicht finden. [0002] --- Abbrechen Wiederholen Ignorieren --- which - by the way - suggests the recent fix about mkdir was not complete - at least the package directory still had to be created manually. I can't reproduce this. I tried with shares on Samba, with shares on a remote NTFS on a machine in the same AD domain, and with shares on a remote machine which is not member of the domain. In all three cases I could install Cygwin from scratch just fine, using the latest setup-1.7.exe. Are you sure the share permissions are sufficient? In contrast to the 1.5 setup, the 1.7 setup tries to create files and directories with explicit ACLs. On the H: drive, I have full access according to the Windows properties dialog. On the T: drive, I don't, but I have read and write permissions of course. However, missing rights to modify ACLs might indeed by the issue here. In usual *nix terms, however, I have sufficient rights to do anything I need, so I think setup.exe might want to be more fault-tolerant here (and issue more precise error hints), esp. if setting ACLs fails. Now I guess that would explain/solve the Unable to extract /etc/ -- the file is in use. but not the Can't open H:\cygwin17/http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f/release-2/alternatives/alternatives-1.3.30c-10.tar.bz2.tmp for writing: No such file or directory because it's full access on that drive. I should also try the other way, using the respective other network drive for root dir / package dir, sorry I didn't try that before. Also, since I am not really familiar with the Windows security stuff, any diagnostic hints might help, like where to look at (so I can take some screenshots), what tools to use to check rights, or maybe even a debug version of setup.exe. Thomas I assumed that this could make problems, but in my case it just doesn't make any. When I created the shares, I just made sure that the share permissions were sufficient. Corinna
Re: 1.7 installation failed (on network drive?)
Thomas Wolff wrote: ext Corinna Vinschen wrote: Are you sure the share permissions are sufficient? In contrast to the 1.5 setup, the 1.7 setup tries to create files and directories with explicit ACLs. On the H: drive, I have full access according to the Windows properties dialog. On the T: drive, I don't, but I have read and write permissions of course. However, missing rights to modify ACLs might indeed by the issue here. 100%. In usual *nix terms, however, I have sufficient rights to do anything I need, so I think setup.exe might want to be more fault-tolerant here (and issue more precise error hints), esp. if setting ACLs fails. Need better error handling, it should fall back to whatever it does on FAT systems. Say, has anyone checked it's still possible to install to a FAT fs using the latest setup.exe? I might try digging up a pen drive later tonight and see what happens. cheers, DaveK
Re: 1.7 installation failed (on network drive?)
On Nov 25 18:30, Dave Korn wrote: Thomas Wolff wrote: ext Corinna Vinschen wrote: Are you sure the share permissions are sufficient? In contrast to the 1.5 setup, the 1.7 setup tries to create files and directories with explicit ACLs. On the H: drive, I have full access according to the Windows properties dialog. On the T: drive, I don't, but I have read and write permissions of course. However, missing rights to modify ACLs might indeed by the issue here. 100%. In usual *nix terms, however, I have sufficient rights to do anything I need, so I think setup.exe might want to be more fault-tolerant here (and issue more precise error hints), esp. if setting ACLs fails. Need better error handling, it should fall back to whatever it does on FAT systems. The files and directories are created with default ACLs. The POSIX-like permissions are set afterwards. It does not matter to setup if setting the POSIX-like permissions fails. However, if anything didn't work in there, you should see this in the setup log. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: 1.7 installation failed (on network drive?)
Dave Korn schrieb: ... Say, has anyone checked it's still possible to install to a FAT fs using the latest setup.exe? I might try digging up a pen drive later tonight and see what happens. Works (FAT32 @ USB). Thomas
Re: 1.7 installation failed (on network drive?)
Thomas Wolff wrote: Dave Korn schrieb: ... Say, has anyone checked it's still possible to install to a FAT fs using the latest setup.exe? I might try digging up a pen drive later tonight and see what happens. Works (FAT32 @ USB). Thanks for testing :) cheers, DaveK
Re: 1.7 installation failed (on network drive?)
I tried this installation to a network drive on one machine again with last week's new setup.exe, which didn't solve the problem as Corinna had assumed, but with more detailed test results: The machine runs Windows XP Professional, drvies H: and T: are normal Windows mounts or NFTS network drives. I started setup-1.7.exe from a command line after explicitly clearing PATH completely. 1. attempt, root dir T:\cygwin17, package dir H:\cygwin17: --- Fehler --- Could not change dir to H:\cygwin17: Das System kann die angegebene Datei nicht finden. [0002] --- Abbrechen Wiederholen Ignorieren --- which - by the way - suggests the recent fix about mkdir was not complete - at least the package directory still had to be created manually. 2. attempt, after manual mkdir H:\cygwin17: --- Cygwin Setup --- Can't open H:\cygwin17/http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f/release-2/alternatives/alternatives-1.3.30c-10.tar.bz2.tmp for writing: No such file or directory --- OK --- 3. attempt, this time with a local package dir D:\cygwin17: --- In-use files detected --- Unable to extract /etc/ -- the file is in use. Please stop all Cygwin processes and select Retry, or select Continue to go on anyway (you will need to reboot). --- Wiederholen Abbrechen --- This is something that Alexander Quinn also reported these days, but since he mentioned C: paths, I don't think he tried network disks, right? Side remarks: 1. If I hit Continue after the previous message, setup hangs at Installing /etc/alternatives/README 2. If I accidently put a space in front of the root directory, setup fails with a confusing message The install directory must be absolute - maybe some simple space stripping could be added here 4. attempt, the other way round: package directory H:\cygwin17, root directory D:\cygwin17: --- Cygwin Setup --- Can't open H:\cygwin17/http%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fdownload%2fcygwin%2f/release-2/alternatives/alternatives-1.3.30c-10.tar.bz2.tmp for writing: No such file or directory --- OK --- Only if I finally use local directories for both package and root dir, it works. And to complete the report, as I noted before, installation of 1.5 to the same network locations (package and root) works. Kind regards, Thomas
Re: 1.7 installation failed (on network drive?)
On Nov 24 18:21, Thomas Wolff wrote: I tried this installation to a network drive on one machine again with last week's new setup.exe, which didn't solve the problem as Corinna had assumed, but with more detailed test results: The machine runs Windows XP Professional, drvies H: and T: are normal Windows mounts or NFTS network drives. I started setup-1.7.exe from a command line after explicitly clearing PATH completely. 1. attempt, root dir T:\cygwin17, package dir H:\cygwin17: --- Fehler --- Could not change dir to H:\cygwin17: Das System kann die angegebene Datei nicht finden. [0002] --- Abbrechen Wiederholen Ignorieren --- which - by the way - suggests the recent fix about mkdir was not complete - at least the package directory still had to be created manually. I can't reproduce this. I tried with shares on Samba, with shares on a remote NTFS on a machine in the same AD domain, and with shares on a remote machine which is not member of the domain. In all three cases I could install Cygwin from scratch just fine, using the latest setup-1.7.exe. Are you sure the share permissions are sufficient? In contrast to the 1.5 setup, the 1.7 setup tries to create files and directories with explicit ACLs. I assumed that this could make problems, but in my case it just doesn't make any. When I created the shares, I just made sure that the share permissions were sufficient. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
1.7 installation failed (on network drive?)
I wanted to install 1.7 on another machine, target directory H:\cygwin, but it failed with the attached error. I had to reinstall 1.5, which I did to the same location and it worked seamlessly. Is there a problem installing 1.7 to a network drive? Thomas cygwin-install-error.png Description: Binary data
Re: 1.7 installation failed (on network drive?)
Thomas Wolff wrote: I wanted to install 1.7 on another machine, target directory H:\cygwin, but it failed with the attached error. Handy hint for next time: Did you know you can copy and paste most windows popup error dialogs? Just press Ctrl+C while the dialog is selected, and then when you paste it into your text file you'll see something like: --- Error --- Could not change dir to W:\wibble: The system cannot find the path specified. [0003] --- Abort Retry Ignore --- As to your actual problem, dunno. I think it ought to work but maybe you had a transient network failure? What happens if you try manually to create a file of that name and path? What kind of network drive is it anyway? cheers, DaveK
