| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 of: r273544
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
They have no effect when coming in pairs, or before .Bl/.Bd
|
|
|
|
|
|
| |
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'.
|
| |
|
|
|
|
| |
Approved by: re (blanket)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
|
|
|
| |
is compiled in the kernel. Also add some useful xrefs to lock(1).
|
|
|
|
| |
full console history.
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
PR: docs/30473
Submitted by: Jonathan Hanna <jhanna@home.com>
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
PR: docs/28000
Submitted by: Robert Drehmel <robert@zoot.quizbot.org>
|
|
|
|
|
|
|
| |
shot2*.
PR:
Submitted by: Olexander Kunytsa
|
|
|
|
| |
with a trailing zero-width space: `e.g.\&'.
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
really "AUTHORS".
|
|
|
|
|
|
| |
Also fix some style bugs in the code and poor language in the man pages.
Reviewed by: sobomax
|
| |
|
|
|
|
|
|
| |
- add nik into Authors section.
Submitted by: ru
|
|
|
|
|
| |
Suggested by: many
Not objected to by: nik (scrshot co-author)
|
| |
|
|
|
|
| |
as they're listed in the synopsis (alphabetical).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
| |
PR: 26050
Submitted by: Alex Kapranoff <alex@kapran.bitmcnit.bryansk.su>
Approved by: nik
|
| |
|
|
|
|
|
|
|
| |
text mode. For example `vidcontrol -g 100x37 VESA_800x600' will setup 100x37
text mode as opposed to default 80x25.
Reviewed by: imp
|
| |
|
| |
|
| |
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
|
| |
PR: 16221
Submitted by: Kelly Yancey <kbyanc@posi.net>
|
| |
|
|
|
|
|
| |
VESA_132x30 is not available mode
SC_PIXLE_MODE -> SC_PIXEL_MODE
|
|
|
|
|
|
| |
to use the VESA_800x600 raster text mode.
- Fix the list of recognized keywords; "40x25" is not recognized,
but "VGA_40x25" is.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- 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>
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
and that font files can be specified in /etc/rc.conf[.local].
|
|
|
|
| |
Submitted by: Nathan Ahlstrom <nrahlstr@winternet.com>
|
|
|
|
|
|
| |
- 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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|