Date: Thu, 25 Aug 2016 08:46:10 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@ntlworld.com> Cc: Supervision <supervision@list.skarnet.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Linuxisms in s6 Message-ID: <CAJ-Vmom1hsUxkXUwAn48E7B2zB_0TCPFiq_ud2Rhym5gvxzWDQ@mail.gmail.com> In-Reply-To: <37d5159b-4957-42f8-2252-fa53d7446bb6@NTLWorld.com> References: <37d5159b-4957-42f8-2252-fa53d7446bb6@NTLWorld.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. :) -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmom1hsUxkXUwAn48E7B2zB_0TCPFiq_ud2Rhym5gvxzWDQ>