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
Date: Thu, 25 Aug 2016 08:46:10 -0700 [thread overview]
Message-ID: <CAJ-Vmom1hsUxkXUwAn48E7B2zB_0TCPFiq_ud2Rhym5gvxzWDQ@mail.gmail.com> (raw)
In-Reply-To: <37d5159b-4957-42f8-2252-fa53d7446bb6@NTLWorld.com>
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
_______________________________________________
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-25 15:46 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 [this message]
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
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=CAJ-Vmom1hsUxkXUwAn48E7B2zB_0TCPFiq_ud2Rhym5gvxzWDQ@mail.gmail.com \
--to=adrian@freebsd.org \
--cc=J.deBoynePollard-newsgroups@ntlworld.com \
--cc=freebsd-hackers@freebsd.org \
--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).