=== cpaelzer__ is now known as cpaelzer | ||
=== ricotz_ is now known as ricotz | ||
zx2c4 | 18:12:14 <apw> zx2c4, should be finished tommorrow if i haven't pooched anything | 19:26 |
---|---|---|
zx2c4 | 18:12:31 <zx2c4> apw: oh cool | 19:26 |
zx2c4 | apw: did this materialize? | 19:26 |
apw | I ended up sick, it is the top item on my list for when I get to my laptop | 20:03 |
zx2c4 | Aw sorry to hear | 20:24 |
apw | i am a migrain sufferer, so its not so uncommon | 20:55 |
aberrant | hi all. I built a custom kernel (version 5.3.10+). Just went to do an apt-upgrade and I saw this: vmlinuz -> boot/vmlinuz-5.3.0-29-generic. Should I relink it to /boot/vmlinuz-5.3.10+ ? | 21:53 |
aberrant | not quite sure what happened here. I thought that since my kernel's version was later than the one from apt, it would be preserved? | 21:54 |
apw | aberrant, depending on which bootloader you are using i don't think those links are used very often | 22:01 |
aberrant | apw - grub, I think | 22:08 |
aberrant | apw - how do I tell what kernel will be booted? | 22:09 |
apw | pretty sure it will not be using those links | 22:09 |
apw | when update-grub runs it shows the menu entries in order | 22:09 |
apw | top to bottom iirc | 22:09 |
apw | failing that /boot/grub/grub.cfg and search for menuentry | 22:10 |
tomreyn | zx2c4: just out of interest: had you considered to also idle in / contribute to #debian-kernel (on oftc)? | 22:12 |
zx2c4 | tomreyn: sure, will join | 22:13 |
aberrant | thanks. | 22:13 |
aberrant | grub-update shows 5.3.10+ first, so there we go :) | 22:18 |
=== ben_r_ is now known as ben_r |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!