Skip to content

Conversation

swills
Copy link
Contributor

@swills swills commented Aug 23, 2019

Given how critical space is in mfsroot, it seems to make sense to avoid
having a copy of /boot in the mfsroot since it's in the ISO anyway and
that's the one that's used for boot, not the copy in mfsroot.

Given how critical space is in mfsroot, it seems to make sense to avoid
having a copy of /boot in the mfsroot since it's in the ISO anyway and
that's the one that's used for boot, not the copy in mfsroot.
@bapt
Copy link
Member

bapt commented Aug 26, 2019

While I do agree with the approach, I disagree with the fact of removing entirely the modules. one can have a kld_list in the rc.conf so I do think we should keep the modules and nuke the kernel itself and all other files.

@swills
Copy link
Contributor Author

swills commented Aug 29, 2019

I agree. Perhaps it would be good to have a separate flag for this?

I've also run into cases where I need to customize the boot, such as creating /boot.config or modifying /boot/device.hints. Perhaps a separate root for the iso contents vs the mfsroot would make sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants