Reini Urban schrieb:
2005-06-26 11:00 MEST I sent to cygwin-announce, which didn't went through.
Oops, sorry for duplicate announces.
The archive does carry it. I oversaw it.
From - Sun Jun 26 11:00:51 2005
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Jun 2005 11:00:50 +0200
From: Reini Urb
2005-06-26 11:00 MEST I sent to cygwin-announce, which didn't went through.
From - Sun Jun 26 11:00:51 2005
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Jun 2005 11:00:50 +0200
From: Reini Urban <[EMAIL PROTECTED]>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.8b)
Gecko/20050
At 04:03 PM 6/28/2005, you wrote:
>Eric Blake wrote:
>>According to Corinna Vinschen on 6/28/2005 2:34 AM:
>>
>>>However, IMHO, ls should be changed to just print no error message,
>>>if file_has_acl() returns -1 and errno is set to EBUSY, and the file
>>>should simply be treated as a file with no
Question NS wrote:
Dear All,
How could I solve this problem?
The first step is to describe it thoroughly. See
http://cygwin.com/problems.html
--
God is my co-pilot, but the Devil is my bombardier.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: ht
Dear All,
How could I solve this problem?
__
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cyg
Eric Blake wrote:
According to Corinna Vinschen on 6/28/2005 2:34 AM:
However, IMHO, ls should be changed to just print no error message,
if file_has_acl() returns -1 and errno is set to EBUSY, and the file
should simply be treated as a file with no ACL. That's the least
intrusive way, IMHO.
It seems that this has been the case for a while, but the tar package is
missing a manpage for tar (though there is an info page). I believe the
manpage exists in the source package (albeit in a strange location) -- any
particular reason it's not included in the binary one?
Igor
--
On Tue, 28 Jun 2005, Dave Korn wrote:
Probably TITTTL material, but...
> Now, I'd certainly agree that short int is a strange default for od (as
> indeed is octal, which it defaults to if you don't specify a base
> explicitly);
Why would octal be a strange default for a program called "octal d
On Tue, 28 Jun 2005, Nikhil Nair wrote:
> Just a quick observation - but first an apology: I haven't read the
> thread, as I've only just subscribed, so this may have already been said.
>
> I'm a bit surprised by this wildcard behaviour, as I would have assumed
> "CD 1..." would have been picked u
On Tue, 28 Jun 2005, Fred Kulack wrote:
> > I've set up Cygwin on XP (now running on a non-admin account) with
> > CYGWIN=tty.
> [... Snipped some stuff about wanting a better terminal ...]
>
> How about rxvt? It has a native window (no X required) mode.
rxvt looks very good. Unfortunately, I ne
On Tue, 28 Jun 2005, Andreas Eibach wrote:
> Needless to say that scripts containing
>
> for i in `ls *.dat*`; do
Ouch!!!
> will NOT work, because Cygwin will interpret each sub-string between the \ '
> s separately, making parsing files a nuisance.
That script won't work anywhere. Who
On Mon, Jun 27, 2005 at 05:25:02PM -0400, Jeff Johnston wrote:
> Corinna Vinschen wrote:
> >On Jun 26 09:37, Humberto Bortolossi wrote:
> >
> >>Hi!
> >>
> >>I'm trying to port a C program written originally in
> >>Linux to the Microsoft Windows plataform.
> >>
> >>I've realized that math.h under cy
At 03:19 AM 6/28/2005, you wrote:
>Hi
>
>I'm new to CYGWIN
>I installed perl via Cygwin installation utility...
>now i want to install perl Tk in my system.. i downloaded Tk-804.027.tar.gz
>it gives a error msg like this
>*
Original Message
>From: Fergus Daly
>Sent: 28 June 2005 15:45
>
> ("od -x .." outputs the strange transposition of bytes that you have
> referred to.)
It's not a 'transposition of bytes'. It's not bytes at all; "od -x"
defaults to reading 16-bit short integers, and outputs them in hos
Hi,
Just a quick observation - but first an apology: I haven't read the
thread, as I've only just subscribed, so this may have already been said.
I'm a bit surprised by this wildcard behaviour, as I would have assumed
"CD 1..." would have been picked up by "CD *".
I'd suggest that this is a bash
>> Exactly the other way round ...
~> echo abcd | od -tx1
000 61 62 63 64 0a
005
is nice; and, for some purposes
~> echo abcd | od -An -tx1
61 62 63 64 0a
(or "od -An -tx1 ") is nicer still.
("od -x .." outputs the strange transposition of bytes
> I've set up Cygwin on XP (now running on a non-admin account) with
> CYGWIN=tty.
[... Snipped some stuff about wanting a better terminal ...]
How about rxvt? It has a native window (no X required) mode.
c:
chdir c:\cygwin\bin
REM See ~/.Xresources for rxvt configuration resources
start C:\cygwi
Hi,
I've set up Cygwin on XP (now running on a non-admin account) with
CYGWIN=tty.
I've struggled to find documentation on what happens when CYGWIN=tty,
apart from that it's more Unix-compatible. Is there any? I'm guessing
that Cygwin is doing some terminal emulation rather than just using
cmd.
Original Message
>From: Andreas Eibach
>Sent: 28 June 2005 14:14
> fix this in cygwin (as it _definitely_ works in Linux,
I'm glad you're so definite about this, it's good to have such confidence
in your own beliefs that you feel no need to verify them against reality.
> ls -hog "CD *"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Andreas Eibach on 6/28/2005 7:36 AM:
> Well, looks like a feature or a bug. :))
Feature.
>
> $ ls -hog CD0.dat
>
> -rw-r--r-- 1 0 Jun 28 14:46 CD0.dat
> (minus r; w minus; r minus; minus r; minus minus)
>
>
> and now ...
>
> $ ls
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Andreas Eibach on 6/28/2005 7:14 AM:
>
> -rw-r--r-- 1 0 Jun 28 14:46 CD0.dat
> -rw-r--r-- 1 24K Jun 28 14:46 CD 1 - Multimedia.dat
> -rw-r--r-- 1 2.9K Jun 28 14:46 CD 2 - Multimedia.dat
...
> ls -hog "CD*[12]*"
>
> WORK
Well, looks like a feature or a bug. :))
$ ls -hog CD0.dat
-rw-r--r-- 1 0 Jun 28 14:46 CD0.dat
(minus r; w minus; r minus; minus r; minus minus)
and now ...
$ ls -hog CD0.dat | od -x
722d 2d77 2d72 722d
Definitely wrong byte order.
In human readable format:
(r minus; minus w; minu
I don't see the problem.
> ls -hog "CD *"
> ls: CD *: No such file or directory
Of course. There is no file whose name is the four character string "CD *", so
ls doesn't find anything.
> ls -hog "CD [12]*"
> ls: CD [12]*: No such file or directory
Ditto. There is no file whose name is the six
Yes, this is the umpteenth time this gets asked, but also the umpteenth plead
to fix this in cygwin (as it _definitely_ works in Linux, also with vfat and
non-Linux partitions!!)
I have two files in ~, say they're
CD0.dat
CD1 - Multimedia (foo1).dat
CD2 - Multimedia2 (foo2).dat
+
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Corinna Vinschen on 6/28/2005 2:34 AM:
>>Hmm - murky waters here. It would be a simple one-line fix to
>>coreutils/lib/acl.c to ignore EBUSY as a non-error, and POSIX has
>>no requirements per se that a failure of acl() should imply a fai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ugh, top-posting. Reformatted.
>>-Original Message-
>>From: Eric Blake [mailto:ebb9 AT byu DOT net]
^
http://cygwin.com/acronyms#PCYMTNQREAIYR
>>My quick guess is that ACLs are at work. Compare the output
>>of
Thank you for your suggestions. Below you see the result for
file x (this is a file which does not work) and file y (which is a file
where chmod works):
$ getfacl -a x y
# file: x
# owner: fischron
# group: mkgroup_l_d
user::rwx
group::---
group:Administrators:rwx
mask:rwx
other:---
# file: y
# o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to [EMAIL PROTECTED] on 6/28/2005 2:51 AM:
> When I create a new file, behaviour depends on how I create it:
>
>touch new_file1
>chmod 0777 new_file1
>
> => works fine.
> But when I open a text editor, from within the editor create
I believe there is a bug in the cygwin DLL that causes a stack overflow
segmentation fault when ofstream::operator<< is used to write a string
that is longer than 2MB.
Attached is a simple program, writen.cc, that will create an ofstream and
write a string of user-specified length to it. When tha
I believe there is a bug in the cygwin DLL that causes a stack overflow
segmentation fault when ofstream::operator<< is used to write a string
that is longer than 2MB.
Attached is a simple program, writen.cc, that will create an ofstream and
write a string of user-specified length to it. When tha
Iv done a bit more investigating. as I thought It might be something to
do with the seconds (ls -l not displaying the seconds). The program t.c
containing:
#include
#include
#include
main(int argc,char *argv[])
{
struct stat finfo;
stat(argv[1],&finfo);
printf("Access : %s\n"
I found after some experimenting, that the previous description of
my chmod problem was not quite correct. The case seems to be more
complicated
than I thought at first. Here is a revised description of my problem:
PROBLEM:
From one day to the next, I can't chmod most old files anymore (error
me
On Jun 28 03:24, Eric Blake wrote:
> [bug-coreutils: posting this cygwin question upstream]
> Corinna Vinschen wrote:
> > Along these lines, we had a short discussion on the developers list
> > and we're wondering if it's necessary that ls prints this error message
> > at all. The message is gener
From one day to the next, I can't chmod any old files anymore (error
message:
"permission denied"), but when I create a new file, I can chmod it
without
problems:
chmod 0777 some_old_file
=> ... Permission denied
touch new_file
chmod 0777 new_file
=> works fine.
My first thought was t
Hi
I'm new to CYGWIN
I installed perl via Cygwin installation utility...
now i want to install perl Tk in my system.. i downloaded Tk-804.027.tar.gz
it gives a error msg like this
**
../pTk/mTk/xlib/X11/Xlib.h:1206
35 matches
Mail list logo
