On Mon, Sep 9, 2013 at 12:55 AM, Henrique de Moraes Holschuh
wrote:
> On Sun, 08 Sep 2013, Joel Rees wrote:
>> I was hoping that AMD was not going to have the license and
>> non-visibility issue that plagues the Intel processor microcode
>> updates. But I find this original announcement from when
(Thanks for obliging, Henrik. ;-)
On Sun, Sep 8, 2013 at 5:34 PM, Henrik Ahlgren wrote:
> On Sun, Sep 08, 2013 at 08:00:12AM +0900, Joel Rees wrote:
>> (1) This requires enabling two repositories that I have been avoiding
>> enabling, contrib and non-free. That means I have to watch the
>> reposi
On 9/09/2013 2:18 AM, Volker Birk wrote:
> On Sun, Sep 08, 2013 at 12:55:05PM -0300, Henrique de Moraes Holschuh wrote:
>> Note that even the internal errata/fix information is bound to be really
>> uninteresting anyway. Backdoors would not be documented anywhere, heck, it
>> is very likely that o
On Sun, Sep 08, 2013 at 12:55:05PM -0300, Henrique de Moraes Holschuh wrote:
> Note that even the internal errata/fix information is bound to be really
> uninteresting anyway. Backdoors would not be documented anywhere, heck, it
> is very likely that only the one or two engineers that had to imple
On Sun, 08 Sep 2013, Joel Rees wrote:
> I was hoping that AMD was not going to have the license and
> non-visibility issue that plagues the Intel processor microcode
> updates. But I find this original announcement from when Henrique made
> the updater tool available:
>
> http://lists.debian.org/d
On Sun, 08 Sep 2013, Henrik Ahlgren wrote:
> > or synaptic to look for new tools, right? Or can we just enable those
> > two repositories long enough to load Henrique's tool and the microcode
> > updates, then disable them again?
>
> Why do you feel that you even need to ask? You are free to handl
On Sun, Sep 08, 2013 at 08:00:12AM +0900, Joel Rees wrote:
> (1) This requires enabling two repositories that I have been avoiding
> enabling, contrib and non-free. That means I have to watch the
> repository more carefully when using
>
> apt-cache search
>
> or synaptic to look for new tools
(I kind of hope this starts a flame war large enough to embarrass the
corporate culprits into behaving themselves about this. Apologies in
advance when I step on toes.)
I was hoping that AMD was not going to have the license and
non-visibility issue that plagues the Intel processor microcode
updat
8 matches
Mail list logo
