Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Now the /boot/grub/grub.cfg file has three instances of this line:
linux /vmlinuz-3.16.0-4-amd64 root=UUID=5ce5(elided) ro threadirqs quiet
...and no other linux /vmlinuz(whatever) line. It gets down to one of those three.
However, when I boot, the threadirqs option is never there. I can add it manually at boot time and later confirm that the kernel has indeed loaded with the option enabled, but I want to have that added correctly. How do I do that???
2)
How do I get to land a punch to the stomach of the people who turned grub into a big pile of feces? Does anyone here know where they hang out? Steve Jobs is dead, but I still have a shot with Bill Gates and the people responsible for grub2, right?
I don't do Debian, soooo ...
1) I would expect them to use update-grub (a Debian/Ubuntu-ism BTW) - you would have to scan the scripts.
2) My recollections is that the Ubuntu (nee Debian) devs drove it initially. Pretty obvious from the verbosity of the scripts.
Banging on about grub vs grub2 is a lost cause - just like systemd. We all liked the classic grub, but it was never going to measure up in the current world of UEFI, gpt ...
depending if you are running on an EFI machine or not. This will prompt you for, and add your args to the systemwide config, instead of having them wiped out.
depending if you are running on an EFI machine or not. This will prompt you for, and add your args to the systemwide config, instead of having them wiped out.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.