From: "Arsen Arsenović" <arsen@aarsen.me>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Alejandro Colomar <alx@kernel.org>,
coreutils@gnu.org, linux-man@vger.kernel.org
Subject: Re: Move GNU manual pages to the Linux man-pages project
Date: Wed, 01 Oct 2025 15:21:28 +0200 [thread overview]
Message-ID: <86a52an4fb.fsf@aarsen.me> (raw)
In-Reply-To: <20250930205552.nevihqli7tw7lefk@illithid>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
"G. Branden Robinson" <g.branden.robinson@gmail.com> writes:
>> (A funny side note: subconsciously, I chose the name "fildes.7" as to
>> not go over eight characters; it came to me naturally after many years
>> of working with and on Unix-like systems, this archaic element simply
>> lodged itself into my instincts after some time.)
>
> Eight's an odd choice for that, though. As I understand it, the Fortran
> linker that Unix originally used (C did not exist yet) had a limit of 6
> characters for externally resolvable symbols, because that was all some
> IBM operating system could handle. File names (or "path name
> components", if one insists) were limited to 14 characters until the
> Berkeley "fast" file system. The tuhs at tuhs dot org is a more
> reliable resource than I can be here, though.
Heh, some confusion it seems. No idea where I got eight from.
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
next prev parent reply other threads:[~2025-10-01 13:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 16:08 Move GNU manual pages to the Linux man-pages project Alejandro Colomar
2025-09-20 16:27 ` Sam James
2025-09-20 16:50 ` Alejandro Colomar
2025-09-20 17:00 ` Alejandro Colomar
2025-09-20 16:34 ` Pádraig Brady
2025-09-20 16:55 ` Alejandro Colomar
2025-09-20 17:01 ` Pádraig Brady
2025-09-20 17:04 ` Alejandro Colomar
2025-09-20 20:05 ` Collin Funk
2025-09-20 21:05 ` Alejandro Colomar
2025-09-20 23:02 ` Collin Funk
2025-09-21 8:36 ` Alejandro Colomar
[not found] ` <PA3P190MB24382227EA61EC2758D5AA11C410A@PA3P190MB2438.EURP190.PROD.OUTLOOK.COM>
2025-09-20 23:18 ` Collin Funk
2025-09-22 15:06 ` Michael Greenberg
2025-09-20 17:42 ` Jakub Wilk
2025-09-20 21:10 ` Alejandro Colomar
2025-09-20 21:22 ` Collin Funk
2025-09-21 8:28 ` Bernhard Voelker
2025-09-21 20:00 ` Chuck Wolber
2025-09-21 12:02 ` Arsen Arsenović
2025-09-21 12:53 ` Alejandro Colomar
2025-09-25 14:04 ` Arsen Arsenović
2025-09-25 14:31 ` Alejandro Colomar
2025-09-29 9:46 ` Arsen Arsenović
2025-09-29 10:33 ` Alejandro Colomar
2025-09-29 21:26 ` Arsen Arsenović
2025-09-29 21:38 ` Alejandro Colomar
2025-09-29 21:41 ` Pádraig Brady
2025-09-29 23:27 ` Alejandro Colomar
2025-09-30 10:12 ` Pádraig Brady
2025-09-30 21:14 ` Bernhard Voelker
2025-09-30 13:23 ` Rob Landley
2025-09-30 13:35 ` G. Branden Robinson
2025-09-30 19:57 ` Arsen Arsenović
2025-09-30 20:55 ` G. Branden Robinson
2025-10-01 13:21 ` Arsen Arsenović [this message]
2025-10-01 19:37 ` Rob Landley
2025-10-02 18:46 ` Arsen Arsenović
2025-10-02 20:48 ` G. Branden Robinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a52an4fb.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=alx@kernel.org \
--cc=coreutils@gnu.org \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.