Re: fw_update lock_db should exit when parent exits

On Wed, Aug 23, 2023 at 08:42:03AM -0600, Todd C. Miller wrote: > On Tue, 22 Aug 2023 19:55:56 -0700, Andrew Hewus Fresh wrote: > > > I noticed this when testing how signal handling worked in fw_update, it > > turns out that if you `pkill -KILL -f fw_update` it may leave behind a perl > > process

Re: [patch] netcat: support --crlf

On Wed, 23 Aug 2023, Pietro Cerutti wrote: > Hi, > > here at FreeBSD, we vendor in your netcat with a few local modifications. > > I'm working on adding support to --crlf. I have a diff against the FreeBSD > version here: https://reviews.freebsd.org/D41489 > > I'd like this to be upstreamed.

dt(4), hardclock(9): move interval, profile providers to dedicated callback

This is the next patch in the clock interrupt reorganization series. This patch moves the entry points for the interval and profile dt(4) providers from the hardclock(9) to a dedicated clock interrupt callback, dt_prov_profile_intr(), in dev/dt/dt_prov_profile.c. - To preserve current behavior,

Re: all platforms: separate cpu_initclocks() from cpu_startclock()

On Mon, Aug 21, 2023 at 10:23:53PM -0500, Scott Cheloha wrote: > On Tue, Aug 22, 2023 at 02:36:31AM +, Mike Larkin wrote: > > On Mon, Aug 21, 2023 at 09:26:00PM -0500, Scott Cheloha wrote: > > > On Mon, Aug 21, 2023 at 10:10:58PM +, Mike Larkin wrote: > > > > On Sat, Aug 19, 2023 at

[patch] netcat: support --crlf

Hi, here at FreeBSD, we vendor in your netcat with a few local modifications. I'm working on adding support to --crlf. I have a diff against the FreeBSD version here: https://reviews.freebsd.org/D41489 I'd like this to be upstreamed. If there's consensus, I'll prepare a patch against

Re: installer: disk crypto: crank KDF rounds to hardware based default

On Fri, Aug 11, 2023 at 03:51:38PM +0100, Stuart Henderson wrote: > On 2023/08/11 16:43, Mark Kettenis wrote: > > See the recent discussion about _bcrypt_autorounds() in libc. > > > > System performance varies, and even on modern hardware it can provide > > varying results. The ramdisk

Re: fw_update lock_db should exit when parent exits

On Tue, 22 Aug 2023 19:55:56 -0700, Andrew Hewus Fresh wrote: > I noticed this when testing how signal handling worked in fw_update, it > turns out that if you `pkill -KILL -f fw_update` it may leave behind a perl > process that is locking the package database. Instead of just waiting > to be

iwx background scan fix

When I updated iwx to -77 firmware I made a mistake in setting up the new version of the scan command, in the particular case of starting a background scan. One part of the command says that active scan should be used. "Active scan" means the device will send probe requests containing a desired