Re: New Cygwin 1.7.0-18 in release-2
On Jul 17 18:18, Eric Blake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Corinna Vinschen on 7/17/2008 9:55 AM: | Hi, | | again I would like to encourage the Cygwin maintainers, to try the new | Cygwin 1.7.0 release and to look for problems in their packages which | might be a result of the fairly massive changes in Cygwin 1.7. I | attached a list of the changes below. The latest changes are: | | - Changes in mkpasswd/mkgroup and in seteuid() should result in more | correct user tokens in AD domains. Try the LSA module. | - Case-sensitivity on NTFS and NFS and mount option posix=[0|1]. | - Remove CYGWIN=ntsec and CYGWIN=smbntsec options in favor of a mount | option acl/noacl. Somewhere between setting obcaseinsensitive to 0 yesterday and upgrading to the new cygwin1.dll today, I'm now suffering from an inability to modify files on a shared drive on my work machine. I can create empty files and remove existing files just fine, but get access denied on any attempt to change contents. The -1 for owner and group looks fishy as well. Drive U is apparently a Samba drive. Is that in a Windows domain? If not, try the noacl mount option. It's equivalent to what was CYGWIN=nosmbntsec before. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: New Cygwin 1.7.0-18 in release-2
On Jul 18 09:34, Corinna Vinschen wrote: On Jul 17 18:18, Eric Blake wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Corinna Vinschen on 7/17/2008 9:55 AM: | Hi, | | again I would like to encourage the Cygwin maintainers, to try the new | Cygwin 1.7.0 release and to look for problems in their packages which | might be a result of the fairly massive changes in Cygwin 1.7. I | attached a list of the changes below. The latest changes are: | | - Changes in mkpasswd/mkgroup and in seteuid() should result in more | correct user tokens in AD domains. Try the LSA module. | - Case-sensitivity on NTFS and NFS and mount option posix=[0|1]. | - Remove CYGWIN=ntsec and CYGWIN=smbntsec options in favor of a mount | option acl/noacl. Somewhere between setting obcaseinsensitive to 0 yesterday and upgrading to the new cygwin1.dll today, I'm now suffering from an inability to modify files on a shared drive on my work machine. I can create empty files and remove existing files just fine, but get access denied on any attempt to change contents. The -1 for owner and group looks fishy as well. Drive U is apparently a Samba drive. Is that in a Windows domain? If not, try the noacl mount option. It's equivalent to what was CYGWIN=nosmbntsec before. Hmm, I can reproduce it and now that I see it myself I can see how this is a problem with cygdrive mounts. I assume the best way to handle this would be to set Samba drives to noacl by default, right? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: Updated package: brltty 3.10-1
On Jul 18 02:40, Samuel Thibault wrote: Hi, There is a new version 3.10-1 of brltty, please upload http://brl.thefreecat.org/brltty/cygwin/brltty-3.10-1-src.tar.bz2 http://brl.thefreecat.org/brltty/cygwin/brltty-3.10-1.tar.bz2 http://brl.thefreecat.org/brltty/cygwin/setup.hint http://brl.thefreecat.org/brltty/cygwin/libbrlapi-devel/libbrlapi-devel-3.10-1.tar.bz2 http://brl.thefreecat.org/brltty/cygwin/libbrlapi-devel/setup.hint http://brl.thefreecat.org/brltty/cygwin/libbrlapi/libbrlapi-3.10-1.tar.bz2 http://brl.thefreecat.org/brltty/cygwin/libbrlapi/setup.hint http://brl.thefreecat.org/brltty/cygwin/python-brlapi/python-brlapi-3.10-1.tar.bz2 http://brl.thefreecat.org/brltty/cygwin/python-brlapi/setup.hint http://brl.thefreecat.org/brltty/cygwin/tcl-brlapi/tcl-brlapi-3.10-1.tar.bz2 http://brl.thefreecat.org/brltty/cygwin/tcl-brlapi/setup.hint http://brl.thefreecat.org/brltty/cygwin/xbrlapi/xbrlapi-3.10-1.tar.bz2 http://brl.thefreecat.org/brltty/cygwin/xbrlapi/setup.hint Uploaded. and only keep version 3.9-1 as old. Done. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: New Cygwin 1.7.0-18 in release-2
On Jul 18 09:54, Corinna Vinschen wrote: On Jul 18 09:34, Corinna Vinschen wrote: On Jul 17 18:18, Eric Blake wrote: Somewhere between setting obcaseinsensitive to 0 yesterday and upgrading to the new cygwin1.dll today, I'm now suffering from an inability to modify files on a shared drive on my work machine. I can create empty files and remove existing files just fine, but get access denied on any attempt to change contents. The -1 for owner and group looks fishy as well. Drive U is apparently a Samba drive. Is that in a Windows domain? If not, try the noacl mount option. It's equivalent to what was CYGWIN=nosmbntsec before. Hmm, I can reproduce it and now that I see it myself I can see how this is a problem with cygdrive mounts. I assume the best way to handle this would be to set Samba drives to noacl by default, right? OTOH, I can't choose different mount options for different per cygdrive mounted drives. All cydrives share the same options. How should we solve that? I hope that doesn't mean we still need the global (no)smbntsec option... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: New Cygwin 1.7.0-18 in release-2
On Jul 18 10:09, Corinna Vinschen wrote: On Jul 18 09:54, Corinna Vinschen wrote: On Jul 18 09:34, Corinna Vinschen wrote: On Jul 17 18:18, Eric Blake wrote: Somewhere between setting obcaseinsensitive to 0 yesterday and upgrading to the new cygwin1.dll today, I'm now suffering from an inability to modify files on a shared drive on my work machine. I can create empty files and remove existing files just fine, but get access denied on any attempt to change contents. The -1 for owner and group looks fishy as well. Drive U is apparently a Samba drive. Is that in a Windows domain? If not, try the noacl mount option. It's equivalent to what was CYGWIN=nosmbntsec before. Hmm, I can reproduce it and now that I see it myself I can see how this is a problem with cygdrive mounts. I assume the best way to handle this would be to set Samba drives to noacl by default, right? OTOH, I can't choose different mount options for different per cygdrive mounted drives. All cydrives share the same options. How should we solve that? I hope that doesn't mean we still need the global (no)smbntsec option... For a start, I don't think we have to go back to smbntsec. The real problem is exactly what I describe in the comment in fhandler_base::open(). Apparently, creating the file and sending the security descriptor to the server is a two step approach. So Samba creates the file first, and then, afterwards, Windows sends the request to change the security descriptor of the file. Now Samba can't map SID-uid and returns STATUS_ACCESS_DENIED. But there seems to be no knowledge that the two actions are actually one system call in Windows. So Samba doesn't remove the file, but still, NtCreateFile failed. Bummer. I have a local workaround which I'll apply in a minute. However, I never really understood why the mapping from the Windows SID to the UNIX user fails, even though the user has been successfully authenticated before. I have written a clueless mail to the samba developers list. Maybe they can enlighten me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: New Cygwin 1.7.0-18 in release-2
--- Corinna Vinschen ha scritto: Hi, Hi Corinna, Download a 1.7 distro using http://cygwin.com/setup-1.7.exe Is it still unable to handle empty tarball ? Bye Marco Posta, news, sport, oroscopo: tutto in una sola pagina. Crea l#39;home page che piace a te! www.yahoo.it/latuapagina
Re: New Cygwin 1.7.0-18 in release-2
On Jul 18 18:36, Marco Atzeri wrote: --- Corinna Vinschen ha scritto: Download a 1.7 distro using http://cygwin.com/setup-1.7.exe Is it still unable to handle empty tarball ? ... of a certain type, yes, unfortunately. Fortunately it doesn't stop the whole setup process, it just prints an error message and asks for user input. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: New Cygwin 1.7.0-18 in release-2
On Fri, Jul 18, 2008 at 07:10:10PM +0200, Corinna Vinschen wrote: On Jul 18 18:36, Marco Atzeri wrote: --- Corinna Vinschen ha scritto: Download a 1.7 distro using http://cygwin.com/setup-1.7.exe Is it still unable to handle empty tarball ? ... of a certain type, yes, unfortunately. Fortunately it doesn't stop the whole setup process, it just prints an error message and asks for user input. Actually I don't think it can handle any type of empty tarball can it? I created them with tar -T /dev/null -cjf foo.tar.bz2 but I think setup.exe still complains about those type of tar files. cgf
Re: New Cygwin 1.7.0-18 in release-2
On Jul 18 13:56, Christopher Faylor wrote: On Fri, Jul 18, 2008 at 07:10:10PM +0200, Corinna Vinschen wrote: On Jul 18 18:36, Marco Atzeri wrote: Is it still unable to handle empty tarball ? ... of a certain type, yes, unfortunately. Fortunately it doesn't stop the whole setup process, it just prints an error message and asks for user input. Actually I don't think it can handle any type of empty tarball can it? I don't know. I thought it handles one type and complains about the other. I didn't actually test it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: New Cygwin 1.7.0-18 in release-2
Corinna Vinschen wrote: Download a 1.7 distro using http://cygwin.com/setup-1.7.exe Cygwin 1.7 and 1.5 can run in parallel sessions on the same machine, but the installation in parallel needs some manual intervention. Setup.exe is not yet using the new registry location and will happily install into your 1.5 installation dir... Are there any instructions on exactly how to do this? I tried to install both of them on my machine. I told setup-1.7 to install into a separate directory, however, all of the other registry stuff that keeps track of what is installed seems to be used as well. So, it installed some stuff, but not everything. The resulting install could not run programs because of missing dll's. Thanks. -Bill
Re: New Cygwin 1.7.0-18 in release-2
Corinna Vinschen wrote: Actually I don't think it can handle any type of empty tarball can it? I don't know. I thought it handles one type and complains about the other. I didn't actually test it. It can handle the type created by bzip2 /dev/null but not the tar -T /dev/null type. I haven't had time to fix that yet, and I apologize for letting setup remain in this state for so long. However, aside from having to dismiss a popup it should be inconsequential -- the resulting installation is not affected. Brian
