Re: OpenGL or no OpenGL
Alan James Caruana schrieb: I found the features page ( http://x.cygwin.com/features.html ) which says that the Mesa 3D Graphics Library provides software-based OpenGL support, but one item of the To-Do list ( http://x.cygwin.com/devel/todo.html ) states that Indirect OpenGL rendering still needs to be implemented, while Direct Rendering will be considered when the Indirect rendering will be finished. Can anyone clarify this please? This means that all OpenGl rendering is done in Software. Work has been started to use OpenGl hardware acceleration, but it isn't finished. And nobody is working on it, afaik. Direct/indirect rendering refers to where the server is running, on the same computer than the program that uses OpenGl (direct access to hardware) or with a network between them (indirect access to hardware). -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: svn on cygwin related problem.
Hello, I think I spotted a bug which happen on the subversion package provided for cygwin. I encountered the following problem while exporting the content of my Subversion repository. In the repository, I have a directory T which contains another file called X.exe and a directory called X. When I export the content of the whole repository (svn export --force svn://localhost/trunk/PathToDirectoryT), the follwoing happens: -the X.exe file gets exported correctly; -when the the X directory would get exported, svn outputs the following error: svn: 'X' exists and is not a directory It does not happen if I manually export first the X directory, and then the X.exe file, like: svn export --force svn://localhost/trunk/PathToT/X svn export --force svn://localhost/trunk/PathToT/X.exe but the error happens if I export the X.exe file before the directory, i.e.: svn export --force svn://localhost/trunk/PathToT/X.exe svn export --force svn://localhost/trunk/PathToT/X svn: 'Programmer' exists and is not a directory which is the sequence of operations when the whole repository is exported. Is this a bug? I am using Windows XP Professional, NTFS fs in both the server and the client computers. A useful link for the confirmation that it is a bug on the [EMAIL PROTECTED] mailing list: http://subversion.tigris.org/servlets/ReadMsg?list=usersmsgNo=61651 or http://svn.haxx.se/users/archive-2007-02/0194.shtml O.S. : Windows XP SP2, NTFS filesystem Subversion: svn --version reports svn, version 1.4.2 (r22196) compiled Dec 2 2006, 14:28:55 Cygwin: Subversion package up to date to 31/1/2007. Greetings, Luca -- 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/
pthread_cond_timedwait
Hi, I have tried to use the pthread_cond_timedwait, but it doesn't seem to work properly. It returns immediately with a return value of 116 (ETIMEDOUT) even if I set the timeout period to e.g. 10 seconds. I have locked the mutex and initialized the condition variable before the invokation is made. What is wrong? The cygwin version was downloaded and installed 2006/12/14 and the posix library date is 10.02.2006 03:50. Best regards Ingvill -- 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: strange bug in gettimeofday function
On Mon, Feb 12, 2007 at 11:00:38AM +0800, Carlo Florendo wrote: Andrew Makhorin wrote: Hi, I detected a strange bug in the standard function gettimeofday. It *sometimes* reports the time which being expressed as the integer number of milliseconds is *less* than the time obtained *earlier* with the same function. If you mean that you call gettimeofday twice and you get different values at each call, with a difference of about 100 ms, then this is all right. Read on... As the author of the function in question, I would still like to get a test case. -- 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: Probllem with New GDB/Eclipse
On Mon, Feb 12, 2007 at 06:53:35AM +, Charles Tubbs wrote: Brian Dessent brian at dessent.net writes: Doyle Rhynard wrote: When others depend upon what you do, the old maximum for physicians should apply also: First, do no harm. My suggestion is to roll back That logic would only apply if the Eclipse module was an actual Cygwin package, but it's not. Fixing packages of 3PPs is not our job, it's theirs. Obviously the CDT developers erred by choosing to use a well defined package that inexplicably changes in the undefined areas. You are a very good advertisement for Visual Studio. You do realize that this thread is more than six months old, right? cgf -- 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/
[ANNOUNCEMENT] EOL for Windows 95/86/Me
I'm not sure if it has reached the consciousness of the general Cygwin user base yet but I wanted to make sure that everyone was aware of the fact that we will be ripping out support for Windows 95, Windows 98, and Windows Me in the next version of Cygwin, which will be version 1.7.0. This has been announced on our web site (http://cygwin.com) for a couple of weeks, has been discussed in the cygwin-developers mailing list (http://cygwin.com/ml/cygwin-developers) for six months or so, and has been discussed between Corinna (corinna) and me (cgf) for longer than that. I hope that the reason to drop the support is fairly obvious. If it isn't feel free to respond to this message in the cygwin mailing list. So, barring any catastrophic problems with the current released version of the Cygwin DLL, the last Cygwin version with support for non-Windows-NT class versions of Windows will be 1.5.24-2. We're not against someone stepping up to continue to support the 1.5.x series in a separate CVS branch, if there is still interest in this. We can provide this person with checkin privileges to the cygwin source control and we'd expect that this person would make periodic releases of the old 1.5.24 version. Barring that however, it's so long Windows 9x. FYI, cgf * *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL and you WILL be able to unsubscribe. * -- 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: Help. Cygwin corrupting files
Frodak wrote: Back up your stuff. This happened to me before days before ntfs.sys deleted itself. I then asked my boss for a new hard-drive and then did a fresh windows install. I had bizarre issues. Amongst what you described that happened for a while, the following occurred and increased in occurrence: 1) DR Watson kept on popping up sometimes when running make. Then it seemed to pop up randomly. It neve did report what crashed, only that something had crashed. 2) The environment would never be stable. I'd open up cmd.exe (10 times in a row) and sometimes the PATH settings would be correct, otherwise it would be truncated. Good Luck, Frodak Thanks. I'm not experiencing any issues with Windows though. DOS prompt works. GUI works. No issues at all. It's only when I'm in cygwin that anything bizarre starts happening. -- 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: Help. Cygwin corrupting files
Andrew DeFaria wrote: Chuck wrote: At first I thought my recent problems with cygwin were limited to the occasional ls command listing nothing. Run it again an it works (usually). Now the problems are getting worse. I tried to rm a file that I own and it didn't fully delete it. It corrupted it. An ls of the file shows this (that is, when the ls command works). $ ls -l ls: cannot access bin_dirs.txt: No such file or directory total 14 drwxr-xr-x+ 2 CHamilto Domain Users 0 Feb 9 14:50 ./ drwxr-xr-x+ 19 CHamilto Domain Users 0 Feb 9 14:33 ../ -rw-r--r-- 1 CHamilto Domain Users 3196 Feb 9 14:48 all_bin_dirs.txt ??? ? ? ? ? ? bin_dirs.txt -rwx-- 1 CHamilto Domain Users 368 Feb 9 14:33 chuck.sh* -rwxrwx--- 1 CHamilto Domain Users 3069 Feb 9 11:06 cleanup_rman.sh* -rw-r--r-- 1 CHamilto Domain Users 1491 Feb 9 14:08 servers -rwxrwx--- 1 CHamilto Domain Users 270 Feb 9 14:50 upload.sh* What is up with that? I can't access or remove the bin_dirs.txt file now with either cygwin or windows. I tried resetting the owner but chown fails too. $ chown CHamilto:Domain Users bin_dirs.txt chown: cannot access `bin_dirs.txt': No such file or directory I have tried reinstalling cygwin and coreutils to no avail. Did something happen in a recent release of cygwin to explain this bizarre behavior? I've been using cygwin for years and never experienced anything like this. Please help! When I've seen this problem before (ls complaining file doesn't exist) it is usually because some other process has the file handle still open. Go to sysinternals.com and download and run Process Explorer. It has a facility to search for handles by strings. Search for bin_dirs.txt and find which process has that file open and either close the file handle or kill the process. Return the bash shell and repeat the ls. You should see no problem anymore. It's not just *a* file. I'm trying to ls entire directories. Sometimes I get nothing listed. Sometimes I get all the files listed. Sometimes I get some of them. One strange thing is that I never see the last line of output showing a partially filled line. It's always a complete line which makes me think that maybe its the writing to stdout that's failing. -- 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: Help. Cygwin corrupting files
Larry Hall (Cygwin) wrote: Chuck wrote: Larry Hall (Cygwin) wrote: Chuck wrote: snip HD scan shows no errors. snip I'm beginning to think I need to remove and reinstall every cygwin package, but I'm not certain that will fix it either. I've already reinstalled both coreutils and cygwin itself. I've even tried rolling both back a few releases, but I get the same problem. This is very strange. Look for the usual suspects of problem software - firewalls, virus checkers, spyware/anti-spyware. Nothing has changed. I did a virus scan and spyware scan too. The virus scan was completely clearn. The spyware scan picked up the usual tracking cookies but nothing really bad. The only other thing I can think of that's new is that Daemontools virtual cd drive software. I've since removed it but it has not cleared up the problem. -- 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: [ANNOUNCEMENT] Updated:lftp-3.5.9-1
lftp ftp.microsoft.com lftp: host name resolve timeout I'm not able to reproduce this problem: $ lftp ftp.microsoft.com lftp ftp.microsoft.com:~ ls dr-xr-xr-x 1 ownergroup 0 Jan 25 11:03 bussys dr-xr-xr-x 1 ownergroup 0 Jan 25 11:18 deskapps dr-xr-xr-x 1 ownergroup 0 Jan 25 11:22 developr dr-xr-xr-x 1 ownergroup 0 Jan 25 11:22 KBHelp dr-xr-xr-x 1 ownergroup 0 Jan 25 11:38 MISC dr-xr-xr-x 1 ownergroup 0 Jan 25 11:43 MISC1 dr-xr-xr-x 1 ownergroup 0 Jan 25 11:45 peropsys dr-xr-xr-x 1 ownergroup 0 Jan 25 11:52 Products dr-xr-xr-x 1 ownergroup 0 Jan 25 11:52 PSS dr-xr-xr-x 1 ownergroup 0 Jan 25 11:53 ResKit dr-xr-xr-x 1 ownergroup 0 Jan 25 12:11 Services dr-xr-xr-x 1 ownergroup 0 Jan 25 17:38 Softlib lftp ftp.microsoft.com:/ exit $ lftp --version LFTP | Version 3.5.9 | Copyright (c) 1996-2006 Alexander V. Lukyanov snip Libraries used: Readline 5.2, Expat 1.95.8, OpenSSL 0.9.8d 28 Sep 2006, libiconv 1.11 --- I'm glad to help troubleshoot, but I probably can't do much until or unless I can observe the problem. Please attach output of cygcheck -svr. Does 'nslookup ftp.microsoft.com' work for you? Andrew. -- 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: Help. Cygwin corrupting files
Chuck wrote: Andrew DeFaria wrote: Chuck wrote: At first I thought my recent problems with cygwin were limited to the occasional ls command listing nothing. Run it again an it works (usually). Now the problems are getting worse. I tried to rm a file that I own and it didn't fully delete it. It corrupted it. An ls of the file shows this (that is, when the ls command works). $ ls -l ls: cannot access bin_dirs.txt: No such file or directory total 14 drwxr-xr-x+ 2 CHamilto Domain Users 0 Feb 9 14:50 ./ drwxr-xr-x+ 19 CHamilto Domain Users 0 Feb 9 14:33 ../ -rw-r--r-- 1 CHamilto Domain Users 3196 Feb 9 14:48 all_bin_dirs.txt ??? ? ? ? ? ? bin_dirs.txt -rwx-- 1 CHamilto Domain Users 368 Feb 9 14:33 chuck.sh* -rwxrwx--- 1 CHamilto Domain Users 3069 Feb 9 11:06 cleanup_rman.sh* -rw-r--r-- 1 CHamilto Domain Users 1491 Feb 9 14:08 servers -rwxrwx--- 1 CHamilto Domain Users 270 Feb 9 14:50 upload.sh* What is up with that? I can't access or remove the bin_dirs.txt file now with either cygwin or windows. I tried resetting the owner but chown fails too. $ chown CHamilto:Domain Users bin_dirs.txt chown: cannot access `bin_dirs.txt': No such file or directory I have tried reinstalling cygwin and coreutils to no avail. Did something happen in a recent release of cygwin to explain this bizarre behavior? I've been using cygwin for years and never experienced anything like this. Please help! When I've seen this problem before (ls complaining file doesn't exist) it is usually because some other process has the file handle still open. Go to sysinternals.com and download and run Process Explorer. It has a facility to search for handles by strings. Search for bin_dirs.txt and find which process has that file open and either close the file handle or kill the process. Return the bash shell and repeat the ls. You should see no problem anymore. It's not just *a* file. I'm trying to ls entire directories. Sometimes I get nothing listed. Sometimes I get all the files listed. Sometimes I get some of them. One strange thing is that I never see the last line of output showing a partially filled line. It's always a complete line which makes me think that maybe its the writing to stdout that's failing. At this point I'd suggest SpinRite: http://www.grc.com/sr/spinrite.htm -- Andrew DeFaria http://defaria.com One reason most people play golf is to wear clothes they wouldn't be caught dead in otherwise. -- 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/
tar --exclude not working
Experts, I'm using tar (GNU tar) 1.16.1 and have an archive with the following entries. Files/report1.html Files/report2.html Files/report3.html Files/report4.html D:/Bkp/sol/ D:/Bkp/sol/test1.pl D:/Bkp/sol/test2.pl D:/Bkp/sol/test3.pl Whenever, I try to exclude files starting with D:/ its not working as expected. The command used is, tar tf test.tar --anchored --exclude=D:/ and if the command is changed to, tar tf test.tar --anchored --exclude=Bkp then its working fine. It seems the --exclude is not working properly if the pattern starts with windows drive letter. The same thing is working fine for inclusion patterns. tar tf test.tar --anchored D:/ (working fine) Is this a bug? Can it be worked atound? Please throw light on this.. Thanks in Advance, Mohankumar -- 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: strange bug in gettimeofday function
On Mon, 12 Feb 2007, Carlo Florendo wrote: Windows could be accurate up to 15 ms or perhaps a little bit more. However, it is very difficult to achieve less than 15 ms or microsecond accuracy with windows due to the limitation on the OS itself. Our extensive tests on windows clocks and timers reveal that windows cannot be accurate to the microsecond level or below 15 ms. In any case, in my experience, windows cannot be accurate with a precision of up to 15 milliseconds. I'm sorry, could you repeat that value one more time, just in case someone missed it ;-). Anyway, I don't think it is relevant to the original thread's question, but I can assure you that Windows can be used for accurate timings in down to 1 or 2 ms (depending on the OS version). I'm not exactly sure what your definition of accurate is. And, for the OP, I haven't ever seen this behavior from gettimeofday. -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... -- 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: Help. Cygwin corrupting files
Andrew DeFaria wrote: which makes me think that maybe its the writing to stdout that's failing. At this point I'd suggest SpinRite: http://www.grc.com/sr/spinrite.htm Haven't tried spinrite yet but I did do a thorough check of the drive using Tuneup Utilities. That's the one that requires exclusive access to the disk, reboots, and runs as the o/s starts to come up. It identifies and fixes bad sectors. It found nothing wrong with the HD. As stated before, I really do *not* believe this is a HD getting ready to fail. If it were I would expect problems in Windows and Cygwin, not just Cygwin. I could be wrong but my suspicion is that Daemon tools' uninstaller left something behind. Something that hooks into the filesystem api. I remember when installing it that it had to reboot *before* installing itself and I think it was adding some sort of virtual device driver or a hook into the Windows filesystem API. After rebooting, it installed itself. I am highly suspicious that whatever it installed during that first reboot is still hanging around and causing problems for cygwin. -- 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: strange bug in gettimeofday function
Andrew Makhorin wrote: I detected a strange bug in the standard function gettimeofday. It *sometimes* reports the time which being expressed as the integer number of milliseconds is *less* than the time obtained *earlier* with the same function. ...how often is often? Also what version of Windows are you running (I'm too lazy to save and re-open your cygcheck, it seems Thunderbird doesn't think it is text)? And for the $64k question, do you use NTP? I have seen this sort of behavior before (on Linux, IIRC, but it might have been Windows): it can be caused by NTP clock slew. -- Matthew Congratulations! You've won a free trip to the future! All you have to do to claim your prize is wait five minutes... -- 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: Help. Cygwin corrupting files
Larry Hall (Cygwin) wrote: Have you checked if you can do similar operations with DOS commands? I believe what you're seeing here is a hardware (probably disk) problem. Years ago I had a failing disk pick off files randomly for a while until the whole thing finally went. Is there a way to run the ls command in debug mode so I can see exactly where it's failing? It might give me some indication of what's going on. TIA -- 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: Help. Cygwin corrupting files
Chuck wrote: Larry Hall (Cygwin) wrote: Have you checked if you can do similar operations with DOS commands? I believe what you're seeing here is a hardware (probably disk) problem. Years ago I had a failing disk pick off files randomly for a while until the whole thing finally went. Is there a way to run the ls command in debug mode so I can see exactly where it's failing? It might give me some indication of what's going on. In Cygwin, there's strace to get a look at the system calls made by Cygwin tools. There's also file and process monitors from sysinternals (now MS) that can provide some insight. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: Help. Cygwin corrupting files
Chuck wrote: Andrew DeFaria wrote: which makes me think that maybe its the writing to stdout that's failing. At this point I'd suggest SpinRite: http://www.grc.com/sr/spinrite.htm Haven't tried spinrite yet but I did do a thorough check of the drive using Tuneup Utilities. That's the one that requires exclusive access to the disk, reboots, and runs as the o/s starts to come up. It identifies and fixes bad sectors. It found nothing wrong with the HD. I cannot speak for Tuneup Utilities however I've heard that SpinRite is better than most out there. As stated before, I really do *not* believe this is a HD getting ready to fail. If it were I would expect problems in Windows and Cygwin, not just Cygwin. And I find it as hard to believe that for some odd reason Cygwin would behave this way just for you. I could be wrong but my suspicion is that Daemon tools' uninstaller left something behind. Something that hooks into the filesystem api. I remember when installing it that it had to reboot *before* installing itself and I think it was adding some sort of virtual device driver or a hook into the Windows filesystem API. After rebooting, it installed itself. I am highly suspicious that whatever it installed during that first reboot is still hanging around and causing problems for cygwin. I have no idea what this Daemon tools thing is. Hooks into the file system. Gee that's beginning to sound like a root-kit! -- Andrew DeFaria http://defaria.com My friend has a baby. I'm writing down all the noises he makes so later I can ask him what he meant. -- Andrew DeFaria http://defaria.com Help! I'm modeming... and I can't hang up!!! -- 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/
cygwin-1.5.24-2: cygpath -w --long-name scrambles non-existing filename
Hi, I experience a problem that has already been reported (and solved) several months before: http://www.cygwin.com/ml/cygwin/2006-07/msg00861.html http://www.cygwin.com/ml/cygwin/2006-07/msg00878.html My output: $ cygpath -v cygpath (cygwin) 1.42 Compiled on Jan 31 2007 $ cygpath -w -l 12345678901234 123456789012 + non printable characters Can you confirm this bug or is my cygwin environment screwed up? best regards, bernhard -- 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: Help. Cygwin corrupting files
Andrew DeFaria wrote: I have no idea what this Daemon tools thing is. Hooks into the file system. Gee that's beginning to sound like a root-kit! Last I checked, it is a program to allow you to mount CD images as real drives. Since it is supposed to make them look real enough to even fool certain copy protection schemes (and since Windows doesn't have built-in iso9660-over-loopback mount support like Linux does), I'm not surprised that it hooks into the file system. Actually, if anything I would be surprised if it could do its thing *without* doing so. A benevolent rootkit, perhaps? -- Matthew Congratulations! You've won a free trip to the future! All you have to do to claim your prize is wait five minutes... -- 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: Help. Cygwin corrupting files
On 2/12/07, Matthew Woehlke wrote: Andrew DeFaria wrote: I have no idea what this Daemon tools thing is. Hooks into the file system. Gee that's beginning to sound like a root-kit! Last I checked, it is a program to allow you to mount CD images as real drives. Since it is supposed to make them look real enough to even fool certain copy protection schemes (and since Windows doesn't have built-in iso9660-over-loopback mount support like Linux does), I'm not surprised that it hooks into the file system. Actually, if anything I would be surprised if it could do its thing *without* doing so. A benevolent rootkit, perhaps? -- Matthew Congratulations! You've won a free trip to the future! All you have to do to claim your prize is wait five minutes... DaemonTools installs a driver that creates a fake SCSI subsystem where your ISOs are mounted. It 'hooks in' just like any other driver. I have no idea what magic it does to do its job though. I have it installed on a few systems that also run cygwin and I have not had the problems being described here. I am not used the latest / greatest DaemonTools however since I am under the impression that it has become adware if you don't buy it. -Jason -- 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: cygwin-1.5.24-2: cygpath -w --long-name scrambles non-existing filename
On Feb 12 17:45, Bernhard Leiner wrote: Hi, I experience a problem that has already been reported (and solved) several months before: http://www.cygwin.com/ml/cygwin/2006-07/msg00861.html http://www.cygwin.com/ml/cygwin/2006-07/msg00878.html My output: $ cygpath -v cygpath (cygwin) 1.42 Compiled on Jan 31 2007 $ cygpath -w -l 12345678901234 123456789012 + non printable characters Can you confirm this bug or is my cygwin environment screwed up? It's a bug which has been fixed already a couple months ago. Cygpath from the developer snapshots won't show this problem. Unfortunately I forgot to merge this patch into the latest 1.5.x releases. As a workaround, always check for existence before calling cygpath this way. 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/
POSIX-Windows conversion for vars other than PATH, etc?
...is there a way to tell Cygwin that variables other than PATH, etc (i.e. arbitrary, user-specified variables) should be converted from POSIX format to Windows format when spawning a non-POSIX application? If not, would it be acceptable to add such a feature if I were to submit a patch for it? -- Matthew Congratulations! You've won a free trip to the future! All you have to do to claim your prize is wait five minutes... -- 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: POSIX-Windows conversion for vars other than PATH, etc?
On Mon, Feb 12, 2007 at 11:38:59AM -0600, Matthew Woehlke wrote: ...is there a way to tell Cygwin that variables other than PATH, etc (i.e. arbitrary, user-specified variables) should be converted from POSIX format to Windows format when spawning a non-POSIX application? If not, would it be acceptable to add such a feature if I were to submit a patch for it? This has come up repeatedly over the years. I'm not a fan of adding a slowdown to an already slow part of cygwin, so, no, I don't think it would be acceptable. cgf -- 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: Help. Cygwin corrupting files
Larry Hall (Cygwin) wrote: Chuck wrote: Larry Hall (Cygwin) wrote: Have you checked if you can do similar operations with DOS commands? I believe what you're seeing here is a hardware (probably disk) problem. Years ago I had a failing disk pick off files randomly for a while until the whole thing finally went. Is there a way to run the ls command in debug mode so I can see exactly where it's failing? It might give me some indication of what's going on. In Cygwin, there's strace to get a look at the system calls made by Cygwin tools. There's also file and process monitors from sysinternals (now MS) that can provide some insight. Thanks. Can you or anyone help debugging the trace output? I ran with strace like this: strace -o ls2.trc -m debug ls -1 I captured output for a failed execution to ls.trc and a succesful one to ls2.trc. ls2.trc contains about 250 lines. ls.trc contains only 1 line [main] ls 1792 set_myself: myself-dwProcessId 1792 The 2nd line in the succesful trace (ls2) is a call to etEnvironmentStrings. Does that mean that's where it's failing when it fails? -- 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: Help. Cygwin corrupting files
Matthew Woehlke wrote: Andrew DeFaria wrote: I have no idea what this Daemon tools thing is. Hooks into the file system. Gee that's beginning to sound like a root-kit! Last I checked, it is a program to allow you to mount CD images as real drives. Since it is supposed to make them look real enough to even fool certain copy protection schemes (and since Windows doesn't have built-in iso9660-over-loopback mount support like Linux does), I'm not surprised that it hooks into the file system. Actually, if anything I would be surprised if it could do its thing *without* doing so. A benevolent rootkit, perhaps? And honestly I only *suspect* it may be the cause. I don't remember exactly when the first time I noticed the problem was but I *think* it was around the time I installed Daemon Tools. Not 100% sure though. I'd buy into the HD-getting-ready-to-fail argument more if I saw weirdness on Windows too, but I don't. At least not yet. Plus scans of the HD with both Tuneup Utilities and Windows itself are not turning anything up. -- 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: POSIX-Windows conversion for vars other than PATH, etc?
Hello, Matthew Woehlke [EMAIL PROTECTED] wrote: ...is there a way to tell Cygwin that variables other than PATH, etc (i.e. arbitrary, user-specified variables) should be converted from POSIX format to Windows format when spawning a non-POSIX application? There is an option in cyg-wrapper.sh [1] to convert some simple environment variables from POSIX to Windows format. NB: the current version of cyg-wrapper.sh calls cygpath with the option -l which is incorrectly handled by the current version of cygpath (I suppose this is tied to the regression discussed today on the list, you can patch my script in the mean time and replace -wl by -w). [1] http://hermitte.free.fr/cygwin/#Win32 HTH, -- Luc Hermitte http://hermitte.free.fr/cygwin/ -- 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: Help. Cygwin corrupting files
DePriest, Jason R. wrote: I am not used the latest / greatest DaemonTools however since I am under the impression that it has become adware if you don't buy it. -Jason It includes adware. You can unselect it in the installer. -- 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: strange bug in gettimeofday function
Andrew Makhorin wrote: Hi, I detected a strange bug in the standard function gettimeofday. It *sometimes* reports the time which being expressed as the integer number of milliseconds is *less* than the time obtained *earlier* with the same function. The expression 100 * tv.tv_sec + tv.tv_usec is calculated in 64-bit arithmetic, so overflow cannot happen. The negative difference in the time values on two successive calls is about 100 milliseconds. Is this a dual-core AMD perchance? There are some high-performance timing instructions that can get off between the two cores. I wouldn't think that gettimeofday would use these, but maybe? Let's see, it looks like the RDTSC instruction, or the Windows QueryPerformanceCounter(). This problem doesn't occur on Intel multi-cores. It is caused by AMD attempting to save power by throttling the cores back separately. You can google for lots of information about the pros/cons of different patches by Microsoft and AMD to resolve the problem. I don't have the cygwin source to check if these are used anywhere. Cary -- 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: Help. Cygwin corrupting files
Chuck wrote: Larry Hall (Cygwin) wrote: Chuck wrote: Larry Hall (Cygwin) wrote: Chuck wrote: snip HD scan shows no errors. snip I'm beginning to think I need to remove and reinstall every cygwin package, but I'm not certain that will fix it either. I've already reinstalled both coreutils and cygwin itself. I've even tried rolling both back a few releases, but I get the same problem. This is very strange. Look for the usual suspects of problem software - firewalls, virus checkers, spyware/anti-spyware. Nothing has changed. I did a virus scan and spyware scan too. The virus scan was completely clearn. The spyware scan picked up the usual tracking cookies but nothing really bad. The only other thing I can think of that's new is that Daemontools virtual cd drive software. I've since removed it but it has not cleared up the problem. Actually, I was suggesting that your firewall, virus checker, and/or spyware software may be interfering. While your symptoms are not typical of these kinds of buggy software, it is a known fact that they can interfere with Cygwin in undesirable ways. To be sure they are not interfering, you must uninstall them. Turning the off is not enough. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: Help. Cygwin corrupting files
Chuck wrote: I'd buy into the HD-getting-ready-to-fail argument more if I saw weirdness on Windows too, but I don't. At least not yet. Plus scans of the HD with both Tuneup Utilities and Windows itself are not turning anything up. WAG but have you looked at the event log? -- Andrew DeFaria http://defaria.com In some cultures what I do would be considered normal. -- 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: Using a DLL built with cygwin in VC++
Papasha wrote: Hello, I'm trying to use a DLL created with cygwin in my VC++ project. First of all, have you read the Cygwin FAQ (specifically, *all* the questions in the Programming FAQ? Read the caveats about linking Cygwin DLLs into VC++ programs. Specifically, Q 16. After you have understood what you're actually trying to do, you may want to try to follow the instructions in Q 16 to generate your .lib and .def files, and then make sure to put in the correct crt hooks, etc. -- 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: ls not showing anything - sometimes
Chuck wrote: $ cd /cygdrive $ ls $ ls -a . .. c g h k s $ ls -a $ ls -a Hmm. Can't replicate this on my system. Nor can I replicate your other report, about corrupted ls output. You should definitely report a problem in the format described by http://cygwin.com/problems.html. Readers can then ask you for followup information as appropriate. -- 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/
Unable to run even simple batch scripts any more
Three of us updated to latest windows cygwin last week, and none can run even simple .sh scripts any more. Prior version was 6 months ago. test 1: y.sh #!/cygdrive/c/cygwin/bin/bash.exe cd ../working pwd results: $ ./y.sh : No such file or directorying(note: directorying should be directory working, but isn't) : command not found (Note: there really is a ../working directory) Test 2: z.sh $ cat z.sh #!/usr/bin/bash.exe cd ../working Results $ ./z.sh : No such file or directorying : command not found Test 3: t.sh $ cat t.sh #!/usr/bin/bash.exe env $ ./t.sh : command not found : command not found Test 4: u.sh $ cat u.sh env [EMAIL PROTECTED] /cygdrive/c/DOCUME~1/dwsimpso/WORKSP~1/sep $ ./u.sh : command not found -- 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: Download Cygwin???
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian D wrote: Hi, ...I live in Fox, Alaska. High-speed internet is not an option at this point. Trying to install Cygwin via the usual setup.exe method fails because my internet connection likes to have problems far too many times during a huge download... Is there any way that I can d/l Cygwin, with the packages that I need, at my workplace, then write a CD-R and take it home for installation??? Comments or advice??? Thanks, Brian Are you using a work computer to download the files? If so then I would be careful but otherwise I see no issue there. Where I work we have a computer that can be used for whatever we please* but that isn't the case everywhere. * Whatever we please as in we can go anywhere and install whatever we want on it. This is not the case for our work computers. Requested installations have to be approved by the IT department with valid business justification. - -- Robert Pendell [EMAIL PROTECTED] Thawte Web of Trust Notary CAcert Assurer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (MingW32) iD8DBQFF0OpnOzNfzNFG1LQRAiDuAKCE0kPB7/RkO+55fSXBR7ALIISnKACfQ7SF /VO2D3zFAm+gw+a4H0b1xL0= =YR8o -END PGP SIGNATURE- -- 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: ls not showing anything - sometimes
One co-worker downloaded the latest Windows cygwin last week. His ls command now consistently does not return anything, regardless of what directory he is in. This is in addition to not being able to run shell scripts any more, either. The other two of us that upgraded last week to the latest Windows cygwin do NOT have this ls problem. ls works fine. -- 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: Unable to run even simple batch scripts any more
Dennis Simpson wrote: Three of us updated to latest windows cygwin last week, and none can run even simple .sh scripts any more. Prior version was 6 months ago. http://cygwin.com/ml/cygwin-announce/2006-12/msg00026.html Next time RTFRA. Oh, and STFLA; this particular horse died a *lng* time ago. -- Matthew Congratulations! You've won a free trip to the future! All you have to do to claim your prize is wait five minutes... -- 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: pasting into an ssh connection painfully slow... sometimes
On 2/8/07, DePriest, Jason R. wrote: On 2/8/07, Lev Bishop wrote: On 2/8/07, Lev Bishop wrote: When I get some time I'll redo those patches against the latest cygwin version. In the meantime, if netscreen provides a sysctl net.inet.tcp.ackonpush or some way to disable delayed acks, then that might help you. Or you could try changing on your cygwin box the registry entry HKLM\SYSTEM\CurrentControlSet\Services\Afd\Parameters\DefaultSendWindow (DWORD) to at least 0x1 Lev Looks like my DefaultSendWindow was set to 0xfc00. I've set it to 0x1 but I can't reboot right now. I'll reboot it in a couple hours and give it a shot. Thanks for the information! -Jason This did not help. The netscreen doesn't have any available options for ackonpush that I can find. The interface is similar to IOS in some ways, so I don't get a full system prompt. As for Larry Hall's suggestion, I don't see a way to configure how it treats 'SSH-2.0-OpenSSH_4.5' vs. '2.0-PuTTY_Release_0.58'. Other than that one line in the connection, where the client announces itself, the traffic looks the same to me... one is just much, much slower. -Jason -- 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: ls not showing anything - sometimes
Dennis Simpson wrote: One co-worker downloaded the latest Windows cygwin last week. His ls command now consistently does not return anything, regardless of what directory he is in. This is in addition to not being able to run shell scripts any more, either. For the problem with running shell scripts, see the bash announcement: http://cygwin.com/ml/cygwin-announce/2007-01/msg00015.html For anything else: Problem reports: http://cygwin.com/problems.html -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: Help. Cygwin corrupting files
Larry Hall (Cygwin) wrote: Chuck wrote: Larry Hall (Cygwin) wrote: Chuck wrote: Larry Hall (Cygwin) wrote: Chuck wrote: snip HD scan shows no errors. snip I'm beginning to think I need to remove and reinstall every cygwin package, but I'm not certain that will fix it either. I've already reinstalled both coreutils and cygwin itself. I've even tried rolling both back a few releases, but I get the same problem. This is very strange. Look for the usual suspects of problem software - firewalls, virus checkers, spyware/anti-spyware. Nothing has changed. I did a virus scan and spyware scan too. The virus scan was completely clearn. The spyware scan picked up the usual tracking cookies but nothing really bad. The only other thing I can think of that's new is that Daemontools virtual cd drive software. I've since removed it but it has not cleared up the problem. Actually, I was suggesting that your firewall, virus checker, and/or spyware software may be interfering. While your symptoms are not typical of these kinds of buggy software, it is a known fact that they can interfere with Cygwin in undesirable ways. To be sure they are not interfering, you must uninstall them. Turning the off is not enough. Can't do that. The virus software is locked down. Anyway I've been using the same av and antispyware software for years. Never had a problem until last week. I really dont think that's the issue. About the only thing I can remove is Windows Defender which I probably don't need anyway. I already spybot. -- 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: Help. Cygwin corrupting files
Andrew DeFaria wrote: Chuck wrote: I'd buy into the HD-getting-ready-to-fail argument more if I saw weirdness on Windows too, but I don't. At least not yet. Plus scans of the HD with both Tuneup Utilities and Windows itself are not turning anything up. WAG but have you looked at the event log? Yea, that was one of the first places I went. Nothing there of interest. I did find out what that other software was that Daemontools installed before it installed itself. It was SPTD (scsi passthrough direct). I've uninstalled that too and still have the problem. I'm beginning to think the problem has nothing to do with DaemonTools or SPTD. It may have just been a coincidence that it began around the time that I installed that. -- 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: ls not showing anything - sometimes
Dennis Simpson wrote: One co-worker downloaded the latest Windows cygwin last week. His ls command now consistently does not return anything, regardless of what directory he is in. This is in addition to not being able to run shell scripts any more, either. The other two of us that upgraded last week to the latest Windows cygwin do NOT have this ls problem. ls works fine. I thought it might be a problem with cygwin too so I rolled back the cygwin kernel to version 1.5.23-1, and coreutils to 6.4-1. That didn't help. I'm glad someone else is reporting this. Maybe there's a real problem here. What hw/os is your colleague working on? Mine is a Dell D610 laptop, Windows XP SP2 with all latest patches. -- 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: Help. Cygwin corrupting files
Chuck wrote: Larry Hall (Cygwin) wrote: Chuck wrote: Larry Hall (Cygwin) wrote: Chuck wrote: Larry Hall (Cygwin) wrote: Chuck wrote: snip HD scan shows no errors. snip I'm beginning to think I need to remove and reinstall every cygwin package, but I'm not certain that will fix it either. I've already reinstalled both coreutils and cygwin itself. I've even tried rolling both back a few releases, but I get the same problem. This is very strange. Look for the usual suspects of problem software - firewalls, virus checkers, spyware/anti-spyware. Nothing has changed. I did a virus scan and spyware scan too. The virus scan was completely clearn. The spyware scan picked up the usual tracking cookies but nothing really bad. The only other thing I can think of that's new is that Daemontools virtual cd drive software. I've since removed it but it has not cleared up the problem. Actually, I was suggesting that your firewall, virus checker, and/or spyware software may be interfering. While your symptoms are not typical of these kinds of buggy software, it is a known fact that they can interfere with Cygwin in undesirable ways. To be sure they are not interfering, you must uninstall them. Turning the off is not enough. Can't do that. The virus software is locked down. Anyway I've been using the same av and antispyware software for years. Never had a problem until last week. I really dont think that's the issue. About the only thing I can remove is Windows Defender which I probably don't need anyway. I already spybot. I understand. But you mention Windows Defender. It's been known to cause at least some trouble: http://cygwin.com/ml/cygwin/2007-01/msg00742.html I'm not saying this is your problem or that this class of issue is your problem. But it is possible that it is an issue. If you haven't already, I'd recommend removing all you can and see if that helps any. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: ls not showing anything - sometimes
On Mon, Feb 12, 2007 at 06:04:57PM -0500, Chuck wrote: Dennis Simpson wrote: One co-worker downloaded the latest Windows cygwin last week. His ls command now consistently does not return anything, regardless of what directory he is in. This is in addition to not being able to run shell scripts any more, either. The other two of us that upgraded last week to the latest Windows cygwin do NOT have this ls problem. ls works fine. I thought it might be a problem with cygwin too so I rolled back the cygwin kernel to version 1.5.23-1, and coreutils to 6.4-1. That didn't help. I'm glad someone else is reporting this. Maybe there's a real problem here. What hw/os is your colleague working on? Mine is a Dell D610 laptop, Windows XP SP2 with all latest patches. I doubt that this particular problem is anything other than a missing package, actually. The details listed at http://cygwin.com/problems.html would probably be helpful. cgf -- 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: Unable to run even simple batch scripts any more
Matthew Woehlke mw_triad at users.sourceforge.net writes: Dennis Simpson wrote: Three of us updated to latest windows cygwin last week, and none can run even simple .sh scripts any more. Prior version was 6 months ago. http://cygwin.com/ml/cygwin-announce/2006-12/msg00026.html Next time RTFRA. Oh, and STFLA; this particular horse died a *lng* time ago. Obviously, the horse is still alive and attempting to limp along. I predict it'll stay alive for quite some time longer. * Bash's current treatment of crlf causes unexpected breakage of things that worked for years, and which most naive users expect to continue to work. * Workaround using text mounts fails because lots of cygwin commands don't work right under text mounts (gzip for example, but there's lots more). * Workaround by exporting SHELLOPTS breaks things because it put interactive things like history expansion into non-interactive shells (try calling man bash after exporting SHELLOPTS with igncr, for example). * Workaround inserting set -o igncr is impractical when there are lots of scripts. * Workaround calling d2u is impractical when there are lots of scripts, and breaks if the scripts must work with non-cygwin shells. I know, cygwin developers are not interested in fixing this, which is certainly their right. But you can be sure that reports of this problem will continue to arrive. -- 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: Unable to run even simple batch scripts any more
Eric Backus wrote: Matthew Woehlke mw_triad at users.sourceforge.net writes: Dennis Simpson wrote: Three of us updated to latest windows cygwin last week, and none can run even simple .sh scripts any more. Prior version was 6 months ago. http://cygwin.com/ml/cygwin-announce/2006-12/msg00026.html Next time RTFRA. Oh, and STFLA; this particular horse died a *lng* time ago. Obviously, the horse is still alive and attempting to limp along. I predict it'll stay alive for quite some time longer. * Bash's current treatment of crlf causes unexpected breakage of things that worked for years, and which most naive users expect to continue to work. * Workaround using text mounts fails because lots of cygwin commands don't work right under text mounts (gzip for example, but there's lots more). * Workaround by exporting SHELLOPTS breaks things because it put interactive things like history expansion into non-interactive shells (try calling man bash after exporting SHELLOPTS with igncr, for example). * Workaround inserting set -o igncr is impractical when there are lots of scripts. * Workaround calling d2u is impractical when there are lots of scripts, and breaks if the scripts must work with non-cygwin shells. I know, cygwin developers are not interested in fixing this, which is certainly their right. But you can be sure that reports of this problem will continue to arrive. And Cygwin's bash maintainer continues to work to improve the situation for those who can't just do the right thing, despite all the email that comes to this list suggesting that he's not interested in these issues. I'd recommend, before others start slinging more mud, that they read the totality of the discussion about this. I think you'll realize that there have been herculean efforts to address the deficiencies mentioned above and that the effort continues. It would be a shame if all this extra noise causes the maintainer to actually loose interest in the issues people find as a result of this change. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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/
where to find archives?
Could you plz let me know where can I find the cygwin tar package archives (say 1.15.x)? Regards, Mohankumar -- 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: where to find archives?
Mohankumar Periasami wrote: Could you plz let me know where can I find the cygwin tar package archives (say 1.15.x)? The only versions that are officially supported are the current and previous version. But if you look on the mirrors there are often older versions as well. I just took a look at sourceware.org and it has versions of the main cygwin package going back to 1.5.15, so all mirrors should have at least those. If you want something further back than that you'll have to just keep searching mirrors until you find one that does not cull previous versions. You can also google for the specific filename of the package, and there is the Cygwin Time Machine site (google it) which has older versions available, and you could build any version you want from source by getting the appropriately dated files from CVS. But do realize that using ancient versions is not supported here on this list so please don't ask for help if something breaks. And it will, unless you're quite careful, since the Cygwin DLL is backwards compatible but NOT forwards compatible -- if you try to use an ancient version of cygwin1.dll with binaries (i.e. .exe files such as ls.exe) that were built and linked against a recent Cygwin version, they will fail. So you have to make sure that everything is from the same vintage -- you can't just drop an ancient cygwin1.dll onto a system with current packages. However, the reverse is not true: you *can* use the current cygwin1.dll with any .exe linked against any v1.x Cygwin DLL in existance, which means that it is always safe to drop in a newer cygwin1.dll to replace an older version, but never the reverse. Brian -- 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/
EOL for Windows 95/86/Me
I'm not sure if it has reached the consciousness of the general Cygwin user base yet but I wanted to make sure that everyone was aware of the fact that we will be ripping out support for Windows 95, Windows 98, and Windows Me in the next version of Cygwin, which will be version 1.7.0. This has been announced on our web site (http://cygwin.com) for a couple of weeks, has been discussed in the cygwin-developers mailing list (http://cygwin.com/ml/cygwin-developers) for six months or so, and has been discussed between Corinna (corinna) and me (cgf) for longer than that. I hope that the reason to drop the support is fairly obvious. If it isn't feel free to respond to this message in the cygwin mailing list. So, barring any catastrophic problems with the current released version of the Cygwin DLL, the last Cygwin version with support for non-Windows-NT class versions of Windows will be 1.5.24-2. We're not against someone stepping up to continue to support the 1.5.x series in a separate CVS branch, if there is still interest in this. We can provide this person with checkin privileges to the cygwin source control and we'd expect that this person would make periodic releases of the old 1.5.24 version. Barring that however, it's so long Windows 9x. FYI, cgf * *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL and you WILL be able to unsubscribe. *
