Pjotr Prins writes:
> On Tue, Jan 09, 2018 at 09:45:33PM -0800, Chris Marusich wrote:
>> It's a little last minute, but I'm thinking of going. It'd be really
>> great to meet people in person and also to be able to go to FOSDEM!
>> Would there still be enough room for me on the Guix/Guile day if
guix offload test works.
however when I try to actually build on the machine, some part fails.
any advice on what could be wrong?
guix build --no-grafts --verbosity=10 icecat
[snip, too long]
| | building of
`/gnu/store/7725ig6g69ah748xkgyxb3wgsdmw6kai-fcitx-4.2.8.6.drv': waitee
`building
Christopher Lemmer Webber writes:
> Katherine Cox-Buday writes:
>
>> Tobias Geerinckx-Rice writes:
>>
>>
>>> I think the real and thornier question for GuixSD
>>> is: if the recent CPU vulnerabilities require a
>>> microcode update to fully mitigate, then how do we
>>> square not recommending pr
On Wed, Jan 10, 2018 at 10:13:51AM +0100, Ludovic Courtès wrote:
> Leo Famulari skribis:
>
> > After rebooting, I found that my user's numerical ID had changed, so I
> > no longer owned any of my files. Not being able to read ~/.ssh means you
> > can't log in remotely.
> >
> > Additionally, sever
On Wed, Jan 10, 2018 at 11:46:46AM +0100, Tobias Platen wrote:
> The Talos II is a free-er system. And its processor (the POWER9) does not
> seem to be affected by Meltdown/Sprectre [1].
>
> [1] https://mobile.twitter.com/RaptorCompSys?p=s
The Talos teams says that their POWER8 and POWER9 systems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Alex,
The libreboot mailing list is down, so you can't CC it at the moment.
I was notified about this thread.
There's not much we can do from the Libreboot side, but there are
mitigations on kernel side... since it's exploitable from javascript
I don't believe that making a microcode update available makes the situation
worse. An earlier version is a non-free component of the system anyway.
I believe, that it might well worth to provide the possibility to update it.
I think it would be beneficial, if we got a singned blob for that,
becau
Alex Vong transcribed 1.7K bytes:
> Mark H Weaver writes:
>
> > Mark H Weaver writes:
> >
> >> I just followed this up with a Spectre mitigation for WebKitGTK+
> >> backported from upstream WebKit:
> >>
> >>
> >> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=56804398a94bea941183ae4ed2
On 10.01.2018 12:49, Adonay Felipe Nogueira wrote:
I don't know if this serves as guidance as to if microcode is functional
or not, but from [1] I quote:
#+BEGIN_QUOTE
However, there is an exception for secondary embedded processors. The
exception applies to software delivered inside auxiliar
I don't know if this serves as guidance as to if microcode is functional
or not, but from [1] I quote:
#+BEGIN_QUOTE
However, there is an exception for secondary embedded processors. The
exception applies to software delivered inside auxiliary and low-level
processors and FPGAs, within which soft
On 09.01.2018 22:18, Tobias Geerinckx-Rice wrote:
Katherine,
Not really an answer to your question, I'm afraid. Just some thoughts I
had after hitting ‘Send’ on my previous non-answer.
Katherine Cox-Buday wrote on 09/01/18 at 21:13:
Tobias Geerinckx-Rice writes:
[...] how do we square not
Alex Vong writes:
> Hello,
>
> I hope this is on topic. Recently, 2 critical vulnerabilities (see
> https://meltdownattack.com/) affecting virtually all intel cpus are
> discovered. I am running libreboot x200 (see
> https://www.fsf.org/ryf). What should I do right now to patch my laptop?
>
> Che
Leo Famulari skribis:
> After rebooting, I found that my user's numerical ID had changed, so I
> no longer owned any of my files. Not being able to read ~/.ssh means you
> can't log in remotely.
>
> Additionally, several of root's "dotfiles" had been replaced with their
> default versions, erasin
13 matches
Mail list logo
