That looks pretty convoluted, but yeah, thats kinda what you'd need to do. There are a lot of bits and pieces there, so if open source is essential, youd want to check that all are OS.
A more pragmatic approach may be to simply accept that because you can flash the firmware, that is good enough. The first party firmware will probably be good, assuming its not had safety systems turned off, and if the firmware actually becomes a problem you can always switch later?
If this is your first printer, I would stick with the stock firmware unless there is something wrong with it. Klipper/Marlin/etc dont really matter as long as it produces the correct print output.
Other than building the firmware and flashing it yourself not really?
Usually they will have flashing instructions somewhere, and thats a goodish sign. Even better if they have the source code published somewhere. But unless you build it and flash it yourself its impossible to know what is on there.
For a real-world example, many Anet A8 machines were shipping with "marlin", but with the runaway thermal protection disabled.
but they can advertise other things that aren't a direct conflict of interest.
Advertising things that arent a direct conflict of interest just results in poorly targeted ads, which both consumers and advertisers don't like.
On the "open source" side, its not enough that the firmware is open source, the flashed binary needs to actually be unmodified. Marlin and klipper run 99% of the budget 3d printer space, and both are open source projects. There are still dozens of printers that are shipped with modified firmware with the changes kept secret. GPL is only as powerful as your lawyers are.
Even when not logged it, yt builds a profile of what you watch. I'm not logged in on my work browser, but it still knows what I watch frequently. So this ones on you...
Container overhead is near zero. They are not virtualized or anything like that, they are just processes on your host system that are isolated. Its functionally not much more different to chroot.
VSS equivalent would be btrfs snapshots or zfs snapshots.
Can you really copy a VSS to a new disk? For a new install, at some point you'll need to reboot and go offline, so I don't see the point in trying to keep uptime. If uptime matters, dont upgrade a disk, replace the entire system.
Easiest IMO is to install both drives, and then use dd to copy drive A to drive B, and then resize the partitions with gparted to fill the rest of the disk.
Do this from a live USB so that your not currently using drive A.
That looks pretty convoluted, but yeah, thats kinda what you'd need to do. There are a lot of bits and pieces there, so if open source is essential, youd want to check that all are OS.
A more pragmatic approach may be to simply accept that because you can flash the firmware, that is good enough. The first party firmware will probably be good, assuming its not had safety systems turned off, and if the firmware actually becomes a problem you can always switch later?
If this is your first printer, I would stick with the stock firmware unless there is something wrong with it. Klipper/Marlin/etc dont really matter as long as it produces the correct print output.