On Mon, Oct 15, 2018 at 03:17:28PM -0700, Ayaka Koshibe wrote:
> Hi all,
>
> Currently, switchctl(8) is able to query a switch for information by
> specifying
> the switch's network address. The following adds support for querying a
> switch(4) instance via its control device:
>
>
> $ doas swit
I think I see some evidence of occasional VM just never finishing booting
to the point of running sshd. At least that's what I surmised from the
posted manager.log file.
https://gist.github.com/blackgnezdo/a69e83c42c0c4cbbd53c7f3b35e91632
Here's an excerpt:
2018/10/16 19:35:08 VMs 2, executed 6832
Hi all,
Justification for removing this code:
1) This is currently dead code, UVM_PAGE_TRKOWN is undefined in GENERIC on all
arches. If it is dead, while reading it gives incorrect impression that this
code is useful.
2) The comment for uvm_page_own() mentions tracking down problems in PG_BUSY
hello,
reading plus64.html I saw the links to imxiomuxc(4), imxccm(4) and
acpicmos(4) did not give results; man -k agrees.
I would have sent man page drafts if I knew what these devices are.
The CVS commit messages did not help.
Therefore this is just a reminder, sorry.
Marcus
On Tue, Oct 16, 2018 at 06:20:41PM +0200, Marcus MERIGHI wrote:
> Just an extra "and" left behind. And some missing links.
In, thanks.
Hello,
thanks for all the work!
Just an extra "and" left behind. And some missing links.
Yeehaa, console scrollback is back!
Marcus
Index: 64.html
===
RCS file: /cvs/www/64.html,v
retrieving revision 1.79
diff -u -p -r1.79 64.ht
Christian Weisgerber wrote:
> Mark Kettenis:
>
> > > Currently, building an amd64 or i386 kernel with lld breaks in
> > > makegap.sh. It turns out that we already have the missing pieces
> > > (gapdummy) on some other archs, so we can just copy them.
> >
> > Any reason why you didn't commit th
Mark Kettenis:
> > Currently, building an amd64 or i386 kernel with lld breaks in
> > makegap.sh. It turns out that we already have the missing pieces
> > (gapdummy) on some other archs, so we can just copy them.
>
> Any reason why you didn't commit this yet?
Theo was concerned that this might
I tested the diff and while im not qualified to judge the code, it now behaves
like i would expect.
Thanks for working on this,
Regards.
> Klemens Nanni hat am 16. Oktober 2018 um 13:34 geschrieben:
>
>
> On Tue, Oct 16, 2018 at 10:03:01AM +0200, Alexandr Nedvedicky wrote:
> > I also wond
Oops I missed the obvious kill(2) only a few lines later, silly me :\
On 13:56 Tue 16 Oct , Sebastien Marie wrote:
> about unveil: it seems fine. open_ok() functions checks if
> cmd.arg.open.path is in allowed_devices. so having it locked to only
> that seems correct.
>
>
> about pledge: "p
On Tue, Oct 16, 2018 at 12:27:33PM +0100, Ricardo Mestre wrote:
> Hi,
>
> xserver's priv proc is responsible for opening devices in O_RDWR mode and send
> their fds over to the parent proc. Knowing this then we already have a list of
> all possible devices that might be opened in the future and we
Hello,
> This comment is way too much, imho. How about this:
>
> Unless errors occured, stop iff any rule matched
> within quick anchors.
I'm fine with your proposal. You have my OK to commit
the fix.
thanks and
regards
sashan
On Tue, Oct 16, 2018 at 10:03:01AM +0200, Alexandr Nedvedicky wrote:
> I also wonder if we should apply same change to wildcard anchors here:
They need fixing as well, but I have yet to look into it.
> diff --git a/sys/net/pf.c b/sys/net/pf.c
> index 0bdf90a8d13..5a5c739773a 100644
> --- a/sys
Hi,
xserver's priv proc is responsible for opening devices in O_RDWR mode and send
their fds over to the parent proc. Knowing this then we already have a list of
all possible devices that might be opened in the future and we can unveil(2)
them by traversing allowed_devices and yes it's a long list
> Date: Fri, 14 Sep 2018 00:25:42 +0200
> From: Christian Weisgerber
>
> Currently, building an amd64 or i386 kernel with lld breaks in
> makegap.sh. It turns out that we already have the missing pieces
> (gapdummy) on some other archs, so we can just copy them.
>
> With this, I can successfull
Hello,
>
> In my understanding they do, but you are missing the point. Given the
> following ruleset:
>
> pass
> anchor quick {
> block inet6
> }
> block
>
> With the current fix ruleset-evaluation terminates after the anchor,
> before the last block even *if no ipv6-traffic was encounte
16 matches
Mail list logo
