Date: Sat, 24 May 1997 00:54:33 +0200 (MET DST) From: Peter Cornelius <dl5bct@inss1.etec.uni-karlsruhe.de> To: "Victor A. Sudakov" <vas@vas.tomsk.su>, Gert Doering <gert@greenie.muc.de>, Frank Bartels <knarf@camelot.de> Cc: questions@freebsd.org, mgetty@muc.de Subject: Re: ? mgetty 0.99-Aug07, FreeBSD 2.2.1-RELEASE, 1&1 Skyconnect (Creatix): Problem ? Message-ID: <Pine.3.89.9705231952.A3486-0100000@inss15> In-Reply-To: <199705100634.OAA10130@vas.tomsk.su>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi there all of you, thanks a lot for the quick responses! Please excuse me not responding earlier, but my car basically broke down and I thus had a bit of a hazle with authorities consuming my leftover time. Anyways, let's get back to business. Thanks for all responses: On Sat, 10 May 1997, Victor A. Sudakov wrote: > Peter Cornelius wrote: (...) > Mgetty 0.98 in the ports collection was broken, I have Gert Doering's > letter confirming this fact. Do not know about 2.2.1-RELEASE though. (...) OOooops... I could have been going on for ages, then. But never mind as I upgraded now. And there's light at the end of the tunnel it seems. I got some responses from the modem though I'm not all 100% sure yet whether it's exactly what I want. Hang on on that topic as I want to walk through documentation again before fussing around again, but it seems to be working by now... (...) > > ___ > > ls -al /dev/modem /dev/cuaa1 > > --- > > crw-rw---- 1 uucp dialer 28, 129 May 8 16:31 /dev/cuaa1 > > lrwxr-xr-x 1 root wheel 10 May 8 13:17 /dev/modem -> /dev/cuaa0 > > (NOTE: also tried hard link with no effect) > > Are you sure the symbolic link "modem" points to the correct device? Where > is your modem - cuaa1 or cuaa0? Ooops. -- I'm sorry. I just listed the wrong cuaaX. Yes I am: $ ls -al /dev/cuaa* /dev/mo* crw-rw---- 1 uucp dialer 28, 128 May 24 00:42 /dev/cuaa0 crw-rw---- 1 uucp dialer 28, 129 May 24 00:04 /dev/cuaa1 crw-rw---- 1 uucp dialer 28, 130 Apr 1 13:34 /dev/cuaa2 crw-rw---- 1 uucp dialer 28, 131 Apr 1 13:34 /dev/cuaa3 lrwxr-xr-x 1 root wheel 10 May 12 23:29 /dev/modem -> /dev/cuaa0 lrwxr-xr-x 1 root wheel 10 May 12 23:29 /dev/mouse -> /dev/cuaa1 (...) > > --- > > /etc/ttys > > --- > [...] > > # Serial terminals > > ttyd0 "/usr/libexec/getty std.9600" unknown off secure > > ttyd1 "/usr/libexec/getty std.9600" unknown off secure > > ttyd2 "/usr/libexec/getty std.9600" unknown off secure > > ttyd3 "/usr/libexec/getty std.9600" unknown off secure > > I would advise you to remove getty from the appropriate device and replace > it with mgetty. I have: Ok, thanks. I uncommented that now. Since I don't use it... ;-)) > #Modem on COM2 > cuaa1 "/usr/local/sbin/mgetty -x5 -n3" pc3r on insecure This one works for me so far: modem "/usr/local/sbin/mgetty" unknown on insecure > I am using mgetty 0.99.9 not from the ports collection, but the portable > version from ftp://ftp.leo.org/pub/comp/networking/communicaton/modem > > It works fine for me with a ZyXEL modem both for receiving and sending faxes > and for dial-in. I had to edit the Makefile and policy.h manually before > compiling. If you wish to use this version, I can mail you my configs. Thanks a lot for that offer! I think that it works now, but with FLOW_SOFT only so far. I might try FLOW_HARD later on, but right now I will better go to bed, I think ;-)) On Sat, 10 May 1997, Gert Doering wrote: > Frank Bartels wrote: > > You, Gert Doering wrote: > > > > 05/09 20:06:28 dem mgetty: experimental test release 0.99-Aug07 > > ^^^ > > /dev/modem is a link to /dev/ttyd0 or whatever, isn't it? > > > > You have to use /dev/cuaa0 (...) with mgetty. > > Huh. This *could* be a reason (though I would have to find out *WHY*). Well, I don't understand why. But anyways, I changed FLOW_HARD to FLOW_SOFT, and now I can send and receive faxes locally. Also mgetty gets out of the way as it should when I dial out. Maybe minicom didn't use hardware flow control at all? I will have to figure that out. Stay tuned for more information on this. I want to reread some sections of mgetty's documentation before raving about again. But surely I will try FLOW_HARD again if I now find out that everything is working. Will have to monitor that for a while, though, I suppose. > > > I *know* that mgetty works just fine under FreeBSD, as one of my friends > > > runs a FreeBSD machine with about 20 modems on it, all with mgetty... > > Yes, I still do. :) And I still have just 35 serial ports. :) > > 35??? How did you do that? > > > FreeBSD with mgetty really rox and works stable for years (yes, > > three years!) here... > > Whoa! > > SCO and mgetty rocks as well :)) ... longer than three years even... from > my archives: > > 18415 Mar 06 1993 /pub/unix.comm/mgetty01.tpz > [..] > 32593 May 02 1993 /pub/unix.comm/mgetty07.tpz > 35022 Jun 08 1993 /pub/unix.comm/mgetty08.tpz > 36470 Jun 25 1993 /pub/unix.comm/mgetty09.tpz Well, folks, that's what I expect from it. I'd like to make it work right now and not to touch it for the next, say... century ? :-)=) On Sat, 10 May 1997, Gert Doering wrote: > yes, this looks very similar. Did you find a "final followup" to it, > stating the solution to the problem? Maybe its a generic FreeBSD thing > that just hasn't found its way into my head yet... Not as yet. I will notify you, if I get down to looking for it. I included Cs:s to questions@freebsd.org and mgetty@muc.de. If anyone doesn't like this please say so. So that's all for now. We have visitors this weekend, so the next response might delay a bit as well. Please don't be bothered... saludos, chao, Peter. +-------------------------------------------------------------------------+ | vy 73, 55 de dl5bct@db0fho.#nds.deu.eu (ax.25) | | Peter Cornelius dl5bct@db0fho.ampr.org (ampr) | | dl5bct * vk2cpc dl5bct@inss1.etec.uni-karlsruhe.de (internet) | | <A HREF="http://inss1.etec.uni-karlsruhe.de/~dl5bct/">click here !</A> | +-------------------------------------------------------------------------+
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.3.89.9705231952.A3486-0100000>