Commit Graph

14 Commits

Author SHA1 Message Date
Marius Strobl
2e47800d98 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
Marius Strobl
9a472268c8 - 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
David E. O'Brien
2a907aec6b Be consistent about the serial line terminal type.
CVS ----------------------------------------------------------------------
2005-03-09 03:57:08 +00:00
Marcel Moolenaar
9a3ee61355 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
Marius Strobl
3420a6e5f1 Catch up with the new device name of sab(4). The entries for tty[a,b]
can't be removed as ofw_console(4) and zs(4) use them so one has to
live with some complaints about non-existent devices at boot time and
remove the respective entries locally for now.
2004-12-04 14:03:45 +00:00
Ken Smith
dfea356f2a With the fixes to getty handling of non-existent devices a default
install now complains about ttyu0/ttyu1 not existing at boot time.
Since users wanting the uart based devices as terminals will need
to do something special to get them anyway set it up so a default
config doesn't complain.

MFC after:	3 days
2004-10-04 03:39:52 +00:00
Hidetoshi Shimokawa
869093b15d 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
Jake Burkholder
be177216b1 Changed the ttyd entries to ttyu, which correspond to the device nodes
created by uart(4).
2003-09-11 00:14:17 +00:00
Doug Barton
4b065e2ce1 Per previous announcement, remove the old version of the rc system.
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.
2003-05-02 05:27:35 +00:00
Ruslan Ermilov
cc76558ad4 Make disktab(5) MI (repo-copied from etc.i386/disktab). 2003-04-02 20:13:59 +00:00
Jake Burkholder
984e265523 Change ofwcons to use the output-device property from the firmware for the
name of the device that it creates.  Update /etc/ttys accordingly.

An alias is created for the old name so that old /etc/ttys will continue to
work, but due to aliases being implemented as symlinks in devfs you cannot
login as root when using the alias device.

Discussed with:	grehan
2003-01-27 04:42:17 +00:00
Jake Burkholder
2e55bb64c3 Add example entries for ttya and ttyb (sab). 2002-08-04 19:16:13 +00:00
Gerald Pfeifer
e6c0365295 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
John Baldwin
64798412f9 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