Hello Lev,
Thursday, September 13, 2018, 2:46:46 AM, you wrote:
> Linux have openssl 1.1.0f, and I've tried both system /usr/bin/openssl
> (1.0.2p)
> and /usr/local/bin/openssl from security/openssl-devel port (1.1.0i), results
> are
> virtually the same. I have "ASM" and "SSE2" options
On 17 September 2018 at 14:17, Warner Losh wrote:
> Items on my list are:
>
> (1) Retiring boot1.efi entirely before 13.0. It was originally designed to
> be a small, never changing blob we'd toss into an ESP and have all the
> smarts in loader.efi.
I'd go further than this: it was originally
On Mon, Sep 17, 2018 at 12:17:25PM -0600, Warner Losh wrote:
> On Sun, Sep 16, 2018 at 11:29 PM Rebecca Cran wrote:
> I've had some interest on #bsdmips about booting a 64-bit FreeBSD on old
> > Apple systems that use 32-bit EFI: it sounds like it should be possible,
> > and is something I'd like
On Sun, Sep 16, 2018 at 11:29 PM Rebecca Cran wrote:
> On 9/16/18 9:32 PM, Warner Losh wrote:
>
> >
> > What did you have in mind working on? I have a few things that are in
> > various stages of completeness around this issue that I've not had
> > time to polish off for the tree. Some I'd like
On 9/10/18 1:20 PM, John Baldwin wrote:
> On 9/8/18 1:44 PM, Michael Butler wrote:
>> On 9/8/18 3:43 PM, Konstantin Belousov wrote:
>>> On Sat, Sep 08, 2018 at 02:07:41PM -0400, Michael Butler wrote:
On 8/31/18 1:28 AM, Konstantin Belousov wrote:
> On Fri, Aug 31, 2018 at 12:21:02AM
On 9/17/18 11:32 AM, Michael Butler wrote:
> On 9/10/18 1:20 PM, John Baldwin wrote:
>> On 9/8/18 1:44 PM, Michael Butler wrote:
>>> On 9/8/18 3:43 PM, Konstantin Belousov wrote:
On Sat, Sep 08, 2018 at 02:07:41PM -0400, Michael Butler wrote:
> On 8/31/18 1:28 AM, Konstantin Belousov
On 16.09.2018 03:04, Larry Rosenman wrote:
> vpanic() at vpanic+0x1a3/frame 0xfe00ca17c150
> panic() at panic+0x43/frame 0xfe00ca17c1b0
> trap_fatal() at trap_fatal+0x35f/frame 0xfe00ca17c200
> trap_pfault() at trap_pfault+0x49/frame 0xfe00ca17c260
> trap() at trap+0x2ba/frame
Hello,
I'm short before updating my poudriere oven, a Dell PowerEdge r210, from
r318593 to r338641. I have there a ZFS in use for poudriere, created
with:
# zpool create poudriere /dev/da1
and set in /usr/local/etc/poudriere.conf:
ZPOOL=poudriere
ZROOTFS=/poudriere
# zpool
On Fri, 14 Sep 2018 at 02:12, Lev Serebryakov wrote:
>
> Hello John,
>
> Friday, September 14, 2018, 1:44:13 AM, you wrote:
>
> >> % grep aesni ~/nanobsd/gatevay.v3/J3160
> >> device aesni
>
> > From my understanding of the OpenSSL code, it doesn't use the kernel driver
> > at all (the
On 17.09.2018 10:40, Daniel Nebdal wrote:
> Could it be relevant that the Debian binary was probably compiled with
> gcc, and the FreeBSD binary with clang?
Maybe. Now I'm trying to trace codepath of "openssl speed -evp
aes-256-cbc" on FreeBSD to understand where and why it refuses to use
AES.
I'm preparing some benchmarking setup, which includes gif tunnel from
FreeBSD to FreeBSD, where one end is 12.0-ALPHA6/r338707 installed as
guest in VirtualBox with virtual NIC (vtnet).
This tunnel works for simple pings, but when I run iperf3 on this
"link" ALPHA4 system crashes. It is 100%
Hi,
I am trying out 12.0-ALPHA6-amd64-20180914-r338675 vmdk with a VM with two
CPUs.
When doing "shutdown -h now" I get a lock order reversal, is this expected?
According to https://www.freebsd.org/doc/faq/troubleshoot.html#idp59076936 it
is possible to get false positives from witness.
12 matches
Mail list logo
