MFC r316422:

Remove checks that background (bg) colors are not bright and buggy
attempts to keep them that way. The bg brightness bit is interpreted
as blinking in some modes, but it would barely be useful to disallow
setting it when it would give blinking in code which knew when that
is. The old code mostly knew this wrong, and added handling errors.
It is in fact impossible to know, since future mode switches may
change the meaning of the bit many times on the screen and in history.

Old versions of vidcontrol disallowed bg color numbers >= 8 in all
cases. This is very VGA/syscons-centric. Syscons uses the VGA defaults
of blinking fg instead of bright bg in text mode and bright bg in
graphics mode. On VGA, this is very easy to toggle at any time, and
vt blows away the VGA text mode default at boot time.

r146736 changed this to try to allow bg color numbers in graphics mode
only. This is even more VGA/syscons-centric, and there are many bugs
in this, and many nearby bugs in the parser. These are increased or
decreased by differences and bugs in vt and teken.

Perhaps the most obvious bug was that almost any vidcontrol command
which changes any color or the mode causes an error if the initial fg
color is bright. E.g., in syscons text mode, after "vidcontrol
lightwhite" to make the fg bright, another "vidcontrol lightwhite" is
rejected and buggy fixup code changes the fg to white. This is because
the bright fg color creates a bright bg color for the phantom reverse
video attribute, so was rejected. (The reverse video attribute is
phantom because teken ignores the user's setting of it and simply
reverses the fg attributes to create the bg attributes. Sometimes
some layer masks off the brightness/blinking bit, but not here.)

Perhaps the next most obvious one was that "vidcontrol lightgreen
lightblue" was misparsed as 2 settings of the fg instead of 1 setting
of the fg and 1 invalid setting of the bg. This is because the
parser supports an undocumented syntax with many parsing bugs (an
ambiguity gives this one).

I recently fix bugs in teken that broke setting of bright fg's and
bg's in the normal way. This gave more settings of then, so the old
bugs showed up more often.

MFC r326276:

various: general adoption of SPDX licensing ID tags.

Mainly focus on files that use BSD 2-Clause license, however the tool I
was using misidentified many licenses so this was mostly a manual - error
prone - task.

The Software Package Data Exchange (SPDX) group provides a specification
to make it easier for automated tools to detect and summarize well known
opensource licenses. We are gradually adopting the specification, noting
that the tags are considered only advisory and do not, in any way,
superceed or replace the license texts.

No functional change intended.

MFC r308312: vidcontrol: improve error handling in vt(4) font loading

PR: 209078

Copy head@r302406 to stable/11 as part of the 11.0-RELEASE cycle.
Prune svn:mergeinfo from the new branch, as nothing has been merged
here.

Additional commits post-branch will follow.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Add "vidcontrol -i active", to print out active vty number,
to be used with eg "vidcontrol -s".

Reviewed by: emaste@
MFC after: 1 month
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D4968

Add META_MODE support.

Off by default, build behaves normally.
WITH_META_MODE we get auto objdir creation, the ability to
start build from anywhere in the tree.

Still need to add real targets under targets/ to build packages.

Differential Revision: D2796
Reviewed by: brooks imp

vidcontrol: skip invalid video modes returned by vt(4)

vt(4) has a stub CONS_MODEINFO ioctl that does not provide any data
but returns success. This needs to be fixed in the kernel, but address
it in vidcontrol(1) as well in case it's run on an older kernel.

Reviewed by: bde
Sponsored by: The FreeBSD Foundation

vidcontrol: make size argument optional again for syscons

r273544 changed the -f option allow no arguments in vt mode (used to
reset the font back to the default), but broke the optionality of the
size argument for syscons. Drop the required argument from syscons'
optstring for -f so the optional argument handler works the same way
for both syscons and vt.

Reported by: bde
Sponsored by: The FreeBSD Foundation

vt(4): Add PIO_VFONT_DEFAULT ioctl to restore the default builtin font

To restore the default font using vidcontrol(1), use the "-f" flag
without an argument:
vidcontrol -f < /dev/ttyv0

PR: 193910
Differential Revision: https://reviews.freebsd.org/D971
Submitted by: Marcin Cieslak <saper@saper.info>
Reviewed by: ray@, emaste@
Approved by: ray@
MFC after: 1 week

Add references to vt(4) to further man-pages.

MFC after: 3 days

Fix vt(4) detection in kbdcontrol and vidcontrol

As sc(4) and vt(4) coexist and are both enabled in GENERIC, the existence
of a vt(4) sysctl is not sufficient to determine that vt(4) is in use.

Reported by: Trond Endrestøl

use .Mt to mark up email addresses consistently (part2)

PR: 191174
Submitted by: Franco Fichtner <franco@lastsummer.de>

o Teach vidcontrol(1) how to load vt(4) font.
o Teach vidcontrol(1) to distinct which virtual terminal system is running now.
o Load vt(4) fonts from different location.
o Add $FreeBSD$ tag for path.h.

Tested by: Claude Buisson <clbuisson@orange.fr>

MFC after: 7 days
Sponsored by: The FreeBSD Foundation

The M_VESA_MODE_MAX is latest valid mode - not the first invalid.
Permit its use in vidcontrol -i

PR: bin/119483
Submitted by: Dan Lukes <dan@obluda.cz>
Arrival-Date: Wed Jan 09 10:30:01 UTC 2008
Reviewed by: ed
MFC after: 3 days

More -Wmissing-variable-declarations fixes.

In addition to adding `static' where possible:

- bin/date: Move `retval' into extern.h to make it visible to date.c.
- bin/ed: Move globally used variables into ed.h.
- sbin/camcontrol: Move `verbose' into camcontrol.h and fix shadow warnings.
- usr.bin/calendar: Remove unneeded variables.
- usr.bin/chat: Make `line' local instead of global.
- usr.bin/elfdump: Comment out unneeded function.
- usr.bin/rlogin: Use _Noreturn instead of __dead2.
- usr.bin/tset: Pull `Ospeed' into extern.h.
- usr.sbin/mfiutil: Put global variables in mfiutil.h.
- usr.sbin/pkg: Remove unused `os_corres'.
- usr.sbin/quotaon, usr.sbin/repquota: Remove unused `qfname'.

Call set_terminal_mode() after video mode change, not before, because
video mode change always reset terminal mode to xterm.
It allows things like 'vidcontrol -T cons25 80x30' works as supposed,
and allows 'allscreens_flags="-T cons25 80x30"' in /etc/rc.conf too.

MFC after: 1 week

Spelling fixes for usr.sbin/

Reencode files to UTF-8. Drop CP1252 em-dash.

Add static keywords to vidcontrol(1).

While there, remove the false optimisation of the colors array. It seems
that changing it to an array of pointers instead of a 16x16 array does
not cause any increase in binary size at all.

mdoc: drop redundant .Pp and .LP calls

They have no effect when coming in pairs, or before .Bl/.Bd

Print memory model of the video mode except for planar memory model.
'P', 'D', 'C', 'H', 'V' mean packed pixel, direct color, CGA, Hercules,
VGA X memory models respectively where they have fixed number of planes.

The last big commit: let usr.sbin/ use WARNS=6 by default.

Add a new flag to vidcontrol, -T, that allows terminal mode switching.

This will make it more easy for people to experiment with TERM=xterm.
Instead of echoing these strange escape sequences, I can just instruct
them to run `vidcontrol -T xterm'.

Tweak some wording and markup.

Remove bogus casts of valid integer ioctl() arguments.

Fix so that color changes are not lost when the video mode changes.

PR: bin/83553
Submitted by: Dan Lukes <dan at obluda dot cz>

Markup fixes.

Approved by: re (blanket)

Add VESA mode support for syscons, which enables the support of 15, 16,
24, and 32 bit modes. To use that, syscons(4) must be built with
the compile time option 'options SC_PIXEL_MODE', and VESA support (a.k.a.
vesa.ko) must be either loaded, or be compiled into the kernel.

Do not return EINVAL when the mouse state is changed to what it already is,
which seems to cause problems when you have two mice attached, and
applications are not likely obtain useful information through the EINVAL
caused by showing the mouse pointer twice.

Teach vidcontrol(8) about mode names like MODE_<NUMBER>, where <NUMBER> is
the video mode number from the vidcontrol -i mode output. Also, revert the
video mode if something fails.

Obtained from: DragonFlyBSD
Discussed at: current@ with patch attached [1]
PR: kern/71142 [2]
Submitted by: Xuefeng DENG <dsnofe at msn com> [1],
Cyrille Lefevre <cyrille dot lefevre at laposte dot net> [2]

Use \033 instead of \e because \e is not a standard.

Noticed by: stefanf
Reviewed by: diff(1)

A foreground color number on pc98 console is 7 not 15.

Use \e for escape char instead of ^[ directly.

WANRS=6 cleanup for vidcontrol(1):
- Use foo(void) instead of foo().
- Use static where applicable.
- Apply more const's when passing parameters
- signed/unsigned madness
- Avoid namespace collision by adding underscores.
- For 64-bit architectures, use %zx instead of %x
when necessary.
- When storing constants, use const instead of
variable.
- Bump WARNS?= from 2 to 6

Propagate ioctl() failure to exit status

mdoc(7) police: Nits.

Document the fact that VTY locking is easily bypassable when DDB
is compiled in the kernel. Also add some useful xrefs to lock(1).

Add a new `-H' modifier, which when combined with `-p' or `-P' allows to dump
full console history.

Remove some missing words.

Submitted by: roam

Deuglify the usage message by making it look more like the synopsis in
the manual page.

Add an -S option that allows the user to disable vty switching. It is
implemented using a new VT_LOCKSWITCH ioctl. Although it is possible
to implement something like this by VT_SETMODEing to VT_PROCESS and
never releasing the vty, that method has a number of downsides, the
biggest of which is that some program has to stay resident for the
lock to be in effect.

Reviewed by: roam, sheldonh

Fix typo in the BSD copyright: s/withough/without/

Spotted and suggested by: des
MFC after: 3 weeks

Use `The .Nm utility'

Fix typo: s/forth/fourth/

Grammar nits.

When loading a font allow suffix specifying its size be omited, in which
case use size of the currently displaying font as a suffix. For example,
when the when the size of the currently displayed font is 8x8 the
following command will load koi8-r-8x8.fnt.

# vidcontrol -f koi8-r

MFC after: 2 weeks

mdoc(7) police: markup nits.

PR: docs/30473
Submitted by: Jonathan Hanna <jhanna@home.com>

mdoc(7) police:

1) Removed the low-level (unneeded in this context) details on
escape sequences that are already documented in screen(4).

2) Removed whitespace at EOL.

3) Removed the garbage from previous revision.

Add additional information about VGA attributes.

PR: docs/28000
Submitted by: Robert Drehmel <robert@zoot.quizbot.org>

The ports that convert screendumps into text or png called scr2*, not
shot2*.

PR:
Submitted by: Olexander Kunytsa

mdoc(7) police: protect trailing full stops of abbreviations
with a trailing zero-width space: `e.g.\&'.

mdoc(7) police:

Avoid using parenthesis enclosure macros (.Pq and .Po/.Pc) with plain text.
Not only this slows down the mdoc(7) processing significantly, but it also
has an undesired (in this case) effect of disabling hyphenation within the
entire enclosed block.

Use the correct ioctl command to set a VESA mode.

PR: 24423
MFC after: 10 days

Remove GCC'isms in CFLAGS.

Remove whitespace at EOL.

Add a comma between the two names in the CONTRIBUTERS section.

Add section "CONTRIBUTORS" and move nik and sobomax there, since we are not
really "AUTHORS".

Move the scrollback controls from kbdcontrol to vidcontrol.
Also fix some style bugs in the code and poor language in the man pages.

Reviewed by: sobomax

- Sort usage() output;
- sync usage() with reality and manpage;
- display usage() even if terminal is not a syscons.

Submitted by: ru, sobomax

Spell FreeBSD.org correctly.

- Fix markup;
- add nik into Authors section.

Submitted by: ru

Move scrshot(1) functionality into vidcontrol(1).

Suggested by: many
Not objected to by: nik (scrshot co-author)

Proper upper limit for mousechar start is UCHAR_MAX - 3, not UCHAR_MAX

PR: 24437
Submitted by: Cejka Rudolf <cejkar@dcse.fee.vutbr.cz>

mdoc(7) police: normalize .Nd.

List the explanations of the command line arguments in the same order
as they're listed in the synopsis (alphabetical).

mdoc(7) police: Fixed markup.

Allow user to omit font size specification when loading a font. In addition
the following fixes had been made:

- check the size of the font being loaded and compare it with possible sizes
to minimise possibility of loading something that is not a fontfile at all
and turning console screen into garbage;

- prevent buffer overflow (and coredump as a result ) when loading valid
uuencoded file with size that exceeds allocated buffer;

- correct and improve several error messages.

Approved by: -audit, -hackers (silently)

Mention that the vga(4) driver supports 90-column video modes.

PR: 26050
Submitted by: Alex Kapranoff <alex@kapran.bitmcnit.bryansk.su>
Approved by: nik

- Backout botched attempt to introduce MANSECT feature.
- MAN[1-9] -> MAN.

Set the default manual section for usr.sbin/ to 8.

Eliminate mdocNG warnings caused by misplaced or extraneous macro calls.

New option `-g' to allow selecting custom text geometry in VESA_800x600 raster
text mode. For example `vidcontrol -g 100x37 VESA_800x600' will setup 100x37
text mode as opposed to default 80x25.

Reviewed by: imp

mdoc(7) police: use certified section headers wherever possible.

Spell the sos's name correctly.

Avoid use of tbl(1).

Initiate deorbit burn sequence for <machine/console.h>.

Replace all in-tree uses with necessary subset of <sys/{fb,kb,cons}io.h>.
This is also the appropriate fix for exo-tree sources.

Put warnings in <machine/console.h> to discourage use.
November 15th 2000 the warnings will be converted to errors.
January 15th 2001 the <machine/console.h> files will be removed.

Remove single-space hard sentence breaks. These degrade the quality
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.

updates the vidcontrol man page to include mention of the new -M flag

PR: 16221
Submitted by: Kelly Yancey <kbyanc@posi.net>

Make the mouse cursor char code configurable via the CONS_MOUSECTL
ioctl.

By popular demand.

Fix broken cross reference : kldload(1) -> kldload(8)

-Wall fix: ambigious else

Various style and visual changes.
VESA_132x30 is not available mode
SC_PIXLE_MODE -> SC_PIXEL_MODE

Fix -s option.

PR: bin/13799

- Mention that the SC_PIXEL_MODE kernel option is required, in order
to use the VESA_800x600 raster text mode.
- Fix the list of recognized keywords; "40x25" is not recognized,
but "VGA_40x25" is.

$Id$ -> $FreeBSD$

Various man page cleanup:

- 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>

Added the EXAMPLE section and try to make the text slightly more informative.

Grammar and Spelling Reviewed by: mpp

While mpp kindly checked grammar and spelling, any technical errors
remaining in the man pages are entirely of mine.

Reflect recent changes in syscons.

Mention that 8x8 font is required for 43, 50 and 60 line text modes,
and that font files can be specified in /etc/rc.conf[.local].

Change LKM to KLD.

Submitted by: Nathan Ahlstrom <nrahlstr@winternet.com>

Back out a couple of i386 conditionals which aren't needed with the new
syscons and fix a few printfs.

Reviewed by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>

fix for compiling on alpha

The first stage of console driver reorganization: activate new
keyboard and video card drivers.

- Express various sizes in bytes, rather than Kbytes, in the video
mode and adapter information structures.

Don't assume that we have extended modes on all platforms.

VESA BIOS support update in syscons.

- Accept generic video mode names: 80x25, 80x30, etc. Specific video
mode names, VGA_80x25, VESA_132x25, are still accpeted too.
- Update the man page accordingly.

Add new '-i' option to usage().

Add VESA support to syscons.

Kazu writes:

The VESA support code requires vm86 support. Make sure your kernel
configuration file has the following line.
options "VM86"
If you want to statically link the VESA support code to the kernel,
add the following option to the kernel configuration file.
options "VESA"

The vidcontrol command now accepts the following video mode names:
VESA_132x25, VESA_132x43, VESA_132x50, VESA_132x60, VESA_800x600

The VESA_800x600 mode is a raster display mode. The 80x25 text will
be displayed on the 800x600 screen. Useful for some laptop computers.

vidcontrol accepts the new `-i <info>' option, where <info> must be
either `adapter' or `mode'. When the `-i adapter' option is given,
vidcontrol will print basic information (not much) on the video
adapter. When the `-i mode' option is specified, vidcontrol will
list video modes which are actually supported by the video adapter.

Submitted by: Kazutaka YOKOTA yokota@FreeBSD.ORG

ioctl() request args are unsigned longs, so don't attempt to store
them as ints. Among other bugs, doing so at best caused benign
overflow followed by fatal sign extension on machines with 32-bit
ints and 64-bit longs.

Use err(3). Stylistic changes in man page.

Add ref to moused(8).

Update to compile under Lite2 includes

Add a -s option for setting the current vty. This should make
life easier if a PS/2 mouse locks up the keyboard (frequent-ish,
but not repeatable).
Tidy up code (a bit) and make it -Wall

Is this a 2.2 candidate ? (although it doesn't -Wall in 2.2 because
of the lack of sys/sysproto.h

Revert $FreeBSD$ to $Id$

Make the long-awaited change from $Id$ to $FreeBSD$

This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.

Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.

Convert to mdoc format.

Submitted by: Sandro Sigala <sandro@cat.local.net> as part of PR# 2134

Fix typo.

Submitted by: Philippe Charnier <charnier@xp11.frmug.org>

Added new -m option, that enable / disables the mousepointer on
a textmode screen.

Fix a bunch of spelling errors in a bunch of man pages.

Remove trailing whitespace.

remove option "-s saver" from usage()

Next syscons update (given up on numbering :)

Removed screensavers from syscons, they are now LKM's. This makes it
possible to do some really "interesting" screensavers...
Fixed bug that sometimes caused garbage to appear when leaving
"scroll-lock" history.
Reformattet indentation, it got too deep for a normal 80 pos screen.
Split up in syscons.c & syscons.h for use with the saver-lkm's.
Temporarily removed -s option from vidcontrol, savers should now
be loaded with modload.

Fixed usage() (cosmetic changes. "(string)" looks much better
than "(string" :-)

Added new choises of cursors.

Added 80x30 & 80x60 experimental modes officially.

Third round in syscons update.

Display update method changed, now allways write in memory buffer,
then periodically update physical display.
Speed improvements (now > 5 times faster than the old syscons).
History now circular buffer, with changeable size.
History scroll by up/down line, up/down page, home and end.
Backtab proberly implemented.
Now space for 96 function keys, 63 allocated standard, default now
SCO/SYSV compat again as in the old days.
New keyboard definition files ~share/syscons/keymaps/*
Misc fixes for old "hacks" that broke SCO/SYSV compat.
More that I forgot before writing this...

First round in syscons update. Several new features has been added:

No kernel config options anymore besides keyboard language layout.
Virtual consoles are now dynamically allocated, no NCONS anymore.
Software cursor blinking/nonblinking.
Visual bell for laptops (don't beep at meetings :-).
Cursor/bell default type setable via config "flags" instead of as defines.
Cursor/bell type setable via ioctl's.
New video modes 80x30 80x60 for some laptops, and those with multisync monitors.
Scroll-lock history (length currently fixed at 100 lines).
Lots of cleanups, some only commented out for now (will goaway soon).
Support for new features in vidcontrol/kbdcontrol.
Updated manpages.

usage help: uncomment -d option, add -x option

Document -d and -x options

Added support for some of the new video modes in syscons.

Reviewed by:
Submitted by:
Obtained from:

Added vidcontrol util from 1.1.5.1+

Reviewed by:
Submitted by: