I have made a little video of q4os raspberry test on Pi5: (based on test release 3)
https://youtu.be/pgrMvIIgfVs
Nice video. Q4OS + Pi 5 team up very well. Pi 4 is just a bit too slow for me to work on it all day. Your tempting me to buy a Pi 5 which in all honesty, I don't need. (I revived too many old PC's already thank to Q4OS!)
Now I'm gonna try the next test version (4) for Pi.
]]>Yes, this is a very good guideline for optimising a q4os installation. In fact, this was my main reference when I started to work on my qperf script, I found some other optimisations to do, but there are some very good ideas here
I've got a question for you vanquishedangel, about the prelink and execstack part. Did you success using these tools on a bookworm installation, and is it relevant for bookworm in first place ? (don't know why not, but I notice you can't find these tools too for bookworm)
Sorry I was on vacation to spain/paris/amsterdam and did not see this until now. Also I lost my chromebook in amsterdam and I am trying to get it back from TSA lol. Anyway yes I was able to use them in bookworm. Some places may say that it is not relevant due to newer parts of the kernel handling the task however, the benefit was in reducing memory usage.
]]>I notice that iwd.service is running, and so is wpasupplicant.service. I did not enable these manually.
Hope this helps somebody somewhere.
]]>