Date: Fri, 14 Sep 2012 10:14:06 +0400 From: Peter Vereshagin <peter@vereshagin.org> To: freebsd-questions@freebsd.org Subject: Re: Sharing COM ports to Windows hosts Message-ID: <20120914061405.GA7815@external.screwed.box> In-Reply-To: <20120905020636.GA38610@admin.sibptus.tomsk.ru> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello. 2012/09/05 09:06:36 +0700 Victor Sudakov <vas@mpeks.tomsk.su> => 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 <peter@vereshagin.org> (http://vereshagin.org) pgp: A0E26627
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120914061405.GA7815>