• R50 areas

    From Janis Kracht@1:2320/100 to All on Mon Aug 28 23:28:52 2017
    Hi Everyone,

    I've connected Michael Dukelsky to this echo today.

    Michael sends out the R50 file echos.

    Welcome Michael :)

    Take care,
    Janis

    --- BBBS/Li6 v4.10 Toy-3
    # Origin: Prism bbs (1:261/38)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Bob Seaborn@1:2320/100 to Janis Kracht on Mon Aug 28 22:57:00 2017
    Hi Everyone,

    I've connected Michael Dukelsky to this echo today.

    Michael sends out the R50 file echos.



    Sure hope he does NOT distribute LFN files!





    .....Bob

    --- GEcho/32 & IM 2.50
    # Origin: http://www.fidonet.ca (1:140/12)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Janis Kracht@1:2320/100 to Bob Seaborn on Tue Aug 29 09:06:30 2017
    Hi Bob,

    I've connected Michael Dukelsky to this echo today.
    Michael sends out the R50 file echos.


    Sure hope he does NOT distribute LFN files!

    I spoke to his source for those files, and he is now aware of the problems his last hatched caused. He's going to rename his archives, etc.

    Take care,
    Janis

    --- BBBS/Li6 v4.10 Toy-3
    # Origin: Prism bbs (1:261/38)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From mark lewis@1:2320/100 to Bob Seaborn on Tue Aug 29 09:55:58 2017

    On 2017 Aug 28 22:57:00, you wrote to Janis Kracht:

    I've connected Michael Dukelsky to this echo today.

    Michael sends out the R50 file echos.

    Sure hope he does NOT distribute LFN files!

    yeah, i've got three over here received on 25 Aug 2017...

    fidoosxip.tar.bz2
    fido_mac_ppc.zip
    gposx-115-20170303.zip

    their TIC files are gone with "file not found" errors because they are not 8.3 and the code simply can't see them... the log records the file names from the TICs chopped at 12 characters long... so no wonder they can't be found...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Pasteurization is your friend.
    ---
    # Origin: (1:3634/12.73)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Bob Seaborn@1:2320/100 to Janis Kracht on Tue Aug 29 11:01:00 2017
    Hi Bob,

    I've connected Michael Dukelsky to this echo today.
    Michael sends out the R50 file echos.


    Sure hope he does NOT distribute LFN files!

    I spoke to his source for those files, and he is now aware of the
    problems his last hatched caused. He's going to rename his archives,
    etc.


    Good, thank you.





    .....Bob

    --- GEcho/32 & IM 2.50
    # Origin: http://www.fidonet.ca (1:140/12)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Bob Seaborn@1:2320/100 to mark lewis on Tue Aug 29 11:02:01 2017

    On 2017 Aug 28 22:57:00, you wrote to Janis Kracht:

    I've connected Michael Dukelsky to this echo today.

    Michael sends out the R50 file echos.

    Sure hope he does NOT distribute LFN files!

    yeah, i've got three over here received on 25 Aug 2017...

    Same here, with similar results.



    fidoosxip.tar.bz2
    fido_mac_ppc.zip
    gposx-115-20170303.zip

    their TIC files are gone with "file not found" errors because they are
    not 8.3 and the code simply can't see them... the log records the file
    names from the TICs chopped at 12 characters long... so no wonder they
    can't be found...





    .....Bob

    --- GEcho/32 & IM 2.50
    # Origin: http://www.fidonet.ca (1:140/12)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Michael Dukelsky@1:2320/100 to Janis Kracht on Tue Aug 29 20:00:26 2017
    Hello Janis,

    Monday August 28 2017, Janis Kracht wrote to All:

    I've connected Michael Dukelsky to this echo today.

    Michael sends out the R50 file echos.

    Welcome Michael :)

    Thank you, Janis.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    # Origin: Moscow, Russia (2:5020/1042)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Michael Dukelsky@1:2320/100 to Bob Seaborn on Tue Aug 29 20:04:48 2017
    Hello Bob,

    Monday August 28 2017, Bob Seaborn wrote to Janis Kracht:

    I've connected Michael Dukelsky to this echo today.
    Michael sends out the R50 file echos.
    Sure hope he does NOT distribute LFN files!

    No, I never hatch files with long file names, but I cannot prevent others from doing it, I can only ask not to do it.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    # Origin: Moscow, Russia (2:5020/1042)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Bob Seaborn@1:2320/100 to Michael Dukelsky on Tue Aug 29 23:04:00 2017
    Hello Bob,

    Monday August 28 2017, Bob Seaborn wrote to Janis Kracht:

    I've connected Michael Dukelsky to this echo today.
    Michael sends out the R50 file echos.
    Sure hope he does NOT distribute LFN files!

    No, I never hatch files with long file names, but I cannot prevent
    others from doing it, I can only ask not to do it.


    I believe the way things work, is that others send you the files, and you send them on to the Filegate System. Should someone send you a file with a LFN, why

    don't you simply pack it into an 8.3 archive, with a note inside that explains that it's a LFN file? To my thinking, that should be the simplest method of ensuring the Filegate only gets 8.3 files, yes? Then you send the originator a

    note that advises them that LFN's are strongly discouraged.





    .....Bob

    --- GEcho/32 & IM 2.50
    # Origin: http://www.fidonet.ca (1:140/12)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Janis Kracht@1:2320/100 to Bob Seaborn on Wed Aug 30 12:01:28 2017
    Hi Bob,

    Monday August 28 2017, Bob Seaborn wrote to Janis Kracht:

    I've connected Michael Dukelsky to this echo today.
    Michael sends out the R50 file echos.
    Sure hope he does NOT distribute LFN files!

    No, I never hatch files with long file names, but I cannot prevent
    others from doing it, I can only ask not to do it.


    I believe the way things work, is that others send you the files, and you send >them on to the Filegate System. Should someone send you a file with a LFN, >why don't you simply pack it into an 8.3 archive, with a note inside that >explains hat it's a LFN file? To my thinking, that should be the simplest >method of ensuring the Filegate only gets 8.3 files, yes? Then you send the >originator note that advises them that LFN's are strongly discouraged.


    Bob, that is not an easy thing to do... Distribution in general works much better if all involved use 8X3 filenames with zip compression to start with.

    If a file must be put in a zip file as you suggest, we STORE it, not ARCHIVE it. (zip -jm0 filename.zip filename.???). Archiving a previously archived file (rar, tar.bz, tar.bz2, etc.) makes is larger than the original.

    Anyway, that is why I contacted the fellow in Russia, Alexandr Kruglikov, who compiled these MAC files and sent them to Michael Dukelsky.

    I explained to Aleksansr that we must use 8X3 filenames and zip is the preferred compression method (but if you are sending a previously archived file, repack it with zip or _store_ it in a zip 'envelope'.)

    Aleksandr and I have been discussing this in netmail, and I have offered to help him if he needs it.

    Take care,
    Janis

    --- BBBS/Li6 v4.10 Toy-3
    # Origin: Prism bbs (1:261/38)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Janis Kracht@1:2320/100 to mark lewis on Wed Aug 30 12:37:32 2017
    Hi Mark,

    yeah, i've got three over here received on 25 Aug 2017...

    fidoosxip.tar.bz2
    fido_mac_ppc.zip
    gposx-115-20170303.zip

    their TIC files are gone with "file not found" errors because they are not 8.3
    and the code simply can't see them... the log records the file names from the TICs chopped at 12 characters long... so no wonder they can't be found...

    BBBS just passed the files right through (there is no way to tell it to stop LFN files and it knows what tar.bz or tar.bz2 files are), so I've been working with the fellow who sent Michael Dukelsky these files.

    Aleksandr Kruglikov compiled these versions for the MAC and sent them to Michael - I've explained to Aleksandr that we need 8X3 filenames, preferably zip files, original archive either repacked to zip or stored (not archived) if the file comes in as some other archive type.

    Aleksandr also had a problem with HTICK since I guess it only understands 8X3 files <grin>... I asked him to resend the corrected files with replace and mentioned that if needs help with HTICK I'll take a look at the docs.

    I guess the reason Aleksandr used tar.bz2 is that it very common to use that archiver with the Mac - I explained to Aleksandr that we really have to go with

    the lowest common denominator in file distribution (8X3 zip archives, original file either repacked or stored).

    Take care,
    Janis

    --- BBBS/Li6 v4.10 Toy-3
    # Origin: Prism bbs (1:261/38)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Michael Dukelsky@1:2320/100 to Bob Seaborn on Wed Aug 30 19:52:34 2017
    Hello Bob,

    Tuesday August 29 2017, Bob Seaborn wrote to Michael Dukelsky:

    I believe the way things work, is that others send you the files, and
    you send them on to the Filegate System. Should someone send you a
    file with a LFN, why don't you simply pack it into an 8.3 archive,
    with a note inside that explains that it's a LFN file?

    Do you mean I inspect every file sent to me and then manually send it to file echo? No, I have software that automatically sends to my links all received files. The files with LFN were sent by Alexander Kruglikov 2:5053/58 and I received the files not from him directly but from his uplink. I had no preliminary information that he was going to hatch files and he never did it before. So I had no chance to prevent the hatching.

    I sent him netmail where I enumerated the requirements to hatched files. Hopefully he will abide to the requirements.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    # Origin: Moscow, Russia (2:5020/1042)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Vince Coen@1:2320/100 to Michael Dukelsky on Wed Aug 30 22:26:48 2017
    Hello Michael!

    Tuesday August 29 2017 20:04, you wrote to Bob Seaborn:

    Hello Bob,

    Monday August 28 2017, Bob Seaborn wrote to Janis Kracht:

    I've connected Michael Dukelsky to this echo today.
    Michael sends out the R50 file echos.
    Sure hope he does NOT distribute LFN files!

    No, I never hatch files with long file names, but I cannot prevent
    others from doing it, I can only ask not to do it.

    Tell him to contact me as my system does play with long fn and will convert them for legacy systems.

    Vince

    --- Mageia Linux v5/Mbse v1.0.7.2/GoldED+/LNX 1.1.501-b20150715
    # Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Sean Dennis@1:2320/100 to Janis Kracht on Wed Aug 30 20:12:44 2017
    Hello Janis,

    30 Aug 17 12:37 at you wrote to mark lewis:

    BBBS just passed the files right through (there is no way to tell it
    to stop LFN files and it knows what tar.bz or tar.bz2 files are), so
    I've been working with the fellow who sent Michael Dukelsky these
    files.

    MBSE has a toggle that can be set per mail link to force 8.3 filenames. I have all of my links, including your system, set to 8.3 to prevent these issues.

    Later,
    Sean

    --- GoldED+/LNX 1.1.5-b20170303
    # Origin: Outpost BBS * Limestone, TN, USA (1:18/200)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Michael Dukelsky@1:2320/100 to Vince Coen on Thu Aug 31 10:34:14 2017
    Hello Vince,

    Wednesday August 30 2017, Vince Coen wrote to Michael Dukelsky:

    I've connected Michael Dukelsky to this echo today.
    Michael sends out the R50 file echos.
    Sure hope he does NOT distribute LFN files!

    No, I never hatch files with long file names, but I cannot prevent
    others from doing it, I can only ask not to do it.

    Tell him to contact me as my system does play with long fn and will convert them for legacy systems.

    Thank you for offering help, but we have already agreed the following naming scheme:

    File names are of the type NBOymmdd.zip where
    N is the first letter of the program Name being sent: B - binkd, H - husky, G -

    Golded.
    B is the program development Branch: C - current, T - stable, P - current with Perl, L - stable with Perl, S - sources.
    O is the Operating system: W - Windows, L - Linux, M - Mac, F - FreeBSD.
    Five decimal digits that follow these three letters denote the program version date.
    y is the last digit of the year,
    mm is the month number from 01 to 12,
    dd is the day number from 01 to 31.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    # Origin: Moscow, Russia (2:5020/1042)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Janis Kracht@1:2320/100 to Michael Dukelsky on Thu Aug 31 10:07:56 2017
    Hi Michael,

    ... we have already agreed the following naming
    scheme:

    File names are of the type NBOymmdd.zip where
    N is the first letter of the program Name being sent: B - binkd, H - husky, G
    Golded.
    B is the program development Branch: C - current, T - stable, P - current with
    Perl, L - stable with Perl, S - sources.
    O is the Operating system: W - Windows, L - Linux, M - Mac, F - FreeBSD.
    Five decimal digits that follow these three letters denote the program version
    date.
    y is the last digit of the year,
    mm is the month number from 01 to 12,
    dd is the day number from 01 to 31.

    This looks great, Michael, thanks to you guys for working this out :)

    Take care,
    Janis

    --- BBBS/Li6 v4.10 Toy-3
    # Origin: Prism bbs (1:261/38)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Wilfred van Velzen@1:2320/100 to Michael Dukelsky on Thu Aug 31 17:56:29 2017
    Hi Michael,

    On 2017-08-31 10:34:14, you wrote to Vince Coen:

    Thank you for offering help, but we have already agreed the following naming scheme:

    File names are of the type NBOymmdd.zip where
    N is the first letter of the program Name being sent: B - binkd, H -
    husky,
    G - Golded. B is the program development Branch: C - current, T - stable,
    P
    - current with Perl, L - stable with Perl, S - sources. O is the Operating system: W - Windows, L - Linux, M - Mac, F - FreeBSD. Five decimal digits that follow these three letters denote the program version date. y is the last digit of the year, mm is the month number from 01 to 12, dd is the
    day
    number from 01 to 31.

    How do you differentiate between binkd 0.9, 1.0 and 1.1 version releases?

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    # Origin: FMail development HQ (2:280/464)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Michael Dukelsky@1:2320/100 to Wilfred van Velzen on Thu Aug 31 20:52:12 2017
    Hello Wilfred,

    Thursday August 31 2017, Wilfred van Velzen wrote to Michael Dukelsky:

    Thank you for offering help, but we have already agreed the
    following naming scheme:

    File names are of the type NBOymmdd.zip where
    N is the first letter of the program Name being sent: B - binkd,
    H - husky, G - Golded. B is the program development Branch: C -
    current, T - stable, P - current with Perl, L - stable with Perl,
    S - sources. O is the Operating
    system: W - Windows, L - Linux, M - Mac, F - FreeBSD. Five
    decimal digits that follow these three letters denote the program
    version date. y is the last digit of the year, mm is the month
    number from 01 to 12, dd is the day number from 01 to 31.

    How do you differentiate between binkd 0.9, 1.0 and 1.1 version
    releases?

    Well, 1.1 is current in this terminology and 1.0 is stable. I do not expect anybody here to hatch 0.9 builds but if such wish will appear, we can mark the build with the second letter R for Release.

    Michael

    ... node (at) f1042 (dot) ru
    --- GoldED+/LNX 1.1.5-b20170303
    # Origin: Moscow, Russia (2:5020/1042)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)