Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
Mint uses systemd, so just use it;
systemd-analyze/systemd-analyze blame.You can also visualize it;
This is the second time I hear about systemd-analyze, which is funny because the first time was earlier today in that Brodie Robertson video about that pewdiepie video...
Anyway, I checked it out and the only thing I noticed was that cups took a whole second, which wouldn't matter, except that I hardly have a printer to print with anyway, so I disabled it. (could also just remove cups I guess)
I feel like the issue is pretty prevalent in the community as systemd not being incredibly popular with the fogies (myself included). Systemd is expanding at an exponential rate and the documentation is difficult to sift through for niche things like this.
But yes, it does exist and works relatively well.
This is so cool. I don't know how yall know all this stuff but thanks for sharing ! My startup is 1 min 21 seconds. I know it should be more like 20 seconds
I think that's really an oversimplification--it really all depends. Systems won't boot in under 20 seconds under all circumstances, and just because your system takes a while to boot doesn't necessarily indicate there's an issue.
But either way,
systemd-analize blamewill help you track down some possible issues and hopefully correct them.Another thing you can try if you're running Gnome, is to edit the
application.desktopfile in your system application launch folder and add a startup delayX-GNOME-Autostart-Delay=60to some non-critical applications that you still want to run at startup. This will ensure that not everything tries to star at once, but you still get all your helpful apps to run at startup.Considering that from my own experience systemd tends to increment boot times by a factor of about 20x due to insisting about things like raising a wifi interface that won't ever connect because you're later on supposed to plug in the wifi password (no save to store), which is an outright historic systemd problem, I wonder: is
systemd-anamyze blameat least honest enough to recognize the fault is in its own design, or will it always blame it on something else in the system?I couldn't tell you. Personally I avoid systemd. My daily driver is Alpine Linux. lol
Alpine? How does it do? I've heard it's pretty good for containers but at the same time some reasonable complaints for end-user workflows such as "it doesn't even have locales".
It has its quirks. But personally I prioritize performance over just about anything else, so I tried it as a daily driver and I haven't found anything yet which would make me drop it. I especially like it in headless environments. All my VPS run it, and it runs critical infrastructure which I'm responsible for that monitors oil and gas extraction rates--so some pretty critical infrastructure.
Pretty rock solid.