For the linux version, instead of using above statically linked executables, I recommend, if you have the setup/tools for it, to
download the sources with git, and compile it yourself.
For the linux version, instead of using above statically linked executables,
I recommend, if you have the setup/tools for it,
to download the sources with git, and compile it yourself.
For the linux version, instead of using above statically linked
executables, I recommend, if you have the setup/tools for it, to
download the sources with git, and compile it yourself.
See netmail...
For the linux version, instead of using above statically linked
executables, I recommend, if you have the setup/tools for it, to
download the sources with git, and compile it yourself.
Compiled in Raspberry PI3 running Debian 32bit. No problems.
Started fconfig from scratch and imported areas.bbs created from husky setup. So this fmail setup runs in parallel with husky/hpt now. Seems ok :)
Next we need fconfig to import husky config. :D
For the linux version, instead of using above statically linked
executables, I recommend, if you have the setup/tools for it, to
download the sources with git, and compile it yourself.
See netmail...
Answered. ;)
Fconfig config actually runs, but did a Segmentation fault when the
ssh session was 80x24 screen size. It was fine at 91x28.
Source was 21:1/195 to 21:1/195.1
pkt.zip & fmailm68k.zip in your inbound.... If you want to do something with M68K support... (This is after all just something todo on my part!)
FMail-lnx-m68k-2.3.0.0-Beta20240317 - The Fast Echomail Processor Copyright (C) 1991-2024 by FMail Developers - All rights reserved
Scanning netmail directory...
Tossing messages...
Packet is addressed to another node (256/49920); packet file: /home/vk3heg/fmail/inbound/f8d28501.pkt is renamed with extension: '.wrong_destination'
Fconfig config actually runs, but did a Segmentation fault when the
ssh session was 80x24 screen size. It was fine at 91x28.
This was due to a wrong check for the screen size, which I set for debugging, but forgot to change back.
As FConfig is originally a DOS program it expects a terminal of at least 80x25. Yesterday I created a version that will run in a 80x24 terminal for
linux (there was a more or less unused line at the bottom of the screen ;-)). I have to do some more testing before I commit the code to git though...
pkt.zip & fmailm68k.zip in your inbound.... If you want to do
something with M68K support... (This is after all just something
todo on my part!)
Not really. ;-) I think there are more important things on the todo
list.
[...]FMail-lnx-m68k-2.3.0.0-Beta20240317 - The Fast Echomail Processor
Packet is addressed to another node (256/49920); packet file:
/home/vk3heg/fmail/inbound/f8d28501.pkt is renamed with
extension: '.wrong_destination'
256/49920 = 1/195, if you swap bytes. So a typical endianess
problem...
pkt.zip & fmailm68k.zip in your inbound.... If you want to do
something with M68K support... (This is after all just something
todo on my part!)
Not really. ;-) I think there are more important things on the todo
list.
That's understandable, I doubt you'd have a huge M68K user base... Mostly a count of 1... #-)
[...]FMail-lnx-m68k-2.3.0.0-Beta20240317 - The Fast Echomail Processor
Packet is addressed to another node (256/49920); packet file:
/home/vk3heg/fmail/inbound/f8d28501.pkt is renamed with
extension: '.wrong_destination'
256/49920 = 1/195, if you swap bytes. So a typical endianess
problem...
I just looked through what andrew did to add M68K support in Talisman BBS and it's not just a few lines of code...
Not really. ;-) I think there are more important things on the
todo list.
That's understandable, I doubt you'd have a huge M68K user
base... Mostly a count of 1... #-)
You are not using it! So 0. ;-)
I just looked through what andrew did to add M68K support in
Talisman BBS and it's not just a few lines of code...
Making the pkt code endianness agnostic isn't a big task. My pktviewer code does it. I wrote it decades ago, so it would compile on both the Amiga and PC. ;-)
But doing so for the three supported messagebases (msg, hudson, jam),
is a huge pain in the ass, because the code for these is all over the place.
I just looked through what andrew did to add M68K support in
Talisman BBS and it's not just a few lines of code...
Making the pkt code endianness agnostic isn't a big task. My pktviewer
code does it. I wrote it decades ago, so it would compile on both the
Amiga and PC. ;-)
Do you want me to test it? Link to the code?
But doing so for the three supported messagebases (msg, hudson, jam),
is a huge pain in the ass, because the code for these is all over the
place.
It's a chicken & egg issue..
Magicka supports JAM but is no longer supported.
Talisman only supports squish, but is still supported!
Both compile and work on M68K Linux!
Do you want me to test it? Link to the code?
http://www.vlzn.nl/fmail/files/pktview-1.1-src.zip
But doing so for the three supported messagebases (msg, hudson,
jam), is a huge pain in the ass, because the code for these is
all over the place.
It's a chicken & egg issue..
Indeed.
Magicka supports JAM but is no longer supported.
Talisman only supports squish, but is still supported!
Both compile and work on M68K Linux!
Maybe I'll try to make the pkt code endianess agnostic first. If that works for you I could look at the message base code.
Does your compiler/environment have endian.h ?
Do you want me to test it? Link to the code?
http://www.vlzn.nl/fmail/files/pktview-1.1-src.zip
Compiles and works:
vk3heg@a3000:~/source/pktview$ ./pktview -v fc5c2f01.pkt
pktview V1.1, Copyright WvV 1998, 2016
Magicka supports JAM but is no longer supported.
Talisman only supports squish, but is still supported!
Both compile and work on M68K Linux!
Maybe I'll try to make the pkt code endianess agnostic first. If that
works for you I could look at the message base code.
It's upto you if you want to spend the time doing it... This was just a test
to see if fmail etc, would even compile and run...
Talsiman's tosser works fine. The only thing I wish it did was toss
the messages into the msg base in date order. The point system doesn't have a set poll schedule.
Does your compiler/environment have endian.h ?
Yes, it is after all Debian Linux M68K:
vk3heg@a3000:~/source/pktview$ whereis endian.h
endian.h: /usr/include/endian.h
Compiles and works:To be sure: This was on M68K? In that case: Cool! ;-)
Does your compiler/environment have endian.h ?
Yes, it is after all Debian Linux M68K:
vk3heg@a3000:~/source/pktview$ whereis endian.h
endian.h: /usr/include/endian.h
Can you sent it to me, for comparison, with the one on my linux?
Compiles and works:
To be sure: This was on M68K? In that case: Cool! ;-)
Yes Linux on my Amiga 3000... Btw: Fconfig does work and creates a config file.
And just to confirm:
https://www.youtube.com/watch?v=caZtHdNe0Ag
That is my Amiga 3000 in this video.. #-) (Eeven with the fact errors & fud
%$#^&% )
vk3heg@a3000:~/source/pktview$ whereis endian.h
endian.h: /usr/include/endian.h
Can you sent it to me, for comparison, with the one on my linux?
There's not much in it:
| Sysop: | Tetrazocine |
|---|---|
| Location: | Melbourne, VIC, Australia |
| Users: | 4 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 59:13:13 |
| Calls: | 65 |
| Files: | 21,500 |
| Messages: | 73,559 |