WLMP cannot map to parent and Rebaseall fails for unknown reason.
Hi all, I am trying to get my version of Cygwin to play nicely with WLMP[1] which installs it's own version of some key cygwin dlls locally. When I launch the WLMP version of lightty, I get the classic 'Unable to Remap' error [2]. This is usually solved by a quick trip to rebaseall, so I tried: $ ./rebaseall -v -T `./find /cygdrive/c/WLMP/LightTPD/ -iname '*dll' rebaseall: '/cygdrive/c/WLMP/LightTPD/CygBZ2-1.dll' is not readable $ ./cat /cygdrive/c/WLMP/LightTPD/CygBZ2-1.dll BINARY JUNK The file is, in fact, readable. I can 'cat' it from the ash command line right there. Heck, I can even write to it. NTFS file permissions are set to 'Full Control' for the user running ./rebaseall. No other files have it open (per process explorer). So why in blazes does rebaseall think that it's not readable?! Oren PS. I know that WLMP is not Cygwin's problem. I was merely hoping that some kind soul would point me in the right direction to rebasing all my DLLs for a happy cygwin + WLMP family. [1] http://en.wlmp-project.net/ -- unfortunately the build of lightty that comes with Cygwin doesn't have SSL baked in, nor is there a PHP/MySQL stack. [2] 35 [main] LightTPD 4604 C:\WLMP\LightTPD\LightTPD.exe: *** fatal error - unable to remap C:\WLMP\LightTPD\cygminires.dll to same address as parent (0x33) != 0x6EFC -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Status of Compatibility with Windows Server 2008 (2k8)
Hello, I am considering upgrading my 2k3 installation to 2k8. I currently use cygwin for basic utilities: mainly lighthttpd, sshd and rsync (and the relative pleasure of using bash instead of cmd). Could someone on this list give me an idea of what kind of issues to expect in the transition? I read through the archives and there are a few issues but those seem to be dated from 2007 and earlier. -Oren PS. The compiled answer could perhaps go into the FAQ for future use. Keywords: Windows Server 2008, Windows Server 2k8 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Status of Compatibility with Windows Server 2008 (2k8)
Perhaps it's bad form to reply to my own message, but I've got the 2k8 installation (x86) up and running and I'm ready to take the plunge and report back on what works and what doesn't work. Should I use the 1.5 release on the main page, or use the 1.7 release (setup-1.7.exe)? Alternatively, should I not even bother because it is known that Win2k8 and Cygwin just don't play well together? ~Oren PS. If the lack of reply to my previous question was due to some failure on my part, I'm quite sorry. I did check the FAQ and the archives of this list for any information in Cygwin's relationship with Win2k8. Google was also rather unhelpful in finding up-to-date information. On Thu, Jan 22, 2009 at 10:16 AM, Oren Elrad orenel...@gmail.com wrote: Hello, I am considering upgrading my 2k3 installation to 2k8. I currently use cygwin for basic utilities: mainly lighthttpd, sshd and rsync (and the relative pleasure of using bash instead of cmd). Could someone on this list give me an idea of what kind of issues to expect in the transition? I read through the archives and there are a few issues but those seem to be dated from 2007 and earlier. -Oren PS. The compiled answer could perhaps go into the FAQ for future use. Keywords: Windows Server 2008, Windows Server 2k8 -- Oren The avoidance of taxes is the only intellectual pursuit that carries any reward. ~John Maynard Keynes Violence can only be concealed by a lie, and the lie can only be maintained by violence. Any man who has once proclaimed violence as his method is inevitably forced to take the lie as his principle. ~Alexander Solzhenitsyn Among the many misdeeds of the British rule in India, history will look upon the act depriving a whole nation of arms as the blackest. ~Mohandas Gandhi We will bankrupt ourselves in the vain search for absolute security. ~Dwight D. Eisenhower -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Proper Windows Permissions for SFTP Users
Hi, Running WinXP Pro, local users only and I find that only admin users can launched an SFTP session (see below for the precise error message). This must be a permissions problem since changing a user to admin allows them to SFTP; change them back to limited and they cannot. I tried the following: (1) Logged on as the user in question, ran cmd (per Cygwin instructions), logged out (2) Set permissions for 'Users' on C:\cygwin and C:\Windows to allow Read and Execute, List Folder Contents and Read recursively (replace all child permissions with these) per recommendation of some other posts on the mailing list. (3) chmod 755 /usr/sbin/* /usr/bin/* (4) Restarted sshd I don't know what other directories I should allow. Any insight would be wonderful. Thanks in advance, Oren Attached: cygcheck.out (produced by cygcheck -s -v -r) Appendix: Error Message Received by non-admin users (snipped) produced with sftp -vv: debug2: we sent a password packet, wait for reply debug1: Authentication succeeded (password). debug2: fd 4 setting O_NONBLOCK debug1: channel 0: new [client-session] debug2: channel 0: send open debug1: Entering interactive session. debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug2: channel 0: request env confirm 0 debug1: Sending subsystem: sftp debug2: channel 0: request subsystem confirm 1 debug2: fd 3 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug2: channel 0: rcvd adjust 2097152 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug2: channel 0: rcvd eof debug2: channel 0: output open - drain debug2: channel 0: obuf empty debug2: channel 0: close_write debug2: channel 0: output drain - closed debug2: channel 0: rcvd close debug2: channel 0: close_read debug2: channel 0: input open - closed debug2: channel 0: almost dead debug2: channel 0: gc: notify user debug2: channel 0: gc: user detached debug2: channel 0: send close debug2: channel 0: is dead debug2: channel 0: garbage collecting debug1: channel 0: free: client-session, nchannels 1 debug1: fd 0 clearing O_NONBLOCK debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.3 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 53 Connection closed cygcheck.out Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
