

I have updated my post to point out the Hungarian Revolution, which is what is written in Wikipedia, if Wikipedia is wrong, please provide more context.
I have updated my post to point out the Hungarian Revolution, which is what is written in Wikipedia, if Wikipedia is wrong, please provide more context.
Yes, which is what I posted in an update of that post.
AFAIK, originally “tankie” comes from being on chinas side of the Tianamen Square Massacre. So on the side of the tanks. It doesn’t have directly to do with U.S.
So if someone thinks that China did good there, they are likely a tankie.
Update: I looked it up and it seems I was wrong, it was about arguing in favor of using tanks in the Hungarian Revolution. See more here: https://en.m.wikipedia.org/wiki/Tankie
According to Christina Petterson, “Politically speaking, tankies regard past and current socialist systems as legitimate attempts at creating communism, and thus have not distanced themselves from Stalin, China, etc.”
So you also have to consider yourself a supporter of what you understand “Comminism” means, to be one.
The text is hiding a lot of details, but the nurse is pushing a normal chair, as if it was a wheelchair.
And the composition gives AI vibes as well. But all of that could also just be because the photo is poorly staged.
I know this post is more about the committing on LLM “fixes”, but find the other reasons more interesting.
Similar to the date & time library there are a couple of other things that look easy at a first glance, but get complicated very quickly, because it has so many special cases:
Well, that could have been fixed by booting from an usb stick, chrooting into you real system and either downloading and (re)installing the python package this way, or, if your package manager depends on python, download the package in the Live Linux and extracting the python package into your system, and then reinstalling it, so the package management overwrites your “manual installation”.
Could be tedious, but less so that having to reinstall everything IMO.
It is more about being lazy.
In most cases, where you havn’t destroyed your filesystem, you can just boot another Linux from a USB stick, mount your filesystems to /mnt, chroot into it, and then investigate and fix there.
See the Archlinux wiki, even if you do not use Archlinux, it is great: https://wiki.archlinux.org/title/Chroot
No no no! When you break something in Linux systems you fix it. Starting over and reinstalling everything is what you do when you mess up on Windows.
“Jackson” but I thought the same.
I found the main issue with many non-rolling release distributions are the upgrade instructions from one stable release to the next, and not the difficulty of installing them.
I’m myself a Archlinux guy, but that does sometimes require some carefulness and regularly (at least weekly) applying updates and does not have stable automatic updates, so I started installing Fedora atomic desktop distributions (Fedora Silverblue/Kinolite/etc.) for people that just want to use their device for basic stuff.
The reason for that is long term maintainability without an expert at hand.
I had so many bad experiences updating distributions from one stable version to the next, be it Debian and Ubuntu-based, or Fedora-based distributions.
And with those atomic desktop distributions the amount of moving parts is much lower, so hopefully upgrading them to newer releases is much more stable.
So I would suggest giving Fedora Silverblue (Gnome desktop), Kinolite (KDE) or Budgie Edition a try.
I get the sentiment, but in this time and age and with the internet, I think the information most likely to be at risk of being destroyed or censored is the one that is not commonly available, or in the hands of law enforcement.
A fascist government will more likely effectively prevent creation of new dissenting works, than suppressing existing ones.
Together with secure boot and your own signing keys, it could be a good way to en/decrypt the a dm-verity secured read-only rootfs. But for the home partition I would probably still want to enter my own decryption key, maybe via systemd-homed. From there you can update the kernel/initramfs and read-only rootfs image and sign them for the next boot.
This is complicated to set up. Otherwise maybe use TPM as a 2FA, so you still have to enter a pin?
That might make it even more dangerous, because you get used to flash to usb sticks on “/dev/sda”. And when you then use a device with a built-in sata drive, you might forget checking in a hurry.
Happened to me a once or twice. I am now only using bmap tools for this.
An interesting concept would be if all hand on the 12 clocks would work, but the hands of the clock in the middle are stuck at 12 position, this way the hands in the middle would point to the clock showing the correct time.
This is the same between many different software development disciplines, fpga devs (or hardware devs for that matter) vs. driver devs, driver devs vs. backend dev, backend devs vs frontend devs, integrators vs everyone.
Well, I consume more open source software that I will ever produce, so I am in a dept to the community. If it means working a bit more to make my contribution useful to others and fit it into the bigger whole, I will gladly do so.
Valve contributed to Linux before, so the fact that they don’t have any direct upstreaming plans right now indicates that something is causing friction.
I would avoid reading too much into it. They and their developers are still contributing on other stuff. Also when working together, there will always be some friction, in any public collaborative project ever.
Nothing of this is a burden, it is just part of being a good contributor that reads and follows the rules. Contributing is pretty easy, when you have read and are following the guides. If you haven’t already, you should give it a try.
I am pretty sure that this isn’t the first contribution of Valve to the Linux kernel. It sounds more to me like “works for me, don’t care about others” attitude. Which is not a good attitude to have when working in any collaborative project. (Not necessarily against the developers, could also be management.)
Well, it is about code quality. And the same codebase should work on different hardware, which is not something that is required in downstream forks.
But it is sad to see that the driver was submitted in the past, is still actively developed and improved, but there doesn’t seem to be plans of submitting them again.
Also I don’t think that a platform driver is so complicated that it requires such a long time for mainlineing. It not a filesystem or VPN.
On a more interesting topic, the SteamDeck platform drivers are still not merged into mainline Linux… :'(
Last news about it: https://www.phoronix.com/news/Steam-Deck-Platform-Driver-2024
Is the update on my post not showing for you? I said I was wrong and posted the Wikipedia link to the Tankie article.