Re: give cron a sensible default max load_avg for batch jobs

On 2015 Nov 13 (Fri) at 20:28:01 -0700 (-0700), Todd C. Miller wrote: :On Fri, 13 Nov 2015 16:45:44 -0700, Theo de Raadt wrote: : :> > This patch changes the default setting to 1.5 * :> > (number_of_cpus_in_system) instead, which I find better matches modern :> > behaviour. :> :> A larger number

Chacha20-Poly1305 PFKEYv2 number

Hi, Since there are no IANA numbers assigned for transformations in PFKEYv2 messages we have been following ISAKMP registry and then with GCM have switched to the IKEv2 registry. The only reason to do so [that I can think of] and not just pick a consecutive number is in hopes of userland

Re: [patch] gprof(1): fix incompatible pointer types

On Tue, 10 Nov 2015, Serguey Parkhomovsky wrote: > Some of the comparator functions in gprof(1) have incompatible pointer > types and generate compiler warnings. The following diff fixes the > problem. Your diff is a step forward, yes. I think it's slightly improved to add more 'const's so

Re: Chacha20-Poly1305 PFKEYv2 number

Mike Belopuhov: > Should we maybe just list them all in a consecutive order > w/o adherence to a particular standard and eliminate gaps > so that checks for "greater than SADB_EALG_MAX" actually > make sense? Or do we want to continue following IKEv2 > registry? I'm fine with either approach.

Re: Pledge for Vi and Ex

Gregor Best writes: > Hi people, > > inspired by someone on Hackernews talking about how hard it would be to > properly pledge an editor, here's a patch to pledge Vi and Ex. I'd like to investigate the ideas you mentioned: disabling proc/exec with -S and making -R actually read-only. But both of

Re: Pledge for Vi and Ex

Gregor Best writes: > @@ -229,6 +230,14 @@ editor(GS *gp, int argc, char *argv[]) > } > if (LF_ISSET(SC_EX) && F_ISSET(gp, G_SCRIPTED)) > silent = 1; > + > + if (secure) { > + if (pledge("stdio rpath wpath cpath fattr flock tty", NULL)) > +

Re: PC Engines APU2 coming soon - how is OpenBSD's support so far?

Mathias Schmocker [s...@smat.ch] wrote: > > First tests with a bootable OpenBSD amd64 5.8-current USB stick and > installation on the 16GB mSata internal storage. > After reboot, BIOS could find mSata to boot on, but defaulted to the memtest > boot payload > This is a setting you can change,

Re: give cron a sensible default max load_avg for batch jobs

> >>> This patch changes the default setting to 1.5 * > >>> (number_of_cpus_in_system) instead, which I find better matches modern > >>> behaviour. > >> > >> A larger number is sensible in this position. > >> > >> I would propose 8. I don't agree with a calculation like that; the > >> amount of

Re: Why OpenBSD uses monolithic kernel?

On 2015/11/14 23:24, Delan Azabani wrote: > When deciding whether and how to reply to this thread, perhaps take a > look at the previous posts that this person has made to misc@. > And freebsd-questions, freebsd-hackers, python-dev, 9fans, dragonfly-kernel, linux-kernel, fedora-devel-list,

Re: PC Engines APU2 coming soon - how is OpenBSD's support so far?

Hello, APU2 BETA TEST 4GB version with: SeaBIOS (version rel-1.8.0-181-g0af5958) BUILD: gcc: (Ubuntu 4.8.4-2ubuntu1~14.04) 4.8.4 binutils: (GNU Binutils for Ubuntu) 2.24 <...> Running option rom at c000:0003 Google, Inc. Serial Graphics Adapter 08/22/15 SGABIOS $Id: sgabios.S 8

Re: Chacha20-Poly1305 PFKEYv2 number

On Sat, Nov 14, 2015 at 13:27 +0100, Mike Belopuhov wrote: > Hi, > > Since there are no IANA numbers assigned for transformations > in PFKEYv2 messages we have been following ISAKMP registry > and then with GCM have switched to the IKEv2 registry. The > only reason to do so [that I can think of]

Re: give cron a sensible default max load_avg for batch jobs

The quesion no one seems to be asking here is "who actually runs batch". Anyone? - todd

Re: MALLOC_STATS and pledge

Might be indeed, there are other use cases with valgrind and protexec and so on ..., utrace might be a good suggestion too except maybe a need for an exception in pledge's side then. On 13 November 2015 at 18:34, Ted Unangst wrote: > David CARLIER wrote: >> Hi all, >> >> I

Why OpenBSD uses monolithic kernel?

In all references that I have read, monolithic kernels are known for being cumbersome, difficult to maintain, difficult to debug, coding in kernel is very challenging, a faulty part of kernel can bring down the whole system and so on ... . On the other hand, hybrid kernels and micro-kernels have

Re: MALLOC_STATS and pledge

On 2015/11/14 14:01, David CARLIER wrote: > Might be indeed, there are other use cases with valgrind and protexec > and so on ..., utrace might be a good suggestion too except maybe a > need for an exception in pledge's side then. btw, valgrind currently ssems to be quite broken with pledge.

Re: Why OpenBSD uses monolithic kernel?

When deciding whether and how to reply to this thread, perhaps take a look at the previous posts that this person has made to misc@.

increase initialization time for serverworks sata

I have a machine here were SATA disks fail to attach on boot: pciide0 at pci8 dev 12 function 0 "ServerWorks K2 SATA" rev 0x00: DMA pciide0: using irq 0 for native-PCI interrupt pciide0: port 0: unknown SStatus: 0x0005 pciide0: port 0: PHY offline pciide0: port 1: PHY offline pciide0: port 2:

Re: utf8 in rs

Hi, Christian Weisgerber wrote on Fri, Oct 23, 2015 at 03:52:31PM +0200: > Ted Unangst: >> I'm very scared to try counting chars vs bytes upfront in such code. Actually, that turns out to be simple. > I think that's insufficient to cover rs's functionality. -z will > overestimate the required

Re: utf8 in rs

Ingo Schwarze wrote: > I think that way we can actually start committing such patches and > improve our userland. > > Two final notes: > > 1. It turns out each of the three programs needs exactly one > multibyte-character helper function in utf8.c, and each helper > function uses

Re: give cron a sensible default max load_avg for batch jobs

On 2015-11-14 09:54, li...@wrant.com wrote: >>> I think 8 is way to high. Isn't the point of batch to run things >>> when the machine is mostly idle? >> The problem is (and we've had this discussion several times before at >> least in misc@), that the system load doesn't really tell us that. >

Re: MALLOC_STATS and pledge

> On 2015/11/14 14:01, David CARLIER wrote: > > Might be indeed, there are other use cases with valgrind and protexec > > and so on ..., utrace might be a good suggestion too except maybe a > > need for an exception in pledge's side then. > > btw, valgrind currently ssems to be quite broken with

Re: increase initialization time for serverworks sata

> Date: Sat, 14 Nov 2015 16:59:56 + > From: Miod Vallat > > I have a machine here were SATA disks fail to attach on boot: > > pciide0 at pci8 dev 12 function 0 "ServerWorks K2 SATA" rev 0x00: DMA > pciide0: using irq 0 for native-PCI interrupt > pciide0: port 0: unknown

Re: increase initialization time for serverworks sata

> Don't tell me this fixes SATA on the xserve G5... I did try that back in the day. I cranked all the delays, and nothing helped. No interrupts came in, ever.

Re: PC Engines APU2 coming soon - how is OpenBSD's support so far?

Le 14.11.15 17:02, Chris Cappuccio a écrit : > Mathias Schmocker [s...@smat.ch] wrote: >> >> First tests with a bootable OpenBSD amd64 5.8-current USB stick and >> installation on the 16GB mSata internal storage. >> After reboot, BIOS could find mSata to boot on, but defaulted to the memtest >>

Re: give cron a sensible default max load_avg for batch jobs

On 2015-11-14 13:57, Todd C. Miller wrote: > The quesion no one seems to be asking here is "who actually runs > batch". Anyone? I gave kind of an answer to that in my original posting. :-) At least I run batch and at, and I do it *all the time*. There is imho no more convenient way of firing