vnconfig: VNDIOCSET: File name too long

This error is due to the relatively small storage size available to store the path to the disk image. I see no reason to use 90 bytes only and not PATH_MAX here. Since bumping the size of the struct is an incompatible change, the kernel keeps some glue to allow old programs to work on a fresh

paste-o fix in comment + load average question

Hi, For a long time I was running an amd64 snapshot from 2016/03/30, then I installed a snapshot from 2016/10/09 on four machines (two laptops, a desktop and a 1U supermicro). One apparent difference was that the load average on all four machines idled at slightly above 1 (1.12, 1.18, ...),

Re: cwm ptrmove keybindings

Fri, 11 Nov 2016 10:42:42 -0500 Okan Demirmen > Hi, > > mpi@ recently alerted me to the fact that cwm(1)'s default keybindings for > ptrmove actions conflict with emacs users' uses, namely all the > control-[arrow] > bindings that cwm(1) grabs. It has actually been like this

cwm ptrmove keybindings

Hi, mpi@ recently alerted me to the fact that cwm(1)'s default keybindings for ptrmove actions conflict with emacs users' uses, namely all the control-[arrow] bindings that cwm(1) grabs. It has actually been like this since keyboard-based pointer movements were added, almost exactly 9 years ago.

Re: malloc type for CPU counters

On Fri, Nov 11, 2016 at 12:55 +1000, David Gwynne wrote: > there isnt a nice bucket for per cpu counters to use. this makes a > pretty obvious one. > > ok? > OK, but could you please put a tab after the #define for style consistency with the other ones? Also please on't forget to update