Re: manpage text width

Hi Paul, Paul Irofti wrote on Fri, Mar 30, 2018 at 11:23:54AM +0300: > Ingo Schwarze wrote: >> * Nowadays, i guess that terminals narrower than 80 columns >>have become seriously rare, so there is not very widespread >>benefit for that case. > Maybe that was true when we still had 4:3

Re: expr: Fix integer overflows

Hi Tobias, Tobias Stoeckmann wrote on Fri, Mar 30, 2018 at 05:39:11PM +0200: > Our expr implementation supports 64 bit integers, but does not check > for overflows during parsing and arithmetical operations. Even though - as discussed previously for test(1) - behaviour is undefined by POSIX

Re: manpage text width

Fri, 30 Mar 2018 08:23:12 -0700 Chris Bennett > On Thu, Mar 29, 2018 at 11:57:43PM +, Ingo Schwarze wrote: > > I *could* maybe teach man(1) to honour $COLUMN by default when > > starting up in interactive mode, but i did not do so for the following > >

[PATCH] src/etc/root/root.mail - URLs -> URL

Hi all, A small typo - plural -> singular. Regards, Raf Index: etc/root/root.mail === RCS file: /cvs/src/etc/root/root.mail,v retrieving revision 1.127 diff -u -p -r1.127 root.mail --- etc/root/root.mail 23 Mar 2018 15:45:56

[PATCH] xenocara/distrib/notes - remove problem_blurb

Hi all, problem_blurb hasn't been used in nearly 10 years[0]. Time to let it go? Remove two trailing empty lines while there. [0] http://cvsweb.openbsd.org/cgi-bin/cvsweb/xenocara/distrib/notes/m4.common.diff?r1=1.3=1.4=h Regards, Raf Index: distrib/notes/README.alpha

shutdown(8): include timezone in deadline estimates

Hey, Shutting down a box at the wrong time of day could be bad. Admins are not infallible and they do they necessarily reside in the same timezone as a given box. Users, too, don't necessarily reside in the same timezone as a given box, so broadcasting that the box is going down at "23:00"

Should rm(1) -Pf change file permission?

Hello, While working on a port of keyringer, I observed the following behavior of rm(1) with the -P option: if the file does not have write permission, the file is removed without being overwritten. This is not the same behavior as shred(1) (from sysutils/coreutils) which do not remove the file

dd(1): overhaul operand parsing

Hey, This overhauls dd(1) operand parsing for expressions. - Eliminate duplicate code by using a single routine, get_expr(). If we check for negative inputs we can use strtoull(3) safely, which covers the accepted input range for both off_t and size_t. - We can then use a single switch

expr: Fix integer overflows

Our expr implementation supports 64 bit integers, but does not check for overflows during parsing and arithmetical operations. This patch fixes the problems based on FreeBSD's implementation, which is a bit more advanced than NetBSD, which it is based upon. The added regression test case is

Re: manpage text width

On Thu, Mar 29, 2018 at 11:57:43PM +, Ingo Schwarze wrote: > I *could* maybe teach man(1) to honour $COLUMN by default when > starting up in interactive mode, but i did not do so for the following > reasons: > > * Many people are using terminals wider than 80 columns, but >texts get hard

Re: manpage text width

On Fri, Mar 30, 2018 at 01:57:43AM +0200, Ingo Schwarze wrote: > When you want a manpage to exactly fill the available terminal width, > you can use an alias like this: > > $ alias wman='man -Owidth=$COLUMNS'# or > $ alias wman='man -Owidth=$((COLUMNS-2))' > > Of course, if you

Re: manpage text width

Hi Ingo, Thanks for the detailed reply. I was expecting it :) > * Nowadays, i guess that terminals narrower than 80 columns >have become seriously rare, so there is not very widespread >benefit for that case. Maybe that was true when we still had 4:3 screens, but now I always have 2 or

Re: manpage text width

On Fri, Mar 30, 2018 at 01:57:43AM +0200, Ingo Schwarze wrote: > Hi Paul, > > Theo de Raadt wrote on Thu, Mar 29, 2018 at 04:17:14PM -0600: > > piroft@ wrote: > > >> Is there any reason why manpage text does not resize nicely > >> with <80 columns xterms? > > I want to avoid excessive magic. >

Re: return packets may not be desired to be scrubbed

On Thu, Mar 29, 2018 at 10:01:02PM +0200, Peter J. Philipp wrote: ... > The end result is here. I add 2 arguments to pf_scrub() for rule/state > direction that is desired and direction that the packet is taking. Then > in random-id the logic does not scrub when we had an "outbound scrub" and >