Linux

48463 readers

501 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 5 years ago

MODERATORS

[email protected]

Why do I have to re-download kernel packages everytime? (self.linux)

submitted 1 year ago by spez to c/[email protected]

7 comments fedilink hide all child comments

Hey, I am using Fedora Linux 38 with the 6.4.13 kernel. I have had this problem for quite a while now. Everytime I run sudo dnf upgrade and there' an update to the kernel, dnf downloads the kernel and related packages (kernel-modules, kernel-modules-extra etc.) but cites a md5 mismatch and then re-downloads it. This time it works but this whole costs me quite a bit of data. What do you think is causing this? I have cleared the dnf cache multiple times and yet this happens.

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

[–] taladar 13 points 1 year ago (1 children)

The real question is why all but the last download do not have the correct checksum. It makes sense for it to delete downloads that do not pass that check. Have you tried checking for differences between the unsuccessful and successful downloads, e.g. different mirrors, file sizes or similar issues besides the checksum itself?

Maybe run something like Wireshark while you run that command to check for network errors and/or differences in the addresses?

Checking log files would also be an option to see if those contain additional information.

It might also be possible to inspect the different runs of the command via strace or bpftrace to get data like the file size or the checksum if it does not print those.

[–] spez 1 points 1 year ago

I am not that technically knowledgeable but I will try to use a different network next time.