‘Oh come on!’ was my initial reaction, but I’ve read your website, and thought: ‘hey, that sounds nice!’
I’m not going to migrate all my Arch boxes (basically all my x86/64 boxes), but I may use it somewhere else, just to test the idea.
I loved the idea of Atomic Fedora, but it did not work seamlessly, and to my experience, it did the opposite: worse than a regular Fedora. I needed to babysit it, and also it didn’t auto switch the previous working system for me. Perhaps it’s me who missed something. As an idea, though, I think that’s what should click to a normie: you tell them to install this distro, get your handful of apps as Flatpaks and forget about the system, as it manages itself.
To keep this topic alive, let me ask you a question: how would you know what’s a working state, so you need to return to the previous one? Does it mean it didn’t boot, or anything else? Just yesterday, I had faced a weird issue: my old trusty MacBook Pro serving as a server now, had no WiFi (it has Ethernet port, but temporarily I cannot use it, so it’s wireless). The broadcom-wl driver switched to linux-headers, which I didn’t have installed. I don’t remember me changing anything, and fortunately that was an easy fix (with an external USB WiFi card): just install Linux headers, and it would rebuild itself. So I’m just curious whether it’s even possible to find out a stupid issue a normie user may face.
On the other hand, perhaps the distros like this are meant to be installed by someone skilled to then be used mostly unattended by a regular user.
‘Oh come on!’ was my initial reaction, but I’ve read your website, and thought: ‘hey, that sounds nice!’
Haha, I know I know, yet another Arch-based distro in this economy, but I really feel like this does fill a gap, thank you for your interest!
On the other hand, perhaps the distros like this are meant to be installed by someone skilled to then be used mostly unattended by a regular user.
My aim is to make this both appealing for the normie who just wants to use it like “SteamOS but with CachyOS speed” and run Flatpaks on it AND for the more experienced user who wants all the benefits of Arch but with a little more peace of mind.
how would you know what’s a working state, so you need to return to the previous one?
As the website explains, it automatically falls back to the last working state if it doesn’t boot, but obviously it can’t detect if something is messed up but still booting like in your example. In that case you just reboot and manually select the last working state (wip but kinda working already) just like a BTRFS snapshot, BUT it only rolls back the system itself, NOT your files. A BTRFS snapshot will also roll back your documents or whatever so my system, when it’s stable and tested, will be superior in every way to BTRFS snapshots.
A BTRFS snapshot will also roll back your documents or whatever
Not necessarily. You can have your documents on one subvolume and the root system on another. I version and snapshot my root disk and home disk separately.
Don’t take it the wrong way, but if you “forget” such a basic thinkg, are you really suited for creating and maintaining a whole distro? Maybe you need a few years more experience first?
No offense taken, but I didn’t use btrfs snapshots in a minute and spent 200 hours in the last 18 days working on my distro with a little less than adequate sleep due to my ADHD keeping me awake, thinking about what to implement next. Please cut me some slack haha
Compiling a kernel? 😀
I’m making my own distro rn, announced it a week ago here and will likely release today or tomorrow! https://pu-239.org/ https://lemmy.ml/post/52307735
‘Oh come on!’ was my initial reaction, but I’ve read your website, and thought: ‘hey, that sounds nice!’
I’m not going to migrate all my Arch boxes (basically all my x86/64 boxes), but I may use it somewhere else, just to test the idea.
I loved the idea of Atomic Fedora, but it did not work seamlessly, and to my experience, it did the opposite: worse than a regular Fedora. I needed to babysit it, and also it didn’t auto switch the previous working system for me. Perhaps it’s me who missed something. As an idea, though, I think that’s what should click to a normie: you tell them to install this distro, get your handful of apps as Flatpaks and forget about the system, as it manages itself.
To keep this topic alive, let me ask you a question: how would you know what’s a working state, so you need to return to the previous one? Does it mean it didn’t boot, or anything else? Just yesterday, I had faced a weird issue: my old trusty MacBook Pro serving as a server now, had no WiFi (it has Ethernet port, but temporarily I cannot use it, so it’s wireless). The
broadcom-wldriver switched tolinux-headers, which I didn’t have installed. I don’t remember me changing anything, and fortunately that was an easy fix (with an external USB WiFi card): just install Linux headers, and it would rebuild itself. So I’m just curious whether it’s even possible to find out a stupid issue a normie user may face.On the other hand, perhaps the distros like this are meant to be installed by someone skilled to then be used mostly unattended by a regular user.
Haha, I know I know, yet another Arch-based distro in this economy, but I really feel like this does fill a gap, thank you for your interest!
My aim is to make this both appealing for the normie who just wants to use it like “SteamOS but with CachyOS speed” and run Flatpaks on it AND for the more experienced user who wants all the benefits of Arch but with a little more peace of mind.
As the website explains, it automatically falls back to the last working state if it doesn’t boot, but obviously it can’t detect if something is messed up but still booting like in your example. In that case you just reboot and manually select the last working state (wip but kinda working already) just like a BTRFS snapshot, BUT it only rolls back the system itself, NOT your files. A BTRFS snapshot will also roll back your documents or whatever so my system, when it’s stable and tested, will be superior in every way to BTRFS snapshots.
Not necessarily. You can have your documents on one subvolume and the root system on another. I version and snapshot my root disk and home disk separately.
True, if you set it up out of the box with CachyOS it rolls the entire disk back, but I forgot that option was a thing, my bad!
Don’t take it the wrong way, but if you “forget” such a basic thinkg, are you really suited for creating and maintaining a whole distro? Maybe you need a few years more experience first?
No offense taken, but I didn’t use btrfs snapshots in a minute and spent 200 hours in the last 18 days working on my distro with a little less than adequate sleep due to my ADHD keeping me awake, thinking about what to implement next. Please cut me some slack haha
This looks amazing! Thank you for your contribution! :D <3