[09:31] <ygk_12345> how to disable unattended security upgrades  through autoinstall for ubuntu 20.04 ?
[20:56] <andybiker> Is there any documentation on how to change or update your mirrors on a terminal? I didn't install the graphic interface on my server and my xenial mirrors are not suggesting any upgrades
[20:56] <andybiker> I am using version 16
[21:00] <RoyK> andybiker: /etc/apt/sources.list
[21:03] <andybiker> are the xenial sources still available?
[21:04] <andybiker> they don't seem to be
[21:05] <TJ-> andybiker: see all the xenial* at http://archive.ubuntu.com/ubuntu/dists/
[21:11] <andybiker> my pc doesn't resolve archive.ubuntu.com. what are the alternatives?
[21:13] <andybiker> they need to be 32 bit as well
[21:14] <RoyK> resolves from here
[21:15] <RoyK> check dns settings
[22:09] <compdoc> mine resolves it, but ipv6
[22:13] <andybiker> Thanks RoyK, I didn't have a network device other than the loop interface and it has taken me an hour to find its name!
[22:13] <andybiker> I was hoping dist-upgrade would work, but not found
[22:28] <RoyK> amurray: ip l l
[23:08] <faekjarz> Gidday, mates! :D I have a bunch of code (github/gnif/vendor-reset) which i've successfully installed via "dkms install .". Now, i'm worried that this kernel module might "vanish" on reboot, after an "apt upgrade" kernel update. I know there are dkms hooks - so, where would i put this source code, in order to be build and included in the newly generated initrd automatically? (20.04 LTS, Linux 5.4.0)
[23:13] <TJ-> faekjarz: if it is installed via dkms install then the kernel dkms hooks should build that module for new kernel version upgrades
[23:14] <TJ-> faekjarz: adding a module into initialramfs is achieved via listing in /etc/initramfs-tools/modules
[23:17] <faekjarz> TJ-: i've added "vendor-reset" to /etc/modules - lsmod listed it after "update-initramfs -ukall" and reboot. What's this /etc/initramfs-tools... about?
[23:24] <TJ-> faekjarz: you asked "...included in the newly generated initrd automatically?" - that's how
[23:24] <TJ-> faekjarz: /etc/modules doesn't do that
[23:29] <faekjarz> TJ-: your statement contradicts the documentation (comments in /etc/modules) [20.04], as well as my experience: "This file contains the names of kernel modules that should be loaded at boot time, one per line."
[23:29] <TJ-> faekjarz: no, it does not
[23:31] <TJ-> faekjarz: modules in /etc/modules are loaded via systemd's init process in the real root file-system. You asked about the initrd, which is the pre-userspace environment built by update-initramfs, which includes modules listed in /etc/initramfs-tools/modules
[23:33] <faekjarz> all i did was "dkms install .", add a line to /etc/modules, "update-initramfs -ukall", and reboot - the module is loaded, all right (and works as described)     ...sorry, Dunning-Kruger just hit me, LOL ;)
[23:33] <faekjarz> i see, the user-space thing, ok
[23:34] <TJ-> faekjarz: modules in initrd is only necessarily if they're required to find and mount the real root file-system
[23:36] <faekjarz> ok, so where to did "dkms install" copy the source code, in order for it to be considered during the next kernel upgrade?
[23:37] <TJ-> faekjarz: it creates links when dkms add/build/install are called
[23:38] <TJ-> faekjarz: convention is to put kernel module sources in /usr/src/$module-$version/
[23:38] <faekjarz> oh, ok, so somewhere under /lib or /usr is a symlink to /home/random/devel/moduleName/ ?
[23:40] <faekjarz> ls /usr/src/ returned what i was looking for - AMAZING :D
[23:40] <TJ-> faekjarz: see "ls -l /var/lib/dkms/*/*/source"
[23:41] <faekjarz> the plot thickens! <3
[23:43]  * faekjarz trusts TJ- senpai's expertise now and humbly apologises for his fierce inquiry *giggles* (Thanks, mate!)