daveg@pwcs.StPaul.GOV (Dave Glowacki) (04/26/88)
In OSx 4.1, Pyramid extended 4.3BSD UUCP to include support for Telebits.
What exactly was done?
I'd really like to move our UUCP traffic over to BNU, if only to have
uucleanup, but if the Trailblazer stuff is significant, I'd probably
end up sticking with 4.3's UUCP. Is it possible to get uucleanup
to work on 4.3 UUCP files? This is the thing I'd like most from BNU,
but I don't want to mess around with it here, since we have 20-30K of
mail and 5-10Megs of news flowing through every day.
Also, are there any plans to bring in uugetty? Is the fact that you need
the att init/getty/login stuff the major reason for not including it?
--
Dave Glowacki ...!{amdahl|hpda}!bungia!pwcs!daveg daveg@pwcs.StPaul.GOVcsg@pyramid.pyramid.com (Carl S. Gutekunst) (04/27/88)
In article <4703@pwcs.StPaul.GOV> daveg@pwcs.StPaul.GOV (Dave Glowacki) writes: >In OSx 4.1, Pyramid extended 4.3BSD UUCP to include support for Telebits. >What exactly was done? OSx 4.1 ucb UUCP had the following changes related to the Telebit: - Fixed interface speed is supported. You get this in L-devices by appending the true speed after the data rate, like this: ACU ttyi47 tone 2400,19200 telebit This will pattern-match against 'ACU 2400' in L.sys, but will talk to the modem at 19200. It will also cause uucico to ignore CONNECT messages from the modem that want to change the speed, e.g.: CONNECT 2400 Without fixed interface speed in L-devices, uucico would change to 2400 when it saw this message. - The uucp protocol can be explicitly specified in L.sys, like this: pyramid Any ACU,g 19200 4155551234 ogin: When I get to it, you will also be able to specify the protocol in L-devices. But this isn't available yet. - There is a dedicated dialer for the TrailBlazer that uses slightly different modem options, and is supposed to do autobauding correctly. (It doesn't :-( so you should use fixed interface speed.) It also defaults to the 'f' proto- col, which was the only thing that worked on a TrailBlazer at the time that OSx 4.1 was shipped. (So you *want* to use the protocol specification in L.sys.) The biggest benefit is that after the connection finishes, you get a LOGFILE message that includes the modem's transfer statistics. I've found this invaluable for indentifying bad phone lines. >Is it possible to get uucleanup to work on 4.3 UUCP files? If you have source, yes. Otherwise, no. There are a number of public domain equivalents for 4.3BSD; we use package called uumailclean that we're happy with. >Also, are there any plans to bring in uugetty? Not uugetty specifically. Dialin/Out on the same line will be supported 4.3BSD style, using a separate tty device for dialin and dialout. I have no idea when this will be included, however. If you want it soon, put in an software problem report to RTOC (call the 800 number, or e-mail pyramid!bugs) and make yourself heard. The more people who bitch about it, the sooner it will get done. There are other pro/con issues of BNU vs. ucb UUCP. The BNU directory-per-site in /usr/spool/uucp/ improves performance. BNU is *much* more secure. ucb UUCP gives you call progress monitoring, so the message you see in the LOGFILE is what the modem actually reported (BUSY, VOICE, NO CONNECT, NO ANSWER, etc.). ucb UUCP has full X.25 and TCP/IP support. We have to use ucb UUCP because of X.25. Note that I call it ucb UUCP, rather than 4.3BSD UUCP. Pyramid's ucb UUCP started with 4.3BSD, and is 100% compatible with it, but has been greatly extended. I don't want people to think the 4.3BSD UUCP on their VAXen will do things like call progress monitoring, autodialing X.25, or fixed interface speed; it won't. <csg>
rsalz@bbn.com (Rich Salz) (04/28/88)
Rick Adams has stated he intends to put all useful BNU features into BSD uucp. It won't happen tomorrow, tho. :-) As Rick and Carl do lots of cooperating, I'm sure any good features Rick does will show up in Pyramid the following morning. Pyramid's UUCP is a real winner. I considered going to HoneyDanBer for Mirror Systems because of HDB's features, but came up with these arguments against them: I had little enough traffic that I didn't need the per-host C./D./D.X directories. I didn't need the snazzy security because I only allowed three commands (mail, rnews, copy) with hosts I trusted. (Oh yeah, we changed our phone numbers often, too :-) I got real good support from pyramid!csg; Err, I mean from Pyramid Corp. BNU is "good luck, sucker." BNU is real sharp, and if you're gonna poke at source it's real nice: you don't need Maalox like you do for other UUCP's. Hope you find this helpful. /rich $alz -- Please send comp.sources.unix-related mail to rsalz@uunet.uu.net.
csg@pyramid.pyramid.com (Carl S. Gutekunst) (04/28/88)
In article <675@fig.bbn.com> rsalz@bbn.com (Rich Salz) writes: >As Rick and Carl do lots of cooperating, I'm sure any good features Rick does >will show up in Pyramid the following morning. That works both ways. My enhancements -- mostly in the dialers -- are given to Rick to fold into 4.3BSD. Ricks fixes, which are more in the body of UUCP, get passed on to me, and folded into the Pyramid release when I have time. I try to run Rick's latest on my machines (Sun, Pyramid, PDP-11) to shake them down. >I considered going to HoneyDanBer for Mirror Systems because of HDB's >features, but came up with these arguments against them: > > I got real good support from pyramid!csg; Err, I mean > from Pyramid Corp. BNU is "good luck, sucker." What Rich doesn't know is that Pyramid supports BNU, as of OSx 4.1. I admit to not knowing its internals as well as 4.3BSD UUCP, but it is definitely not an unsupported shot in the dark, as it was when you had to buy it from AT&T and port it yourself. Oh, and I got a wonderfully helpful notice from Karl Fox at Morningstar; the X.25 card has a built-in UUCP dialer that we didn't even know was there. It is primitive compared to the "gpsc" dialer in ucb UUCP, but it does the basic job well and is usable from HoneyDanBer. I set up an L-devices chat script for it, and that worked just fine; Dialers would work just as well. I will supply the config information to RTOC for people who want it; requests -> pyramid!bugs. <csg>