=== Montresor is now known as Unit193
[20:04] <LLOL> :(
[20:15] <tomreyn> don't be sad, have a LLOLly!
[20:15] <Eickmeyer> Hahahaha
[20:30] <corrinado[m]> General question: is there a write-up or standardized procedure to fix an install that is holding onto older kernels? I have a US that was installed with a script on top of a fresh Ubuntu 20.04 install. I just noticed it has 7+ kernels in the /boot. I can manually delete the older ones, but wanted a safe method to alter the behavior.
[20:30] <Eickmeyer> corrinado[m]: If you have a fresh Ubuntu install, then the update tool should give you the option when you run updates.
[20:30] <Eickmeyer> Otherwise, you'll have to manually remove them.
[20:37] <corrinado[m]> Interesting. Just to be clear; are you saying that the Update tool from the GUI? Or the standard apt-get CLI method should clear those up? I've been remotely ssh-ing into the box. Maybe that's why I'm seeing this.
[20:43] <Eickmeyer> The update tool from the GUI. apt doesn't remove unless explicitly told. The gui is merely a front-end to apt, for the most part.
[20:43] <Eickmeyer> corrinado[m]: ^
[20:44] <Eickmeyer> ajan: I gave you one week to get your connection issues resolved. If you cannot fix your connection issues, that temporary ban I had on you will become permanent.
[21:21] <corrinado[m]> Appreciate the advice Eickmeyer . I'll go that route!
[22:26] <ajan> What connection issues?
[22:31] <Eickmeyer> ajan: You keep joining/parting due to ping timeout.
[22:33] <ajan> Eickmeyer: I am on a laptop, and it goes to standby/lock whenever I am off the desk. Maybe there is problem with Thunderbird that I use for IRC that does not do disconnect reconnect gracefully, and I have not been aware by that. I saw a ban, but did not see a warning.
[22:34] <Eickmeyer> ajan: We had warned you several times to get it fixed. I understand the situation, but if you've got that going on, I recommend getting some sort of bouncer set-up.
[22:41] <ajan> I am sorry, I have not seen any warning until now. I am a university professor, not a troll. I am on IRC since 1996 and never had issues with such a policy on any channel. Sorry again. Will think of some way to live with this, in the meanwhile I will stop joining the channel if this bothers people.
[22:43] <Eickmeyer> ajan: It's ok, we weren't looking to pick a fight. We do, however, temp-ban people with connection issues for a week so they can get them fixed, but if it's not a connection issue, then if you wish to maintain a presence, I recommend a bouncer or relay that's on an always-connected computer that you can connect to. weechat, quassel, and znc are good examples.
[22:54] <ajan> Eickmeyer: thanks for the suggestion. I would like to know what exactly is the problem to try to address it properly. Is the fact that I am often disconnecting/reconnecting an issue, or the fact that I am disconnected but have not left the channel properly?
[22:56] <Eickmeyer> ajan: It's the frequency of disconnect/reconnect. Generally frowned-upon, but you explained the situation and were responsive. Usually when we ban it's because the person hasn't been responsive.
[22:56] <Eickmeyer> We figure at that point it's a client without a person behind it. :)
[22:58] <ajan> OK, I understand. Will try to do better.
=== cassandra is now known as cass