Re: binutils-2.17 ownership fixes

On Thu, Sep 15, 2016 at 1:58 PM, Martin Natano wrote: > This should do it. The 'fix' is ugly, but I couldn't find a cleaner way > to pass the right STRIP value to libtool. Any better ideas? Ok? ... > --- gnu/usr.bin/binutils-2.17/Makefile.bsd-wrapper 11 Sep 2016 07:42:02

Re: rebound quantum entanglement

Theo de Raadt [dera...@openbsd.org] wrote: > > That rebound acts like a nameserver is what prompted the idea to > > hijack the resolver. But it's really a tool that takes over certain > > duties from the libc resolver, so the libc resolver should be properly > > configurable to hand over duties,

Re: rebound quantum entanglement

Ted Unangst wrote: > So the plan is for rebound to be the 'system' resolver, with libc talking to > rbeound and rebound talking to the cloud. The main wrinkle is how does rebound > find the cloud? rebound.conf, but dhclient doesn't know anything about > rebound.conf, preferring to edit

Re: ifconfig(8) rdomain pseudogroup

On Thu, Sep 15, 2016 at 09:27:00PM +, Ivan Markin wrote: > Jason McIntyre: > > ...then isn't it covered by the notes already attached to "interface"? > > > > Otherwise all interfaces of the same type will be displayed (for > > example, ``fxp'' will display all fxp(4) interfaces). > >

Re: ifconfig(8) rdomain pseudogroup

Jason McIntyre: > Otherwise all interfaces of the same type will be displayed (for > example, ``fxp'' will display all fxp(4) interfaces). btw, what is called here 'type' is actually 'name' from above. I.e. it's driver type, not a generic type (which is 'rdomain'). -- Ivan Markin

Re: ifconfig(8) rdomain pseudogroup

Jason McIntyre: > ...then isn't it covered by the notes already attached to "interface"? > > Otherwise all interfaces of the same type will be displayed (for > example, ``fxp'' will display all fxp(4) interfaces). Right, it seems to be. But is 'rdomain' a type? We'll get 255 new

Re: ifconfig(8) rdomain pseudogroup

On Thu, Sep 15, 2016 at 09:10:00PM +, Ivan Markin wrote: > Jason McIntyre: > > i think the "group" description of ifconfig(8) would be the more logical > > place to document this. > > Even if it is not a real group? 'rdomain' pseudogroup is only used to > display interfaces. One can't

Re: ifconfig(8) rdomain pseudogroup

Jason McIntyre: > i think the "group" description of ifconfig(8) would be the more logical > place to document this. Even if it is not a real group? 'rdomain' pseudogroup is only used to display interfaces. One can't actually consider it as a group. -- Ivan Markin

Re: ifconfig(8) rdomain pseudogroup

On Thu, Sep 15, 2016 at 08:52:00PM +, Ivan Markin wrote: > Hi tech@, > > After some struggling with manual looking for the interfaces attached to > particular rdomain, I added such option to ifconfig(8). So now it > behaves like there is a 'group' for each rdomain. > > i think the "group"

Re: binutils-2.17 ownership fixes

> install: strip: No such file or directory > > Is there a better option than removing it again? > > > $ cd /usr/src/gnu/usr.bin/binutils-2.17 > $ doas make -f Makefile.bsd-wapper install > [...] > Making install in po > test -z "/usr/bin" || /bin/sh >

Re: rebound quantum entanglement

> That rebound acts like a nameserver is what prompted the idea to > hijack the resolver. But it's really a tool that takes over certain > duties from the libc resolver, so the libc resolver should be properly > configurable to hand over duties, or not. 'search' is the logical > place for this.

Re: rebound quantum entanglement

On Thu, 15 Sep 2016, Chris Cappuccio wrote: > That rebound acts like a nameserver is what prompted the idea to > hijack the resolver. But it's really a tool that takes over certain > duties from the libc resolver, so the libc resolver should be properly > configurable to hand over duties, or not.

Re: rebound quantum entanglement

Bryan Steele [bry...@gmail.com] wrote: > On Thu, Sep 15, 2016 at 10:14:51AM -0400, Ted Unangst wrote: > > Florian Obser wrote: > > > Not everything listening on localhost port 53 is a recursive resolver. > > > nsd(8) per defaults listens on 0.0.0.0 and will respond with REFUSED for > > > almost

Re: teach BFD how to send route messages

On 2016 Sep 15 (Thu) at 14:47:24 +0200 (+0200), Peter Hessler wrote: :On 2016 Sep 15 (Thu) at 13:28:10 +0200 (+0200), Martin Pieuchot wrote: ::On 14/09/16(Wed) 15:50, Peter Hessler wrote: ::> + ::> + bfd = pool_get(_pool_msghdr, PR_WAITOK | PR_ZERO); :: ::This doesn't make sense you're

Re: binutils-2.17 ownership fixes

Theo Buehler writes: > On Sat, Sep 10, 2016 at 07:01:20PM -0700, Philip Guenther wrote: >> On Sat, 10 Sep 2016, Philip Guenther wrote: >> > Same diff as binutils, with same open question: >> > >> > > Maybe we should add ${INSTALL_STRIP} to the INSTALL_PROGRAM assignment >> >

Re: binutils-2.17 ownership fixes

On Sat, Sep 10, 2016 at 07:01:20PM -0700, Philip Guenther wrote: > On Sat, 10 Sep 2016, Philip Guenther wrote: > > Same diff as binutils, with same open question: > > > > > Maybe we should add ${INSTALL_STRIP} to the INSTALL_PROGRAM assignment > > > here? > > Here's the combined diff that does

Re: Improve error message in rcctl(8)

Antoine, I've been following this thread and noted that you did add _rc_check_name to rc.subr and call it in rcctl. This looks clean and comprehensive. Two thoughts, however: 1. I had to look at the pattern match in _rc_check_name for a while before I understood it; the suggestion below makes

netinet bcopy->memcpy

Hello - Here is another diff to switch some bcopy's to memcpy's. Most bcopy's are on freshly alloc'd memory. for netinet/ Index: ip_ah.c === RCS file: /cvs/src/sys/netinet/ip_ah.c,v retrieving revision 1.122 diff -u -p -r1.122

Re: video(1): Use read(2) to read file specified with -i

On Thu, Sep 15, 2016 at 02:57:16PM +0200, Jeremie Courreges-Anglas wrote: > [...] > I think this is the right way to work around the problem and make > video(1) more user-friendly. However, I doubt that the manpage bits are > relevant. So I'd like to commit only the .c diff. > > Thoughts? >

Re: rebound quantum entanglement

On 2016/09/15 06:23, Jiri B wrote: > On Thu, Sep 15, 2016 at 10:04:00AM +0100, Stuart Henderson wrote: > > > What about this: > > > > > > Add "rebound" as possible value to the lookup keyword in resolv.conf. > > > If this is set the libc resolver sends dns requests to the unix socket > > >

Re: rebound quantum entanglement

On Thu, Sep 15, 2016 at 10:14:51AM -0400, Ted Unangst wrote: > Florian Obser wrote: > > Not everything listening on localhost port 53 is a recursive resolver. > > nsd(8) per defaults listens on 0.0.0.0 and will respond with REFUSED for > > almost every query. asr stops in that case and does not

Re: teach BFD how to send route messages

On 2016 Sep 15 (Thu) at 16:18:46 +0200 (+0200), Henning Brauer wrote: :* Peter Hessler [2016-09-15 14:48]: :> On 2016 Sep 15 (Thu) at 13:28:10 +0200 (+0200), Martin Pieuchot wrote: :> :By the way 'softc' is generally for device drivers, you might prefer :> :something like

timeout_set_proc(9)

After discussing with a few people about a new "timed task" API I came to the conclusion that mixing timeouts and tasks will result in: - always including a 'struct timeout' in a 'struct task', or the other the way around or - introducing a new data structure, hence API. Since I'd

Re: rebound quantum entanglement

* Ted Unangst [2016-09-15 16:15]: > The good news is I think we can still bind to > localhost:53 if nsd is on *:53 (right?). right. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services GmbH, http://bsws.de, Full-Service ISP Secure Hosting, Mail and DNS.

Re: teach BFD how to send route messages

* Peter Hessler [2016-09-15 14:48]: > On 2016 Sep 15 (Thu) at 13:28:10 +0200 (+0200), Martin Pieuchot wrote: > :By the way 'softc' is generally for device drivers, you might prefer > :something like bfdd (d for descriptor). > There's be a whole lot of bikeshedding about this

Re: rebound quantum entanglement

Florian Obser wrote: > Not everything listening on localhost port 53 is a recursive resolver. > nsd(8) per defaults listens on 0.0.0.0 and will respond with REFUSED for > almost every query. asr stops in that case and does not try the next > resolver in the list. Ah! There's the catch. The good

Re: random malloc junk

Otto Moerbeek wrote: > On Wed, Sep 14, 2016 at 12:53:05PM -0400, Ted Unangst wrote: > > > Daniel Micay wrote: > > > > > > The current OpenBSD code only wipes up to MALLOC_MAXCHUNK with junk @ 1, > > > and it similarly doesn't wipe at all with 'U' (even though junk-on-free > > > also serves the

Re: teach BFD how to send route messages

> :By the way 'softc' is generally for device drivers, you might prefer > :something like bfdd (d for descriptor). > > There's be a whole lot of bikeshedding about this topic, I would prefer > not to change it for now. It should be changed. mpi is right. That variable naming should only refer

Re: video(1): Use read(2) to read file specified with -i

Gregor Best writes: > Hi, Hi, > video(1) fails to read files that were previously recorded with -o > somefile, unless -g (to select read(2) as the input method) is also > specified: > >$ video -o foo >^C >$ video -i foo >video: ioctl VIDIOC_REQBUFS: Bad file

Re: rebound quantum entanglement

On Wed, Sep 14, 2016 at 09:19:07PM -0400, Ted Unangst wrote: > So the plan is for rebound to be the 'system' resolver, with libc talking to > rbeound and rebound talking to the cloud. The main wrinkle is how does rebound > find the cloud? rebound.conf, but dhclient doesn't know anything about >

Re: CPUID: Check for PTM and HWP features

Thanks for noticing this! Here's an updated diff. I also included Hardware Duty Cycling (HDC) tests. Index: arch/amd64/include/specialreg.h === RCS file: /cvs/src/sys/arch/amd64/include/specialreg.h,v retrieving revision 1.48 diff

Re: rebound quantum entanglement

On Thu, Sep 15, 2016 at 10:04:00AM +0100, Stuart Henderson wrote: > On 2016/09/15 10:39, Remi Locherer wrote: > > On Wed, Sep 14, 2016 at 08:10:29PM -0600, Theo de Raadt wrote: > > > > > wont this also mean if it is not running i have to wait for the > > > > > localhost > > > > > attempt to fail

Re: teach BFD how to send route messages

On 14/09/16(Wed) 15:50, Peter Hessler wrote: > This is a work-in-progress diff that I would like to commit. I can print > a few things, but there is a problem when trying to bring in more > fields. Printing is also ugly, but I can fix that in-tree. Well you're mixing multiples things in one

Re: rebound quantum entanglement

On 2016/09/15 10:39, Remi Locherer wrote: > On Wed, Sep 14, 2016 at 08:10:29PM -0600, Theo de Raadt wrote: > > > > wont this also mean if it is not running i have to wait for the > > > > localhost > > > > attempt to fail before the resolver moves on? (ASR_STATE_NEXT_NS, etc) > > > > so i > > > >

Re: rebound quantum entanglement

On Wed, Sep 14, 2016 at 08:10:29PM -0600, Theo de Raadt wrote: > > > wont this also mean if it is not running i have to wait for the localhost > > > attempt to fail before the resolver moves on? (ASR_STATE_NEXT_NS, etc) so > > > i > > > slow everything down for a timeout? > > > > Not if he

Re: rebound quantum entanglement

On Wed, Sep 14, 2016 at 09:19:07PM -0400, Ted Unangst wrote: > And so I present the following diff to enable a smooth transition. It's > 'quantum' because it works whether or not rebound is running. No need to open > the box. I'm sure there's a cat(ch)... -- Erling Westenvik

Re: OMAP4/5 Wake-up generator driver

> Date: Thu, 15 Sep 2016 14:53:14 +1000 > From: Jonathan Gray > > It turns out on OMAP4/OMAP5 there is a "Wake-up generator" > interrupt controller that routes interrupts to the GIC and does power > management comparable to imx with the i.MX6 General Power Controller > (GPC). >

LibreSSL selects weak digest for (EC)DH

Hi, I would like to fix this SNI issue. reported by @davidben https://github.com/libressl-portable/openbsd/issues/69 #3560: OpenSSL selects weak digest for (EC)DH https://rt.openssl.org/Ticket/Display.html?id=3560 original OpenSSL commit is here.

move uvm_map_addr to RBT code

this tree uses all the red-black tree features, so its an interesting test of the RBT code. it uses the augment functionality in red black trees, which nothing else does, and poisons nodes. we dont have any other trees that do this. we also get some space back, of course. ok? Index: