From: Mek101 <Mek101@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] [Package Request] wsdd or wsdd2
Date: Mon, 25 Jan 2021 10:34:14 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28216@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]
New issue by Mek101 on void-packages repository
https://github.com/void-linux/void-packages/issues/28216
Description:
Since NetBIOS discovery is not supported by Windows anymore, [wsdd](https://github.com/christgau/wsdd/) and [wssd2](https://github.com/Andy2244/wsdd2) daemons make hosts to appear in Windows again using the Web Service Discovery method.
I'm listing both of them because, while they serve the same thing, the first is just a python script, while the second is C implementation, and one may be easier to port and maintain than the other.
reply other threads:[~2021-01-25 9:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28216@inbox.vuxu.org \
--to=mek101@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).