See page 6 of
https://www.bipm.org/documents/20126/77765681/Resolutions-2022.pdf/281f3160-fc56-3e63-dbf7-77b76500990f
OK?
diff --git usr.bin/units/units.lib usr.bin/units/units.lib
index c50011dcbc8..fb61ae63dc4 100644
--- usr.bin/units/units.lib
+++ usr.bin/units/units.lib
@@ -13,6 +13,8 @@
Hi all,
we are working on automated bootloader and device-tree updates for Apple
Silicon machines. This is necessary because both drivers and device trees
are moving targets and without a way to update both we end up in situations
where drivers suddenly stop working.
All of the fw_update(8)
On Sun, 25 Sep 2022 13:12:44 +0200, =?UTF-8?Q?S=C3=B6ren?= Tempel wrote:
> Currently, the OpenBSD ed implementation incorrectly writes information
> to standard error that should be written to standard out (as per POSIX).
>
> For the read and write command the POSIX standard states the following:
Index: nologin.c
===
RCS file: /cvs/src/sbin/nologin/nologin.c,v
retrieving revision 1.9
diff -u -p -r1.9 nologin.c
--- nologin.c 12 Jul 2021 15:09:19 - 1.9
+++ nologin.c 18 Nov 2022 16:59:31 -
@@ -25,7 +25,6 @@
*
This does not help anything.
Josiah Frentsos wrote:
> Index: nologin.c
> ===
> RCS file: /cvs/src/sbin/nologin/nologin.c,v
> retrieving revision 1.9
> diff -u -p -r1.9 nologin.c
> --- nologin.c 12 Jul 2021 15:09:19 - 1.9
> Date: Thu, 17 Nov 2022 20:23:37 +0100
> From: Mark Kettenis
>
> > From: Jeremie Courreges-Anglas
> > Date: Thu, 17 Nov 2022 18:00:21 +0100
> >
> > On Tue, Nov 15 2022, Martin Pieuchot wrote:
> > > UVM vnode objects include a reference count to keep track of the number
> > > of processes
I love xz compression. It really pinches the bytes outa ascii files, which log
files
are of course made of.
Is there a direction someone can point me in that would permit the
functionality this
diff provides without hardcoding it and perhaps be acceptable for the tree?
diff --git
I completely disagree on this, of course.
We do not make base use ports.
Todd T. Fries wrote:
> I love xz compression. It really pinches the bytes outa ascii files, which
> log files
> are of course made of.
>
> Is there a direction someone can point me in that would permit the
>
On Sat, 19 Nov 2022 14:41:18 +0900 (JST)
YASUOKA Masahiko wrote:
> On Wed, 12 Oct 2022 07:58:20 +0900 (JST)
> YASUOKA Masahiko wrote:
>> On Wed, 05 Oct 2022 13:37:35 +0900 (JST)
>> Masato Asou wrote:
>>> From: "Theo de Raadt"
>>> Date: Tue, 04 Oct 2022 21:58:13 -0600
Userland may not ask
On Wed, 12 Oct 2022 07:58:20 +0900 (JST)
YASUOKA Masahiko wrote:
> On Wed, 05 Oct 2022 13:37:35 +0900 (JST)
> Masato Asou wrote:
>> From: "Theo de Raadt"
>> Date: Tue, 04 Oct 2022 21:58:13 -0600
>>> Userland may not ask the kernel to allocate such a huge object. The
>>> kernel address space is
10 matches
Mail list logo