>On Wed, Jun 18, 2014 at 11:47 AM, Matthew Dempsky <[email protected]> wrote:
>> On Wed, Jun 18, 2014 at 5:32 AM, David Higgs <[email protected]> wrote:
>>> While upgrading my snapshot VMs this morning, bsd.rd on both the i386
>>> and amd64 produced 'Bad System Call' somewhere between making device
>>> nodes and reboot.
>>
>> That might happen if the bsd.rd you're using for the upgrade process
>> is older than the sets you're installing. We added a new system call
>> (getentropy(2)) in the last few days, and libc is already making use
>> of it.
>>
>> If you can reproduce the issue with a fully up-to-date bsd.rd, then
>> I'd be interested in tracking down what's going on.
>
>Interesting, I didn't know that bsd.rd made use of installed
>components - I had assumed it was fully self-contained, hence my
>surprise/confusion.
Yes, it does. Highly unfortunate.
encrypt
mtree
pwd_mkdb
These will not fit into instbin without substantial refit, especially
mtree.
