OK kn
Philip Guenther(guent...@gmail.com) on 2019.06.16 12:28:35 -0700:
>
> Testing something else I needed to call syslog(3) with LOG_CONS. Diff
> below adds support to logger(1) for doing that. Option choice is
> compatible with NetBSD.
>
> ok?
sounds useful, -c looks like a good choice too.
On Mon, Jun 10, 2019 at 10:01:59AM +0200, Matthieu Herrb wrote:
> Hi,
>
> another update: libXext 1.3.4. No real bug fixes though.
>
> ok ?
ok tb
I tested this together with the libXcomposite, libXcursor, libXdamage,
libXext updates on my main laptop without noticing any regressions. The
diffs
On Mon, Jun 10, 2019 at 06:43:25PM +0200, Matthieu Herrb wrote:
> Hi,
>
> last update of the current batch : libXdamage 1.1.5
>
> ok ?
ok tb
On Mon, Jun 10, 2019 at 06:42:19PM +0200, Matthieu Herrb wrote:
> Hi,
>
> another update : libXcursor 1.2.0
>
> ok ?
ok tb
On Mon, Jun 10, 2019 at 06:41:24PM +0200, Matthieu Herrb wrote:
> Hi,
>
> a another quite boring update to libXcomposte 0.4.5.
>
> ok?
ok tb
Testing something else I needed to call syslog(3) with LOG_CONS. Diff
below adds support to logger(1) for doing that. Option choice is
compatible with NetBSD.
ok?
Philip Guenther
Index: logger.1
===
RCS file:
On Sun, Jun 16, 2019 at 09:55:24PM +1000, Damien Miller wrote:
>
>
> On Sun, 16 Jun 2019, Matthieu Herrb wrote:
>
> > On Sun, Jun 09, 2019 at 04:47:53PM +0200, Matthieu Herrb wrote:
> > > Hi,
> > >
> > > ssh-askpass(1) is trying to be clever and computes the size of its
> > > indicator
On Sun, Jun 16, 2019 at 09:25:45AM +0200, Florian Obser wrote:
> On Sat, Jun 15, 2019 at 06:20:49PM +0200, Florian Obser wrote:
> > OK?
>
> update to apply cleanly on -current
The acctproc.c change looks ok with some minor comments inline.
I haven't tried to verify the JSON stuff.
>
> diff
Martijn van Duren wrote:
> > 2. When doing keepenv, nothing changes, except addition of above.
>
> It feels inconsistent to make keepenv behave different here.
> - It may allow certain applications to behave unexpected compared to
> without keepenv (e.g. scripts that use $HOME/.cache).
> - The
Mark Kettenis on Thu, Jun 13 2019:
> So here is a diff that fixes the problem as far as I can tell.
> Jonathan, Sven, can you give this a go?
Works for me.
> + tq->tq_waiting++;
> msleep(tq, >tq_mtx, PWAIT, "bored", 0);
> + tq->tq_waiting--;
Heh, didn't
*bump*
On Fri, May 24, 2019 at 07:17:29PM +0200, Jesper Wallin wrote:
> Hi tech@
>
> A few days ago, I decided to set kern.securelevel=2 just for the sake
> of locking down my machine as much as possible. Today I learned that
> this affects bioctl(8) when trying to attach a crypto RAID.
>
>
On Sun, 16 Jun 2019, Matthieu Herrb wrote:
> On Sun, Jun 09, 2019 at 04:47:53PM +0200, Matthieu Herrb wrote:
> > Hi,
> >
> > ssh-askpass(1) is trying to be clever and computes the size of its
> > indicator relatively to the screen resolution.
> >
> > Unfortunatly, when multiple screens are
hi,
On 2019/02/26 14:00, Nils Frohberg wrote:
> On Mon, Feb 25, 2019 at 03:50:48PM -0300, Martin Pieuchot wrote:
>> On 25/02/19(Mon) 14:52, Nils Frohberg wrote:
[snip]
>>> I didn't get around to much testing/debugging lately, therefore I
>>> wanted to share the current state (diff below).
>>>
>>>
hi,
On 2019/02/28 06:53, Nils Frohberg wrote:
> On Tue, Feb 26, 2019 at 08:57:57PM +0200, Artturi Alm wrote:
>> On Tue, Feb 26, 2019 at 03:00:15PM +0100, Nils Frohberg wrote:
[snip]
>> Have you looked at what NetBSD has done with their axen(4)? there has
>> been 20commits in 2019 so far[0], while
On Sun, Jun 09, 2019 at 07:22:26PM +0200, Matthieu Herrb wrote:
> Hi,
>
> We disabled almost all X font server support code already. The patch
> below removes support for connecting to a font server from libXfont2.
>
> It means that you X server will no longer be able to use fonts from a
>
On Sun, Jun 09, 2019 at 04:47:53PM +0200, Matthieu Herrb wrote:
> Hi,
>
> ssh-askpass(1) is trying to be clever and computes the size of its
> indicator relatively to the screen resolution.
>
> Unfortunatly, when multiple screens are present, this gets ugly. The
> support for Xinerama correctly
On Sun, Jun 16, 2019 at 10:05:55AM +0200, Florian Obser wrote:
> I'm not sure why we use get1 and not get0.
> get0 should be ok here, no?
>
> Someone in the know please apply a clue bat, thanks.
Since the references are local to the functions and there are no
threads, no-one's going to
I'm not sure why we use get1 and not get0.
get0 should be ok here, no?
Someone in the know please apply a clue bat, thanks.
diff --git acctproc.c acctproc.c
index 09ac8c83372..fd0a22629db 100644
--- acctproc.c
+++ acctproc.c
@@ -86,6 +86,7 @@ op_thumb_rsa(EVP_PKEY *pkey)
else if ((json =
This uses less code and unveil(2) seems to be the better tool here.
There is probably nothing wrong with the chroot code because of pledge
but it still makes me feel uneasy.
The directory one chroots into needs to be carefully setup (they are
not) and comon wisedom is that root can break out of
On Sat, Jun 15, 2019 at 06:20:49PM +0200, Florian Obser wrote:
> OK?
update to apply cleanly on -current
diff --git acctproc.c acctproc.c
index 52309b765d5..09ac8c83372 100644
--- acctproc.c
+++ acctproc.c
@@ -24,6 +24,7 @@
#include
#include
+#include
#include
#include
#include
@@
21 matches
Mail list logo
