A new foundation for TUXEDO OS: Switching to Debian: Many users have noticed that we have reduced our update cadence over the past few months, particularly with regard to Plasma updates. While Plasma 6.7.x is already available, TUXEDO OS is currently ...
This seems like slop for all the Ubuntu haters, but i agree moving to testing isn’t a good sign.
TBH while I like the hardware of my laptop, I’ve been pretty unimpressed by the software that Tuxedo provide.
While i appreciate not having snaps by default, the control center they ship is an electron app that requires /tmp be executable out of the box, and talks to a backend daemon that wasn’t particularly secure by default, and both live in /opt despite coming from the distro itself, so I think it’s ironic when people engage in technical sneering while throwing stones from within their glasshouses.
Also boot security doesn’t seem to be a priority for them out of the box, this seems like what they should focus on IMO, instead of switching their base
✘ CET OS Support: Unknown
✘ Linux kernel lockdown: Disabled
✘ Linux kernel: Tainted
✘ UEFI secure boot: Disabled
That it’s good enough as a distro, although I’ll probably just switch to neon if Tuxedo move to a rolling release base.
Can one adopt Debian SID and automate this? I mean, how difficult would it be for a person not looking to create and maintain a distro but use Debian SID and pull the latest and greatest security patches?
Interesting. They are concerned about security updates delay, but then there is this: https://www.debian.org/doc/manuals/securing-debian-manual/ch10.en.html#security-support-testing
Basically, it says that testing gets security updates later than stable and unstable.
This seems like slop for all the Ubuntu haters, but i agree moving to testing isn’t a good sign.
TBH while I like the hardware of my laptop, I’ve been pretty unimpressed by the software that Tuxedo provide.
While i appreciate not having snaps by default, the control center they ship is an electron app that requires /tmp be executable out of the box, and talks to a backend daemon that wasn’t particularly secure by default, and both live in /opt despite coming from the distro itself, so I think it’s ironic when people engage in technical sneering while throwing stones from within their glasshouses.
Also boot security doesn’t seem to be a priority for them out of the box, this seems like what they should focus on IMO, instead of switching their base
✘ CET OS Support: Unknown ✘ Linux kernel lockdown: Disabled ✘ Linux kernel: Tainted ✘ UEFI secure boot: Disabled
That it’s good enough as a distro, although I’ll probably just switch to neon if Tuxedo move to a rolling release base.
The thing is Neon could die at any moment thanks to KDE Linux.
Using
debsecanto pull security updates fromsidandexperimentalis trivial to setup.Why not go with SID then?
Can one adopt Debian SID and automate this? I mean, how difficult would it be for a person not looking to create and maintain a distro but use Debian SID and pull the latest and greatest security patches?