9front - general discussion about 9front
 help / color / mirror / Atom feed
From: stanley lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] inquery: plans for phasing out cpu, rx and import
Date: Tue, 09 Aug 2016 13:56:06 -0400	[thread overview]
Message-ID: <05638c9d-a2c6-4437-b87e-12d11e887b71@email.android.com> (raw)
In-Reply-To: <ec636efe19eab6ea525f1d5165c4340e@felloff.net>

cinap_lenrek@felloff.net wrote:

>> We still keep a lot of other dirty stuff, specifically so we can talk
>to other outmoded servers that are not even Plan 9. Maybe Plan 9
>systems are so rare it doesn't matter, but this policy seems quite
>randomly applied.
>
>correct, but theres a difference there. cpu and import are our native
>plan9 protocols. for foreign protocols you cannot do much, if they
>are bad and widely deployed. while cpu and import deployment is
>assumingly
>much smaller as we used it mostly ourselfs. so the responsibility of
>cleaning up the mess is on us i think... before anyone gets hurt.
>
>disabling the listener is a good first step, maybe many people will
>whine about it. but i doubt it. lets see.
>
>speaking of other outmoded servers, openssh deleted sshv1 protocol
>support.
>
>> sl
>
>--
>cinap

9front users don't need old cpu at all. The only reason I recommend keeping it is so we can continue talking to Plan 9. Those old Plan 9 systems don't have the option of using rcpu and friends instead of old cpu. It just seems weird to chop off those legacy systems completely, since the Plan 9 world does not consist solely of 9front.

I agree that the number of Plan 9 systems is decreasing and it probably doesn't really matter. In the end, anyone who really needs old cpu on 9front will be capable of grabbing it from /n/extra.

Pointing out that ssh1 is deprecated is not really a like comparison, because ssh servers now mostly offer ssh2. Old Plan 9 cannot offer rcpu.

sl



  reply	other threads:[~2016-08-09 17:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06 19:39 cinap_lenrek
2016-08-07  2:25 ` [9front] " sl
2016-08-07 23:55   ` kokamoto
2016-08-08  1:37     ` sl
2016-08-08  7:38       ` kokamoto
2016-08-08 15:22         ` stanley lieber
2016-08-08 15:53           ` hiro
2016-08-08 16:33             ` cinap_lenrek
2016-08-09  9:45               ` hiro
2016-08-09 14:57                 ` Kurt H Maier
2016-08-09 15:12                   ` stanley lieber
2016-08-09 17:46                   ` cinap_lenrek
2016-08-09 15:09                 ` stanley lieber
2016-08-09 15:33                   ` Kurt H Maier
2016-08-11  8:47                     ` Steve Simon
2016-08-09 17:44                   ` cinap_lenrek
2016-08-09 17:56                     ` stanley lieber [this message]
2016-08-09 17:49                   ` cinap_lenrek
2016-08-09 17:59                     ` stanley lieber
2016-08-10 10:04                       ` hiro
2016-08-08 15:54           ` cinap_lenrek

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=05638c9d-a2c6-4437-b87e-12d11e887b71@email.android.com \
    --to=sl@stanleylieber.com \
    --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).