Re: Stop the madness in radix.c take 2

2014-01-18 Thread Mike Belopuhov
On Sun, Jan 19, 2014 at 06:37 +0100, Claudio Jeker wrote: > On Sun, Jan 19, 2014 at 06:15:06AM +0100, Mike Belopuhov wrote: > > On Sun, Jan 19, 2014 at 05:42 +0100, Claudio Jeker wrote: > > > Here is more cleanup. > > > > > > Kill the MKget MKfree madness and replace it with *drummrolls* > > > a p

Re: Stop the madness in radix.c take 2

2014-01-18 Thread Claudio Jeker
On Sun, Jan 19, 2014 at 06:15:06AM +0100, Mike Belopuhov wrote: > On Sun, Jan 19, 2014 at 05:42 +0100, Claudio Jeker wrote: > > Here is more cleanup. > > > > Kill the MKget MKfree madness and replace it with *drummrolls* > > a pool(9). Makes the code a lot easier to digest. > > Better? -- :wq

Re: Stop the madness in radix.c take 2

2014-01-18 Thread Mike Belopuhov
On Sun, Jan 19, 2014 at 05:42 +0100, Claudio Jeker wrote: > Here is more cleanup. > > Kill the MKget MKfree madness and replace it with *drummrolls* > a pool(9). Makes the code a lot easier to digest. > > -- > :wq Claudio > > Index: net/radix.c >

Re: rc default PF ruleset too restrictive for DHCPv6

2014-01-18 Thread Kenneth Westerback
send_packet() sends packets out a raw socket unless the destination is INADDR_BROADCAST, in which case it sends the packet out via bpf. Ken On 19 Jan 2014 17:33, "Brad Smith" wrote: > On Sun, Jan 19, 2014 at 04:10:21AM +0100, Claudio Jeker wrote: > > On Sat, Jan 18, 2014 at 09:57:26PM -0500

Stop the madness in radix.c take 2

2014-01-18 Thread Claudio Jeker
Here is more cleanup. Kill the MKget MKfree madness and replace it with *drummrolls* a pool(9). Makes the code a lot easier to digest. -- :wq Claudio Index: net/radix.c === RCS file: /cvs/src/sys/net/radix.c,v retrieving revision 1

Re: rc default PF ruleset too restrictive for DHCPv6

2014-01-18 Thread Brad Smith
On Sun, Jan 19, 2014 at 04:10:21AM +0100, Claudio Jeker wrote: > On Sat, Jan 18, 2014 at 09:57:26PM -0500, Brad wrote: > > On Thu, Jan 09, 2014 at 03:55:44PM -0500, Brad Smith wrote: > > > The default PF ruleset as setup by rc is too restrictive. Have the default > > > ruleset allow for DHCPv6. > >

Re: rc default PF ruleset too restrictive for DHCPv6

2014-01-18 Thread Todd T. Fries
This seems to make sense. ok todd@. Please get at least one other ok though. Penned by Brad Smith on 20140118 20:57.26, we have: | On Thu, Jan 09, 2014 at 03:55:44PM -0500, Brad Smith wrote: | > The default PF ruleset as setup by rc is too restrictive. Have the default | > ruleset all

Re: Stop the madness in radix.c

2014-01-18 Thread Mike Belopuhov
On 19 January 2014 16:35, Claudio Jeker wrote: > We no longer use radix.c in userland since routed(8) was killed > aeons ago. There is no need for this madness anymore so remove it. OK

Stop the madness in radix.c

2014-01-18 Thread Claudio Jeker
We no longer use radix.c in userland since routed(8) was killed aeons ago. There is no need for this madness anymore so remove it. -- :wq Claudio Index: radix.c === RCS file: /cvs/src/sys/net/radix.c,v retrieving revision 1.34 diff

Re: rc default PF ruleset too restrictive for DHCPv6

2014-01-18 Thread Claudio Jeker
On Sat, Jan 18, 2014 at 09:57:26PM -0500, Brad wrote: > On Thu, Jan 09, 2014 at 03:55:44PM -0500, Brad Smith wrote: > > The default PF ruleset as setup by rc is too restrictive. Have the default > > ruleset allow for DHCPv6. > > Anyone? Looks good to me. OK claudio@ Question: should we add the s

Re: rc default PF ruleset too restrictive for DHCPv6

2014-01-18 Thread Mike Belopuhov
On 19 January 2014 15:57, Brad Smith wrote: > On Thu, Jan 09, 2014 at 03:55:44PM -0500, Brad Smith wrote: >> The default PF ruleset as setup by rc is too restrictive. Have the default >> ruleset allow for DHCPv6. > > Anyone? > yes, i think this is ok.

Re: Request for Funding our Electricity

2014-01-18 Thread Kent R. Spillner
On Jan 18, 2014, at 16:25, Sia Lang wrote: > If the tests are as good as this project claims them to be, the process > should take exactly one test cycle. If that's the case, then the test regime > suck big time. Logic brother. Logic. I don't know what tests you're referring to. OpenBSD bui

Re: rc default PF ruleset too restrictive for DHCPv6

2014-01-18 Thread Brad Smith
On Thu, Jan 09, 2014 at 03:55:44PM -0500, Brad Smith wrote: > The default PF ruleset as setup by rc is too restrictive. Have the default > ruleset allow for DHCPv6. Anyone? > Index: rc > === > RCS file: /home/cvs/src/etc/rc,v > retri

Re: remove max_datalen since it is used only once

2014-01-18 Thread Mike Belopuhov
On 19 January 2014 12:39, Claudio Jeker wrote: > Subject sais it all. One less gloabl symbol. > > -- > :wq Claudio > OK

Re: Request for Funding our Electricity

2014-01-18 Thread MJ
On 19 Jan 2014, at 01.36, Jan Stary wrote: > > So, the 1 is the thought, and the 0 is the amount? > > Sorry, but your comments were so ridiculous I couldn't help it. > Saying it's the thougth that counts to people who have > repeated explicitly they need MONEY. There you go again with your sim

Re: Request for Funding our Electricity

2014-01-18 Thread MJ
On 18 Jan 2014, at 20.15, Jan Stary wrote: > On Jan 18 16:29:46, m...@sci.fi wrote: >> On 18 Jan 2014, at 04.33, Theo de Raadt wrote: >> And I hope it?s the thought that counts more than the amount. > > LOL, yes, especially when it comes to bills being paid. > You, too, sir, can also take an

Re: OPENBSD FUNDING SOLUTION -- COME AND PARTICIPATE

2014-01-18 Thread MJ
On 18 Jan 2014, at 22.25, Chris Cappuccio wrote: > Mike, maybe you can stop your rambling, and just do the same. Because > otherwise, I don't understand why you feel justified to be on this mailing > list. You were henning's roommate, so that means that you know all about > OpenBSD, programming,

remove max_datalen since it is used only once

2014-01-18 Thread Claudio Jeker
Subject sais it all. One less gloabl symbol. -- :wq Claudio Index: kern/uipc_domain.c === RCS file: /cvs/src/sys/kern/uipc_domain.c,v retrieving revision 1.33 diff -u -p -r1.33 uipc_domain.c --- kern/uipc_domain.c 20 Aug 2013 09:14

signify output

2014-01-18 Thread Fritjof Bornebusch
Hi tech, this diff changes the readpassphrase call to be more like described in the manpage. On the users site "readpassphrase" doesn't really show what the problem is. On the developers site the flag 0 is not described in the manpage. Regards, Fritjof Index: signify.c =

report icmp error drops because of rate limiting

2014-01-18 Thread Claudio Jeker
As done in IPv6 land report how many packets are dropped because we hit the rate limiter (net.inet.icmp.errppslimit). On bigger routers it may be needed to tune that value up in case to many packets are dropped. OK? -- :wq Claudio Index: sys/netinet/icmp_var.h ===

Re: fw_update manpage examples

2014-01-18 Thread Fritjof Bornebusch
Theo de Raadt schrieb am Sat, 18. Jan 15:42: > > > this page does not need an EXAMPLES section. > > > jmc > > What are the criteria to add an EXAMPLES section to a manpage? > > Examples should cover either "slightly non-obvious but powerful" usage > cases that are not entirely expected, and thus

Re: fw_update manpage examples

2014-01-18 Thread Jason McIntyre
On Sat, Jan 18, 2014 at 03:42:50PM -0700, Theo de Raadt wrote: > > > this page does not need an EXAMPLES section. > > > jmc > > What are the criteria to add an EXAMPLES section to a manpage? > > Examples should cover either "slightly non-obvious but powerful" usage > cases that are not entirely ex

Re: fw_update manpage examples

2014-01-18 Thread Theo de Raadt
> > this page does not need an EXAMPLES section. > > jmc > What are the criteria to add an EXAMPLES section to a manpage? Examples should cover either "slightly non-obvious but powerful" usage cases that are not entirely expected, and thus lead people to seeing the power of the command. An exampl

Re: fw_update manpage examples

2014-01-18 Thread Fritjof Bornebusch
Theo de Raadt schrieb am Sat, 18. Jan 15:02: > > I have added some examples to the fw_update manpage, to show how you > > can install, update or delete a firmware package. It tooks a little > > while until I figured out how fw_update works, so maybe it can help > > the next one. > > You sure did

Re: fw_update manpage examples

2014-01-18 Thread Fritjof Bornebusch
Jason McIntyre schrieb am Sat, 18. Jan 21:56: > On Sat, Jan 18, 2014 at 10:28:18PM +0100, Fritjof Bornebusch wrote: > > Hi tech, > > > > I have added some examples to the fw_update manpage, to show how you can > > install, update or delete a firmware package. > > It tooks a little while until I

Re: Request for Funding our Electricity

2014-01-18 Thread Theo de Raadt
> > The old hardware would still run while they're validating the emulators, > > and that process would probably take a really long time. > > > > If the tests are as good as this project claims them to be, the process > should take exactly one test cycle. If that's the case, then the test > regime

Re: fw_update manpage examples

2014-01-18 Thread Theo de Raadt
> I have added some examples to the fw_update manpage, to show how you > can install, update or delete a firmware package. It tooks a little > while until I figured out how fw_update works, so maybe it can help > the next one. You sure did spot a real problem in the man page, which is that it doe

Re: fw_update manpage examples

2014-01-18 Thread Jason McIntyre
On Sat, Jan 18, 2014 at 10:28:18PM +0100, Fritjof Bornebusch wrote: > Hi tech, > > I have added some examples to the fw_update manpage, to show how you can > install, update or delete a firmware package. > It tooks a little while until I figured out how fw_update works, so maybe it > can help th

Re: lpd: race condition

2014-01-18 Thread Todd C. Miller
Perhaps something like this? Only compile-tested. - todd Index: usr.sbin/lpr/lpd/printjob.c === RCS file: /home/cvs/openbsd/src/usr.sbin/lpr/lpd/printjob.c,v retrieving revision 1.49 diff -u -r1.49 printjob.c --- usr.sbin/lpr/lpd/p

fw_update manpage examples

2014-01-18 Thread Fritjof Bornebusch
Hi tech, I have added some examples to the fw_update manpage, to show how you can install, update or delete a firmware package. It tooks a little while until I figured out how fw_update works, so maybe it can help the next one. Regards, Fritjof Index: fw_update.1 ==

iopools for sparc64/vdsk(4)

2014-01-18 Thread David Gwynne
this gets rid of NO_CCB in vdsk. it considers space on the tx ring as the resource the iopool is managing, but gated by the availability of the service domain. it takes advantage of the newly available scsi_iopool_run() interface to restart io when the domain providing a disk comes back. is anyone

OPENBSD FUNDING SOLUTION -- COME AND PARTICIPATE

2014-01-18 Thread Chris Cappuccio
MJ [m...@sci.fi] wrote: > > On 18 Jan 2014, at 04.33, Theo de Raadt wrote: > > > > Why is there this effort to convince us to do less? > > > > I do not propagate such a train of thought; only said that if you want > corporate funding then be prepared to detail your costs and justify each and

pflow(4) with optional flowsrc

2014-01-18 Thread Nathanael Rensen
Some time ago I proposed a diff to allow pflow(4) to determine the src IP address based on the route table if flowsrc was not specified. That diff was not accepted because having multiple places look up route tables is undesirable. Since then henning@ moved UDP checksum calcs into ip_output. That

Re: Request for Funding our Electricity

2014-01-18 Thread MJ
On 18 Jan 2014, at 04.33, Theo de Raadt wrote: > > Why is there this effort to convince us to do less? > I do not propagate such a train of thought; only said that if you want corporate funding then be prepared to detail your costs and justify each and every one of them as well as satisfying

libedit: retain local changes

2014-01-18 Thread Tobias Stoeckmann
Hi, back in OpenBSD 5.0 times, there was a merge with NetBSD's libedit. It was supposed to retain local modifications, but unfortunately they got lost. In el.c, they got reintroduced with revision 1.18, but the following ones are still lost: history.c: revision 1.13 term.c: revision 1.13 Tobi

Re: signed packages

2014-01-18 Thread Marc Espie
On Fri, Jan 17, 2014 at 12:39:49PM -0500, sven falempin wrote: > i read the manuals , and well , i am still unsure, > > if i put SIGNER=bob in the package configuration > > then it will be signed with > > /etc/signify/bob.sec > > having to read 4 different manual page to get this is strange :p

Re: Request for Funding our Electricity

2014-01-18 Thread Kent R. Spillner
I notice a lot of people have suggested "use an emulator," as if that had never occurred to the OpenBSD developers before, but nobody has volunteered to verify that the available emulators are good enough to actually replace real hardware. Also, I don't understand why anyone thinks emulation wou

Re: Request for Funding our Electricity

2014-01-18 Thread Aram Hăvărneanu
On Sat, Jan 18, 2014 at 7:53 AM, Brett Lymn wrote: > On Fri, Jan 17, 2014 at 07:33:01PM -0700, Theo de Raadt wrote: >> >> What other community has users who commonly run upstream software on >> 64-bit big-endian strict alignment platform with register windows >> adjusting the frames in odd ways, o

Re: Request for Funding our Electricity

2014-01-18 Thread Philipp
Am 17.01.2014 22:14 schrieb Kevin Lyda: That's a bug to be filed against an emulator. And it's easier to do that *now* when the older hardware is around to test for bug compatibility. And how do you do that when the hardware has gone? And I must admit the resistance to this is weird. This a

Re: Request for Funding our Electricity

2014-01-18 Thread Kenneth Gober
I do not doubt that emulators can be useful for some things. Indeed, I use them myself when real hardware isn't available. but emulators have limits -- invariably they are written to emulate certain things accurately (albeit imperfectly, because all programmers make mistakes) while other things d