On 2020-05-28 at 21:22, Michael Morgan wrote: > Dear friends, > > Here are files under my /boot directory: > > # ls -l > -rw-r--r-- 1 root root 186716 Nov 11 2019 config-4.9.0-11-amd64 > -rw-r--r-- 1 root root 186696 Jan 20 12:38 config-4.9.0-12-amd64 > drwxr-xr-x 5 root root 4096 May 28 20:14 grub > -rw-r--r-- 1 root root 18158152 May 1 01:18 initrd.img-4.9.0-11-amd64 > -rw-r--r-- 1 root root 18818504 May 28 20:14 initrd.img-4.9.0-12-amd64 > -rw-r--r-- 1 root root 3204823 Nov 11 2019 System.map-4.9.0-11-amd64 > -rw-r--r-- 1 root root 3206712 Jan 20 12:38 System.map-4.9.0-12-amd64 > -rw-r--r-- 1 root root 4249376 Nov 11 2019 vmlinuz-4.9.0-11-amd64 > -rw-r--r-- 1 root root 4261664 Jan 20 12:38 vmlinuz-4.9.0-12-amd64 > > # hostnamectl > . > Operating System: Debian GNU/Linux 9 (stretch) > Kernel: Linux 4.9.0-12-amd64 > Architecture: x86-64
I'd prefer to check the result of $ uname -r first, because I don't know hostnamectl and so I don't entirely trust it, but it's probably fine (although it seems a bit weird that something with "hostname" as its primary name component wouldn't report the actual hostname of the computer). > Is it fine I delete all 4.9.0-11 files under /boot? What does the following command output? $ dpkg -l "*4.9.0*" | grep ii If it lists any packages which match 4.9.0-11, then no, you should not delete these files. If you want them gone, you should remove those packages instead - but be careful that nothing depends on them. That said, in my experience the system usually automatically retains the current kernel and the previous kernel, but flags any previous ones for autoremoval (via e.g. 'apt-get autoremove'). As long as you have only those two kernels, I wouldn't bother removing the old one. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
