Currently, pkgsrc/sysutils/ups-nut works well on NetBSD (somewhat shaky
testing on some points, but my current belief):
UPS is monitored and data is available
configuration of UPS params
messages on loss of comms and restore
messages on transition to battery and return
initiation of
On Thu, Jan 05, 2023 at 11:46:42PM +0700, Robert Elz wrote:
> Date:Thu, 5 Jan 2023 11:16:22 -0500 (EST)
> From:Mouse
> | I'd do it myself except I don't know where to find an
> | authoritative spec for jot.
>
> I'd tend to assume it is the code.
Remark from the
Date:Fri, 6 Jan 2023 20:56:17 +0100
From:i...@netbsd.org
Message-ID:
| | The name jot derives in part from iota, a function in APL.
| Maybe somebody(tm) should look that up.
It has been a long time since I did any APL programming, but
in that, the iota function
mo...@rodents-montreal.org (Mouse) writes:
>>> I'd tend to assume it is the code.
>Well, then, there never can be any such thing as a bug in jot.
The original code (see rev 1.1) seems to be more clear on how
the parameters should be evaluated.
>>> I'd do it myself except I don't know where to find an authoritative
>>> spec for jot.
>> I'd tend to assume it is the code.
Well, then, there never can be any such thing as a bug in jot.
I find that...dubious.
> Remark from the peanut gallery, after (again) reading this in jot(1):
> | The
>> [...jot...]
> The original code (see rev 1.1) seems to be more clear on how the
> parameters should be evaluated.
Yes. Arguably the right thing to do here is to do the analog of what
that version does and list all 16 possible combinations of START, REPS,
ENDER, and STEP, with explicit code
