I heard about OpenBSD/Loongson still doesn't support newer Loongson 3A/3B
system, then got contact with some Lemote staff and they tell me there are
some Loongson 3A1000 and 3B1500 machine in are ready to donate. These board was
used as Debian auto-build server and can ship from Germany.
Am 16.07.2020 um 07:49 schrieb Paul de Weerd:
> What I have is this:
>
> for DOMAIN in `awk '/^domain/ {print $2}' /etc/acme-client.conf`
My script is similar to this...
> As I need to update OCSP staples per domain anyway, doing a per-domain
> song-and-dance makes sense for me. Since I set the
Just for completeness, 1 Joule = 1 watt per second, so 3600 Joules = 1
Watt-hour. This may be related to the total amount of energy harvested by
the chip to allow analyze how much power hungry are the CPU for a given
job.
Regards!
El mar., 14 jul. 2020 a las 19:48, Theo de Raadt ()
escribió:
>
On Jul 15 15:48:41, mill...@openbsd.org wrote:
> Upstream tzcode removed the LOCALE_HOME bits in 2014. There's no
> reason for us to keep it.
With that removed, the header file can go too.
Jan
Index: lib/libc/time/strftime.c
On 2020/07/15 10:02, Theo de Raadt wrote:
> It is extremely unwise to use DNS names at this level (or things which
> look like DNS names). The same problems that pf has with DNS, are
> present here. You really don't want people to get into this habit.
Same in gre(4) config which needs addresses
Does xargs need to set LC_MESSAGES?
Jan
Index: usr.bin/xargs/xargs.c
===
RCS file: /cvs/src/usr.bin/xargs/xargs.c,v
retrieving revision 1.34
diff -u -p -r1.34 xargs.c
--- usr.bin/xargs/xargs.c 12 Jun 2018 15:24:31
On Thu, Jul 16, 2020 at 10:23:20AM +0100, Stuart Henderson wrote:
> On 2020/07/15 10:02, Theo de Raadt wrote:
> > It is extremely unwise to use DNS names at this level (or things which
> > look like DNS names). The same problems that pf has with DNS, are
> > present here. You really don't want
Interface index 0 is never associated with interface descriptor. So
we can assign this value to session's interface index before destroy
corresponding `ifnet'. It's safe to use indexes instead of pointers to
`ifnet' in pipex(4).
Index: sys/net/if_pppx.c
Scott Cheloha:
> Can we add the missing LFENCE instructions to userspace and the
> kernel? And can we excise the upper 32 bits?
> + uint32_t lo;
> +
> + asm volatile("lfence");
> + asm volatile("rdtsc" : "=a"(lo));
That's wrong. rtdsc will clobber %rdx, whether you use that value
> Date: Wed, 15 Jul 2020 20:36:04 -0500
> From: Scott Cheloha
>
> On Sat, Jul 11, 2020 at 01:16:43PM +0200, Mark Kettenis wrote:
> > > From: Paul Irofti
> > > Date: Sat, 11 Jul 2020 13:50:37 +0300
> > >
> > > On 2020-07-11 13:46, Mark Kettenis wrote:
> > > >> From: Paul Irofti
> > > >> Date:
Hi tech@,
Here is a diff to merge the two if blocks checking if the font in use
contains a given character in rasops_mapchar().
Comments? OK?
Index: sys/dev/rasops/rasops.c
===
RCS file: /cvs/src/sys/dev/rasops/rasops.c,v
On Thu, Jul 16, 2020 at 02:14:45PM +0200, Christian Weisgerber wrote:
> Scott Cheloha:
>
> > Can we add the missing LFENCE instructions to userspace and the
> > kernel? And can we excise the upper 32 bits?
>
> > + uint32_t lo;
> > +
> > + asm volatile("lfence");
> > + asm volatile("rdtsc"
There's a logic bug in iwn(4) which means that automatic rate control
for A-MPDU runs while a fixed Tx MCS is configured with a command like
"ifconfig iwn0 media HT-MCS10 mode 11n".
The intention was of course the inverse: Use automatic rate control if
the Tx MCS is not fixed (i.e. if
On Wed, Jul 15, 2020 at 09:08:29AM -0500, Scott Cheloha wrote:
> Hi,
>
> adjtime(2) skews the clock at up to 5000ppm per second. The way this
> actually happens is pretty straightforward: at the start of every UTC
> second we call ntp_update_second() from tc_windup() and reset
> th_adjustment.
Make iwn_ampdu_tx_done() record an ACK for the frame for which the hardware
triggered the Tx completion interrupt, instead of the frame with the starting
sequence number (SSN) of the firmware's block ack window. The frame at SSN
is unrelated and may not even have been transmitted yet.
ok?
diff
Hi Jan,
Jan Stary wrote on Thu, Jul 16, 2020 at 09:45:44AM +0200:
> Does xargs need to set LC_MESSAGES?
As it stands, your patch doesn't make much sense. It is true that
it doesn't change behaviour, but it leaves more cruft behund than
it tidies up.
That said, i agree that we will never
I gave a quick look at replacing prompt with readpassphrase(3), but that
would be more trouble than it's worth. (adjusting pledge, semantics
change in where the "?..." would be printed).
Minor nits inline, but either way OK martijn@
On Thu, 2020-07-16 at 21:49 +0200, Ingo Schwarze wrote:
> Hi
On Thu, Jul 16, 2020 at 09:49:21PM +0200, Ingo Schwarze wrote:
> That allows a nice cleanup, simplifying the code and getting rid
> of several headers and several calls to complicated functions.
OK kn
Hi tech@,
Here is a diff to add a new column to wsfontload -l output, which
reports the number of characters contained in a loaded font.
It's especially useful with user loaded fonts as they can contain more
than 256 characters.
Below is the current output of wsfontload -l, without the diff:
#
> Note the third sentence.
>
> Given that, I reason that a serializing instruction before *and* after
> the RDTSC should freeze it in place.
I haven't seen anyone read it that way.
> On Jul 16, 2020, at 19:36, Theo de Raadt wrote:
>
>> Note the third sentence.
>>
>> Given that, I reason that a serializing instruction before *and* after
>> the RDTSC should freeze it in place.
>
> I haven't seen anyone read it that way.
They say that instructions after RDTSC can run
21 matches
Mail list logo
