The End of a Job as We Know It
http://www.forbes.com/sites/joshbersin/2012/01/31/the-end-of-a-job-as-we-know-it/
Re: How to have more than 15 pflog interfaces?
On Thu, Apr 12, 2012 at 3:44 AM, Henning Brauer lists-openbsdt...@bsws.de wrote: diffs are for current of course but should work for 5.1 as well - dunno what you are trying. Dear Henning, I have upgraded my firewall to 5.1 could you please give ma a unified diff or something I can try Thanks Siju
Re: How to have more than 15 pflog interfaces?
On Fri, Apr 13, 2012 at 1:40 PM, Henning Brauer henn...@openbsd.org wrote: if nobody tests this beyond my extremely light tests (try actually USING the pflog interfaces to log to, I didn't), I can't get this in :) I will test. getting a system up with current. Thanks --Siju
Re: How to have more than 15 pflog interfaces?
On Wed, Apr 11, 2012 at 3:50 PM, Henning Brauer lists-open...@bsws.de wrote: please try this report back Thanks Henning but I need some help :-( I got the following errors and I have attached the .rej files = # patch -p0 patch.if_pflog Hmm... Looks like a unified diff to me... The text leading up to this was: -- |Index: if_pflog.c |=== |RCS file: /cvs/src/sys/net/if_pflog.c,v |retrieving revision 1.49 |diff -u -p -r1.49 if_pflog.c |--- if_pflog.c 3 Feb 2012 01:57:50 - 1.49 |+++ if_pflog.c 11 Apr 2012 10:19:56 - -- File to patch: sys/net/if_pflog.c Patching file sys/net/if_pflog.c using Plan A... Hunk #1 failed at 80. Hunk #2 failed at 92. Hunk #3 failed at 110. Hunk #4 failed at 180. Hunk #5 failed at 256. 5 out of 5 hunks failed--saving rejects to sys/net/if_pflog.c.rej Hmm... The next patch looks like a unified diff to me... The text leading up to this was: -- |Index: pf_ioctl.c |=== |RCS file: /cvs/src/sys/net/pf_ioctl.c,v |retrieving revision 1.250 |diff -u -p -r1.250 pf_ioctl.c |--- pf_ioctl.c 3 Apr 2012 15:09:03 - 1.250 |+++ pf_ioctl.c 11 Apr 2012 10:19:57 - -- File to patch: sys/net/pf_ioctl.c Patching file sys/net/pf_ioctl.c using Plan A... Hunk #1 failed at 2595. 1 out of 1 hunks failed--saving rejects to sys/net/pf_ioctl.c.rej done === Thanks Siju [demime 1.01d removed an attachment of type application/octet-stream which had a name of if_pflog.c.rej] [demime 1.01d removed an attachment of type application/octet-stream which had a name of pf_ioctl.c.rej]
Re: How to have more than 15 pflog interfaces?
On Thu, Apr 12, 2012 at 3:44 AM, Henning Brauer lists-openbsdt...@bsws.de wrote: diffs are for current of course but should work for 5.1 as well - dunno what you are trying. Ok thanks :-) I am running 5.0 --Siju
Re: Allegations regarding OpenBSD IPSEC
On Fri, Dec 17, 2010 at 11:39 PM, Pawel Veselov pawel.vese...@gmail.com wrote: Whoa, wait a second here. B If you think I gave it credibility, you need to go back and read my words again. B I called it an allegation, and I stick with that. B I was extremely careful with my words, and you are wrong to interpret them as you do. Look, if somebody like me posted something like this here, it would be just plain dismissed. So it is good that Theo posted it here. He is serious about this allegation. Serious about proving if it is true or false. He has opened the invitation to any in order to acheive the objective. And he and others are dong the needful the outcome of which you will be able to see in a a couple or more of days. If Perry posted his email here, he'd just be under fire to show some or any proof. Well may be Theo does not fell the urge to push away responsibility on others? Being the project leader he is doing just what a responsible and accountable person will do. The reason this was so widely picked up and generated so much flame and buzz, is because you posted it here. So would you prefer he kept it secret? It's an unfortunate consequence of a right action, really. I'm not even remotely saying that you intended to give it weight, or that you should've swept it under the rug. Then waht are you tring to say? thanks --Siju
Invitation to connect on LinkedIn
LinkedIn I'd like to add you to my professional network on LinkedIn. - Siju Accept Siju George's invite: https://www.linkedin.com/e/isd/822153491/bbsdY9cj/ -- (c) 2009, LinkedIn Corporation
