I'm kind of new to Linux, or my Pi uinit. I want to install a BinkD mailer on it... Does anyone have the instructions as to how to do this kicking around somewhere??
Hi Ib!
16 Sep 2018 07:16, from Ib Joe -> All:
I'm kind of new to Linux, or my Pi uinit. I want to install a BinkD
mailer on it... Does anyone have the instructions as to how to do
this kicking around somewhere??
Make sure you have build-essential installed (compiler, make, etc.)
Then download the source and compile.
If you encounter issues post them here.
CU, Ricsi
I just installesd build-essential and .... I will get some help on the compile >deal. I am so new at this I want to have no issues...
I just installesd build-essential and .... I will get some help on the
compile deal. I am so new at this I want to have no issues...
If you are worried about the compile not going well, you can get the actual release version by doing an apt-get:
apt-get install binkd
As the Pi runs a debian derivative, and there is a debian package available, that is the easier way.
I was able to install it that way initially on my pi, as well as another debian system. One is now running a newer version that I compiled from source. I forget which is which because they both work just fine. You just have to be sure to get the config file, and file permissions, right. The passwords in the config file, too, of course.
One thing to remember is that, if you install it via apt, the default behavior is to run as a daemon. So, if you try to start it from the command line it could bomb because it is already running.
On Sun, 16 Sep 2018 07:16:53 +1200, Ib Joe wrote:
I'm kind of new to Linux, or my Pi uinit. I want to install a BinkD
mailer on it... Does anyone have the instructions as to how to do this
kicking around somewhere??
Thanx :)
IB Joe AKA Joe Schweier SysOp of Joe's Computer & BBS Since 1991
joesbbs.com
It is in the std repository so from the comand line try
sudo apt-get install binkd
Hello Ib!
This is how I do it.
Run the following commands on your Pi (in Terminal if you use GUI or just in the remote SSH console):
sudo apt install git build-essential
This is the frustrating part, for me anyway, in learning Linux is.... well..
I may have ephed things up. I did run apt-get install... it ran... I looked everywhere and couldn't find it. tried the second way, building it via source... it built it... somewhere... Can't find it. I have a local guy/friend I know who'll dig me out of this mess.
I did run apt-get install... it ran... I looked everywhere and
couldn't find it.
I did run apt-get install... it ran... I looked everywhere and
couldn't find it.
An "apt-get update" will update the indices, so that it will find it.
i know this is old, now, but joe was saying that it installed but he
has no clue where... he has/had the same problem with compiling it and
not knowing where the binaries were put in the directory tree...
i know this is old, now, but joe was saying that it installed but he
has no clue where... he has/had the same problem with compiling it
and not knowing where the binaries were put in the directory tree...
If you are compiling yourself, then simply look into the makefile.
On 10-10-18 09:58, mark lewis wrote to Richard Menedetter <=-
FWIW: this is one of the main reasons why we use "mc" (aka midnight commander) on all *nix systems... it just makes it much easier to be
nosey and go looking where things are and what they contain...
@MSGID: <5BBE84C1.190.binkd@capitolcityonline.net>
@REPLY: <5BBE5AC5.189.binkd@capitolcityonline.net>
On 2018 Oct 10 19:55:22, you wrote to me:
i know this is old, now, but joe was saying that it installed but he
has no clue where... he has/had the same problem with compiling it
and not knowing where the binaries were put in the directory tree...
If you are compiling yourself, then simply look into the makefile.
true but he doesn't know that or at least he didn't when he wrote his post... he's a freshly born newbie when it comes to linux stuff... he
can raise his head to look around and might, by now, be able to scoot around on his belly but hasn't figured out how to crawl, yet... much
less walk or run ;)
FWIW: this is one of the main reasons why we use "mc" (aka midnight
commander) on all *nix systems... it just makes it much easier to be
nosey and go looking where things are and what they contain...
'find' works pretty well too. :)
find -name <filename>
On 10-10-18 09:58, mark lewis wrote to Richard Menedetter <=-
FWIW: this is one of the main reasons why we use "mc" (aka midnight
commander) on all *nix systems... it just makes it much easier to be
nosey and go looking where things are and what they contain...
'find' works pretty well too. :)
find -name <filename>
:)
Linux most likely has a BETTER WAY, but I'm writing this idea of mine that with some Linux'ey modification(s) may be of help to someone wanting to
see where a File is stored on their Linux system.
On 10-11-18 00:16, mark lewis wrote to Tony Langdon <=-
'find' works pretty well too. :)
it does if you know it exists and how to use it ;)
find -name <filename>
-iname would be better because of case sensitivity and not knowing the case of a file... also using "-type f" so you don't end up finding directories when you want files only...
find . -type f -iname "*.foo"
On 10-11-18 07:15, Joacim Melin wrote to Tony Langdon <=-
find -name <filename> -print to actually see the results. :)
find -name <filename> -print to actually see the results. :)
I've never had to use -print. :)
FWIW: this is one of the main reasons why we use "mc" (aka midnight
commander) on all *nix systems... it just makes it much easier to be
nosey and go looking where things are and what they contain...
'find' works pretty well too. :)
find -name <filename>
:)
find -name <filename> -print to actually see the results. :)
On Oct 11, 2018, at 07:19, mark lewis (1:3634/12.73)<mark.lewis@p73.f12.n3634.z1.fidonet> wrote:
On 2018 Oct 11 07:15:22, you wrote to Tony Langdon:it
FWIW: this is one of the main reasons why we use "mc" (aka midnight ml>>> commander) on all *nix systems... it just makes it much easier to be ml>>> nosey and go looking where things are and what they contain...
'find' works pretty well too. :)
find -name <filename>
:)
find -name <filename> -print to actually see the results. :)
-print is the default... i've never used it and always see the results ;)
)\/(ark
Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin'
wrong...
... Is it further to Boston, or by bus?
---
* Origin: (1:3634/12.73)
On 10-11-18 13:31, Wilfred van Velzen wrote to Tony Langdon <=-
I've never had to use -print. :)
It's the default if you don't specify any other output options, in the implementations of find that I know...
One thing to remember is that, if you install it via apt, the default behavior is to run as a daemon. So, if you try to start it from the command line it could bomb because it is already running.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,027 |
Nodes: | 17 (0 / 17) |
Uptime: | 62:22:58 |
Calls: | 502,334 |
Calls today: | 2 |
Files: | 100,779 |
D/L today: |
10,841 files (1,021M bytes) |
Messages: | 300,075 |