Jan-Willem HarmannijAdded a "distrobox create" and "distrobox enter" test to the #AeonDesktop openQA tests:
https://openqa.opensuse.org/tests/5973555
This will hopefully catch any issues with #Distrobox on Aeon faster in the future.
JackI like my little home lab and my tiny #snac instance but I'm trying to simplify my home mindspace / meatspace so thinking of burning it all down this weekend (which starts in about two hours). That likely means decommissioning my instance, exporting my @readeck stuff, and wiping my lab NUC.
My lab NUC is faster than my desktop and uses about a third of the power. I'd swap SSDs between the two (better SSD in the desktop), install #AeonDesktop, run Readeck in a local container (probably behind @tailscale) and staying on this Mastodon instance for a while. Then, offering this (tiny, Xeon-based) desktop to my co-worker for free to replace her Pi in her home lab, and voila: Marie Kondo Home Lab.
Jack@[email protected] Highly recommend #AeonDesktop, though it might still be in pre-release. Fast, stable, easy.
Thinking about installing Steam on my new-to-me #AeonDesktop laptop and running from some zombies this weekend.
Nothing erases your brain like running from some zombies. Have a bad day? Watch some Walking Dead. Always makes your day look not so bad.
Nothing erases your brain like running from some zombies. Have a bad day? Watch some Walking Dead. Always makes your day look not so bad.
Barrel connector to USB-C widget came in, which means I just got a significant craptop upgrade:
- Hardware Model: MOTILE M141
- Memory: 16.0 GiB
- Processor: AMD Ryzen™ 3 3200U with Radeon™ Vega Mobile Gfx × 4
- Graphics: AMD Radeon™ Vega 3 Graphics
- Disk Capacity: 128.0 GB
passthejoeThis article attempts to say that #atomic and #immutable are two different things when it comes to operating systems, yet it doesn't make any attempt to label the nine Linux distros it lists under atomic/immutable as one or the other.
Plus it missed #AeonDesktop and #Kalpa entirely, while mentioning #OpenSUSE MicroOS, which isn't a desktop system (though Kalpa is derived from it).
https://www.zdnet.com/article/atomic-vs-immutable-linux-distro-how-to-decide/
Plus it missed #AeonDesktop and #Kalpa entirely, while mentioning #OpenSUSE MicroOS, which isn't a desktop system (though Kalpa is derived from it).
https://www.zdnet.com/article/atomic-vs-immutable-linux-distro-how-to-decide/
I've been a happy #AeonDesktop user since a year or so. As a way of giving back, I installed #openQA on my laptop and wrote tests for tik (Aeon's installer) and for the first-boot process.
OpenQA is a really awesome and versatile system testing tool, and has excellent documentation. With openQA tests, a new operating system snapshot can be automatically tested before it's released to the public. The tests can verify anything, from screenshots to shell commands and script outputs.
I was able to add Aeon as a new "product" to the existing openSUSE tests repository without too much trouble. The results are now submitted as PRs. I hope they can be merged soon. After that, I will create some more testcases:
- run the default apps
- create a Distrobox
- upgrade an existing system
JackI've been screwing around on this decade-old craptop for almost two and a half hours now, mostly in #Vivaldi, running #AeonDesktop. Battery was at 93% when I started, now at 68%.
I have it in Power Saver mode, and I noticed that Vivaldi is much more performant than Chrome in this mode. I actually had to go look to see which power mode I was in, worried that it was in Performance mode and going to eat battery.
Starting to really like this combination for anything that's not processor-intensive.
I have it in Power Saver mode, and I noticed that Vivaldi is much more performant than Chrome in this mode. I actually had to go look to see which power mode I was in, worried that it was in Performance mode and going to eat battery.
Starting to really like this combination for anything that's not processor-intensive.
slubmanFriday, before the start of the week-end I received the @frameworkcomputer #framework12 laptops for my parents.
They will be installed with #Linux of course.
As they won’t be delivered before some time, I ’m playing a bit with them. One have been installed with #fedora #silverblue, the other one with #aeondesktop.
So far I like what I’ve seen with the #gnome desktop:
* When the screen is rotated, the keyboard is disabled.
* When in tablet mode, the screen orientation follow the device orientation.
* The power draw in sleep mode looks ok.
* BIOS/UEFI update are supported with #lvfs.
But I also have some issues:
* The virtual keyboard in tablet mode, is only in qwerty, even if the system is configured with another layout.
* When the virtual keyboard appears, some windows content is not moved above the keyboard, which might make it difficult to see what one is typing.
* On the Aeon install I had to `sdbootutil --ask-pin update-predictions` after installation to have the #tpm2 unlock working.
I've been checking out @[email protected] and decided I wanted to see how it fares on something with restrictive system resources, wondering what the #Vivaldi version of a Chromebook would look like. So wiped the craptop again, installed #AeonDesktop but without Firefox, pulled down the Vivaldi flatpak, and voila. Might as well be a Chromebook.