Marc Espie wrote:
> reorganizing a large part of usr.bin or usr.sbin to just be one
> single variation of bsd.prog.mk with multiple progs and multiple object
> files... works just fine for, say 95% of the binaries in those directories
>
> (considering there are lots of directories with one single
On Thu, Nov 28, 2019 at 01:05:43AM +0100, Klemens Nanni wrote:
> With that, the next step is to implement `ldomctl console guest01' in
> analogy to vmctl(8).
Here's a complete diff for updating the status output and implementing
the console command, mainly to ease testing and review. I do want to
On Thu, Nov 28, 2019 at 01:05:43AM +0100, Klemens Nanni wrote:
> t4-2# ./obj/ldomctl status
> primary -running OpenBSD running
> 0%
> guest01 ttyV0running OpenBoot Primary Boot Loader
> 50%
> guest02
Each logical domain has a serial port that is always present no matter
the domain's state.
Currently, one has to infer the minor number from the domain's position
in the running configuration, e.g. with ldom.conf(5)
domain "primary" {
vcpu 64
memory 64G
mopping up references to cvsync that we missed
Refrence to the original commit in ports
2019-11-07 03:16 naddy
* devel/quirks/Makefile, devel/quirks/files/Quirks.pm,
net/Makefile: Remove cvsync to encourage a switch to rsync for
repository mirroring.
Note:
Theo de Raadt wrote in <91679.1574892...@cvs.openbsd.org>:
|Steffen Nurpmeso wrote:
|1> Theo de Raadt wrote in <29275.1574888...@cvs.openbsd.org>:
|>|The following change only permits system calls from address-ranges
|>|in the process which system calls are expected from.
|> ...
Steffen Nurpmeso wrote:
1> Theo de Raadt wrote in <29275.1574888...@cvs.openbsd.org>:
> |The following change only permits system calls from address-ranges
> |in the process which system calls are expected from.
> ...
> |Unfortunately our current go build model hasn't followed solaris/macos
Theo de Raadt wrote in <29275.1574888...@cvs.openbsd.org>:
|The following change only permits system calls from address-ranges
|in the process which system calls are expected from.
...
|Unfortunately our current go build model hasn't followed solaris/macos
|approach yet of calling libc
The following change only permits system calls from address-ranges
in the process which system calls are expected from.
If you manage to upload exploit code containing a raw system call
sequence and instruction, and mprotect -w+x that block, such a system
call will not succeed but the process is
If you are used to building your own src tree, be aware a
dangerous ld.so change will come in about a week. It
will need a kernel from roughly nov27 onwards. snapshot
upgrades will be fine, but use of older kernels won't work.
If an anchor/ruleset contains no rules, there is no point in creating
a temporary copy, optimizing and replacing it.
Regress passes on amd64.
Feedback? OK?
Index: pfctl_optimize.c
===
RCS file:
This should get rid of the weird error (don't know how to make
.../all/debug-*.tgz) when switching from !DEBUG_PACKAGES to DEBUG_PACKAGES.
Basically, this introduces a "build two targets at once" in bsd.port.mk.
make has some glue to figure out whether this is a "duplicate the work" or
"one
Alexander Bluhm wrote:
> On Tue, Nov 26, 2019 at 04:51:36PM -0700, Theo de Raadt wrote:
> > ok with me
>
> So here is the full diff with all architecture makefiles that may
> be affected.
>
> I have done a build release on amd64. Boot loader on i386, armv7,
> arm64, macppc compiles and links.
On Tue, Nov 26, 2019 at 04:51:36PM -0700, Theo de Raadt wrote:
> ok with me
So here is the full diff with all architecture makefiles that may
be affected.
I have done a build release on amd64. Boot loader on i386, armv7,
arm64, macppc compiles and links. hppa, landisk, octeon is just a
guess
On Wed, Nov 27, 2019 at 06:21:01PM +0200, Lauri Tirkkonen wrote:
> All that said I do understand if there is reluctance to merge the
> jobserver stuff since it doesn't actually help the current situation in
> most cases. Nevertheless it has been personally beneficial to me in
> identifying areas
On Tue, Nov 26, 2019 at 04:17:46PM -0800, Ayaka Koshibe wrote:
> Currently, we assume that OpenFlow 1.3 set_field actions can contain
> multiple header match fields (OXMs). According to specification, a
> set_field action contains exactly one OXM, followed by padding to align
> the action field in
On Wed, Nov 27 2019 17:09:09 +0100, Marc Espie wrote:
> I did experiment with something similar a while back:
>
> reorganizing a large part of usr.bin or usr.sbin to just be one
> single variation of bsd.prog.mk with multiple progs and multiple object
> files... works just fine for, say 95% of
The inteldrm(4) driver keeps a cache of graphics objects, allegedly to
make things faster by avoiding cache flushes. But those graphics
objects consume memory that we want to free if we need it for
something else.
The diff below hooks up the "shrinker" code in inteldrm(4) and calls
it from the
On Wed, Nov 27, 2019 at 05:31:48PM +0200, Lauri Tirkkonen wrote:
> I'll give you some more background that I maybe should have given
> earlier already: in my hobby OS Unleashed, we use bmake and earlier did
> some (slightly hacky) modifications to subdir.mk to enable paralellizing
> jobs in
On Wed, Nov 27 2019 16:14:44 +0100, Marc Espie wrote:
> On Fri, Nov 15, 2019 at 03:29:29PM +0200, Lauri Tirkkonen wrote:
> > On Fri, Nov 15 2019 15:24:57 +0200, Lauri Tirkkonen wrote:
> > > Your points are valid and I agree with them completely. There are
> > > clearly problems with lock
On Fri, Nov 15, 2019 at 03:29:29PM +0200, Lauri Tirkkonen wrote:
> On Fri, Nov 15 2019 15:24:57 +0200, Lauri Tirkkonen wrote:
> > Your points are valid and I agree with them completely. There are
> > clearly problems with lock contention,
>
> and I should mention here that I would probably not
Hi benno,
If you remove "include" then please make the unveil next to pledge like
the below, that way we know right away why exactly we need rpath for in
pledge.
Also, you only need unveil(NULL, NULL) if you're not actually calling pledge
somewhere down the code.
Index: rad.c
On 20/11/19(Wed) 22:24, Alexander Bluhm wrote:
> Hi,
>
> Quite often I see "panic: unmount: dangling vnode". My test
> regress/sys/kern/mount triggers it, but it also happens when rebooting
> virtual machines.
>
> The problem is, when dirty buffers are flushed to disk, the unmount
> process
On Wed, Nov 27 2019 11:49:00 +0100, Marc Espie wrote:
> On Wed, Nov 27, 2019 at 12:42:48PM +0200, Lauri Tirkkonen wrote:
> > In a lesson to always proof-read *before* sending your message:
> >
> > On Wed, Nov 27 2019 12:31:51 +0200, Lauri Tirkkonen wrote:
> > > - a full release build with the
On Wed, Nov 27, 2019 at 12:42:48PM +0200, Lauri Tirkkonen wrote:
> In a lesson to always proof-read *before* sending your message:
>
> On Wed, Nov 27 2019 12:31:51 +0200, Lauri Tirkkonen wrote:
> > - a full release build with the jobserver enabled passed after
> >disabling
In a lesson to always proof-read *before* sending your message:
On Wed, Nov 27 2019 12:31:51 +0200, Lauri Tirkkonen wrote:
> - a full release build with the jobserver enabled passed after
>disabling gnu/usr.bin/binutils
this should, in fact, read "gnu/usr.bin/binutils-2.17". binutils builds
New diff, almost entirely rewritten and slightly redesigned, based on
your previous feedback as well as problems uncovered in testing. Sorry
it's taken so long; I've been a bit stingy with my spare time with
respect to this :)
Description of the design:
- the top-level make initializes
> On 26. Nov 2019, at 07:44, Gilles Chehade wrote:
>
> hello,
>
> smtpd has an implicit listener which is "listen on socket".
>
> I propose that we write it explicitely in the default config and give up
> with this last bit of implicit configuration.
>
> The goal behind that is to stop
28 matches
Mail list logo
