| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
MFC r270653: Update man-pages to correctly refer to changed pathes and namin
MFC r270657: More man pages that need to know about vt in addition to syscon
MFC r270659: (by pluknet@) Missed comma.
MFC r270660: Back-out the references to vt(4) from this man-page. It appears
MFC r270933: Add references to vt(4) to further man-pages.
MFC r270934: Final patches to the tools used to convert syscons keymaps for
MFC r270935: Add vt(4) support to the console initialisation script, specifi
Second batch of MFCs to add support for Unicode keymaps for use with vt(4).
It contains the following changes:
- Add references to vt(4) to relevant man-pages.
- Update comment in defaults/rc.conf to mention vt
- Update rc.d/syscons to warn about syscons keymaps used under vt.
An attempt is made to identify the vt keymap to load instead.
- Minor changes to the conversion tool based on mail comments on keymaps.
Relnotes: yes
|
|
|
|
|
|
|
|
|
|
|
| |
also move to a 2-clause license. From n_hibma@:
"The 3rd clause was originally there for a reason, but I guess that it is
safe to assume that no one can assume endorsement by me or anyone else
without prior consent on anything really, so we might as well remove that
clause."
Approved by: n_hibma
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
| |
devices that return the next available device when opened.
PR: 50280, 50281, 50282, 50283
Submitted by: Sergey A.Osokin <osa@FreeBSD.org.ru>
|
|
|
|
| |
Reviewed by: n_hibma, roberto
|
|
|
|
|
|
| |
PR: docs/44306
Submitted by: Dmitry Dyomin <old@old.com.ua>
MFC after: 3 days
|
|
|
|
| |
PR: 40909
|
|
|
|
| |
PR: docs/32955
|
| |
|
|
|
|
|
|
|
|
|
|
| |
cd src/share; find man[1-9] -type f|xargs perl -pi -e 's/[ \t]+$//'
BTW, what editors are the culprits? I'm using vim and it shows
me whitespace at EOL in troff files with a thick blue block...
Reviewed by: Silence from cvs diff -b
MFC after: 7 days
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
precedent.
|
|
|
|
| |
Submitted by: Mike Meyer <mwm@mired.org>
|
| |
|
| |
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
| |
device blah0 -> device blah for PCI devices and busses.
|
|
|
|
|
| |
* some style and syntax fixes
* some duplicated $FreeBSD$ tags removed
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Sort xrefs
- FreeBSD.ORG -> FreeBSD.org
- Be consistent with section names as outlined in mdoc(7).
- Other misc mdoc cleanup.
PR: doc/13144
Submitted by: Alexey M. Zelkin <phantom@cris.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
track.
The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;
.\" $Id$
.\"
If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.
Approved by: bde
|
|
|
|
| |
OKed by: peter
|
| |
|
| |
|
|
|