s6-rc: 0.0.2.1
s6: 2.2.4.3
skalibs: 2.3.9.0
Yeah, all bets are off with those versions - in particular the old
skalibs, a lot of bugs have been fixed since then.
I'll release a new s6-rc before next week; and if the s6-rc-init crash
happens again then I'll look into it.
--
Laurent
On 2017-10-03 11:11, Laurent Bercot wrote:
>> Do you plan to do a bugfix release soon'ish?
>
> I can do one some time later this week if you need it. However, if
> it's not urgent,
It's not that urgent, but it would be nice to have a rough idea of when
you might roll the release, and preferable
Do you plan to do a bugfix release soon'ish?
I can do one some time later this week if you need it. However, if
it's not urgent, I'd like some time to investigate the s6-rc-init crash
you reported, if it's still happening for you. I cannot reproduce it
so far.
--
Laurent
On 2017-10-02 11:58, Rasmus Villemoes wrote:
> On 2017-09-30 12:24, Laurent Bercot wrote:
>>
>> In the latest s6-rc git, s6-rc-update now creates its new livedir with
>> mkdtemp() and does not use any cryptographically strong random number
>> generation.
>>
>> Please test it and tell me if it
On 2017-09-30 12:24, Laurent Bercot wrote:
>
> In the latest s6-rc git, s6-rc-update now creates its new livedir with
> mkdtemp() and does not use any cryptographically strong random number
> generation.
>
> Please test it and tell me if it works for you.
A quick test shows that the board
In the latest s6-rc git, s6-rc-update now creates its new livedir with
mkdtemp() and does not use any cryptographically strong random number
generation.
Please test it and tell me if it works for you.
--
Laurent
src/librandom/random_makeseed.c says that that's precisely the point; I
was quoting verbatim.
Ah, indeed. My mistake. Full disclosure: at first I wanted to speed up
the /dev/urandom initialization. Then, after careful re-reading of the
Linux man pages, I realized it wouldn't work; but I found
On 2017-09-26 17:47, Laurent Bercot wrote:
>
>> On a modern linux system, s6-rc-update ends up calling getrandom(2) via
>> the random_sauniquename() library function. But on embedded systems, and
>> especially during early initialization, that is likely to block, which
>> means that the entire
On a modern linux system, s6-rc-update ends up calling getrandom(2) via
the random_sauniquename() library function. But on embedded systems,
and
especially during early initialization, that is likely to block, which
means that the entire boot process hangs.
Yes. That's a feature. You
On a modern linux system, s6-rc-update ends up calling getrandom(2) via
the random_sauniquename() library function. But on embedded systems, and
especially during early initialization, that is likely to block, which
means that the entire boot process hangs.
No, writing 160 bytes of crap to
10 matches
Mail list logo
