Date: Mon, 14 Sep 1998 14:47:04 -0500 (EST) From: Alfred Perlstein <bright@hotjobs.com> To: Brian Somers <brian@Awfulhak.org> Cc: questions@FreeBSD.ORG Subject: Re: help with mgetty? Message-ID: <Pine.BSF.3.96.980914144401.19799C-100000@bright.fx.genx.net> In-Reply-To: <199809141114.MAA10130@woof.lan.awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
heh, as a funny side note you were quite right, i had to reboot to get rid of init trying to fork the "wrong" mgetty. now i know for future referance. works fine now, i just have to tweak the win95 TAPI driver to fake it out enough... y'know i find it quite irritating that so much of microsoft's stuff has no, or hard to find docs... C:\> man tapi bad command or filename C:\> feh... anyhow if i get the .INF file right, i should be able to use my serial line as dial up netowrking device... i'll post it back if anyone is interested. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Mon, 14 Sep 1998, Brian Somers wrote: > You shouldn't comment things out of /etc/ttys - switch them off > instead. If you comment them out, init tends to forget about them > and they don't get killed. > > BTW, why do you want to use mgetty on a null-modem ? Won't getty do, > bearing in mind the pp= capability in /etc/gettydefs ? > > > does anyone here have config files to get mgetty working on a serial line > > (null modem) with PPP? > > > > i'm working on it currently but if anyone could toss me some working > > config files i'd appreciate it a lot. > > > > one of the "problems" i'm having is that it seems that mgetty is trying to > > be run twice and if happily filling my logs up :) > > > > tried these two lines in /etc/ttys: > > #cuaa1 "/usr/local/sbin/mgetty -s 115200" unknown on insecure > > ttyd1 "/usr/local/sbin/mgetty -s 115200" unknown on insecure > > > > mgetty logs: > > # tail mgetty.* > > ==> mgetty.cuaa1 <== > > 09/13 02:12:59 aa1 print welcome banner (/etc/issue) > > 09/13 02:12:59 aa1 getlogname (AUTO_PPP), read:[0d] > > 09/13 02:12:59 aa1 input finished with '\r', setting ICRNL ONLCR > > 09/13 02:12:59 aa1 tio_set_flow_control( HARD ) > > 09/13 02:12:59 aa1 print welcome banner (/etc/issue) > > 09/13 02:12:59 aa1 getlogname (AUTO_PPP), read:[0d] > > 09/13 02:13:01 aa1 input finished with '\r', setting ICRNL ONLCR > > 09/13 02:13:01 aa1 tio_set_flow_control( HARD ) > > 09/13 02:13:01 aa1 print welcome banner (/etc/issue) > > 09/13 02:13:01 aa1 getlogname (AUTO_PPP), read: > > ==> mgetty.ttyd1 <== > > 09/13 02:17:21 yd1 mod: cannot open line /dev/ttyd1: Device busy > > 09/13 02:17:21 yd1 open device /dev/ttyd1 failed: Device busy > > 09/13 02:17:21 yd1 cannot get terminal line dev=ttyd1, exiting: Device > > busy > > -- > > 09/13 02:17:21 yd1 mgetty: experimental test release 1.1.16-Jul05 > > 09/13 02:17:21 yd1 check for lockfiles > > 09/13 02:17:21 yd1 locking the line > > 09/13 02:17:22 yd1 mod: cannot open line /dev/ttyd1: Device busy > > 09/13 02:17:22 yd1 open device /dev/ttyd1 failed: Device busy > > 09/13 02:17:22 yd1 cannot get terminal line dev=ttyd1, exiting: Device > > busy > > > > i'm pretty sure this is some problem mgetty is having because of the > > device bond thingy in freebsd between cuaa* and ttyd* > > > > i'm kinda confused as to why i'm told to use cuaa1 in the ttys file, and i > > tell it to use cuaa1 but it still freaks out like that, turning up logging > > didn't help much :( > > > > mgetty config file: > > > > port cuaa1 > > debug 9 > > fax-id 00 00 000000 > > speed 115200 > > direct YES > > #blocking NO > > blocking YES > > port-owner uucp > > port-group uucp > > port-mode 0660 > > #toggle-dtr YES > > #toggle-dtr-waittime 500 > > data-only NO > > fax-only NO > > modem-type data > > #init-chat "" ATS0=0Q0&D3&C1 OK > > modem-check-time 3600 > > #rings 1 > > #answer-chat "" ATA CONNECT \c \r > > answer-chat-timeout 80 > > autobauding NO > > ringback NO > > ringback-time 30 > > #ignore-carrier false > > ignore-carrier true > > issue-file /etc/issue > > prompt-waittime 500 > > login-prompt @!login: > > login-time 240 > > diskspace 1024 > > notify faxadmin > > fax-owner uucp > > fax-group modem > > fax-mode 0660 > > > > (anything with a # means i've tried it both ways) > > > > please cc to me as i'm not on thie list > > > > thank you very much, > > Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com > > -- There are operating systems, and then there's FreeBSD. > > -- http://www.freebsd.org/ 3.0-current > > -- > Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <brian@OpenBSD.org> > <http://www.Awfulhak.org>; > Don't _EVER_ lose your sense of humour.... > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980914144401.19799C-100000>