lordievader | Good morning | 07:26 |
---|---|---|
=== denningsrogue682 is now known as denningsrogue68 | ||
maret | hi I've upgraded to 5.12 kernel and I would like to downgrade to 5.11 which I had previously. I've seens multiple approaches, not sure which one is preffered | 08:00 |
maret | this is output of sudo dpkg --list | egrep -i --color 'linux-image|linux-headers' https://paste.debian.net/1197949/ | 08:01 |
maret | hi I've upgraded to 5.12 kernel and I would like to downgrade to 5.11 which I had previously. I've seens multiple approaches, not sure which one is preffered, this is output of sudo dpkg --list | egrep -i --color 'linux-image|linux-headers' https://paste.debian.net/1197949/ | 08:26 |
Walex | maret: for kernels there is no "upgrading" or "downgrading", you can have multiple versions installed at the same time. | 08:32 |
Walex | maret: what you can "upgrade" or "downgrade" are the kernel metapackages, which exist just to pull in the "latest", but you can install explicitly any others. | 08:34 |
maret | Walex: ou ofc , so can I switch on ubuntu server without external monitor? | 08:54 |
maret | AFAIK I should change GRUB_DEFAULT=0 to GRUB_DEFAULT="gnulinux-5.11.0-051100-generic-advanced-88781ebc-4b9d-43cc-908f-411c03f7e814" given this list of options https://paste.debian.net/1197957/ | 08:59 |
Walex | maret: you can change the default kernel to boot to an explicit version or to a number which is the position in the list of bootable kernels. That is a different issue from upgrading/downgrading kernels | 09:08 |
maret | yeah thats what I wanna do | 09:08 |
Walex | maret: note though | 09:11 |
Walex | maret: note though that 'GRUB_DEFAULT' should be the name of the 'menuentry', not of a kernel. | 09:11 |
Walex | maret: so in your case "Ubuntu, with Linux 5.11.0-051100-generic" | 09:12 |
maret | Walex: thanks I was following this article https://meetrix.io/blog/aws/changing-default-ubuntu-kernel.html | 09:41 |
maret | but you are saying i should chage GRUB_DEFAULT=0 toGRUB_DEFAULT="Ubuntu, with Linux 5.11.0-051100-generic" | 09:42 |
maret | btw I have ubuntu-server | 09:42 |
maret | seems like according to that i should have GRUB_DEFAULT="gnulinux-advanced-88781ebc-4b9d-43cc-908f-411c03f7e814>gnulinux-5.11.0-051100-generic-advanced-88781ebc-4b9d-43cc-908f-411c03f7e814" | 09:46 |
Walex | maret: https://www.gnu.org/software/grub/manual/grub/grub.html search for "GRUB_DEFAULT" | 09:47 |
Walex | maret: if you want to use the "id" that is "recommended" by the manual, but it is "too stable" | 09:49 |
maret | what do you mean by too stable and so GRUB_DEFAULT="gnulinux-advanced-88781ebc-4b9d-43cc-908f-411c03f7e814>gnulinux-5.11.0-051100-generic-advanced-88781ebc-4b9d-43cc-908f-411c03f7e814" should work right? | 09:54 |
Walex | maret: minor kernel release upgrades will change the "id". | 09:55 |
Walex | maret: but you are already using self-supported kernels, so you know what you are doing of course :-) | 09:57 |
maret | Walex: hh not that much :) just want to be safe I am not planning to update kernel after this | 10:29 |
maret | ok so I am going to change the id to GRUB_DEFAULT="gnulinux-advanced-88781ebc-4b9d-43cc-908f-411c03f7e814>gnulinux-5.11.0-051100-generic-advanced-88781ebc-4b9d-43cc-908f-411c03f7e814" and reboot | 10:30 |
=== denningsrogue683 is now known as denningsrogue68 | ||
jo-erlend | I've been gone so long, I've forgotten a lot of things and I really have to read up. Should I bother spending time on iptables, or should I just go straight to nftables? My impression is that it's where things are moving, but with Linux you never know. :) | 11:35 |
=== Walex is now known as loser_walex | ||
teward | jo-erlend: nftables is probably where it'll be going, but not everything uses it so i still keep my iptables knowledge around :P | 13:23 |
teward | jo-erlend: but you should probably consider that unless you're going to be editing the firewalls directly yourself, you probably will find most people are using `ufw` unless they need a ton of expert level stuff | 13:58 |
=== cwaydt8 is now known as cwaydt | ||
=== cpaelzer_ is now known as cpaelzer | ||
=== loser_walex is now known as Walex | ||
=== lotuspsychje_ is now known as lotuspsychje | ||
hallyn | serge@sl ~$ dpkg -S /usr/sbin/dhclient | 17:16 |
hallyn | dpkg-query: no path found matching pattern /usr/sbin/dhclient | 17:16 |
hallyn | this gets me every time | 17:16 |
hallyn | i guess isc-dhcp-client works | 17:18 |
sarnold | hallyn: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=134758 :( :( :( | 17:41 |
ubot3 | Debian bug 134758 in dpkg "dpkg-query: Make -S handle unowned symlinks resolving to owned pathnames" [Wishlist, Open] | 17:41 |
hallyn | sarnold: yeah i just figured that out a few mintues ago :) thanks :) | 17:42 |
hallyn | i hadn't realized there was a bug for it. i don't see how that's fixable, actually. | 17:42 |
hallyn | i mean, apart from hardcoding the known symlinks i guess | 17:42 |
sarnold | hallyn: me neither, which is probably why it's been open for almost twenty years | 17:42 |
sarnold | but with usrmerge it's a lot more annoying now than it used to be | 17:43 |
hallyn | for a few minutes i was convicned it was being installed as part of initial debootstrap and not tracked by a package. which woudl be scary in terms of updates :) | 17:43 |
sarnold | hah, that would be the worse outcome indeed :) | 17:45 |
xibalba | im confused about something basic. when i run dpkg -l | grep -i maria, i see mariadb-client-10.1, but when i do apt remove mariadb-client-10.1 it tells me " 'mariadb-client-10.1' is not installed, so not removed" | 19:17 |
mybalzitch | what about just mariadb-client | 19:19 |
xibalba | ah i didn't think about that | 19:20 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!