Updating src tree:
P src/bin/kill/kill.c
P src/bin/sh/Makefile
P src/bin/sh/jobs.c
P src/bin/sh/trap.c
P src/lib/libcurses/addch.c
P src/lib/libcurses/attributes.c
P src/lib/libcurses/ctrace.c
P src/lib/libcurses/curses_private.h
P src/lib/libcurses/refresh.c
U src/sys/arch/aarch64/aarch64/efi_ma
Date:Sun, 28 Oct 2018 13:14:34 +0100
From:Michael van Elst
Message-ID: <20181028121433.ga20...@serpens.de>
| On Sun, Oct 28, 2018 at 04:45:58PM +0700, Robert Elz wrote:
|
| > 1. when the firmware is told to boot
| > 2. when the boot loader gets control from
This is an automatically generated notice of new failures of the
NetBSD test suite.
The newly failing test cases are:
net/npf/t_npf:npf_bpf
net/npf/t_npf:npf_nat
net/npf/t_npf:npf_nbuf
net/npf/t_npf:npf_rule
net/npf/t_npf:npf_state
net/npf/t_npf:npf_table
The above tests
On Sun, Oct 28, 2018 at 04:45:58PM +0700, Robert Elz wrote:
> 1. when the firmware is told to boot
> 2. when the boot loader gets control from the firmware
> 3. when the kernel first starts executing.
3a. when the kernel has started clock
3b. when the kernel has mounted root
> 4. When the kern
Date:Sun, 28 Oct 2018 07:45:12 - (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID:
| We could save the uptime value at that point and make dmesg -T adjust
| the timestamps accordingly
I think we need to define just what is boottime? sysctl(7) is
g...@pobox.com (Geoff Wing) writes:
>From my quick look, sys/kern/init_main.c:666 initialises boottime
>after mounting the root file system, so "dmesg -T" is using a bad
>value.
When there is no TOD clock, the time is deduced from the timestamp in the
superblock of the root filesystem. That's why
