| 1 |
Mark Knecht wrote: |
| 2 |
> A problem I often have after a big update is emerge -p --depclean |
| 3 |
> tells me it is going to remove my running kernel. |
| 4 |
> |
| 5 |
> sys-kernel/gentoo-sources |
| 6 |
> selected: 2.6.26-r4 |
| 7 |
> protected: none |
| 8 |
> omitted: 2.6.25-r8 2.6.27-r10 |
| 9 |
> |
| 10 |
> dragonfly ~ # uname -a |
| 11 |
> Linux dragonfly 2.6.26-gentoo-r4 #1 SMP PREEMPT Tue Dec 9 11:08:39 PST |
| 12 |
> 2008 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux |
| 13 |
> dragonfly ~ # |
| 14 |
> |
| 15 |
> My general reaction is to remove packages by hand at this point but |
| 16 |
> today I have 30-40 and would like to protect this kernel source. Is |
| 17 |
> there a generaic way to *always* protect the kernel that is currently |
| 18 |
> running? |
| 19 |
> |
| 20 |
> Thanks, |
| 21 |
> Mark |
| 22 |
> |
| 23 |
> |
| 24 |
> |
| 25 |
|
| 26 |
Just emerge it with the exact version. emerge |
| 27 |
=sys-kernel/gentoo-sources-2.6.26-r4 should work. There is a option to |
| 28 |
add it to world without actually "compiling" it again but I can't recall |
| 29 |
what it is. |
| 30 |
|
| 31 |
Feel free to correct any typo's. |
| 32 |
|
| 33 |
Dale |
| 34 |
|
| 35 |
:-) :-) |
Archives