Re: new feature in pkg_add(1)

On Wed, Jun 22, 2016 at 02:19:26PM +0200, Marc Espie wrote: > On Tue, Jun 21, 2016 at 10:43:07PM +0200, Patrik Lundin wrote: > > The reason for doing this is that it is much faster than just blindly > > trying to install a package, and does not hammer mirrors needlessly. > > > > Are there any

Re: Allow device/fifo creation with zipped archives

On Wed, Jun 22, 2016 at 09:02:03PM -0400, tro...@kagu-tsuchi.com wrote: > As brought up on misc@ pax doesn't allow creation of devices or fifos without > the p flag, however this is only when the archive is not compressed. If you > compress the archive, you can create them upon

Re: sqlite3 update

Stuart Henderson wrote: > Turns out I forgot about the pthread stubs, without which there > are build failures in mandoc and various ports things unless we link > them with -lpthread. This broke a few things in my first ports test > build, but thanks to guenther's work it should now be valid to

Re: opencvs - fix revision lookups for branches

Yes please. As noted in older thread that XXX block in rcs.c produced side effects with cvs annotate. https://marc.info/?l=openbsd-tech=144757775319206=2 On Wed, Jun 22, 2016 at 05:20:01PM +0200, Joris Vink wrote: > On Wed, Jun 22, 2016 at 09:07:03AM -0600, Todd C. Miller wrote: > > On Wed, 22

unit test for fix included in r1.13 of bin/cat/cat.c

Hello, The patch below adds a regress test to check the behaviour of cat when invoked with the flags '-se' to ensure blank lines contain a dollar sign. The attached patch reverts the fix from r1.13 on the latest version of cat which allowed me to perform a comparison test. This fix was committed

Allow device/fifo creation with zipped archives

As brought up on misc@ pax doesn't allow creation of devices or fifos without the p flag, however this is only when the archive is not compressed. If you compress the archive, you can create them upon decompression/unarchiving. Since dpath was added to allow creation of devices in the pledge

Re: sqlite3 update

On 2016/06/22 00:10, Stuart Henderson wrote: > On 2016/06/08 19:01, James Turner wrote: > > I prefer option 2. Switch to the amalgamation with our changes on top. > > I've been looking at this. I don't really like any of the options > but this seems the "least worst" one. I'm not terribly happy

Re: pf divert port reuse

On Wed, Jun 22, 2016 at 08:15:09PM +0200, Mike Belopuhov wrote: > Can you or benno test NAT64 with this change? > In case of weird behavior do this: > > int sidx = pd->af == pd->naf ? pd->sidx : pd->didx; > int didx = pd->af == pd->naf ? pd->didx : pd->sidx; > > And use sidx/didx throughout

Re: [PATCH] let the mbufs use more then 4gb of memory

> secondly, allocating more than 4g at a time to socket buffers is > generally a waste of memory. and there is one further problem. Eventually, this subsystem will starve the system. Other subsystems which also need large amounts of memory, then have to scramble. There have to be backpressure

Re: klog message buffer full

> But if install kernel size is not that important, I can remove both > ifdefs. Kernel size does matter on the ramdisks. But excessive sprinkling of #ifdef gets out of control in some types of code. Then it better to forego it, and find a different target where it is less gross. As long as we

Re: klog message buffer full

On Wed, Jun 22, 2016 at 05:08:24PM -0400, Ted Unangst wrote: > Alexander Bluhm wrote: > > +#ifndef SMALL_KERNEL > > + if (mbp->msg_bufd > 0) { > > + char buf[64]; > > This is not so much code that I'm worried about it on small kernels. Rather, > now you have the same problem where

Re: [PATCH] let the mbufs use more then 4gb of memory

On Wed, Jun 22, 2016 at 01:58:25PM +0200, Simon Mages wrote: > On a System where you use the maximum socketbuffer size of 256kbyte you > can run out of memory after less then 9k open sockets. > > My patch adds a new uvm_constraint for the mbufs with a bigger memory area. > I choose this area

Re: klog message buffer full

Alexander Bluhm wrote: > This also gets me closer to my goal of reliable logging. > > Do we want this feature? yes, and I'd say always. > +#ifndef SMALL_KERNEL > + if (mbp->msg_bufd > 0) { > + char buf[64]; This is not so much code that I'm worried about it on small kernels.

Re: klog message buffer full

On Wed, 22 Jun 2016 22:14:19 +0200, Alexander Bluhm wrote: > When doing usb debugging with a lot of kernel printfs, the dmesg > buffer can overflow easily. It is annoying that you don't notice > this. Then it is hard to correlate the messages. > > So to make clear what happens, I would like to

update nsd to 4.1.7 -> 4.1.10

Lightly tested, I will test AXFR with tsig tomorrow. tests / OKs? diff --git Makefile.in Makefile.in index 9103291..3fbd01b 100644 --- Makefile.in +++ Makefile.in @@ -439,9 +439,9 @@ xfrd-disk.o: $(srcdir)/xfrd-disk.c config.h $(srcdir)/xfrd-disk.h $(srcdir)/xfrd xfrd-notify.o:

klog message buffer full

Hi, When doing usb debugging with a lot of kernel printfs, the dmesg buffer can overflow easily. It is annoying that you don't notice this. Then it is hard to correlate the messages. So to make clear what happens, I would like to write such a message to syslogd: Jun 22 21:58:16 t430s /bsd:

Re: Stop mesa W^X violations

On Mon, Jun 20, 2016 at 10:22:58PM +0200, Mark Kettenis wrote: > As reported by several people, mesa contains code that violates W^X. > As a result glxgears aborts when using the swrast driver. The diff > below disables the offending code. The code seems to deal the absence > of W|X memory just

Re: pf divert port reuse

On Tue, Jun 21, 2016 at 05:12:39PM +0200, Mike Belopuhov wrote: > On Tue, Jun 21, 2016 at 16:08 +0200, Alexander Bluhm wrote: > > On Tue, Jun 21, 2016 at 02:45:42PM +0200, Mike Belopuhov wrote: > > > Unless I'm wrong, I have to retract my OK and ask you to fix > > > the sport bit instead. > > > >

Re: Deprecate flags DH_FLAG_NO_EXP_CONSTTIME and RSA_FLAG_NO_CONSTTIME

I'm wondering outloud it we should remove the #define, instead of leaving it in there. I.E. should we be deliberately breaking anything making use of that? At the very least this (along with the DH one) can probably #ifndef LIBRESSL_INTERNAL - and failing that should we nuke them and bump majors?

Re: add mirror discovery to pkg_add

>this is the exact same code that s currently in install.sub >transposed ad perl I get it. It makes sense for installing the base system. We started using it in pkg.conf. I am no longer sure that is the right thing to do. Speaking to the installation backend all the time worries me.

Re: add mirror discovery to pkg_add

this is the exact same code that s currently in install.sub transposed ad perl

Re: add mirror discovery to pkg_add

> On 06/22/16 18:57, Theo de Raadt wrote: > >>> Aside from that, i dont think we should be hardcoding ip-adresses like > >>> that. > >>> > >> we are doing that with miniroot/install.sub, time to change ? > > > > No, that is not what miniroot/install.sub does. Not at all. > > > I know, I just

Re: add mirror discovery to pkg_add

On 06/22/16 18:57, Theo de Raadt wrote: >>> Aside from that, i dont think we should be hardcoding ip-adresses like that. >>> >> we are doing that with miniroot/install.sub, time to change ? > > No, that is not what miniroot/install.sub does. Not at all. > I know, I just said that the ip address

Re: add mirror discovery to pkg_add

> > Aside from that, i dont think we should be hardcoding ip-adresses like that. > > > we are doing that with miniroot/install.sub, time to change ? No, that is not what miniroot/install.sub does. Not at all.

Re: add mirror discovery to pkg_add

On 06/22/16 18:28, Sebastian Benoit wrote: > Ted Unangst(t...@tedunangst.com) on 2016.06.22 12:25:04 -0400: >> Marc Espie wrote: >>> This would allow pkg_add to auto-configure a mirror, for the case where >>> PKG_PATH was not specified and where pkg.conf does not exist. >>> >>> It only triggers

Re: add mirror discovery to pkg_add

Ted Unangst(t...@tedunangst.com) on 2016.06.22 12:25:04 -0400: > Marc Espie wrote: > > This would allow pkg_add to auto-configure a mirror, for the case where > > PKG_PATH was not specified and where pkg.conf does not exist. > > > > It only triggers when a location ends up empty and when run in

Re: add mirror discovery to pkg_add

I agree with Ted. This feels very much like building a CDN at the wrong level, considering how slowly and carelessly the mirrors are updated at this time.

Re: add mirror discovery to pkg_add

Marc Espie wrote: > This would allow pkg_add to auto-configure a mirror, for the case where > PKG_PATH was not specified and where pkg.conf does not exist. > > It only triggers when a location ends up empty and when run in interactive > mode, e.g., it shouldn't interfere with local lookups. > >

Fwd: tcp state transition in sloppy mode

Thanks for help on this issue! -- Forwarded message -- From: Stuart Henderson Date: Wed, Jun 22, 2016 at 2:21 AM Subject: Re: tcp state transition in sloppy mode To: Jingmin Zhou Hi, Nice analysis. The PF mailing list is not very

Re: add mirror discovery to pkg_add

Here's an expanded version of the patch. So far, ask_list was happy with prompting, but the mirror list is slightly large, so being able to pipe thru more comes in handy. This means a bit of refactor: we've got state, so we can get the height from a progressmeter (or the stub), and it's

Re: opencvs - fix revision lookups for branches

On Wed, Jun 22, 2016 at 09:07:03AM -0600, Todd C. Miller wrote: > On Wed, 22 Jun 2016 12:21:56 +0200, Joris Vink wrote: > > Index: rcs.c > > === > > RCS file: /cvs/src/usr.bin/cvs/rcs.c,v > > retrieving revision 1.313 > > diff -u -p

Re: opencvs - fix revision lookups for branches

On Wed, 22 Jun 2016 12:21:56 +0200, Joris Vink wrote: > This diff below fixes a serious issue in opencvs when > checking out revisions from a branch. > > Properly perform a revision lookup so update -r actually > works again, as a bonus throw a more correct error when > the revision could not be

Add $REQUEST_SCHEME (block) macro to httpd

The patch below adds a "$REQUEST_SCHEME" macro to those available in block rules in httpd.conf Justification: when redirecting from a (virtual) server which supports both http and https to a (virtual) server which also supports both schemes, it make sense to be able to respect (preserve) the

add mirror discovery to pkg_add

Most of the code was already there. This would allow pkg_add to auto-configure a mirror, for the case where PKG_PATH was not specified and where pkg.conf does not exist. It only triggers when a location ends up empty and when run in interactive mode, e.g., it shouldn't interfere with local

Deprecate flags DH_FLAG_NO_EXP_CONSTTIME and RSA_FLAG_NO_CONSTTIME

This is another patch from César Pereida that disables the DH and RSA non-constant-time flags as well. ok? Index: src/crypto/dh/dh.h === RCS file: /cvs/src/lib/libssl/src/crypto/dh/dh.h,v retrieving revision 1.16 diff -u -p -u -p

iwm: lower retry limit for management frames

The Linux iwlwifi driver uses less retry attempts for management frames, as in the diff below. I think it makes sense to do likewise. Index: if_iwm.c === RCS file: /cvs/src/sys/dev/pci/if_iwm.c,v retrieving revision 1.92 diff -u -p

Re: [PATCH] let the mbufs use more then 4gb of memory

On Wed, Jun 22, 2016 at 01:58:25PM +0200, Simon Mages wrote: > On a System where you use the maximum socketbuffer size of 256kbyte you > can run out of memory after less then 9k open sockets. > > My patch adds a new uvm_constraint for the mbufs with a bigger memory area. > I choose this area

Re: new feature in pkg_add(1)

On Tue, Jun 21, 2016 at 10:43:07PM +0200, Patrik Lundin wrote: > The reason for doing this is that it is much faster than just blindly > trying to install a package, and does not hammer mirrors needlessly. > > Are there any plans to teach pkg_info -e about "%"? Is it even possible? Okay, just

Re: new feature in pkg_add(1)

On Tue, Jun 21, 2016 at 10:43:07PM +0200, Patrik Lundin wrote: > However, "pkg_info -e" does not understand it: > === > # pkg_info -e python%2.7 > Invalid spec: python%2.7 > === > > I use pkg_info -e to check if a requested package is installed or > not prior to attempting to install/remove it. >

[PATCH] let the mbufs use more then 4gb of memory

On a System where you use the maximum socketbuffer size of 256kbyte you can run out of memory after less then 9k open sockets. My patch adds a new uvm_constraint for the mbufs with a bigger memory area. I choose this area after reading the comments in sys/arch/amd64/include/pmap.h. This patch

opencvs - log command fixes

Hi, Brings log a bit more inline with its GNU counterpart by attempting to parse the date range early on, killing extra output from date.y and having a proper fatal message. Any caller of date_parse() already displays its own error messages anyway if it fails. Additionally lets not return -1

opencvs - use correct size when creating h_table

Hi, Don't allocate the length of a pointer but rather the entire size of the struct hash_head data structure when creating the h_table array. .joris Index: hash.c === RCS file: /cvs/src/usr.bin/cvs/hash.c,v retrieving revision 1.2

opencvs - fix signed vs unsigned type confusion across opencvs.

Hi, The diff below fixes several signed vs unsigned type confusion warnings and shuffles some assignments around. .joris Index: buf.c === RCS file: /cvs/src/usr.bin/cvs/buf.c,v retrieving revision 1.83 diff -u -p -r1.83 buf.c ---

opencvs - correct type of p in annotate

Hi, Use the correct type for p. .joris Index: annotate.c === RCS file: /cvs/src/usr.bin/cvs/annotate.c,v retrieving revision 1.65 diff -u -p -r1.65 annotate.c --- annotate.c 5 Nov 2015 09:48:21 - 1.65 +++ annotate.c 22

opencvs - fix revision lookups for branches

Hi, This diff below fixes a serious issue in opencvs when checking out revisions from a branch. Properly perform a revision lookup so update -r actually works again, as a bonus throw a more correct error when the revision could not be found. .joris Index: rcs.c