From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Choice of KVM?
Date: Sat, 16 Sep 2017 15:35:16 +0100 [thread overview]
Message-ID: <6F01A255-193B-4E0B-8207-9FDC9BE51D48@stellar.eclipse.co.uk> (raw)
In-Reply-To: <47052055.5YIo8tqYQF@peak>
> On 16 Sep 2017, at 15:19, Peter Humphrey <peter@prh.myzen.co.uk> wrote:
>
> As always, as soon as I'd sent that I found an answer: someone who'd
> replaced "flaky" Belkin with Aten.
I think they're probably all based on the same OEM chipsets, anyway.
I was quite into the KVM-over-IP versions a few years ago, and they certainly all were. I'd find a near identical product (you could especially tell by the web interface) from half a dozen or more manufacturers.
Stroller.
next prev parent reply other threads:[~2017-09-16 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-16 14:00 [gentoo-user] [OT] Choice of KVM? Peter Humphrey
2017-09-16 14:19 ` Peter Humphrey
2017-09-16 14:35 ` Stroller [this message]
2017-09-16 15:55 ` mad.scientist.at.large
2017-09-16 14:43 ` Alan Mackenzie
2017-09-16 16:07 ` Peter Humphrey
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=6F01A255-193B-4E0B-8207-9FDC9BE51D48@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.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