KvE> I know what you did in the past with makenl and I appreciate that very
 KvE> much.

   Thank you.

 KvE> But, you and Ward are using features, that do not exist in the unix
 KvE> version.

   I'm sorry to hear that. The last version I left behind was 3.141 -- I was
working my way down PI...  8-)

 KvE> Janis as well I run manknl on a unix system.

   Well, *my* last contribution worked the same with MSDOS, Windows, unix,
linux, Amiga SAS and a lot of other OSs that I cant remember, but my make file
was written in cooperation with Jamnntp author Johan Billing, and we spent a
lot of time to create one single, universal make file that would work on almost
 any environment.

   Once again, I'm sorry to hear that the guys that took over Johan's and mine
project lost some, if not all, that universal functionality.

 KvE> a file is file name. Most region updates are distributed as filename.XXX
 KvE> where XXX is the daynumber for the coming friday.

   And that, in my mind, is a huge mistake. Ever since I first used MakeNl as
2:203/0 in 1991 (I think) I've always used the password.UPD approach. It wasn't
 until I became RC20 that I had to start using the daynumber approach. Alas,
I've only had a few glitches along the way, but I still think that the password
 approach is much safer.

 KvE> But that does not matter, it
 KvE> will be put in the master directory with the daynumber of the the
 KvE> publishing day.

   So what?

 KvE> In windows as well a in Unix, you can use filename.upd or whatever. What
 KvE> makenl will do with when it is moved to the master directory,

   It's not moved to the main directory if you configure it properly, it's
moved to this directory:

update .\tmp

 KvE> is as above,
 KvE> dat the daynumber of the publishing day. So you get a file with the name:
 KvE> filename.upd.128 if today was the publishing day.

   ???  I've never ever seen something so outlandish a hypothetical situation
happening here.

 KvE> What happens in windows/dos, is the OS cannot handle two dots in a
filename

  Of course Windows, as well as it's DOS emulation, can handle two dots! I have
 media files that have more than a dozen dots in them. How long ago was it that
 you used Windows...?  8-)

 KvE> If it should work as you say, then there
 KvE> is a definit bug in the makenl code.

   If that is so, the bug must have been introduced after I left it. But I
highly doubt it, because that part of the code should never need to be changed
IMHO.

 KvE> Well I did, and using a * in the CTL file as some do, also creates havoc
 KvE> on systems that do not limit how the filename is structured.

   Well, *that* does not surprise me a bit. I bet that option is not in the
default config file or the DOC file

 KvE> Your turn Sir.

   <pong>



..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
 * Origin: news://eljaco.se (2:203/2)