Linux

59012 readers

777 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

psa: snapd leads to massive slowdowns in boot time (lemmy.eco.br)

submitted 1 week ago by bunitor@lemmy.eco.br to c/linux@lemmy.ml

12 comments fedilink hide all child comments

i run debian 13 on my laptop. it runs on a 5200rpm hard disk, so some bootup slowdown is to be expected, but it got really bad for some reason. booting up could take up to 3 minutes just to get to the display manager

after running systemd-analyze blame i found the two main culprits: docker and snapd. i had snapd and flatpak installed so that i could have access to as many applications as i could, but it seems that snaps have a huge amount of overhead. i knew about the one million mountpoints caused by snaps, but the amount of services they have to start on boot surprised me. snapd alone took 30 seconds to start and then there were its dependencies

my boot time is now down to 1min 50s. i recommend anyone who still has snapd installed on a non-ubuntu distro to uninstall it

you are viewing a single comment's thread
view the rest of the comments

[–] trevor@lemmy.blahaj.zone 8 points 1 week ago* (last edited 1 week ago)

Because their sandboxing format subtly breaks so many applications (more than flatpak) and Canonical very nefariously co-opts your apt install <package> with a deb package that's actually a stub to install the Snap version, so when your shit breaks, you can waste hours before you realize that they fucked your installation.

Beyond that, Snap cold start times (installations or updates) are slow as shit (yes, even with LZO compression), and since each snap application can update on its own, you'll also encounter random times when your shit appears to "freeze" but what's actually happening is Canonical is busy polluting your loopback devices to decompress their shittified version of your app.