From owner-freebsd-questions@freebsd.org Sun Feb 4 01:21:57 2018 Return-Path: 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 CE781EDB768 for ; Sun, 4 Feb 2018 01:21:57 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from cosmo.uchicago.edu (cosmo.uchicago.edu [128.135.20.71]) by mx1.freebsd.org (Postfix) with ESMTP id 777F8851EB for ; Sun, 4 Feb 2018 01:21:57 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: by cosmo.uchicago.edu (Postfix, from userid 48) id 7D85ACB8D0F; Sat, 3 Feb 2018 19:21:56 -0600 (CST) Received: from 108.68.160.114 (SquirrelMail authenticated user valeri) by cosmo.uchicago.edu with HTTP; Sat, 3 Feb 2018 19:21:56 -0600 (CST) Message-ID: <53029.108.68.160.114.1517707316.squirrel@cosmo.uchicago.edu> In-Reply-To: References: <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> <044e62f7-69ca-71fe-34a8-5c5cafc06f08@yahoo.com> <0520dd84-c00c-fbf2-da1c-f6ff4c63739d@yahoo.com> <20180203224612.GA10517@milliways.localdomain> <51178.108.68.160.114.1517699531.squirrel@cosmo.uchicago.edu> Date: Sat, 3 Feb 2018 19:21:56 -0600 (CST) Subject: Re: Response to Meltdown and Spectre From: "Valeri Galtsev" To: "Christian Weisgerber" Cc: freebsd-questions@freebsd.org Reply-To: galtsev@kicp.uchicago.edu User-Agent: SquirrelMail/1.4.8-5.el5.centos.7 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Feb 2018 01:21:58 -0000 On Sat, February 3, 2018 7:00 pm, Christian Weisgerber wrote: > On 2018-02-03, "Valeri Galtsev" wrote: > >> With all due respect, one person saying, it didn't affect me, doesn't >> prove it is not disastrous for somebody else. Even if it is one machine >> out of thousand that is "bricked" for some time, it is a disaster for >> sysadmin who has that machine as a production server > > Of course, but who at all is saying that Intel's microcode updates > have "bricked" any machines? This appears to be an entirely spurious > claim, based on nothing other than grievous exaggeration that turns > "higher system reboots" into "bricked". You guys are talking each > other into a frenzy of fear over nothing. 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. I bet I am not the only sysadmin with this point of view. That is why I said production server is by no means comparable to sobody's home workstation. But I bet many people have the same attitude to their home workstations as I have to servers I am responsible for. Well, I for one have the same attitude to all my computers, including laptops, and as a sysadmin - to all computers of people I support. Of course, some people may have different point of view on this, which does not deprive me of expecting from my hardware to work without "glitches". My apologies for being edgy. These things make me such. Valeri > > -- > Christian "naddy" Weisgerber naddy@mips.inka.de > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++