From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: [9front] [NOTICE] /sys/lib/dist/ndb update and purposed removal
Date: Sun, 21 Apr 2024 14:38:01 -0500 [thread overview]
Message-ID: <75284c2f-a0c3-411b-91bc-81e15829e25e@posixcafe.org> (raw)
All,
We just pushed up a change to /sys/lib/dist/ndb to update some of the root servers as
well as add a script for keeping it updated. These are usually copied to /lib/ndb
when creating the iso image, so if you would like to update your current /lib/ndb on
an existing installation this will have to be manually copied.
Additionally I would like to purpose the removal of some of the code in /sys/lib/dist/ndb/common.
This seems a bit silly to ship with every install, and would like to clean this up. If anyone is
currently relying on these entries please reply on this thread.
Thanks,
moody
For ease the following is the snippet we would like to remove:
#
# authdom declarations need to be visible on the inside network,
# even for outside machines. putting them here ensures
# their visibility everywhere.
#
# bell labs
auth=sources.cs.bell-labs.com authdom=outside.plan9.bell-labs.com
# for geoff
auth=www.9netics.com authdom=9netics.com
auth=newcpu.9netics.net authdom=9netics.net
auth=mordor.tip9ug.jp authdom=tip9ug.jp
# for geoff's ipv6 testing
auth=9grid.hamnavoe.com
authdom=hamnavoe.com
authdom=9grid.hamnavoe.com
auth=whale.lsub.org
authdom=lsub.org
authdom=dat.escet.urjc.es
# for jmk
auth=tor.texas.9grid.us authdom=9grid.us
auth=9grid.net authdom=9grid.net
# for sape
auth=130.89.145.31 authdom=cs.utwente.nl
# for sl
auth=auth.stanleylieber.com authdom=inri
auth=mars2.inri.net authdom=mars2
auth=cb.inri.net authdom=nyc
next reply other threads:[~2024-04-21 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 19:38 Jacob Moody [this message]
2024-04-21 19:49 ` 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=75284c2f-a0c3-411b-91bc-81e15829e25e@posixcafe.org \
--to=moody@posixcafe.org \
--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).