More typos and suggestions

Hello,

I would like to tell you about some bugs I've recently encountered, along with ideas of possible enhancement.

The NetBSD Guide, 27.1.1 Configuration of generic mapping
	smtp_generic_maps = hash:/etc/postfix/generic
The variable does not exist anymore. After a long time spent searching the web, I found out it has been
renamed to "sender_canonical_maps", and either it's not mentioned in the manpages, or I simply
overlooked it.

It would be nice to see some more examples, like this one, that allows the use of gmail, who require
authentication and encryption:
	smtp_use_tls = yes
	smtp_sasl_auth_enable = yes
	relayhost = [smtp.gmail.com]:587
	smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
	smtp_sasl_security_options =
	sender_canonical_maps = hash:/etc/postfix/generic
	message_size_limit = 20480000
The contents of sasl_passwd are:
	# destination                   credentials
	[smtp.gmail.com]:587		mike.d.ft402:p4$$W0rD
	# [mail.isp.example]:submission username:password
It and sasl_passwd.db must have proper mode (640?) so that random people can not see their contents.

The "message_size_limit" variable is very useful on its own, for emails nowadays may contain large
attachments, and might fail to be delivered locally. If you run fetchmail from cron, that might give an
illusion of having no incoming mail.

Speaking of cron, it would be nice to mention it in "27.2 fetchmail", for this saves the trouble of checking

Style guide for Markdown?

Hi,

converting to Markdown is easy, but there are some things underspecified
(e.g., how to reference commands). Call me a nitpicker, but this is a style
guide I roughly thought about. I don't want to enforce it for anyone, just
hear some comments.

Regards, Julian

# Style guide for NetBSD documentation

Markdown is a very liberal language in what range of input it accepts,
rendering all the same output although looking very different.

This is a proposal how to write NetBSD documentation. It is not necessary to  
strictly adhere it, but for the sake of unity and readability, the last two 
sections about *Code and keywords* and *Referencing manpages* should be read.

# Using lists

Lists should be indented by a space, an asterisk, and a space again. Text on  
that list level should then continue with three spaces indented.
Deeper list levels should continue the same pattern, just starting with the 
indentation. I.e., second-level lists should be started by four spaces, then
an asterisk, then a space; following lines should be indented by six spaces,
etc.

Bad:

* structures

Legal questions: Copyright notices

Hi,

when looking at the {NetBSD,internals,pkgsrc} guide, you always see the
acknowledgements and copyright notices separately, and blabla, NetBSD is a
registered trademark.
I wonder: How should such things be handled in the wiki? Is there need for a
copyright by TNF? Is there need for a trademark note? Do we have to tell
everyone that registered trademarks of their respective owners, etc.?
How should achknowledgements be handled? Put them in the commit messages, or
continue having them separately?
Do we have the possibility to add comments in ikiwiki, to put licences in? Or
should we make them public?
What is the default licence?

Regards, Julian

re: MAN UTD COOPERAZIONE,

MAN UTD COOPERAZIONE,
Matt Busby Way, Old Trafford,
Manchester, M16 0RA, Regno Unito.
+44-871-974-0480

Questo messaggio ti informiamo che non vi è una linea MANCHESTER UNITED Donazione richiama programma
internazionale per il primo trimestre dell'anno 2013 e
che sono stati selezionati tramite e-mail attraverso il nostro sistema di selezione computerizzata
(CSS), che ti ha fatto un beneficiario di 1 milione di EUR. Fornire con la tua
Nome completo:
Numero di telefono:
  Indirizzo:
Età / Sesso / Professione
Per tutti i dettagli e le procedure di reclami,
Persona di contatto: MR.EVANS PETERSON
Emai: pte <at> manager.in.th
Tel. Numero: +44-871-974-0480

CD-ROM information on NetBSD website

Hi,

This page:
http://netbsd.org/releases/index.html#formal
says NetBSD 6.0.1 CD-ROMs can be ordered, but the next page does not list places 
offering anything after 5.0.1.
I have not found any site offering 6.0.1 with Google...

Kind regards,

--

-- 
Luc van der Veen
http://luc.xs4all.nl

What is the licence of nb documentation?

Hi,

I'm wondering: What is the licence of the documentation?
The Guide contains information about it, but the wiki and the website?

Regards, Julian

announcing mdoc.su, a deterministic man-page URL shortener

Dear NetBSD,

I would like to announce and introduce http://mdoc.su/ , 
a deterministic URL shortener for BSD manual pages, 
written entirely in nginx.conf.

It supports several address schemes, for example:

http://mdoc.su/NetBSD/3X11/XFree
http://mdoc.su/netbsd/macppc/4/intro
http://mdoc.su/n/intro.4.macppc
http://mdoc.su/n/mdoc.7
http://mdoc.su/n/curl

Source code for the whole mdoc.su.nginx.conf is available at:
https://github.com/cnst/mdoc.su
https://bitbucket.org/cnst/mdoc.su

Specifically, the following currently (as of 2013-02-17) controls 
NetBSD rewriting, and best describes the access scheme for NetBSD:

	location /NetBSD {	rewrite	^/NetBSD(/.*)?$	/n$1;	}
	location /n {
		set	$nb	"http://netbsd.gw.com/cgi-bin/man-cgi?";
		rewrite	^/netbsd(/.*)?$	/.$1;
		rewrite	^/./([a-z]+[0-9]*[kx]?)/([^/]+)/([^/]+)$	$nb$3+$2.$1	redirect;
		rewrite	^/./([^/]+)/([^/]+)$		$nb$2+$1	redirect;
		rewrite	^/./([^/]+)\.([1-9]\.[a-z]+[0-9]*[kx]?)$	$nb$1+$2	redirect;
		rewrite	^/./([^/]+)\.([1-9])$		$nb$1+$2	redirect;
		rewrite	^/./([^/]+)$			$nb$1	redirect;

awk FS magic

The -F option for awk is more clever than the manual says.  Do we want
the behavior, or is the manual right?  

I noticed a working bug in a little script that led to this suprising
result:

	$ echo foo | awk -F t '{print FS}' | hexdump -C
	00000000  09 0a                                             |..|
	00000002

If the argument to the -F option is

	t

awk assumes you meant '\t' and sets the FS variable to TAB.  That's not
mentioned in the manual.  Apparently the only way to use the letter 't'
as a field separator is with the regex '[t]'.

I'm sure that's meant to help the clueless, because I found myself
taking advantage of it in my own script

        |  grep -f /etc/whitelist.dat   \
        |  awk -F\t '{print $2}'  \
        |  sed s'/[<>]//g'  \

even though I had no right to expect it to work.  

This appears to be the only specially treated character.  The relevant
function is setfs().  It has a pithy comment inside conditional
compilation:

Вот наша раскрутка реально приносит прибыль.

http://connemara.seguret.chez.com/download/u1.php

Perdi il tuo peso facilmente

A typo in the Guide.

Grettings,

I've found an error in the Guide from 120101, that can slightly affect 
the understanding.
Pp. 227, 235 - "lose" should be used instead of "loose".

Sincerely,
Mike