| 1 |
I have multiple (would you believe 2?) kernels in /boot. |
| 2 |
|
| 3 |
[x8940][waltdnes][~] ll /boot/vm* |
| 4 |
-rwxr-xr-x 1 root root 7046848 Jun 12 23:46 /boot/vmlinuz-experimental |
| 5 |
-rwxr-xr-x 1 root root 6986624 Jun 12 16:55 /boot/vmlinuz-production |
| 6 |
|
| 7 |
The grub kernel listing at bootup is |
| 8 |
|
| 9 |
- production kernel |
| 10 |
- production kernel recovery mode |
| 11 |
- experimental kernel |
| 12 |
- experimental kernel recovery mode |
| 13 |
|
| 14 |
The default is the first entry, i.e. "GRUB_DEFAULT=0" in |
| 15 |
/etc/default/grub. I prefer going with "experimental". If I screw up |
| 16 |
the config to the point where it can't boot, then I'll manually override |
| 17 |
to "production". The simple way of getting the third entry as default |
| 18 |
is "GRUB_DEFAULT=2" (remember to count from zero). |
| 19 |
|
| 20 |
This works for now. But what happens if/when I add more kernels for |
| 21 |
whatever reason? Let me rephrase the question more generally... given a |
| 22 |
kernel "/boot/vmlinuz-fubar" how and where do I specify it by name as |
| 23 |
the default boot kernel? |
| 24 |
|
| 25 |
-- |
| 26 |
Walter Dnes <waltdnes@××××××××.org> |
| 27 |
I don't run "desktop environments"; I run useful applications |
Archives