d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
8b5fede0ac
freebsd-skq/sbin/init/ttys.arm

50 lines
2.0 KiB
Plaintext
Raw Normal View History

Import the ttys file for arm. make TARGET_ARCH=arm world now works (but still with external patches for the toolchain bits).
2004-06-11 15:37:49 +00:00
#
# $FreeBSD$
# @(#)ttys 5.1 (Berkeley) 4/17/89
#
# This file specifies various information about terminals on the system.
# It is used by several different programs. Common entries for the
# various columns include:
#
# name The name of the terminal device.
#
# getty The program to start running on the terminal. Typically a
# getty program, as the name implies. Other common entries
# include none, when no getty is needed, and xdm, to start the
# X Window System.
#
# type The initial terminal type for this port. For hardwired
# terminal lines, this will contain the type of terminal used.
Switch the default terminal emulation style to xterm for most platforms. Right now syscons(4) uses a cons25-style terminal emulator. The disadvantages of that are: - Little compatibility with embedded devices with serial interfaces. - Bad bandwidth efficiency, mainly because of the lack of scrolling regions. - A very hard transition path to support for modern character sets like UTF-8. Our terminal emulation library, libteken, has been supporting xterm-style terminal emulation for months, so flip the switch and make everyone use an xterm-style console driver. I still have to enable this on i386. Right now pc98 and i386 share the same /etc/ttys file. I'm not going to switch pc98, because it uses its own Kanji-capable cons25 emulator. IMPORTANT: What to do if things go wrong (i.e. graphical artifacts): - Run the application inside script(1), try to reduce the problem and send me the log file. - In the mean time, you can run `vidcontrol -T cons25' and `export TERM=cons25' so you can run applications the same way you did before. You can also build your kernel with `options TEKEN_CONS25' to make all virtual terminals use the cons25 emulator by default. Discussed on: current@
2009-11-13 05:54:55 +00:00
# For virtual consoles, the correct type is typically xterm.
Remove the reference to pseudo-terminals from the description. Pseudo-terminals are no longer listed in this file, since the utmpx implementation doesn't depend on ttyslot().
2011-03-30 08:22:29 +00:00
# Other common values include dialup for incoming modem ports, and
# unknown when the terminal type cannot be predetermined.
Import the ttys file for arm. make TARGET_ARCH=arm world now works (but still with external patches for the toolchain bits).
2004-06-11 15:37:49 +00:00
#
# status Must be on or off. If on, init will run the getty program on
# the specified port. If the word "secure" appears, this tty
# allows root login.
#
# name getty type status comments
#
# If console is marked "insecure", then init will ask for the root password
# when going to single-user mode.
console none unknown off secure
#
For video consoles, only launch a getty if the device exists. Differential Revision: https://reviews.freebsd.org/D15169
2018-05-09 20:49:00 +00:00
ttyv0 "/usr/libexec/getty Pc" xterm onifexists secure
Import the ttys file for arm. make TARGET_ARCH=arm world now works (but still with external patches for the toolchain bits).
2004-06-11 15:37:49 +00:00
# Virtual terminals
For video consoles, only launch a getty if the device exists. Differential Revision: https://reviews.freebsd.org/D15169
2018-05-09 20:49:00 +00:00
ttyv1 "/usr/libexec/getty Pc" xterm onifexists secure
ttyv2 "/usr/libexec/getty Pc" xterm onifexists secure
ttyv3 "/usr/libexec/getty Pc" xterm onifexists secure
ttyv4 "/usr/libexec/getty Pc" xterm onifexists secure
ttyv5 "/usr/libexec/getty Pc" xterm onifexists secure
ttyv6 "/usr/libexec/getty Pc" xterm onifexists secure
ttyv7 "/usr/libexec/getty Pc" xterm onifexists secure
Remove more vestiges of /usr/X11R6, but leave mtree for portmgr.
2007-05-29 06:37:58 +00:00
#ttyv8 "/usr/local/bin/xdm -nodaemon" xterm off secure
Import the ttys file for arm. make TARGET_ARCH=arm world now works (but still with external patches for the toolchain bits).
2004-06-11 15:37:49 +00:00
# Serial terminals
# The 'dialup' keyword identifies dialin lines to login, fingerd etc.
Enable ttyv0 and ttyu0 by default if they are available consoles. Tested on: RPI-B Sponsored by: The FreeBSD Foundation
2015-05-08 14:13:19 +00:00
ttyu0 "/usr/libexec/getty 3wire" vt100 onifconsole secure
Enable ttyu1, ttyu2, ttyu3 for arm installations. This should make all consoles available, whether it is VGA, HDMI, serial, or JTAG, but more importantly enables all consoles when ttyu0 is not predictable. For example, the Pandaboard ES apparently has three consoles available, but the DB9/RS232 serial port is ttyu2, so not available by default after the system boots. MFC after: 3 days Sponsored by: The FreeBSD Foundation
2015-06-21 19:50:02 +00:00
ttyu1 "/usr/libexec/getty 3wire" vt100 onifconsole secure
ttyu2 "/usr/libexec/getty 3wire" vt100 onifconsole secure
ttyu3 "/usr/libexec/getty 3wire" vt100 onifconsole secure
Import the ttys file for arm. make TARGET_ARCH=arm world now works (but still with external patches for the toolchain bits).
2004-06-11 15:37:49 +00:00
# Dumb console
dcons "/usr/libexec/getty std.9600" vt100 off secure
Reference in New Issue Copy Permalink