public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Alternatives to knutclient
Date: Sun, 29 Oct 2017 21:38:37 +0000	[thread overview]
Message-ID: <20171029213837.22931a9d@digimed.co.uk> (raw)
In-Reply-To: <1868041.QUjdRgedtp@dell_xps>

[-- Attachment #1: Type: text/plain, Size: 681 bytes --]

On Sun, 29 Oct 2017 19:11:13 +0000, 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.  :-(

I can see the power station cooling towers from my house, but I still used
to get flickering lights and repeated ha


-- 
Neil Bothwick

Is that "woof" feed me; "woof" walk me; "woof" rdware failures
until I invested in a UPS or two.there's a burglar? What??

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-10-29 21:38 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
2017-10-29 21:38                 ` Neil Bothwick [this message]
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=20171029213837.22931a9d@digimed.co.uk \
    --to=neil@digimed.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