public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
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	[thread overview]
Message-ID: <2130972.i0k47PUt0k@wstn> (raw)
In-Reply-To: <553CECDF.3000101@gmail.com>

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



  reply	other threads:[~2015-04-26 15:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-25 16:07 [gentoo-user] And so the emerge spake: Let there be conflicts...and see, everything was chaos and sin Meino.Cramer
2015-04-25 20:15 ` Daniel Frey
2015-04-26  2:06   ` Meino.Cramer
2015-04-26  7:38     ` Alan McKinnon
2015-04-26 14:16       ` Daniel Frey
2015-04-26  6:49 ` [gentoo-user] " Martin Vaeth
2015-04-26  7:32   ` Meino.Cramer
2015-04-26 13:13     ` Martin Vaeth
2015-04-26 13:30       ` Meino.Cramer
2015-04-26  8:19   ` Neil Bothwick
2015-04-26 13:08     ` Martin Vaeth
2015-04-26  7:35 ` [gentoo-user] " Alan McKinnon
2015-04-26  7:57   ` Meino.Cramer
2015-04-26 11:30     ` Alan McKinnon
2015-04-26 11:45       ` Meino.Cramer
2015-04-26  8:17   ` Neil Bothwick
2015-04-26 13:49     ` Alan McKinnon
2015-04-26 15:14       ` Peter Humphrey [this message]
2015-04-26 16:07       ` [gentoo-user] " walt
2015-04-26 17:17       ` [gentoo-user] " Neil Bothwick
2015-04-26 19:17         ` Philip Webb
2015-04-26 20:23           ` Michael Orlitzky
2015-04-26 21:28             ` Philip Webb
2015-04-26 22:06               ` Neil Bothwick
2015-04-26 22:23               ` Michael Orlitzky
2015-04-27  5:47                 ` Alan McKinnon
2015-04-28 14:11                   ` Dale
2015-04-28 16:34                   ` Philip Webb
2015-04-27  5:40               ` Alan McKinnon
2015-04-27  7:30               ` [gentoo-user] " Martin Vaeth
2015-04-26 20:48         ` james
2015-04-27 20:11           ` Michael Orlitzky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2130972.i0k47PUt0k@wstn \
    --to=peter@prh.myzen.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox