From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 5667 invoked from network); 23 Jan 2022 00:54:57 -0000
Received: from 4ess.inri.net (216.126.196.42)
  by inbox.vuxu.org with ESMTPUTF8; 23 Jan 2022 00:54:57 -0000
Received: from mimir.eigenstate.org ([206.124.132.107]) by 4ess; Sat Jan 22 13:18:21 -0500 2022
Received: from stockyard (ue.tmodns.net [172.58.238.253])
	by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 335b945c (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO)
	for <9front@9front.org>;
	Sat, 22 Jan 2022 10:18:05 -0800 (PST)
Message-ID: <9297E9E410CD2F55C039E55C78E3C19D@eigenstate.org>
To: 9front@9front.org
Date: Sat, 22 Jan 2022 13:18:03 -0500
From: ori@eigenstate.org
In-Reply-To: <87bl0n230a.fsf@turtle-trading.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: app enhancement SQL over ACPI singleton-oriented singleton property generator 
Subject: Re: [9front] Fix error messages from sshfs
Reply-To: 9front@9front.org
Precedence: bulk

Quoth Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>:
> Hi all,
> 
> As discussed in the previous thread "ape/_errno: ENOENT", APE has
> difficulties classifying the error messages from sshfs, because sshfs
> passes through the error messages from the server.  This patch fixes
> that for the currently known errors by using sshfs's own error strings
> as far as possible.
> 
> Thanks, benny
> 
> 

lgtm, thanks again for pinging. (it's been
a busy week, and my spare time has been on
other hacking)