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

TuneD sets variables in grubenv - arguably risky (may run out of very limited space), and unnecessary? #706

Open
mikebeaton opened this issue Nov 5, 2024 · 1 comment

Comments

@mikebeaton
Copy link

After intialising a TuneD profile which uses [bootloader] it sets up the variables tuned_params and tuned_initrd in both grub.cfg and grubenv.

It seems that there is no need to set these variables in both places, and quite a strong argument against setting them in grubenv - namely, space there is extremely limited, and the values of these variables could validly be very long.

@mikebeaton mikebeaton changed the title TuneD sets variables in grubenv - arguably risk (may run out of very limited space), and unnecessary? TuneD sets variables in grubenv - arguably risky (may run out of very limited space), and unnecessary? Nov 5, 2024
@mikebeaton
Copy link
Author

mikebeaton commented Nov 5, 2024

I saw that @yarda has already kindly responded about this issue here: https://bugzilla.redhat.com/show_bug.cgi?id=2323514#c8

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