On Saturday, 13 July 2019 23:03:11 BST Mick wrote:
> Unlike my old Intel which lights up like a christmas tree with "Vulnerable,
> no microcode found" because Intel has thrown its users to the kerb, both
> AMDs show "Not Vulnerable" and for some of the vulnerabilities it reports:
>
> (your CPU ve
> Then I came across this old message regarding Piledriver CPUs:
>
> https://lists.debian.org/debian-security/2016/03/msg00084.html
>
> The post refers to model 2 of cpu family 21. Not all models in the same
> family, only model 2. So I am thinking although patch files are named per
> CPU
> famil
On 2019-07-13 19:06, Mick wrote:
> > If linux-firmware is emerged with the savedconfig use flag, then
> > only the firmware not deleted from the config file is left.
>
> Yes. I used to do this, but gave up after a while.
I find it odd that there is apparently no central way to track which
firmw
On Sun, Jul 14, 2019 at 4:06 AM Mick wrote:
> On Saturday, 13 July 2019 18:42:27 BST Jack wrote:
> >
> > If linux-firmware is emerged with the savedconfig use flag, then only
> > the firmware not deleted from the config file is left.
>
> Yes. I used to do this, but gave up after a while.
Kerne
Does anyone have a binary package for app-backup/amanda-3.4.5 he could
share?
I have to (test the) downgrade because of issues with 3.5.1, and my
binary package doesn't install anymore (perl now upgraded etc)
and the latest amanda doesn't talk to a legacy client which I can't
upgrade at all
Ma
Am 15.07.19 um 08:41 schrieb Stefan G. Weichinger:
>
> Does anyone have a binary package for app-backup/amanda-3.4.5 he could
> share?
>
> I have to (test the) downgrade because of issues with 3.5.1, and my
> binary package doesn't install anymore (perl now upgraded etc)
>
> and the latest amand
6 matches
Mail list logo
