From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) by sourceware.org (Postfix) with ESMTPS id C5D883858010 for ; Sun, 17 Jan 2021 22:24:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org C5D883858010 Received: by mail-ed1-x52c.google.com with SMTP id bx12so1481118edb.8 for ; Sun, 17 Jan 2021 14:24:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eYN7OJSNZkvDzMh7tECqrcBJukwThVkTPMMn34Hrb0Q=; b=OMtCHwoq7DhHKNUbzZq0I1IcY/UU78ZzjEvYgKNypJ7ScwAxESm09Z90uFNvsDwN/P Vl9koUybUSJypaLGNrKeoe1GlT8J17gxEtJ1OiLaxlIdOBuEKqrg4pVKti0mwYoP5xnH WHgJNGmsQGOZI0AJuGWCbXgX6im0raUhU7qL4eB5G4HJGChlZQn2yJFtxYQQKP0OHME0 2uuCdW5xZMv9PlzMlkzXqFTuZCJKwBpcSk1NvP8o3/i/1WKC02E/7F1xprqW7HJxfhSX odLrvG+v7ETAB4iZuPMbB8Ecrsze5rWpAGzbkVydL2izmPrjyTBIDr8nCxSpOCa5x/2q /owQ== X-Gm-Message-State: AOAM530RKVAHcwMEbHQ8vVJTMjiOpgRjV09TCEeRT+Z+M8B/+0P2h83S aPFczGrt/qeRN0RtmdrSgY80V3MG7V6Ivk/EUJ8= X-Google-Smtp-Source: ABdhPJwPuqGOSkfnc9jDOWA12ZcSyVL54b6rQ0nqJrLp2ZfVxZ8WZ91g0PUT8AV21Es7JwITmD8NIsGyZIfBgy7Ui3Y= X-Received: by 2002:a50:8004:: with SMTP id 4mr1054668eda.155.1610922287891; Sun, 17 Jan 2021 14:24:47 -0800 (PST) MIME-Version: 1.0 References: <1742171701.1391964.1610730544471.ref@mail.yahoo.com> <1742171701.1391964.1610730544471@mail.yahoo.com> <03cc5513-8a2c-d9cc-6b71-e0c2df0125ed@SystematicSw.ab.ca> <449114268.20210117211118@yandex.ru> <2213ecae-52ec-4148-9370-78b846fb26cc@SystematicSw.ab.ca> <1218339117.1507408.1610917628826@mail.yahoo.com> In-Reply-To: <1218339117.1507408.1610917628826@mail.yahoo.com> From: David Dyck Date: Sun, 17 Jan 2021 14:24:36 -0800 Message-ID: Subject: Re: misterious GIT failure (SOLVED) To: matthew patton Cc: "cygwin@cygwin.com" X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jan 2021 22:24:50 -0000 On Sun, Jan 17, 2021 at 1:08 PM matthew patton via Cygwin wrote: > I haven't run into a scenario yet where 'readlink' doesn't work. .... > Here's a unrelated example where symbolic links don't work the same as on unix/linux ( not sure this is a readlink issue ) When I try to write through /proc to to a processes stdout I get errors e.g. $ ls -l /proc/1708/fd/1 lrwxrwxrwx 1 DavidD Domain Users 0 Jan 17 14:20 /proc/1708/fd/1 -> /dev/pty2 $ printf "\033]0;foo\7" > /proc/1708/fd/1 -bash: printf: write error: Bad file descriptor but $ printf "\033]0;foo\7" > /dev/pty2 works I'm not sure if this is a readlink issue or just a bug in the cygwin implementation of /proc :-)