Subj : New binkd setup Linux-Kubuntu 14.04 64b
To   : rick christian
From : Alan Ianson
Date : Fri Sep 16 2016 03:14 pm

Friday September 16 2016 15:32, you wrote to me:

 rc> No DEB's, or a PPA with DEB's,  no go. I don't know why, well I do,
 rc> its not on topic here, the package is so outdated in the repos.

In the case of binkd it is a simple matter to compile your own. It would be
great if the repos had upto date versions but they don't always. You may need
zlib-dev and bzip2-dev installed to build support to compress pkts on the fly.
I don't have a debian based distro at hand to look up the exact package names
but I think you can find them with the above in your standard repos. They may
or may not be installed already. On a debian based disto like the ubuntus
installing build-essential will install most of what you need to compile your
own software.

 AI>> Permissions I think. I'm not sure what user your binkd is running
 AI>> as or where it is storing inbounds or logs. Check /var/log for
 AI>> any binkd.log files and check where it is storing inbounds, you
 AI>> may have some!

 rc> I think that is a large part of the issue: init.d starts this up as
 rc> ftn:ftn, but thats not a real user... so I am think I just move it the
 rc> main user that I would use it under...since golded will need access to
 rc> that and that will run under SSH or XDMCP connection.

It might be enough to add yourself to the ftn group to have read/write
permission to the outbound/inbound.

 rc> Again, no DEB's no go! I've been through the horrors of "attempting"
 rc> to compile. It never works.

Don't even think about being intimidated by binkd. There is a readme.md (or
similar) in the binkd archive or if you get your source from cvs, it contains a
 few simple steps to compile binkd and then you are on your way. I'll outline
it for you here.

Extract the archive to the place of your choosing. Go into the root of that
directory.

cd /home/alan/binkd

Copy the files from mkfls/unix to the root binkd directory.

cp mkfls/unix/* .

Run configure.

../configure

Now run make..

make

If that was all successful you should now have a binkd in there. If that wasn't
 successful there is some easy to find solution we just need to know the
problem.

Place the binkd executible somewhere like /usr/local/bin or /usr/local/sbin and
 run it with your config.

.... Some days you're the windshield, some days you're the bug
--- GoldED+/LNX 1.1.5-b20160322
 * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

.