Howdy,

When MBSE tosses incoming files, is there a setting to stop it creating a symlink? I was going to look through the code, but I thought I'd ask here
too, in case this route provides a quicker answer ;)

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker! (3:633/509.1)

Hello Deon!

16 Mar 19 11:44, you wrote to all:

When MBSE tosses incoming files, is there a setting to stop it
creating a symlink? I was going to look through the code, but I
thought I'd ask here too, in case this route provides a quicker answer
;)

There isn't a setting to prevent the creation of symlinks. MBSE creates symlinks to ensure that every file has both an 8.3 DOS compatible filename and the "real" full filename.

Andrew

--- GoldED+/LNX 1.1.5-b20180707
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Hey Andrew,

On 16 Mar 2019, Andrew Leary said the following...

There isn't a setting to prevent the creation of symlinks. MBSE creates symlinks to ensure that every file has both an 8.3 DOS compatible
filename and the "real" full filename.

OK, I think there are opportunities for the TIC processing to be improved.
This is something I wanted to look at for a long time, but I just cant seem
to find the time or headspace to look into it.

Here is an example of what I see:
-rw-r--r-- 1 mbse bbs 1063026 Dec 2 21:55 NULL003L32.Z
-rw-r--r-- 1 mbse bbs 1027027 Dec 2 21:55 NULL003RPI.Z
-rw-r--r-- 1 mbse bbs 780512 Dec 2 21:55 NULL003W32.Z
lrwxrwxrwx 1 mbse bbs 12 Dec 7 20:29 null003l32.zip -> NULL003L32.Z lrwxrwxrwx 1 mbse bbs 12 Dec 7 20:29 null003rpi.zip -> NULL003RPI.Z lrwxrwxrwx 1 mbse bbs 12 Dec 7 20:29 null003w32.zip -> NULL003W32.Z

and
-rw-r--r-- 1 mbse bbs 238387 Oct 2 21:13 TDFSTUDIO110
lrwxrwxrwx 1 mbse bbs 12 Nov 8 21:39 tdfstudio110_l32.zip ->
TDFSTUDIO110
lrwxrwxrwx 1 mbse bbs 12 Nov 8 21:39 tdfstudio110_rpi.zip ->
TDFSTUDIO110

In the second output, you'll see that I received something inbound, it was converted to uppercase and truncated to 12 chars (the DOS format?) and then symlinked to the unix format (name untouched). In the process, one of these links is wrong.

I would like to see incoming files be tossed and stored "as received"
(since MBSE is running on Linux - converted to lowercase if necessary), and
the symlink be created to support DOS conventions (if it cannot be disabled). Additionally, the DOS link should be 8.3 chars and if there is no extension,
it should just be 8 chars (and all uppercase). (The first output above is
wrong for DOS).

I have a mess of a badtic dir and file areas because MBSE doesnt handle large filenames well - and I know you've just released an update (which I'm yet to look at) - I'm not sure if it will help the issue I'm seeing.

...deon

_--_|\ | Deon George
/ \ | Chinwag BBS - A BBS on a PI in Docker!
\_.__.*/ |
V | Coming from the 'burbs of Melbourne, Australia

--- Mystic BBS v1.12 A42 2018/12/27 (Raspberry Pi/32)
* Origin: Chinwag | MysticBBS in Docker! (3:633/509.1)