9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Edouard Klein <edou@rdklein.fr>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Content of your /rc/bin/service or /dis/svc ?
Date: Wed, 06 Mar 2024 12:06:08 +0100	[thread overview]
Message-ID: <87o7brzkjc.fsf@rdklein.fr> (raw)
In-Reply-To: <17096788450.Ee6a0bf7D.15037@composer.9fans.topicbox.com>


a@9srv.net writes:

> I wonder what percentage of people who reply are going to be running a finger server they wrote. :-) My tcp79 comes from my implementation, here:
> http://txtpunk.com/finger/index.html
>
> I think we've got enough interoperable unicode-aware implementations we can start working on the update to the RFC now.
>
> I have a service which allows some unix hosts I run to submit vac scores after they perform a backup to my venti; a slightly outdated version is here:
> https://9p.io/sources/contrib/anothy/bin/rc/tcp17038
>
> tcp411 calls pqsrv, I think the same version as on the "extra" page: http://9p.io/sources/extra/
>
> I usually have at least one "poor man's nat traversal" thing running with aux/trampoline.
>
> I love how easy aux/listen makes sticking trivial little services up on the net. I used to have one that provided a menu of MUDs to connect to. Another gave the weather, as the telnet
> service at Weather Underground started to go unmaintained (of course, mine used darksky, which is now also defunct).

I forgot to mention: you may be interested about:

finger paris@graph.no

>I made a little text-based zine server (inspired by Cara Esten's
> https://github.com/caraesten/dial_a_zine, which powered the things at anewsession.com); that's up, although very lightly used: http://txtpunk.com/zine/
>
> Before life got away from me last year, I was trying to get a VoIP bridge working so I could plug a POTS line into my modem and get telcodata working again. I think 'cp tcp2323
> telcodata' should be enough to make that zine server dialable. (Sadly, I've only gotten the bridge to *place* calls over my crummy DSL line.)
>
> As a young unix sysadmin back in the 1900s, aux/listen was one of the first things that caught my eye about Plan 9, in comparison to inetd and the direction everyone else was headed
> from there. Certainly the growth (in multiple senses) of systemd has only tightened my grip on that particular tool.
> 9fans / 9fans / see discussions + participants + delivery options Permalink

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tf73851503467346f-Mc5c3a50fb7cce6b9b57854d2
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  parent reply	other threads:[~2024-03-06 11:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02 10:34 Edouard Klein
2024-03-02 11:54 ` sirjofri
2024-03-05 21:28   ` Edouard Klein
2024-03-05 21:59     ` sirjofri
2024-03-05 22:47       ` a
2024-03-06  0:53         ` hiro
2024-03-06 11:03           ` Edouard Klein
2024-03-06 10:42         ` Edouard Klein
2024-03-06 11:06         ` Edouard Klein [this message]
2024-03-06 10:28       ` Edouard Klein
2024-03-06 12:52         ` sirjofri
2024-03-06 15:12           ` Edouard Klein

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=87o7brzkjc.fsf@rdklein.fr \
    --to=edou@rdklein.fr \
    --cc=9fans@9fans.net \
    /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).