Skull giver

You can convert a running ext4 system into BTRFS and even move back to ext4, but to optimise the file system there are quite a few tricks to run as well. They come down to “remove the ext4 metadata (can’t go back after that), defragment, balance, maybe defragment again” and there are tools out there that make this stuff doable though the GUI, but I wouldn’t necessarily recommend that approach I novices.

The cleanest switch would be to reinstall. Not just because of the steps above, but also to make sure the right subvolumes are set up with the right properties. This too can be done from a (mostly) running system, but it’s an absolute pain in the ass to have to do manually, especially if you’re not an expert in command line stuff.

ext4 works fine if you don’t want to deal with all of this, but you’ll have to keep an eye on things like backup sizes just a bit more often

If you can’t take advantage of Timeshift’s BTRFS support, you’ll probably need to keep an eye on disk space regardless.

All the .deb files are installed across system directories like /usr and /etc. If you only want backups of your files, just exclude everything outside /home and your data drive. This makes it more difficult to recover from a failed upgrade Windows System Restore style (as you exclude the system components from the backups) but hopefully you’ll never need that (or will be willing to reinstall and restore from backup when failure does happen). You may also want to exclude folders like $HOME/.cache and $HOME/.var if they’re present on your system. I think Chrome puts some of its cache in $HOME/.config as well, though I’d back up most .config folders myself.

If your storage is that limited and you’re already familiar with Timeshift, you may want to consider switching to BTRFS. It’s not very friendly when it’s almost full, but compression and deduplication can save a lot of disk space, especially with tools like Timeshift. Other filesystems also offer these features, but Timeshift doesn’t make use of anything but BTRFS as far as I know.

I get skin irritations regardless of how clean my smart watch is after my wrist gets wet. Not entirely sure why, but something to consider if cleaning doesn’t help.

Check the manual to see if there are specific cleaning instructions. You don’t want to accidentally damage any rubber seals with soap that’s too aggressive or scrub off a protective coating somewhere.

My watch came with instructions to wipe it down with clean water, then some standard disinfectant alcohol. If that doesn’t work, soap-free detergent is recommended (I didn’t know that existed in any mild form?), so I’m guessing my watch really doesn’t like soap.

I wouldn’t mess with stuff like alcohol on rubber/silicone bands without checking if it doesn’t melt the material. Accidentally making napalm by combining plastics and solvents is way too easy!

I wonder why that person decided to stir drama now. I guess they must’ve been upset after Ladybird got a good amount of investment money or something?

Seems like a lot of exaggerated claims of malice to me, even for Github drama. Assuming someone is transphobic for closing a trans person’s PR quite the stretch.

You can probably just swap the SSD if your dock uses a protocol that Windows’ bootloader can understand. Some USB 3.2/Thunderbolt docks just seem to work with Windows, albeit a bit slower because of hubs and such that aren’t always top quality.

Just try it. It either boots or it doesn’t. If it doesn’t, it’s probably a massive pain to get working in the dock (best of luck to you if you’ll still try).

You should also check for updates/update your new SSD’s firmware, probably under Windows. Not a lot of brands make Linux installers and the automatic tools that check compatibility generally aren’t part of the Linux firmware downloads.

Re: file transfer: make sure you have your Bitlocker recovery key, or disable encryption on the Windows partition so you can access it in Linux. Other than that, just copy over the files. Linux can read Windows’ file system just fine. If you load the right drivers, Windows can also read file systems like btrfs or ext4 just fine.

A lot of people are afraid of systemd expanding because systemd handles a lot of stuff, so distros are likely to support it rather than the mishmash of tools they personally prefer. It all started with the System-V/Upstart replacement and now very few distros have the patience to customise and roll out the 90s style service management anymore. Their preferences used to align with the mainstream, but no longer do these days, and that causes friction.

This process pushes people who prefer old tools to fringe distros, and newer software is less likely to work on their setups. They’re still free to use whatever system they like, of course, but the burden for developing and maintaining daemon management scripts is now on their fringe distro or themselves if their distro doesn’t have anything yet. I’d find that pretty annoying too, especially with how convoluted many older system management scripts are and how many moving parts are typically involved. Plus, some stuff like socket activation can’t even be done with some of the older init systems so people have to find alternatives.

I doubt anyone reeling against run0 was ever going to consider it anyway.

sudo had several severe security bugs caused by copying env variables so I’m not surprised run0 isn’t doing much of that. I’ve had to help a whole bunch of people fix the permissions/ownership on their Jo. E directory after running sudo so I can even see the point of jot copying $HOME by default.

I don’t think it’ll replace sudo necessarily, or doas would’ve done that already. It’s still useful as a shorthand for systemd-run and in some locked down system configurations I can see it being useful (i.e. when minimising the amount of SUID binaries). Maybe some elaborate enterprise setups will switch to it for security reasons, especially if they’re already leveraging PolKit heavily.

ActivityPub is actually a good way to authenticate things. If an organization vouches for something they can post it on their server and it can be viewed elsewhere.

AP has some pretty big issues when it comes to moving servers, expiring and re-purchased domain names, and other such edge cases. Servers either blindly accept new keys after a certain time, or are vulnerable to enabling key ransoming after hacks (the reason HKPK went nowhere).

We could just move to a “watermark” system where everyone takes credit for their contributions.

North Korea actually has this embedded in their government Linux distro and it works well as long as everyone who opens the file runs a supported OS. Not for AI, but to track who wrote what unpleasant documents, but still, it proves the idea can work.

On the other hand, how do you determine trust? I can generate a million plausible names and digital addresses on my computer. Half the images I see online are screenshots or screen recordings already (because “save as” isn’t available on “modern” websites).

In theory, we can solve this by simply having digital stuff be signed, but setting up a web of trust will be difficult. Especially since most of the internet is semi-anonymous.

Funnily enough, the Fediverse already signs most data, so this scheme is already active unintentionally here on Lemmy! But for all I know, you’re not really “Kevon Looney” and just a fake from another server.

The nice thing is that it already runs Linux. The less nice thing is that it’s running some ancient Linux 2.6 kernel with Android on top of it.

It should be doable to install Linux in some form or another onto it, but it won’t be easy like installing Linux on a PC.

DDG doesn’t have their own search index, they’re mostly using Bing and maybe a few fallback providers. They’re entirely reliant on other search engines that they purchase results from, they barely do any actual searching themselves. Things like image search even come from one single source (Bing).

Because you can’t just boolean search the entirety of the web the same way you do a local database. You’re not getting all results every time you search, that’d be insanely inefficient, so doing full filters like with boolean database search won’t work.

That said, based on my experience with Google, negations work just fine, as do double quotes. Last time I checked NEAR even worked pretty well. AND is implied, OR used to work but is probably derived from the rest of the query these days.

People hate it when their query doesn’t return anything. So, whenever you search for something and get very little results, search engines will relax their boundaries to find something that may answer your query.

Search engines in the early 00s had them because they required very specific phrase matches and the experience was horrible. You either got millions or results that didn’t relate to what you were searching for or you got none and had to start over.

At some point, search engines started interpreting what you mean instead of what you type. For most people, searching for “rain” and getting results about “precipitation” is exactly what they want. Using the 90s/00s search term syntax, you’d need to type “~rain” to also get synonyms, which is obviously a terrible user experience that serves only the most pedantic people.

There is a limited amount of creativity, but a properly “creative” AI, should not keep repeating the same design pattern over and over.

It’s generative AI, not magic. Repeating the patterns it was trained on is what it was designed to do, even if those patterns aren’t always entirely obvious.

I think the model has been overfitted on its training set, but you can’t expect the types of generative AI we have today to be creative.

Corporate stuff is probably already running on unsupported and unpatched Linux distros if they still haven’t migrated to Python 3. I doubt the new version of Fedora removing the binaries will make much of a difference.

That’s just a normal weather app. Google’s weather widget looks very close, and Samsung’s isn’t very different.

One or two overviews and a bunch of info blocks is all you’ll get from the popular weather APIs, so it’s hard to get creative. Maybe it could’ve added a map of sorts to make the weather stand out? But then you’d probably be copying some other weather app in the process.

Unless you have some kind of knockoff SSD, that ūsung SSD looks like something is corrupted to me. usb 1-10 device descriptor read/64, error -71 might be unrelated.

This could be a problem with RAM defects or overclocking. If your computer is overclocked, try setting it to stock configuration. Also run a memtest to check if your RAM sticks aren’t going bad. I don’t know what might’ve changed between 6.8.9 and 6.8.10 to cause this, but it could just be a coincidence (i.e. the kernel defaulting to a different RAM page that suffers from corruption for whatever reason).

These messages are actually part of the systemd startup sequence, so the kernel has already loaded at this point. This means the problem may not be the kernel, but the initramfs installed/generated for your computer. You can try regenerating your initramfs on Fedora by running dracut --regenerate-all as root. Before you do that, you may also want to double check your /etc/fstab to make sure nothing accidentally added a swap device for some reason.

Restart your ssh server to be sure (probably sudo systemctl restart sshd). No need to reboot your server for this.

I don’t know how reliable this is, but I usually go into htop to check if stuff needs to be restarted. Processes in red have been replaced or removed since starting.

That said, regular server reboots are a good idea to make sure kernel patches are applied. Can’t go wrong with a reboot just in case.

It is, as of a few hours ago according to the Manjaro website. Looks like the problem finally solved itself!

This usually happens when Manjaro doesn’t carry a package that Arch does carry (and that the package you’re trying to install from the AUR depends on).

This is always a risk when combining Manjaro with the AUR, as Manjaro is a few weeks behind Arch when it comes to packaging. You can try if the beta repositories have the package, but otherwise you’ll just have to wait for Manjaro to update its packages. It’ll probably resolve itself, eventually.

You can try looking on the Manjaro forums (I don’t see a workaround other than switching to testing/unstable) to check if there’s a fix, but please don’t bother the Arch/AUR people, they can’t help you.

Looks like the maintainer has better things to do

In post on the Gradience Discord, the tool’s primary developer David Lapshin (daudix) explains: –

“Archiving the project […] will make it clear that Gradience is, well, unmaintained, and will prevent the issue tracker from being filled with duplicates asking when new release will be out/why nautilus sidebar is white.”

“And, if someone will want to maintain it one day, it can always be unarchived with a press of a button.”