From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Alternatives to knutclient
Date: Sun, 29 Oct 2017 19:30:15 +0000 [thread overview]
Message-ID: <59F62C47.4070703@youngman.org.uk> (raw)
In-Reply-To: <1868041.QUjdRgedtp@dell_xps>
On 29/10/17 19:11, Mick wrote:
> BTW, perhaps in UK cities general and unpredicted power cuts are relatively
> rare and brownouts don't occur often. Out in the sticks the infrastructure is
> so neglected power cuts and brown outs can be a weekly occurrence. I just
> bought yet another UPS to protect my TV and media devices, having suffered
> catastrophic failures in the past. :-(
That looks like infrastructure failure, not plain insufficient power
which is what we are apparently heading for. Certainly the "explosions"
one is "old news" - where I worked suffered this sort of failure in the
early 90's.
The story as I understood it was some crooks went down a manhole to try
and blow their way into a Lloyds Bank vault. Unfortunately, between them
and the vault was a - somewhat overloaded - 50KV supply line. When the
charge went off, this shorted for some 5 miles of cable :-(
It's too long ago now, I think it happened on a Sunday night so we came
in to work to no power. They got an emergency rig up and running Monday
afternoon, one phase back by about Wednesday, and everything back to
normal the following Monday. This was the Kings Road in London!
But the new feature is just "not enough power" - that really will be a
problem!
Cheers,
Wol
next prev parent reply other threads:[~2017-10-29 19:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-28 8:58 [gentoo-user] Alternatives to knutclient Mick
2017-10-28 14:18 ` Daniel Frey
2017-10-28 16:48 ` Mick
2017-10-28 23:51 ` Daniel Frey
2017-10-29 1:56 ` Dale
2017-10-29 8:49 ` Mick
2017-10-29 11:21 ` Dale
2017-10-29 19:01 ` Wols Lists
2017-10-29 19:11 ` Mick
2017-10-29 19:30 ` Wols Lists [this message]
2017-10-29 21:38 ` Neil Bothwick
2017-10-29 19:46 ` Dale
2017-10-30 9:10 ` Peter Humphrey
2017-10-30 10:15 ` Mick
2017-10-30 14:09 ` Daniel Frey
2017-10-30 14:47 ` Mick
2017-10-30 19:33 ` Daniel Frey
2017-10-30 19:37 ` Daniel Frey
2017-10-30 19:40 ` Rich Freeman
2017-10-30 21:01 ` Dale
2017-10-30 23:39 ` Mick
2017-10-31 0:09 ` mad.scientist.at.large
2017-10-31 17:33 ` Wols Lists
2017-10-31 23:29 ` Peter Humphrey
2017-11-01 12:45 ` Wols Lists
2017-11-01 13:47 ` Peter Humphrey
2017-10-31 0:26 ` Dale
2017-10-31 0:55 ` Daniel Frey
2017-10-30 20:51 ` mad.scientist.at.large
2017-10-30 20:50 ` Dale
2017-10-30 21:04 ` Rich Freeman
2017-10-30 23:28 ` Mick
2017-10-30 23:42 ` Rich Freeman
2017-10-31 17:05 ` Wols Lists
2017-10-31 17:13 ` Rich Freeman
2017-10-31 16:56 ` Wols Lists
2017-10-31 17:08 ` Rich Freeman
2017-10-30 22:59 ` Mick
2017-10-30 23:32 ` Rich Freeman
2017-10-31 17:17 ` Wols Lists
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=59F62C47.4070703@youngman.org.uk \
--to=antlists@youngman.org.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