From owner-freebsd-questions@FreeBSD.ORG Fri Sep 14 06:22:22 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B2F9106566C for ; Fri, 14 Sep 2012 06:22:22 +0000 (UTC) (envelope-from peter@vereshagin.org) Received: from mx1.skyriver.ru (ns1.skyriver.ru [89.108.118.221]) by mx1.freebsd.org (Postfix) with ESMTP id B57768FC0A for ; Fri, 14 Sep 2012 06:22:21 +0000 (UTC) Received: from localhost (h-188-250.a189.priv.bahnhof.se [85.24.188.250]) by mx1.skyriver.ru (Postfix) with ESMTPSA id 995495AD3 for ; Fri, 14 Sep 2012 10:14:13 +0400 (MSK) Date: Fri, 14 Sep 2012 10:14:06 +0400 From: Peter Vereshagin To: freebsd-questions@freebsd.org Message-ID: <20120914061405.GA7815@external.screwed.box> References: <20120903030217.GA79339@admin.sibptus.tomsk.ru> <86wr0binyc.fsf@srvbsdfenssv.interne.associated-bears.org> <20120903072920.GB92658@admin.sibptus.tomsk.ru> <20120903125210.GA5387@external.screwed.box> <20120905020636.GA38610@admin.sibptus.tomsk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20120905020636.GA38610@admin.sibptus.tomsk.ru> Organization: ' X-Face: 8T>{1owI$Byj]]a; ^G]kRf*dkq>E-3':F>4ODP[#X4s"dr?^b&2G@'3lukno]A1wvJ_L(~u 6>I2ra/<,j1%@C[LN=>p#_}RIV+#:KTszp-X$bQOj,K Subject: Re: Sharing COM ports to Windows hosts X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Sep 2012 06:22:22 -0000 Hello. 2012/09/05 09:06:36 +0700 Victor Sudakov => To freebsd-questions@freebsd.org : VS> > Depending on a task I think the most interactive user-friendly solution here is VS> > a minicom(s) each in its own ssh'ed jail(s). VS> VS> There is special Windows software for managing Natex MUXes. It works [..] VS> Solution 2. Using an existing networked FreeBSD box sitting next to VS> the MUX, it already has COM ports. Advantage: cheap, no additional ok. no interactivity. But I'm still optimistic about virtualization. emulators/qemu at the least should be able to run that software and use com-ports from the master freebsd system at the same time. Then you can you can use remote access features for workstation access to the software. VS> doubts ... English is so poor coffee is your friend (c) -- Peter Vereshagin (http://vereshagin.org) pgp: A0E26627