Bug#676792: closed by Ben Hutchings ( Bug#676792: dm_mod: Unknown symbol scsi_verify_blk_ioctl)
On Sat, 2012-06-09 at 15:13 +0200, Arno Wagner wrote:
> Indeed. I did not notice this. Now I have a new bug for you:
> For some reason,
> apt-get install --reinstall linux-image-2.6.32-5-amd64
> does not write all files in /boot:
> v5:/boot# ll
> total 14M
> drwxr-xr-x 3 root root 4.0K Jun 9 15:09 ./
> drwxr-xr-x 23 root root 4.0K Jun 8 22:31 ../
> -rw-r--r-- 1 root root 1.6M May 6 11:24 System.map-2.6.32-5-amd64
> -rw-r--r-- 1 root root 104K May 6 11:24 config-2.6.32-5-amd64
> drwxr-xr-x 3 root root 4.0K Jun 9 15:09 grub/
> -rw-r--r-- 1 root root 9.6M Jun 9 15:09 initrd.img-2.6.32-5-amd64
> -rw-r--r-- 1 root root 2.4M May 6 11:18 vmlinuz-2.6.32-5-amd64
> You can see that vmlinuz-2.6.32-5-amd64, config-2.6.32-5-amd64
> and System.map-2.6.32-5-amd64 are old, while initrd.img-2.6.32-5-amd64
> has been updated. That strikes me as wrong for --reinstall.
The files installed from a package are always given the same
modified-time as the original files that were copied into the package.
So reinstalling doesn't change the time.
> That also leaves the question of how I can upgrade these files.
> Do a purge and install new?
If it jams, force it. If it breaks, it needed replacing anyway.