Re: symbolic link curiousity in 3.6.0

On 2025-04-04 10:40, Pádraig Brady wrote: Is this patch is OK to be applied to gnulib, with the tweaks Corinna mentioned? Yes, I did that just now, and propagated it into coreutils. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documen

Re: symbolic link curiousity in 3.6.0

On 2025-03-30 05:50, Corinna Vinschen wrote: The definition of O_PATH requires an additional #include Thanks, I added that and installed the patch into Gnulib. However, assuming not only Cygwin is affected, shouldn't the patch rather use O_PATH if it's available, O_RDONLY if not? I h

Re: symbolic link curiousity in 3.6.0

traditionally (and I'm talking about 7th edition Unix) a single output line of 'ls' corresponded to a state obtained atomically from the file system. I realize we can't always do that nowadays but the further we depart from it, the worse 'ls' users will be. The link dereferencing is a courtesy of

Re: symbolic link curiousity in 3.6.0

On 3/31/25 12:26, Corinna Vinschen wrote: ls(1) always potentially shows a past state anyway. Sure, but traditionally (and I'm talking about 7th edition Unix) a single output line of 'ls' corresponded to a state obtained atomically from the file system. I realize we can't always do that nowad

Re: symbolic link curiousity in 3.6.0

On 3/31/25 11:27, Pádraig Brady wrote: The file could be deleted at any time. We're just suppressing errors in the edge case it's deleted More generally, though, the file could be renamed and another put in its place, which means that an attacker could cause 'ls' to generate a line that does

Re: symbolic link curiousity in 3.6.0

On 2025-03-30 07:26, Pádraig Brady wrote: On 30/03/2025 13:50, Corinna Vinschen wrote: In terms of coreutils, I think either ls(1) gobble_file() or file_has_aclinfo_cache() should still handle ENOENT from file_has_aclinfo() and not print any error message.  After all, due to the preconditions fo

Re: symbolic link curiousity in 3.6.0

patch work for you? I haven't tested or installed it (I don't use Cygwin).From e245ab6ac865c7ff723837645886eb717c53a754 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Sat, 29 Mar 2025 10:27:01 -0600 Subject: [PATCH] file-has-acl: port symlink code to Cygwin Problem reported by Cori

Re: bug#75806: Trailing spaces; pattern "\s" before "[[:cntrl:]]" faulty

On 2025-01-24 05:27, Andreas BROCKMANN via Bug reports for GNU grep wrote: The 1st command below correctly reports trailing spaces, for Unix and Windows format files. The 2nd one incorrectly reports all lines. grep -sHn -i " [[:cntrl:]]*$" *.vhd grep -sHn -i "\s[[:cntrl:]]*$" *.vhd I do

Re: bug#23314: gzip-1.7-1 regression: cannot redirect output of gzip -l

Come to think of it, that part of gzip can be simplified considerably, which should make future problems like this less likely. I installed the attached additional patch. Yay, 46 fewer files in the gzip tarball! >From 02b67e301e66c8641230afbe8663f2d503c0f57b Mon Sep 17 00:00:00 2001 From: P

Re: bug#23314: gzip-1.7-1 regression: cannot redirect output of gzip -l

Thanks for reporting the problem. I installed the attached gzip patch on savannah. From 9167b7b9d5b68cea52bdd683b81a3b64381b7ff9 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Tue, 19 Apr 2016 17:43:09 -0700 Subject: [PATCH] gzip: fix bug with -l output to pipes Problem reported by Christian

Re: [PATCH] openat-die: use _Noreturn markup

Jim Meyering wrote: Glad you found the root of the problem, and that it's not in gnulib. Likewise. For future reference, we avoid in gnulib because MSVC mishandles it. Please see doc/posix-headers/stdnoreturn.texi for details. -- Problem reports: http://cygwin.com/problems.html FAQ

Re: bug#14569: 24.3.50; bootstrap fails on Cygwin

On 06/14/2013 11:03 AM, Christopher Faylor wrote: > You pointed to an archived mail messages which implies that was fixed > more than a year ago. What makes you think it is still a problem? The message I pointed to says this: > Testcase sign

Re: bug#14569: 24.3.50; bootstrap fails on Cygwin

Cygwin developers, I'm worried about a Cygwin bug where pthread_kill may not send a signal to the correct thread. This bug may be causing Emacs to crash. The Cygwin bug is discussed in this thread: http://cygwin.com/ml/cygwin/2012-05/msg00472.html Emacs uses pthread_kill to redirect SIGCHLD to t

Re: [PATCH] root-uid: new module

On 06/27/2012 12:48 AM, Corinna Vinschen wrote: > I guess, the most platform-independent approach would be to encapsulate > the whole problem into a function requesting a specific capability along > the lines of the POSIX 1.e definitions, Some Gnulib code (e.g., unlinkdir.c) relies on the Solaris-

Re: [Bug-tar] Re: tar --atime-preserve with an empty file triggers a warning

Thanks for reporting that. I installed the following patch into GNU tar: From 24980ce3c6e01ce43cdccd5d1f693c9838e447ed Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Mon, 7 Mar 2011 15:40:32 -0800 Subject: [PATCH] --atime-preserve=replace: fix correctness and performance bugs reported by

Re: bug#7948: 16-bit wchar_t on Windows and Cygwin

On 02/02/11 03:29, Bruno Haible wrote: > - Define a type 'wwchar_t' on all platforms, equivalent to uint32_t > on Windows platforms and to 'wchar_t' otherwise. As a minor point, would it be OK to call this type 'xchar_t' instead? 'x' is the successor to 'w', after all, and it can be thought

Re: cygwin -mno-cygwin AC_CHECK_SIZEOF

Eric Blake <[EMAIL PROTECTED]> writes: > Patch below. Keep replies on the autoconf-patches list. Thanks. In retrospect it was a mistake to append the trailing newline, I guess. I installed the following: it differs from your patch only in adding more commentary. 2006-12-01 Eric Blake <[EMAI

Re: Where is patch?

Stepan Kasal <[EMAIL PROTECTED]> writes: > Paul, where will the next stable version appear? > At ftp://ftp.gnu.org/gnu/patch or ftp://ftp.gnu.org/gnu/diffutils ? At this point I'm planning to make 'patch' part of diffutils. No schedule yet, though. -- Unsubscribe info: http://cygwin.com/m

Re: mkdir -p and EROFS

Jim Meyering <[EMAIL PROTECTED]> writes: > Are there `real' environments that use a set-up like you describe, > with a writable file system mounted inside a read-only one? I vaguely recall doing this myself a while back, on a Solaris box. I made /usr read-only, but /usr/tmp was a writeable files

Re: mkdir -p and EROFS

all this patch at this late date? 2005-10-12 Paul Eggert <[EMAIL PROTECTED]> * mkdir-p.c (make_dir_parents): Don't fail if an intervening mkdir fails due to EROFS, or due to EEXIST or other reasons for that matter. Problem reported by Eric Blake. (ENOSY

Re: should a space really be a "special character" ?

ve just noticed that autoconf/aclocal.m4 also holds > AM_MISSING_HAS_RUN. Why? To avoid dependencies? Yes; someone who's installing Autoconf shouldn't need Automake, to avoid the usual bootstrapping problems. To work around the problem I installed the following Autoconf patch. Thanks

Re: bug in du

Eric Blake <[EMAIL PROTECTED]> writes: > One possible fix is revisiting line 377 in src/du.c in CVS, which > currently skips hard links only if a file has multiple links. Sorry, I don't quite follow this. Don't all the directories in question have multiple links? Or, if you're talking about wal

Re: [Fwd: Strange-Dangerous behaviour in Cygwin]

k the disagreement with POSIX was unintended. So I installed this patch. (It's not often that I get to fix one of his bugs! :-) 2005-05-08 Paul Eggert <[EMAIL PROTECTED]> * NEWS: cp, ln, mv, rm no longer discard white space when intepreting responses. * lib/

Re: DD converts LF -> CR / LF

Eric Blake <[EMAIL PROTECTED]> writes: > it now defaults to the underlying mount mode when the user does not > specify binary or text. In my opinion, dd should default to binary > when neither text nor binary is specified Hmm, overriding the explicit advice of the system administrator? How commo

Re: mkdir -p and network drives

Christopher Faylor <[EMAIL PROTECTED]> writes: > Except that it can't be made to work correctly due to a bash bug. Which Bash bug is that? Bash bugs can be fixed. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentat

Re: mkdir -p and network drives

Igor Pechtchanski <[EMAIL PROTECTED]> writes: > There's always Pierre's solution of doing minimal support for stat()ing > '//' and '//MACHINE', though... Yes, that's the basic idea. That's the only thing that makes sense here. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple P

Re: mkdir -p and network drives

Eric Blake <[EMAIL PROTECTED]> writes: >> + if (do_chdir && dirpath[0] == '/') >> +{ >> + /* POSIX says "//" might be special, so chdir to "//" if the >> + file name starts with exactly two slashes. */ >> + char const *root = "//" + (dirpath[1] != '/' || dirpath[2] == '

Re: mkdir -p and network drives

Eric Blake <[EMAIL PROTECTED]> writes: > //MACHINE currently generates ENOENT, whether or not there is a > server on the network with that name, and mkdir(2), stat(2), and > chdir(2) with an argument of "//MACHINE" fail. That's certainly a hassle. Let's not worry about going through zillions of

Re: mkdir -p and network drives

ain it.) That being said, it can't hurt to add the following minor workaround, (which would work on Domain OS anyway :-), so I installed it. 2005-05-05 Paul Eggert <[EMAIL PROTECTED]> * makepath.c (make_path): chdir to "//", not "/", if the file name