Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.vbc.net!samba.rahul.net!rahul.net!a2i!news.PBI.net!news.mathworks.com!newsfeed.internetmci.com!netnews.nwnet.net!symiserver2.symantec.com!usenet From: tedm@agora.rdrop.com Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Trouble w/ UUCP: ``Timed out when setting MIN to 1; retrying'' Date: 8 Sep 1996 10:53:54 GMT Organization: Symantec Corporation Lines: 35 Message-ID: <50u8k2$r8m@symiserver2.symantec.com> References: <87u3tc2h45.fsf@pippin.jblhome.ping.dk> <8791amjd06.fsf@pippin.jblhome.ping.dk> Reply-To: tedm@agora.rdrop.com NNTP-Posting-Host: 198.6.34.2 X-Newsreader: IBM NewsReader/2 v1.2.5 In <8791amjd06.fsf@pippin.jblhome.ping.dk>, jacob@jblhome.ping.dk (Jacob Bohn Lorensen) writes: >>>>>> "tedm" == tedm <tedm@agora.rdrop.com> writes: > tedm> First, Taylor UUCP seems to do a "speed mode set" or some > tedm> such practically between every byte, and this upsets some > tedm> cloney buffered serial port chips. > >What puzzles me, though, is that I used Taylor UUCP with absolutely >*no problems at all* with the same hardware running Linux. I have had I'm sorry I wasn't more clear. The problem is in the sio.c driver interaction with the hardware. Patching the UUCP source merely avoids tickling the particular FreeBSD driver/hardware combination that activates the bug. Of course, I am only tossing out some wild guesses to point you in _a_ direction, I can think of lots more reasons why the problem I mentioned is NOT the cause of your problems. However, it is certainly worth a shot. In these hardware matters with FreeBSD I came to the conclusion a while back that it is usually more effective to swap hardware with a different machine than to spend time attempting to modify the source code. (which frequently introduces more bugs anyway) Of course, there are exceptions such as the ft driver that are so awful that you would have to work to make them badder. Besides all that, used 14.4K internal modems are cheap and plentiful, so you aren't that bad off. There's lot of people out there with very expensive video boards right now who are SOL and hating it, a bunch of them all were yelling about it for a few weeks there. (now there's an attitude, reward the manufacturers who don't support the product by buying their unsupported hardware! With that logic, I guess that all the WInblows people who are buying supported video cards really want FreeBSD to succeed really bad!! That's sure to make everyone else put FreeBSD support high on the priority list!!!) I suppose my attitude is not the most helpful for the sake of the code, but then again, _my machines_, _ are running_. :-) :-) :-)