From: mkf9 <mkf9@riseup.net>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] remove misleading BUGS from auth(8)
Date: Thu, 2 Jun 2022 22:51:49 +0430 [thread overview]
Message-ID: <ae83c1cc-72a4-0c7b-c8d3-8397881454a1@riseup.net> (raw)
In-Reply-To: <59969514-082b-4373-6134-71026b443362@posixcafe.org>
Jacob Moody wrote:
>> do different $services use different kernels in 9front
>> or it's a legacy of bell labs?
>>
>
> In 9front its all one kernel with different code paths depending on $service.
> From my understanding of the code this is mostly to set resource defaults,
> and different init scripts (/bin/termrc vs /bin/cpurc).
> If my history serves me correct they did used to actually be different
> builds. The wording here does give away how old this "bug" is. In any
> case, this section of the man page only serves to further confuse things.
> I've committed the change.
>
>
> Thanks,
> moody
>
I see, thank you.
next prev parent reply other threads:[~2022-06-02 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 17:28 Jacob Moody
2022-06-02 16:28 ` mkf9
2022-06-02 16:53 ` Jacob Moody
2022-06-02 18:21 ` mkf9 [this message]
2022-06-02 17:23 ` Stanley Lieber
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=ae83c1cc-72a4-0c7b-c8d3-8397881454a1@riseup.net \
--to=mkf9@riseup.net \
--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).