King Charles accepted award from Nazi veteran
gnuhaut @ gnuhaut @lemmy.ml Posts 8Comments 519Joined 2 yr. ago
gnuhaut @ gnuhaut @lemmy.ml
Posts
8
Comments
519
Joined
2 yr. ago
This article is dumb AF. Dude was a fucking 18 year old infantryman when Nazi Germany surrendered. This article tries to portray him as some high-level Nazi and tries to smear the monarchy by implication.
Hmm, let's read the article. (Savaryn is the guy):
Originally from Ukraine, he served in the 14th Waffen Grenadier Division of the SS – the so-called Galicia division – during World War Two.
And:
Savaryn rarely spoke publicly about his wartime experiences, but admitted in an interview to joining the Galicia division in 1944 after much of the unit was encircled and destroyed during the Soviet liberation of Ukraine.
Rather than fighting to free Ukraine from Soviet rule, the Galicia division retreated deeper into German-occupied Europe. Savaryn confessed to hunting down partisans during Slovakia’s uprising against the Nazis in 1944.
According to the Military Historical Institute of Slovakia, “If we compare them to regular Wehrmacht units, the way they behaved, the cruelty and the pillage by the Galicia Division was much worse. The Galician Division was the most cruel, the worst of all.”
Just an "18 year old infantryman" my ass. Was he sorry for what he did?
In his memoirs, Savaryn refers to the Galicia division as “the Knights of the Golden Lion” – a reference to an old Galician kingdom’s coat of arms adopted by the Ukrainian SS men as their unit’s insignia.
Also pictured in Savaryn’s memoirs is his presence at the consecration of the Galicia division memorial in Edmonton’s St. Michael’s Cemetery in 1976 by Catholic Cardinal and Ukrainian nationalist Josyf Slipyj. The memorial lies close to the Ukrainian Youth Unity Complex.
I guess not.
Now get fucked with your Nazi apologia.
A lot of distros, I think, are started more due to political/social/psychological reasons, and not fundamental technical reasons, and that's why a lot of them are so similar. Those reasons can be good and legit, but sometimes they are probably wrongheaded (but understandable), like an unwillingness to engage with upstream because that's tedious and frustrating, whereas the technical work of creating another distro with oneself in charge may be more fun.
Also, of course, once a distro is big enough, with a sizable community of developers and users, there's a strong incentive to keep it going, even if it's very similar to another distro. Maybe there used to more of difference in the past, but you're not going to convince a whole community to just shut down and join some other project. And business-run distros will keep going as long as the company is making money there is some business reason to keep doing them.
While this is generally true, there are sometimes exceptions to this, especially during the freeze.
Even unstable slows down during the freeze, as the usual way to get stuff into testing is through unstable, and packagers, especially of large collections or important dependencies, opt not to disturb the freeze by dumping a bunch of bleeding edge stuff in there. Consequently you also get more new stuff in unstable shortly after a new Debian release.
I use tlp.
I also have a battery info using i3status in the status bar, and a script I named battery-check, which warns me via a dunst popup and a beep when the battery gets low:
#!/bin/sh
set -eu
bat=/sys/class/power_supply/BAT0
if [ ! -d "$bat" ]; then
exit 1;
fi
status=$(cat "$bat/status")
energy_now=$(cat "$bat/energy_now")
energy_full=$(cat "$bat/energy_full")
battery_percent=$(( ${energy_now}00 / ${energy_full} ))
if [ "$status" != "Charging" -a "$battery_percent" -le 15 ]; then
dunstify -t 8000 -u critical "Battery at ${battery_percent}%"
play -q -n -c1 synth 2 sine 600
fi
I run this from my ~/.config/sway/config like so:
exec sh -c 'while true; do sleep 180; battery-check || break; done'
I don't think the problem is with GRUB.
There are various different ways in which USB keyboards can encode keypresses. I've seen some BIOSes that just cannot deal with some keyboards due to this. The USB keyboard driver that will be in use during GRUB should be the BIOS/UEFI driver. So I would try updating the mainboard firmware/EFI or try a different keyboard maybe? Or disable the GRUB password if that's an option.
More expensive business-class laptops, like the T-series, is I think what RedHat and others give to their employees, thus they are usually better supported than cheaper consumer models.
Ah that's your point. Yeah I agree that splitting literal a b c is convenient. It is surprising to many (like here) that this happens after variable substitution, and that's not very convenient since you almost never want that. You could define this to happen the other way around, but then you'd obviously have to invent a new syntax for explicit splitting, which would be its own kind of annoying.
Edit: YSH (oil) does that btw. See here.
I disagree. The vast majority of the time when writing shell scripts, I quote variables, because that's almost always what I want. Splitting is basically only useful if you have a list of arguments, and you know for sure there are no spaces in any of the arguments (so no filenames).
(The workarounds in pure POSIX shell are btw super annoying if you want to pass a list arguments that may have spaces in them: You can abuse the special "$@" variable. Or you could probably also construct something with xargs.)
As others have said, if you quote your variables, they won't get split on spaces. The Unix shell unfortunately has ton of gotchas like this, and the reason this is not changed is backwards-compatibility. Lots of shell scripts depend on this behavior, e.g. there might be something like:
flags="-a -l"
ls $flags
If you quote this (ls "$flags"), ls will see it as one argument, instead of splitting it into two arguments. You could patch the shell to not split arguments by default, and invent some other syntax for when you want this splitting behavior, but that would break a ton of existing shell scripts, and confuse users who are already familiar with the way it works right now. It would also make the shell incompatible with other shells, and violate the POSIX standard.
I did it during the gcc 3 transition. I used a very new gcc 3 (maybe even pre-release), which wasn't at all recommended. A couple of (most?) C++ packages didn't compile (some change having to do with namespace scope), which meant I had to fix the source of some packages (generally pretty trivial changes, usually having to prepend namespace:: to identifiers). Overall this problem was pretty rare, like it affected less than 1% of C++ files, but with things like Qt or Phoenix (or whatever Firefox was called back then), with thousands of files, I had to fix dozens of things. I guess running into problems made it more interesting and fun actually.
Did I learn anything? The main thing I learned is about all the different basic packages and what sort of binaries and libraries are included in them and why you need them. Also about some important config files in /etc. And a bit of shell experience, but I dare say I knew most of that stuff already. How much you learn depends a lot on how much you already know.
Overall what I learned was not very deep knowledge, nor was it a very time-efficient way to learn. But it was a chill learning experience, goal-oriented and motivating. And it made me more comfortable and confident in my ability to figure out and fix stuff.
Also it's obviously not practical to keep that up to date, so I switched back to a distro after a couple of months of this.
I'll make an appeal to authority (kernel developer working on memory management):
Disabling swap does not prevent disk I/O from becoming a problem under memory contention, it simply shifts the disk I/O thrashing from anonymous pages to file pages. Not only may this be less efficient, as we have a smaller pool of pages to select from for reclaim, but it may also contribute to getting into this high contention state in the first place.
And then he goes on to say what I said, that it can make the OOM killer quicker to react.
This doesn't work to avoid thrashing. The kernel may invoke the OOM killer slightly quicker if you have no swap, so I guess that can sort of help, but it doesn't properly solve the problem.
On Linux, there's a thing called the page cache (aka disk cache): Every time (part of) a file gets read to or written from, that (part of) the file gets copied to RAM. The file is then kept there unless that RAM is needed for something more important. It is cached in RAM. But since it is also on disk, the kernel can drop the file from RAM anytime it wants.
If you're low on RAM, the kernel therefore evicts all of the disk cache, because it can, because those pages can be reloaded from disk if needed. This means it will drop all the programs you're running, the binary code. So any program you're running is constantly interrupted, because its code is not in RAM.
So it runs a couple of instructions, but oh no! Call to function foo() from glibc, but guess what? That's on disk. Queue wait for the kernel to load that. Oh now it wants function bar() from zlib, shit! Need to load that. Since loading stuff from disk is about as slow as running like a gazillion instructions, all your programs are like 1000x slower now.
This happens even with zero swap.
The correct advice is the one from @RedWeasel@lemmy.world: install/enable systemd-oomd or earlyoom.
Does Russia aim those nukes at Poland? They will if there are nukes there.
Screen is the terminal though?
It's not going to be something useful like a power house though. It'll be a bunch of dudes simulating how to blow up poor third-world peasants in the most expensive way possible. In case the market demands that particular skillset. And who is going to command this lot? Von der Leyen? I'd rather not give an army to the aristocratic horse lady (again). She probably always wanted to order a cavalry charge against some peasants, so let's not give her the chance.
OK glad you found some workaround!
Since when is aluminium biologically important? I'm under the impression that humans (and other life?) do not need aluminium at all.
Having said that, my info is that it's nothing to worry about. It is very common in food (naturally and since forever), and the body can get rid of it, and they haven't been able to show adverse effects except in very very high doses. That's the messaging I've been seeing anyway.
It actually starts, and then turns off. I didn’t notice it before you drew my attention.
That does sound like DPMS ("vesa display power management signaling") shenanigans though.
Maybe you can disable XFCE's display power management stuff completely? Systemd's logind (/etc/systemd/logind.conf) can do (and does by default I think) suspend on lid-close without any window manager involvement at all, works fine with i3 here. So disabling XFCE's stuff probably "only" messes with your monitor not going standby after a while, and you can maybe use xset or xscreensaver and set this by hand (after making sure it's actually properly disabled in XFCE, so XFCE doesn't override that stuff).
Found this about how to stop xfce4-power-manager and disable DPMS:
xfce4-power-manager -q
xset -dpms
Try doing that and see if lid close works afterwards.
Since that bug seems related to the X server somehow, I wonder if your monitor is showing black or actually off/standby (as in backlight off)?
If it's the backlight, maybe it's related to DPMS (monitor power management), and you can jolt it back to life with something like
xset dpms force on
after waking up. Or maybe disable DPMS completely and see if that changes anything.
It would also be interesting to know if this problem also happens outside of XFCE. If you just use (say) openbox (which I don't think does any power management or DPMS stuff by itself), does that work?
If you had read the article you would know the guy grew up in what was then Poland during the Holodomor, not Ukraine. You probably have double genocide brainworms, and this excuses nothing. (Nazi apologia count: 1)
You ignored where I quoted how the guy was at the consecration of a fucking Waffen-SS memorial in 1976, you know, at age 50. Instead you keep repeating how young he was (Nazi apologia count: 2)
You also ignored that the guy is definitely a war criminal, being part of the Waffen-SS in Slovakia, instead you paint him as the victim. Oh how hard it must have been during the Slovakia uprising, for, checks notes, the poor Waffen-SS soldier on massacre duty. Come on, you got to be kidding me. (Nazi apologia count: 3)
Then there's some bullshit about how "Nazis gave them hope" (do you hear yourself?) and "impossible situation", apparently that's a valid excuse to join the Waffen-SS in your book. You know who didn't join the Waffen-SS? Literally almost every other Ukrainian. (Nazi apologia count: 4, 5)
Can I see this promotion of multiculturalism and tolerance please? And how is it possible that this very tolerant man put up a Waffen-SS memorial at age 50? I don't believe you, you're making this shit up. But I see this fun quote by him about multiculturalism:
Or maybe you mean that he was president of the "World Congress of Free Ukrainians"? Because I can already smell the fascist OUN stink coming off of this org. Oh yeah here it is.