CMahaff

Curious did you get the survey popup in desktop mode on the deck? Or does it work in "big picture"?

I got the hardware survey on my Windows PC, but not on my Steamdeck. So I wonder if there is only 1 survey per user, and most people don't use a steamdeck exclusively?

One thing you could do that I don't see mentioned here is to install Virtual Box in Windows and create a Linux Mint Virtual Machine. It's basically installing a computer within a computer. You should be able to find some tutorials online.

This would let you try Linux Mint in a sandbox within Windows so that you could experiment a bit with everything before changing anything.

Just keep in mind that within the VM, things will be less performant, especially graphically, and certain peripherals, etc. might not work. But it would let you test out installing the software you want, the cloud storage solution you want, browsing around, etc.

Speaking of graphics, you'll want to do some research about how well supported your GPU is. It will almost certainly "work" out of the box, but if you want to get the most performance out of it, like Windows, you're going to need special drivers. I've heard Nvidia can be a bit of a pain, but I think it varies by model.

I wouldn't be too worried about the touch screen as that will probably work - or at least has on every laptop I've tried. I've had more issues with things like fingerprint scanners generally speaking. Definitely check out everything you can think of when you install, like Bluetooth, cameras, microphone, peripherals, etc. Oh and when using the laptop definitely manually knock yourself down out of performance mode using the upper-righthand corner in gnome. For me at least, it makes a huge difference in battery life if I'm in performance vs balanced vs power saver. Windows is better at automatically making those adjustments.

I've also heard that lately Microsoft is making dual-boot harder - notably that Windows updates will just casually break your dual-boot and revert it to just Windows. I don't know the details since it's been years since I've done it myself, but something to keep in mind.

Finally I'll throw out there to make sure you have a recovery plan if the install goes south. Have all your files backed up. Have a copy of Linux and Windows installers ready. It honestly should be fine, but especially if this is your only PC you don't want to be stuck if you have some kind of issue, accidentally blow away your laptop's SSD, etc . Not trying to scare you or anything, but better safe than sorry, right?

I'm pretty sure @[email protected] has said before what he uses. I thought back in the day it was publicly listed with the expenses, but I couldn't find it.

The most recent update I found was here: https://lemmy.world/post/75556

But it could definitely be old information, I'd take the other commenter's advice and ask in the admin channel to be sure.

More of a debugging step, but have you tried running lsinitrd on the initramfs afterwards to verify your script actually got added?

You theoretically could decompress the entire image to look around as well. I don't know the specifics for alpine, but presumably there would be a file present somewhere that should be calling your custom script.

Really incredible that the thrusters still function at all after all this time - and that it has any fuel left / usable fuel after all this time.

It looks like there are instructions here about hosting your own flatpak instance: https://docs.flatpak.org/en/latest/hosting-a-repository.html

Doubling what Klaymore said, I've seen this "just work" as long as all partitions have the same password, no key files necessary.

That said, if you needed to use a key file for some reason, that should work too, especially if your root directory is one big partition. Keep in mind too that the luks commands for creating a password-based encrypted partition vs a keyfile-based encrypted partition are different, so you can't, for example, put your plaintext password into a file and expect that to unlock a LUKS partition that was setup with a password.

But the kernel should be trying to mount your root partition first at boot time where it will prompt for the password. After that it would look to any /etc/crypttab entries for information about unlocking the other partitions. In that file you can provide a path to your key file, and as long as it's on the same partition as the crypttab it should be able to unlock any other partitions you have at boot time.

It is also possible, as one of your links shows, to automatically unlock even the root partition by putting a key file and custom /etc/crypttab into your initramfs (first thing mounted at boot time), but it's not secure to do so since the initramfs isn't (and can't be) encrypted - it's kind of the digital equivalent of hiding the house key under the door mat.

Out of curiosity, what content are you looking for? Discovery on Lemmy can be a problem, but sometimes the communities are there and even active, just buried.

But may I also suggest searching by Top Day/12-hour/6-hour to see the most active posts. Lemmy's scaled algorithm still doesn't get it quite right IMO.

The CEO said they were going to add pay-walled subreddits at an earnings call.

So... Yep.

I know for me, at least with gnome, toggling between performance, balanced, and battery saver modes dramatically changes my battery life on Ubuntu, so I have to toggle it manually to not drain my battery life if it's mostly sitting there. I don't know if Mint is the same, but just throwing out the "obvious" for anyone else running Linux on a laptop.

Found a blog post that gives a quick overview of how to do git via email in general: https://peter.eisentraut.org/blog/2023/05/09/how-to-submit-a-patch-by-email-2023-edition

So at least from my understanding you'd make your changes, email the contents of the patch to the maintainer, and then they'd apply it on their side, do code review, email you comments, etc. until it was in an acceptable state.

There's also the full kernel development wiki that goes into all the specifics: https://www.kernel.org/doc/html/v4.16/process/howto.html

(I never got through the whole thing)