On Fri, Apr 23, 1999 at 06:19:05AM -0400, Aaron M. Stromas wrote: > i ran dpkg --purge kernel-source-2.0.34 and it looked it did. > > mortirolo:# dpkg --purge kernel-source-2.0.34 > (Reading database ... 28636 files and directories currently installed.) > Removing kernel-source-2.0.34 ... > Purging configuration files for kernel-source-2.0.34 ... > > i was happy. later i looked in /usr/src and here they were: > > mortirolo:# ls -l /usr/src/ > total 2 > drwxr-xr-x 6 root root 1024 Apr 16 00:12 kernel-source-2.0.34 > lrwxrwxrwx 1 root root 21 Feb 11 06:17 linux -> > kernel-source-2.0.34/ > lrwxrwxrwx 1 root root 20 Feb 11 05:37 linux-2.0.34 -> > kernel-source-2.0.34 > drwxr-sr-x 2 root root 1024 Feb 25 05:05 modules > > mortirolo:# ls /lib/modules/ > 2.0.34 2.0.36 > > mortirolo:# dpkg -S /usr/src/kernel-source-2.0.34 > dpkg: /usr/src/kernel-source-2.0.34 not found. > > dpkg removed all the traces of the kernel=source-2.0.34 from its database, so > should i just remove the vestiges of the 2.0.34 manually? btw, the only > modules.dep is in /lib/modules/2.0.36. any other reasons why dpkg tries to
The /lib/modules/2.0.34 directory is not created by installation of kernel-source-2.0.34, but by installation of the modules, so dpkg is unaware of it. If you have removed 2.0.34 from your system, it is safe to remove /lib/modules/2.0.34 as well as any other traces that dpkg could not handle. Bob -- Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen
