mirror/freebsd
1
0
Fork 0
mirror of https://git.FreeBSD.org/src.git synced 2024-12-24 11:29:10 +00:00
Code Issues Releases Activity
7dbe66c157
freebsd/etc/etc.sparc64/ttys

56 lines
2.2 KiB
Plaintext
Raw Normal View History

Populate etc.sparc64: - The disktab was taken from etc.alpha. - rc.sparc64 doesn't do anything right now. - The ttys file has all the vty's commented out since we don't know how those will work yet. Also, an entry is added for the Openfirmware console device. Submitted by: jake (partially)
2002-01-07 23:53:34 +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.
Mention that terminal type vt220 will work better if one needs interoperability with other systems like Solaris or GNU/Linux. PR: 33810 Approved by: obrien
2002-04-17 10:42:41 +00:00
# Other common values include network for network connections on
Populate etc.sparc64: - The disktab was taken from etc.alpha. - rc.sparc64 doesn't do anything right now. - The ttys file has all the vty's commented out since we don't know how those will work yet. Also, an entry is added for the Openfirmware console device. Submitted by: jake (partially)
2002-01-07 23:53:34 +00:00
# pseudo-terminals, dialup for incoming modem ports, and unknown
# when the terminal type cannot be predetermined.
#
# 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
- In preparation to turning syscons(4) etc. on by default in the sparc64 GENERIC comment in ttyN. - Add the name of the device driver creating the device nodes above the respectives blocks so it's easier for user to find the right entry to shut up warnings from getty(8). Replace 'Requires device 'uart' be enabled.' with just 'uart(4)' as the former referred to a sparc64 GENERIC back when uart(4) wasn't enabled by default, yet. - Turn off the getty(8) on screen as screen is created by ofw_console(4) which is no longer enabled in the sparc64 GENERIC (and also only is a last resort) to shut up warnings from getty(8) with the current GENERIC.
2005-06-10 23:06:14 +00:00
# ofw_console(4)
screen "/usr/libexec/getty Pc" vt100 off secure
Be consistent about the serial line terminal type. CVS ----------------------------------------------------------------------
2005-03-09 03:57:08 +00:00
ttya "/usr/libexec/getty 3wire.9600" vt100 off secure
ttyb "/usr/libexec/getty 3wire.9600" vt100 off secure
- In preparation to turning syscons(4) etc. on by default in the sparc64 GENERIC comment in ttyN. - Add the name of the device driver creating the device nodes above the respectives blocks so it's easier for user to find the right entry to shut up warnings from getty(8). Replace 'Requires device 'uart' be enabled.' with just 'uart(4)' as the former referred to a sparc64 GENERIC back when uart(4) wasn't enabled by default, yet. - Turn off the getty(8) on screen as screen is created by ofw_console(4) which is no longer enabled in the sparc64 GENERIC (and also only is a last resort) to shut up warnings from getty(8) with the current GENERIC.
2005-06-10 23:06:14 +00:00
# syscons(4)
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
ttyv0 "/usr/libexec/getty Pc" xterm on secure
Populate etc.sparc64: - The disktab was taken from etc.alpha. - rc.sparc64 doesn't do anything right now. - The ttys file has all the vty's commented out since we don't know how those will work yet. Also, an entry is added for the Openfirmware console device. Submitted by: jake (partially)
2002-01-07 23:53:34 +00:00
# Virtual terminals
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
ttyv1 "/usr/libexec/getty Pc" xterm on secure
ttyv2 "/usr/libexec/getty Pc" xterm on secure
ttyv3 "/usr/libexec/getty Pc" xterm on secure
ttyv4 "/usr/libexec/getty Pc" xterm on secure
ttyv5 "/usr/libexec/getty Pc" xterm on secure
ttyv6 "/usr/libexec/getty Pc" xterm on secure
ttyv7 "/usr/libexec/getty Pc" xterm on 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
Populate etc.sparc64: - The disktab was taken from etc.alpha. - rc.sparc64 doesn't do anything right now. - The ttys file has all the vty's commented out since we don't know how those will work yet. Also, an entry is added for the Openfirmware console device. Submitted by: jake (partially)
2002-01-07 23:53:34 +00:00
# Serial terminals
# The 'dialup' keyword identifies dialin lines to login, fingerd etc.
- In preparation to turning syscons(4) etc. on by default in the sparc64 GENERIC comment in ttyN. - Add the name of the device driver creating the device nodes above the respectives blocks so it's easier for user to find the right entry to shut up warnings from getty(8). Replace 'Requires device 'uart' be enabled.' with just 'uart(4)' as the former referred to a sparc64 GENERIC back when uart(4) wasn't enabled by default, yet. - Turn off the getty(8) on screen as screen is created by ofw_console(4) which is no longer enabled in the sparc64 GENERIC (and also only is a last resort) to shut up warnings from getty(8) with the current GENERIC.
2005-06-10 23:06:14 +00:00
# uart(4)
Start gettys on ttyu0 and ttyu1 instead of ttya and ttyz0 now that uart(4) is the default driver. MFC after: 2 weeks
2005-01-30 09:31:22 +00:00
ttyu0 "/usr/libexec/getty std.9600" vt100 on secure
ttyu1 "/usr/libexec/getty std.9600" vt100 on secure
Enable getty(8) on ttyu2 by default in order to get machines that use a RSC (Remote System Control) connected via uart2 as console working out of the box. On machines that use uart2 to connect a keyboard and thus the ttyu2 node doesn't exist this will trigger a warning from getty(8) but cause no real harm. MFC after: 1 week
2006-02-04 23:30:09 +00:00
ttyu2 "/usr/libexec/getty std.9600" vt100 on secure
Changed the ttyd entries to ttyu, which correspond to the device nodes created by uart(4).
2003-09-11 00:14:17 +00:00
ttyu3 "/usr/libexec/getty std.9600" vt100 off secure
Add dumb console driver and related bits. dcons(4): very simple console and gdb port driver dcons_crom(4): FireWire attachment dconschat(8): User interface to dcons Tested with: i386, i386-PAE, and sparc64.
2003-10-24 15:44:10 +00:00
# Dumb console
dcons "/usr/libexec/getty std.9600" vt100 off secure
Reference in New Issue Copy Permalink