On 9/18/2024 at 3:09 PM, jsavargas said:

I modified the fork I had of nerdtools in my git and I plan to keep it, if anyone wants the plugin address, ask me, while squid ls changes in the CA

Do you have a public link to your fork? I wouldn't mind taking a look and seeing what it would take to contribute and help support.

nmap: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

 

It seems nmap is looking for some OpenSSL 1.1 dependencies while Unraid 7 is using version 3.

Edited December 12, 20241 yr by remati

20 minutes ago, remati said:

nmap: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

 

It seems nmap is looking for some OpenSSL 1.1 dependencies while Unraid 7 is using version 3.

you may need to 3rd party downlad that tool and/or the lib file...

https://slackware.pkgs.org/15.0/slackware-x86_64/nmap-7.92-x86_64-1.txz.html

 

cd /boot/extra
wget https://slackware.uk/slackware/slackware64-15.0/slackware64/n/nmap-7.92-x86_64-1.txz

#you will need to remove or uninstall the other nmap in the boot extra folder

Edited December 12, 20241 yr by bmartino1
wrng package type needs x86_64

I just tried locating NerdTools in CA but I was not able to do it, was it removed?

7 hours ago, palakmar said:

I just tried locating NerdTools in CA but I was not able to do it, was it removed?

Yeah myself I got a notification it's no longer compatible with 7 rc... Darn!

On 9/22/2024 at 1:37 PM, Rysz said:

 

Why not just use the pre-compiled binaries, they are bundled with all the dependencies.

I just tested all the -glibc versions on 7.0 beta and they work just fine...

https://github.com/borgbackup/borg/releases

 

Just get it via wget and put into /boot/extras? didn't work for me. Which version did you load exactly?

You can't just use any linux package, it needs to be specific to Slackware15.

 

Here's a link to the packages distro:

 

http://slackware.cs.utah.edu/pub/slackware/slackware64-current/slackware64/

 

But borgbackup is not there, you'll have to either find the right package, or compile and build the package yourself.

 

To build it yourself you can just use SlackBuilds.org:

 

https://slackbuilds.org/repository/15.0/system/borgbackup/?search=borgbackup

18 hours ago, shpitz461 said:

You can't just use any linux package, it needs to be specific to Slackware15.

 

Here's a link to the packages distro:

 

http://slackware.cs.utah.edu/pub/slackware/slackware64-current/slackware64/

 

But borgbackup is not there, you'll have to either find the right package, or compile and build the package yourself.

 

To build it yourself you can just use SlackBuilds.org:

 

https://slackbuilds.org/repository/15.0/system/borgbackup/?search=borgbackup

Yeah, thats why I am asking. Atm I use the "fat binary" for borg. This is working in general, and I don't mind the 26Mb. I am actually looking for a simple was to have this binray in unraid after boot. Right now I have a user script that get's the latest stable, checks the signature and puts it in /usr/sbin ... not very elegant but ok for now.

honestly, I think borgbackup may be better maintained via the python 3 for unraid plugin and running borg backup via Python and the repo:

https://github.com/borgbackup/borg/releases/tag/1.4.0

run borg for a venv form unraid host

https://borgbackup.readthedocs.io/en/stable/installation.html#using-pip

 

At lease with the python implementation its replacement unzip or use pyinstaller to pip upgrade borg for its use case and calls...

Edited December 22, 20241 yr by bmartino1
data - typo

is the nerdtools plugin even needed if you don't use the default included packages?   it's just a matter of finding compatible slackware packages and dropping them into /boot/extras right?

39 minutes ago, oliver said:

it's just a matter of finding compatible slackware packages and dropping them into /boot/extras right?

Yes. 
 

but be aware that the version of package that is compatible could change for future Unraid releases in case you encounter problems after any upgrade.

For someone that is new that maybe a bit more complicated.  

10 hours ago, palakmar said:

For someone that is new that maybe a bit more complicated.  

 

if copying packages to /boot/extras/ is complicated, you have no business using something like nerdtools to begin with

3 hours ago, oliver said:

 

if copying packages to /boot/extras/ is complicated, you have no business using something like nerdtools to begin with

To expand on this a bit for anyone who is new, installing additional packages on the unraid host (regardless of the method) is not recommended. Functionality not built into unraid is meant to be achieved in Docker or a VM, leaving the host os unmodified. While it may feel like added complexity for those used to linux, it serves the purpose of insulating unraids stable core functionality from user applications.

^^^

 

And that is the entire reason why I will not take over the maintenance / updates on this plugin.  I don't believe in the entire concept of it.  I've only kept it published as people would complain about it's disappearance.  But, since there are no takers on anyone wanting to maintain it, it is going to die its death that should have happened a long time ago.

On 12/26/2024 at 12:11 PM, Squid said:

^^^

 

And that is the entire reason why I will not take over the maintenance / updates on this plugin.  I don't believe in the entire concept of it.  I've only kept it published as people would complain about it's disappearance.  But, since there are no takers on anyone wanting to maintain it, it is going to die its death that should have happened a long time ago.

I'm conflicted. I agree but it seems to fulfill a purpose for some. I have used it myself when doing dev work, though now I mostly use different methods. I doubt most people use it for development so I wonder exactly what others use it for that isn't suited for plugins and docker containers.

I don't know. There just seems to something missing that this plugin helps alleviate, that doesn't fit well with the current plugin/docker model. If that can be addressed, then maybe this can die.

I agree that the Nerd Tools plugin should be deprecated. However, I also believe the "extra" folder should be maintained for those who prefer to manually install third-party applications on Slackware. From the Nerd Tools plugin, the only truly useful application I noticed was screen. The rest can be managed using Python virtual environments or other system setups.

 

A better approach would be to set up a VM with the current Slackware version and use its package manager to get the latest program updates, precompile binaries, and pull necessary dependencies. From examining the Nerd Tools GitHub repository, it appears to implement some questionable methods that I wouldn't trust on an Unraid host. While I do use some third-party Slackware packages, I ensure they are precompiled binaries, and I actively monitor their sources for updates and CVEs. Due to the potential risks, I wouldn't rely on any Nerd Tools application for production use.

That said, there's nothing inherently wrong with using older versions, as long as users understand that these may rely on libraries or other Slackware core components that may no longer exist in Unraid.

 

I appreciate Rysz for maintaining a Python 3 virtual environment plugin, which provides some functionality at the host level. However, 90% of the tools Unraid offers are already available in Docker form. In my opinion, much of the desire to run applications at the host level comes from misconceptions about folder passing and usage inside Docker containers, as well as concerns about Docker’s resource overhead.

 

As long as the "extra" folder for third-party installations remains and the Python 3 plugin continues to be supported, I see no issue with Nerd Tools being deprecated. Most modern applications, such as BorgBackup, are already designed to run within a Python environment.

 

I’d suggest creating a LXC/Docker container instead of using a plugin. The container could allow users to manage packages via the web UI, providing options to curl, download, install, and delete applications. This approach would ensure that packages and precompiled applications come directly from their maintainers, who are responsible for updates and addressing bugs or CVEs. This would be a cleaner, more secure solution compared to the current implementation. 

As I debated on remaking this reviewing the github but found that to be weird and not well organized/maintained. So a full rewrite would need to be done. At that point looking what the end result as I'd prefer to have the client/end user find the 3rd party application and its repo. and have the plugin web ui curl/wget the link / file into the extra fold where one can easily remove or add a link and update packages. Something that the webui can show version to help. Other scripts can be run to ad repos but that a pipe dream. More due to Slackware not getting repos and building the latest version of some applications. Something I abanded as it was easier to go find the latest pre compiled binary if it existed and give them a script to cd to the extra folder and curl/wget download... thus I never worked on it and decided to remove it from my task as I found it to be unnecessary...

Most can be found here:
https://packages.slackware.com/

https://slackware.pkgs.org/
Lookgin for a pre compiled binary for x86_64 ...
As then its on the user to install maintain and watch for updates.

The point end users should use other means to acomplish this in a supported matter. either a docker vm LXC or python script.

I usual use https://pkgs.org/download/vlc vlc for example

and search for a package i'm looking for at the top right in the search bar then scroll down and go to 

 

this gives me quite a bit of data on the package and the ability to grab the lattest binary and known repo...

Should a plugin do this for you NO! its up to the end user to install and maintain 3rd party application not found in unraid!

Thanks for the updates/info, I have removed nerdtools and manually installed slack packages for screen and powertop into /boot/extras...those were the only two things I really needed anyway.

On 1/2/2025 at 1:15 PM, planetwilson said:

Thanks for the updates/info, I have removed nerdtools and manually installed slack packages for screen and powertop into /boot/extras...those were the only two things I really needed anyway.

 

Does this mean, any files added into /boot/extras will automatically boot on startup of the server, or are you having to run a script to install these manually on boot?

4 minutes ago, thatja said:

 

Does this mean, any files added into /boot/extras will automatically boot on startup of the server, or are you having to run a script to install these manually on boot?

Yes slackware packages are loaded at boot from the extras die.

Since this plugin is depreciated I've started to build my own Slackware packages using SlackBuild scripts.  They are being uploaded to a github repository for anyone to use.  Send me a message if you want the link as I do not know if I can post it here.  Requests are accepted.

 

I'm also going to rebuild the packages from NerdTools so they are as up to date as SlackBuild has them. 

Hi, has anybody managed to use the package auditd (audit-3.0.7-x86_64-2_SBo_UES.txz) ?

Audit relies on functions included in the Slackware sysvinit package for the startup script.  I've grabbed the package and cleaned it a little for unraid so it doesn't bother to create redundant rc.[1-6] folders in /etc/rc.d.  It focuses on /etc/rc.d/init.d and the /etc/init.d symlink + dependent binaries.

 

And yes it works once that is included.

Thanks for the warning @Squid

Thanks to your update assistent I know I'll need to wait a bit to upgrade to Unraid 7 until there is a proper NerdTools replacement

 

Hopefully we'll have one soon in the apps page! 

20 minutes ago, LinkinsRepeater said:

until there is a proper NerdTools replacement

That's unlikely to ever happen, you'll have to manually put your packages in /boot/extra.