1. Forum
  2. Fidonet Message
  3. MBSE

  • Dreationtiontion of softlinks

    From Vince Coen@2:250/1 to Deon George on Thursday, March 21, 2019 13:53:58
    Hello Deon!

    Monday March 18 2019 20:07, you wrote to me:

    On 18 Mar 2019, Vince Coen said the following...
    Are these files from other sources i.e., you downloaded them and
    hatched them etc ?

    No, these files have coming in from various uplinks and nets.

    Suggest at least for now you ask uplinks to send files conforming to the 8.3 standards.

    That said mbse does need looking at to see where the problem is.

    Worse comes to it we can always use rendom naming when getting a duplicate name error.
    That is the drawback of shortening file names down to eight chars.



    Vince

    --- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Vince Coen@2:250/1 to Deon George on Thursday, March 21, 2019 13:58:17
    Hello Deon!

    Monday March 18 2019 20:07, you wrote to me:

    On 18 Mar 2019, Vince Coen said the following...
    Are these files from other sources i.e., you downloaded them and
    hatched them etc ?

    No, these files have coming in from various uplinks and nets.

    Have you created a bug report for this ?

    If not please do so.



    Vince

    --- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Deon George@3:633/509.1 to Vince Coen on Friday, March 22, 2019 00:57:58
    On 21 Mar 2019, Vince Coen said the following...
    Suggest at least for now you ask uplinks to send files conforming to the 8.3 standards.

    Yeah, I dont think that will happen.

    I thought my suggestion would would at least improve the handling. IE: The current handling looses incoming files if two files have the same first 12 chars. My suggestion would be to keep the files as is and create the symlinks for DOS purposes - and if they are wrong, its an easier manual fix by the sysop.

    ...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)
  • From Deon George@3:633/509.1 to Vince Coen on Friday, March 22, 2019 00:58:24
    On 21 Mar 2019, Vince Coen said the following...
    Have you created a bug report for this ?

    No, dont know where to.

    I thought posting here was enough :)

    ...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)
  • From Andrew Leary@1:320/219 to Deon George on Friday, March 22, 2019 04:05:23
    Hello Deon!

    21 Mar 19 23:58, you wrote to Vince Coen:

    Have you created a bug report for this ?

    No, dont know where to.

    I thought posting here was enough :)

    You can create a ticket at https://sourceforge.net/p/mbsebbs/tickets/ with your report. This will help us track the reported issues.

    I do see that there are situations where the current setup can cause problems. Michiel Broek originally designed mbfido's .TIC processing to work with 8.3 DOS style filenames. I need to do some thinking about a way to create 8.3 DOS filenames from incoming long filenames, without breaking existing setups.

    The safest way to avoid problems is to store a long filename archive in a .ZIP file with an 8.3 name and then hatch that.

    Andrew

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