From owner-freebsd-questions@freebsd.org  Mon Feb  5 16:19:48 2018
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8DD96ED8FDA
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Mon,  5 Feb 2018 16:19:48 +0000 (UTC)
 (envelope-from frank2@fjl.co.uk)
Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 117277A2E5
 for <freebsd-questions@freebsd.org>; Mon,  5 Feb 2018 16:19:47 +0000 (UTC)
 (envelope-from frank2@fjl.co.uk)
Received: from roundcube.fjl.org.uk (localhost [127.0.0.1])
 by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id w15GJhWh072727
 for <freebsd-questions@freebsd.org>; Mon, 5 Feb 2018 16:19:43 GMT
 (envelope-from frank2@fjl.co.uk)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date: Mon, 05 Feb 2018 16:19:43 +0000
From: Frank Leonhardt <frank2@fjl.co.uk>
To: freebsd-questions@freebsd.org
Subject: Re: Response to Meltdown and Spectre
Organization: FJL Microsystems
In-Reply-To: <20180205155721.GA2938@c720-r314251>
References: <CA+tpaK2o1nbY2W2JVRtogN=P2VM9rag_dodK=GtLWgKwNsYZkg@mail.gmail.com>
 <F395799E-2C94-47E9-AA1C-5CB075C50076@kreme.com>
 <044e62f7-69ca-71fe-34a8-5c5cafc06f08@yahoo.com>
 <slrnp7bpa3.2k8.naddy@lorvorc.mips.inka.de>
 <0520dd84-c00c-fbf2-da1c-f6ff4c63739d@yahoo.com>
 <20180203224612.GA10517@milliways.localdomain>
 <51178.108.68.160.114.1517699531.squirrel@cosmo.uchicago.edu>
 <slrnp7cmpn.5vo.naddy@lorvorc.mips.inka.de>
 <53029.108.68.160.114.1517707316.squirrel@cosmo.uchicago.edu>
 <20180205143720.d4d98011.freebsd@edvax.de>
 <20180205155721.GA2938@c720-r314251>
Message-ID: <9db8908e8c86efddcab5b768fcde1f24@roundcube.fjl.org.uk>
X-Sender: frank2@fjl.co.uk
User-Agent: Roundcube Webmail/0.9.2
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Feb 2018 16:19:48 -0000

On 2018-02-05 15:57, Matthias Apitz wrote:
> El día lunes, febrero 05, 2018 a las 02:37:20p. m. +0100, Polytropon 
> escribió:
> 
>> > For all production server I run any reboot that is not scheduled by admins
>> > is ultimate disaster, so it is equivalent to "bricked" machine. That
>> > hardware can not be further used as production server, but "mere" fact or
>> > reboot is ultimate disaster itself.
>> 
>> While this is not the established meaning of "bricked", it it
>> definitely an understandable (!) interpretation of the term.
> 
> For me "bricked" in addition to "unusable" means: there is no software
> way any more to change the fault because the hardware does not boot up
> into a state where it could read(...) any attempts to change somethinb. 
> The
> device is now "dark" and does not communicate anymore by no means.
> 
> Only a hardware change (for example replace some chip) would help.

I'd go further - something is only bricked to me when I can't fix it 
using a rework station. It's been done...

HOWEVER, Polytropon et al make a very good point - if the software 
update means the device is no longer usable for its intended purpose 
then it might as well have bricked it. The effect is the same.