Re: pledge(2) sndioctl(1)

On Fri, May 22, 2020 at 08:10:54AM +0100, Ricardo Mestre wrote: > Hello, > > I tried to open the raw device but now it seems I was to sleepy to > figure out that I couldn't access it due to sndiod(8) having the device > opened earlier and therefore coundn't reach that code path. > > Here's the

[PATCH} efifb support for wsmoused + smaller fonts

The efifb driver behaves almost identically to the inteldrm driver for wscons, but did not implement the getchar() accessops, so wsmoused would fail at startup. Separately, I increased the maximum screen dimensions to 160x50 to allow the 12x24 font to be used on an 1920 monitor, which looks

Re: pppx(4): avoid direct usage of pxi owned session.

Sorry about delay. > On 20 May 2020, at 10:54, Martin Pieuchot wrote: > > On 14/05/20(Thu) 15:53, Vitaliy Makkoveev wrote: >> Each `struct pppx_if' holds it's own `pipex_session' and this session is >> used directly within ifnet's related handlers pppx_if_start() and >> pppx_if_output(). > > I

Provide ldomctl(8) better error messages when parsing ldom.conf

Currently ldomctl init-system will error out in many situations. A number of them involve requesting more resources than there are available. Right now onw just gets error messages like: resource_id larger than max_mblocks resource_id larger than max_guests not enough VCPU resources available not

Re: vmm timer for linux guests

Hello Dave, Pratik, > My hacky "vmm-clock" implementation is here if you'd like to compare > notes: https://git.sr.ht/~voutilad/linux/log/linux-5.4-obsd The clock is in sync with these patches. It is keeping the clock in sync with the host. sudo dmesg | grep -i clock [0.034850]

Re: random(4): use arc4random_ctx_buf() for large device reads

Makes sense to me. Christian Weisgerber wrote: > (This is in a different part of the file from Theo's current efforts.) > > For large reads from /dev/random, use the arc4random_ctx_*() functions > instead of hand-rolling the same code to set up a temporary ChaCha > instance. > > ok? > > >

random(4): use arc4random_ctx_buf() for large device reads

(This is in a different part of the file from Theo's current efforts.) For large reads from /dev/random, use the arc4random_ctx_*() functions instead of hand-rolling the same code to set up a temporary ChaCha instance. ok? Index: rnd.c

Re: vmm timer for linux guests

Hello Pratik, I thought the serial console has been stable since this patch. I just noticed a hang. So, the issue seems to still persist. Thanks

Improve error reporting in pfkey_sa_last_used

While I hunt for the reason child SAs expiring results in ESRCH during pfkey_sa_last_used, this more detailed log message on error is much more helpful than the default pretty print of "pfkey_sa_last_used: No such process". I suspect it's useful to others. Thank you, all. matthew weaver ---

Re: Fix manpage links in upgrade67.html

Hi Andre, Andre Stoebe wrote on Sat, May 23, 2020 at 06:10:36PM +0200: > following patch fixes two manpage links that point to the wrong section. Committed, thanks. Ingo > Index: faq/upgrade67.html > === > RCS file:

Re: vi.beginner diff and analysis (vi.advanced to follow)

Hi Andras, Andras Farkas wrote on Sun, May 24, 2020 at 01:27:18AM -0400: > I went through vi.beginner. Thanks. > It works both with vi's regular settings, > and with the settings applied via EXINIT in vi.tut.csh. Good. > I have a diff attached. I was mostly light and gentle with my >

mountd: Remove dead *netent(3) code

schwarze neutered the *netent(3) family as well as networks(5) in 2018, mountd(8) remains the only user of these functions in base. setnetent() and endnetent() are empty functions now, getnetent() always returns NULL unconditionally so the while loop is never entered, the entire if block is code

Re: vmd(8) and thread safety: a quick proof of concept using libevent 2.1 from ports

On Sat, May 23, 2020 at 9:38 PM Dave Voutila wrote: > > Hello tech@, > > Attached is a diff that patches vmd(8) to utilize libevent 2.1 (from > ports) in an attempt to test the hypothesis that thread safety will > help stabilize Linux guest support. There's some longer detail below > about this

iwx: add support for the soc command

Going back over the full list of commands the Linux driver sends to an ax200 device when it connects to an access point, I have noticed some that are missing from our driver. One of those is the SOC_CONFIGURATION command which provides some low-level details about the hardware device to firmware.

iwx: bt config command fix

The iwx(4) driver intends to disable bluetooth. The command we send to the firmware says "wifi only", but also enables a bluetooth module. This seems to work as intended but is ambiguous. Linux also leaves all modules disabled in wifi-only mode. So do not enable any BT modules in the BT_COEX