nanook

@MicroWave When you pack a few hundred tonnes of gunpowder into a small building, that can happen.

@Pro It’s one thing to provide a definition and another to implement, without the latter it’s useless.

@5714 @Drusas Obvioously but older people don’t go to school. However, this whole blaming the weapon thing has gone too far. Need to start just putting the perpetrators to death and end this.

@daniel_callahan You’ve never seen a US Senator ACT this way.

@phantomwise @SpiderUnderUrBed Every program on your system has “kernel access”, it’s called “syscalls”, but actually being able to modify the kernel, that is another matter.

@MachineFab812 @SpiderUnderUrBed even if you have steamOS, what keeps you from downloading kernels from kernel.org and building?

@Godort @SpiderUnderUrBed That’s really the conundrum, in an open source kernel, where can you put anti-cheat that someone else can’t readily pull out?

@FlexibleToast @zero_spelled_with_an_ecks If that company built upon open source and had then to release their work because of the original license, then I can’t speak for others, but I’m ok with it. They can do original work or they can build on others, if they do the latter then they have to expect the same.

@Dark_Arc @LeFantome I’ve had mixed luck with debian in this regard. Bullseye to Bookworm was a smooth upgrade but some of the others have not gone so well.

@potentiallynotfelix You’re most welcome!

@potentiallynotfelix Ya gotta love it!

@binom If you film with a camera with a ntsc vertical reference rate of 59.95 hz you will see a beat note between the lights and the led lighting indicating it is not well filtered if at all. If you have a newer HiDef camera, most of them work at a 24Hz refresh rate, that IS a slow enough rate that you see jitter in the movement, they also will have a beat note if recording under most LED lights. Many cheap led lights just have a capacitive current limiter and that’s it. If you power them off of 50Hz you will see the flicker, if you get dimmable LED lights they will NOT have a filter. But I don’t want to interfere with anyone’s bragging rights.

@FlembleFabber Do you have LED lights in your house? Can you see 60Hz flicker?

@Rubanski if you have mdraid partitions, you also should add bootdegraded=true to the grub command line so the system will still boot even if a disk fails and an array is in the degraded mode.

@VinesNFluff Most people can’t honestly perceive any change in their visual field in less than 1/60th of a second except perhaps at the very periphery (for some reason rods are faster than cones and there are more rods in your peripheral vision) and even then not in much detail. So honestly, frame rates above 60 fps don’t really buy you anything except bragging rights.

@over_clox You are most welcome. This is one aspect I love about Linux, damned near everything is adjustable. Those adjustments aren’t necessarily well organized, but they are usually there, somewhere…

@over_clox You can adjust this with hdparm:

hdparm -B 254 /dev/sda (or whatever the drive name)
Will prevent spin down altogether.

hdparm -B 1-127 /dev/sda
Will allow spin down with ‘1’ being the most aggressive power management and 127 the
least.

I put these in /etc/rc.local so that it gets run by systemd at boot-up.

@queermunist @propitiouspanda I don’t think they’d put the funds into development that they do if that were the case.

@Rubanski If it’s booting into emergency mode, there are usually one of three issues, kernel is corrupt, a file system can not be mounted read/write, and this can be because of file system corruption or in the case of mdraid, because a raid device failed to self-assemble, or initramfs is broken. The easy way to fix most of these is to use an automated utility called boot repair, you download the ISO then burn to a thumb drive, then when you run into this kind of problem boot off the thumb drive. I’d start by trying to determine which of these it is, if you get into emergency mode then you at least have a shell prompt, try typing dmesg to see if there are any errors relating to the kernel, then check if all of the partitions are mounted and if they are all mounted read/write. If one or more is mounted read only this usually means that the automatic fsck found errors it can not fix and needs a manual run, in which case try fsck -f -y /dev/sdxx or /dev/nvmexnxpx, which ever the case may be (hard drive verses SSD). If this was the issue after the fsck successfully repairs the file system you should be able to boot successfully. If not, and nothing kernel related shows up in dmesg, then probably your initramfs has gotten hurt. In this case since you are new to Linux, boot repair is the easiest way to fix it. You can also fix manually but that is more complex, however if you need instructions on how to do this let me know and I will elaborate. Even doing so manually though requires another bootable Linux media, does not have to be boot repair, a popos install USB will also do.

@carzian I paid about $60 for a used unlocked Galaxy Android phone, whatever the dollar equivalent of 890 euros is, it’s out of my budget.