s/comms/communications/

This commit is contained in:
Giorgos Keramidas 2003-02-01 17:48:26 +00:00
parent ceafe46b44
commit 8471e51628
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=15874

View file

@ -13,7 +13,7 @@
<h2>The Problem</h2>
<p>You have a computer room with lots of Unix server machines and
lots of comms hardware. Each of these machines needs a serial
lots of communications hardware. Each of these machines needs a serial
console. But serial terminals are hard to find and quite
expensive (especially compared to a much more capable PC). And
they take up a lot of precious space in the computer room.</p>
@ -71,7 +71,7 @@
"<em>KVM switch</em>" is one possible solution. This allows the
use of a single <em>K</em>eyboard, <em>V</em>ideo screen and
<em>M</em>ouse for multiple boxes. This cuts down on the space
problem, but only works for PC hardware (not any comms gear you
problem, but only works for PC hardware (not any communications gear you
might have), and is not accessible from outside the computer
room. Nor does it have much scroll-back or logging, and you
have to handle alerting some other way. The big downside is
@ -1147,7 +1147,7 @@ ttyd0 "/usr/libexec/getty std.9600" vt100 on secure
<p>David Harris' <a
href="http://www.conserver.com/consoles/msock.html">Minor Scroll
Of Console Knowledge</a> contains heaps of good information on
serial consoles and serial comms in general.</p>
serial consoles and serial communications in general.</p>
<p>His <a href="http://www.conserver.com/consoles/">Greater Scroll
of Console Knowledge</a> contains even more specific info on
@ -1229,7 +1229,7 @@ conventions
Last modified: Thu Jul 19 10:19:28 EST 2001
<!-- hhmts end -->
<br>
$Id: article.sgml,v 1.10 2002-12-15 21:57:29 ceri Exp $
$Id: article.sgml,v 1.11 2003-02-01 17:48:26 keramida Exp $
</body>
</html>