Wayland in forum distros

[Clarity]

There has been movement is EACH of the forum area among distro builders in 2024-2025. These distros, operationally, are stable in my findings in testing the.

Teh KL distros are stable, the Woof CE distros are solid, @mistfire has produced a solid implementation and others are forthcoming in the coming months from the varied forum developers.

There is a Youtube tester who is well-known who has been critical to a feature that he feel is overdue. So much so, that he has made 2 videos addressing the feature during the past 24 hours. One is about plasma,while his other relates to SDDM in desktop manager use. For those developers who are interested, they are here:
https://www.youtube.com/watch?v=Gq8Oo_CUq_A
https://www.youtube.com/watch?v=gPUWfVew7lI

FYI

[Wiz57]

I don't know if Wayland is the over-riding development in Linux yet or not. X still has quite a large presence.
Something I've been experimenting with just the last week is the "overlay" union file system as an option to AUFS. There have been a few problems of late with AUFS, but overlay may offer a long term alternative.

[mistfire]

I don't know if Wayland is the over-riding development in Linux yet or not. X still has quite a large presence.
Something I've been experimenting with just the last week is the "overlay" union file system as an option to AUFS. There have been a few problems of late with AUFS, but overlay may offer a long term alternative.

X11 is being abandoned due to the following reasons:

1. no active upstream maintainers
2. complex implementations
3. lack of security features
4. no longer fitted on modern gpu implementations

Wayland development these days was significantly fast. It has simpler and faster graphics implementations, and it has security features.

AUFS was still third-party due to the complexity of the aufs codebase.

Overlayfs can still be used on Puppy, however some sacrifices must be made:

1. Abandoning ramdisk caching (odd-numbered pupmode for now)
2. Abandoning on-the-fly SFS module loading. (Although there is a partial overlayfs implementation for loading SFS modules on-the-fly)

[dimkr]

1. Abandoning ramdisk caching (odd-numbered pupmode)

What do you mean? I did all the necessary adjustments, PUPMODE 13 works just fine and so does copying of SFSs to RAM. Only difference compared to aufs is that files are not deleted from pup_rw after saving to pup_ro1, because overlay forbids changes to lower layers.

[mistfire]

Only difference compared to aufs is that files are not deleted from pup_rw after saving to pup_ro1, because overlay forbids changes to lower layers.

However it quickly fill the ram since it wasn't deleted on pup_rw. That's why abandoning the odd pupmodes on overlayfs is a better choice for now unless the developers of overlayfs gave an option for on-the-fly branch changes.