Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
Gentoo is GOAT. I am also glad that Arch exists though. Both have excellent wikis, good knowledgeable communities, lots of configuration options. In terms of pure speed, it is hard to beat a build it all from source as per your own custom USE flags setup like in Gentoo.
THIS WAS THE MEME I WAS ACTUALLY LOOKING FOR!! Thanks!
Those modules, manβ¦ theyβre the biggest cause ofβdare I say it?βbloat in the kernel.
For the few people here who may not know about it: thereβs a utility called modprobe-db that watches what kernel modules get loaded at runtime, and can generate a kernel build config file accordingly. Thereβs even an ArchWiki article about it. You need to keep it around for a while (e.g. several weeks or months) so it can get a proper sample of the modules you use; that way, your kernel can have all the modules you need (ask me how I know). If you do it right, however, you can slim down your compile time significantly.
Fun fact about monitors turning on slowly: did you know Windows has a bluescreen code for that?
The WIN32K_POWER_WATCHDOG_TIMEOUT bug check has a value of 0x0000019C. This indicates that Win32k did not turn the monitor on in a timely manner.
That's right, Windows will panic and throw a bluescreen if your monitors take a little too long to wake up. Had the pleasure of dealing with this suddenly becoming an issue and causing wide bluescreens on wakeup after an update back in mid-2024, on any Surface Dock using DisplayPort with specific Acer monitors.
Woah woah..... is there someplace in the event logs where this would show? Does this mean that you cannot run a windows computer headless?
It gets logged in the event viewer, yeah. That's how I discovered it, on account of the screens not waking up in time to show the actual bluescreen. The users were only reporting that their computers were deleting all their windows when waking up. From their perspective, all they saw was their computer taking a mildly longer time to wake up from deep sleep and then losing their entire session, but what it was actually doing was hard rebooting.
Headless is fine, the bug was specifically triggered when a computer woke up and detected a monitor exists, but the monitor took some unspecified amount of time too long to wake up. It was also fixed at some point, I'm not sure when, but it went on long enough that we swapped dozens of cables because it specifically only happened on the ones using DisplayPort, not HDMI.
Oh shit, this may be the problem I've been having with my laptop dock at work
Wow... I feel like I might have ran into this issue dozens of times. So cool the kinds of things I learn here
I feel like the boot time is almost entirely uefi ram timing shenanigans these days
I hate my monitor for that. Entering the bios is guesswork about when to press a key if I remember what key to press. Also I can't turn it on too early before the PC or it will go to stand by after not receiving a signal for two seconds and then take even longer.
I want a monitor turns on and stays on.
Let me guess, samsung odyssey? Had one of those, never again.
Friend even called me that he has fucked up his pc rebuild - his Samsung monitor was just not waking up because it literally turns off.
Typical Samsung product. Good hardware, acceptable build quality/ material selection, horrible software.
On mine you can't even select the input manually, the monitor always cycles through every input. Couldn't find anything on input 2 I just plugged in? Let's do another round of checking all inputs for 10 seconds, and again, and again.... And always finish on the input you started, or turn off if no active input is found.
Software always destroys their products.
All modern monitors are like this now. Dell, HP, Asus...
Doesn't detect input? Instant power off. Now you have to press the menu key every 5 seconds to try and find the input for your PC.
Beyond ridiculous. I have a Dell that's like 15 years old and it stays on for multiple minutes before going into power saving. It's glorious
I've learned the hard way that there's only one decent Samsung product - from big appliances to little electronics - and it's their phones (and even those leave questions on privacy).
in that case there are zero decent Samsung product lines.
horrible repairability, horrible privacy with all the built in bloatware and spyware, no more bootloader unlock to get rid of all of them, but even before they made that impossible they were the only android phone maker that required their own quirky tools for that, and blowing permanent efuses while at it.
What's this "boot" of which you speak?
Do people really turn their machines off these days?
Yes, I'm not wasting my hardware life and electricity for no gain.
Thermal cycling
You've got to reboot after kernel updates, otherwise it can't load new modules. I've been confused at least twice why something didn't load until.I remembered the reboot.
I think the command "systemctl kexec" would like to have a word. Great command to know if you have a VM on a system you dont manage / share with others.
Great command to know if you have a VM on a system you dont manage / share with others.
won't this kill all their processes?
So you can just run kexec if its installed on the distro. This tells the kernel to boot into another kernel. The reason to use it with systemctl is to properly shut down all the services running in userspace. That command will have systemd gracefully turn off all services and then the new kernel with whatever updates / modules can be loaded in a clean environment.
Its useful if say, you have a VM in a data center. Now most of them provide a web gui where you can turn your VM off and then on. But if you're lazy like me and already remoted into the terminal lol
but I still don't get it. couldn't you just systemctl reboot? it will boot the new kernel that way too. its supposed to be the same as from the web gui
I didn't know about that one.
Every day
yes
I thought arch was all about reducing bloat. Is gentoo better than arch?
Gentoo recompiles everything, so it can do optimisations based on your particular setup Arch can't.
You can also just recompile the kernel and any utils yourself on Arch, if you want
Yeah, but I'm using Arch cause I have better things to do. You guys have fun compiling your own stuff without me.
You can recompile the kernel in any distro. In Gentoo, you have to compile the kernel (because you compile everything).
In Gentoo, you have to compile the kernel
This is not true any more. Gentoo provides sys-kernel/gentoo-kernel-bin as an option.
Obviously arch can be rebuilt pretty easily, gentoo does almost nothing that arch can't, and rebuilding itself osn't one of those things. Look up ABS.
Arch is about telling other people what you use. If you use gentoo, you can take way more pride in you installation.
Arch is pourover coffee; Gentoo is those ridiculous Rube Goldberg setups that take 45 minutes to make a single cup. Both are for hipsters.
Ubuntu is that shitty Keurig machine with big plastic pods, but they call them "snaps".
Does that make Debian standard filter coffee? The coffee everyone can get behind π«Ά
Arch basically happens at a granularity of individual packages. You decide from the ground up which packages you actually need, which is how you end up with a comparatively minimal setup.
But yeah, if the package itself is big, then Arch doesn't usually deal with that. The Linux kernel comes with drivers for most hardware out of the box, which you can remove, if you know you won't need that hardware.
And while this can also be done on Arch, it is Gentoo's thing to do precisely that.
To add to this, the big thing you get when using Gentoo is to setup your compiler to use all of the optimizations for your exact CPU/other hardware.
The binaries for arch are built for generic x86-64, while your Gentoo system could bet setup to include AMD-specific optimizations or to remove code paths that you would never used based on your hardware.
The result will be that the binaries will typically be smaller and optimized specifically for your hardware.
The downside is that a system update will take you half a day of churning your CPU on compiling.
Keep going. Kevin can get smaller, leaner, faster and hopefully has apparmor or selinux already.
this reminds me i should update my kernel
Statements of the utterly deranged