For Slackware 15.1 I hope there would be two versions of stable ISOs: one original version and one with all package updates applied. Currently we have to set up Slackware 15 and then update the system, it would be lovely if all that could be done in one go.

-- ltlnx

1 members found this post helpful.

You spect new isos every time slackware provide a new security update ?

I think that never succes ...fresh install and apply the patches..as ever.

2 members found this post helpful.

success !

strange cause i request same thing some time back , but ignored , now it happend and im happy.

with this , projects using cmake as built tool can see now zstd.

1 members found this post helpful.

Per previous poster, that's not a small ask.

Of course, you can make such an iso for yourself if/when you require it.

1 members found this post helpful.

Although updating an ISO every time a patch is issued would be a lot of work, having a periodic (once every few months?) update of an ISO to include patches-to-date would probably be handy for some users.

Personally, I manually apply patches, and keep the original 15.0 ISO and all downloaded patches, so I can apply all patches without having to download anything again. But for people setting up automated upgrades, having a recent starting point instead of a 2-year-old starting point would substantially reduce the patches that are needed when doing a complete reinstall.

3 members found this post helpful.

Or during installation fetch and install packages from remote repositories instead of the ones on the ISO if newer.

2 members found this post helpful.

USARIONUEVO: Curious if you provided a solution (a slackbuild) or it was just a request?

Pat: Thank you! If you want to take qt6 off my hands, I think it will save users a long build time. I think I have the build in a good spot now, so it should be easy to just version bump it. https://slackbuilds.org/repository/15.0/libraries/qt6/

I also have no idea why Slackware's version of clang fails to build and we need to bootstrap ubuntu's clang. My guess is a configuration option in our version of clang? More info in the README.SLACKWARE.

Was curious to see how much time it would save.

So, did all of the following on my slowest machine which is an Intel DualCore with 8GB of RAM
and to the oldest/slowest HDD I have which is a circa 2000 250GB drive.

Did a 100% complete install of slackware64-15.0 from its original DVD dated 2022-02-02

Booted to the new install, picked a mirror for /etc/slackpkg/mirrors, made a script with these 4 lines.

--- slackup.sh ---
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system
_______________________________


root@glennmcc:/# time ./slackup.sh

real 38m6.669s
user 22m48.668s
sys 8m44.589s

___________________________

A few min more to update the boot loader
and reboot to the fully updated system
puts it at probably a grand total of 45min.

______________

On my i7 machine with 32GB of RAM and a brand-new 1TB HDD....
probably a grand total of less than 30min for all of the patches.

(BTW... there are currently 85 patches plus 5 more in the directory with the updated kernel)

Which one? podman on SBo has version 1.6.2, from 2019, not exactly new.

For why podman working with cgroupsv2 is better, perhaps, see https://rootlesscontaine.rs/getting-...ommon/cgroup2/ . This should allow limiting access to cpu, cpuset and io "controllers".

Also, podman stats should give better output with cgroupsv2. (I.e. should work in rootless mode.)

Unrelated to podman, but the parameter "memory.min" is not available on cgroupsv1, but I think it is very useful, to be able to set memory protection for critical processes.

on that page I'm reading this bit

I think that is permission related, not software-related. I.e., there is a permission to use those controller namespaces, which systemd can grant on user login. I think it should be possible to create "user slices" manually, and let cgroupfs with cgroupsv2 manage the controllers.

I might be wrong, of course, but properly investigating this would still require a fresh libcgroup, so that standard cg-related commands, such as cgcreate would work with v2 groups.

UPD: let me try to phrase this differently. SystemD itself is a cgroup management process. I suspect that it supports delegating those controllers to non-root users in recent versions, which is why that page is claiming "need for a recent systemd". When the cgroup management backend is not systemd, but cgroupfs (with libcgroup), I think that that requirement does not apply (at least not directly).

I might be wrong, of course.

freerdp 2.11.1, it contains a fix for a regression in 2.11 that broke connections to old windows 2008 rdp server.

I'm using 4.x, and just upgraded to 4.6.2. I use rootless containers, but I'm not using any of the limiting functionality.

It was a request here 09-14-22, 06:21 PM

https://www.linuxquestions.org/quest...ml#post6380210

and my explanation to the change ..

https://www.linuxquestions.org/quest...ml#post6380243

The important thing is that happen now , happy with this change , thats all.

Also elogind itself is a cgroup management process. Is it compatible with these cgroups v2?

Please note that I have nothing against migrating fully to systemd to have full cgroups v2 support.