r00ty

Then I suggest they use an XNOR pointer instead! Checkmate patent trolls!

That should all be covered in the unit tests.

No. That’s just because the thread simulating your consciousness has leaked too much memory. So when you sleep the thread saves important parts of the memory map and terminates and a new one is started with an empty memory map ready for a new “day” .

Yes. But one less thing it can do.

We’d also be entirely unaware of reboots. Our reality would just resume from the last save point and we’d just move on like nothing happened.

How do you know? Just because the repository is hosted outside of our space-time. Doesn’t mean it’s not an open source repository.

I’m sure I’ve said all this before. But still. LLMS are very useful tools I don’t doubt that. The problem that no organisation that is “embracing” AI is really considering is how they work.

They essentially rewrite code or art or content they have seen before. If they replace developers, artists and authors/article writers wholesale the only source of new content will be, other AI.

It’s been known from the start that AI feeding on AI very quickly degenerates today garbage in garbage out.

They are also (currently) unable to innovate. So use of AI is going to stifle innovation or even completely kill it.

These are the medium to longer term problems that might only be really realised when the developers, artists and authors have moved onto other work and a lot might just not want to come back.

That’s my main problem with the wholesale use of AI. Used as a tool to complement people doing their job, makes sense and is possible to maintain going forward.

Here you go

#include <iostream>
#include <csignal>
#include <unistd.h>

void sigusr1_handler(int signal)
{
	std::cout << "Signal USR1" << std::endl;
}

int main()
{
	std::cout << "Installed handler for USR1" << std::endl;
	std::signal(SIGUSR1, sigusr1_handler);
	while (1 == 1)
	{
		usleep(5000000);	// 5 seconds
		std::cout << "Waiting for signal" << std::endl;
	}
}

That will help you read at least one of them.

I’m going to argue that it’s a little of both. While I doubt Ofcom have much chance being able to actually recover money through legal channels because of US constitutional amendments, they must have thought about this and the next step is likely to be an even more draconian “great firewall of britain” moment. Which of course will likely be equally as trivial to bypass as the age verification so…

They’re out there and not so hidden. If you look, you’ll find them. There’s definitely an iptv community out there.

This story seems a bit weird to me. A lot of iptv operators don’t sell directly to people, rather wholesale to dealers.

So I bet they got a dealer here is all.

It’d look worse without the patches to be fair.

Linux secure boot was a little weird last I checked. The kernel and modules don’t need to be secure boot signed. Most distros can use shim to pass secure boot and then take over the secure boot process.

There are dkms kernel modules that are user compiled. These are signed using a machine owner key. So the machine owner could for sure compile their own malicious version and still be in a secure boot context.

Yep. Also, I did clarify that I would usually do an overall upgrade at the same time.

I get the message there’s an upgrade. Say I’ll do it myself, go to console.

yay -S discord (or more likely just do an overall upgrade and reboot, what they hell)

Restart discord.

But this is the crucial thing. It wasn’t in the repository. It was in the tarball. It’s a very careful distinction because, people generally reviewed the repository and made the assumption that what’s there, is all that matters.

The changes to the make process only being present in the tarball was actually quite an ingenius move. Because they knew that the process many distro maintainers use is to pull the tarball and work from that (likely with some automated scripting to make the package for their distro).

This particular path will probably be harder to reproduce in the future. Larger projects I would expect have some verification process in place to ensure they match (and the backup of people independently doing the same).

But it’s not to say there won’t in the future be some other method of attack the happens out of sight of the main repository and is missed by the existing processes.

Yeah, but asking film/tv producers for permission would kill my content collection!

It’s for backup purposes mainly. A lot of cloud backup providers don’t store permissions.

So if I restore the data I can then restore the permissions after. So these are the folders I am backing up (with some exceptions in /var)

OK so it’s fairly simple. You need to install the acl package (or whatever equivalent package contains getfacl/setfacl. Then you can use that to dump the data from an entire structure into a file (I also then bzip that). Then I backup all installed packages to help with a restore too.

So the script looks like:

#!/bin/bash
cd /etc
/usr/bin/getfacl -R . | /usr/bin/bzip2 -9 >PERMISSION_BACKUP.bz2
chmod 600 PERMISSION_BACKUP.bz2
cd /home
/usr/bin/getfacl -R . | /usr/bin/bzip2 -9 >PERMISSION_BACKUP.bz2
chmod 600 PERMISSION_BACKUP.bz2
cd /root
/usr/bin/getfacl -R . | /usr/bin/bzip2 -9 >PERMISSION_BACKUP.bz2
chmod 600 PERMISSION_BACKUP.bz2
cd /var
/usr/bin/getfacl -R . | /usr/bin/bzip2 -9 >PERMISSION_BACKUP.bz2
chmod 600 PERMISSION_BACKUP.bz2
/usr/bin/apt list --installed | /usr/bin/bzip2 -9 >/root/INSTALLED-PACKAGES.bz2
chmod 600 /root/INSTALLED-PACKAGES.bz2

To restore you change to the folder the backup was taken from, unbzip the file (or uncompress live via pipe) and use setfacl --restore=<file>

Yeah. Only on my phone right now but will get it and post here later/tomorrow.

I mean, too late for you now. But I have a script that backs up just the permissions and owners for a given folder hierarchy.

I use it because I backup to a cloud backup platform that doesn’t save them. So these files are backed up with the data so the files and permissions/owners can be restored in an emergency.

But you could of course also use the file to restore permissions after a user generated mistake too.