Date: Tue, 25 Feb 1997 21:47:31 -0600 (CST) From: "Jay D. Nelson" <jdn@qiv.com> To: Doug White <dwhite@resnet.uoregon.edu> Cc: wott@mail.iserv.net, freebsd-questions@freebsd.org Subject: Re: NEWBIE questions - cu & named Message-ID: <Pine.NEB.3.95.970225214202.823C-100000@acp.qiv.com> In-Reply-To: <Pine.BSI.3.94.970224225811.4530M-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry -- I got in on this late. cu uses the uucp configuration files. If they are not set up with at least "direct" in dial or Dialer, you probably can't get there. I never done anything more to get cu to work. -- Jay On Mon, 24 Feb 1997, Doug White wrote: ->On Mon, 24 Feb 1997 wott@mail.iserv.net wrote: -> ->> ->> I'm relatively new to FreeBSD (2.1.6) and am having a couple of ->> problems. ->> When trying to use cu, I receive an error that the specified port is ->> not found (cuaa2). I can use ecu, and dial right out, but the ->> display gets set so the text is black on black. Any suggestions? I'm ->> trying to attach to an older system and have to use some form of cu. -> ->Make sure you are in the dialer group (see /etc/group). -> ->> Also, I need the terminal type set to an att605 so when/if I get ->> connected I will be able to read things, will this be a problem? -> ->You need to tell the remote side you're an att605. -> ->> The named problem is minor, when starting up, I get an error that the ->> named.boot file is not found, but by loading it from a command prompt, ->> it loads just fine... possibly a problem in where it is located in the ->> sysconfig ? -> ->Perhaps, make sure the path to named.boot is given explicitly. -> ->Doug White | University of Oregon ->Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant ->http://gladstone.uoregon.edu/~dwhite | Computer Science Major ->
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.970225214202.823C-100000>