cygwin/xemacs marking a buffer as read-only
I am changing the subject here because this problem is cygwin/xemacs-specific only, so it has nothing to do with smb permissions because I can touch and edit the same file with nano and save properly. Same with vi. It's entirely xemacs. I've attached my config, per request. -Original Message- From: Igor Peshansky [ mailto:[EMAIL PROTECTED] Sent: Wednesday, September 05, 2007 7:20 PM To: Joseph Koenig Cc: cygwin@cygwin.com Subject: Re: Passing domain credentials for a non-domain machine (similar to mapping drives through the Windows shell) On Wed, 5 Sep 2007, Joseph Koenig wrote: I have a desktop that I use to access a share with domain credentials despite not being on domain. So when I map a drive, I map it under domain\user and give it the password. This drive is mapped as Z. When I use cygwin to work on those files, it does not inherit the permissions that I mapped the network drive under and instead insists on using my local windows user and password (generated with mkpasswd) rather than what I mapped Z as. You want to add smbntsec to your CYGWIN environment variable. See http://cygwin.com/cygwin-ug-net/using-cygwinenv.html for details. Is there an easy way to manually edit the /etc/passwd file or change how cygwin reads the mapped volume to get it to use the same permissions that the windows shell is using? You'll also want to use mkpasswd -d /etc/passwd to get domain user information into it, and possibly mkgroup -d /etc/group (notice the double to append). (I searched the archives for thisI'm sure it's been answered but I couldn't find anything - I apologize) It also helps to read and follow Problem reports: http://cygwin.com/problems.html in particular the bit about attaching the output of cygcheck -svr. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Belief can be manipulated. Only knowledge is dangerous. -- Frank Herbert -- 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/
xemacs marking a buffer as read-only
I am changing the subject here because this problem is cygwin/xemacs-specific only, so it has nothing to do with smb permissions because I can touch and edit the same file with nano and save properly. Same with vi. It's entirely xemacs. I've attached my config, per request. -Original Message- From: Igor Peshansky [ mailto:[EMAIL PROTECTED] Sent: Wednesday, September 05, 2007 7:20 PM To: Joseph Koenig Cc: cygwin@cygwin.com Subject: Re: Passing domain credentials for a non-domain machine (similar to mapping drives through the Windows shell) On Wed, 5 Sep 2007, Joseph Koenig wrote: I have a desktop that I use to access a share with domain credentials despite not being on domain. So when I map a drive, I map it under domain\user and give it the password. This drive is mapped as Z. When I use cygwin to work on those files, it does not inherit the permissions that I mapped the network drive under and instead insists on using my local windows user and password (generated with mkpasswd) rather than what I mapped Z as. You want to add smbntsec to your CYGWIN environment variable. See http://cygwin.com/cygwin-ug-net/using-cygwinenv.html for details. Is there an easy way to manually edit the /etc/passwd file or change how cygwin reads the mapped volume to get it to use the same permissions that the windows shell is using? You'll also want to use mkpasswd -d /etc/passwd to get domain user information into it, and possibly mkgroup -d /etc/group (notice the double to append). (I searched the archives for thisI'm sure it's been answered but I couldn't find anything - I apologize) It also helps to read and follow Problem reports: http://cygwin.com/problems.html in particular the bit about attaching the output of cygcheck -svr. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Belief can be manipulated. Only knowledge is dangerous. -- Frank Herbert -- 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/
Passing domain credentials for a non-domain machine (similar to mapping drives through the Windows shell)
I have a desktop that I use to access a share with domain credentials despite not being on domain. So when I map a drive, I map it under domain\user and give it the password. This drive is mapped as Z. When I use cygwin to work on those files, it does not inherit the permissions that I mapped the network drive under and instead insists on using my local windows user and password (generated with mkpasswd) rather than what I mapped Z as. Is there an easy way to manually edit the /etc/passwd file or change how cygwin reads the mapped volume to get it to use the same permissions that the windows shell is using? (I searched the archives for thisI'm sure it's been answered but I couldn't find anything - I apologize) -j -- 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: cygheap base mismatch detected - only on Vista x64, not seen on Vista x86
Congrats on figuring the problem out so quickly. Forgive my lack of familiarity with the cygwin development process (and cygwin in general), but as you've seemingly isolated root cause, do you feel that a point fix should be forthcoming shortly or do you feel as though this problem might persist for some time? Also, do you believe that fixing this problem in the cygwin dll will solve the extent of vista incompatibilities or do you think that Vista64 functionality is going to require additional fixes? Yes, it's sort of a request to speculate a bit, but I'm trying to ascertain whether I should continue my little project on Vista32 for a short while until a Vista64 fix or if I should abandon my project that triggered this bug in the first place. Regards, Joe -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] dot com] On Behalf Of Corinna Vinschen Sent: Wednesday, November 22, 2006 5:04 AM To: cygwin@cygwin.com Subject: Re: cygheap base mismatch detected - only on Vista x64, not seen on Vista x86 On Nov 17 18:29, Joseph Koenig wrote: DISCLAIMER: Yes, I realize Vista is not officially supported. If anything I hope this e-mail will end up in the archives to prevent other uses who see this same problem from wasting time if there is no war available. I have successfully used cygwin on Vista32 with no problems. On Vista64 I can complete the install but I have errors when I try to execute basic commands, such as ls. This is with Vista RTM. Some useful info: The error message:: I actually receive this several times at various entry points to main, but I'll just paste it once: bash-3.2$ ls 5 [main] ? (1376) D:\cygwin\bin\bash.exe: *** fatal error - cygheap base m ismatch detected - 0x0/0x611828F0. This problem is probably due to using incompatible versions of the cygwin DLL. Search for cygwin1.dll using the Windows Start-Find/Search facility and delete all but the most recent version. The most recent version *should* reside in x:\cygwin\bin, where 'x' is the drive on which you have installed the cygwin distribution. Rebooting is also suggested if you are unable to find another cygwin DLL. 3 [main] bash 2032 fork: child -1 - died waiting for longjmp before initia lization, retry 0, exit code 0x100, errno 11 bash: fork: Resource temporarily unavailable I have mixed news on this issue. The good news is, it's quite easy to reproduce since it occurs all the time, so I started to debug this. The bad news is that I have no idea why happens what happens. What happens is this: Basically, when forking a process Cygwin calls CreateProcess, starting the current application another time and then parent and child fiddle with the shared handles and memory to give the child an up-to-date, forked-like outfit. This however requires a way to propagate information to the child process which allows the child to do certain actions at a very early stage of initialization. The way to do this is to utilize the STARTUPINFO given to the CreateProcess call. One parameter in there is called lpReserved2, which is, for instance, also used by the MSVCRT C runtime library to propagte information to child processes. Well, we are our own C runtime. Cygwin processes are not linked against MSVCRT for that reason, so it's safe to use lpReserved2 for our own, dubious purposes. The child calls the GetStartupInfo function and gets all information needed. Not so under Vista x64. The child calls GetStartupInfo and gets a valid result, with an apparently also valid lpReserved2 pointer. At least the pointer points to something valid within the child's address space. Unfortunately, what it points to is only filled with zeros. The information expected at this point is just not there anymore. This in turn leads to the above result. So far I know that it has nothing to do with being started by a 64 bit process and I also know that this is not a generic problem with the lpReserved2 member in Vista WOW64 processes. as a simple testcase(tm) showed. So, as for the why... I'm quite puzzeled. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- 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/
cygheap base mismatch detected - only on Vista x64, not seen on Vista x86
DISCLAIMER: Yes, I realize Vista is not officially supported. If anything I hope this e-mail will end up in the archives to prevent other uses who see this same problem from wasting time if there is no war available. I have successfully used cygwin on Vista32 with no problems. On Vista64 I can complete the install but I have errors when I try to execute basic commands, such as ls. This is with Vista RTM. Some useful info: The error message:: I actually receive this several times at various entry points to main, but I'll just paste it once: bash-3.2$ ls 5 [main] ? (1376) D:\cygwin\bin\bash.exe: *** fatal error - cygheap base m ismatch detected - 0x0/0x611828F0. This problem is probably due to using incompatible versions of the cygwin DLL. Search for cygwin1.dll using the Windows Start-Find/Search facility and delete all but the most recent version. The most recent version *should* reside in x:\cygwin\bin, where 'x' is the drive on which you have installed the cygwin distribution. Rebooting is also suggested if you are unable to find another cygwin DLL. 3 [main] bash 2032 fork: child -1 - died waiting for longjmp before initia lization, retry 0, exit code 0x100, errno 11 bash: fork: Resource temporarily unavailable Some cygcheck: D:\cygwin\bincygcheck -s -v Cygwin Configuration Diagnostics Current System Time: Fri Nov 17 18:21:49 2006 Windows Longhorn/Vista (not yet supported!) Ver 6.0 Build 6000 Running under WOW64 on AMD64 Path: C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem 'id' program not found 'id' program not found SysDir: C:\Windows\system32 WinDir: C:\Windows Path = 'C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem' ALLUSERSPROFILE = 'C:\ProgramData' APPDATA = 'C:\Users\SVT\AppData\Roaming' CommonProgramFiles = 'C:\Program Files (x86)\Common Files' CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files' CommonProgramW6432 = 'C:\Program Files\Common Files' COMPUTERNAME = 'SVT-101' ComSpec = 'C:\Windows\system32\cmd.exe' FP_NO_HOST_CHECK = 'NO' HOMEDRIVE = 'C:' HOMEPATH = '\Users\SVT' LOCALAPPDATA = 'C:\Users\SVT\AppData\Local' LOGONSERVER = '\\SVT-101' NUMBER_OF_PROCESSORS = '2' OS = 'Windows_NT' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' PROCESSOR_ARCHITECTURE = 'x86' PROCESSOR_ARCHITEW6432 = 'AMD64' PROCESSOR_IDENTIFIER = 'EM64T Family 6 Model 15 Stepping 6, GenuineIntel' PROCESSOR_LEVEL = '6' PROCESSOR_REVISION = '0f06' ProgramData = 'C:\ProgramData' ProgramFiles = 'C:\Program Files (x86)' ProgramFiles(x86) = 'C:\Program Files (x86)' ProgramW6432 = 'C:\Program Files' PROMPT = '$P$G' PUBLIC = 'C:\Users\Public' SESSIONNAME = 'Console' SystemDrive = 'C:' SystemRoot = 'C:\Windows' TEMP = 'C:\Users\SVT\AppData\Local\Temp' TMP = 'C:\Users\SVT\AppData\Local\Temp' USERDOMAIN = 'SVT-101' USERNAME = 'SVT' USERPROFILE = 'C:\Users\SVT' windir = 'C:\Windows' POSIXLY_CORRECT = '1' Use '-r' to scan registry c: hd NTFS 1Mb 71% CP CS UN PA FC d: hd NTFS 37174Mb 1% CP CS UN PA FC e: cd N/AN/A D:\cygwin / system binmode D:\cygwin/bin /usr/bin system binmode D:\cygwin/lib /usr/lib system binmode . /cygdrive system binmode,cygdrive Not Found: awk Not Found: bash Not Found: cat Not Found: cp Not Found: cpp (good!) Not Found: crontab Not Found: find Not Found: gcc Not Found: gdb Not Found: grep Not Found: kill Not Found: ld Not Found: ls Not Found: make Not Found: mv Not Found: patch Not Found: perl Not Found: rm Not Found: sed Not Found: ssh Not Found: sh Not Found: tar Not Found: test Not Found: vi Not Found: vim 61k 2006/11/10 D:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0 cygbz2-1.dll v0.0 ts=2006/11/10 15:42 7k 2006/10/22 D:\cygwin\bin\cygcharset-1.dll - os=4.0 img=1.0 sys=4.0 cygcharset-1.dll v0.0 ts=2006/10/22 16:43 7k 2003/10/19 D:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0 cygcrypt-0.dll v0.0 ts=2003/10/19 0:57 1125k 2006/10/04 D:\cygwin\bin\cygcrypto-0.9.7.dll - os=4.0 img=1.0 sys=4.0 cygcrypto-0.9.7.dll v0.0 ts=2006/10/4 5:12 1053k 2006/10/04 D:\cygwin\bin\cygcrypto-0.9.8.dll - os=4.0 img=1.0 sys=4.0 cygcrypto-0.9.8.dll v0.0 ts=2006/10/4 5:45 40k 2006/11/15 D:\cygwin\bin\cygform-8.dll - os=4.0 img=1.0 sys=4.0 cygform-8.dll v0.0 ts=2006/11/14 23:06 45k 2001/04/25 D:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0 cygform5.dll v0.0 ts=2001/4/24 22:28 35k 2002/01/09 D:\cygwin\bin\cygform6.dll - os=4.0 img=1.0 sys=4.0 cygform6.dll v0.0 ts=2002/1/8 22:03 48k 2003/08/09 D:\cygwin\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0 cygform7.dll v0.0 ts=2003/8/9 2:25 28k 2003/07/20 D:\cygwin\bin\cyggdbm-3.dll - os=4.0 img=1.0 sys=4.0 cyggdbm-3.dll v0.0 ts=2003/7/20 0:58 30k 2003/08/11 D:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0
