| 1 |
On 161025-19:06+0200, Miroslav Rovis wrote: |
| 2 |
> On 161025-17:24+0200, Miroslav Rovis wrote: |
| 3 |
... |
| 4 |
> > > On 10/25/16 10:10 AM, Francisco Blas Izquierdo Riera (klondike) wrote: |
| 5 |
> > > > El 25/10/16 a las 12:56, Miroslav Rovis escribió: |
| 6 |
... |
| 7 |
> |
| 8 |
> And the need to move forware I, of course, I understand. But 4.4.8-r1 |
| 9 |
> has the mad COW, and the 4.7.10 will probably have that bug carried |
| 10 |
> over... |
| 11 |
> |
| 12 |
> I spent almost two days testing for that bug, and should be off, and |
| 13 |
> will be off with other business... But I too use my machines daily, and |
| 14 |
> I don't have a reliable system now... |
| 15 |
... |
| 16 |
|
| 17 |
The 4.4.8-r1 can be patched just like any other kernel! |
| 18 |
|
| 19 |
Developer Fernando Rodriguez has been kind to tollerate my obstinate |
| 20 |
misunderstanding of his tip, and taught me how to do it: |
| 21 |
|
| 22 |
[gentoo-user] Dirty COW, 4.4.8-hardened-r1 how to fix? |
| 23 |
https://archives.gentoo.org/gentoo-user/message/be9665d005ad02d1826610571d0c7d5d |
| 24 |
|
| 25 |
So it is likely just, now after patching it, I only need to: |
| 26 |
|
| 27 |
# make && make install && make modules_install & |
| 28 |
|
| 29 |
Regards! |
| 30 |
-- |
| 31 |
Miroslav Rovis |
| 32 |
Zagreb, Croatia |
| 33 |
http://www.CroatiaFidelis.hr |
Archives