I would like to request for Slackware to stick with the 140 ESR branch of Firefox until its EOL date on September 15.

1 members found this post helpful.

Also requesting Ristretto, the official Xfce image viewer.
I think Xfce needs more love, there's plenty of stuff already available for KDE after all...

8 members found this post helpful.

And after that, give up firefox if it doesn't build on 32 bits?

You mean giving up on it also on Slackware64? Seems a bit extreme to me but what do I know.

IDK if this has been reported before.
If FF uses client-side decorations, KWin crashes while cycling windows with alt-tab on AMD Radeon graphics hardware.
Deactivating the stupid client-side decorations and reactivating Firefox's title bar is a workaround.

1 members found this post helpful.

Seconded, I haven't tested --Current but I would have hoped by now the installer would install GRUB2.

Also I am voting again for consideration of COSMIC desktop, or maybe it can just be added to /extra .

I use for xfce pure installs ...plus file-roller for graphical manage of compressed files.

Slackware is installing the following crontab files:

Why not make man-db, logrotate, and mlocate .new files for consistency?

Also, I suggest a small reform for the cron files.

Instead of using "run-parts", which is not terribly pleasant, because runs all scripts together and mails the output lumped in a single file, I would propose installing "individual crontabs" per service into /etc/crontabs/ and making symlinks for them into /etc/cron.d/

This way, /etc/cron.daily/dehydrated.new, which is currently
Would be transformed into /etc/crontabs/dehydrated.new
and a symlink: /etc/cron.d/dehydrated -> /etc/crontabs/dehydrated

Switching services on/off will be done by removing the symlink. This way we are getting nice names for the cron jobs (dehydrated instead of run-parts), can adjust starting time for each service, instead of running them all together, and would not have to edit systemwide crontab (a fragile operation) to adjust cron jobs, relying on the standard UNIX model of "everything is a file" (even a cron job) in a dedicated directory.

2 members found this post helpful.

Seconded. Maybe it could even replace geeqie? Lightweight but functional. With libheif installed, ristretto also handles heic/heif.

3 members found this post helpful.

Even better would be some kind of "my defaults" "mode" when some kind of "all defaults" configuration file on the installation media has been customized. It would also be nice if this configuration would allow to still ask for some settings like hostname or static IP address.

However, the manual work of the installation is not limited to answering questions by the setup scripts, at the post install step there is also a lot of questions asked by scripts in var/log/setup. Those scripts can be replaced by custom packages to not ask any questions, so it would also be nice if the setup by default also looked for custom packages in some directory/directories.

One more thing to consider is that before setup is run the disk should be partitioned, most users would probably like to being offered a default partition layout but still being able to make a total custom partition layout if they are configuring something like a dual boot system. Again, it would be nice if that default partition layout configuration file/script would be easy to customize on the installation media.

I usually customize my Slackware installation media to hard code my preferences into setup and post install scripts. I also have a script that at boot of installation media partitions the disk before running my customized setup scripts.

If the setup scripts were written to look for custom settings by default and those settings were stored in files on the .iso image rather than within initrd it would be much easier to customize the installation to "few questions asked".

regards Henrik

1 members found this post helpful.

I think all defaults can serve more than one purpose. I like and agree with you here, but when I suggest all defaults, my main focus (my request) is for users who just want the "official out of the box, I don't have to do anything, 'defaults' that are supported / recommended by Patrick." So to that end it would stand to reason that some kind of automated, "partition, and format " would be done in accordance with that.

When I go through the installer as we have it now, I see things like 'RECOMMENDED' in the options of pkgtools setup.
I imagine, for example, the RECOMMENDED selection for network selection is to use 'NetworkManager' -- I don't claim to know this for a fact, however. That said I think in the spirit of the current installer (assuming I understand the spirit of the current installer) RECOMMENDED should be added. So my request is, take all these 'RECOMMENDED' selections, and turn them into a "all defaults".

1 members found this post helpful.

When using dracut it outputs this message twice:

After booting up my system I then get dropped to a dracut debug shell.

Appending systemd-pcrextend and systemd-pcrphase to the omit_dracutmodules variable in /etc/dracut.conf.d/omit_systemd_modules.conf fixed the issue.

1 members found this post helpful.

Since we've already added qemu, I'd like to suggest podman and libvirt.

They're both maintained on SBo by two members of the Slackware development team as well (Mr. Batts and Mr. Workman).

3 members found this post helpful.

podman was updated by me 3 years ago as VBatts is busy with other things
libvirt was updated by Ponce mostly

2 members found this post helpful.

Ah, my bad.

I went off the names listed on the SBo pages for them.