From: "Lyndon Nerenberg (VE7TFX/VE6BBM)" <lyndon@orthanc.ca>
To: 9front@9front.org
Subject: [9front] Out-of-date and obsolete documentation
Date: Sun, 16 Jun 2024 13:20:47 -0700 [thread overview]
Message-ID: <ec7c9db2559e4fc0@orthanc.ca> (raw)
In-Reply-To: <E7CA6583020215A2D55AC14DF9DE809D@eigenstate.org>
ori@eigenstate.org writes:
> the manpages here need a rewrite; they're somewhat.. uh.. historical.
> fs(8) is more or less for cwfs; hjfs has its own console, and gefs
> has its own.
"Rewrite" is the key word here. There is still a lot of
text in the fs manpages that refers to kenfs behaviour that
has been gone for decades.
At this point I think all of the fs- and boot-related man pages
need a quick rm and then we need to start over from scratch.
But for this to work it would need a small group of dedicated
volunteers to do the work. I cannot be one of those right now
(but possibly in a couple of months). I might start tinkering
with some rewrites in the meantime, though.
--lyndon
prev parent reply other threads:[~2024-06-16 20:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-11 14:57 [9front] Staying up-to-date Thomas Nemeth
2024-06-11 15:08 ` phil9
2024-06-11 15:15 ` Thomas Nemeth
2024-06-12 11:57 ` cosarara
2024-06-12 16:57 ` Thomas Nemeth
2024-06-13 0:46 ` sl
2024-06-13 1:05 ` sl
2024-06-13 6:31 ` Thomas Nemeth
2024-06-13 17:16 ` hiro
2024-06-12 12:21 ` ori
2024-06-12 2:30 ` Thaddeus Woskowiak
2024-06-12 17:10 ` Thomas Nemeth
2024-06-12 12:51 ` hiro
2024-06-12 13:04 ` ori
2024-06-12 17:10 ` Thomas Nemeth
2024-06-12 19:34 ` Ori Bernstein
2024-06-12 21:55 ` Stanley Lieber
2024-06-12 17:03 ` Thomas Nemeth
2024-06-12 17:56 ` hiro
2024-06-12 18:11 ` Thomas Nemeth
2024-06-12 19:35 ` Ori Bernstein
2024-06-13 6:38 ` Thomas Nemeth
2024-06-14 20:11 ` hiro
2024-06-16 10:01 ` Thomas Nemeth
2024-06-16 13:03 ` Thaddeus Woskowiak
2024-06-16 14:27 ` Thomas Nemeth
2024-06-16 18:02 ` ori
2024-06-17 11:04 ` hiro
2024-06-16 18:00 ` ori
2024-06-16 20:20 ` Lyndon Nerenberg (VE7TFX/VE6BBM) [this message]
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=ec7c9db2559e4fc0@orthanc.ca \
--to=lyndon@orthanc.ca \
--cc=9front@9front.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).