Re: sysupgrade: exit 1 instead of exit 0 when ending early

On 2022-10-07 14:39 -04, Josh Grosse wrote: > For ease of running sysupgrade from within a script. > > diff --git a/usr.sbin/sysupgrade/sysupgrade.sh > b/usr.sbin/sysupgrade/sysupgrade.sh > index d80ff127ffa..ce5800093c9 100644 > --- a/usr.sbin/sysupgrade/sysupgrade.sh > +++

Re: ThinkPad X13s and OpenBSD

On Fri, Oct 07, 2022 at 01:44:50PM -0700, Mike Larkin wrote: > On Fri, Oct 07, 2022 at 11:59:49AM -0700, Bryan Vyhmeister wrote: > > Hey Patrick, > > > > I hope you're doing well. We have not talked in quite a while. I was > > wondering how well the support for the ThinkPad X13s works right now in

Re: ThinkPad X13s and OpenBSD

On Fri, Oct 07, 2022 at 11:59:49AM -0700, Bryan Vyhmeister wrote: > Hey Patrick, > > I hope you're doing well. We have not talked in quite a while. I was > wondering how well the support for the ThinkPad X13s works right now in > OpenBSD. I did some searching around and couldn't find much other

ThinkPad X13s and OpenBSD

Hey Patrick, I hope you're doing well. We have not talked in quite a while. I was wondering how well the support for the ThinkPad X13s works right now in OpenBSD. I did some searching around and couldn't find much other than "support being added" but I'm not sure if that means everything works or

sysupgrade: exit 1 instead of exit 0 when ending early

For ease of running sysupgrade from within a script. diff --git a/usr.sbin/sysupgrade/sysupgrade.sh b/usr.sbin/sysupgrade/sysupgrade.sh index d80ff127ffa..ce5800093c9 100644 --- a/usr.sbin/sysupgrade/sysupgrade.sh +++ b/usr.sbin/sysupgrade/sysupgrade.sh @@ -153,7 +153,7 @@ rm SHA256.sig if

Re: [PATCH] ssh: don't make the umask more permissive than the user has set

On 10/6/22 16:46, Damien Miller wrote: > On Tue, 4 Oct 2022, Alex Henrie wrote: > >> Daniel Kahn Gillmor suggested this exact change on the openssh-unix-dev >> mailing list in 2008, but I couldn't find any reply. [1] >> >> Ignoring the current umask makes it hard to fulfill the Defense >>

Re: tsc: AMD Family 17h, 19h: compute frequency from MSRs

> Date: Fri, 7 Oct 2022 12:38:24 -0500 > From: Scott Cheloha > > On Fri, Oct 07, 2022 at 11:27:45AM -0500, Scott Cheloha wrote: > > On Fri, Oct 07, 2022 at 09:34:46AM -0500, Scott Cheloha wrote: > > > On Thu, Sep 29, 2022 at 09:14:51AM -0500, Scott Cheloha wrote: > > > > This patch computes the

Re: tsc: AMD Family 17h, 19h: compute frequency from MSRs

On Fri, Oct 07, 2022 at 11:27:45AM -0500, Scott Cheloha wrote: > On Fri, Oct 07, 2022 at 09:34:46AM -0500, Scott Cheloha wrote: > > On Thu, Sep 29, 2022 at 09:14:51AM -0500, Scott Cheloha wrote: > > > This patch computes the TSC frequency for AMD family 17h and 19h CPUs > > > (Zen

Re: tsc: AMD Family 17h, 19h: compute frequency from MSRs

On Fri, Oct 07, 2022 at 09:34:46AM -0500, Scott Cheloha wrote: > On Thu, Sep 29, 2022 at 09:14:51AM -0500, Scott Cheloha wrote: > > This patch computes the TSC frequency for AMD family 17h and 19h CPUs > > (Zen microarchitecture and up) from AMD-specific MSRs. Computing the > > TSC frequency is

Re: tsc: AMD Family 17h, 19h: compute frequency from MSRs

On Thu, Sep 29, 2022 at 09:14:51AM -0500, Scott Cheloha wrote: > This patch computes the TSC frequency for AMD family 17h and 19h CPUs > (Zen microarchitecture and up) from AMD-specific MSRs. Computing the > TSC frequency is faster than calibrating with a separate timer and > introduces no error.

bgpctl openmetric/prometheus output

This diff adds `bgpctl show metric` which is a command that dumps some stats out in openmetric format. This format can be ingested by e.g. prometheus and used for monitoring. The openmetric handling is in ometric.[ch]. It is fairly basic and not intended for long running processes. There is a