Re: unveil(2) usbhidctl(1)

On 2021-12-12 01:52 UTC, Ricardo Mestre wrote: > Hi, > > usbhidctl(1) after hid_start(3) doesn't need to open any more files so we can > restrict all fs access with unveil(2). > > comments? ok? > > Index: usbhid.c > === > RCS file: /c

unveil(2) usbhidctl(1)

Hi, usbhidctl(1) after hid_start(3) doesn't need to open any more files so we can restrict all fs access with unveil(2). comments? ok? Index: usbhid.c === RCS file: /cvs/src/usr.bin/usbhidctl/usbhid.c,v retrieving revision 1.17 diff

unveil(2) usbhidaction(1)

Hi, disclaimer: fortunately people are using ucc(4) instead of usbhidaction(1), the devices I have cannot be tested properly with this diff so please bear with me. this is similar to the diff I sent for usbhidctl(1), the exception is that you can run this as a daemon and `conf' can be re-read on

Re: ipsec ipo tdb mutex

On Sat, Dec 11, 2021 at 12:53:35AM +0100, Alexander Bluhm wrote: > To cache lookups, the policy ipo is linked to its SA tdb. There > is a list of SAs that belong to a policy. To make it MP safe we > need a mutex around these pointers. > > Hrvoje: Can you test this alone and together with the ip

Re: w(1): always print "up" before uptime

Hi all, Is there anything else that would be needed to get this patch committed? Kind regards, + Kimmo On Mon, 29 Nov 2021 at 11:22, Kimmo Suominen wrote: > > Hi, > > The following patch will make w(1) always print the word "up" before the > uptime. Currently "up" is not printed if uptime is le

Event filter adjustments for ttys

This adds EVFILT_EXCEPT handler for ttys to let kqueue-based poll(2) detect POLLHUP when pollfd.event == 0. filt_ttywrite(), and also filt_ptcwrite(), appear to lack HUP detection. Has this been intentional? The poll(2) emulation would need the HUP bits if feature similarity to ttpoll(), and ptcp

Re: Adjust socket and FIFO's EVFILT_EXCEPT

On Mon, Dec 06, 2021 at 05:17:21PM +, Visa Hankala wrote: > This patch adjusts the EVFILT_EXCEPT code of sockets and FIFOs so that > it would raise the HUP condition only when the channel has been closed > from both sides. This should match better with the POLLHUP case of > soo_poll() and fifo_

Re: Fix typo in '}' command in less.1

On Fri, Dec 10, 2021 at 03:04:11PM GMT, Richard Ulmer wrote: > Hi, > this is just a minor copy-and-paste error fix for the less(1) man page. > I also contributed this upstream: https://github.com/gwsw/less/pull/228 Hi Richard, You might want to consider reporting it to less-fork[0] which OpenBSD