Re: First thoughts on s6

From: Colin Booth <cathexis_at_gmail.com>
Date: Tue, 16 Jun 2015 19:25:49 -0700

On Tue, Jun 16, 2015 at 5:44 PM, Steve Litt <slitt_at_troubleshooters.com> wrote:
> Hi all,
>
> I'd suggest a ./configure option called --urandom-instead, because this
> isn't the first time I've seen a /dev/random act like this, and
> probably most people don't want to pull the strongarm I did (I wouldn't
> either if it were a real machine).
>
Use --enable-force-devr and/or fix the entropy seed into the vm.
There's a bunch of other options for configure, and they are different
between skalibs and the rest of the packages. I'm sure there's
differences within the non-skalibs packages as well but I've never
bothered with them.
>
> * cat /service/tty5/log/main/current | tai64nlocal
>
> * cat /service/tty5/log/main/current | tai64n
>
> The former command worked as expected and printed out yyyy/mm/dd plus
> time timestamps. The latter command appeared to print out two different
> tai64n timestamps, both fairly close to each other but different.
>
Read the html documentation for those two commands, they are opposites.
>
> I think the following additions would make the s6 website a lot easier
> to use, and a lot easier for somebody to begin using s6:
>
> * FAQ
> * A page with simple files, including run and log/run for a tty.
>
> Here are the run files I used for tty5:
>
> For the service:
>
> #!/bin/sh
> exec 2>&1
> echo Starting tty5 >&2
> exec /sbin/getty tty5
>
Doesn't work on BSD. getty lives in /usr/libexec/ and at least by
default includes some extra type data. Also may want to set a baud
rate. You also don't need to redirect the echo since stderr and stdout
are going to the same place already.

This not working is part of the curse of the maintainer and why I
think a big collection of definitions that isn't tied to individual
packages is a mistake. In this case for the examples, Laurent went
with assuming getty is in the path (though it'll still fail on BSD
since /usr/libexec isn't in anyones path by default).
>
> For the tty5 log:
> #!/bin/sh
> exec s6-log t ./main
>
> They seemed to work well. Anyway, so far so good.
>

Cheers!
Received on Wed Jun 17 2015 - 02:25:49 UTC