[This may not be the place to ask this question. If I'm not in the right place could someone point me to the correct list? TIA]
I'm wondering about why the rpm kernel install (via dracut) method results in an initramfs but the install targets have an initrd. Is there any technical reason for the difference?
Thanks,
P.
On Wed, Aug 12, 2015 at 08:59:22AM -0400, Prarit Bhargava wrote:
[This may not be the place to ask this question. If I'm not in the right place could someone point me to the correct list? TIA]
I'm wondering about why the rpm kernel install (via dracut) method results in an initramfs but the install targets have an initrd. Is there any technical reason for the difference?
Thanks,
P.
I was usually under the impression that it was at this point just a nomenclature thing. Initrds used to be fs image files that were mounted via loopback block devices while initramfs files are cpio files that are copied into a tmpfs file system. I thought both dracut and kernel install targets used initramfs at this point, but the latter just kept the naming for convienience.
Note, I've always just assumed this, not directly checked, so I may be wrong.
Neil
kernel mailing list kernel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel
On Wed, Aug 12, 2015 at 9:58 AM, Neil Horman nhorman@redhat.com wrote:
I was usually under the impression that it was at this point just a nomenclature thing. Initrds used to be fs image files that were mounted via loopback block devices while initramfs files are cpio files that are copied into a tmpfs file system. I thought both dracut and kernel install targets used initramfs at this point, but the latter just kept the naming for convienience.
Note, I've always just assumed this, not directly checked, so I may be wrong.
Neil
AFAIK this is correct. I don't think anything actually uses initrd anymore but the name has stuck around - to refer to either initrd or initramfs. Even the plymouth initrd image is actually an initramfs (I believe).
Some reading for the interested: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documen... https://www.linux.com/learn/linux-training/92607-the-kernel-newbie-corner-qi...
- Donavan
On 08/12/2015 10:39 AM, Donavan Lance wrote:
On Wed, Aug 12, 2015 at 9:58 AM, Neil Horman nhorman@redhat.com wrote:
I was usually under the impression that it was at this point just a nomenclature thing. Initrds used to be fs image files that were mounted via loopback block devices while initramfs files are cpio files that are copied into a tmpfs file system. I thought both dracut and kernel install targets used initramfs at this point, but the latter just kept the naming for convienience.
Note, I've always just assumed this, not directly checked, so I may be wrong.
Neil
AFAIK this is correct. I don't think anything actually uses initrd anymore but the name has stuck around - to refer to either initrd or initramfs. Even the plymouth initrd image is actually an initramfs (I believe).
Some reading for the interested: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documen... https://www.linux.com/learn/linux-training/92607-the-kernel-newbie-corner-qi...
FWIW -- there are/can be some compression differences from the early microcode stuff. I'll ping the anaconda folks at some point to see about switching the name to initramfs instead of initrd.
P.
- Donavan
kernel mailing list kernel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel
kernel@lists.fedoraproject.org