DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 52P9vsh12610511 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 52P9vsh12610511 Authentication-Results: delorie.com; dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=RYczOzDC X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org DFCE6385743A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1742896672; bh=Q6pYFxAAoLLdBgcpTxUD3waHH6w+ajCRO46Q4kAUUE8=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=RYczOzDCQcV9jjdA7XZ8UHqYwOHyAV/3oQEeXfhN9p23l2CjPVO2DyZr8RONJdNIp pD4ERfvOA9igw8baH0GAsN08DO+AMwOvq9ZlLC5Qz0gMt1icySfHpFgn0FemD4n3gR X5SfNoD+riAiqW5mSlDGi4gZc7U627vN5/AmiQv0= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1EFC13858D33 Date: Tue, 25 Mar 2025 10:56:55 +0100 To: cygwin AT cygwin DOT com Subject: Re: symbolic link curiousity in 3.6.0 Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Mar 25 02:25, Mark Geisert via Cygwin wrote: > This occurs on the released 3.6.0 but not in 3.6.0 test build 327. > > /tmp ls foo bar > ls: cannot access 'foo': No such file or directory > ls: cannot access 'bar': No such file or directory > > /tmp ln -s foo bar > > /tmp ls foo bar > ls: cannot access 'foo': No such file or directory > bar@ > > /tmp ls -l foo bar > ls: cannot access 'foo': No such file or directory > ls: bar: Not supported > lrwxrwxrwx 1 Mark None 3 Mar 25 02:08 bar -> foo > > The spurious "Not supported" message is new and curious. > I could not see anything obvious in an strace of the command. This is weird. I just tried the same with 3.6.0-1: $ cd /tmp $ ls -l foo bar ls: cannot access 'foo': No such file or directory ls: cannot access 'bar': No such file or directory $ ln -s foo bar $ ls foo bar ls: cannot access 'foo': No such file or directory bar $ ls -l foo bar ls: cannot access 'foo': No such file or directory lrwxrwxrwx 1 corinna vinschen 3 Mar 25 10:46 bar -> foo That's the expected output. Your ls output shows an at-sign after the name "bar". You're probably using an alias for ls including the -F option. Can you paste your alias here? Are you using a specific setting of the CYGWIN env var including a symlink type? Can you try intermediate test release between 327 and -1? Corinna -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple