On Wed, 14 Nov 2018 17:13:15 -0800
Michael Forney wrote:
> On 2018-11-12, Sean MacLennan wrote:
> > I am surprised you are getting away with binding the socket to the
> > broadcast address.
>
> I found in ip(7):
>
> INADDR_BROADCAST (255.255.255.255) means any host and has the same
> eff
On 2018-11-12, Sean MacLennan wrote:
> I am surprised you are getting away with binding the socket to the
> broadcast address.
I found in ip(7):
INADDR_BROADCAST (255.255.255.255) means any host and has the same
effect on bind as INADDR_ANY for historical reasons.
So that explains why it wo
On 2018-11-13, Markus Wichmann wrote:
> On Mon, Nov 12, 2018 at 01:14:38PM -0800, Michael Forney wrote:
>> Usually how it works is either the display server itself needs to be
>> setuid to open those input devices, or some other program (commonly
>> systemd-logind) needs to open it on its behalf.
This is very cool :-)
Sent from my iPhone
> On 14 Nov 2018, at 20:37, Kurt Van Dijck
> wrote:
>
>> On ma, 12 nov 2018 13:14:38 -0800, Michael Forney wrote:
>>
>> Xorg seems to work similarly, and you might be able to avoid libudev
>> and retain hotplug support by writing a "netlink" config ba
On ma, 12 nov 2018 13:14:38 -0800, Michael Forney wrote:
>
> Xorg seems to work similarly, and you might be able to avoid libudev
> and retain hotplug support by writing a "netlink" config backend here:
> https://cgit.freedesktop.org/xorg/xserver/tree/config
Long ago, I wrote such handler, to rem
