From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] ssl deprecation
Date: Mon, 31 May 2021 13:55:48 +0200 [thread overview]
Message-ID: <05B34B036B7AB83D8B159A53FED697A6@felloff.net> (raw)
In-Reply-To: <143CF0E38A4C37EFF206B9E296969CC4@fulton.software>
and what todo with pushssl(2) and cpu(1), import(4) and oexportfs(4)?
if you kill devssl, you break any remoting supporting with inferno and
classic plan9.
i wanted to kill it along time ago especially as devssl had kernel
crash bugs. but you need to explain the consequences of your changes
clearly and stand the discussion with people wanting to run 9front
together with inferno and labs plan9 installations.
--
cinap
next prev parent reply other threads:[~2021-06-01 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 13:40 fulton
2021-05-31 11:55 ` cinap_lenrek [this message]
2021-06-01 22:04 ` 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=05B34B036B7AB83D8B159A53FED697A6@felloff.net \
--to=cinap_lenrek@felloff.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).