MESSAGE
| DATE | 2018-03-05 |
| FROM | valdis.kletnieks@vt.edu
|
| SUBJECT | Re: [Hangout - NYLXS] Year 2038 time set problem
|
From hangout-bounces-at-nylxs.com Mon Mar 5 20:38:39 2018
Return-Path:
X-Original-To: archive-at-mrbrklyn.com
Delivered-To: archive-at-mrbrklyn.com
Received: from www2.mrbrklyn.com (www2.mrbrklyn.com [96.57.23.82])
by mrbrklyn.com (Postfix) with ESMTP id 4308F161177;
Mon, 5 Mar 2018 20:38:39 -0500 (EST)
X-Original-To: hangout-at-www2.mrbrklyn.com
Delivered-To: hangout-at-www2.mrbrklyn.com
Received: by mrbrklyn.com (Postfix, from userid 1000)
id 5716E16115C; Mon, 5 Mar 2018 20:38:37 -0500 (EST)
Resent-From: Ruben Safir
Resent-Date: Mon, 5 Mar 2018 20:38:37 -0500
Resent-Message-ID: <20180306013837.GJ2765-at-www2.mrbrklyn.com>
Resent-To: hangout-at-mrbrklyn.com
X-Original-To: ruben-at-mrbrklyn.com
Delivered-To: ruben-at-mrbrklyn.com
Received: from omr2.cc.vt.edu (outbound.smtp.vt.edu [198.82.183.121])
by mrbrklyn.com (Postfix) with ESMTP id B1322161132
for ; Mon, 5 Mar 2018 03:50:28 -0500 (EST)
Received: from mr2.cc.vt.edu (smtp.ipv6.vt.edu
[IPv6:2607:b400:92:9:0:9d:8fcb:4116])
by omr2.cc.vt.edu (8.14.4/8.14.4) with ESMTP id w258oRIH006963
for ; Mon, 5 Mar 2018 03:50:27 -0500
Received: from mail-qt0-f197.google.com (mail-qt0-f197.google.com
[209.85.216.197])
by mr2.cc.vt.edu (8.14.7/8.14.7) with ESMTP id w258oMW9008328
for ; Mon, 5 Mar 2018 03:50:27 -0500
Received: by mail-qt0-f197.google.com with SMTP id v89so13562785qte.21
for ; Mon, 05 Mar 2018 00:50:27 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:sender:from:to:cc:subject:in-reply-to:references
:mime-version:content-transfer-encoding:date:message-id;
bh=X51JvXTxNAKNj3ipTzRXZmp2MYPfxWT2sgy7M9hRAb8=;
b=PplnXOSOOeueGJLCJ5G+uWOxepIlBg3twmOwpzNNsQqEUc5SPlYS2POiiJfnBz9Mvx
Kiq/DAVzYbc0ZnO18Kk6oV4sAu94iau30523kdnd0lb3+hJvke9yLJH5UV6FZxlOLZJI
gFpObqvYIW33Go1z/vCtnj6DV5qPOb1ifJTPwg3D/IqpiNo+b6oRTZ5EGCFvQiB2pwxs
KXv8nOah29oZKhkM1UeGZwDwPXxPxpRejlbKUQF43F5/Fl3gPaMO2iAAxr47wELRJl6w
OLpXybwSCmgb8nBCzhUC2KKPclyTsOP+0yt+20Zjio4hbdluNvJoTUrUrd4neqI9m2Kr
5x8w==
X-Gm-Message-State: AElRT7GDQMfUAvqPWGIVk1iZohq+PWp7w5rhdlQiLq+5YTTotJgAMV7m
9t7eZ7cbFDRqglYYD7MOAgreUppn5ADRJ/6uRPoNoXMviILZllemMmUPmPQIfvvF2SMdS5EWmXu
TNNIPIHuuETbq+AtCTo3KCIweCrbPBeBLvuTd3+dZ80kiDISbpM6BU1jhAV+93PKs9m+51RIlYw
Rh770=
X-Received: by 10.200.12.68 with SMTP id l4mr21649931qti.71.1520239822019;
Mon, 05 Mar 2018 00:50:22 -0800 (PST)
X-Google-Smtp-Source: AG47ELv2M9vu0TH5M8sk/ydae7zoUN6YQOt/EQDbm9IVnGnB2PsivKvF+wl9Axdcm+YE7AjdY5QFfw==
X-Received: by 10.200.12.68 with SMTP id l4mr21649913qti.71.1520239821749;
Mon, 05 Mar 2018 00:50:21 -0800 (PST)
Received: from turing-police.cc.vt.edu
([2601:5c0:c001:4342:f962:5e05:19b5:1136])
by smtp.gmail.com with ESMTPSA id a73sm8076119qkb.14.2018.03.05.00.50.20
(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
Mon, 05 Mar 2018 00:50:20 -0800 (PST)
From: valdis.kletnieks-at-vt.edu
X-Google-Original-From: Valdis.Kletnieks-at-vt.edu
X-Mailer: exmh version 2.8.0 04/21/2017 with nmh-1.7+dev
To: Ruben Safir
In-Reply-To: <7cc29390-03dd-944d-827c-bdb286dc26ae-at-mrbrklyn.com>
References:
<77520.1520202258-at-turing-police.cc.vt.edu>
<80280427-f23e-ae30-a3cd-5230c7a5de06-at-mrbrklyn.com>
<118179.1520223358-at-turing-police.cc.vt.edu>
<7cc29390-03dd-944d-827c-bdb286dc26ae-at-mrbrklyn.com>
Mime-Version: 1.0
Date: Mon, 05 Mar 2018 03:50:19 -0500
Message-ID: <148676.1520239819-at-turing-police.cc.vt.edu>
X-UID: 46798
Cc: kernelnewbies-at-kernelnewbies.org
Subject: Re: [Hangout - NYLXS] Year 2038 time set problem
X-BeenThere: hangout-at-nylxs.com
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: NYLXS Tech Talk and Politics
List-Unsubscribe: ,
List-Post:
List-Help:
List-Subscribe: ,
Content-Type: multipart/mixed; boundary="===============1289026294=="
Errors-To: hangout-bounces-at-nylxs.com
Sender: "Hangout"
--===============1289026294==
Content-Type: multipart/signed; boundary="==_Exmh_1520239818_14985P";
micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
--==_Exmh_1520239818_14985P
Content-Type: text/plain; charset=us-ascii
On Sun, 04 Mar 2018 23:50:32 -0500, Ruben Safir said:
> Don't pretend to understand what I can and can not afford. Your not
> picking security policy for Google. What your failing to address,
> because you are so blinded to your own frame of reference, is that your
> solution leaves out well over 90% of the devices connected to the
> internet, some of those devices connected to things like nuclear power
> plants. Others are just VOIP appliances.
Give an example of a system - *ANY* system - where you *can't* afford
the time down for a reboot, but the downtime for a hardware failure *is*
acceptable.
If you connect something to a nuclear power plant and can't afford a reboot
time, what is your plan if the device fails entirely?
If you can't stand your VOIP box being down at 3AM when there's no calls
in progress, what do you intend to use for voice service if you're down
because a DIMM failed?
Don't confuse "the downtime for a reboot pisses me off personally"
with "if we take downtime at all, it's A Serious Problem". If it's the
former, then you have to learn that reboots are like changing the oil
in your car - refusing to do periodic maintenance will bite you eventually.
If it's the latter, and you *aren't* already doing things like HA to deal with
hardware failures, *you are being negligent*. And yes, we're talking in "court
of law" mode here for some things - if you knew that downtime would cause
damages (either physical or monetary) and you didn't do anything about it, you
better have a *really* hefty insurance policy covering negligence on your part.
And if you *are* doing stuff to deal with hardware failures, *then a reboot
is a non-issue*.
(And by the way - as I've mentioned, managing reboots is the *easy* part of
updating an Internet of Pwned Things device. The hard part is getting the
vendor to produce an update in the first place...)
--==_Exmh_1520239818_14985P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Comment: Exmh version 2.8.0 04/21/2017
iQEVAwUBWp0Eyo0DS38y7CIcAQK/nAgAhmjcJSG3zG8VqbKY9ReLrxOb/N+Uc3us
OVYMS5gbtKXWoPgVDuasMJcnjpkVWBVugf2OUlPqFL2DqzofMFj/E5tC+ugfWBhg
ea84h+j2Hshxr5v5C2qURZRzNAZxd+huHuVTfeqX+1HiMeTGJ4/pz+16X3ChzyTH
XpLrItQ77+lSXkAHqgCE3sVs8W8dqH+WhjrKjE7NLcdw355bNblHS4k5ypLjjHUf
UvBVsp39Zqxed7A9UB1QqJVeplyx5rHZhoIRs06OWLF8B7CWEP8x5jXiB0NAXagc
93y5Chq6VZHkK2LFpGtihCPF0c/P1M8k/Uj/qFv5b+c6lAb+jUQ5fA==
=YxE+
-----END PGP SIGNATURE-----
--==_Exmh_1520239818_14985P--
--===============1289026294==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout
--===============1289026294==--
--===============1289026294==
Content-Type: multipart/signed; boundary="==_Exmh_1520239818_14985P";
micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
--==_Exmh_1520239818_14985P
Content-Type: text/plain; charset=us-ascii
On Sun, 04 Mar 2018 23:50:32 -0500, Ruben Safir said:
> Don't pretend to understand what I can and can not afford. Your not
> picking security policy for Google. What your failing to address,
> because you are so blinded to your own frame of reference, is that your
> solution leaves out well over 90% of the devices connected to the
> internet, some of those devices connected to things like nuclear power
> plants. Others are just VOIP appliances.
Give an example of a system - *ANY* system - where you *can't* afford
the time down for a reboot, but the downtime for a hardware failure *is*
acceptable.
If you connect something to a nuclear power plant and can't afford a reboot
time, what is your plan if the device fails entirely?
If you can't stand your VOIP box being down at 3AM when there's no calls
in progress, what do you intend to use for voice service if you're down
because a DIMM failed?
Don't confuse "the downtime for a reboot pisses me off personally"
with "if we take downtime at all, it's A Serious Problem". If it's the
former, then you have to learn that reboots are like changing the oil
in your car - refusing to do periodic maintenance will bite you eventually.
If it's the latter, and you *aren't* already doing things like HA to deal with
hardware failures, *you are being negligent*. And yes, we're talking in "court
of law" mode here for some things - if you knew that downtime would cause
damages (either physical or monetary) and you didn't do anything about it, you
better have a *really* hefty insurance policy covering negligence on your part.
And if you *are* doing stuff to deal with hardware failures, *then a reboot
is a non-issue*.
(And by the way - as I've mentioned, managing reboots is the *easy* part of
updating an Internet of Pwned Things device. The hard part is getting the
vendor to produce an update in the first place...)
--==_Exmh_1520239818_14985P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Comment: Exmh version 2.8.0 04/21/2017
iQEVAwUBWp0Eyo0DS38y7CIcAQK/nAgAhmjcJSG3zG8VqbKY9ReLrxOb/N+Uc3us
OVYMS5gbtKXWoPgVDuasMJcnjpkVWBVugf2OUlPqFL2DqzofMFj/E5tC+ugfWBhg
ea84h+j2Hshxr5v5C2qURZRzNAZxd+huHuVTfeqX+1HiMeTGJ4/pz+16X3ChzyTH
XpLrItQ77+lSXkAHqgCE3sVs8W8dqH+WhjrKjE7NLcdw355bNblHS4k5ypLjjHUf
UvBVsp39Zqxed7A9UB1QqJVeplyx5rHZhoIRs06OWLF8B7CWEP8x5jXiB0NAXagc
93y5Chq6VZHkK2LFpGtihCPF0c/P1M8k/Uj/qFv5b+c6lAb+jUQ5fA==
=YxE+
-----END PGP SIGNATURE-----
--==_Exmh_1520239818_14985P--
--===============1289026294==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
Hangout mailing list
Hangout-at-nylxs.com
http://lists.mrbrklyn.com/mailman/listinfo/hangout
--===============1289026294==--
|
|
