Skip to content
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

Question: why, for grub2, grub.cfg is tested for "automatically generated" header? #26

Open
cova-fe opened this issue Aug 31, 2021 · 0 comments

Comments

@cova-fe
Copy link

cova-fe commented Aug 31, 2021

Sorry if my question is silly, but I'm a a bit puzzled. I'm using genkernel to create and install my kernels. I tried to use eclean-kernel to remove old kernels and I noticed that it does not find any kernel referenced in grub.cfg (believe me, they are :) ).
It seems that is due to the line 30 of grub2.py, where the file is tested for the header "...DO NOT EDIT THIS FILE...". Is this the intended behavior? I'm not sure why this is done, as basically this could lead eclean-kernel to remove all kernel files even without -d parameter, that does not seems to be really safe.

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

No branches or pull requests

1 participant