| lotuspsychj3 | good morning | 03:22 |
|---|---|---|
| JanC | ravage: you should not tell people to run commands like update-grub that can have side-effects just to get something that happens to be in their output | 12:15 |
| JanC | especially as in the worst possible case, a failed update-grub could make a system unbootable :) | 12:16 |
| lotuspsychj3 | the user didnt edit their grub? | 12:17 |
| JanC | it wa to list installed kernels on the system | 12:17 |
| JanC | was* | 12:17 |
| lotuspsychj3 | ah | 12:18 |
| lotuspsychj3 | dpkg --list | grep linux-image | 12:20 |
| pragmaticenigma | that would be in accurate, as that lists the kernel packages on the machine, but wouldn't necessarily list the configured kernels for booting | 12:27 |
| pragmaticenigma | *inaccurate | 12:27 |
| === JanC is now known as Guest6880 | ||
| === JanC_ is now known as JanC | ||
| lotuspsychj3 | so whats the best command without update-grub | 12:28 |
| pragmaticenigma | update-grub is certainly a bit unorthodox way to get the list, but I don't see much issue in it. To me, at worst it would complete an incomplete setup from a interrupted update by apt. | 12:31 |
| lotuspsychj3 | its a reload mechanism that could be tricky 'after' grub edits | 12:32 |
| pragmaticenigma | indeed it is, one could `ls -l /etc/initrd*` but there are symlinks that get returned with that | 12:36 |
| pragmaticenigma | oops | 12:36 |
| pragmaticenigma | too tird | 12:36 |
| pragmaticenigma | indeed it is, one could `ls -l /boot/initrd*` but there are symlinks that get returned with that | 12:36 |
| pragmaticenigma | or swap initrd with config | 12:36 |
| JanC | pragmaticenigma: worst case it writes an empty or incorrect grub.cfg ... | 12:38 |
| JanC | it's *unlikely* but not impossible :) | 12:38 |
| pragmaticenigma | a bit too doom and gloom... if that were to happen, I think the user has bigger problems | 12:39 |
| JanC | but it's not needed, so why take the risk? | 12:39 |
| JanC | when you can use ls or the package manager | 12:39 |
| lotuspsychj3 | sudo apt update && sudo apt full-upgrade is also risky :p | 12:40 |
| JanC | that's not what I mean, obviously | 12:41 |
| pragmaticenigma | they both have system wide impact. I see no differnce between running either one | 12:43 |
| JanC | I would never suggest you run either one as part of *diagnosing* a problem, that's the whole point | 12:45 |
| pragmaticenigma | you haven't suggested an alternative. so I don't understand why you're getting upset when someone trying to help does something you don't agree with, but fail to offer a safer alternative. | 12:47 |
| JanC | the alternative was already given | 12:47 |
| pragmaticenigma | I'm going to use your playbook. "that's not what I meant" | 12:49 |
| pragmaticenigma | you didn't immediately offer something when you made your statement. someone else suggested something | 12:49 |
| pragmaticenigma | I was busy trying to verify an alternative, which was to `cat /boot/grub/menu.lst` but that has long been outdated | 12:50 |
| JanC | an alternative was given in #ubuntu before the update-grub statement was made, so I didn't need to give one... | 12:51 |
| pragmaticenigma | wow, just wow... | 12:52 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!