On Mon, May 27, 2019 at 3:43 PM Brian Callahan wrote:
> Below is a small diff in response to some configuration attempts
> found in ports land.
> lang/ponyc uses $(shell getconf LONG_BIT) in its Makefile to
> determine whether or not we're on a 64-bit platform.
>
It needs to know that at the
Hi tech --
Below is a small diff in response to some configuration attempts
found in ports land.
lang/ponyc uses $(shell getconf LONG_BIT) in its Makefile to
determine whether or not we're on a 64-bit platform.
However, our getconf(1) doesn't support reporting LONG_BIT.
This diff enables it.
* Renato Aguiar [2019-05-27 03:53:11 -0700]:
Hi,
The following patch makes Linux guests use kvm-clock by setting KVM's
CPUID signature on VMM:
I think the right thing is to make linux attach pvclock if it's on
OpenBSD vmm. You want to send them a patch?
Otherwise, does vmm pvclock keep
On Mon, May 27, 2019 at 7:36 AM Jeremie Courreges-Anglas
wrote:
>
> A bunch of our ports expect pthread_np.h to be standalone, alas our
> version doesn't include pthread.h. The diff below should help us get
> rid of some patches in (at least) mongodb, mono, gnustep and webkitgtk4.
>
> ok?
>
ok
When we started work on W^X, we knew it would be a long road due to the
prevalance of JIT tooling.
1) Some of the JIT tooling is clean and will flip memory between W and X
states -- accepting the cost of mprotect().
2) Other JIT tooling creates aliases between a pair of W and X mappings of
the
On Sat, May 25, 2019 at 09:27:48AM -0500, J Sisson wrote:
> Noticed a typo in jme(4) printf output. Found additional typos while
> browsing the code.
>
> Yes, possibly the most useless diff ever...I freely admit it.
>
fixed, thanks (though note your diff didn;t apply).
jmc
> Index:
On Mon, May 27, 2019 at 03:53:11AM -0700, Renato Aguiar wrote:
> Hi,
>
> The following patch makes Linux guests use kvm-clock by setting KVM's CPUID
> signature on VMM:
>
By saying the hypervisor is KVM to all guests, does this cause the guests
to make other assumptions we don't want?
> Index:
On Sun, May 26, 2019 at 11:38:37PM -0700, Mike Larkin wrote:
> On Wed, May 22, 2019 at 08:05:50PM -0500, Katherine Rohl wrote:
> > Hi,
> >
> > Adjusted NS8250 behavior in vmd(8) so it gets detected as an 8250 and not a
> > 16450 by OpenBSD’s boot process. Also generalized some of the
A bunch of our ports expect pthread_np.h to be standalone, alas our
version doesn't include pthread.h. The diff below should help us get
rid of some patches in (at least) mongodb, mono, gnustep and webkitgtk4.
ok?
Index: include/pthread_np.h
On Mon, May 13, 2019 at 21:11 Claudio Jeker
wrote:
> When using a rule forcing the nexthop to a specific address bgpd
> currently does not mark that nexthop as no-modify. In other words
> the default rules for nexthop propagation applies. This means that
> for ebgp it only sends out the set
On Mon, May 13, 2019 at 09:03:41PM +0200, Claudio Jeker wrote:
> When using a rule forcing the nexthop to a specific address bgpd
> currently does not mark that nexthop as no-modify. In other words
> the default rules for nexthop propagation applies. This means that
> for ebgp it only sends out
Hi,
The following patch makes Linux guests use kvm-clock by setting
KVM's CPUID signature on VMM:
Index: sys/arch/amd64/amd64/vmm.c
===
RCS file: /cvs/src/sys/arch/amd64/amd64/vmm.c,v
retrieving revision 1.245
diff -u -p -r1.245
On Mon, May 27, 2019 at 01:36:38PM +0200, Stefan Sperling wrote:
> Anyone?
makes sense to me, ok jmatthew@
>
> On Wed, May 22, 2019 at 02:49:43PM +0200, Stefan Sperling wrote:
> > On Mon, Apr 15, 2019 at 04:56:52PM +0200, Stefan Sperling wrote:
> > > The ifconfig mode command is broken; It is
Anyone?
On Wed, May 22, 2019 at 02:49:43PM +0200, Stefan Sperling wrote:
> On Mon, Apr 15, 2019 at 04:56:52PM +0200, Stefan Sperling wrote:
> > The ifconfig mode command is broken; It is supposed to force a wireless
> > interface into 11a/b/g/n media mode. This stopped working some time ago,
> >
Stuart Henderson wrote:
> On 2019/05/20 10:46, Paul de Weerd wrote:
> > However, library_aslr delays the boot sequence (because libraries must
> > be completed before the system can boot up) while kernel_aslr does not
> > - it only introduces a bit of extra load on your machine.
>
> That
Ted Unangst wrote:
> Jake Champlin wrote:
> > - readscores(1);
> > penalty = loot = 0;
> > initscr();
> > + if (unveil(scorepath, "rwc") == -1)
> > + err(1, "unveil");
> > +#ifdef LOGGING
> > + if (unveil(logpath, "rwc") == -1)
> > + err(1, "unveil");
> > +
There are plans to adapt sysupgrade for upgrading to arbitrary snapshots
from the archives, to help everyone do bisect.
When that comes, all these proposed changes will be backwards.
Otto Moerbeek wrote:
> On Mon, May 27, 2019 at 04:16:01AM +0200, giovani...@tuta.io wrote:
>
> > Hello,
> >
>
Hello,
I had some problems connecting to my SSL enabled pure-ftpd server with
filezilla 3.42 (on windows) which uses GnuTLS 3.6.7. I am running
OpenBSD 6.5.
I opened a thread on filezilla forum and the developer claims this is
due to a bug in LibreSSL.
The thread is here:
On Sat, May 25, 2019 at 01:43:43AM -0500, Katherine Rohl wrote:
> (Side note, what console email program is
> the best for submitting these patches anyway?)
It doesn't really matter what tooling you use as long as it does not
mangle patches; typically, whitespace reformatting and line-wrapping
On Wed, May 22, 2019 at 08:05:50PM -0500, Katherine Rohl wrote:
> Hi,
>
> Adjusted NS8250 behavior in vmd(8) so it gets detected as an 8250 and not a
> 16450 by OpenBSD’s boot process. Also generalized some of the COM1-specific
> I/O address definitions to support adding COM2 (and COM3, and
On Sat, May 25, 2019 at 09:27:18PM +1000, Mitchell Krome wrote:
> I tracked this down to what I think is a typo. The code for updating the
> laststate and timer is looking at laststate before it's been updated.
> Patch below makes it work as expected
You're right, thanks. OK kn if anyone else
21 matches
Mail list logo
