From: eso@self.rodeo
To: 9front@9front.org
Subject: Re: [9front] panic on hjfs fshalt
Date: Fri, 29 Dec 2023 13:38:37 -0800 [thread overview]
Message-ID: <0e03ae4bd466455c37bde891ddbe81b3@self.rodeo> (raw)
In-Reply-To: <799925dd-9ed5-499b-aed8-09d78e199a99@posixcafe.org>
> mk nuke
> mk libs
thanks, that's what i was forgetting. still getting used to the
consequences of "programs should do one thing well". most operating
systems recompile for you, not to say plan 9 should, but to say that
plan 9 expects you to make those decisions yourself.
sorry for the borked attachment btw
next prev parent reply other threads:[~2023-12-29 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 2:35 eso
2023-12-29 3:26 ` Thaddeus Woskowiak
2023-12-29 4:11 ` cinap_lenrek
2023-12-29 4:41 ` Thaddeus Woskowiak
2023-12-29 6:38 ` eso
2023-12-29 6:54 ` Jacob Moody
2023-12-29 21:38 ` eso [this message]
2023-12-29 3:39 ` Thaddeus Woskowiak
2023-12-29 5:22 ` ori
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=0e03ae4bd466455c37bde891ddbe81b3@self.rodeo \
--to=eso@self.rodeo \
--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).