On 9/26/25 3:21 PM, home user via users wrote:

On 9/26/2025 3:06 PM, Samuel Sieb wrote:
On 9/26/25 10:35 AM, home user via users wrote:

On 9/25/2025 10:59 PM, Tim wrote:
[snip]

Not for planning the install, but for my education and understanding:
In the context of your last sentence, what file(s) are you considering
to be the "kernel", and where (path) are they, given that you consider
initramfs* to not be a part of the "kernel"?
[snip]

The kernel is essentially the core of programming that does the work in
that OS.  Which is the vmlinux file, these days.  The initramfs
(initial RAM file system, it's drivers, tools, and scripts) is extra
things used by the kernel.  And there's even more *things* that are
files in the rest of the directory tree.  You can take a lot of those
things out of the kernel bundle of doo-dahs, and still have a working
kernel.  Of course it will have less in-built features.  Tools can be
in the kernel, or they can be files somewhere in the rest of the
directory tree.  The same can be said for drivers and handlers.
[snip]
So when you (and Samuel, and others?) use the word "kernel", you're referring to the /boot/vmlinuz*?  The term brought to my mind config* + initramfs* + System.map + vmlinuz* + other things in sub- directories of /boot.

It's a bit ambiguous.  The actual bootable kernel is the vmlinuz file, but then the initramfs contains a lot of kernel modules which are really part of the kernel as well.  But what is contained in the initramfs is decided by dracut and that's where the size issue came from.  So it wasn't actually that the kernel was getting bigger, it was that dracut included a whole bunch of extra things that weren't in there before.

Thank-you, Samuel.
That to me almost sounds like dracut is something in installation that constructs initramfs.  Now I suppose someone will tell me I got it wrong.

That's exactly what it is. It's the program that generates the initramfs. It's normally run during kernel installations, but you can also run it manually if you need to update or change what is included.

--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to