shinji257

ZFS Master may need an update with the current 7.2-rc2 (and rc1 as well but that isn't current now). When this plugin is installed it causes the Unraid Connect icon to disappear on the Main tab. It doesn't prevent it from working in other areas but it is definitely annoying and I had to dig a little to figure out the cause.

Sorry. Been busy with some life stuff. Make sure you have the libjodycode package installed as well. Run un-get installed and send back the output if it still doesn't work. If for some reason they do not appear in the un-get search then you can use these links and install them manually. Make sure to put them in /boot/extra so they get reinstalled on reboot as well https://github.com/shinji257/unraid_pkgs/raw/refs/heads/main/slackware64-current/jdupes/jdupes-1.28.0-x86_64-2_SBo.tgz https://github.com/shinji257/unraid_pkgs/raw/refs/heads/main/slackware64-current/libjodycode/libjodycode-3.1.1-x86_64-2_SBo.tgz

This has been a very useful tool and have it loaded on Unraid 7 as well (it works right? -- hope so). Anyways while it doesn't seem to necessarily break anything I noticed that its portion on the Main page causes a couple of 404 errors to show in the log. Figured I'd let you know in case you didn't already know. Apr 7 06:26:27 Pithos nginx: 2025/04/07 06:26:27 [error] 43564#43564: *483992 open() "/usr/local/emhttp/plugins/dynamix.docker.manager/styles/style-black.css" failed (2: No such file or directory) while sending to client, client: 127.0.0.2, server: , request: "GET /plugins/dynamix.docker.manager/styles/style-black.css?v=autov_fileDoesntExist HTTP/1.1", host: "127.0.0.1", referrer: "http://127.0.0.1/Main" Apr 7 06:26:27 Pithos nginx: 2025/04/07 06:26:27 [error] 43564#43564: *483987 open() "/usr/local/emhttp/plugins/dynamix.docker.manager/styles/style-black.css" failed (2: No such file or directory) while sending to client, client: 127.0.0.2, server: , request: "GET /plugins/dynamix.docker.manager/styles/style-black.css?v=autov_fileDoesntExist HTTP/1.1", host: "127.0.0.1", referrer: "http://127.0.0.1/Main"

Open a ticket so I can add it to the todo list. I'll add it when I get a minute to do so.

I was working to fork NerdTools but I was only planning to support Unraid 7 at this time. From what I could tell from the code it gets the version Unraid currently running and builds that into the url for package downloads so it would be possible to just setup another folder named for the prior version (I think it would be 6.12) and installing NerdTools there would point to an appropriate folder automatically. As for a build system... I've been using lxc with the minimal slackware current environment and adding package as needed. It's a bit of trial and error. Getting errors, figuring out what slackware package has to be installed, and trying the build again.

I've been rebuilding packages to work on Unraid 7.

Many of the packages in the original NerdTools is broken in Unraid 7 because it is based on a newer slackware branch. That's why it is depreciated/unsupported now.

I plan to modify NerdTools to point at a varient of my repo but I need to see how it determined dependencies and file paths so I can get it done properly. Currently been busy with work so have not had much chance to look at it.

Make sure you downloaded the raw file and not just the file link itself. Edit: See a couple of messages up.

Adding packages in /boot/extra allows Unraid to reinstall them (using installpkg) at boot so that they may persist between reboots. You have this correct. 1.) Unraid 7 has a newer GLIB than Unraid 6.12 and since they are built for Unraid 7 (actually Slackware -current) many of them won't work and will throw an error regarding that fact. 2.) This should not impact the packages running on future versions pending compatibility. There is always that risk when running software on the host system that were not included by default. How the files are downloaded are left as an exercise to the end user. There are many ways to go about doing it including the one you mentioned.

For me I started even more barebones but I just used slackbuilds and you can pull packages from slackware-15 directly. I think un-get points at slackware-current by default for the slackware packages repo but you can switch it to slackware-15 instead since you are on 6.12.5. This will at least work for slackware official where vim was sourced from. https://mirrors.slackware.com/slackware/slackware64-15.0/slackware64/ slackware-15 Slacker.it (conraid) builds for slackware-current as well as myself. I'll see about making a slackware-15.0 repo folder for those staying on 6.12.x. My current build environment is actually the Slackware LXC container running on Unraid 7. XD Forgot to address the actual question. If you install it yourself I think Slackware installs all packages. The only packages I actually build are the ones from Slackbuilds since they don't distribute binaries. You would download the source and slackbuilds archives. Unpack the slackbuilds archive, place the source archive in the same folder and run the SlackBuilds script. It's a shell script and should automate everything. Note any errors and try to resolve them. They actually target slackware-15

Sorry my repository targets and requires Unraid 7 as it was created in response to NerdTools depreciation on that version. I don't currently have packages built for Unraid 6.12.

Ahh. Then I at least have to note that libsodium is a dependency on my packages list. This is the type of stuff I need to know since I don't yet know where to look on the slackware repos for package dependencies.

Hmm. I got an email notification that someone has an issue with vim but seems reply might be deleted? If you are still having issues let me know either here or open an issue on my repository and I'll look into it. Edit: My vim package is the same as the one from slackware-current as I just copy theirs rather than rebuilding it. Pretty sure there are no other builds of vim by default but still let me know if you have issues and post any errors you are getting.

Just want to say thank you for your work on this. I've setup a Slackware lxc container (for my repository work since it is on -current) and a Debian container for other stuff. I also found information on the config file setup and managed to have it create a dev/shm automatically for Slackware (one doesn't exist by default and is needed for certain things) and mount a host folder on Debian.