From: Warner Losh <imp@bsdimp.com>
To: Jan Bramkamp <crest@rlwinm.de>
Cc: Supervision <supervision@list.skarnet.org>,
Adrian Chadd <adrian@freebsd.org>,
Jonathan de Boyne Pollard
<J.deBoynePollard-newsgroups@ntlworld.com>,
Lars Engels <lars.engels@0x20.net>,
FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject: Re: Linuxisms in s6
Date: Fri, 26 Aug 2016 08:11:43 -0600 [thread overview]
Message-ID: <CANCZdfqN4keZ0QZSTv3oa_ZdDg_CGnqPPP6ysRhW3OUaUULaYg@mail.gmail.com> (raw)
In-Reply-To: <bed7950d-cdf1-724a-02ef-4bfa1864a053@rlwinm.de>
On Fri, Aug 26, 2016 at 4:44 AM, Jan Bramkamp <crest@rlwinm.de> wrote:
> On 25/08/16 23:17, Adrian Chadd wrote:
>>
>> On 25 August 2016 at 14:13, Warner Losh <imp@bsdimp.com> wrote:
>>>
>>> On Thu, Aug 25, 2016 at 3:08 PM, Adrian Chadd <adrian@freebsd.org> wrote:
>>>>
>>>> On 25 August 2016 at 12:48, Lars Engels <lars.engels@0x20.net> wrote:
>>>>>
>>>>> On Thu, Aug 25, 2016 at 08:46:10AM -0700, Adrian Chadd wrote:
>>>>>>
>>>>>> On 24 August 2016 at 21:53, Jonathan de Boyne Pollard
>>>>>> <J.deBoynePollard-newsgroups@ntlworld.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>> http://adrianchadd.blogspot.co.uk/2016/08/freebsd-on-tiny-system-whats-missing.html?showComment=1471236502051#c1305086913155850955
>>>>>>> , Adrian Chadd:
>>>>>>>
>>>>>>>> We're using s6 at work, and it works out mostly ok. Mostly once you
>>>>>>>> get
>>>>>>>> around the linuxisms, and the lack of sensible time code in it (its
>>>>>>>> calculations for daemon run duration is based on system time, not
>>>>>>>> wall
>>>>>>>> clock, so if your box boots jan 1, 1970 then gets NTP, things are..
>>>>>>>> hilarious), and some of the arcane bits to get logging working
>>>>>>>> right.
>>>>>>>>
>>>>>>> What are these Linuxisms in s6? s6-linux-utils and s6-linux-init
>>>>>>> have
>>>>>>> Linuxisms, obviously. But what Linuxisms does s6 have?
>>>>>>
>>>>>>
>>>>>> We just had a bunch of fun trying to get it to build right, and the
>>>>>> uptime stuff really threw us.
>>>>>>
>>>>>> It's fine though, I found that s6 may start growing an IPC mechanism
>>>>>> so we could possibly do a launchd/jobd style service later (ie to run
>>>>>> things upon event changes, like ifup, ifdown, ifcreate, ifdestroy,
>>>>>> arbitrary messages, etc) so I may try incorporating it again. :)
>>>>>>
>>>>>
>>>>> Can't this be done with devd?
>>>>
>>>>
>>>> Sure, but I'm looking for something more generic than just devd. Like,
>>>> notifications about events like "default route is up" can be done by
>>>> sniffing the rtsock, but notifications like "ntpdate has updated the
>>>> date, we can now do crypto services" doesn't happen there right now.
>>>
>>>
>>> devd was never intended to be limited to just device events from the
>>> kernel. It has grown beyond that, and could easily grow to cope with
>>> routing events and other notifications. No need to reinvent everything
>>> for that.
>>
>>
>> Right. I don't want to reinvent the wheel if it can be avoided.
>
>
> Afaik devd is limited handling events reported by the kernel on /etc/devctl.
> There is no way to inject events into arbitrary events from userspace into
> devd (no ptrace hacks don't count).
It would be trivial to add though, especially since the author is easy to
work with :). It already fans out data to multiple listeners.
Warner
_______________________________________________
freebsd-hackers@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
next prev parent reply other threads:[~2016-08-26 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 4:53 Jonathan de Boyne Pollard
2016-08-25 9:56 ` Jan Bramkamp
2016-08-25 15:46 ` Adrian Chadd
2016-08-25 19:48 ` Lars Engels
2016-08-25 21:08 ` Adrian Chadd
2016-08-25 21:13 ` Warner Losh
2016-08-25 21:17 ` Adrian Chadd
2016-08-26 10:44 ` Jan Bramkamp
2016-08-26 14:11 ` Warner Losh [this message]
2016-08-27 16:37 ` Jonathan de Boyne Pollard
2016-08-28 1:58 ` Adrian Chadd
2016-08-27 13:38 ` Jonathan de Boyne Pollard
2016-08-27 16:51 ` Jonathan de Boyne Pollard
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=CANCZdfqN4keZ0QZSTv3oa_ZdDg_CGnqPPP6ysRhW3OUaUULaYg@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=J.deBoynePollard-newsgroups@ntlworld.com \
--cc=adrian@freebsd.org \
--cc=crest@rlwinm.de \
--cc=freebsd-hackers@freebsd.org \
--cc=lars.engels@0x20.net \
--cc=supervision@list.skarnet.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).