| 1 |
On Thu, 17 Jan 2019 18:51:20 -0500, Rich Freeman wrote: |
| 2 |
|
| 3 |
> Basically grub2 is a completely inert package. The stuff in /usr/bin |
| 4 |
> and so on doesn't do anything unless you explicitly run it. The |
| 5 |
> bootloader reads its config file and does what it says, just like the |
| 6 |
> old one. The bootloader won't even be there unless you explicitly |
| 7 |
> install it, just as with the old grub. |
| 8 |
> |
| 9 |
> The one issue you're going to have is finding documentation on the |
| 10 |
> config file. There is a TON of docs on running mkconfig, and very |
| 11 |
> little on rolling your own, but it definitely can be done. |
| 12 |
|
| 13 |
You can also replace the generator scripts in /etc/grub with your own, |
| 14 |
which is what I did. They are just simple shell scripts that look at the |
| 15 |
contents of /boot and generate menu entries. The supplied scripts have to |
| 16 |
cover all use cases, which is where much of the bloat comes from, but |
| 17 |
scripts for a setup controlled by you can be very simple. |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
Neil Bothwick |
| 22 |
|
| 23 |
The cow is nothing but a machine which makes grass fit for us people to |
| 24 |
eat. |
Archives