Re: mdoc(7) .Sq Fl for a dash
On Tue, Jul 16, 2013 at 12:38:42AM +0200, Jan Stary wrote: > > Index: oldrdist.1 > === > RCS file: /cvs/src/usr.bin/oldrdist/oldrdist.1,v > retrieving revision 1.20 > diff -u -p -u -p -r1.20 oldrdist.1 > --- oldrdist.13 Sep 2011 22:59:07 - 1.20 > +++ oldrdist.115 Jul 2013 22:29:30 - > @@ -69,10 +69,8 @@ is > the standard input is used. > .El > .Pp > -If either the > +If the > .Fl f > -or > -.Sq Fl > option is not specified, the program looks first for > .Dq Pa distfile , > then > Index: cat.1 > === > RCS file: /cvs/src/bin/cat/cat.1,v > retrieving revision 1.32 > diff -u -p -u -p -r1.32 cat.1 > --- cat.1 18 Jan 2013 21:48:43 - 1.32 > +++ cat.1 15 Jul 2013 22:34:45 - > @@ -53,7 +53,7 @@ operands are processed in command-line o > If > .Ar file > is a single dash > -.Pq Sq \&- > +.Pq Sq - > or absent, > .Nm > reads from the standard input. > ok, these and the rest (getty/crontab/diff) fixed. for oldrdist, i also used Sq instead of Dq for "-". jmc
Re: mdoc(7) .Sq Fl for a dash
On Tue, Jul 16, 2013 at 12:36:32AM +0200, J??r??mie Courr??ges-Anglas wrote: > >> > >> Fl may seem wrong because we're talking about an argument, but I don't > >> think a bare `-' (a hyphen) would be better. We're talking about an > >> ascii minus sign here; mandoc_char(7) says a minus sign can be obtained > >> with \- . > >> > > > > it's not a minus sign. it's a literal "-". > > I was thinking encoding-wise: you're typing an ascii minus sign, at the > cli. If you have a man/mdoc formatter that distinguishes hyphens and > minus signs, it could produce different output for those, and you would > not be able to copy-paste examples. Maybe mandoc doesn't, but groff > can (some distros even disabled this behavior). > i'm not sure i follow. the differing widths of "-" will only happen if you add mark up. i'm arguing to remove it. a literal "-", with no mark up, can be copied/pasted no matter what the output format. well, i say this without actually having tried it. but if you can;t, something is not right. if you add markup (you suggested "\-"), then the width will vary for output formats such as postscript. that might stop you being able to paste (though again i've never tried). jmc
Re: Management of pf.conf
On 07/11/2013 07:18 AM, Jummo wrote: > Hi, > > How do you manage your pf.conf? > > My setup: I have 9 firewalls with carp and each with around 500 lines of > pf.conf, except one firewall, later more. I edit the pf.conf manually. > Every logical pf rule has a unique identifier (a number) which I add > manually and maps to the rule on a wiki page. The wiki page has this > format. > > START WIKI PAGE > > === Firewall > > This firewall is for ... > > == ID > > A ID identify one or more rules for a particular service. Please use the > next free ID. > > Last used ID: 21 > > == Changelog > > No | Date | Action | Executed by > > == Tables > > Table | Content > > == NAT/Redirection > > ID | Description | Source | Port | Destination | Port | NAT-To | > Redirect-To | > Protocol | Date > > == Rules > > ID | Description | Direction (outgoing/incoming/forwarded) | Source | > Port | Destination | Port | Protocol | Date > > END WIKI PAGE > > I use a script to manually copy the changed pf.conf to the corresponding > carp partner to keep the firewall pair in sync. Idea: To check the sync > state of pf.conf, Icinga cloud compare the file date of the two pf.conf. > > This works quiet good for me and my firewalls with one exception, my big > fat central router/firewall. This firewall has around 2000 lines of > pf.conf, is attached with 12 VLAN interfaces and get slowly unmanageable > with this concept. > > How to you manage such big firewalls? Do you split the pf.conf into > logical parts? Do you use a base structure for every pf.conf? Do you use > a tool for automatic creation of pf.conf? How do you tests your old > rules after you changed something? > > I'm happy about any feedback. > > Best Regards, > Patrick > > vim(1), git(1) and sh(1). I edit with Vim, then commit. Pre-commit hooks in git check the syntax with pfctl(1). Post-commit hooks push the commits to our central repo and trigger all hosts in the cluster to pull and apply the changes. A few status checks happen along the way to ensure things stay consistent-- mostly. The hooks are modular so the various stages may be run alone, if needed. Something similar could probably be done with rdist(1) or rsync(1). - *question everything*learn something*answer nothing* Lucas Yamanishi -- Systems Administrator, ADNET Systems, Inc. NASA Space and Earth Science Data Analysis (606.9) 7515 Mission Drive, Suite A100 Lanham, MD 20706 * 301-352-4646 * 0xE23F3D7A
Re: OpenBSD ipsec performance on modern HW
Evgeniy Sudyr [eject.in...@gmail.com] wrote: > > BOX1 dmesg: > cpu0: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.45 MHz > cpu1: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.09 MHz > cpu2: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.09 MHz > cpu3: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.09 MHz > cpu4: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.09 MHz > cpu5: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.09 MHz > cpu6: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.09 MHz > cpu7: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.09 MHz > cpu8: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.09 MHz > cpu9: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.08 MHz > cpu10: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.08 MHz > cpu11: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.08 MHz > cpu12: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.09 MHz > cpu13: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.09 MHz > cpu14: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.08 MHz > cpu15: Intel(R) Xeon(R) CPU E5620 @ 2.40GHz, 2400.08 MHz > > > BOX2 dmesg: > cpu0: Intel(R) Xeon(R) CPU E31240 @ 3.30GHz, 3292.98 MHz > cpu1: Intel(R) Xeon(R) CPU E31240 @ 3.30GHz, 3292.53 MHz > cpu2: Intel(R) Xeon(R) CPU E31240 @ 3.30GHz, 3292.53 MHz > cpu3: Intel(R) Xeon(R) CPU E31240 @ 3.30GHz, 3292.53 MHz > cpu4: Intel(R) Xeon(R) CPU E31240 @ 3.30GHz, 3292.53 MHz > cpu5: Intel(R) Xeon(R) CPU E31240 @ 3.30GHz, 3292.53 MHz > cpu6: Intel(R) Xeon(R) CPU E31240 @ 3.30GHz, 3292.53 MHz > cpu7: Intel(R) Xeon(R) CPU E31240 @ 3.30GHz, 3292.53 MHz I think to get better performance, you need to add more CPUs and more RAM. 16 CPUs and 32GB of RAM is hardly enough to get more than 270Mbps encryption throuhput. Ok, maybe I'm exaggerating. You won't see difference between a dual core CPU of similar spec with 1GB of RAM and what you have now. Really, OpenBSD needs to use more than one of your 16 cores at a time for encryption if you want higher speed. Some people talked about giving the encryption system its own core to work on so it doesn't compete with the rest of the kernel. That would help you get somewhat higher throughput. But the real solution for getting significant speed boosts on kernel-based IPsec with your type of hardware is much farther off. You can only hope for small improvements until that magical work is completed by the master magicians.
Re: mdoc(7) .Sq Fl for a dash
Jason McIntyre writes: > On Mon, Jul 15, 2013 at 11:34:53PM +0200, Jérémie Courrèges-Anglas wrote: >> Jason McIntyre writes: >> >> > On Mon, Jul 15, 2013 at 07:53:04PM +0200, Jan Stary wrote: >> >> Some of the manpages, e.g. crontab(1), >> >> markup the folklore phrase >> >> >> >> named file, or standard input >> >> if the pseudo-filename `-' is given >> >> >> >> as >> >> >> >> named file, or standard input >> >> if the pseudo-filename >> >> .Sq Fl >> >> is given. >> >> >> >> Is this correct semantic markup? IMHO not: >> >> it just abuses the fact that the flags (Fl) >> >> happen to start with a dash; but that's not >> >> what is meant here; this is not a flag; >> >> it is the literal dash that is recognized >> >> in place of a filename. >> >> Then it is an argument (Ar). >> > not really. Ar represents an argument name - this is a literal > argument. That makes sense. > it should therefore be Li, but because the markup on a single > character is hard to spot, we use Sq. there is a Ql macro which "does > the right thing", but the effect would be the same as using Sq. Sq is > probably best, i think. > >> >> So I believe it should be simply >> >> >> >> .Sq - >> >> >> >> Right? >> >> See below. >> >> >> The diff below replaces those occurences >> >> that a grep revealed for me in /usr/share/man; >> >> Another grep reveals that most other manpages >> >> actually use ".Sq -". >> >> >> >> I left out oldrdist(1) and shutdown(8) >> >> where it _is_ actually a flag >> >> and the code processes it as such. >> >> >> >> Jan >> >> >> > >> > ok, i agree with this. Fl seems wrong. however there's some ambiguity, >> > for me anyway - do oldrdist and shutdown actually process "-" >> > differently, or do the manuals talk about them differently? >> >> Fl may seem wrong because we're talking about an argument, but I don't >> think a bare `-' (a hyphen) would be better. We're talking about an >> ascii minus sign here; mandoc_char(7) says a minus sign can be obtained >> with \- . >> > > it's not a minus sign. it's a literal "-". I was thinking encoding-wise: you're typing an ascii minus sign, at the cli. If you have a man/mdoc formatter that distinguishes hyphens and minus signs, it could produce different output for those, and you would not be able to copy-paste examples. Maybe mandoc doesn't, but groff can (some distros even disabled this behavior). >> I wonder about cat(1) using >> .Pq Sq \&- >> is that really telling mandoc to treat it as a minus sign? >> >> What about: >> .Pq Sq Ar \- >> > > the \& is wrong, yes. but so is Ar > [...] -- Jérémie Courrèges-Anglas PGP Key fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
Re: mdoc(7) .Sq Fl for a dash
On Jul 15 23:24:40, j...@kerhand.co.uk wrote: > i think the previous suggestion (If the -f option is not specified) is > clearer. > > > Why cannot this be just > > .Pq Sq - > > > it should be. so roll this into your diff. Index: oldrdist.1 === RCS file: /cvs/src/usr.bin/oldrdist/oldrdist.1,v retrieving revision 1.20 diff -u -p -u -p -r1.20 oldrdist.1 --- oldrdist.1 3 Sep 2011 22:59:07 - 1.20 +++ oldrdist.1 15 Jul 2013 22:29:30 - @@ -69,10 +69,8 @@ is the standard input is used. .El .Pp -If either the +If the .Fl f -or -.Sq Fl option is not specified, the program looks first for .Dq Pa distfile , then Index: cat.1 === RCS file: /cvs/src/bin/cat/cat.1,v retrieving revision 1.32 diff -u -p -u -p -r1.32 cat.1 --- cat.1 18 Jan 2013 21:48:43 - 1.32 +++ cat.1 15 Jul 2013 22:34:45 - @@ -53,7 +53,7 @@ operands are processed in command-line o If .Ar file is a single dash -.Pq Sq \&- +.Pq Sq - or absent, .Nm reads from the standard input.
Re: author emails in manpages
ok, but watch out for the spurious scan_ffs change. jmc On Tue, Jul 16, 2013 at 12:15:50AM +0200, Jan Stary wrote: > On Jul 15 23:23:57, h...@stare.cz wrote: > > Here is a diff for /usr/src/usr.bin: > > Here is another for usr/src/sbin; > while in there, remove a forgotten > man(7) line from scan_ffs(8) > > > Index: bioctl/bioctl.8 > === > RCS file: /cvs/src/sbin/bioctl/bioctl.8,v > retrieving revision 1.90 > diff -u -p -u -p -r1.90 bioctl.8 > --- bioctl/bioctl.8 22 Sep 2012 20:09:43 - 1.90 > +++ bioctl/bioctl.8 15 Jul 2013 22:11:24 - > @@ -318,7 +318,7 @@ command first appeared in > The > .Nm > interface was written by > -.An Marco Peereboom Aq ma...@openbsd.org . > +.An Marco Peereboom Aq Mt ma...@openbsd.org . > .Sh CAVEATS > Only devices with 512-byte sectors are supported. > .Pp > Index: dhclient/dhclient.8 > === > RCS file: /cvs/src/sbin/dhclient/dhclient.8,v > retrieving revision 1.22 > diff -u -p -u -p -r1.22 dhclient.8 > --- dhclient/dhclient.8 14 Jul 2013 19:44:38 - 1.22 > +++ dhclient/dhclient.8 15 Jul 2013 22:11:26 - > @@ -350,9 +350,9 @@ database of acquired leases > .An -nosplit > .Nm > was written by > -.An Ted Lemon Aq mel...@fugue.com > +.An Ted Lemon Aq Mt mel...@fugue.com > and > -.An Elliot Poger Aq ell...@poger.com . > +.An Elliot Poger Aq Mt ell...@poger.com . > .Pp > The current implementation was reworked by > -.An Henning Brauer Aq henn...@openbsd.org . > +.An Henning Brauer Aq Mt henn...@openbsd.org . > Index: dhclient/dhclient.conf.5 > === > RCS file: /cvs/src/sbin/dhclient/dhclient.conf.5,v > retrieving revision 1.29 > diff -u -p -u -p -r1.29 dhclient.conf.5 > --- dhclient/dhclient.conf.5 2 Mar 2013 07:11:19 - 1.29 > +++ dhclient/dhclient.conf.5 15 Jul 2013 22:11:27 - > @@ -459,8 +459,8 @@ file \- the defaults are usually fine. > .An -nosplit > .Xr dhclient 8 > was written by > -.An Ted Lemon Aq mel...@vix.com > +.An Ted Lemon Aq Mt mel...@vix.com > under a contract with Vixie Labs. > .Pp > The current implementation was reworked by > -.An Henning Brauer Aq henn...@openbsd.org . > +.An Henning Brauer Aq Mt henn...@openbsd.org . > Index: dhclient/dhclient.leases.5 > === > RCS file: /cvs/src/sbin/dhclient/dhclient.leases.5,v > retrieving revision 1.8 > diff -u -p -u -p -r1.8 dhclient.leases.5 > --- dhclient/dhclient.leases.524 Feb 2013 12:18:43 - 1.8 > +++ dhclient/dhclient.leases.515 Jul 2013 22:11:27 - > @@ -96,8 +96,8 @@ Current lease file. > .An -nosplit > .Xr dhclient 8 > was written by > -.An Ted Lemon Aq mel...@vix.com > +.An Ted Lemon Aq Mt mel...@vix.com > under a contract with Vixie Labs. > .Pp > The current implementation was reworked by > -.An Henning Brauer Aq henn...@openbsd.org . > +.An Henning Brauer Aq Mt henn...@openbsd.org . > Index: growfs/growfs.8 > === > RCS file: /cvs/src/sbin/growfs/growfs.8,v > retrieving revision 1.10 > diff -u -p -u -p -r1.10 growfs.8 > --- growfs/growfs.8 28 Nov 2008 00:15:54 - 1.10 > +++ growfs/growfs.8 15 Jul 2013 22:11:29 - > @@ -123,9 +123,9 @@ The > utility first appeared in > .Fx 4.4 . > .Sh AUTHORS > -.An Christoph Herrmann Aq c...@freebsd.org > -.An Thomas-Henning von Kamptz Aq toms...@freebsd.org > -.An The GROWFS team Aq gro...@tomsoft.com > +.An Christoph Herrmann Aq Mt c...@freebsd.org > +.An Thomas-Henning von Kamptz Aq Mt toms...@freebsd.org > +.An The GROWFS team Aq Mt gro...@tomsoft.com > .Sh BUGS > Filesystems must be checked with > .Xr fsck 8 > Index: iked/iked.8 > === > RCS file: /cvs/src/sbin/iked/iked.8,v > retrieving revision 1.14 > diff -u -p -u -p -r1.14 iked.8 > --- iked/iked.8 29 Jun 2013 09:08:41 - 1.14 > +++ iked/iked.8 15 Jul 2013 22:11:29 - > @@ -152,7 +152,7 @@ program first appeared in > The > .Nm > program was written by > -.An Reyk Floeter Aq r...@openbsd.org . > +.An Reyk Floeter Aq Mt r...@openbsd.org . > .Sh CAVEATS > .Nm > is not yet finished and is missing some important security features. > Index: iked/iked.conf.5 > === > RCS file: /cvs/src/sbin/iked/iked.conf.5,v > retrieving revision 1.24 > diff -u -p -u -p -r1.24 iked.conf.5 > --- iked/iked.conf.5 22 May 2013 10:32:09 - 1.24 > +++ iked/iked.conf.5 15 Jul 2013 22:11:30 - > @@ -851,4 +851,4 @@ file format first appeared in > The > .Xr iked 8 > program was written by > -.An Reyk Floeter Aq r...@openbsd.org . > +.An Reyk Floeter Aq Mt r...@openbsd.org . > Index: iopctl/iopctl.8 > ==
Re: mdoc(7) .Sq Fl for a dash
On Mon, Jul 15, 2013 at 11:53:38PM +0200, Jan Stary wrote: > > > > for oldrdist, "-" is actually the argument to -f. so it's not an option, > > as far as i can see. just the manual seems to blur things by documenting > > "If either the -f or `-' option is not specified", whereas above, the > > text suggests "-f-" or "-f -" is how it would work. > > You are right: the `-' is actually an argument to -f, > and the manpage wording just confuses things by talking > about "the `-' option". BTW, it uses ".Dq" everywhere else. > > Index: oldrdist.1 > === > RCS file: /cvs/src/usr.bin/oldrdist/oldrdist.1,v > retrieving revision 1.20 > diff -u -p -u -p -r1.20 oldrdist.1 > --- oldrdist.13 Sep 2011 22:59:07 - 1.20 > +++ oldrdist.115 Jul 2013 21:38:51 - > @@ -69,11 +69,9 @@ is > the standard input is used. > .El > .Pp > -If either the > -.Fl f > -or > -.Sq Fl > -option is not specified, the program looks first for > +If the > +.Ar distfile > +is not specified, the program looks first for > .Dq Pa distfile , > then > .Dq Pa Distfile > i think the previous suggestion (If the -f option is not specified) is clearer. > > > > similarly, look at cat(1): > > > > If file is a single dash (`-') or absent, cat reads from the > > standard input. > > > > no mention of "-" in SYNOPSIS. > > Yes; here it does not suggest that `-' is an option, > just that it is recognized as a special value for `file' > (which is described in SYNOPSIS). > > Incidentaly, it uses > > .Pq Sq \&- > > Why cannot this be just > > .Pq Sq - > > ? > it should be. so roll this into your diff. > > but shutdown(8), which lists "-" in > > SYNOPSIS: > > > > If `-' is supplied as an option, the warning message is read > > from standard input. > > > > so, it looks like oldrdist and shutdown are just talking about "-" > > differently to other manuals, but not behaving differently to other > > apps. i.e. we should tweak oldrdist and shutdown too. > > shutdown code actually recognizes `-' as a getopt case: > it is technically an option, meaning "do not expect the message > on the commandline, read it from stdin instead". > ok, so we can leave shutdown alone. jmc
Re: mdoc(7) .Sq Fl for a dash
On Mon, Jul 15, 2013 at 11:34:53PM +0200, J??r??mie Courr??ges-Anglas wrote: > Jason McIntyre writes: > > > On Mon, Jul 15, 2013 at 07:53:04PM +0200, Jan Stary wrote: > >> Some of the manpages, e.g. crontab(1), > >> markup the folklore phrase > >> > >>named file, or standard input > >>if the pseudo-filename `-' is given > >> > >> as > >> > >>named file, or standard input > >>if the pseudo-filename > >>.Sq Fl > >>is given. > >> > >> Is this correct semantic markup? IMHO not: > >> it just abuses the fact that the flags (Fl) > >> happen to start with a dash; but that's not > >> what is meant here; this is not a flag; > >> it is the literal dash that is recognized > >> in place of a filename. > > Then it is an argument (Ar). > not really. Ar represents an argument name - this is a literal argument. it should therefore be Li, but because the markup on a single character is hard to spot, we use Sq. there is a Ql macro which "does the right thing", but the effect would be the same as using Sq. Sq is probably best, i think. > >> So I believe it should be simply > >> > >>.Sq - > >> > >> Right? > > See below. > > >> The diff below replaces those occurences > >> that a grep revealed for me in /usr/share/man; > >> Another grep reveals that most other manpages > >> actually use ".Sq -". > >> > >> I left out oldrdist(1) and shutdown(8) > >> where it _is_ actually a flag > >> and the code processes it as such. > >> > >>Jan > >> > > > > ok, i agree with this. Fl seems wrong. however there's some ambiguity, > > for me anyway - do oldrdist and shutdown actually process "-" > > differently, or do the manuals talk about them differently? > > Fl may seem wrong because we're talking about an argument, but I don't > think a bare `-' (a hyphen) would be better. We're talking about an > ascii minus sign here; mandoc_char(7) says a minus sign can be obtained > with \- . > it's not a minus sign. it's a literal "-". > I wonder about cat(1) using > .Pq Sq \&- > is that really telling mandoc to treat it as a minus sign? > > What about: > .Pq Sq Ar \- > the \& is wrong, yes. but so is Ar > > for oldrdist, "-" is actually the argument to -f. so it's not an option, > > as far as i can see. just the manual seems to blur things by documenting > > "If either the -f or `-' option is not specified", whereas above, the > > text suggests "-f-" or "-f -" is how it would work. > > Yup, sounds weird. The text above is right, the next sentence should be > changed. Why not: > > If the > .Fl f > option is not specified, the program looks first for... > that seems right. > I've just discovered oldrdist, btw. I hope tedu isn't reading this > mail. :) > > > similarly, look at cat(1): > > > > If file is a single dash (`-') or absent, cat reads from the > > standard input. > > > > no mention of "-" in SYNOPSIS. but shutdown(8), which lists "-" in > > SYNOPSIS: > > > > If `-' is supplied as an option, the warning message is read > > from standard input. > > shutdown.c uses '-' in its getopt string, so that it can be passed > before (and probably between) other options (see SYNOPSIS). This does > not match the way most utilities from the base system handle options and > arguments, so I think the current wording is ok (see getopt(3), > STANDARDS). > > > so, it looks like oldrdist and shutdown are just talking about "-" > > differently to other manuals, but not behaving differently to other > > apps. i.e. we should tweak oldrdist and shutdown too. > > > > can anyone confirm if there is a technical difference (and, if there is, > > does it translate into practical difference for users)? > > Both use it as "read input from stdin", but I think only oldrdist needs > a tweak. > i think you're right. jmc
Re: author emails in manpages
On Jul 15 23:23:57, h...@stare.cz wrote: > Here is a diff for /usr/src/usr.bin: Here is another for usr/src/sbin; while in there, remove a forgotten man(7) line from scan_ffs(8) Index: bioctl/bioctl.8 === RCS file: /cvs/src/sbin/bioctl/bioctl.8,v retrieving revision 1.90 diff -u -p -u -p -r1.90 bioctl.8 --- bioctl/bioctl.8 22 Sep 2012 20:09:43 - 1.90 +++ bioctl/bioctl.8 15 Jul 2013 22:11:24 - @@ -318,7 +318,7 @@ command first appeared in The .Nm interface was written by -.An Marco Peereboom Aq ma...@openbsd.org . +.An Marco Peereboom Aq Mt ma...@openbsd.org . .Sh CAVEATS Only devices with 512-byte sectors are supported. .Pp Index: dhclient/dhclient.8 === RCS file: /cvs/src/sbin/dhclient/dhclient.8,v retrieving revision 1.22 diff -u -p -u -p -r1.22 dhclient.8 --- dhclient/dhclient.8 14 Jul 2013 19:44:38 - 1.22 +++ dhclient/dhclient.8 15 Jul 2013 22:11:26 - @@ -350,9 +350,9 @@ database of acquired leases .An -nosplit .Nm was written by -.An Ted Lemon Aq mel...@fugue.com +.An Ted Lemon Aq Mt mel...@fugue.com and -.An Elliot Poger Aq ell...@poger.com . +.An Elliot Poger Aq Mt ell...@poger.com . .Pp The current implementation was reworked by -.An Henning Brauer Aq henn...@openbsd.org . +.An Henning Brauer Aq Mt henn...@openbsd.org . Index: dhclient/dhclient.conf.5 === RCS file: /cvs/src/sbin/dhclient/dhclient.conf.5,v retrieving revision 1.29 diff -u -p -u -p -r1.29 dhclient.conf.5 --- dhclient/dhclient.conf.52 Mar 2013 07:11:19 - 1.29 +++ dhclient/dhclient.conf.515 Jul 2013 22:11:27 - @@ -459,8 +459,8 @@ file \- the defaults are usually fine. .An -nosplit .Xr dhclient 8 was written by -.An Ted Lemon Aq mel...@vix.com +.An Ted Lemon Aq Mt mel...@vix.com under a contract with Vixie Labs. .Pp The current implementation was reworked by -.An Henning Brauer Aq henn...@openbsd.org . +.An Henning Brauer Aq Mt henn...@openbsd.org . Index: dhclient/dhclient.leases.5 === RCS file: /cvs/src/sbin/dhclient/dhclient.leases.5,v retrieving revision 1.8 diff -u -p -u -p -r1.8 dhclient.leases.5 --- dhclient/dhclient.leases.5 24 Feb 2013 12:18:43 - 1.8 +++ dhclient/dhclient.leases.5 15 Jul 2013 22:11:27 - @@ -96,8 +96,8 @@ Current lease file. .An -nosplit .Xr dhclient 8 was written by -.An Ted Lemon Aq mel...@vix.com +.An Ted Lemon Aq Mt mel...@vix.com under a contract with Vixie Labs. .Pp The current implementation was reworked by -.An Henning Brauer Aq henn...@openbsd.org . +.An Henning Brauer Aq Mt henn...@openbsd.org . Index: growfs/growfs.8 === RCS file: /cvs/src/sbin/growfs/growfs.8,v retrieving revision 1.10 diff -u -p -u -p -r1.10 growfs.8 --- growfs/growfs.8 28 Nov 2008 00:15:54 - 1.10 +++ growfs/growfs.8 15 Jul 2013 22:11:29 - @@ -123,9 +123,9 @@ The utility first appeared in .Fx 4.4 . .Sh AUTHORS -.An Christoph Herrmann Aq c...@freebsd.org -.An Thomas-Henning von Kamptz Aq toms...@freebsd.org -.An The GROWFS team Aq gro...@tomsoft.com +.An Christoph Herrmann Aq Mt c...@freebsd.org +.An Thomas-Henning von Kamptz Aq Mt toms...@freebsd.org +.An The GROWFS team Aq Mt gro...@tomsoft.com .Sh BUGS Filesystems must be checked with .Xr fsck 8 Index: iked/iked.8 === RCS file: /cvs/src/sbin/iked/iked.8,v retrieving revision 1.14 diff -u -p -u -p -r1.14 iked.8 --- iked/iked.8 29 Jun 2013 09:08:41 - 1.14 +++ iked/iked.8 15 Jul 2013 22:11:29 - @@ -152,7 +152,7 @@ program first appeared in The .Nm program was written by -.An Reyk Floeter Aq r...@openbsd.org . +.An Reyk Floeter Aq Mt r...@openbsd.org . .Sh CAVEATS .Nm is not yet finished and is missing some important security features. Index: iked/iked.conf.5 === RCS file: /cvs/src/sbin/iked/iked.conf.5,v retrieving revision 1.24 diff -u -p -u -p -r1.24 iked.conf.5 --- iked/iked.conf.522 May 2013 10:32:09 - 1.24 +++ iked/iked.conf.515 Jul 2013 22:11:30 - @@ -851,4 +851,4 @@ file format first appeared in The .Xr iked 8 program was written by -.An Reyk Floeter Aq r...@openbsd.org . +.An Reyk Floeter Aq Mt r...@openbsd.org . Index: iopctl/iopctl.8 === RCS file: /cvs/src/sbin/iopctl/iopctl.8,v retrieving revision 1.11 diff -u -p -u -p -r1.11 iopctl.8 --- iopctl/iopctl.8 26 Jun 2008 05:42:06 - 1.11 +++ iopctl/iopctl.8 15 Jul 2013 22:11:31 - @@ -97,8 +97,8 @@ support was added in The .Nm command was written by -.An Andrew Doran Aq a...@netbsd.org , +.An Andrew Doran Aq Mt a...@netbsd.org , and porte
Re: mdoc(7) .Sq Fl for a dash
On Jul 15 21:46:21, j...@kerhand.co.uk wrote: > On Mon, Jul 15, 2013 at 07:53:04PM +0200, Jan Stary wrote: > > Some of the manpages, e.g. crontab(1), > > markup the folklore phrase > > > > named file, or standard input > > if the pseudo-filename `-' is given > > > > as > > > > named file, or standard input > > if the pseudo-filename > > .Sq Fl > > is given. > > > > Is this correct semantic markup? IMHO not: > > it just abuses the fact that the flags (Fl) > > happen to start with a dash; but that's not > > what is meant here; this is not a flag; > > it is the literal dash that is recognized > > in place of a filename. > > > > So I believe it should be simply > > > > .Sq - > > > > Right? > > > > The diff below replaces those occurences > > that a grep revealed for me in /usr/share/man; > > Another grep reveals that most other manpages > > actually use ".Sq -". > > > > I left out oldrdist(1) and shutdown(8) > > where it _is_ actually a flag > > and the code processes it as such. > > > > Jan > > > > ok, i agree with this. Fl seems wrong. however there's some ambiguity, > for me anyway - do oldrdist and shutdown actually process "-" > differently, or do the manuals talk about them differently? > > for oldrdist, "-" is actually the argument to -f. so it's not an option, > as far as i can see. just the manual seems to blur things by documenting > "If either the -f or `-' option is not specified", whereas above, the > text suggests "-f-" or "-f -" is how it would work. You are right: the `-' is actually an argument to -f, and the manpage wording just confuses things by talking about "the `-' option". BTW, it uses ".Dq" everywhere else. Index: oldrdist.1 === RCS file: /cvs/src/usr.bin/oldrdist/oldrdist.1,v retrieving revision 1.20 diff -u -p -u -p -r1.20 oldrdist.1 --- oldrdist.1 3 Sep 2011 22:59:07 - 1.20 +++ oldrdist.1 15 Jul 2013 21:38:51 - @@ -69,11 +69,9 @@ is the standard input is used. .El .Pp -If either the -.Fl f -or -.Sq Fl -option is not specified, the program looks first for +If the +.Ar distfile +is not specified, the program looks first for .Dq Pa distfile , then .Dq Pa Distfile > similarly, look at cat(1): > > If file is a single dash (`-') or absent, cat reads from the > standard input. > > no mention of "-" in SYNOPSIS. Yes; here it does not suggest that `-' is an option, just that it is recognized as a special value for `file' (which is described in SYNOPSIS). Incidentaly, it uses .Pq Sq \&- Why cannot this be just .Pq Sq - ? > but shutdown(8), which lists "-" in > SYNOPSIS: > > If `-' is supplied as an option, the warning message is read > from standard input. > > so, it looks like oldrdist and shutdown are just talking about "-" > differently to other manuals, but not behaving differently to other > apps. i.e. we should tweak oldrdist and shutdown too. shutdown code actually recognizes `-' as a getopt case: it is technically an option, meaning "do not expect the message on the commandline, read it from stdin instead".
Re: mdoc(7) .Sq Fl for a dash
Jason McIntyre writes: > On Mon, Jul 15, 2013 at 07:53:04PM +0200, Jan Stary wrote: >> Some of the manpages, e.g. crontab(1), >> markup the folklore phrase >> >> named file, or standard input >> if the pseudo-filename `-' is given >> >> as >> >> named file, or standard input >> if the pseudo-filename >> .Sq Fl >> is given. >> >> Is this correct semantic markup? IMHO not: >> it just abuses the fact that the flags (Fl) >> happen to start with a dash; but that's not >> what is meant here; this is not a flag; >> it is the literal dash that is recognized >> in place of a filename. Then it is an argument (Ar). >> So I believe it should be simply >> >> .Sq - >> >> Right? See below. >> The diff below replaces those occurences >> that a grep revealed for me in /usr/share/man; >> Another grep reveals that most other manpages >> actually use ".Sq -". >> >> I left out oldrdist(1) and shutdown(8) >> where it _is_ actually a flag >> and the code processes it as such. >> >> Jan >> > > ok, i agree with this. Fl seems wrong. however there's some ambiguity, > for me anyway - do oldrdist and shutdown actually process "-" > differently, or do the manuals talk about them differently? Fl may seem wrong because we're talking about an argument, but I don't think a bare `-' (a hyphen) would be better. We're talking about an ascii minus sign here; mandoc_char(7) says a minus sign can be obtained with \- . I wonder about cat(1) using .Pq Sq \&- is that really telling mandoc to treat it as a minus sign? What about: .Pq Sq Ar \- > for oldrdist, "-" is actually the argument to -f. so it's not an option, > as far as i can see. just the manual seems to blur things by documenting > "If either the -f or `-' option is not specified", whereas above, the > text suggests "-f-" or "-f -" is how it would work. Yup, sounds weird. The text above is right, the next sentence should be changed. Why not: If the .Fl f option is not specified, the program looks first for... I've just discovered oldrdist, btw. I hope tedu isn't reading this mail. :) > similarly, look at cat(1): > > If file is a single dash (`-') or absent, cat reads from the > standard input. > > no mention of "-" in SYNOPSIS. but shutdown(8), which lists "-" in > SYNOPSIS: > > If `-' is supplied as an option, the warning message is read > from standard input. shutdown.c uses '-' in its getopt string, so that it can be passed before (and probably between) other options (see SYNOPSIS). This does not match the way most utilities from the base system handle options and arguments, so I think the current wording is ok (see getopt(3), STANDARDS). > so, it looks like oldrdist and shutdown are just talking about "-" > differently to other manuals, but not behaving differently to other > apps. i.e. we should tweak oldrdist and shutdown too. > > can anyone confirm if there is a technical difference (and, if there is, > does it translate into practical difference for users)? Both use it as "read input from stdin", but I think only oldrdist needs a tweak. > jmc > >> >> Index: src/libexec/getty/getty.8 >> === >> RCS file: /cvs/src/libexec/getty/getty.8,v >> retrieving revision 1.13 >> diff -u -p -u -p -r1.13 getty.8 >> --- src/libexec/getty/getty.831 May 2007 19:19:39 - 1.13 >> +++ src/libexec/getty/getty.815 Jul 2013 17:42:42 - >> @@ -55,7 +55,7 @@ is the special device file in >> .Pa /dev >> to open for the terminal (for example, ``ttyh0''). >> If there is no argument or the argument is >> -.Sq Fl , >> +.Sq - , >> the tty line is assumed to be open as file descriptor 0. >> .Pp >> The >> Index: src/usr.bin/diff/diff.1 >> === >> RCS file: /cvs/src/usr.bin/diff/diff.1,v >> retrieving revision 1.41 >> diff -u -p -u -p -r1.41 diff.1 >> --- src/usr.bin/diff/diff.1 20 Jan 2013 11:19:12 - 1.41 >> +++ src/usr.bin/diff/diff.1 15 Jul 2013 17:42:53 - >> @@ -331,7 +331,7 @@ If either >> or >> .Ar file2 >> is >> -.Sq Fl , >> +.Sq - , >> the standard input is >> used in its place. >> .Ss Output Style >> Index: src/usr.sbin/cron/crontab.1 >> === >> RCS file: /cvs/src/usr.sbin/cron/crontab.1,v >> retrieving revision 1.28 >> diff -u -p -u -p -r1.28 crontab.1 >> --- src/usr.sbin/cron/crontab.1 31 Jan 2011 19:13:31 - 1.28 >> +++ src/usr.sbin/cron/crontab.1 15 Jul 2013 17:42:57 - >> @@ -48,7 +48,7 @@ they are not intended to be edited direc >> .Pp >> The first form of this command is used to install a new crontab from some >> named file, or standard input if the pseudo-filename >> -.Sq Fl >> +.Sq - >> is given. >> .Pp >> If the > -- Jérémie Courrèges-Anglas PGP Key fingerprint: 61DB D9A0 00A4 67CF 2A90 8961 6191 8FBF 06A1 1494
Re: mdoc(7) .Sq Fl for a dash
On Mon, Jul 15, 2013 at 07:53:04PM +0200, Jan Stary wrote: > Some of the manpages, e.g. crontab(1), > markup the folklore phrase > > named file, or standard input > if the pseudo-filename `-' is given > > as > > named file, or standard input > if the pseudo-filename > .Sq Fl > is given. > > Is this correct semantic markup? IMHO not: > it just abuses the fact that the flags (Fl) > happen to start with a dash; but that's not > what is meant here; this is not a flag; > it is the literal dash that is recognized > in place of a filename. > > So I believe it should be simply > > .Sq - > > Right? > > The diff below replaces those occurences > that a grep revealed for me in /usr/share/man; > Another grep reveals that most other manpages > actually use ".Sq -". > > I left out oldrdist(1) and shutdown(8) > where it _is_ actually a flag > and the code processes it as such. > > Jan > ok, i agree with this. Fl seems wrong. however there's some ambiguity, for me anyway - do oldrdist and shutdown actually process "-" differently, or do the manuals talk about them differently? for oldrdist, "-" is actually the argument to -f. so it's not an option, as far as i can see. just the manual seems to blur things by documenting "If either the -f or `-' option is not specified", whereas above, the text suggests "-f-" or "-f -" is how it would work. similarly, look at cat(1): If file is a single dash (`-') or absent, cat reads from the standard input. no mention of "-" in SYNOPSIS. but shutdown(8), which lists "-" in SYNOPSIS: If `-' is supplied as an option, the warning message is read from standard input. so, it looks like oldrdist and shutdown are just talking about "-" differently to other manuals, but not behaving differently to other apps. i.e. we should tweak oldrdist and shutdown too. can anyone confirm if there is a technical difference (and, if there is, does it translate into practical difference for users)? jmc > > Index: src/libexec/getty/getty.8 > === > RCS file: /cvs/src/libexec/getty/getty.8,v > retrieving revision 1.13 > diff -u -p -u -p -r1.13 getty.8 > --- src/libexec/getty/getty.8 31 May 2007 19:19:39 - 1.13 > +++ src/libexec/getty/getty.8 15 Jul 2013 17:42:42 - > @@ -55,7 +55,7 @@ is the special device file in > .Pa /dev > to open for the terminal (for example, ``ttyh0''). > If there is no argument or the argument is > -.Sq Fl , > +.Sq - , > the tty line is assumed to be open as file descriptor 0. > .Pp > The > Index: src/usr.bin/diff/diff.1 > === > RCS file: /cvs/src/usr.bin/diff/diff.1,v > retrieving revision 1.41 > diff -u -p -u -p -r1.41 diff.1 > --- src/usr.bin/diff/diff.1 20 Jan 2013 11:19:12 - 1.41 > +++ src/usr.bin/diff/diff.1 15 Jul 2013 17:42:53 - > @@ -331,7 +331,7 @@ If either > or > .Ar file2 > is > -.Sq Fl , > +.Sq - , > the standard input is > used in its place. > .Ss Output Style > Index: src/usr.sbin/cron/crontab.1 > === > RCS file: /cvs/src/usr.sbin/cron/crontab.1,v > retrieving revision 1.28 > diff -u -p -u -p -r1.28 crontab.1 > --- src/usr.sbin/cron/crontab.1 31 Jan 2011 19:13:31 - 1.28 > +++ src/usr.sbin/cron/crontab.1 15 Jul 2013 17:42:57 - > @@ -48,7 +48,7 @@ they are not intended to be edited direc > .Pp > The first form of this command is used to install a new crontab from some > named file, or standard input if the pseudo-filename > -.Sq Fl > +.Sq - > is given. > .Pp > If the
How-To updated : Vpn IKEv2 between a Windows 8 Road Warrior Host and an OpenBSD-5.3 gateway
Hi everyone, I just updated my How-To about ikev2. You can reach it here : http://www.mouedine.net Cheers, Wesley MOUEDINE ASSABY
mdoc(7) .Sq Fl for a dash
Some of the manpages, e.g. crontab(1), markup the folklore phrase named file, or standard input if the pseudo-filename `-' is given as named file, or standard input if the pseudo-filename .Sq Fl is given. Is this correct semantic markup? IMHO not: it just abuses the fact that the flags (Fl) happen to start with a dash; but that's not what is meant here; this is not a flag; it is the literal dash that is recognized in place of a filename. So I believe it should be simply .Sq - Right? The diff below replaces those occurences that a grep revealed for me in /usr/share/man; Another grep reveals that most other manpages actually use ".Sq -". I left out oldrdist(1) and shutdown(8) where it _is_ actually a flag and the code processes it as such. Jan Index: src/libexec/getty/getty.8 === RCS file: /cvs/src/libexec/getty/getty.8,v retrieving revision 1.13 diff -u -p -u -p -r1.13 getty.8 --- src/libexec/getty/getty.8 31 May 2007 19:19:39 - 1.13 +++ src/libexec/getty/getty.8 15 Jul 2013 17:42:42 - @@ -55,7 +55,7 @@ is the special device file in .Pa /dev to open for the terminal (for example, ``ttyh0''). If there is no argument or the argument is -.Sq Fl , +.Sq - , the tty line is assumed to be open as file descriptor 0. .Pp The Index: src/usr.bin/diff/diff.1 === RCS file: /cvs/src/usr.bin/diff/diff.1,v retrieving revision 1.41 diff -u -p -u -p -r1.41 diff.1 --- src/usr.bin/diff/diff.1 20 Jan 2013 11:19:12 - 1.41 +++ src/usr.bin/diff/diff.1 15 Jul 2013 17:42:53 - @@ -331,7 +331,7 @@ If either or .Ar file2 is -.Sq Fl , +.Sq - , the standard input is used in its place. .Ss Output Style Index: src/usr.sbin/cron/crontab.1 === RCS file: /cvs/src/usr.sbin/cron/crontab.1,v retrieving revision 1.28 diff -u -p -u -p -r1.28 crontab.1 --- src/usr.sbin/cron/crontab.1 31 Jan 2011 19:13:31 - 1.28 +++ src/usr.sbin/cron/crontab.1 15 Jul 2013 17:42:57 - @@ -48,7 +48,7 @@ they are not intended to be edited direc .Pp The first form of this command is used to install a new crontab from some named file, or standard input if the pseudo-filename -.Sq Fl +.Sq - is given. .Pp If the
Re: 5.4-beta#20 xterm(1)/luit(1) in cwm, CM-Return random defunc
Philip Guenther wrote: > Ha! I believe this bug is a result of posix_openpt() being > implemented in 5.3 and the luit configure script picking that instead > of openpty(), as the code for the former results in the client side > being opened (by PTMGET), then closed, then reopened by name, which > leaves a window where the master will read EOF. >From the ktraces, it appears that in the parent luit, select() says an fd is ready for reading, but the read() returns EOF, and luit exits. If this is due to a race, then I don't see why only OpenBSD should be affected. The switch to openpty() has fixed this, but there is still another problem. Try something like this: $ while true; do luit -encoding ISO8859-2 -- ls; done Sometimes, luit will hang (stuck in select) and only exit when it can read a character from the tty (i.e., you press a key). ... And on my amd64, where I couldn't reproduce this before matthieu's patch, I now still don't get hangs, but screwed up termios settings-- most obviously onlcr is lost. Damn, I didn't realize luit was that buggy. The X.org version is effectively unmaintained. We should consider switching to Thomas Dickey's, who I think will be rather more interested in hearing about these bugs, if he hasn't fixed them already. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: DVD Video Ripping Tools
Sun 14.Jul'13 at 13:31:40 +, Christian Weisgerber > James Griffin wrote: > > > I want to rip some DVD's to my hard disk for viewing later. I've > > searched and found some old threads going back a few years which have > > some good suggestions and examples. As some of this stuff is a bit > > dated, can anyone recommend some decent software from packages/ports > > that will do the job? > > Personally, I use lsdvd to see what tracks there are and then just > dump them with mplayer, e.g. > > $ mplayer -dumpstream -dumpfile conan.vob dvd://1 Thanks Christian, nice simple solution. Jamie -- James Griffin: jmz at kontrol.kode5.net A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38
Re: ACPI - shutdown on current kernel
Hi Alexey, Alexey E. Suslikov wrote: I'm really trying to guess here, but could you try to revert http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/acpi/acpiec.c.diff?r1=1.47;r2=1.48 rebuild kernel and see if problem remain. Sebastian built me a kernel and I tried it out, save errors, power-off works. However hitting the power button to make the laptop to powerdown doesn't work anymore, it will just power-cycle the machine without "shutting it down". Previously that did work (except of course, leaving the computer in the strange running state). Riccardo
