Bug in command line switch parsing in lpr.c

2013-02-14 Thread Jared S. Candelaria
Hi, In usr.sbin/lpr/lpr/lpr.c there isn't a break in the case for '#' when there should be. Here's a patch to fix it from writing a pointer where it shouldn't. Thanks! --- lpr.c 2009-10-29 00:34:48.0 -0400 +++ lpr.patched.c 2013-02-14 17:46:28.364251608 -0500 @@ -150,6 +150,7

Re: Security and ignorance from the major ISPs

2013-02-14 Thread Geoff Steckel
On 02/14/2013 06:40 PM, Ryan Freeman wrote On Thu, Feb 14, 2013 at 04:20:30PM -0700, Daniel Bertrand wrote: Hello, Thanks for providing such great software. It really is much appreciated. I was wondering what your stance is about the constant hack attempts on machines on our ISP networks..

Re: Security and ignorance from the major ISPs

2013-02-14 Thread Bob Beck
I'd reccomend http://www.openbsd.org/books.html#book8 It's a very good way to learn pf enough to deal with it. On Thu, Feb 14, 2013 at 4:20 PM, Daniel Bertrand wrote: > Hello, > > Thanks for providing such great software. It really is much appreciated. > > I was wondering what your stance is

Re: Security and ignorance from the major ISPs

2013-02-14 Thread Ryan Freeman
On Thu, Feb 14, 2013 at 04:20:30PM -0700, Daniel Bertrand wrote: > Hello, > > Thanks for providing such great software. It really is much appreciated. > > I was wondering what your stance is about the constant hack attempts on > machines on our ISP networks.. > > I see CONSTANT scanning for por

Security and ignorance from the major ISPs

2013-02-14 Thread Daniel Bertrand
Hello, Thanks for providing such great software. It really is much appreciated. I was wondering what your stance is about the constant hack attempts on machines on our ISP networks.. I see CONSTANT scanning for ports from all over the world, mostly from Italy, Russia, and China. Every firewal

Re: install(1) confusing error message

2013-02-14 Thread Bob Beck
Yes. absolutely.. ok On Thu, Feb 14, 2013 at 1:38 PM, Miod Vallat wrote: > This is what happens when install(1) is used to install files on a > read-only filesystem: > > # mount -u -o ro /usr > # cd /usr/src > # make build > cd /usr/src/share/mk && exec make install > install -c -o root -g bin -

Re: man pages: wireless frequency nit 2GHz vs 2.4GHz

2013-02-14 Thread Amit Kulkarni
> > a section of athn.4 manpage is fluff, information is repeated twice. once > > in words, other times in a table summarizing the list of working/supported > > chips. the same manpage was copied over for iwn, a table of supported chips > > would be nice in there too. if there's any interest i will

Re: install(1) confusing error message

2013-02-14 Thread Kenneth R Westerback
On Thu, Feb 14, 2013 at 08:38:02PM +, Miod Vallat wrote: > This is what happens when install(1) is used to install files on a > read-only filesystem: > > # mount -u -o ro /usr > # cd /usr/src > # make build > cd /usr/src/share/mk && exec make install > install -c -o root -g bin -m 444 bsd.REA

mg(1) M-{} line number fix

2013-02-14 Thread Mark Lumsden
Fix forward-paragraph and backward-paragraph's handling of line numbers. ok? -lum Index: paragraph.c === RCS file: /cvs/src/usr.bin/mg/paragraph.c,v retrieving revision 1.22 diff -u -p -r1.22 paragraph.c --- paragraph.c 29 Nov 2011

install(1) confusing error message

2013-02-14 Thread Miod Vallat
This is what happens when install(1) is used to install files on a read-only filesystem: # mount -u -o ro /usr # cd /usr/src # make build cd /usr/src/share/mk && exec make install install -c -o root -g bin -m 444 bsd.README bsd.dep.mk bsd.lib.mk bsd.man.mk bsd.nls.mk bsd.obj.mk bsd.own.mk bsd.p

Re: man pages: wireless frequency nit 2GHz vs 2.4GHz

2013-02-14 Thread Stuart Henderson
On 2013/02/14 17:47, Jason McIntyre wrote: > On Thu, Feb 14, 2013 at 10:53:54AM -0600, Amit Kulkarni wrote: > > On Thu, Feb 14, 2013 at 6:33 AM, Stuart Henderson > > wrote: > > > > > Amit Kulkarni gmail.com> writes: > > > > > > > > > > > I was reading the manpages of athn/iwn for purchasing a su

Re: man pages: wireless frequency nit 2GHz vs 2.4GHz

2013-02-14 Thread Jason McIntyre
On Thu, Feb 14, 2013 at 10:53:54AM -0600, Amit Kulkarni wrote: > On Thu, Feb 14, 2013 at 6:33 AM, Stuart Henderson wrote: > > > Amit Kulkarni gmail.com> writes: > > > > > > > > I was reading the manpages of athn/iwn for purchasing a suitable > > wireless card > > and found repeated > > > occurenc

Re: man pages: wireless frequency nit 2GHz vs 2.4GHz

2013-02-14 Thread Chris Cappuccio
Amit Kulkarni [amitk...@gmail.com] wrote: > I was reading the manpages of athn/iwn for purchasing a suitable wireless > card and found repeated occurences of 2GHz, when in fact it should be 2.4GHz. > That is the standard frequency when purchasing a wireless a/b/g/n card. The > code is filled wit

Re: man pages: wireless frequency nit 2GHz vs 2.4GHz

2013-02-14 Thread Amit Kulkarni
On Thu, Feb 14, 2013 at 6:33 AM, Stuart Henderson wrote: > Amit Kulkarni gmail.com> writes: > > > > > I was reading the manpages of athn/iwn for purchasing a suitable > wireless card > and found repeated > > occurences of 2GHz, when in fact it should be 2.4GHz. That is the > standard > frequency

Re: fcntl F_SETFD 1->FD_CLOEXEC

2013-02-14 Thread David Hill
This was ok'd by millert@ anyone else want to ok and commit? On Sun, Jan 20, 2013 at 05:23:00PM -0500, David Hill wrote: >Use FD_CLOEXEC instead of 1. > >Change one instance in libutil to use O_CLOEXEC instead of a fcntl right >after. > >Index: bin/systrace/openbsd-syscalls.c >===

Re: man pages: wireless frequency nit 2GHz vs 2.4GHz

2013-02-14 Thread STeve Andre'
On 02/14/13 07:33, Stuart Henderson wrote: Amit Kulkarni gmail.com> writes: I was reading the manpages of athn/iwn for purchasing a suitable wireless card and found repeated occurences of 2GHz, when in fact it should be 2.4GHz. That is the standard frequency when purchasing a wireless a/b/

Re: man pages: wireless frequency nit 2GHz vs 2.4GHz

2013-02-14 Thread Stuart Henderson
Amit Kulkarni gmail.com> writes: > > I was reading the manpages of athn/iwn for purchasing a suitable wireless card and found repeated > occurences of 2GHz, when in fact it should be 2.4GHz. That is the standard frequency when purchasing a > wireless a/b/g/n card. The code is filled with 2GHz re