handWavey VS rpm-ostree

Shameless self plug: handWavey is a tool that I wrote to control your computer using a leap motion controller. I've put a lot of time into making it practical for real world desktop usage as well as some underserved accessibility use-cases, and I absolutely love it. And I still have a lot more that I want to do with it. You can see handWavey in action here.

Have you played with any leapmotion based solutions? I wrote handWavey which gives you the ability to control the mouse and keyboard by moving your hands like in minority report. There's also a foot gestureLayout, which is highly experimental, and not ready for daily use, but might give you ideas.

I'm really interested in this as well. I think I'm missing a lot of opportunities. Like a few months ago, I released handWavey, which I think is fricken cool I posted it in a small number of places, and then just continued to work on it quietly.

hands/arms don't work? Try the foot gestureLayout. (This layout is a proof-of-concept, and is highly experimental. I don't recommend it, for now, but it shows what can be done if there is interest from people who would benefit from it.)

The important thing is that the gestures are completely configurable. And everything assumption/"that seems right" is configurable. I've gone into more detail about this in the main video. I've also provided some examples and documentation. You'll see that I've even made a gestureLayout for operating it entirely with your feet. I don't recommend it (it needs much more development, which could happen if there is interest), but it works. With that gestureLayout, I've make the left click happen by simply moving your primary foot through to the "action zone". But you can add your secondary foot to perform a right click, middle click, or scroll.

I definitely agree that immutability offers considerable value in regards to improving security. But arguably it's insufficient to pull the win over mutable Fedora due to the losses caused by the inability to install the kernel-hardened package and the lack of UKI (Unified Kernel Image) support.

Issue: https://github.com/coreos/rpm-ostree/issues/3944

Oversimplifying might have been the most sensible in this context. However, you might have gone a little bit too far as your description fits only NixOS, Guix and distros that utilize rpm-ostree.

here's the documentation of ostree (the package manager)

Now... this was VERY alarming to say the least, so I went online and did indeed find an issue on GitHub.

And there are still some issues with layering. Some packages that don't behave or follow standards will modify files in /usr/local, which isn't supported, so you simply won't be able to install them on Silverblue. I think it's the same for /opt as well. (https://github.com/coreos/rpm-ostree/issues/233) This means it fundamentally can't do everything Workstation can, which is unfortunate.

ublue is based off of fedora and rpm-ostree, which is what "CoreOS" is today.

What happened was old school CoreOS was A/B partition based: https://github.com/coreos/docs/blob/master/os/sdk-disk-parti...

My memory is hazy but here's how I remember it: After Red Hat acquired CoreOS they rebased the entire thing around rpm-ostree, which is the CoreOS people know today: https://coreos.github.io/rpm-ostree/

At the time there was some anxiety in the community as to what would happen, as there was no direct upgrade path from old CoreOS to new CoreOS. Theoretically if we all believed the kool-aid we were drinking it's just a redeploy, no pets!

Kinvolk came along, forked it, and made Flatcar Linux, which kept the A/B partitioning system, and more crucially, let you just change a config file and all your old CoreOS nodes would just move to Flatcar and then you were good to go. So now if you wanted to stay on the system you were comfortable with you could just use Flatcar. If the composability of rpm-ostree attracted you then new CoreOS have you covered. Red Hat deserves a hat tip here because in their documentation/blog they explicitly mentioned Flatcar as an option for people who wanted to stick with what they know, which I thought was cool and how I discovered it!

Later on Microsoft acquired Kinvolk and and then people raised eyebrows. I have not checked in a while but the folks involved continued to do their thing and run it like a good OSS project, hold public meetings, all that stuff.

I use both and they're both high quality.

Whenever I was looking at using CoreOS, I was somewhat disheartened that automatic reboots weren't built in: https://github.com/coreos/rpm-ostree/issues/2831. Has this changed? I know zincati has maintenance window support, which would also be nice to have.

Doesn't look like it https://github.com/coreos/rpm-ostree/issues/1091