-
Notifications
You must be signed in to change notification settings - Fork 42
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
An option to disable boot timeout or set timeout time #1594
Comments
* Use workaround by sending esc until we hit grub2-bootloader gh#agama-project/agama/issues/1594 * usb devices tend to boot back the installer
Hi @lkocman AFAIK, there is not such an option yet.
About this,
Let me ping @ancorgs to help us here. |
The "hidden" option you mention is used to specify you want the system (ie. the That's an option, as @dgdavid said, hidden on purpose. We know is a use-case for some people... but that's people with several disks and that know very well how they want to organize them. Going back to the original topic (configuring aspects of the bootloader like the timeout), we need to discuss it. I'm a bit defensive about re-introducing YaST features into Agama. |
* Use workaround by sending esc until we hit grub2-bootloader gh#agama-project/agama/issues/1594 * usb devices tend to boot back the installer
@dgdavid This it's not workaround, setting timeout during installation to 0 is what openqa generally expects. |
So, I miss-understood your first comment 😅
Thanks for the explanation.
I see. But as @ancorgs said it needs some discussion first. |
I agree, we're not blocked any more, but in general I think we should have this feature. |
Hello team
I was just looking where to disable bootloader timeout (quite important for openQA for reboot after install) and well aside from that not being an option, I noticed that it's ver well hidden and I really had to be creative to find it :-)
Aside from this particular openQA case I think generally people want some timeout for power on lan, reboot after outage etc, automatic updates etc ... I could alternatively set a long timeout, in case that there is some value that can be set.
The text was updated successfully, but these errors were encountered: