From owner-freebsd-questions@freebsd.org Tue Feb 6 15:16:31 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 8B080EDF84E for ; Tue, 6 Feb 2018 15:16:31 +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 1C5C66E192 for ; Tue, 6 Feb 2018 15:16:30 +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 w16FGL1U037090 for ; Tue, 6 Feb 2018 15:16:21 GMT (envelope-from frank2@fjl.co.uk) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 06 Feb 2018 15:16:21 +0000 From: Frank Leonhardt To: freebsd-questions@freebsd.org Subject: Re: Response to Meltdown and Spectre Organization: FJL Microsystems 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> <53029.108.68.160.114.1517707316.squirrel@cosmo.uchicago.edu> <20180205143720.d4d98011.freebsd@edvax.de> Message-ID: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Feb 2018 15:16:31 -0000 On 2018-02-06 01:06, Chris Hill wrote: > 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 > :^\ Are you seriously saying that their Windows servers stayed up ALL WEEK without a reboot?