Hello All!

I failed to compile fastlst for FreeBSD.

What is the actual status of fastlst?

I'm not sure if i need a V7 nodelist but a tool for diff handling should be minimum.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

Friday June 30 2023, Kai Richter wrote to All:

I failed to compile fastlst for FreeBSD.
What is the actual status of fastlst?

I don't see any reason to support it.

I'm not sure if i need a V7 nodelist but a tool for diff handling
should be minimum.

Why do you need diffs? The full nodelist is not big now and hard drives have much more capacity than 25 years ago. If you still want to use diffs, you may use nlupd from nltools.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20230221
* Origin: Moscow, Russia (2:5020/1042)

Hello Michael!

30 Jun 23, Michael Dukelsky wrote to Kai Richter:

What is the actual status of fastlst?

I don't see any reason to support it.

How about "i have an existing setup and i'm lazy to configure another tool"?

;-)

I'm not sure if i need a V7 nodelist but a tool for diff handling
should be minimum.

Why do you need diffs?

Why do i need fidonet? Diffs are the traditional way of nodelist distribution. And diffs are documents of history, who joined and who left fidonet.

The full nodelist is not big now and hard drives have much more
capacity than 25 years ago.

True but the "why do we need" question should be still there. Why do we need to transport 170kB if we need to change 3kB only? Why should we drop an efficient way of data distribution that was working well for 25+ years.

I do understand that we do not have the resources to migrate all ftn software to the latest plattforms. But i don't see the need of dropping working concepts.

If you still want to use diffs, you may use nlupd from nltools.

Found and i will take a look.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

Sunday July 02 2023, Kai Richter wrote to Michael Dukelsky:

What is the actual status of fastlst?

I don't see any reason to support it.

How about "i have an existing setup and i'm lazy to configure another tool"?

Laziness is sacred. How about "I'm lazy to support another tool"? :-)

I'm not sure if i need a V7 nodelist but a tool for diff
handling should be minimum.

Why do you need diffs?

Why do i need fidonet? Diffs are the traditional way of nodelist distribution. And diffs are documents of history, who joined and who
left fidonet.

That's right. So, you may receive diffs and store them for history. And at the same time you may use a full nodelist, since that does not require to build full nodelist from the previous nodelist and a diff. Such a build is potentially error-prone if a nodelist or a diff is missing.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20230221
* Origin: Moscow, Russia (2:5020/1042)

Hello Michael!

02 Jul 23, Michael Dukelsky wrote to Kai Richter:

What is the actual status of fastlst?

I don't see any reason to support it.

How about "i have an existing setup and i'm lazy to configure
another tool"?

Laziness is sacred. How about "I'm lazy to support another tool"? :-)

I'm not sure. Sometimes i wished i could get rid of my laziness. But you are perfect fine. I understood above "I don't see any reason for anyone to support it." and i had/have no intention to motivate you or anyone to support fastlst. Especially for the FreeBSD platform.

Why do you need diffs?

Why do i need fidonet? Diffs are the traditional way of nodelist
distribution. And diffs are documents of history, who joined and
who left fidonet.

That's right. So, you may receive diffs and store them for history.
And at the same time you may use a full nodelist, since that does not require to build full nodelist from the previous nodelist and a diff.

It would work but it's against my line ot thought. Why should i buy 60 pots when one pot will do it's job perfectly? Use of 60 times more resources for a job is a sign of the global throw-away society. I know - the resources required to maintain fastlst would outnumber the savings of the reduced transportation resources. The sad thing is i couldn't learn C languages within my remaining lifetime. But even with laziness there is progress. Slow, but

% ./nlupd
nlupdate/fbsd 1.9 2023-02-24
Could not find Config-file

Ooops? I said slow. ;-)

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

Sunday July 02 2023, Kai Richter wrote to Michael Dukelsky:

% ./nlupd
nlupdate/fbsd 1.9 2023-02-24
Could not find Config-file

As usual, you need to provide the path to the configuration file either in the FIDOCONFIG environment variable, or with the "-c" option. Also see man nlupdate.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20230221
* Origin: Moscow, Russia (2:5020/1042)

Hello Michael!

02 Jul 23, Michael Dukelsky wrote to Kai Richter:

nlupdate/fbsd 1.9 2023-02-24
Could not find Config-file

As usual, you need to provide the path to the configuration file
either in the FIDOCONFIG environment variable, or with the "-c"
option. Also see man nlupdate.

There is no config, yet. I'm just too lazy to do the configration.
Migration from the linux node shouldn't be that difficult.
My priority is to build all required software first.
If there is no replacement like nlupd for fastlst then the whole migration is in question because i can't fix broken software.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hi Michael!

Sunday July 02 2023 17:40, you wrote to Kai Richter:

% ./nlupd
nlupdate/fbsd 1.9 2023-02-24
Could not find Config-file

As usual, you need to provide the path to the configuration file either in the FIDOCONFIG environment variable, or with the "-c" option. Also see man nlupdate.

JFYI

[fido@brorabbit ~]$ hptlink --help
hptlink/lnx 1.9 2023-01-07

Usage: hptlink [options] [areaname ...]
Options: -t - build reply TREE
-s - do not use Subject
-a - search in all messages (for singlethread only)
-r - do not use REPLY:/MSGID:
-n - link with 'new' messages only ('new' from last linked + 1) [fido@brorabbit ~]$ hptlink -t crimea.talk
hptlink/lnx 1.9 2023-01-07

Could not find Config-file
[fido@brorabbit ~]$ hptlink -c ~/etc/hpt.cfg -t crimea.talk
hptlink/lnx 1.9 2023-01-07

Usage: hptlink [options] [areaname ...]
Options: -t - build reply TREE
-s - do not use Subject
-a - search in all messages (for singlethread only)
-r - do not use REPLY:/MSGID:
-n - link with 'new' messages only ('new' from last linked + 1)

Would you be so kind to add "-c" option?

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hi Stas.

hptlink/lnx 1.9 2023-01-07

Usage: hptlink [options] [areaname ...]
Options: -t - build reply TREE
-s - do not use Subject
-a - search in all messages (for singlethread only)
-r - do not use REPLY:/MSGID:
-n - link with 'new' messages only ('new' from last
linked + 1)

Would you be so kind to add "-c" option?

Please update. :)

=== Cut ===
hptlink/lnx 1.9 2023-02-24

Usage: hptlink [options] [areaname ...]
Options:
-c <config> - config file
-t - build reply TREE
-s - do not use Subject
-a - search in all messages (for singlethread only)
-r - do not use REPLY:/MSGID:
-n - link with 'new' messages only ('new' from last linked + 1) === Cut ===

'Tommi

---
* Origin: - rbb.fidonet.fi - Finland - (2:221/6)

Hi Tommi!

Monday July 31 2023 10:51, you wrote to me:

hptlink/lnx 1.9 2023-01-07

Usage: hptlink [options] [areaname ...]
Options: -t - build reply TREE

[...skipped...]

Please update. :)

=== Cut ===
hptlink/lnx 1.9 2023-02-24

Usage: hptlink [options] [areaname ...]
Options:
-c <config> - config file

Thanks.

Have a nice night.
Stas Mishchenkov.

--- Have You daily sexual life? Hide it proper from Your wife! ;)
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)

Hello Michael!

31 Jul 23, Stas Mishchenkov wrote to Michael Dukelsky:

As usual, you need to provide the path to the configuration file
either in the FIDOCONFIG environment variable, or with the "-c"
option.

Some mails before:

If neither "-c" command line option, nor FIDOCONFIG environment
variable is defined, then the fidoconfig location is given by CFGDIR
and CFGNAME defined in huskymak.cfg during compilation.

I think that's a good usual default.

$ hptlink -t crimea.talk hptlink/lnx 1.9 2023-01-07

Could not find Config-file
Would you be so kind to add "-c" option?

And fix the usual default config detection first? ;-)

Btw, is the config file detection part of every individual module or is it a centralized fidoconfig function?

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai,

Tuesday September 19 2023, Kai Richter wrote to Michael Dukelsky:

As usual, you need to provide the path to the configuration file
either in the FIDOCONFIG environment variable, or with the "-c"
option.

Some mails before:

If neither "-c" command line option, nor FIDOCONFIG environment
variable is defined, then the fidoconfig location is given by
CFGDIR and CFGNAME defined in huskymak.cfg during compilation.

I think that's a good usual default.

$ hptlink -t crimea.talk hptlink/lnx 1.9 2023-01-07

Could not find Config-file
Would you be so kind to add "-c" option?

And fix the usual default config detection first? ;-)

It was fixed in hptlink in February AFAIR.

Btw, is the config file detection part of every individual module or
is it a centralized fidoconfig function?

It is defined in fidoconfig library and used by all programs.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20230926
* Origin: Moscow, Russia (2:5020/1042)