9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Staying up-to-date
Date: Sun, 16 Jun 2024 14:00:29 -0400	[thread overview]
Message-ID: <E7CA6583020215A2D55AC14DF9DE809D@eigenstate.org> (raw)
In-Reply-To: <4898776.GXAFRqVoOG@cixi>

Quoth Thomas Nemeth <tnemeth@free.fr>:
> Le vendredi 14 juin 2024 22:11:48 CEST, vous avez écrit :
> > the best is to pxe boot from a proper fileserver and learn to forget
> > all those sd card problems.
> 
>     That's an idea, indeed. Seen it in the FQA.
> 
>     Although I'm quite familiar with PXE, BOOTP and DHCP due to my work
>     on Linux embedded systems for ~25y, I'm not when it's related to
>     Plan9 and I find the documentation hard to follow -_-;
> 
>     It seems to be Plan9-fileserver oriented (obviously).
> 
>     In the mean time I was looking at `man 8 fs` and found that the
>     fs "check" command could be used to check for a filesystem
>     integrity. But it's nowhere to be found on the console (in the
>     current state of my research).

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.

>     I also wanted to know which filesystems where mounted and couldn't
>     find it in the man pages of the commands specified in the
>     unix2plan9 wiki page. Thanks to fshalt I found out that the root
>     filesystem was hjfs :)
> 
>     Even though I've been playing occasionally with Plan9 and then
>     9front for ~10y, I still don't feel confident enough for system
>     administration.

Yes, it's not difficult, but it's certainly different. A smaller
community also means a lot less documentation.


  parent reply	other threads:[~2024-06-16 18:02 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11 14:57 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 [this message]
2024-06-16 20:20                   ` [9front] Out-of-date and obsolete documentation Lyndon Nerenberg (VE7TFX/VE6BBM)

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=E7CA6583020215A2D55AC14DF9DE809D@eigenstate.org \
    --to=ori@eigenstate.org \
    --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).