Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!noc.netcom.net!netcom.com!casy From: casy@netcom.com Subject: Re: cu/tip problems Message-ID: <casyDA56BJ.IuD@netcom.com> Organization: NETCOM On-line Communication Services (408 261-4700 guest) X-Newsreader: TIN [version 1.2 PL1] References: <casyDA4q65.571@netcom.com> Date: Wed, 14 Jun 1995 02:45:19 GMT Lines: 28 Sender: casy@netcom19.netcom.com casy@netcom.com wrote: : Hi! : I have installed FreeBSD 2.0 using the standard options then recompiled : the kernel so I could use my NE2000 card at 0x320 irq 5. But then I got : stuck: I had posted : here about my troubles getting cu/tip to work and I got the advice I : should use the cua0* and cuia0* devices for dial out to avoid the 'link : down' message that prevents me from dialing out on tty00. My only : problem is that that I cannot find the devices that I was recommended to : use. I included my device listing, my remote file, and my phones file. : Can you guys help me figure out what I'm doing wrong. Which device am I : supposed to use if tty00 gives nme 'link down' and if I don't have : 'cua00' or cuai00 and neither do I have cua01 or cuai01. : All help would be greately appriciated. I have figured out how to do this. Took me a week, but now I know what is going on. I searched through the news archives of www.cdrom.com with the keyword cua and I found references to MAKEDEV which in turn lead me to the solution: I had to generate a device useing /dev/MAKEDEV cua01. Now I'm logging in from my FreeBSD!!!! I'm so happy. It made my day:) Thanks for your patience with my newbie questions. You guys have helped me a lot! casy.