Hi Jason,
Does this look OK to you?
diff --git a/share/man/man9/sysctl_int.9 b/share/man/man9/sysctl_int.9
index bc335aedd9c..e6b37391a0a 100644
--- a/share/man/man9/sysctl_int.9
+++ b/share/man/man9/sysctl_int.9
@@ -36,7 +36,7 @@
.Ft int
.Fn sysctl_int "void *oldp" "size_t *oldlenp" "void
On 2020/08/01 22:21, Mark Kettenis wrote:
> > pci11 at ppb9 bus 10
> > vga1 at pci11 dev 0 function 0 "ASPEED Technology AST2000" rev 0x30
>
> This is the BMC graphics and seems to be the only grapics device
> available on this machine.
Correct.
> > wsdisplay at vga1 not configured
>
> And I
> Date: Sat, 1 Aug 2020 18:23:08 +1000
> From: Jonathan Matthew
> Cc: tech@openbsd.org
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> On Wed, Jul 29, 2020 at 08:29:31PM +1000, Jonathan Matthew wrote:
> > On Wed, Jul 29, 2020 at 10:06:14AM +0200, Mark Kettenis
> Date: Sat, 1 Aug 2020 20:54:28 +0100
> From: Stuart Henderson
>
> I've just been building a machine with serial console to go to colo
> tomorrow and have noticed that there's no output on glass console
> after the "switching console to com0" message. The only getty running
> after boot is the
I've just been building a machine with serial console to go to colo
tomorrow and have noticed that there's no output on glass console
after the "switching console to com0" message. The only getty running
after boot is the one on serial console.
I won't be able to do much in the way of testing on
On Sat, 01 Aug 2020 17:29:11 +0200, Jan Stary wrote:
> ping
This was already committed.
revision 1.33
date: 2020/07/16 20:08:12; author: millert; state: Exp; lines: +1 -146;
commitid: LVVrFB1zB8C0gLBS;
Remove obsolete LOCALE_HOME code we have never used (and never will).
Upstream removed
On Sat, Aug 01, 2020 at 07:30:55PM +0200, Klemens Nanni wrote:
> On Sat, Aug 01, 2020 at 06:06:32PM +0100, Jason McIntyre wrote:
> > hmm. so then the current text ("the last background process") already
> > covers all these cases. why single out co-processes?
> Yes, "background process"
On Sat, Aug 01, 2020 at 06:06:32PM +0100, Jason McIntyre wrote:
> hmm. so then the current text ("the last background process") already
> covers all these cases. why single out co-processes?
Yes, "background process" technically covers co-processes, but at least
for me "background processes" aka.
->sc_devnode,
> + "_UID", 0, NULL, ) == 0)
> + sc->sc_cpu = uid;
>
> if (aml_evalnode(sc->sc_acpi, sc->sc_devnode, 0, NULL, ) == 0) {
> if (res.type == AML_OBJTYPE_PROCESSOR) {
>
See below for the old and the new dme
On Sat, Aug 01, 2020 at 06:59:43PM +0200, Klemens Nanni wrote:
> On Sat, Aug 01, 2020 at 05:40:07PM +0100, Jason McIntyre wrote:
> > i'm worried that you're blurring the distinction between asynchronous
> > and co-process for the reader. i think that's relevant because, as you
> > say, a page like
On Sat, Aug 01, 2020 at 05:40:07PM +0100, Jason McIntyre wrote:
> i'm worried that you're blurring the distinction between asynchronous
> and co-process for the reader. i think that's relevant because, as you
> say, a page like sh(1) does not document co-processes, whereas ksh(1)
> does.
You raise
On Sat, Aug 01, 2020 at 05:57:01PM +0200, Klemens Nanni wrote:
> Otherwise it is not clear whether $! will be set or not. This way,
> `/Co-proc' brings me to *all* relevant spots in the manual.
>
> Snippet to demonstrate how $! is set for an asynchronous process:
>
> $ ksh -c ': |& echo
Otherwise it is not clear whether $! will be set or not. This way,
`/Co-proc' brings me to *all* relevant spots in the manual.
Snippet to demonstrate how $! is set for an asynchronous process:
$ ksh -c ': |& echo $!'
67163
FWIW, sh(1) doesn't document Co-processes (whis is
On Sat, Aug 01, 2020 at 07:44:17PM +0900, YASUOKA Masahiko wrote:
> Hi,
>
> I'm not sure when it is broken, in old versions, it was assumed the
> pipex queues are empty when pipex_iface_stop() is called. The problem
> mvs@ found is the assumption is not true any more.
>
> pipex has a mechanism
ping
On Jul 16 09:23:22, h...@stare.cz wrote:
> 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:
Hi,
I'm not sure when it is broken, in old versions, it was assumed the
pipex queues are empty when pipex_iface_stop() is called. The problem
mvs@ found is the assumption is not true any more.
pipex has a mechanism that delete a session when the queues are empty.
819 Static void
820
On Wed, Jul 29, 2020 at 08:29:31PM +1000, Jonathan Matthew wrote:
> On Wed, Jul 29, 2020 at 10:06:14AM +0200, Mark Kettenis wrote:
> > > Date: Wed, 29 Jul 2020 10:38:55 +1000
> > > From: Jonathan Matthew
> > >
> > > On Tue, Jul 28, 2020 at 07:30:36PM +0200, Mark Kettenis wrote:
> > > > > Date:
17 matches
Mail list logo
