First, you break into the house, then you install an invisible backdoor, and then you can come and go freely.

It’s a “post-exploit” tool. It’s the persistent backdoor you install after you break in. It survives reboots, unlike most exploits.

apt dist-upgrade. No first dash.

Notice it’s apt not apt-get. That’s all they were saying.

Fix your title. The answer is “no”. People are getting the wrong idea.

From GIMP team: We are NOT rebranding GIMP

Take a time to read the commit messages and the commit diff.

Pacman has the worst syntax of all package managers. pacman -Syyurape

apt is fine, and zypper is the friendliest, I think. It’s similar to apt, but has obvious two-letter abbreviations for commands. It also has nice coloring of the output.

This should be in your title. Your title sounds like you’re ripping off user data from Piefed in order to put ads on it.

This is why you have 60 downvotes and all these people calling you an unethical jerk.

deleted by creator

Different than what? You mean between Linux and Windows? No, but you can have them pre-install an OS of your choice.

Oh, I see. I did some looking and it seems it’s a lightweight, UEFI-only replacement for GRUB.

I installed it last Summer. Does that mean I’m currently running a different init system?

Does it actually list the packages that are suggested?

If a package is recommended, it gets installed by default. They’re not strictly necessary for the core functionality of the main package, but they are commonly used by many users.

On the other hand, suggested packages are like plugins. They won’t necessarily be important to most users, but some might find them handy. Things like alternate backends for specific use cases, or a plugin to enable a specific (and rarely used) service.

I haven’t used apt in a while, but I don’t think there’s a way to automatically install all suggested packages. I think you just install them manually by copying and pasting the package names, and running additional apt install commands.

But unless you know what specific usage you need before I probably wouldn’t bother.

I’ve tried nothing and I’m all out of ideas.

–cpu-moe

The real answer is to open it up and solder in a wire that shorts out the LED.

I’ve never heard of that nor had that happen to me.

That’s funny, I prefer the opposite (actually changing bits) because then it works with every player and device.

I use QMP3Gain. It actually changes the bits in the file so the files work with every app and player without needing to rely on tags. However, It also adds tags to the file which let you undo the changes later, if needed (it’s lossless).

It has two modes. You can modify all the files in an album equally so that they play at the same relative volume. I guess the loudest song is set to your target volume and then the rest are adjusted relative to that. It’s great because it doesn’t ruin the flow of albums whose tracks connect seamlessly. Or you can modify tracks irrespective of other tracks, which is good for random singles you own.

The result is, songs in your entire library all sound more or less the same volume. The exception being that quiet tracks from certain albums will still be quiet.

You can drag every full album you own into the UI, and do them all at once in album mode. It works based on tags. Then do the same with all singles you own in track mode.

It defaults to 89.0 dB, but I prefer to use 95 dB because some devices just don’t have enough volume. A tiny bit of clipping is imperceptible because decoders account for it. Many of your current MP3s already have clipping, and I’m sure you haven’t noticed. So don’t worry if you see red "Y"s in the clipping column.

It uses the ReplayGain algorithm. Once in a while there’s a track that it just doesn’t get right. A certain single will just come out too loud or quiet and needs a different dB value than everything else. Out of the thousands of MP3s I have maybe five files have been like this.

How else are you going to rice your Debian install?

Well, my laptop only has one spot for a drive. I guess if you have more than one, it should work. The main point is never share a drive with Windows. Windows will mess it up.

Personally, I dual boot with an external NVMe drive. It works great! I have Linux and only Linux on the internal drive and Windows gets relegated to an external one.

The trick to getting it to work is: you have to temporarily install the NVMe drive internally in order to install Windows onto it. Then you pop it into an external enclosure and it just works. Just make sure your BIOS is set up to boot USB devices before internal drives.

OpenSUSE Tumbleweed has a GUI for almost everything. It has a nice GUI for basic system config, and uses YaST2 for deeper settings, and it uses Discover for Flatpaks as well as system library updates.

Although, I have seen a couple people say Discover shouldn’t be used for doing system updates because it can fail, and to only use it for Flatpak updates and installs. I dunno. But it’s not like typing sudo zypper dup to do a distro upgrade is hard, so I just do that out of an abundance of caution.

OpenSUSE has some other cool features too, like having Snapper installed by default for system snapshots. It’s pretty easy to roll back if an upgrade goes sideways. There’s a boot entry that lets you open a previous snapshot as read-only and then you can make that snapshot permanent by creating a new top-level snapshot from it. So then you can at least use your computer while you try to figure out why the upgrade you did failed.

You’ll probably want to use KDE as your desktop environment. It’ll be somewhat familiar if you’re use to Windows, and it has a lot of features that make it comfortable to use.

There are lots of good YouTube videos on why OpenSUSE is pretty cool. Check some out.