From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 048B3138C9D for ; Sun, 26 Apr 2015 15:14:46 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CC8DBE089E; Sun, 26 Apr 2015 15:14:39 +0000 (UTC) Received: from smarthost01d.mail.zen.net.uk (smarthost01d.mail.zen.net.uk [212.23.1.7]) by pigeon.gentoo.org (Postfix) with ESMTP id BA2CBE088F for ; Sun, 26 Apr 2015 15:14:38 +0000 (UTC) Received: from [82.69.80.10] (helo=wstn.localnet) by smarthost01d.mail.zen.net.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YmOGT-00071V-UA for gentoo-user@lists.gentoo.org; Sun, 26 Apr 2015 15:14:38 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] And so the emerge spake: Let there be conflicts...and see, everything was chaos and sin... Date: Sun, 26 Apr 2015 16:14:45 +0100 Message-ID: <2130972.i0k47PUt0k@wstn> Organization: Society for Retired Gentlefolk User-Agent: KMail/4.14.3 (Linux/3.18.11-gentoo; KDE/4.14.3; x86_64; ; ) In-Reply-To: <553CECDF.3000101@gmail.com> References: <20150425160758.GA32271@solfire> <20150426091742.3cb310cb@digimed.co.uk> <553CECDF.3000101@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost01d-IP: [82.69.80.10] X-Archives-Salt: 1ddf52d4-b6e9-490d-9720-24a6ef0649a4 X-Archives-Hash: 4b1cfbc425c498c7a56fecc2e6f5e789 On Sunday 26 April 2015 15:49:19 Alan McKinnon wrote: > I disagree. emerge really needs to have it's output redesigned from > scratch. Right now it arrives at the conclusion (the top) and dumps it's > data tree bottom-up, apparently stopping halfway and never getting to > output what the top is. This discussion reminds me of an AGR (Advanced Gas-cooled Reactor) power station being commissioned 40-odd years ago, in which a minor plant failure (e.g. a high oil temp in an auxiliary pump) could lead to cascades of other abnormal conditions, making it impossible for a reactor operator to discover the real problem he needed to fix, and ignore all the others. So we put up a second alarm screen alongside the first, showing major causes only; it was populated with the output of an analysis routine that was called whenever an alarm occurred. All those decision trees had to be designed and input by hand (on paper tape, like everything else). Not to mention testing, of course. And there were thousands of digital inputs. Maybe something like that would be useful here. -- Rgds Peter