Virtual Private Server (VPS) Hosting provided by Central Point Networking cpnllc.com
For some reason, the "Nodelist" and "Recent Callers" features are not working.
| Sysop: | Ray Quinn |
|---|---|
| Location: | Visalia, CA |
| Users: | 60 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 64:07:26 |
| Calls: | 12 |
| Files: | 12,938 |
| Messages: | 99,115 |
Check out the US 99 menu above for links to information about US Highway 99, after which the US 99 BBS is named.
Be sure to click on the Amateur Radio menu item above for packet BBSes, packet software, packet organizations, as well as packet how-to's. Also included is links to local and some not-so-local Amateur Radio Clubs.
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.
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'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.
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.
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'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.
This will I see if I can do next time for the pascal files.
* 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'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.
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.
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.
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.
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.
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??
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.
There is normal 2 versions of Doomday Engine.week
dde200 is version 2.0.0 build and it comes out from author 3-4 times a
where I then only will send it out once a week.
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.
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...
You cannot use the SAME filename for two different files.
Definitely :) There is no reason to use the same filename for any
file.
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.
Everytime I moan and bitch about this Ron says "Geez, Cut the Link"..
18 Jan 2016 11:38, Janis Kracht wrote to Gert Andersen:
You cannot use the SAME filename for two different files.
how did bbbs handle this inbound ?
got you :=)
It didn't get that far <g>
It didn't get that far <g>
if Gert just used Windows 98 and BBBS there he would not have to ask
how to solve all gentoo problems :=)
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...
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?? ;)
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
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 foolssure there it... hot lead at high velocity ;)
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 ?