Hey Felipe!

Aug 28 23:25 06, Felipe T. Dorado wrote to Todos:

 FTD> A point of mine has tried to install husky using the uri listed in 
 FTD> http://husky.sourceforge.net/debian
 FTD> She put the sources for Debian Sarge testing in her sources.list and 
 FTD> in Synaptic installed:

 FTD> hpt
 FTD> libfidoconf1
 FTD> fidoconf-runtime
 FTD> bsopack
 FTD> huskybase
 FTD> libsmapi2


My points use;

fidoconf-1.4-rc5.tar.gz
hpt-1.4-rc5.tar.gz
huskybase-1.4-tar.gz
msged-6.2RC1-stable-src.tgz
smapi-2.4-rc5.tar.gz

For transfers to the uplink, 1:261/38 in this case, I use ftp but binkd
will work.  Given the distance between this point and the uplink ftp is
best.  My other point 1:140/13.1 also uses the exact same setup also using
ftp but only has a few meters to reach the hub over a wired LAN (ethernet).
 The node machine has binkd but only uses that to transfer to 1:140/1 and a
few other nodes that for whatever strange reason prefer slower and buggier
transfer agents over the best transfer agent ftp.  Anyhow it all works.

 FTD> Did not find either msged nor golded available for installation.

No surprise there.  Try http://sourceforge.net/projects/husky and you
should see msged there.


 FTD> But she asks me:
 FTD> Now what do I do?
 FTD> How do I call your system?
 FTD> How do I write and read messages?

She can't do any of the above.  All the listed stuff can do is reformat
between one humanly unreadable format to another humanly unreadable format.
 Tha probably is one major reason why Fido is slipping into obscurity
except in this case the reason why is called DOS compatibity.  Look what
happened to DOS and that should tell the tale.

 FTD> ¨What is husky?  What does it do?

Without an editor, a transfer agent and at least one user, absolutely
nothing.  It just sits there.

 FTD> Does it call or poll my uplink?

No.

 FTD> No, it uses binkd which it is not a 
 FTD> dependancy.

She could use something else.  I use ftp since it is the best.  Also I use
ftp for other things so it works out best for me given that binkd and
simular programs never gets any real usage.  My nearest binkd link is
literally 100's of kms away and seldom transfers anything but fills up my
log file with zero byte transfers.  The hub for the node is 1000 kms away
and that sees actual traffic for Husky to deal with.  On the node I have

fidoconf-1.4-rc5.tar.gz
hpt-1.4-rc5.tar.gz
smapi-2.4-rc5.tar.gz
binkd-1.0.tar.gz

Everything is passthrough so no need for an editor or user.

 FTD> Does it toss? No, it uses hpt to do it and this is not a dependancy.

Yes but fidoconfig is a dependency for hpt and smapi is a dependency for fidoconfig. 

 FTD> Does it allow me to read and write messages?  No, it uses msged for 
 FTD> that but this is not included in the dependancies.
 FTD> Then, what does husky do?

Reformat between one humanly unreadable format to another humanly unreadable format.

 FTD> Has left me a bit baffled. I though the main dependencies were 
 FTD> covered in the debian packages for a point.

Obviously not.  My list gives the barebones minimum relating to Husky.

If you, or her, require a working example then feel free to ask.

Life is good,
Maurice

--- Msged/LNX 6.2.0