I have to upgrade my Mint install every two years
I know you're joking around here, but you don't have to upgrade every two years. You can use an LTS release instead, or, on the opposite of the spectrum, a rolling release.
Release schedule and duration of support should always be factored into the decision of choosing a distro.
Save your sanity and do Settings -> Blocks -> Block instance -> lemmy.ml
I approve this comment.
Strange women lying in ponds distributing swords is no basis for a system of government.
Millenials - Load"$“,8 LIST LOAD"LEISURESUIT*”,8,1 (wait 10 min.) RUN
Even the oldest millennials were just toddlers when the C64 was relevant, so this is not a typical millennial experience at all. It's really a GenX thing... so once again we are forgotten.
I would say millennials' computer experience starts in the late DOS/Win3.11 era at the very earliest, but more typically in the Windows 9x and early XP era. So even IRQ/DMA/config.sys/autoexec.bat fuckery is not that typical.
Now we’ve got to fucking participate in it?
Ah yes, killing all those innocent civilians hidden in incoming Iranian ballistic missiles...
I see military spending as a necessary evil, it's like paying your insurance policy against the evils in the world. There will always be someone with a stick willing to beat someone weaker than them. So you could theoretically spend that military money on something "more useful", but if all your friends do that as well, you won't be able to enjoy that nice world for very long.
Also, people usually highly overrate how much a country spends on defense and underrate how much is spent on social security. Where I live, in Belgium, with a similar military budget as Canada (in terms of % of GDP) they did a survey once and asked people to estimate how many euros out of €100 of tax money went to the military and other things. People on average thought it was €6.1 to the military and €17.4 to social security. In reality the proportions are just €1.3 to the military and €37.5 to social security.
So I guess what I'm saying is: it's okay to enjoy the cool noises without guilt. You paid for it, it's necessary, and at least they're providing people with some entertainment now.
I guess it’s why some Jellyfin streams started transcoding for me.
You're better off using the Jellyfin Media Player standalone application anyway.
The thing is, you can't really engineer against anti-social behavior. For every better made apartment you will find that there is an even bigger anti-social idiot who still manages to make life hell for their neighbors.
I'm pretty blessed with my mostly boomer neighbors (🤞) who don't make a peep after 10PM, but my girlfriend has had some shitty neighbors even though her apartment is pretty well made. Sound insulation between apartments is no match for cigarette and marijuana smoke wafting in from the balcony below any time you want to open the window to air out, or if, heavens forbid, you want to sleep with the window open in the summer, nor does it help much if they are partying and speaking loudly on their balcony until 4AM on weekdays. And then I'm not even getting into how they're treating shared spaces.
The proximity makes everything so much worse than it would be with a house, at some point only adding distance helps.
A core memory of mine is getting flung off of one of these things because of the centrifugal force, falling on my back, and being unable to breathe for like 20-30 seconds ... until I screamed at the top of my lungs, and things slowly returned to normal, while the teacher just went: oh you're fine, don't be a baby. I was 6.
All true, yet it has nothing to do with what we are discussing, so why are you muddying the water with it?
my body, my choice
It's a bit more complicated than that with transplants. Should people for example be able to sell their kidney to the highest bidder? That's also "my body, my choice". And should doctors be forced to participate in such a scheme?
A transplant system should consider fairness, equality and possible abuse. Obviously I think it should be possible to donate to a loved one, but we should also be careful not to create a system where the rich get priority, because they can pay more, and where poor people could be financially pressured to give up their bodily integrity by having to sell an organ.
We're explicitly talking about a situation where the donor is suitable. So I don't know what kind of information you're trying to add here.
The past year or two I've found several stores where they are abandoning it. I presume because people carrying cash, especially coins, is becoming rarer and they don't want to inconvenience their customers?
Strangely enough, carts still get returned even at these stores.
Even if her partner could donate his own liver, it should still go to a better recipient
That's nonsense, because the partner would not donate his liver if it went to someone else.
The flag is called --no-preserve-root, but the flag wouldn't do anything here because you're not deleting root (/), you're deleting all non-hidden files and directories under root (/*), and rm will just let you do it.
It’s apparently a hobby and to be competitive, you need to be able to spew bullshit at amazing rates. Personally I’ve maxed out at 140 wpm
I'm limited by the rate at which I can think of bullshit.
I feel like we need to talk about Lemmy's massive tankie censorship problem. A lot of popular lemmy communities are hosted on lemmy.ml. It's been well known for a while that the admins/mods of that instance have, let's say, rather extremist and onesided political views. In short, they're what's colloquially referred to as tankies. This wouldn't be much of an issue if they didn't regularly abuse their admin/mod status to censor and silence people who dissent with their political beliefs and for example, post things critical of China, Russia, the USSR, socialism, ...
As an example, there was a thread today about the anniversary of the Tiananmen Massacre. When I was reading it, there were mostly posts critical of China in the thread and some whataboutist/denialist replies critical of the USA and the west. In terms of votes, the posts critical of China were definitely getting the most support.
I posted a comment in this thread linking to "https://archive.ph/2020.07.12-074312/https://imgur.com/a/AIIbbPs" (WARNING: graphical content), which describes aspects of the atrocities that aren't widely known even in the West, and supporting evidence. My comment was promptly removed for violating the "Be nice and civil" rule. When I looked back at the thread, I noticed that all posts critical of China had been removed while the whataboutist and denialist comments were left in place.
This is what the modlog of the instance looks like:
Definitely a trend there wouldn't you say?
When I called them out on their one sided censorship, with a screenshot of the modlog above, I promptly received a community ban on all communities on lemmy.ml that I had ever participated in.
Proof:
So many of you will now probably think something like: "So what, it's the fediverse, you can use another instance."
The problem with this reasoning is that many of the popular communities are actually on lemmy.ml, and they're not so easy to replace. I mean, in terms of content and engagement lemmy is already a pretty small place as it is. So it's rather pointless sitting for example in /c/linux@some.random.other.instance.world where there's nobody to discuss anything with.
I'm not sure if there's a solution here, but I'd like to urge people to avoid lemmy.ml hosted communities in favor of communities on more reasonable instances.
I have a small server in my closet which is running 4 Debian 12 virtual machines under kvm/libvirt. The virtual machines have been running fine for months. They have unattended-upgrades enabled, and I generally leave them alone. I only reboot them periodically, so that the latest kernel upgrades get applied.
All the machines have an LVM configuration. Generally it's a debian-vg volume group on /dev/vda for the operating system, which has been configured automatically by the installer, and a vgdata volume group on /dev/vdb for everything else. All file systems are simple ext4, so nothing fancy. (*)
A couple of days ago, one of the virtual machines didn't come up after a routine reboot and dumped me into a maintenance shell. It complained that it couldn't mount filesystems that were on vgdata. First I tried simply rebooting the machine, but it kept dumping me into maintenance. Investigating a bit deeper, I noticed that vgdata and the block device /dev/vdb were detected but the volume group was inactive, and none of the logical volumes were found. I ran vgchange -a y vgdata and that brought it back online. After several test reboots, the problem didn't reoccur, so it seemed to be fixed permanently.
I was willing to write it off as a glitch, but then a day later I rebooted one of the other virtual machines, and it also dumped me into maintenance with the same error on its vgdata. Again, running vgchange -y vgdata fixed the problem. I think two times in two days the same error with different virtual machines is not a coincidence, so something is going on here, but I can't figure out what.
I looked at the host logs, but I didn't find anything suspicious that could indicate a hardware error for example. I should also mention that the virtual disks of both machines live on entirely different physical disks: VM1 is on an HDD and VM2 on an SSD.
I also checked if these VMs had been running kernel 6.1.64-1 with the recent ext4 corruption bug at any point, but this does not appear to be the case.
Below is an excerpt of the systemd journal on the failed boot of the second VM, with what I think are the relevant parts. Full pastebin of the log can be found here.
Dec 16 14:40:35 omega lvm[307]: PV /dev/vdb online, VG vgdata is complete. Dec 16 14:40:35 omega lvm[307]: VG vgdata finished ... Dec 16 14:42:05 omega systemd[1]: dev-vgdata-lvbinaries.device: Job dev-vgdata-lvbinaries.device/start timed out. Dec 16 14:42:05 omega systemd[1]: Timed out waiting for device dev-vgdata-lvbinaries.device - /dev/vgdata/lvbinaries. Dec 16 14:42:05 omega systemd[1]: Dependency failed for binaries.mount - /binaries. Dec 16 14:42:05 omega systemd[1]: Dependency failed for local-fs.target - Local File Systems. Dec 16 14:42:05 omega systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Dec 16 14:42:05 omega systemd[1]: local-fs.target: Triggering OnFailure= dependencies. Dec 16 14:42:05 omega systemd[1]: binaries.mount: Job binaries.mount/start failed with result 'dependency'. Dec 16 14:42:05 omega systemd[1]: dev-vgdata-lvbinaries.device: Job dev-vgdata-lvbinaries.device/start failed with result 'timeout'. Dec 16 14:42:05 omega systemd[1]: dev-vgdata-lvdata.device: Job dev-vgdata-lvdata.device/start timed out. Dec 16 14:42:05 omega systemd[1]: Timed out waiting for device dev-vgdata-lvdata.device - /dev/vgdata/lvdata. Dec 16 14:42:05 omega systemd[1]: Dependency failed for data.mount - /data. Dec 16 14:42:05 omega systemd[1]: data.mount: Job data.mount/start failed with result 'dependency'. Dec 16 14:42:05 omega systemd[1]: dev-vgdata-lvdata.device: Job dev-vgdata-lvdata.device/start failed with result 'timeout'.
(*) For reference, the disk layout on the affected machine is as follows: ````
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS vda 254:0 0 20G 0 disk ├─vda1 254:1 0 487M 0 part /boot ├─vda2 254:2 0 1K 0 part └─vda5 254:5 0 19.5G 0 part ├─debian--vg-root 253:2 0 18.6G 0 lvm / └─debian--vg-swap_1 253:3 0 980M 0 lvm [SWAP] vdb 254:16 0 50G 0 disk ├─vgdata-lvbinaries 253:0 0 20G 0 lvm /binaries └─vgdata-lvdata 253:1 0 30G 0 lvm /data
vgs
VG #PV #LV #SN Attr VSize VFree debian-vg 1 2 0 wz--n- <19.52g 0 vgdata 1 2 0 wz--n- <50.00g 0
pvs
PV VG Fmt Attr PSize PFree /dev/vda5 debian-vg lvm2 a-- <19.52g 0 /dev/vdb vgdata lvm2 a-- <50.00g 0
lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert root debian-vg -wi-ao---- 18.56g swap_1 debian-vg -wi-ao---- 980.00m lvbinaries vgdata -wi-ao---- 20.00g lvdata vgdata -wi-ao---- <30.00g ````