From owner-freebsd-questions Wed Oct 22 07:01:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA00117 for questions-outgoing; Wed, 22 Oct 1997 07:01:51 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA00104 for ; Wed, 22 Oct 1997 07:01:43 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id JAA16644; Wed, 22 Oct 1997 09:01:24 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id JAA02808; Wed, 22 Oct 1997 09:00:52 -0500 Message-ID: <19971022090052.02383@right.PCS> Date: Wed, 22 Oct 1997 09:00:52 -0500 From: Jonathan Lemon To: ringlord@bbs.dcoisp.net Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Freebsd on Remote Terminal? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from ringlord@bbs.dcoisp.net on Oct 10, 1997 at 01:39:44AM -0500 Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Oct 10, 1997 at 01:39:44AM -0500, ringlord@bbs.dcoisp.net wrote: > Hello everyone. > I have recently installed freebsd 2.2.2, and now I would like to > accomplish the following task. I need to be able to login to freebsd > from a remote terminal. The reason is because I have a speech output > device on this remote terminal that is my only way of seeing the screen. > Of course, once I get all my networking cards ETC configured, I can > just rlogin to it or telnet, but for now, I need to access my new > freebsd box over a remote terminal. What are the files that I need to > modify to accomplish this? Also, if there is some documentation that I > should be reading on this subject, if you could point me to it, I don't > mind reading. I just don't have a lot of time to figure this out since > I can't always have someone there reading the screen for me. Assuming that your terminal is connected through a serial port, you'll just need to modify /etc/ttys, and turn the status of the correct serial port from "off" to "on". Then 'kill -HUP 1' to re-read the /etc/ttys file. See the ttys(5) man page. -- Jonathan