I have been running FAH6.34-Linux64 via terminal. It works fine. I installed it because I couldn't get the v7 installer to work properly, using the installer package. I'm still trying to get v7 to work. Here is what happens when I try to install manually:
Selecting previously deselected package fahclient.
(Reading database ... 167534 files and directories currently installed.)
Unpacking fahclient (from fahclient_7.1.52_amd64.deb) ...
usermod: no changes
Setting up fahclient (7.1.52) ...
Adding system startup for /etc/init.d/FAHClient ...
/etc/rc0.d/K20FAHClient -> ../init.d/FAHClient
/etc/rc1.d/K20FAHClient -> ../init.d/FAHClient
/etc/rc6.d/K20FAHClient -> ../init.d/FAHClient
/etc/rc2.d/S20FAHClient -> ../init.d/FAHClient
/etc/rc3.d/S20FAHClient -> ../init.d/FAHClient
/etc/rc4.d/S20FAHClient -> ../init.d/FAHClient
/etc/rc5.d/S20FAHClient -> ../init.d/FAHClient
Starting fahclient. . .FAIL
invoke-rc.d: initscript FAHClient, action "start" failed.
Processing triggers for ureadahead ...
lewinb@Xeon:~/folding$
This is what I get when I just try to run FAHClient:
lewinb@Xeon:~/folding$ FAHClient
FAHClient: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory
lewinb@Xeon:~/folding$
But I have other things installed that use ssl... and shouldn't dpkg have picked that up, as a dependency?
This is the log for dpkg, starting with removal of the previous (non-working) v7 install:
2012-04-11 21:17:13 startup packages remove
2012-04-11 21:17:13 status installed fahclient 7.1.52
2012-04-11 21:17:16 remove fahclient 7.1.52 <none>
2012-04-11 21:17:16 status half-configured fahclient 7.1.52
2012-04-11 21:17:16 status half-installed fahclient 7.1.52
2012-04-11 21:17:16 status triggers-pending ureadahead 0.100.0-11
2012-04-11 21:17:16 status half-installed fahclient 7.1.52
2012-04-11 21:17:19 status config-files fahclient 7.1.52
2012-04-11 21:17:19 status config-files fahclient 7.1.52
2012-04-11 21:17:19 trigproc ureadahead 0.100.0-11 <none>
2012-04-11 21:17:19 status half-configured ureadahead 0.100.0-11
2012-04-11 21:17:19 status installed ureadahead 0.100.0-11
2012-04-11 21:25:51 startup archives install
2012-04-11 21:25:54 install fahclient 7.1.52 7.1.52
2012-04-11 21:25:54 status half-installed fahclient 7.1.52
2012-04-11 21:25:54 status triggers-pending ureadahead 0.100.0-11
2012-04-11 21:25:54 status half-installed fahclient 7.1.52
2012-04-11 21:25:54 status unpacked fahclient 7.1.52
2012-04-11 21:25:54 status unpacked fahclient 7.1.52
2012-04-11 21:25:54 configure fahclient 7.1.52 7.1.52
2012-04-11 21:25:54 status unpacked fahclient 7.1.52
2012-04-11 21:25:54 status unpacked fahclient 7.1.52
2012-04-11 21:25:54 status half-configured fahclient 7.1.52
2012-04-11 21:25:56 status triggers-awaited fahclient 7.1.52
2012-04-11 21:25:56 trigproc ureadahead 0.100.0-11 0.100.0-11
2012-04-11 21:25:56 status half-configured ureadahead 0.100.0-11
2012-04-11 21:25:56 status installed fahclient 7.1.52
2012-04-11 21:25:56 status installed ureadahead 0.100.0-11
At this point I don't know where else to look for a reason, as to why it is failing. Am I correct in my understanding that "amd64" is used nowadays for *all* 64-bit processors, not just amd? I noted that the v.34 version that worked was not labeled "linux64".

