openvpn-install VS rpm-ostree

and for OpenVPN: https://github.com/Nyr/openvpn-install

I'm trying to establish a private torrenting setup using qBittorrent on my local whitebox server machine using Ubuntu 22.04 and a Virtual Private Server (VPS) as a VPN using Ubuntu 22.04 and OpenVPN (I used https://github.com/Nyr/openvpn-install). My local machine, acting as a private tracker seedbox, has qBittorrent installed and configured to use port 15986 for inbound connections with tun0 as the network interface.

Hello, I installed an OpenVPN server on my Centos server using the easy install script here https://github.com/Nyr/openvpn-install.git My client is MacOS and it works fine for the most part BUT I need to access devices on the server's LAN When I'm using my home internet, I can access the server fine but everything that is not in the same subnet as what OpenVPN gave me does not work. When using LTE and network sharing on my computer, I can still access the server and now I can also access devices on the server's LAN that is not in the same subnet as OpenVPN. I don't understand why it behave like this and I want to always be able to access the server's LAN when connecting to the VPN.

https://github.com/Nyr/openvpn-install

My idea would be to create a Debian VM on Proxmox, and install OpenVPN using Nyr script (https://github.com/Nyr/openvpn-install) and create a user for each of my friends.

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