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 31453 invoked from network); 5 Jun 2021 22:20:27 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 5 Jun 2021 22:20:27 -0000 Received: from MTA-11-4.privateemail.com ([198.54.127.104]) by 1ess; Sat Jun 5 17:04:23 -0400 2021 Received: from mta-11.privateemail.com (localhost [127.0.0.1]) by mta-11.privateemail.com (Postfix) with ESMTP id DA616800BB for <9front@9front.org>; Sat, 5 Jun 2021 17:04:13 -0400 (EDT) Received: from localhost (unknown [10.20.151.225]) by mta-11.privateemail.com (Postfix) with ESMTPA id 015BB80075 for <9front@9front.org>; Sat, 5 Jun 2021 17:04:12 -0400 (EDT) Date: Sat, 5 Jun 2021 14:04:03 -0700 From: Anthony Martin To: 9front@9front.org Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Virus-Scanned: ClamAV using ClamSMTP List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: extensible reduce/map scripting-based SVG reduce/map descriptor core DOM generator Subject: [9front] Re: /proc/n/fd format clarification Reply-To: 9front@9front.org Precedence: bulk binary cat once said: > So this mentions 3 things, a path, a version, and a type. This > checks out, until you look at the supposed lengths. The path is > supposed to be 8 bytes, which would be 16 hex digits, that's ok, > but it says 4 bytes for the version, which would be 8 hex digits, > and we don't see anything like that here. What's going on here? The qid version is a decimal integer. The other components of the qid are printed in hexadecimal. It's just a very old convention. Note that ls(1) with the -q flag will display the qid in the same format. Cheers, Anthony