From owner-freebsd-questions@freebsd.org Tue Feb 6 01:18:37 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 C1401EE0370 for ; Tue, 6 Feb 2018 01:18:37 +0000 (UTC) (envelope-from chris@monochrome.org) Received: from mail.monochrome.org (host-209-190-254-14.client.atlantech.net [209.190.254.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail", Issuer "mail" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 833416BD6E for ; Tue, 6 Feb 2018 01:18:34 +0000 (UTC) (envelope-from chris@monochrome.org) Received: from tripel.monochrome.org (tripel.monochrome.org [192.168.1.11]) by mail.monochrome.org (8.15.2/8.15.2) with ESMTP id w1616YLB010515; Mon, 5 Feb 2018 20:06:35 -0500 (EST) (envelope-from chris@monochrome.org) Date: Mon, 5 Feb 2018 20:06:38 -0500 (EST) From: Chris Hill To: Polytropon cc: galtsev@kicp.uchicago.edu, freebsd-questions@freebsd.org Subject: Re: Response to Meltdown and Spectre In-Reply-To: <20180205143720.d4d98011.freebsd@edvax.de> Message-ID: 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> <53029.108.68.160.114.1517707316.squirrel@cosmo.uchicago.edu> <20180205143720.d4d98011.freebsd@edvax.de> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed 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: Tue, 06 Feb 2018 01:18:37 -0000 On Mon, 5 Feb 2018, Polytropon wrote: > ...On the other hand, I know many businesses where rebooting servers > is quite common ("Windows"-based installations, of course), which if > often due to software problems, wrongly configured hardware, broken > hardware, or missing technical skills of the "professional > consultants" and "solution experts"... Off topic here, for a change. At the place where I worked during the year 2000, a sysadmin told me it was standard that they would reboot the servers (Windows monoculture, even back then) every Friday after close of business. When I asked him why, he said it was "best practice." And if anything went wrong, they had the weekend to fix it :^\ > ...Working in IT is not fun anymore... ;-) I'm technically under the IT group at work, but I thank bloody bog that my job is not actually IT. -- Chris Hill chris@monochrome.org ** [ Busy Expunging ]