summaryrefslogtreecommitdiffstats
path: root/etc/etc.sparc64
Commit message (Collapse)AuthorAgeFilesLines
* Remove the note about using vt220, which makes no sense at all.ed2009-06-141-3/+1
| | | | | | 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.
* Remove pts(4) entries from /etc/ttys.ed2009-02-121-512/+0
| | | | | | | | | | | | | | | 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.
* Restore 256 pty(4) entries.ed2008-08-241-0/+256
| | | | | | | | | | | | 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
* Remove old BSD-style entries from /etc/ttys and increase pts(4) to 512.ed2008-08-231-512/+256
| | | | | | | | | 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)
* Bump up the number of ttys supported by pty(4) to 512 by making use ofjhb2007-11-191-0/+256
| | | | | | | [pt]ty[lmnoLMNO][0-9a-v]. MFC after: 3 days Reviewed by: rwatson
* Add ttys lines for pts/0-pts/255.rwatson2007-11-151-0/+256
| | | | MFC after: 3 days
* Remove more vestiges of /usr/X11R6, but leave mtree for portmgr.dougb2007-05-291-1/+1
|
* Remove last vestiges of sab(4).marius2006-04-251-3/+0
|
* Enable getty(8) on ttyu2 by default in order to get machines that use amarius2006-02-041-1/+1
| | | | | | | | | 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
* - In preparation to turning syscons(4) etc. on by default in the sparc64marius2005-06-101-13/+14
| | | | | | | | | | | | 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.
* Be consistent about the serial line terminal type.obrien2005-03-091-5/+5
| | | | CVS ----------------------------------------------------------------------
* Start gettys on ttyu0 and ttyu1 instead of ttya and ttyz0 now thatmarcel2005-01-301-4/+4
| | | | | | uart(4) is the default driver. MFC after: 2 weeks
* Catch up with the new device name of sab(4). The entries for tty[a,b]marius2004-12-041-0/+2
| | | | | | 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.
* With the fixes to getty handling of non-existent devices a defaultkensmith2004-10-041-2/+3
| | | | | | | | | 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
* Add dumb console driver and related bits.simokawa2003-10-241-0/+2
| | | | | | | | 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.
* Changed the ttyd entries to ttyu, which correspond to the device nodesjake2003-09-111-4/+4
| | | | created by uart(4).
* Per previous announcement, remove the old version of the rc system.dougb2003-05-021-9/+0
| | | | | | | | | | 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.
* Make disktab(5) MI (repo-copied from etc.i386/disktab).ru2003-04-021-224/+0
|
* Change ofwcons to use the output-device property from the firmware for thejake2003-01-271-4/+4
| | | | | | | | | | 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
* Add example entries for ttya and ttyb (sab).jake2002-08-041-0/+2
|
* Mention that terminal type vt220 will work better if one needsgerald2002-04-171-2/+4
| | | | | | | interoperability with other systems like Solaris or GNU/Linux. PR: 33810 Approved by: obrien
* Populate etc.sparc64:jhb2002-01-073-0/+540
- 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)
OpenPOWER on IntegriCloud