1 |
fre 2010-04-30 klockan 18:24 +0200 skrev Enrico Weigelt: |
2 |
> * Daniel Pielmeier <billie@g.o> schrieb: |
3 |
> |
4 |
> > What about searching the complete file system but using an exclude file where |
5 |
> > you can put directories and files which should not be searched. It is tedious to |
6 |
> > tell every path on the command-line. Also for instance if you specify /lib it |
7 |
> > will also search under /lib/modules and I am sure you do not consider all |
8 |
> > contents there as unneeded. |
9 |
> |
10 |
> hmm, perhaps there's some way to assign these files to some package ? |
11 |
> |
12 |
|
13 |
Eh, no and it should not be since files in that directory is kernel |
14 |
modules, and most of the files there is created by "cd /usr/src/linux && |
15 |
make" or genkernel or something alike and it is supposed to be that way. |
16 |
Looking at the contents of that directory is pretty easy to see if a |
17 |
directory there should be left alone or removed (as there is just one |
18 |
directory per kernel. not any longer running a kernel anymore? remove |
19 |
the corresponding dir). |
20 |
It is better to have the script not tuch that directory at all or at |
21 |
most point out "the directory contains directories for more kernels then |
22 |
the currently running (i.e. there is more then one dir) and it is |
23 |
totally THIS big. You may want to take a look if you have files from |
24 |
older kernels that you do not longer need." |
25 |
That would leave up to the user to figure out what kernel modules to |
26 |
keep and what kernel to pount. Or you suggest autocleaning of /boot |
27 |
and /usr/src/linux-* as well? Dangerous! |