this post was submitted on 06 Dec 2025
547 points (97.9% liked)

linuxmemes

28380 readers
1058 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    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.

    founded 2 years ago
    MODERATORS
     
    top 50 comments
    sorted by: hot top controversial new old
    [–] rezad@lemmy.world 161 points 5 days ago (1 children)

    OP is not updating his Arch system regularly.

    his previous update must have been at least two hours old.

    [–] SaltyIceteaMaker@lemmy.ml 25 points 5 days ago (1 children)
    [–] rezad@lemmy.world 71 points 5 days ago (1 children)
    [–] victorz@lemmy.world 11 points 4 days ago

    I would swap the two characters in this image. I'm the user initiating the upgrade and the system is like "come on, not every day, right?"

    [–] alecsargent@lemmy.zip 157 points 5 days ago (1 children)

    I'm a simple man, I see a negative Net Upgrade Size and I get horny.

    [–] BurnedDonutHole@ani.social 31 points 5 days ago* (last edited 5 days ago) (1 children)

    I was going to ask why then again I thought to myself why not? And couldn't find a good answer. You do your thing my horny internet friend. I'm sorry for interrupting, I'll take my leave... α••(ᐛ)α•—

    [–] luciferofastora@feddit.org 10 points 4 days ago (2 children)

    Meanwhile, I'll stay and watch.

    The update, of course.

    [–] wizblizz@lemmy.world 2 points 4 days ago (1 children)

    Of course! We have a special chair for you to sit in.

    [–] qjkxbmwvz@startrek.website 1 points 3 days ago

    I assume you're referring to the cuckpdate chair.

    [–] BurnedDonutHole@ani.social 1 points 4 days ago

    (β€žΰ²‘Ο‰ΰ²‘β€ž)

    [–] Buffalox@lemmy.world 40 points 5 days ago (9 children)

    22.8 GiB install size !?
    WTF?

    I must admit I don't recall the size of my own installation, but that seems HUGE!
    Anyways congratulations on getting it trimmed. πŸ˜‹

    [–] silenium_dev@feddit.org 36 points 5 days ago (1 children)

    If you're doing anything with GPU compute (Blender, AI, simulations etc.), just ROCm, CUDA or oneAPI alone will take up half of that

    [–] Buffalox@lemmy.world 5 points 5 days ago* (last edited 5 days ago) (1 children)

    On my system Blender is only Β½ a gig with all dependencies...

    [–] devfuuu@lemmy.world 17 points 5 days ago (1 children)

    You need to start installing more electron applications and a bunch of jvms too.

    [–] SmoochyPit@lemmy.ca 14 points 4 days ago

    CLEARLY This user doesn’t use corporate desktop apps

    [–] rustydrd@sh.itjust.works 17 points 5 days ago (1 children)

    Larger than my entire root partition (currently at 21GB), but that's because I made the fatal mistake to limit the partition to 25GB when I set it up. So I have to keep it trim, and I envy OP deep down.

    [–] Buffalox@lemmy.world 4 points 5 days ago

    Haha I did that once too, because I had a system that when upgrading I wanted a separate home partition so I could just reassign it to my new install.

    [–] Nalivai@lemmy.world 7 points 4 days ago (1 children)

    That's like what, one and a half instances of Electron

    [–] _stranger_@lemmy.world 4 points 4 days ago

    in reality it's like 70, which is still insane

    [–] Andrew15_5@mander.xyz 6 points 4 days ago

    Akchooly it's 22.3 GiB.

    [–] Sxan@piefed.zip 3 points 4 days ago (1 children)

    Anytime Factorio gets an update, ΓΎe entire game downloads again, and it ain't small.

    [–] Buffalox@lemmy.world 5 points 4 days ago (1 children)

    Which distro has Factorio as part of the standard package system?
    Seems like a nice way to save €32,-.

    [–] Sxan@piefed.zip 1 points 2 days ago

    Oh, I completely skipped ΓΎe cost part. You still have to pay for ΓΎe game -- it just gives you a way to maintain ΓΎe installation ΓΎrough AUR.

    [–] SaltyIceteaMaker@lemmy.ml 5 points 5 days ago

    there are a lot of things that i only used once, or that are duplicate in case something breakes lol

    [–] cole 4 points 5 days ago (2 children)

    lol mine is like 76GB. have been running the same install for going on 9 years now

    [–] Ricaz@lemmy.dbzer0.com 4 points 4 days ago

    I'm sorry but that's fucking insane.

    I thought I was untidy but this is next level

    [–] Buffalox@lemmy.world 7 points 5 days ago* (last edited 5 days ago) (1 children)

    76 GB packages from you Linux distro? Did you simply install ALL packeages?

    [–] locahosr443@lemmy.world 8 points 4 days ago

    If you install all the packages you can't get sudden fomo at 3 am.

    It's the key to a restful night

    load more comments (2 replies)
    [–] Jankatarch@lemmy.world 5 points 3 days ago (2 children)

    Remember to yay -Scc once in a while

    [–] TechieDamien@lemmy.ml 1 points 3 days ago

    paccache can be configured to keep x amount of old packages and can be added as a pacman hook, so you never need to run that yourself!

    [–] rickywithanm@aussie.zone 3 points 3 days ago (1 children)

    I’m fairly new to arch what does the -Scc flag do?

    [–] Jankatarch@lemmy.world 3 points 3 days ago

    Clears cache.

    [–] MangoPenguin@lemmy.blahaj.zone 13 points 5 days ago (4 children)

    Download of 6GB is wild, is that re-downloading the entire package for each one that needs an update? Shouldn't it be more efficient to download only the changes and patch the existing files?

    At this point it seems like my desktop Linux install needs as much space and bandwidth than windows does.

    [–] Olap@lemmy.world 16 points 5 days ago (2 children)

    Patching means rebuilding. And packagers don't really publish diffs. So it's use all your bandwidth instead!

    [–] definitemaybe@lemmy.ca 29 points 5 days ago (2 children)

    Which is WAY more economical.

    Rebuilding packages takes a lot of compute. Downloading mostly requires just flashing some very small lights very quickly.

    [–] cmnybo@discuss.tchncs.de 6 points 5 days ago (1 children)

    If you have multiple computers, you can always set up a caching proxy so you only have to download the packages once.

    load more comments (1 replies)
    [–] Olap@lemmy.world 3 points 5 days ago (1 children)

    Yeah, totally is. There's a reason nobody publishes diffs

    [–] Ephera@lemmy.ml 2 points 4 days ago (1 children)

    openSUSE Leap does have differential package updates. Pretty sure, I once saw it on one of the Red-Hat-likes, too.

    But yeah, it makes most sense on slow-moving, versioned releases with corporate backing.

    [–] Olap@lemmy.world 2 points 4 days ago (1 children)

    Ooh, got any links on how Leap does this? My searching isn't yielding much

    [–] Ephera@lemmy.ml 2 points 4 days ago (2 children)

    Had to search for a bit, too, but finally found the relevant keyword: Delta RPMs
    (Which also explains why it's a Red Hat / SUSE thing. πŸ˜…)

    Here's a decent article, which links to some more in-depth explanations: https://www.certdepot.net/rhel7-get-started-delta-rpms/

    [–] Olap@lemmy.world 2 points 4 days ago

    Thanks, really well hidden feature here for someone I'm sure

    [–] Ricaz@lemmy.dbzer0.com 1 points 4 days ago

    I don't think anyone actually uses these

    [–] SlurpingPus@lemmy.world 1 points 3 days ago

    With stuff like rsync, diffs can be calculated on the fly. But it requires way more server cpu than just chucking files onto the network.

    [–] Ephera@lemmy.ml 5 points 4 days ago (1 children)

    This doesn't work too well for rolling releases, because users will quickly get several version jumps behind.

    For example, let's say libbanana is currently at version 1.2.1, but then releases 1.2.2, which you ship as a distro right away, but then a few days later, they've already released 1.2.3, which you ship, too.
    Now Agnes comes home at the weekend and runs package updates on her system, which is still on libbanana v1.2.1. At that point, she would need the diffs 1.2.1β†’1.2.2 and then 1.2.2β†’1.2.3 separately, which may have overlaps in which files changed.

    In principle, you could additionally provide the diff 1.2.1β†’1.2.3, but if Greg updates only every other weekend, and libbanana celebrates the 1.3.0 release by then, then you will also need the diffs 1.2.1β†’1.3.0, 1.2.2β†’1.3.0 and 1.2.3β†’1.3.0. So, this strategy quickly explodes with the number of different diffs you might need.

    At that point, just not bothering with diffs and making users always download the new package version in full is generally preferred.

    [–] MangoPenguin@lemmy.blahaj.zone 2 points 4 days ago (1 children)

    Interesting, it wouldn't work like rsync where it compares the new files to the old ones and transfers the parts that have changed?

    [–] Ephera@lemmy.ml 1 points 4 days ago (1 children)

    Hmm, good question. I know of one such implementation, which is Delta RPM, which works the way I described it.
    But I'm not sure, if they just designed it to fit into the current architecture, where all their mirrors and such were set up to deal with package files.

    I could imagine that doing it rsync-style would be really terrible for server load, since you can't really cache things at that point...

    Yeah I guess these days the majority of users have fast enough connections that its not worth it. It sucks if you have crappy internet though hah.

    [–] kuberoot@discuss.tchncs.de 4 points 4 days ago

    Shouldn't it be more efficient to download only the changes and patch the existing files?

    As people mentioned, that becomes problematic with a distro like arch. You could easily be jumping 5-6 versions with an update, with some more busy packages and updating less frequently. This means you need to go through the diffs in order, and you need to actually keep those diffs available.

    This actually poses two issues, and the first one is that software usually isn't built for this kind of binary stability - anything compiled/autogenerated might change a lot with a small source change, and even just compressing data files will mess it up. Because of that, a diff/delta might end up not saving much space, and going through multiple of them could end up bigger than just a direct download of the files.

    And the second issue is, mirrors - mirrors need to store and provide a lot of data, and they're not controlled by the distribution. Presumably to save on space, they quickly remove older package versions - and when I say older, I mean potentially less than a week old. In order for diffs/deltas to work, you'd need the mirrors to not only store the full package files they already do (for any new installs), but now also store deltas for N days back, and they'd only be useful to people who update more often than every N days.

    [–] Ricaz@lemmy.dbzer0.com 1 points 4 days ago

    No, that's not how compiling works. And yes, 6GB is wild. If I don't patch in a month, the download might be 2GB and the net will still be smaller.

    I don't think I could get close to my Windows installation even if I installed literally every single package..

    [–] oz1sej@discuss.online 2 points 3 days ago

    "Perfection is reached not when there is nothing more to add, but when there is nothing more to remove."

    • Antoine Saint-Exupery
    load more comments
    view more: next β€Ί