On Thu, Dec 08, 2022 at 02:17:22PM -0600, Chris Adams wrote: > Once upon a time, Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> said: > > This is the direction Daniel was thinking down. I'm waiting for someone > > with more expertise to reply, but I suspect the reply is going to be > > along the lines of "yes, we *can* do that, but it's somewhat tricky > > work that involves thinking about lots of paths that aren't obvious, > > and somebody would need to dedicate their time to working on that". > > One other thing that I noticed a while back that takes up a chunk of > space is the kernel... it's included inside install.img (in two places > even, although I assume it's hardlinked?), even though it has to have > already been loaded before install.img can be read. What two places? On rawhide we have one on the iso under /images/pxeboot/ and another inside the install.img under /usr/lib/modules... I think I tried removing the kernel from the install.img at one point, but it ended up being required for FIPS (see https://github.com/weldr/lorax/issues/1021). And when there were 2 kernels on the iso they were hardlinked (one under pxeboot and the other under isolinux). Brian -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
