| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Pseudo-terminals are no longer listed in this file, since the utmpx
implementation doesn't depend on ttyslot().
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we had utmp(5), we had to list all the psuedo-terminals in ttys(5)
to make ttyslot(3) function properly. Now that pututxline(3) deals with
slot allocation internally (not based on TTY names), we don't need to
list all the TTYs on the system in ttys(5) to make user accounting work
properly.
This patch removes all the entries from the /etc/ttys files, but also
the pts(4) entries that were appended implicitly, which was added in
r154838.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
|
|
|
|
|
| |
vt220 will not work better. Even though it probably will remove warnings
about unknown terminal types, a cons25 emulator is not compatible with
vt220 at all.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Even though I increased the amount of pts(4) entries in /etc/ttys some
time ago, I didn't realize back then those entries shouldn't have been
there in the first place.
I just looked at the getttyent() source code and it turns out when you
call setttyent(), it walks through /dev/pts and looks for the device
with the highest number. After you receive EOF's from getttyent(), it
makes up entries for pts(4) devices.
This means that adding entries for pts(4) is somewhat harmful, because
if you now traverse the list, you get redundant entries, so just remove
them.
|
|
|
|
|
|
|
|
|
|
|
|
| |
As discussed with Robert Watson on the src-committers list, it is safer
to keep at least some pty(4) entries in /etc/ttys, for applications that
roll their own PTY allocation routine and only search for BSD-style
PTY's.
This means we've now just toggled the amount of entries for pts(4) and
pty(4).
Requested by: rwatson
|
|
|
|
|
|
|
|
|
| |
Because we now use pts(4)-style PTY's exclusively, there is no use for
these entries in /etc/ttys. Right now the pts(4) entries only go from 0
to 255. Because we're going to touch these files anyway, increase the
number to 511.
Discussed with: philip (ex-mentor)
|
|
|
|
|
|
|
|
|
|
|
| |
The uart(4) driver has the advantage of supporting a wider variety of
hardware on a greater amount of platforms. This driver has already been
the standard on platforms such as ia64, powerpc and sparc64.
I've decided not to change anything on pc98. I'd rather let people from
the pc98 team look at this.
Approved by: philip (mentor), marcel
|
|
|
|
|
|
|
| |
[pt]ty[lmnoLMNO][0-9a-v].
MFC after: 3 days
Reviewed by: rwatson
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
All functionality from the previous system has been preserved, and
users should still customize their system boot with the familiar
methods, rc.conf, rc.conf.local, rc.firewall, sysctl.conf, etc.
Users who have customized versions of scripts that have been removed
should take great care when upgrading, since the compatibility code
that used those old scripts has also been removed.
|
|
|
|
| |
Approved by: re@ (scottl)
|
|
|
|
|
|
|
| |
interoperability with other systems like Solaris or GNU/Linux.
PR: 33810
Approved by: obrien
|
|
|
|
|
| |
syscons sh code was identical on both platforms except for whitespace
differences.
|
|
|
|
|
|
|
|
| |
as the previous line already tells us we are in rc.${MACHINE_ARCH}. This
also allows more syscons configuration messages during startup to fit on
one line.
Reviewed by: dougb
|
|
|
|
|
|
|
|
|
|
| |
* Put quotes around each line
* Single quotes for lines with no variable interpolation
* Double quotes if there is
* Capitalize each word that begins a line
* Make echo -n 'Doing foo:' ... echo '.' more of a standard
No functionality changes
|
|
|
|
| |
case got lost.
|
|
|
|
|
|
|
|
|
|
| |
kernel modules for ibcs2_enable and svr4_enable.
Don't rely on a shell script to do the neglibly less simple
job of loading a kernel module and running one command for
linux_enable.
These shell scripts are going away.
|
|
|
|
|
|
| |
location.
Sponsored by: LinuxWorld frustration
|
|
|
|
| |
revisited when the new /dev/random is done.
|
|
|
|
|
|
| |
happen with a keyboard and monitor the console change was not as needed
in the i386 case as the Alpha case. IMO >50% of Alpha installs are using
a serial console, the change matching rev 1.7 should not be backed out.
|
|
|
|
|
| |
the console reguardless of the type of console.
* Make the Alpha version match the i386 version.
|
|
|
|
|
|
| |
anable -> enable
Spotted by: Alexander Leidinger <Alexander@leidinger.net>
|
|
|
|
| |
Submitted by: Blaz Zupan <blaz@amis.net>
|
|
|
|
|
| |
Necessary change to due removal of apmconf which got moved into apm
by green.
|
|
|
|
|
|
|
|
|
| |
more comprehensive. Previously, at least colour changes were not
applied to all virtual consoles.
PR: 15066
Reported by: Andy Farkas <andyf@speednet.com.au>
Submitted by: yokota
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
case instead of test where appropriate, since case allows case is a sh
builtin and (as a side-effect) allows case-insensitivity.
Changes discussed on freebsd-hackers.
Submitted by: Doug Barton <Doug@gorean.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* All variables are now embraced: ${foo}
* All comparisons against some value now take the form:
[ "${foo}" ? "value" ]
where ? is a comparison operator
* All empty string tests now take the form:
[ -z "${foo}" ]
* All non-empty string tests now take the form:
[ -n "${foo}" ]
Submitted by: jkh
|
| |
|
|
|
|
|
|
| |
Make it clear that apmd depends on apmconf -e.
Reviewed by: obrien, my friend :-)
|
|
|
|
|
| |
Pointed out by: obrien
Forgotten by: iwasaki
|
|
|
|
| |
Update some files for apmd.
|
| |
|
|
|
|
|
|
| |
Submitted by: wes
Added commentary to ttys to clarify the meaning of the columns.
Added commentary to ttys to clarify the meaning of the columns.
|
|
|
|
| |
Suggested by: jkh
|
|
|
|
|
|
|
|
| |
Strictly speaking, it is not necessary; the screen saver will load
even if the splash module is still in memory. But still, it is the right
thing to do, otherwise the splash decoder module just wasts the kernel space.
Discussed with: des
|
| |
|
|
|
|
|
| |
instead the public writable directory /tmp
PR: conf/8330
|
| |
|
|
|
|
|
|
|
| |
already. The modstat output goes to the screen.
PR: 7351
Reviewed by: phk
Submitted by: Jos Backus <Jos.backus@nl.origin-it.com>
|
| |
|
| |
|
|
|
|
| |
for all virtual screens (via for loop)
|
|
|
|
| |
Submitted by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
|
|
|
|
| |
Reminded by: bde
|