On Wed, Jan 08, 2014 at 03:53:32PM -0500, Ted Unangst wrote:
> This may or may not be useful. We can embed the message after the
> signature and reduce the number of files in half. It's not a lot of
> code. (This is how the crypto_sign API originally worked, but we've
> since added some metadata, s
This may or may not be useful. We can embed the message after the
signature and reduce the number of files in half. It's not a lot of
code. (This is how the crypto_sign API originally worked, but we've
since added some metadata, so we still need to destruct and
reconstruct the crypto_sign inputs an
We don't need this mapping anymore. For some time now we have been mapping
the tramps later (and this code entered a mapping for PA 0x3000, a page
which we weren't even using anyway).
Part of the ongoing effort to clean up the tramps and low mem mappings.
Tested lightly on a couple of i386 SMP not
On 8 January 2014 12:02, Martin Pieuchot wrote:
> I find it really difficult to understand and work with the code of
> rtsock.c because of the following defines:
>
>
> /* Sleazy use of local variables throughout file, warning */
> #define dstinfo.rti_info[RTAX_DST]
>
I find it really difficult to understand and work with the code of
rtsock.c because of the following defines:
/* Sleazy use of local variables throughout file, warning */
#define dstinfo.rti_info[RTAX_DST]
#define gate info.rti_info[RTAX_GATEWAY]
...
But
I haven't tried auto-install yet, but as long as the normal
siteXX.tgz/install.site mechanism works, you should be able to handle kernel
config changes with a scripted run of 'config -ef /mnt/bsd'. You would need a
custom ramdisk too: again config -ef will let you save these changes in the
on-d
Am 08-01-2014 03:06, schrieb Theo de Raadt:
Am 08-01-2014 03:02, schrieb Aleksandar Lazic:
Am 08-01-2014 02:50, schrieb Theo de Raadt:
> Autoinstall does not handle this type of problem either.
Is there a plan to be able to handle such a problem with autoinstall?
Yes... get a CF card which
One problem I have seen with autoinstall is that sequence
of lines in install.conf is important.
It seems not to much to closes pattern. For example if you put
'Start ntpd(8) by default' and 'NTP server' (IIRC) in the
beginning it would impact answers to questions having 'server'
in the question.
