Hi there,
we got some Problems with init.
init died (signal 11 exit 0)
after using reboot(8) without any flags.
after some investigation i saw that in reboot(8)
at line 241 folling code starts:
for (i = 1;; ++i) {
if (kill(-1, SIGKILL) == -1) {
Hi there,
i think i found a bug in the build process, im not able to build miniroot
with multiple processes through - for example - 'make -j4'
$ pwd
/usr/src/distrib/amd64/ramdisk_cd
$ sudo make -j 4
awk -f /usr/src/distrib/amd64/ramdisk_cd/../../miniroot/makeconf.awk
CBIN=instbin
I restored the functionality according to the manpage.
That means that read() on bpf is blocking again. If a
timeout is set read() will block until the timeout is
over.
Maybe asynchronous is also broken, i will look into that later.
Index: sys/net/bpf.c
-0800,
Mike Larkin wrote:
On Thu, Nov 27, 2014 at 12:44:54PM +0100, Mages, Simon wrote:
Hi there,
the temperatures 'sysctl hw.sensors' displays for each CPU
are wrong for the most modern Intel CPUs.
OpenBSD uses only 100 or 85 degC as TJmax for Intel CPUs, but
in reality the TJmax
Thank you, fixed.
Index: sys/arch/amd64//amd64/identcpu.c
===
RCS file: /home/cvs/src/sys/arch/amd64/amd64/identcpu.c,v
retrieving revision 1.54
diff -u -p -r1.54 identcpu.c
--- sys/arch/amd64//amd64/identcpu.c13 Jul 2014
Hi,
tcpdump feels a bit laggy or slow some times when i use it for live debugging.
The following patch adds a new flag, '-b', to tcpdump. With this flag, tcpdump
sets BIOCIMMEDIATE for the current bpf(4) interface. With BIOCIMMEDIATE set,
the output is fluent.
Index: usr.sbin/tcpdump/privsep.c
Hi,
if BIOCGRTIMEOUT is set, we should wait for the timeout and not just
set EWOULDBLOCK. From my point of view the whole 'if' is unnecessary.
If the User doesn't set a timeout we have to wait anyway with tsleep()
and loop again. Well, and if the timeout is set, we should tsleep()
for the set
Hi there,
the temperatures 'sysctl hw.sensors' displays for each CPU
are wrong for the most modern Intel CPUs.
OpenBSD uses only 100 or 85 degC as TJmax for Intel CPUs, but
in reality the TJmax value is somewhere around those specified
values. Intel defines a TJmax for every production batch
