1 |
On 15/02/18 02:57, Daniel Frey wrote: |
2 |
> On 02/14/18 09:29, Nikos Chantziaras wrote: |
3 |
>> On 14/02/18 04:38, Daniel Frey wrote: |
4 |
>>> On 02/12/18 19:39, Ian Zimmerman wrote: |
5 |
>>>> On 2018-02-12 19:24, Daniel Frey wrote: |
6 |
>>>> |
7 |
>>>>> I've read online that there should be vulnerability info (Meltdown, |
8 |
>>>>> Spectre) in /sys under /sys/devices/system/cpu/vulnerabilities but this |
9 |
>>>>> doesn't exist on my PC. |
10 |
>>>>> [...] |
11 |
>>>> |
12 |
>>>> See the other threads: you need at least 4.9.79 for the /sys bits. |
13 |
>>>> [...] |
14 |
>>> |
15 |
>>> I'm surprised I missed those threads, I read all messages on here. |
16 |
>>> According to the thread I found it's actually starts on 4.9.77, I'm just |
17 |
>>> on the latest stable (.76). |
18 |
>> |
19 |
>> During "special emergencies" like this one, it would be a good idea to |
20 |
>> use the latest 4.9.x, regardless of whether portage marked it "stable" |
21 |
>> or not. At least for a while and until the situation has settled down |
22 |
>> again. |
23 |
>> |
24 |
>> |
25 |
> |
26 |
> Nah, I like stability over everything else. I recall lots of pain and |
27 |
> instability in January when everyone rushed to patch the flaws (both |
28 |
> Windows and linux.) |
29 |
> |
30 |
> These are my personal computers, not a work environment. |
31 |
|
32 |
Personal preference of course, but I prefer to risk some instability |
33 |
compared to risking having a bitcoin miner infesting my PC or some |
34 |
botnet worm. |
35 |
|
36 |
That's just me though. |