So I have completed the switch to linux with my mystic bbs (from
windows) and I actually just put it online an hour ago. In watching MIS screen I am noticing that all my fidopoll events now end with a RES 127 when they used to end with a RES 0? As far as I can tell seems to be functioning ok, anyone run into this before? Is there anything different
I can tell you that mine end with 127, under linux... further than that I'm not much help, but I always took 127 as good.
I can tell you that mine end with 127, under linux... further than th I'm not much help, but I always took 127 as good.
I think g00r00 has been talking about just this in the Mystic echo on Fidonet. Do go there to see the messages, though I'll attempt to answer.
127 is a linux/BASH error. It means that something was not found. Perhaps because of a PATH issue, or because of some other Linux thing.
In this case, probably the two most common fixes are:
1) To add the ./ in front of the command (to say that it's something
that should be executed.)
2) To include full paths to commands, so that you're not dependent on relative directories or items being in the PATH system environment variable.
--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Storm BBS (21:2/108)
Would you happen to know, if it is possible to get mystic windows to resize with terminal windows as it did in windows? This is my first go
and, seems like i better start adding fidonet so i can pull the nets the g00r00 posts in. thanks.
what is the correct code? 0?
On 25 Aug 2020, Adept said the following...
and, seems like i better start adding fidonet so i can pull the nets
the g00r00 posts in. thanks.
what is the correct code? 0?
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 95 |
Nodes: | 16 (0 / 16) |
Uptime: | 11:14:43 |
Calls: | 4,627 |
Calls today: | 3 |
Files: | 8,491 |
Messages: | 348,947 |
Posted today: | 3 |