| 1 |
On 04/12/09 14:14, Dale wrote: |
| 2 |
>Mark Knecht wrote: |
| 3 |
>> A problem I often have after a big update is emerge -p --depclean |
| 4 |
>> tells me it is going to remove my running kernel. |
| 5 |
>> |
| 6 |
>> sys-kernel/gentoo-sources |
| 7 |
>> selected: 2.6.26-r4 |
| 8 |
>> protected: none |
| 9 |
>> omitted: 2.6.25-r8 2.6.27-r10 |
| 10 |
>> |
| 11 |
>> dragonfly ~ # uname -a |
| 12 |
>> Linux dragonfly 2.6.26-gentoo-r4 #1 SMP PREEMPT Tue Dec 9 11:08:39 PST |
| 13 |
>> 2008 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux |
| 14 |
>> dragonfly ~ # |
| 15 |
>> |
| 16 |
>> My general reaction is to remove packages by hand at this point but |
| 17 |
>> today I have 30-40 and would like to protect this kernel source. Is |
| 18 |
>> there a generaic way to *always* protect the kernel that is currently |
| 19 |
>> running? |
| 20 |
|
| 21 |
I would like to protect the current kernel as well, will statement in make.conf works? |
| 22 |
CONFIG_PROTECT="/usr/src/linux/*" |
| 23 |
|
| 24 |
I've not test it yet. |
| 25 |
|
| 26 |
-- |
| 27 |
Joseph |
Archives