From: Steve Simon <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] bonjour mDNS?
Date: Sat, 2 Jan 2016 09:21:52 +0000 [thread overview]
Message-ID: <DCB4ED94-587D-460D-A16C-82568F5A344E@quintile.net> (raw)
In-Reply-To: <62E80203-4B7F-42FF-B75E-93B55D8FBE64@boschma.cx>
that would not work, because of how dns(1) presents its interface.
if the file server presented a directory of files then you can merge them.
however dns has a single file that you open, write a request to, and then later
read a reply from.
in this later form you merge the directories you just have two request files,
rather than one request file which offers the service of moth files.
I am not sure I have explained this very well, I hope you understand.
-Steve
> On 2 Jan 2016, at 05:17, Marc Boschma <marc@boschma.cx> wrote:
>
> Still getting my head around Plan9 but wouldn’t mounting the unicast and multicast DNS file servers over the top of each other work? (I assume the order of the mount (bind) would lead to resolution order… but maybe no unified responses.
>
> Marc
>
>> On 2 Jan 2016, at 2:42 pm, erik quanstrom <quanstro@quanstro.net> wrote:
>>
>> On Fri Jan 1 19:32:25 PST 2016, marc@boschma.cx wrote:
>>>
>>>> On 2 Jan 2016, at 7:05 am, Steve Simon <steve@quintile.net> wrote:
>>>> anyone done any work to implement mDNS / bonjour on plan9?
>>>
>>> No, but I have an interest; just starting out with Plan9 :)
>>>
>>>> my rough plan is to write a file server which generates /lib/ndb/mdns
>>>> which can be included into your /lib/ndb/local.
>>>>
>>>> I fear the biggest hassle is the clash of UDP port use may mean
>>>> mDNS must become part of dns(1) rather than a separate file server.
>>>
>>> Shouldn’t dns(1) only bind to unicast UDP port and thus mDNS could bind to the multicast UDP port?
>>>
>>> Are you only considering resolution or also publishing services?
>>
>> it would make sense to me to make a dnsudp request file server that manages requests, and
>> fork (ha!) that task off to it. this file server would not care if it's querying normal dns,
>> or mdns.
>>
>> - erik
>
next prev parent reply other threads:[~2016-01-02 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 20:05 Steve Simon
2016-01-02 3:30 ` Marc Boschma
2016-01-02 3:42 ` erik quanstrom
2016-01-02 5:17 ` Marc Boschma
2016-01-02 9:21 ` Steve Simon [this message]
2016-01-02 9:59 ` Marc Boschma
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=DCB4ED94-587D-460D-A16C-82568F5A344E@quintile.net \
--to=steve@quintile.net \
--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).