From: james palmer <james@biobuf.link>
To: 9front@9front.org
Subject: Re: [9front] plan9.ini fs= should accept full dial strings
Date: Thu, 26 Aug 2021 12:31:37 +0100 [thread overview]
Message-ID: <0A85BD7D-C04C-4028-8168-B943DC56057F@biobuf.link> (raw)
In-Reply-To: <E2CAB4C3558CF4F09660E633BEDC47F8@5ess.inri.net>
Quoth sl@stanleylieber.com:
> let's say we want to do both serve a full file system
> to certain clients *and* serve a specially constructed
> namespace to generic clients trying to 9fs us on the
> standard port.
>
> currently, plan9.ini fs= value must be just an ip
> address or host name. the system translates it
> internally to tcp![ip]!564.
>
> why can't fs= be any valid dial string?
>
> sl
seems to be because the port depends onthe value of bootargs.
tcp boot is on 564 and tls boot is 17020.
to keep compatibility with existing plan9.ini files the fs variable would need to be parsed to see if a port has been specified.
another option might be to treat bootargs as a dialstring (similar to how local filesystems are handled) like so:
bootargs=local!/dev/sdE0/fs -> local hjfs
bootargs=tls!192.168.0.2 -> tls to the 192.168.0.2 file server
bootargs=tcp!biobuf.link!555 -> tcp boot to a remote file server on a non standard port
- james
prev parent reply other threads:[~2021-08-26 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 3:36 sl
2021-08-26 11:31 ` james palmer [this message]
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=0A85BD7D-C04C-4028-8168-B943DC56057F@biobuf.link \
--to=james@biobuf.link \
--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).