From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] inquery: plans for phasing out cpu, rx and import
Date: Thu, 11 Aug 2016 09:47:51 +0100 [thread overview]
Message-ID: <00E66543-E527-4AC8-8756-4022A255FB6B@quintile.net> (raw)
In-Reply-To: <20160809153307.GA39931@wopr>
yep,
still on the labs code base.
btw. is there a documented way to jump ship to 9 front?
-Steve
> On 9 Aug 2016, at 16:33, Kurt H Maier <khm@sciops.net> wrote:
>
>> On Tue, Aug 09, 2016 at 11:09:41AM -0400, stanley lieber wrote:
>>
>> So we keep things like ftp and nfs clients in the base system but remove the ability to talk to Plan 9?
>>
>
> I didn't see this as removing support for a protocol so much as removing
> an older version of the protocol -- like not shipping support for nfsv1
> or whatever. I have reconsidered and I agree, we should keep them.
>
>> Disabling the listeners on 9front is obvious, and since Plan 9 is dead, maintenance is not really needed, but why remove it, exactly? Just to feel "clean"?
>
> Originally I supported removing them because they were completely
> superseded by rcpu et al; if what we have is sufficient, it would
> simplify code maintenance and documentation, presumably, to remove the
> cruft.
>
>> 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.
>
> This is what made me reconsider -- as long as sources is up, I don't
> like the idea of losing access to labs contrib. Obviously we could
> make it available with our tools...
>
> ... on the other hand, when was the last time any of us saw a labs plan
> 9 installation that wasn't some transient nerd totem, like a raspberry
> pi or something?
>
> Anyone on this list touch labs plan 9 on the regular?
>
> khm
next prev parent reply other threads:[~2016-08-11 8:47 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 [this message]
2016-08-09 17:44 ` cinap_lenrek
2016-08-09 17:56 ` stanley lieber
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=00E66543-E527-4AC8-8756-4022A255FB6B@quintile.net \
--to=steve@quintile.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).