The question is more like where else would you put your backups?

If you care that much about the data then yeah you’ll probably take the time to export that snapshot to a third-party service, possibly another cloud. But if you’re just going to throw it in an S3 bucket or something, you’re basically just manually doing what AWS already does for you internally, so a complete waste of time.

Make Docker depend on the mount. You can simply use systemctl edit docker.service and then

[Unit]
Requires=path-to-your-smb.mount
After=path-to-your-smb.mount

Then it will guarantee it’s mounted by the time Docker starts.

On top of everything the others have said, another way this isn’t possible reliably is servers that just accept all email and forward it to a catchall address.

Some also have trap addresses where sending email to it will result in putting that address directly into the spam filter and everything coming from it feeds into training the spam filter. I’m an individual, not a company, so all the common IT, HR, support, press, sales, whatever addresses are traps.

When websites force me to enter an email, I enter one of the traps so everything they send me and everyone they share that email with gets the banhammer instantly, and I can track which asshole website did that to me as well.

The problem with that is that the rest of the ecosystem keeps moving on, and the more time passes the more left behind you are. So you stick with old versions of whatever you use and when the time comes to upgrade it hurts even more because it’s not just the OS that works differently but also all the software you’re using including Python, Ruby, PHP, NodeJS or whatever your software stack is built on. So you have to upgrade all of that code too. At some point you might as well start over from scratch which just makes it even harder and daunting to tackle to you increasingly push it further until you hit the 12 years and you’re forced to do it with time constraints

The proper solution to critical systems you’re too afraid to upgrade is to… upgrade and redeploy them more often in test environments so you’re not afraid of upgrading the system. And the very companies that would pay for the 12 years of support are the ones that really should have the whole thing fully automated and fully tested.

What kind of filename do they have? How big are they?

My guess would be that they’re Android thumbnail files or some sort of hidden metadata file. Possibly some raw jpeg because all the parameters are expected to be fixed size so they didn’t bother with the header. Or it’s a custom header.

But even then, that’s a lot of zeros for an image format.

Does it seem to have a JPEG header later in the file? It could be a header followed by a normal JPEG file too.

That guy’s channel got blessed by the algorithm, got it recommended yesterday as well.

Yep and there’s even a BIOS option for that use case! I really like they they go “oh, people use the parts for that, we’ll add a feature for it!”

Fingerprint reader working perfectly on my FW16. Not sure it’s the same reader module, but getting it set up on Arch was easy, pretty much worked out of the box in Plasma 6. Adding fprint to pam.d/sudo also worked right out of the box for fingerprint sudo.

I have one (FW 16 AMD), I don’t have any complaints so far. It comes mostly assembled but you put your RAM, SSD, screen bezel, keyboard, touchpad and all the port modules yourself. The machine is well built and genuinely very easy to work with. You can swap the keyboard and touchpad without touching a screw.

For the most part it seems like they’re holding up to their promise, you can buy a new motherboard for a CPU upgrade, remove the old one, put the new one in, and you’re good to go with the rest of your existing stuff (as long as it’s compatible, if the new board needs DDR5 instead of DDR4 then you need new RAM too but that’s expected). So far everything I’ve disassembled as part of the firs assembly has been a breeze. It’s a very nice laptop to work on and swap parts that’s for sure. You get the assurance that you can swap the battery, input modules, IO modules for the foreseeable future.

Where I’ve been disappointed is the third-party ecosystem for it is not what I was hoping it would be, there’s not a lot of third-party modules for it. But the designs are all open-sourced so you can 3D print parts for it. Maybe in the future we’ll have more modules. Overall though, it’s not like you could even think about that on any other laptop brands, you get the laptop and it’s what it’ll be for the rest of its life.

Runs great on Linux, most of the company actually uses Linux so support for Linux is very good. All of the models will run Minecraft very well, Minecraft in particular has been known to run significantly better on Linux to begin with, especially on Intel graphics where the OpenGL drivers on Windows are terrible.

No. This gets painted on the framebuffer when the OS boots up, it’s after firmware is done with it. It’s barely any different than when full graphics mode load up.

LogoFAIL is based on replacing the BIOS logo with one that will trigger the exploit in firmware code, before the OS even starts.

I would trust them more than Microsoft because at least they would actually store it encrypted safely and not just basic ACLs that are easy to bypass.

Even with a root shell on macOS you can’t bypass certain things like access to the camera for example. You’d have to work way harder to access recall data, not in a way that malware can trivially access.

I still wouldn’t use it though, because I think the whole thing is dumb and I don’t need my computer to spy on me so I can remember what I did yesterday. I have browser/shell history for that.

They share the same partition, but they’re treated like independent filesystems. They can have different mount options, so on one you can enable compression but not another some you may want to disable Copy-on-Write, etc. That’s also useful so you can rollback a system update without also rolling back your data or vice-versa. You can also store multiple distros each in a subvolume and boot different ones all while sharing the same partition and not wasting space. If you have multiple users it’s worth having a subvolume each so each user can independently rollback their home directory. Maybe you want your projects on a subvolume so you can snapshot and btrfs-send it frequently.

I don’t use btrfs but on ZFS I have tons of datasets: steam library gets large recordsize and light compression, backups are heavily compressed and encrypted, VMs have a dataset tweaked for disk images, my music and movies also have a larger recordsize but no compression. I have one that’s case insensitive that’s shared with Windows machines and Wine stuff. I cap the size of caches and logs.

It’s very versatile.

But it’s already up to date. It shows updates to the version they’re already using.

Lemmy updates are a little touchy and buggy, can’t blame them for taking their time. It’s only been out for like a week. They have to load a backup on another server and test it out to see if there’s any issues with the upgrade and how long it’ll take. They have to plan downtime and set aside enough time to do it, handle any issues and a potential rollback.

My feeling about that is that I should assume anyone who could monitor my traffic should be assumed to do so and I therefore should apply reasonable defenses regardless. Even if the government doesn’t do it, hackers around the world will. That means the moment it leaves my router, it’s assumed compromised.

Same for smart Internet connected devices. The government might be listening, but I certainly don’t trust the manufacturer to not be listening for the purpose of advertising either.

How many stories broke out recently of ISP router having been compromised by foreign hackers for years? Yeah. The Internet is the wild west.

I believe it’s also highly recommended to use Xscreensaver specifically as the author is well aware of the risks and limitations and does as much as possible to guard against all known ways to bypass it.

That definitely looks like a Cinnamon bug, specifically its screensaver component. Worst case they’ll direct you to where to report the bug, or they’ll move the ticket themselves.

Also, obligatory this is one of the many ways X11 is insecure and unsuited to proper screen locking. Lock screens on X11 are just fullscreen windows you pray the window manager won’t ever allow to unfocus, close, resize or move or not cover the rest of the desktop.

FFmpeg should be able to do that without reencoding the video, possibly also audio. Basically you want to use -c:v copy -c:a copy and remap the right channel to a single mono channel, and remux all of that in a new output file.

https://trac.ffmpeg.org/wiki/AudioChannelManipulation

Windows 95 and Macintosh LC, elementary school computer lab stuff. My grandpa had a Windows 3.1 IBM PS/2. Those were all pretty old and practically obsolete computers when I used those, 98SE was out and ME was right around the corner.

My very first Linux distribution experience was Mandrake Linux I believe version 9 or something like that. Didn’t last that long though, I revisited Linux later with Ubuntu 7.04 which is when I actually switched to Linux full time.

ArchLinux since 2011. Still running that install to this day!

None or negligible. It’s a container which uses namespaces just like Flatpak and Docker. It depends solely on what you run inside of it: there’s no VM or anything to just eat away cycles, it’s a process like any other on your host kernel.