Hello Wilfred,

How's the linux port coming along? I've noticed you've been testing it for a few months or more now.

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Hi Nicholas,

On 2017-07-22 09:27:40, you wrote to All:

How's the linux port coming along? I've noticed you've been testing it
for a few months or more now.

That's right. In my configuration the FMail and FTools modules are running quite stable now. The FConfig module, because of the screen interaction hasn't been converted yet. I'm still using the windows module for that. But I made it so that the linux and windows version can use the same configuration files. Dos/Windows drive letters in the paths are converted in the linux version to a linux path with a command line option. I haven't been too active on the development front for the last 2 months or so, except for bugs that popped up. Even fixed some decades old bugs, that now showed itself because of the different compiler on linux. ;)

I'm kind of ready for a public beta test, except maybe for creating make files (probably will use cmake for that), so it's easier for beta testers to build the modules. I'm now using the http://www.codeblocks.org/ ide for building the modules...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hello,

On Sun, 23 Jul 2017 14:03:30 +0200, Wilfred Van Velzen -> Nicholas Boel wrote:

That's right. In my configuration the FMail and FTools modules are running quite stable now. The FConfig module, because of the screen interaction hasn't been converted yet. I'm still using the windows
module for that. But I made it so that the linux and windows version can use the same configuration files. Dos/Windows drive letters in the paths are converted in the linux version to a linux path with a command line option. I haven't been too active on the development front for the last
2 months or so, except for bugs that popped up. Even fixed some decades old bugs, that now showed itself because of the different compiler on linux. ;)

Awesome!

I'm kind of ready for a public beta test, except maybe for creating make files (probably will use cmake for that), so it's easier for beta
testers to build the modules. I'm now using the http://www.codeblocks.org/ ide for building the modules...

Understood. I just set up a clean 64bit ArchlinuxARM on my other raspi3. Let me
know when you're ready! ;)

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Hi! Wilfred,

In a msg of Mon, 24 Jul 17, Nicholas Boel wrote to you:

Understood. I just set up a clean 64bit ArchlinuxARM on my
other raspi3. Let me know when you're ready! ;)

On the other end of the scale, I have a test bed Puppy (linux v2.6.x.x) VirtualBox waiting while I'm working slowly through an FM config in an old XP VirtualBox. :)

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Nicholas,

On 24 Jul 17 21:02, Nicholas Boel wrote to Wilfred van Velzen:
about: "Status check":

I'm kind of ready for a public beta test, except maybe for creating
make files (probably will use cmake for that), so it's easier for
beta testers to build the modules. I'm now using the
http://www.codeblocks.org/ ide for building the modules...

Understood. I just set up a clean 64bit ArchlinuxARM on my other
raspi3. Let me know when you're ready! ;)

Arm... Interesting! ;)

I'm already compiling for a 64 bit target. But I don't know what other differences there might exist between the arm and intel architectures that might cause problems?

Does this machine have a gui environment? (So you could use codeblocks)

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hi Paul,

On 25 Jul 17 12:21, Paul Quinn wrote to Wilfred Van Velzen:
about: "Status check":

Understood. I just set up a clean 64bit ArchlinuxARM on my
other raspi3. Let me know when you're ready! ;)

On the other end of the scale, I have a test bed Puppy (linux v2.6.x.x) VirtualBox waiting while I'm working slowly through an FM config in an old XP VirtualBox. :)

Do those two virtual box's use common drive space? (Then you're ready ;))

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hi! Wilfred,

On Tue, 25 Jul 17, you wrote to me:

On the other end of the scale, I have a test bed
Puppy (linux v2.6.x.x) VirtualBox waiting while I'm
working slowly through an FM config in an old XP VirtualBox. :)

Do those two virtual box's use common drive space? (Then
you're ready ;))

Nope. Na'er the twain meets, except via IP. OTOH, one VM has a drive letter, a colon, and path(s) with slants thusly "\", while the other has the same path(s) with "/" slants. A simple command-line argument will fix that, you say... ;-)

While I have your attention: how much RAM would be recommended for Fmail/linux?
(The intended working Puppy vBox has been humming for six years with 256Mb, running binkD, CM II, GoldEd and JamNNTPd, and, rarely ever uses half of it.) Too early to say yet? Then say so. :)

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Paul,

On 25 Jul 17 17:18, Paul Quinn wrote to Wilfred Van Velzen:
about: "Re: Status check":

On the other end of the scale, I have a test bed
Puppy (linux v2.6.x.x) VirtualBox waiting while I'm
working slowly through an FM config in an old XP VirtualBox. :)

Do those two virtual box's use common drive space? (Then
you're ready ;))

Nope. Na'er the twain meets, except via IP. OTOH, one VM has a drive letter, a colon, and path(s) with slants thusly "\", while the other has the same path(s) with "/" slants. A simple command-line argument will fix that, you say... ;-)

I said that wrong. It's an environment variable you have to set. ;)
If that is set the drive letter plus colon is replaced with the contents of the
environment variable and "\"'s are converted to "/"'s in the configuration paths.

However FConfigW32 checks and creates paths when you configure them, so it would be much easier if it does that on the "shared" drive were the real files exist. So you don't have to create them by hand on the linux drive, and copy over the configuration files, with the chance you make mistakes, every time you
change something in the config.

While I have your attention: how much RAM would be recommended for Fmail/linux? (The intended working Puppy vBox has been humming for six years with 256Mb, running binkD, CM II, GoldEd and JamNNTPd, and, rarely ever uses half of it.) Too early to say yet? Then say so. :)

FMail uses the most memory when it calls the JAMmaint function. It does that when messages are tossed into a Jam area, and you have 'Update reply chains' configured to 'Yes', or when the 'FTools Maint' command is used. It will at least use twice as much memory as the combined size of the 4 files that make up
a Jam area. So memory usage will depend on your largest Jam area.

Everything else is in the kilobyte range or maybe lower megabyte range, so more
or less neglectable, I suspect, because I've never measured this. ;)

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hi! Wilfred,

On Tue, 25 Jul 17, you wrote to me:

A simple command-line argument will fix that,
you say... ;-)

I said that wrong. It's an environment variable you have
to set. ;)

No problem. I can do them too.

If that is set the drive letter plus colon is replaced with
the contents of the environment variable and "\"'s are
converted to "/"'s in the configuration paths.

Ah-huh. Sweet.

However FConfigW32 checks and creates paths when you
configure them, so it would be much easier if it does that
on the "shared" drive were the real files exist. So you
don't have to create them by hand on the linux drive, and
copy over the configuration files, with the chance you
make mistakes, every time you change something in the
config.

Mistakes... nah, ain't gonna happen. I'm a profeesioanl anatuer. ;-)

FMail uses the most memory when it calls the JAMmaint
function. It does that when messages are tossed into a Jam
area, and you have 'Update reply chains' configured to
'Yes', or when the 'FTools Maint' command is used. It will
at least use twice as much memory as the combined size of
the 4 files that make up a Jam area. So memory usage will
depend on your largest Jam area.

Not a problem. The biggest area currently is BinkD, at ~20Mb. There again, I'll be starting off the Fmail/Linux environment from scratch.

Everything else is in the kilobyte range or maybe lower
megabyte range, so more or less neglectable, I suspect,
because I've never measured this. ;)

:) Nice to know. Thank you, kindly.

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Paul,

On 2017-07-25 19:48:00, you wrote to me:

FMail uses the most memory when it calls the JAMmaint
function. It does that when messages are tossed into a Jam
area, and you have 'Update reply chains' configured to
'Yes', or when the 'FTools Maint' command is used. It will
at least use twice as much memory as the combined size of
the 4 files that make up a Jam area. So memory usage will
depend on your largest Jam area.

Not a problem. The biggest area currently is BinkD, at ~20Mb.

Mine too, at 30Mb. Probably because of the weekly faq post, because it isn't the busiest area...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hello,

On Tue, 25 Jul 2017 08:40:40 +0200, Wilfred Van Velzen -> Nicholas Boel wrote:

Arm... Interesting! ;)

I'm already compiling for a 64 bit target. But I don't know what other differences there might exist between the arm and intel architectures that might cause problems?

I don't know exactly, but husky stuff, golded, and other things all compiled without issue. I do believe there was a small issue or two that was fixed early
on with Synchronet, and I had to contact a couple authors with my compile errors on a couple other pieces of software.

I'm guessing if there's a lot of intel specific code in it, the more problems there will be. ;)

Does this machine have a gui environment? (So you could use codeblocks)

Not at the moment, and I wasn't really planning on it. However, if it were completely necessary, (as in to compile on ARM because you don't have access to
it) it's not hard at all to install xorg and fluxbox.

Let's just say I would much rather use Makefiles, but if that is not possible at the moment.. I can suffer a bit. ;)

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Hi Nicholas,

On 25 Jul 17 15:49, Nicholas Boel wrote to Wilfred van Velzen:
about: "Status check":

Arm... Interesting! ;)

I'm already compiling for a 64 bit target. But I don't know what
other differences there might exist between the arm and intel
architectures that might cause problems?

I don't know exactly, but husky stuff, golded, and other things all compiled without issue. I do believe there was a small issue or two that was fixed early on with Synchronet, and I had to contact a couple authors with my compile errors on a couple other pieces of software.

It's already compiling with a current gnu compiler, without errors and warnings. So I don't expect many of those.

I'm guessing if there's a lot of intel specific code in it, the more problems there will be. ;)

I try not to write code that's specific for any target. But it still contains a
lot of decades old legacy code I never touched. So you never know what hidden problems are lurking... ;)

Does this machine have a gui environment? (So you could use
codeblocks)

Not at the moment, and I wasn't really planning on it. However, if it were completely necessary, (as in to compile on ARM because you don't have access to it) it's not hard at all to install xorg and fluxbox.

Let's just say I would much rather use Makefiles, but if that is not possible at the moment.. I can suffer a bit. ;)

It shouldn't be too difficult to create the make files, but I don't know when they will be finished, so if you want to start compiling today, that's your only option. ;)

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hello,

On Wed, 26 Jul 2017 08:43:36 +0200, Wilfred Van Velzen -> Nicholas Boel wrote:

It's already compiling with a current gnu compiler, without errors and warnings. So I don't expect many of those.

I haven't had to worry about too many issues. Only a couple minor things. Off the top of my head, Teamspeak doesn't offer an ARM version of their server (for
gaming, which is hardly used any more anyways, so it doesn't really matter in the long run), then Jon Justvig's "Legion" door game as well as Usurper wouldn't compile due to a ton of Intel code. I got Usurper to compile by removing the Intel specific code, but that made the game very unstable and unusable. Synchronet had some compiling errors, and when reported were fixed right away.

Otherwise, I haven't had any issue with setting up binkd/golded/husky type stuff. So I don't see any major problems as long as it doesn't have a ton of Intel related stuff.

I try not to write code that's specific for any target. But it still contains a lot of decades old legacy code I never touched. So you never know what hidden problems are lurking... ;)

True. And the only way to find out is to jump in! ;)

Let's just say I would much rather use Makefiles, but if that is not
possible at the moment.. I can suffer a bit. ;)

It shouldn't be too difficult to create the make files, but I don't know when they will be finished, so if you want to start compiling today, that's your only option. ;)

I'm sitting on a barebones 64bit ArchlinuxARM install that I'm not 100% sure exactly what I want to do with it yet. I do know I want to switch my Synchronet
BBS over to Mystic at some point, but there's no 64bit version available yet. I
could use the 32bit version available for the raspi3, but that would totally defeat the purpose of the 64bit build. ;)

Still tossing around ideas at the moment. GUIs on the raspi3 makes my single core AMD 3700+ seem fast, which is why I'm trying to avoid it at all costs. As a console server, it definitely keeps up with all the tasks I've pushed at it. It's just that damn resource intensive GUI that drags it down.

I've gone so far as trying out LXDE, XFCE, Linux Mint, Ubuntu (Cinnamon), and even Fluxbox on this thing when I was using it as a media server.. and I don't have one good comment about the performance once that GUI is added. ;(

So, I guess for now, keep me near the top of the list. If makefiles happen before I find a solution, great.. if not.. I may see about running QEMU on my Windows desktop with an emulated version of the OS I'm using on the raspi3 to do these tasks, as I would assume it would be a lot faster on a 6-core Intel with 16gb ram, even if it is emulated.

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Hi Nicholas,

On 26 Jul 17 16:41, Nicholas Boel wrote to Wilfred van Velzen:
about: "Status check":

then Jon Justvig's "Legion" door game as well as Usurper wouldn't
compile due to a ton of Intel code. I got Usurper to compile by
removing the Intel specific code,

Can you give an exampleof "Intel specific code"? I'm still wondering what you mean by that exactly. ;)

I've gone so far as trying out LXDE, XFCE, Linux Mint, Ubuntu
(Cinnamon), and even Fluxbox on this thing when I was using it as a
media server.. and I don't have one good comment about the performance once that GUI is added. ;(

It's probably the lack of memory. Didn't you say it "only" has 256 MB? ;)

So, I guess for now, keep me near the top of the list. If makefiles
happen before I find a solution, great..

Makefiles are on the top of my to-do list. ;)


Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hi! Wilfred,

On 07/27/2017 04:25 PM, you wrote to Nicholas Boel:

I've gone so far as trying out LXDE, XFCE, Linux Mint, Ubuntu
(Cinnamon), and even Fluxbox on this thing when I was using it as a
media server.. and I don't have one good comment about the
performance once that GUI is added. ;(

It's probably the lack of memory. Didn't you say it "only" has 256 MB? ;)

That was me. I was speaking of my Puppy Linux vBox system, which is the intended target system (currently using CM II). However initial source compiling tests will be conducted on a non-Fido Puppy with 512Mb RAM; I call it
a 'shadow' system, as it will do nothing more than process "as-yet-unprocessed"
inbound mail passed to it by the current CM II system.

OTOH, I'm wondering if Nick tried the Pi-3 release of Puppy.[shrug]
It's a GUI OS with user apps; disk image is 360Mb. (When other Puppy versions run from CD, USB and [I presume] micro-SD, the entire OS loads into RAM. I haven't looked but the Pi-3 version will probably be the same.) Anyway... that's for him to try if he wants.

So, I guess for now, keep me near the top of the list. If makefiles
happen before I find a solution, great..

Makefiles are on the top of my to-do list. ;)

Mmm... I was looking at that this afternoon. You are quite welcome to complete
that first. :)

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Hello,

On Thu, 27 Jul 2017 08:25:54 +0200, Wilfred Van Velzen -> Nicholas Boel wrote:

Can you give an exampleof "Intel specific code"? I'm still wondering
what you mean by that exactly. ;)

The Usurper sources are at usurper.info. Take a look for yourself, as I'm not a
coder but there were plenty of lines with "intel" directly in the code. That's all I can really do to describe it.

It's probably the lack of memory. Didn't you say it "only" has 256 MB? ;)

128mb storage on a microSD card, but 2gb ram with a quad core processor.

So, I guess for now, keep me near the top of the list. If makefiles
happen before I find a solution, great..

Makefiles are on the top of my to-do list. ;)

Great! ;)

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Hi Nicholas,

On 27 Jul 17 15:35, Nicholas Boel wrote to Wilfred van Velzen:
about: "Status check":

Can you give an exampleof "Intel specific code"? I'm still wondering
what you mean by that exactly. ;)

The Usurper sources are at usurper.info. Take a look for yourself, as I'm not a coder but there were plenty of lines with "intel" directly in the code. That's all I can really do to describe it.

I've looked at the latest release 0.24 source code from 2 years ago, and the pre-release version. They have exactly 1 line with 'intel':

{$asmmode intel}

(And I'm not sure what that does exactly.)

The 0.23f and 0.20e (I haven't looked at all the versions inbetween). They have
none.

Anyway, this is pascal, you can't really compare that with the C sources of FMail!

The original code of FMail did however contain some assembler code, which of course is intel specific, and DOS specific interrupt calls. They have all been removed in the past 10 years since I took over from Folkert.

It's probably the lack of memory. Didn't you say it "only" has 256
MB? ;)

128mb storage on a microSD card, but 2gb ram with a quad core processor.

128mb? Do they still make them that small? ;)


Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hello,

On Fri, 28 Jul 2017 08:31:42 +0200, Wilfred Van Velzen -> Nicholas Boel wrote:

I've looked at the latest release 0.24 source code from 2 years ago, and the pre-release version. They have exactly 1 line with 'intel':

{$asmmode intel}

(And I'm not sure what that does exactly.)

Yeah that sounds like you're on the right track. I had to ditch quite a bit of that assembler code, too.. which caused the code to compile, but with some major problems in the game itself. Since I didn't really know what I was doing,
I stopped there and left it alone.

128mb? Do they still make them that small? ;)

GB, of course.

Regards,
Nick

.... "Не знаю. Я здесь только работаю."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Hello Wilfred,

On Thu Jul 27 2017 08:25:54, Wilfred van Velzen wrote to Nicholas Boel:

So, I guess for now, keep me near the top of the list. If
makefiles happen before I find a solution, great..

Makefiles are on the top of my to-do list. ;)

If you aren't going to be able to get to the makefiles for a bit, you might as well give me some instructions on how to go about the codeblocks route. Is it just as easy as installing a GUI, installing codeblocks, and grabbing the FMail
sources from sourceforge? I already have gcc 7.1.1 installed.

I've realized that with my aarch64 install there is no easy way to make it multilib. So there goes any of my other plans at the moment. Instead, I can give this a trial and see where it gets me.

Is there any hiccups in compiling for 64bit Linux at the moment (obviously the ARM support may bring in it's own problems, but besides that..)?

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi Nicholas,

On 03 Aug 17 20:14, Nicholas Boel wrote to Wilfred van Velzen:
about: "Status check":

So, I guess for now, keep me near the top of the list. If
makefiles happen before I find a solution, great..

Makefiles are on the top of my to-do list. ;)

If you aren't going to be able to get to the makefiles for a bit,

Once I start on it, it shouldn't take that long. But I haven't worked on FMail for a couple of weeks now...

you might as well give me some instructions on how to go about the codeblocks route. Is it just as easy as installing a GUI, installing codeblocks, and grabbing the FMail sources from sourceforge?

It should be, and maybe adapt some paths in the project file to your system...

I used the Windows codeblocks project files for the linux version to start with, and the changes were minimal. So going from one linux distribution to the
other should be easy...

I already have gcc 7.1.1 installed.

I'm using 4.8.5, so I don't know how it will compile with this newer compiler...

Is there any hiccups in compiling for 64bit Linux at the moment

Not that I'm aware of. The version I'm using is a 64bit compile. And for the functionality I'm using on my system it works flawless...

(obviously the ARM support may bring in it's own problems, but besides that..)?

Obviously. ;)

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hello Wilfred,

On Fri Aug 04 2017 08:40:34, Wilfred van Velzen wrote to Nicholas Boel:

Makefiles are on the top of my to-do list. ;)

If you aren't going to be able to get to the makefiles for a bit,

Once I start on it, it shouldn't take that long. But I haven't worked
on FMail for a couple of weeks now...

That will eventually be the route I go when they're available, as I'd like to eventually set this up on a GUI-less system. I've installed Ubuntu Mate 32bit on my other raspi3 for now just to play with the FMail code. Once I'm able to compile it for aarch32 I will most likely re-install 32bit Archlinux.

It should be, and maybe adapt some paths in the project file to your system...

That's a given.

I used the Windows codeblocks project files for the linux version to
start with, and the changes were minimal. So going from one linux distribution to the other should be easy...

Okay.

I already have gcc 7.1.1 installed.

I'm using 4.8.5, so I don't know how it will compile with this newer compiler...

Bleh. So far behind the times. ;)

Is there any hiccups in compiling for 64bit Linux at the moment

Not that I'm aware of. The version I'm using is a 64bit compile. And
for the functionality I'm using on my system it works flawless...

Ok, good to know. I had some issues trying to get a GUI installed on the 64bit Archlinux install, and it seemed like some programs, while they may have been ported to install properly on aarch64, didn't work as expected. Running "lspci"
on my 32bit raspi3 would at least give an error that it can't open /proc/bus/pci. The 64bit version said absolutely nothing - and the 64bit version is not well supported, if at all. So I think I'll stick with 32bit on those things. ;)

(obviously the ARM support may bring in it's own problems, but
besides that..)?

Obviously. ;)

Can't hurt to give it a shot though. I'll let you know if I run into any issues.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi Nicholas,

On 2017-08-04 10:46:32, you wrote to me:

I already have gcc 7.1.1 installed.

I'm using 4.8.5, so I don't know how it will compile with this newer
compiler...

Bleh. So far behind the times. ;)

Yeah, the distribution on my PC is already 1 year and a couple of months old. ;)

(obviously the ARM support may bring in it's own problems, but
besides that..)?

Obviously. ;)

Can't hurt to give it a shot though. I'll let you know if I run into any issues.

I am interested! ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Fri Aug 04 2017 19:00:32, Wilfred van Velzen wrote to Nicholas Boel:

Yeah, the distribution on my PC is already 1 year and a couple of
months old. ;)

Can't hurt to give it a shot though. I'll let you know if I run
into any issues.

I am interested! ;)

So far, both FMail and FTools compiled fine. All I had to do was change "-mtune=generic" to "-mtune=native" in the project files.

I can't get FConfig to do anything, though. Is that normal?

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello Wilfred,

On Fri Aug 04 2017 19:00:32, Wilfred van Velzen wrote to Nicholas Boel:

I am interested! ;)

You don't by chance have an fidoconfig -> fmail config generator, do you?
I'm guessing I'll have to add a ton of links manually. ;)

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello Wilfred,

On Fri Aug 04 2017 12:11:36, Nicholas Boel wrote to Wilfred van Velzen:

I can't get FConfig to do anything, though. Is that normal?

After looking a little further, it looks like you copied FConfig.cbp to FConfig-linux.cbp but haven't made modifications yet. I take it this is where you left off? ;)

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi Nicholas,

On 2017-08-04 12:11:36, you wrote to me:

Yeah, the distribution on my PC is already 1 year and a couple of
months old. ;)

Can't hurt to give it a shot though. I'll let you know if I run
into any issues.

I am interested! ;)

So far, both FMail and FTools compiled fine.

Great!

All I had to do was change "-mtune=generic" to "-mtune=native" in the project files.

Doesn't 'generic' work for the arm target? I use 'native' for my own compiles. And there is a 'native' target in the project you can switch to.

I can't get FConfig to do anything, though. Is that normal?

As said before, FConfig hasn't been converted to linux. You will have to use the windows version....

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi Nicholas,

On 2017-08-04 12:13:36, you wrote to me:

You don't by chance have an fidoconfig -> fmail config generator, do
you?

fidoconfig is Husky? But the answer is no. ;)

I'm guessing I'll have to add a ton of links manually. ;)

Start slow with 1, for testing if it works at all! ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Fri Aug 04 2017 19:54:46, Wilfred van Velzen wrote to Nicholas Boel:

So far, both FMail and FTools compiled fine.

Great!

All I had to do was change "-mtune=generic" to "-mtune=native" in
the project files.

Doesn't 'generic' work for the arm target? I use 'native' for my own compiles. And there is a 'native' target in the project you can switch
to.

No. It wasn't a valid option, so I went with the next best "generic" method. Otherwise, besides "native" there were only specific things, like "armv7" and the like.

As for the native target in the project you can switch to. I was lucky I was able to figure out how to build it. I've never used codeblocks before until this past hour. ;)

I can't get FConfig to do anything, though. Is that normal?

As said before, FConfig hasn't been converted to linux. You will have
to use the windows version....

That's what I figured after looking into it a little more. I tried getting into
it a little bit, but the first file couldn't find io.h, then when I commented that out to see where it would go next, it errored on the next file with some invalid code. So I gave up so as to not wreck anything.

I'll install the Windows version and setup a point for now to see how everything is handled and tinker with it a bit. If I like it, it may very well be replacing hpt soon.

So hurry up! :) :) :)

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello Wilfred,

On Fri Aug 04 2017 19:58:50, Wilfred van Velzen wrote to Nicholas Boel:

You don't by chance have an fidoconfig -> fmail config generator,
do you?

fidoconfig is Husky? But the answer is no. ;)

I had to ask, but figured I wouldn't be so lucky!

I'm guessing I'll have to add a ton of links manually. ;)

Start slow with 1, for testing if it works at all! ;)

Seems you've already been testing with 1 for awhile now. I may have to try 2 or
3, or 100+. ;)

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi Nicholas,

On 2017-08-04 13:05:54, you wrote to me:

All I had to do was change "-mtune=generic" to "-mtune=native" in
the project files.

Doesn't 'generic' work for the arm target? I use 'native' for my own
compiles. And there is a 'native' target in the project you can switch
to.

No. It wasn't a valid option, so I went with the next best "generic" method. Otherwise, besides "native" there were only specific things, like "armv7" and the like.

Or maybe just leave out the -mtune option. That should work too I think.

As for the native target in the project you can switch to. I was lucky
I was able to figure out how to build it. I've never used codeblocks before until this past hour. ;)

You seemed to have done fine, in such a short time span! ;)

I can't get FConfig to do anything, though. Is that normal?

As said before, FConfig hasn't been converted to linux. You will have
to use the windows version....

That's what I figured after looking into it a little more. I tried getting into it a little bit, but the first file couldn't find io.h, then when I commented that out to see where it would go next, it errored on the next file with some invalid code. So I gave up so as to not wreck anything.

If it were that simple! ... ;)

The problem is mostly in the conio library, which is dos/windows specific, for doing the text user interface. I want to replace that with ncurses, but that will take some figuring out. And I fear they are wildly different, so it wouldn't be a case of just replacing library calls...2

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi Nicholas,

On 2017-08-04 13:11:28, you wrote to me:

I'm guessing I'll have to add a ton of links manually. ;)

Start slow with 1, for testing if it works at all! ;)

Seems you've already been testing with 1 for awhile now. I may have to try 2 or 3, or 100+. ;)

I use it with my regular setup with 40+ links. But the arm target is new, so I meant arm specific testing...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Fri Aug 04 2017 21:35:52, Wilfred van Velzen wrote to Nicholas Boel:

No. It wasn't a valid option, so I went with the next best
"generic" method. Otherwise, besides "native" there were only
specific things, like "armv7" and the like.

Or maybe just leave out the -mtune option. That should work too I
think.

That's a possibility. I think the "native" option is more widely used than "generic" though. Codeblocks or gcc (5.1.1 I believe) didn't like it and suggested I use native.

As for the native target in the project you can switch to. I was
lucky I was able to figure out how to build it. I've never used
codeblocks before until this past hour. ;)

You seemed to have done fine, in such a short time span! ;)

Once I realized I originally grabbed the "CodeBlocks" tree that was Windows specific, I went back and grabbed the "linux" tree which contained the correct .cbp files I needed. Had I ran into any issues compiling fmail and ftools, though.. I'd be scratching my head a bit, I'm sure. ;)

That's what I figured after looking into it a little more. I
tried getting into it a little bit, but the first file couldn't
find io.h, then when I commented that out to see where it would
go next, it errored on the next file with some invalid code. So I
gave up so as to not wreck anything.

If it were that simple! ... ;)

I know. I had a gleam of hope in my eye, which disappeared pretty fast.

The problem is mostly in the conio library, which is dos/windows
specific, for doing the text user interface. I want to replace that
with ncurses, but that will take some figuring out. And I fear they
are wildly different, so it wouldn't be a case of just replacing
library calls...2

Meh, piece of cake. ;)

When I have some time, I'll go through FConfig (already installed on Windows) and fill in the blanks to get a config file I can copy over to the pi for some more testing.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello Wilfred,

On Fri Aug 04 2017 21:49:06, Wilfred van Velzen wrote to Nicholas Boel:

Seems you've already been testing with 1 for awhile now. I may
have to try 2 or 3, or 100+. ;)

I use it with my regular setup with 40+ links. But the arm target is
new, so I meant arm specific testing...

So far with everything I've compiled myself on the raspi3, I haven't had any different results than the linux version. Most things just needed to be re-compiled for the new architecture, but it's still linux.

Either way, I get your drift. ;)

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi! Nick,
On 08/05/2017 04:11 AM, you wrote to Wilfred van Velzen:

You don't by chance have an fidoconfig -> fmail config generator,
do you?

fidoconfig is Husky? But the answer is no. ;)

I had to ask, but figured I wouldn't be so lucky!

The best assist is importing an Areas.Bbs config. Just set up your mail options and up/down/sideways-links, and, then start the echo areas import business. Fidoonfig/hpt can do an export, can't it?

You should find as I did that the Linux file system paths are imported *intact*
into the (Win/32) area manager! 168-odd areas! That was a bonus. Since I manage some access security through group management, I just had to edit about 20 echoes to conform with agreements with three other linked systems.

I'm all set for testing. Due to my shortcomings I have to rely on others' skills with compiling from source, until it is as easy as with binkD. Grovel, grovel... :)

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Hi Nicholas,

On 2017-08-04 16:42:52, you wrote to me:

You seemed to have done fine, in such a short time span! ;)

Once I realized I originally grabbed the "CodeBlocks" tree that was

Windows

specific, I went back and grabbed the "linux" tree which contained the correct .cbp files I needed. Had I ran into any issues compiling fmail and ftools, though.. I'd be scratching my head a bit, I'm sure. ;)

I should have told you about that! But I allways forget about my current git branch. ;)

The 'codeblocks' branch is merged back into the 'master' so shouldn't be used anyways. And that should happen to the 'linux' branch too, in the future...

When I have some time, I'll go through FConfig (already installed on Windows) and fill in the blanks to get a config file I can copy over
to the pi for some more testing.

That's the way...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hello Paul,

On Sat Aug 05 2017 08:13:22, Paul Quinn wrote to Nicholas Boel:

The best assist is importing an Areas.Bbs config. Just set up your
mail options and up/down/sideways-links, and, then start the echo
areas import business. Fidoonfig/hpt can do an export, can't it?

I would think so. There's probably some perl or python script out there to whip
up an areas.bbs. Heck, I may even have it already (just looked, I do).

I just hope that it can export and import all the links without having to do so
manually. I probably have somewhere around 100, if not more. Doing that manually is the main reason I haven't switched tossers yet. ;)

You should find as I did that the Linux file system paths are imported *intact* into the (Win/32) area manager! 168-odd areas! That was a bonus. Since I manage some access security through group management,
I just had to edit about 20 echoes to conform with agreements with
three other linked systems.

That's definitely a plus. Manually having to change each and every one would be
a PITA.

I'm all set for testing. Due to my shortcomings I have to rely on
others' skills with compiling from source, until it is as easy as with binkD. Grovel, grovel... :)

You're just using Linux, right? Wilfred can probably just give you his binaries
for fmail and ftools and off you go. I had to compile for ARM (Raspberry Pi), which is really the only reason I had to do it myself, since nobody had done it
yet.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello Wilfred,

On Sat Aug 05 2017 12:04:26, Wilfred van Velzen wrote to Nicholas Boel:

I should have told you about that! But I allways forget about my
current git branch. ;)

No problem. I figured it out eventually.

When I have some time, I'll go through FConfig (already installed
on Windows) and fill in the blanks to get a config file I can
copy over to the pi for some more testing.

That's the way...

Come to find out that fconf2areasbbs.pl doesn't want to work properly (it's probably old and outdated, or possibly works with the 1.4-stable branch and not
the 1.9-current one). We'll see if I can get this going easily or not. :|

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi Nicholas,

On 2017-08-07 17:16:46, you wrote to Paul Quinn:

You're just using Linux, right? Wilfred can probably just give you his binaries for fmail and ftools and off you go.

We can at least try that. If I can make binaries that are compatible with Pauls
system, it should work...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi! Wilfred,

On 08/08/2017 04:48 PM, you wrote to Nicholas Boel:

You're just using Linux, right? Wilfred can probably just give you
his binaries for fmail and ftools and off you go.

We can at least try that. If I can make binaries that are compatible
with Pauls system, it should work...

Yes, please. Just 32-bit generic Linux 2.6.x.x, as far as I know. Though the Puppy distros are quite slim, at ~128Mb .iso images of the versions I'm running
on three VirtualBox systems. They usually lack any 'make' or gcc facilities but I do have such an environment on one system. If there's any dependency problems, they can be sorted.

Perhaps starting with whatever you're using? Just drop them off, as I will know what they are & who they're from. Or, some other arrangement?

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Hi Paul,

On 2017-08-08 18:41:27, you wrote to me:

Yes, please. Just 32-bit generic Linux 2.6.x.x, as far as I know.
Though the Puppy distros are quite slim, at ~128Mb .iso images of the versions I'm running on three VirtualBox systems. They usually lack
any 'make' or gcc facilities but I do have such an environment on one system. If there's any dependency problems, they can be sorted.

Perhaps starting with whatever you're using? Just drop them off, as I

will

know what they are & who they're from. Or, some other arrangement?

"Whatever I'm using" is 64bit, and native for my I7 processor, so that definitly won't work for you. So I'll have to whip up some 32 bit generic version, and statically linked. I'll see what I can do in one of the comming evenings...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi! Wilfred,

On Tue, 08 Aug 17, you wrote to me:

Perhaps starting with whatever you're using?

"Whatever I'm using" is 64bit, and native for my I7
processor, so that definitly won't work for you. So I'll
have to whip up some 32 bit generic version, and
statically linked. I'll see what I can do in one of the
comming evenings...

I gave up 64-bit anything after dumping Windows 8.1, and then Tahr Puppy 6.0.5 64-bit after a week; nothing made any more sense than still doing 32-bit.

Oh, and no pressure. I've got a couple of other projects 'on the boil' at the moment. Thanks for the thought.

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Paul,

On 2017-08-08 19:48:00, you wrote to me:

"Whatever I'm using" is 64bit, and native for my I7
processor, so that definitly won't work for you. So I'll
have to whip up some 32 bit generic version, and
statically linked. I'll see what I can do in one of the
comming evenings...

I gave up 64-bit anything after dumping Windows 8.1, and then Tahr Puppy 6.0.5 64-bit after a week; nothing made any more sense than still doing 32-bit.

Oh, and no pressure. I've got a couple of other projects 'on the boil' at the moment. Thanks for the thought.

It wasn't very difficult, so here it is:

http://www.vlzn.nl/fmail/files/FMail-lnx32-2.1.0.17-Beta20170808.zip

It contains the 2 executables as 32 bit versions. They are dynamically linked, because there was a problem with static linking. So if this works: great, if not I'll try something else. ;)

If you just run 'fmail' it should produce some help output...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hello Paul,

On Tue Aug 08 2017 18:41:26, Paul Quinn wrote to Wilfred van Velzen:

Yes, please. Just 32-bit generic Linux 2.6.x.x, as far as I know.
Though the Puppy distros are quite slim, at ~128Mb .iso images of the versions I'm running on three VirtualBox systems. They usually lack
any 'make' or gcc facilities but I do have such an environment on one system. If there's any dependency problems, they can be sorted.

Ick. You may not be so lucky then, unless Wilfred has a machine with a 2.6.x kernel installed still (most distros are using the 4.4.x stable kernel, or 4.9.x (32bit) or 4.12.x (64bit) latest and greatest). You really should upgrade
though. Lots of security issues have been fixed since then.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hi! Wilfred,

On 08/09/2017 06:34 AM, you wrote:

It wasn't very difficult, so here it is:

http://www.vlzn.nl/fmail/files/FMail-lnx32-2.1.0.17-Beta20170808.zip

Got it! Thank you.

It contains the 2 executables as 32 bit versions. They are dynamically linked, because there was a problem with static linking. So if this works: great, if not I'll try something else. ;)

If you just run 'fmail' it should produce some help output...

Not yet. Well, what happened was expected: on this PC, which uses a later version of Puppy, it couldn't find /lib/libc.so.6 (part of GLIBC 2.17) but I can fix that.

More on this later, once I get out of bed. :)

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Hi! Nick,

On 08/09/2017 07:50 AM, you wrote:

Yes, please. Just 32-bit generic Linux 2.6.x.x, as far as I know.

Ick. You may not be so lucky then, unless Wilfred has a machine with a 2.6.x kernel installed still (most distros are using the 4.4.x stable kernel, or 4.9.x (32bit) or 4.12.x (64bit) latest and greatest). You really should upgrade though. Lots of security issues have been fixed since then.

The current config is ensconced on its fourth Linux OS, by choice. The possibility of a fifth is not out of the question. 8-)

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Hi Nicholas,

On 08 Aug 17 16:50, Nicholas Boel wrote to Paul Quinn:
about: "Status check":

Ick. You may not be so lucky then, unless Wilfred has a machine with a 2.6.x kernel installed still (most distros are using the 4.4.x stable kernel, or 4.9.x (32bit) or 4.12.x (64bit) latest and greatest).

I'm on 4.7.5.

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hi Paul,

On 09 Aug 17 08:38, Paul Quinn wrote to Wilfred van Velzen:
about: "Linux beta":

If you just run 'fmail' it should produce some help output...

Not yet. Well, what happened was expected: on this PC, which uses a later version of Puppy, it couldn't find /lib/libc.so.6 (part of GLIBC 2.17) but I can fix that.

At least it didn't crash right away! ;)

More on this later, once I get out of bed. :)

I'll stay tuned...

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hi! Wilfred,

On 08/09/2017 04:39 PM, you wrote:

Not yet. Well, what happened was expected: on this PC, which
uses a later version of Puppy, it couldn't find /lib/libc.so.6
(part of GLIBC 2.17) but I can fix that.

At least it didn't crash right away! ;)

You're sick & twisted, just like me. I was expecting the same thing. :)

More on this later, once I get out of bed. :)

I'll stay tuned...

No improvement. I took the binaries to my test vBox, did a 'blind' install of the libc.so.6 package available for Puppy (i.e. not knowing if it was already installed). Then rebooted (eek! it's second reboot in a year!). Re-ran "./fmail[Enter]" and this time got two error lines. The first error referred to
libc.so.6 as being from GLIBC 2.7 and then the second error as for the first, above.

I suspect a glitch in your 64-bit configs but take that with a grain of salt, as I am not even a 'novice' in such things. I'm hanging out for a makefile solution, for a local build. I've already been working on solutions for my predicament since March last year. I can wait. :)

I may try another vBox of a more modern OS but that be months away...

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Hi Paul,

On 2017-08-09 18:09:11, you wrote to me:

At least it didn't crash right away! ;)

You're sick & twisted, just like me. I was expecting the same thing. :)

Part of your job as a software developper is imagining what can go wrong and adapt your code to it. So being a pesimist makes you a good developper. ;)

More on this later, once I get out of bed. :)

I'll stay tuned...

No improvement. I took the binaries to my test vBox, did a 'blind'

install

of the libc.so.6 package available for Puppy (i.e. not knowing if it was already installed). Then rebooted (eek! it's second reboot in a year!). Re-ran "./fmail[Enter]" and this time got two error lines. The first error referred to libc.so.6 as being from GLIBC 2.7 and then the second error as for the first, above.

I suspect a glitch in your 64-bit configs but take that with a grain of salt, as I am not even a 'novice' in such things. I'm hanging out for a makefile solution, for a local build. I've already been working on solutions for my predicament since March last year. I can wait. :)

I'll try building a statically linked binary again first. Maybe just ftools as that would be more simple as a test case...

I may try another vBox of a more modern OS but that be months away...

That would be better! ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi! Wilfred,

On 08/09/2017 06:27 PM, you wrote:

I suspect a glitch in your 64-bit configs but take that with a
grain of salt, as I am not even a 'novice' in such things.

It was wrong of me to suggest that. I regret saying so.

I'll try building a statically linked binary again first. Maybe just ftools as that would be more simple as a test case...

Hold that thought, mate. I have in mind to try something else in an hour or two but am stuck on this netbook. Be back soon...

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Hi Paul,

On 2017-08-09 19:00:35, you wrote to me:

I'll try building a statically linked binary again first. Maybe just
ftools as that would be more simple as a test case...

Hold that thought, mate. I have in mind to try something else in an hour or two but am stuck on this netbook. Be back soon...

I won't be trying that anyway, for at least 6 to 7 hours, when I'm home again in the evening! ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi! Wilfred,

In a msg of Wed, 09 Aug 17, I wrote to you:

I'll try building a statically linked binary again
first. Maybe just ftools as that would be more simple
as a test case...

Hold that thought, mate. I have in mind to try something
else in an hour or two but am stuck on this netbook. Be
back soon...

Just tried another host and both binaries worked! Ftools even complained about
there being no Fmail.cfg, and was 'active' for exactly 0.0020 seconds. Thank you. Now to flesh out a plan 'B'. ;-)

Am trying to deal with cold pizza...

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Paul,

On 2017-08-09 19:30:00, you wrote to me:

Hold that thought, mate. I have in mind to try something
else in an hour or two but am stuck on this netbook. Be
back soon...

Just tried another host and both binaries worked! Ftools even complained about there being no Fmail.cfg, and was 'active' for exactly 0.0020 seconds. Thank you. Now to flesh out a plan 'B'. ;-)

I'm going to send you the static test build of ftools anyway, later today. Because I would really like to know it that would work on more machines out of the box...

Am trying to deal with cold pizza...

Just nuke it! ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi! Wilfred,

On Wed, 09 Aug 17, you wrote to me:

I'm going to send you the static test build of ftools
anyway, later today. Because I would really like to know
it that would work on more machines out of the box...

Groovy. More input... mmm, reminds me of a movie.

Am trying to deal with cold pizza...

Just nuke it! ;)

I did! But all this typing is stopping me from finishing it all off, and the keyboard's getting all clagged with tomato paste. (Bear in mind that it is the
depth of winter here: just barely 10C!) Oh, woe is me...

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Paul,

On 2017-08-09 19:48:00, you wrote to me:

Am trying to deal with cold pizza...

Just nuke it! ;)

I did! But all this typing is stopping me from finishing it all off, and the keyboard's getting all clagged with tomato paste. (Bear in mind that it is the depth of winter here: just barely 10C!) Oh, woe is me...

It's the middle of summer here. But just 18.5C arround noon now. And I like it!
Much better than the hot days of 25+... ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi! Wilfred,

On Wed, 09 Aug 17, you wrote to me:

It's the middle of summer here. But just 18.5C arround
noon now. And I like it! Much better than the hot days of
25+... ;)

It was 18.5C here at 10:00, and 24.7C at 15:00. Beautiful one day, perfect the
next... they say. :)

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Paul,

On 2017-08-09 11:34:10, I wrote to you:

Just tried another host and both binaries worked! Ftools even
complained about there being no Fmail.cfg, and was 'active' for
exactly 0.0020 seconds. Thank you. Now to flesh out a plan 'B'. ;-)

0.0006 on mine ;-P

I'm going to send you the static test build of ftools anyway, later today. Because I would really like to know it that would work on more machines out of the box...

Can you test this one:

http://www.vlzn.nl/fmail/files/FTools-lnx32-static-2.1.0.17-Beta20170809.zip

If it works I can make an fmail version like this too. But it will lack the smtp function (which nobody uses probably ;))....

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi! Wilfred,

On Wed, 09 Aug 17, you wrote to me:

I'm going to send you the static test build of
ftools anyway, later today. Because I would really
like to know it that would work on more machines
out of the box...

Can you test this one:

Done! Same complaint... no config. 'Active' for 0.0014 sec. There were still
2x seti@home jobs chugging 24/7, Firefox, Tux Commander, and an RDP client running this time. No VirtualBox appliances running this time. BTW, this host
is a stock HP 110-501a; its network name is 'junkpile' after having viewed Carey Holman's unboxing/review of a similar piece of kit on EwwToob, while the box was still in-transit to me. It runs Xubuntu 14.04.3 LTS... at the moment.
:)

If it works I can make an fmail version like this too. But
it will lack the smtp function (which nobody uses probably
;))....

I've had my own for over a decade, which may be 7/10ths of the way into its second.

You have a winner, me thinks. Congratulations. Thank you.

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Paul,

On 10 Aug 17 09:52, Paul Quinn wrote to Wilfred Van Velzen:
about: "Re: Linux beta":

Can you test this one:

Done! Same complaint... no config. 'Active' for 0.0014 sec.

But no complaints about libs, so that's good if this was on the machine with the 2.6 kernel were it didn't work before?

It runs Xubuntu 14.04.3 LTS... at the moment. :)

That would be at least a 3.13 kernel if I search a bit on the internet...

If it works I can make an fmail version like this too. But
it will lack the smtp function (which nobody uses probably
;))....

I've had my own for over a decade, which may be 7/10ths of the way into its second.

??

You have a winner, me thinks. Congratulations. Thank you.

I'm not sure yet, if you tested on the right machine... ;)

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

Hi! Wilfred,

On Thu, 10 Aug 17, you wrote to me:

Done! Same complaint... no config. 'Active' for
0.0014 sec.

But no complaints about libs, so that's good if this was
on the machine with the 2.6 kernel were it didn't work
before?

Oh, that one... 'Kernal too old' & then segfaulted.

It runs Xubuntu 14.04.3 LTS... at the moment. :)

That would be at least a 3.13 kernel if I search a bit on
the internet...

And I intend it to be the new testbed here. There is one advantage: it has a running binkD. That's it.

I've had my own for over a decade, which may be
7/10ths of the way into its second.

??

More than 17 years... Pop3/Smtp server.

You have a winner, me thinks. Congratulations.
Thank you.

I'm not sure yet, if you tested on the right machine... ;)

Sorry. My focus was on plan 'B', to use this PC.

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Paul,

On 2017-08-10 20:02:00, you wrote to me:

Done! Same complaint... no config. 'Active' for
0.0014 sec.

But no complaints about libs, so that's good if this was
on the machine with the 2.6 kernel were it didn't work
before?

Oh, that one... 'Kernal too old' & then segfaulted.

And that is with the ftools static version? If so, that will end my "endeavours" to build a generic linux binary suitable for all systems. ;)

I've had my own for over a decade, which may be
7/10ths of the way into its second.

??

More than 17 years... Pop3/Smtp server.

There is no smtp server in fmail, just a function to send pkt files base64 encoded in emails...


Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi! Wilfred,

On Thu, 10 Aug 17, you wrote to me:

this was on the machine with the 2.6 kernel were it
didn't work before?

Oh, that one... 'Kernal too old' & then segfaulted.

And that is with the ftools static version?

Yes.

If so, that will end my "endeavours" to build a
generic linux binary suitable for all systems. ;)

I concur. 8-)

There is no smtp server in fmail, just a function to send
pkt files base64 encoded in emails...

Oh, I have a similar Fidonet solution for that (dunno about encoding level). That's been running for ~15 years. :)

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Paul,

On 2017-08-10 21:24:00, you wrote to me:

If so, that will end my "endeavours" to build a
generic linux binary suitable for all systems. ;)

I concur. 8-)

So my time goes into the make files (and debugging possible issues found by Nicolas ;)).

There is no smtp server in fmail, just a function to send
pkt files base64 encoded in emails...

Oh, I have a similar Fidonet solution for that (dunno about encoding level). That's been running for ~15 years. :)

And you have links that use that? I've never used this function in FMail, so I don't know how well or bad it works...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi! Wilfred,

On Thu, 10 Aug 17, you wrote to me:

So my time goes into the make files (and debugging
possible issues found by Nicolas ;)).

Yep, I'm watching. I'll get to re-configuring things here on the weekend...

There is no smtp server in fmail, just a function
to send pkt files base64 encoded in emails...

Oh, I have a similar Fidonet solution for that (dunno
about encoding level). That's been running for ~15
years. :)

And you have links that use that? I've never used this
function in FMail, so I don't know how well or bad it
works...

I have had many links using it over the years but it gets little to no use these days. But it's more than you're thinking of. It's original purpose is to provide a mailing list<-->echomail gateway, either locally-hosted echomail areas or remote groups. Netmail can be shoved through to email as well, and vice-versa.

It's called Transnet but is somewhat 'dated', from pre-1998. The distro archive is available via FREQ from -this- node as 'tn211.zip' (minus quotes). I also have the required Windows utils and the sources for the following version (mostly C, C++ and some object files).

Cheers,
Paul.

--- Paul's Win98SE VirtualBox
* Origin: Quinn's Post - Maryborough, Queensland, OZ (3:640/384)

Hi Paul,

On 2017-08-10 22:39:00, you wrote to me:

It's called Transnet but is somewhat 'dated', from pre-1998. The
distro archive is available via FREQ from -this- node as 'tn211.zip' (minus quotes). I also have the required Windows utils and the
sources for the following version (mostly C, C++ and some object
files).

It does sound a bit familiar. Was/isn't that something that irex could do?

Bye, Wilfred.

--- FMail-lnx64 2.1.0.17-B20170711
* Origin: FMail development HQ (2:280/464)

Hi! Wilfred,

On 08/10/2017 11:22 PM, you wrote:

It's called Transnet but is somewhat 'dated', from pre-1998. The
distro archive is available via FREQ from -this- node as 'tn211.zip'
(minus quotes). I also have the required Windows utils and the
sources for the following version (mostly C, C++ and some object
files).

It does sound a bit familiar. Was/isn't that something that irex could

do?

I don't know. I couldn't get iRex to run. (Which I count as a +plus+, BTW.) A close approximation could be Soupgate, though I've never used it either.

But, no-no, no. I must have had a brain-fart that late last night; I went off at a tangent that wasn't related to your Fmail function at all. I've just now twigged to what you were talking about...

Yes, I was doing similar back around the turn of the century when I was still only on dial-up, and had a point operator living in Halle, Germany. :) I think I was using a package called 'Fido 2 Internet', which encoded packets into email and decoded incoming emails back into echomail packets. (With the POP3/SMTP server I could dedicate an email address to that function.)

I think I still have the archive (FREQ-able as fd2i101.rar on my other node) but I can't open .RARs from this netbook, and I'm not getting out of bed for anyone to check it right now. ;-)

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)

Hi Paul,

On 11 Aug 17 07:53, Paul Quinn wrote to Wilfred van Velzen:
about: "Linux beta":

It's called Transnet but is somewhat 'dated', from pre-1998. The
distro archive is available via FREQ from -this- node as 'tn211.zip'
(minus quotes). I also have the required Windows utils and the
sources for the following version (mostly C, C++ and some object
files).

It does sound a bit familiar. Was/isn't that something that irex
could do?

I don't know. I couldn't get iRex to run. (Which I count as a +plus+, BTW.)

It is a long time ago, since I used irex, so it's very possible I'm wrong. ;)

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)