-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kern_path cannot be changed #1
Comments
yes, i still need to think about handling foreign roots a little more overall |
i think the main problem really comes down to that with such system it's not enough to be able to change where /lib/modules is - for example the compiler itself is a concern, one is expected to build the kernel modules with roughly the same compiler as the target system is using, and also the source code for the modules will be present on the target system, so in general chrooting may be a good idea anyway - but i'll think about it some more |
i can think of a couple more reasons why managing foreign roots without chroot is likely unfeasible:
that said, if you can think of ways to address these issues in a reasonable way, i'm open to implementing this |
This precludes
ckms
from being used in environments with multiple roots (i.e. having two OSes on separate partitions or btrfs subvols etc) and managing kernel modules withoutchroot
.Also,
do_depmod
uses/lib/modules
itself instead ofkern_path
which may be an oversight. (depmod
itself supports this sort of thing with-b
.)The text was updated successfully, but these errors were encountered: