You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to create a custom RHEL installer ISO that is based on rhel-8.10-x86_64-boot.iso and uses kikstart for the automatic installation process. I noticed that install.img contains /usr/lib/firmware which takes up a lot of space.
What is the purpose of the /usr/lib/firmware in install.img if ISO installer will be include a linux-firmware RPM package in BaseOS (e.g. linux-firmware-20230824-119.git0e048b06.el8_9.noarch.rpm)?
Note: I installed such an ISO with a recreated install.img without anything in /usr/lib/firmware, and there were no problems during installation and operation on a some virtual machine and a hardware server (HP). I want to be sure that this won't cause any problems in other cases.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm trying to create a custom RHEL installer ISO that is based on rhel-8.10-x86_64-boot.iso and uses kikstart for the automatic installation process. I noticed that install.img contains /usr/lib/firmware which takes up a lot of space.
What is the purpose of the /usr/lib/firmware in install.img if ISO installer will be include a linux-firmware RPM package in BaseOS (e.g. linux-firmware-20230824-119.git0e048b06.el8_9.noarch.rpm)?
Note: I installed such an ISO with a recreated install.img without anything in /usr/lib/firmware, and there were no problems during installation and operation on a some virtual machine and a hardware server (HP). I want to be sure that this won't cause any problems in other cases.
Beta Was this translation helpful? Give feedback.
All reactions