*Originally Posted In IFDC
*Originally Posted by Janis Kracht

Hi Gert,

Even though you separated the hatch of these two files by several hours, it STILL caused problems with a number of my downlinks:

160118 04:00 BTICK: Processing file vpascal.zip in PASLINUX (21007kB).
160118 09:14 BTICK: Processing file vpascal.zip in PASWIN (21007kB).

You cannot use the SAME filename for two different files.

Not everyone gets crash delivery immediately upon a files arrival.

Even if they did, it would STILL cause problems because these files are in a somewhat large range and take some time to go out to all downlinks:

21M Jan 18 04:00 /home/ftp/pub/pascal-net/paslinux/vpascal.zip
21M Jan 18 09:14 /home/ftp/pub/pascal-net/paswin/vpascal.zip

I've have had some people ask me to disconnect them from all of your file echos
because of this situation, and I understand the frustration they feel.

In the future, please name the files in a manner that will indicate the version
number and OS, for instance FP20WIN, FP20LNX, etc.

Thanks,
Janis

--- BBBS/Li6 v4.10 Dada-2
* Origin: Prism bbs (1:261/38)

* Reply to message originally in area CarbonArea

Hello Janis!

Mon Jan 18 2016, Janis Kracht wrote to Gert Andersen:

Even though you separated the hatch of these two files by several
hours, it STILL caused problems with a number of my downlinks:

160118 04:00 BTICK: Processing file vpascal.zip in PASLINUX (21007kB).
160118 09:14 BTICK: Processing file vpascal.zip in PASWIN (21007kB).

You cannot use the SAME filename for two different files.

Not everyone gets crash delivery immediately upon a files arrival.

Even if they did, it would STILL cause problems because these files are
in a somewhat large range and take some time to go out to all
downlinks:

21M Jan 18 04:00 /home/ftp/pub/pascal-net/paslinux/vpascal.zip
21M Jan 18 09:14 /home/ftp/pub/pascal-net/paswin/vpascal.zip

I've have had some people ask me to disconnect them from all of your
file echos because of this situation, and I understand the frustration
they feel.

In the future, please name the files in a manner that will indicate the
version number and OS, for instance FP20WIN, FP20LNX, etc.

This will I see if I can do next time for the pascal files.

Take care,
Gert

- Get the best with linux -

--- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))
* Origin: * One bird in hand is better than 10 on the roof * (2:230/150)

Hello Gert!

Tuesday January 19 2016 09:41, you wrote to Janis Kracht:

This will I see if I can do next time for the pascal files.

Do so for ALL archives !



Vince

--- Mageia Linux v5/Mbse v1.0.6/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

Hello Janis.

18 Jan 16 11:38, you wrote to Gert Andersen:

You cannot use the SAME filename for two different files.

Not everyone gets crash delivery immediately upon a files arrival.

Even if they did, it would STILL cause problems because these files
are in a somewhat large range and take some time to go out to all downlinks:

I would have to agree. While I appreciate Gert for making the files available. I too have occasional problems when files show up using the same filenames.

I've have had some people ask me to disconnect them from all of your
file echos because of this situation, and I understand the frustration they feel.

I also have had people ask me about the rather large (20m-30m) files.



Jeff

--- GoldED+/W32-MINGW 1.1.5-b20070503
* Origin: Region 14 IP Server - ftn.region14.org (1:14/5)

Hi Jeff,

are in a somewhat large range and take some time to go out to all
downlinks:

I would have to agree. While I appreciate Gert for making the files available.
I too have occasional problems when files show up using the same filenames.

It can only cause problems no matter when it occurs, and there is no reason on earth send files out with the same name. A simple change by one letter or adding a number is enough, though I really prefer to see version number and OS type for files like this one that Gert sent out.

I've have had some people ask me to disconnect them from all of your
file echos because of this situation, and I understand the frustration
they feel.

I also have had people ask me about the rather large (20m-30m) files.

I understand that some programming files can be in that range, and why (Windows
files are notorious <g>) but when the files are large and have to be rehatched because of problems like this I think everyone sighs.

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-2
* Origin: Prism bbs (1:261/38)

Hi Vince,

Tuesday January 19 2016 09:41, you wrote to Janis Kracht:

This will I see if I can do next time for the pascal files.

Do so for ALL archives !

Definitely :) There is no reason to use the same filename for any file.

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-2
* Origin: Prism bbs (1:261/38)

Hi Gert,

I've have had some people ask me to disconnect them from all of your
file echos because of this situation, and I understand the frustration
they feel.

In the future, please name the files in a manner that will indicate the
version number and OS, for instance FP20WIN, FP20LNX, etc.

This will I see if I can do next time for the pascal files.

As Vince said, you should always do this for any file you send out.

Sending out the same filename across a number of file echos like paswin, pasfiles, pasos2, etc. does NOT work.

It does not work even if you separate the hatching over several hours. Sure, it works on my system as the first distribution point, but once it gets here and then goes out to others it will fail because you can't control how often people may poll for files.

Thanks Gert.

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-2
* Origin: Prism bbs (1:261/38)

* Reply to message originally in area CarbonArea

Hello Vince!

Tue Jan 19 2016, Vince Coen wrote to Gert Andersen:

* Forwarded from area 'FILEGATE'
Hello Gert!

Tuesday January 19 2016 09:41, you wrote to Janis Kracht:

This will I see if I can do next time for the pascal files.

Do so for ALL archives !

I normally try to make it when there is more than 1 OS as Linux, Windows, OS/2 and MAC files.


Take care,
Gert

- Get the best with linux -

--- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))
* Origin: * One step from heaven is not enough * (2:230/150)

* Reply to message originally in area CarbonArea

Hello Janis!

Tue Jan 19 2016, Janis Kracht wrote to Gert Andersen:

I've have had some people ask me to disconnect them from all of your
file echos because of this situation, and I understand the frustration
they feel.

In the future, please name the files in a manner that will indicate the
version number and OS, for instance FP20WIN, FP20LNX, etc.

This will I see if I can do next time for the pascal files.

As Vince said, you should always do this for any file you send out.

Sending out the same filename across a number of file echos like
paswin, pasfiles, pasos2, etc. does NOT work.

It does not work even if you separate the hatching over several hours.
Sure, it works on my system as the first distribution point, but once
it gets here and then goes out to others it will fail because you can't
control how often people may poll for files.

Is there more than 1 OS of a file will I try to see if I can make to be a lnx or L , win or W etc. for it OS type file.

Take care,
Gert

- Get the best with linux -

--- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))
* Origin: * One bird in hand is better than 10 on the roof * (2:230/150)

* Reply to message originally in area CarbonArea

Hello Robert!

Tue Jan 19 2016, Robert Wolfe wrote to Gert Andersen:

This will I see if I can do next time for the pascal files.

And if you would not mind refraining from that danged HUGE DDE200L.ZIP
file every week or so, that would help out a lot, too.

The dde200L.zip files is send out from my system 2 times a week and sometimes only once a week if there is a new made once a week and sometimes can there goes longer times for it send out.

Take care,
Gert

- Get the best with linux -

--- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))
* Origin: * One step from heaven is not enough * (2:230/150)

20 Jan 16 09:31, you wrote to Robert Wolfe:

And if you would not mind refraining from that danged HUGE
DDE200L.ZIP file every week or so, that would help out a lot, too.

The dde200L.zip files is send out from my system 2 times a week and sometimes only once a week if there is a new made once a week and sometimes can there goes longer times for it send out.

that's the problem, gert... how many times does it need to be sent out?? if it is alpha or beta code, DON'T sent it... if it is release code, then send it once and not over and over and over again... do you know how long it takes to send that danged thing out at 768k upload speed?

so far this month alone, we've gotten four editions of that specific file... one on the 2nd, 4th, 8th and then the 18th... on my connection, each one took ~10 minutes to arrive... it takes ~4 times as long to send it out and that's not counting overhead or other traffic in the pipe which will increase the upload time... so roughly 40 minutes to upload to one uplink... if there's two uplinks, that's already ~90 minutes with no other traffic being sent... can you
see the problem yet??

)\/(ark

"So let me ask you a question about this brave new world of yours. When you've killed all the bad guys, and when it's all perfect, and just and fair, and when
you have finally got it exactly the way you want it, what are you going to do with the people like you? The trouble makers. How are you going to protect your
glorious revolution from the next one?" - The twelfth Doctor

... He who says "Where there's smoke there's fire" never owned a fireplace
---
* Origin: (1:3634/12.73)

The dde200L.zip files is send out from my system 2 times a week and sometimes only once a week if there is a new made once a week and sometimes can there goes longer times for it send out.

Yes, but you must realize that it takes a while for files of that size
to get downloaded from Janis' connection from time to time. Yes, I
have a slightly faster connection than she has, but a file that size
coming in a 30-something k/sec is painful for both my system and
probably her connection as well. I also noticed that the archives
contain binaries. If you MUST hatch this file, why not just hat out
the compressed SOURCE CODE only. That will make the archives much
smaller. Either that or I drop the file echo completely from my
normal mail queue.

--- Ezycom V3.00 01FB0027
* Origin: Neptune's Lair * neptune.ddns.net * Memphis, TN (1:116/18)

This will I see if I can do next time for the pascal files.

And if you would not mind refraining from that danged HUGE DDE200L.ZIP
file every week or so, that would help out a lot, too.

You don't know how bad it is conversing with Gert.......

I asked him a million years ago it seems to stop sending me dde* files and still they come in... there's another variant.. forget the filename, same problem...

Everytime I moan and bitch about this Ron says "Geez, Cut the Link"..

He's right. I just think maybe Gert will realize the problem????

Guess not.

Take care,
Janis

--- BBBS/Li6 v4.10 Dada-2
* Origin: Prism bbs (1:261/38)

21 Jan 16 10:55, you wrote to me:

There is normal 2 versions of Doomday Engine.
dde200 is version 2.0.0 build and it comes out from author 3-4 times a

week

where I then only will send it out once a week.

so that's development code, aka ALPHA and/or BETA... don't ship it! how hard is
that to understand???

dmd115x is complete new 1.15.x version there comes from author once a month Then can the author sometimes had made a version I make to be dde115x there is some new build version, but it is only happens from
time to time and is not regular.

this appears to be general availability code, aka full release... not alpha or beta... distributing updates of that once a month is fine... the complaint is you shipping 50+ meg of the same file every few days... the complaint is even stronger because you are shipping alpha/beta code that is not stable...

)\/(ark

"So let me ask you a question about this brave new world of yours. When you've killed all the bad guys, and when it's all perfect, and just and fair, and when
you have finally got it exactly the way you want it, what are you going to do with the people like you? The trouble makers. How are you going to protect your
glorious revolution from the next one?" - The twelfth Doctor

... Been dazed and confused for so long it's normal.
---
* Origin: (1:3634/12.73)

* Reply to message originally in area CarbonArea

Hello mark!

Fri Jan 22 2016, mark lewis wrote to Gert Andersen:

There is normal 2 versions of Doomday Engine.
dde200 is version 2.0.0 build and it comes out from author 3-4 times a
week where I then only will send it out once a week.

so that's development code, aka ALPHA and/or BETA... don't ship it! how
hard is that to understand???

dmd115x is complete new 1.15.x version there comes from author once a
month Then can the author sometimes had made a version I make to be
dde115x there is some new build version, but it is only happens from
time to time and is not regular.

this appears to be general availability code, aka full release... not
alpha or beta... distributing updates of that once a month is fine...
the complaint is you shipping 50+ meg of the same file every few
days... the complaint is even stronger because you are shipping
alpha/beta code that is not stable...

The last one got out today friday as a dde200L in lnx4games and is not comng out more if it not is regular 200 vwersion without build number so stable Doomday Engine of DDE is 1.15.6 the real Doomsday Engine is dmd 1.15.7 so if things is working is there goes about 3-4 months is dmd up on version 2.0.0 then.
Mostly is the OS to be tried to be just around 40-50M for Linux and Win at 30-40M and the MAC is changing around 49-53M.
But MAC dmg versions is sometimes smaller and sometimes bigger in split files from 3-4 files.


Take care,
Gert

- Get the best with linux -

--- Msged/LNX 6.2.0 (Linux/2.6.39-gentoo-r1 (x86_64))
* Origin: KofoBBS at ftp://fido0.kofobbs.net (2:230/150)

Hello mark!

28 Feb 2016 18:00, mark lewis wrote to Benny Pedersen:

if he used something besides a rolling release that isn't gentoo he
would not have half the problems he does... he would also not have to
ask how to solve the gentoo problems that he has...

lol a rolling raspberry pi 2 would give him more problems then gentoo


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/4.4.3-gentoo (i686))
* Origin: openvpn on its way here (2:230/0)

29 Feb 16 21:36, you wrote to me:

if he used something besides a rolling release that isn't gentoo he
would not have half the problems he does... he would also not have to
ask how to solve the gentoo problems that he has...

lol a rolling raspberry pi 2 would give him more problems then gentoo

no shit?? perhaps he should stick to LTS releases like most other operators and
admins that require stable OSes?? ;)

)\/(ark

Always Mount a Scratch Monkey

... To know the road ahead, ask those coming back.
---
* Origin: (1:3634/12.73)

Hello mark!

29 Feb 2016 22:51, mark lewis wrote to Benny Pedersen:

no shit?? perhaps he should stick to LTS releases like most other operators and admins that require stable OSes?? ;)

LTS like ubuntu phone ? :=)

there is no solution to talented fools


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/4.4.3-gentoo (i686))
* Origin: openvpn on its way here (2:230/0)

01 Mar 16 12:50, you wrote to me:

no shit?? perhaps he should stick to LTS releases like most other
operators and admins that require stable OSes?? ;)

LTS like ubuntu phone ? :=)

no... LTS like ubuntu server...

there is no solution to talented fools

sure there it... hot lead at high velocity ;)

)\/(ark

Always Mount a Scratch Monkey

... Def: Xmas list, item #1: a 48-hour day!
---
* Origin: (1:3634/12.73)

Hello mark!

01 Mar 2016 09:31, mark lewis wrote to Benny Pedersen:

no shit?? perhaps he should stick to LTS releases like most other
operators and admins that require stable OSes?? ;)

LTS like ubuntu phone ? :=)

no... LTS like ubuntu server...

and then we can start talk about malware ?

there is no solution to talented fools

sure there it... hot lead at high velocity ;)

or gaffa tape ?


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.2.0 (Linux/4.4.3-gentoo (i686))
* Origin: openvpn on its way here (2:230/0)

01 Mar 16 20:39, you wrote to me:

no shit?? perhaps he should stick to LTS releases like most other
operators and admins that require stable OSes?? ;)

LTS like ubuntu phone ? :=)

no... LTS like ubuntu server...

and then we can start talk about malware ?

maybe on someone else's system... i've never had any malware or virus infestations on any of my machines... ever...

there is no solution to talented fools

sure there it... hot lead at high velocity ;)

or gaffa tape ?

hot lead is more satisfying...

)\/(ark

Always Mount a Scratch Monkey

... Zen and the Art of Echo Mail: Be the message...
---
* Origin: (1:3634/12.73)