Date: Mon, 25 Apr 2005 14:10:53 -0400 From: Bill Moran <wmoran@potentialtech.com> To: Pete French <petefrench@ticketswitch.com> Cc: freebsd-stable@freebsd.org Subject: Re: Newbie Question About System Update Message-ID: <20050425141053.76034863.wmoran@potentialtech.com> In-Reply-To: <E1DQ7mA-0005mD-JF@dilbert.firstcallgroup.co.uk> References: <20050425134005.089d61c2.wmoran@potentialtech.com> <E1DQ7mA-0005mD-JF@dilbert.firstcallgroup.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Pete French <petefrench@ticketswitch.com> wrote: > > KVM requires you to physically _be_ at the colo. > > ?! Not the one I have for our colo - it's a little java app > where I choose a machine from a dropdown and get the video > in a window on the desktop. That's an out of the ordinary KVM. Would you mind passing on the manufacturer of that unit, I'd like to recommend that unit to a number of clients/associates of mine. The point is that a normal, run of the mill KVM doesn't have that capability. > > A serial console with an IP address and ssh capabilities (which is easy to > > set up, or fairly inexpensive to purchase) allows you access to the system > > as if you're sitting at it, over ssh. > > Ah, O.K. sounds fairly similar to what I have. Preseumably you can get at > BIOS settings and stuff like that too ? > > Still don't see the advantage to be honest, but thanks for the explanation. With a networkable KVM like you've got, there is no real advantage that I can see (unless you're doing kernel debugging, but that's a pretty advanced topic) But compare your KVM to a typical, non-networkable KVM and you get the same idea of what I was thinking when I compared a serial console to a KVM. -- Bill Moran Potential Technologies http://www.potentialtech.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050425141053.76034863.wmoran>