(religious mode on - I know some people are just as religious about "ease of use" as I am about "being standard". That's why they make source code you can build your own from :-) )
Because IMHO it's the de-facto standard UUCP implementation at this time. There are thousands of sites with experienced admins and there are many places you can get incredibly good information concerning the HDB setup.
The uucp-1.04 that's in SLS 1.02 and later has all three modes of config files built in. While I can't test it, I did "rtfm" and Ian Taylor tells me that it should work.
The search order for config files is Taylor then V2 (L.sys) then HDB.
Use the uuconv utility in /usr/lib/uucp to convert config files from one mode
to another.
If you can't wait, grab the sources for uucp and specify HAVE_BNU_CONFIG,
HAVE_V2_CONFIG *and* HAVE_TAYLOR_CONFIG in the policy.h file and type "make".
The following workaround is ugly, but it does work, if you want to run Taylor configs from binaries that don't have it built in.
"-I /usr/local/lib/uucp/config" to _every_ invocation of
whatever program in uucp packageAlso, the current Slackware has a nice setup where they separated the
config files for the various configurations into separate directories.
For example, the HDB config files would go into /usr/lib/uucp/hdb_config.
While I used to 'roll my own' here, I've been running the out-of-the-box
Slackware UUCP in HDB mode here with no problems for quite a while.
feed Any ACU,ag 38400 5551212 ogin: \c\d "" yourname word: passwd
*** conn.c.orig Mon Feb 22 20:25:24 1993
--- conn.c Mon Feb 22 20:33:10 1993
***************
*** 204,209 ****
--- 204,212 ----
/* Make sure any signal reporting has been done before we set
fLog_sighup back to TRUE. */
+ /* SMR: it seems to me if we don't care about SIGHUPS, we should clear
+ the flag before we return */
+ afSignal[INDEXSIG_SIGHUP] = FALSE;
ulog (LOG_ERROR, (const char *) NULL);
fLog_sighup = TRUE;
The SLS anonymous uucp only works in Taylor mode because it's compiled with HAVE_TAYLOR_CONFIG. If you want to do anon uucp in HDB mode, you'll have to recompile the sources with just HDB defined. Ian Taylor is considering which way to deal with this "feature".
Also, Taylor in HDB mode seems to be sensitive to white space and blank lines. To be safe, make sure that there are no blank lines or trailing spaces in the Permissions file.
Lastly, make sure that you have a file called remote.unknown in /usr/lib/uucp
and that it's *NOT* executable. See the O'Reilly+Assoc book "Managing UUCP
and USENET" for details regarding this file.
In all probability, you are attempting to use a device (/usr/lib/uucp/Devices)
that doesn't exist, or the device you've specified in the
/usr/lib/uucp/Systems file doesn't match up with any valid devices in the
Devices file.
Following this are *sanitized* versions of my working Taylor 1.05 HDB config files that you can plug in and use.
note the "ACU" in the Systems ? That tells which "port" to use in Devices
see the "scout" word in Systems ? That tells which dialer to use in Dialers.
If you had a ACU port, but none that matched the specified dialer on the same line in Systems, you'll get that message.
The following are "known-good" config files for Taylor 1.05 under Linux in HoneyDanBer mode. They work on kernels of 0.99-8 or later. All files should be in /usr/lib/uucp unless you've tweaked the sources to put the uucp library elsewhere.
If you *HAVE* put things in non-standard places, be aware that things like sendmail might get very confused. You need to ensure that all communications-related programs agree on your idea of "standard" paths.
If you're running a kernel of 0.99-7 or earlier, change "cua1" to "ttyS1".
#------------- Devices ------------- # make sure the device (cua1 here) matches your system # cua1 = COM2 # # here "scout" is the Digicom Scout Plus 19.2 modem I use # tbfast etc. is for a Telebit Trailblazer Plus modem's various speeds # ACU cua1 - 19200 scout ACU cua1 - 9600 tbfast ACU cua1 - 1200 tbslow ACU cua1 - 2400 tbmed #------------- dialers -------------- # note the setting of the Trailblazer registers "on the fly" # "scout" is a Digicom Scout Plus (Hayes-like) modem I use here # scout =W-, "" ATM0DT\T CONNECT tbfast =W-, "" A\pA\pA\pT OK ATS50=255DT\T CONNECT\sFAST tbslow =W-, "" A\pA\pA\pT OK ATS50=2DT\T CONNECT\s1200 tbmed =W-, "" A\pA\pA\pT OK ATS50=3DT\T CONNECT\s2400 #-------------- Systems ------------- # this is a very generic entry that will work for most systems # # the Any;1 means that you can call once per minute with using -f (force) # the ACU,g means force "g" protocol rather than Taylor's default "i" # fredsys Any;1 ACU,g 19200 scout5555555 "" \r ogin:--ogin: uanon word: uanon #-------------------------------- Permissions ------------------------- # Taylor UUCP in HDB mode appears to be sensitive to blank lines. # Make sure all Permissions lines are real or commented out. # # this is a anonymous uucp entry # LOGNAME=nuucp MACHINE=OTHER \ READ=/usr/spool/uucp/nuucp \ WRITE=/usr/spool/uucp/nuucp \ SENDFILES=yes REQUEST=yes \ COMMANDS=/bin/rmail # # this is a normal setup for a remote system that talks to us # note the absolute path to rnews since this site puts things # in locations that aren't "standard" # LOGNAME=fredsys MACHINE=fredsys \ READ=/usr/spool/uucp/fredsys:/usr/spool/uucp/uucppublic:/files \ WRITE=/usr/spool/uucp/fredsys:/usr/spool/uucppublic \ SENDFILES=yes REQUEST=yes \ COMMANDS=/bin/rmail:/usr/local/lib/news/bin/rnews #----------------------------------------------------------------------
The new v1.05 has an added '-z' switch to uucico that will try alternate numbers for a remote system.