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 s
Chuck wrote:
Larry Hall (Cygwin) wrote:
Chuck wrote:
HD scan shows no errors.
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
bot
Larry Hall (Cygwin) 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 i
On 2/9/07, winner wei wrote:
Hi,
when I wanted to open a file at a specified directory for writing, running it
in Cygwin, the opening just failed. It is extremely simple, like this:
if((fp=fopen("C:\cygdrive\c\home\user\data\filename", "w"))==NULL)
You need to use posix-style paths. You're
Hi,
when I wanted to open a file at a specified directory for writing, running it
in Cygwin, the opening just failed. It is extremely simple, like this:
if((fp=fopen("C:\cygdrive\c\home\user\data\filename", "w"))==NULL)
{
handling exception...
}
I also tried a few other ways for the pathname, l
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.
>
>
Everyth
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 s
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
Thanks for pointing that out -- I'm really not very conversant with
Windows security.
While logged in as Administrator, I tried adding sshd_server to the list
of users with the "Act as part of the operating system" privilege
(SeTcbPrivilege), but for some reason on my system both the "Add User
A new version of the lftp package is available in the Cygwin
distribution. lftp is a sophisticated file transfer program and
ftp/http client. It
supports multiple network protocols, offers tab completion, command
history, job control, and bookmarks, can mirror sites and transfer
multiple files in
Phil Betts wrote:
David Bear wrote on Friday, February 09, 2007 4:56 AM::
Okay, the problem is in quoting in shell scripts, I think.
It is. It's not a Windows problem and it certainly isn't a cygwin problem.
Although spaces occur more often in Windows than on other platforms,
they can and do
I started noticing a strange problem recently. When I am in the
/cygdrive directory I can't ls anything most of the time. Same thing
sometimes happens in my home directory too but it happens less often.
Here's some sample output. As you can see the /cygdrive
$ uname -a
CYGWIN_NT-5.1 1.5.24(0.156/
Dave Korn wrote:
On 07 December 2006 16:00, Keith Christian wrote:
Baffling. Any ideas?
Different binutils versions? make versions? Run "cygcheck -s -v -r" on
each machine and then diff the two?
Yesterday I downloaded the 0.59 binary zipfile, and it WORKS on the machine
where the 0.5
David Bear wrote on Friday, February 09, 2007 4:56 AM::
> Okay, the problem is in quoting in shell scripts, I think.
It is. It's not a Windows problem and it certainly isn't a
cygwin problem.
Although spaces occur more often in Windows than on other
platforms, they can and do occur on Unix/Linu
David Bear wrote:
> I would like to have used something like
>
> cd $USERPROFILE
>
> in a bash script but since windows insists on putting spaces in
> names, this seems impossible.
You might be happier writing your scripts in zsh:
bash% cd;pwd
/home/gsw
bash% export SP="silly path"
bash% mkd
I have updated syslog-ng on cygwin.com to the latest stable release
1.6.12. This is just a minor update which contains scalability
improvements and bug fixes.
syslog-ng, as the name shows, is a syslogd replacement, but with new
functionality for the new generation. The original syslogd allows
mes
I've updated the version of tin to 1.8.3-1.
New minor release with some bugfixes:
-- 1.8.3 release 20070201 "Scotasay" --
018) Christian Weisgerber <[EMAIL PROTECTED]>
BUG. assumed that wchar_t and wint_t are of the same size
FIX. tcurses.c
017) Antonio Querubin <[EMAIL PROTECTED]>
I've just updated the version of cpio to 2.7-1.
This is an official upstream release. The Cygwin version has been
built from the vanilla sources. cpio passes all (two) tests in the
testsuite.
What's new in 2.7?
* Improved error checking and diagnostics
* Bugfixes
** Fixed CAN-1999-1572
** All
David Bear wrote:
Brian Dessent wrote:
David Bear wrote:
Okay, the problem is in quoting in shell scripts, I think.
Here's an example:
#!/usr/bin/bash
curdir=`pwd`
echo $curdir
prodir=`cygpath $USERPROFILE`
Should be:
prodir=$(cygpath "$USERPROFILE")
echo $prodir
cd $prodir
Should be:
19 matches
Mail list logo
