1 |
depends: |
2 |
|
3 |
I have been caught with a non-bootable system a few times and its much |
4 |
easier to start from an existing config and go from there (After |
5 |
numerous disasters, I wont use genkernel - even if its supposedly ok |
6 |
these days) |
7 |
|
8 |
A (very) few in-tree stuff still seems to want a kernel |
9 |
(vmware-modules?) - not sure what but these days I always keep the last |
10 |
two around as Ive been caught in the past. |
11 |
|
12 |
I also do an occasional ext package - sometimes they want kernel source |
13 |
code. |
14 |
|
15 |
So yes, on a basic, user system you dont need it. But do something out |
16 |
of the ordinary and its quite handy to keep the source code around... |
17 |
|
18 |
YMMV |
19 |
BillK |
20 |
|
21 |
|
22 |
|
23 |
|
24 |
On Fri, 2007-04-27 at 12:12 +0200, Hemmann, Volker Armin wrote: |
25 |
> On Freitag, 27. April 2007, W.Kenworthy wrote: |
26 |
> |
27 |
> > |
28 |
> > rm -rf /usr/src/linux* - dangerous, lokk in there first and only remove |
29 |
> > what you are not using (i.e., leave your current kernel, plus one other |
30 |
> > "good" version as a backup - the number of times Ive had to roll |
31 |
> > back ... :) |
32 |
> |
33 |
> emm, no. Not dangerous at all. After you installed your kernel and the 3rd |
34 |
> party modules, you can safely remove the source-dir. There is nothing in it |
35 |
> that is needed anymore. And you don't keep old 'backup sources'. Backup |
36 |
> kernels in /boot are good enough... |
37 |
-- |
38 |
William Kenworthy <billk@×××××××××.au> |
39 |
Home! |
40 |
-- |
41 |
gentoo-user@g.o mailing list |