public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Brent Harding" <bharding@doorpi.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: VmWare
Date: Mon, 16 Apr 2007 09:35:13 -0500	[thread overview]
Message-ID: <000c01c78034$71fded70$224a5c46@brent827e59cc1> (raw)
In-Reply-To: <20070416043538.GA98469@fajrero>

To install about anything else that needs serial console, where does one end 
up getting a virtual serial port into the Windows side? I assume that a 
virtual port is needed on the host side to connect to the VM's virtual 
serial port. I would say that Minicom with Cygwin is probably the easiest 
way to deal with installations where you need to deal with the checkboxes 
and other controls in dialog boxes that come from the VM side of the 
connection.
----- Original Message ----- 
From: "Tyler Spivey" <tspivey@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, April 15, 2007 11:35 PM
Subject: Re: VmWare


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I've installed everything from FreeBSD to Solaris to Linux in a vm, and
> am getting quite good at it now. The one requirement is having a lot of
> ram, since the vm's ram + however much ram the host needs is quite a
> bit. With 768MB, it's not too bad - but it could be better. Also,
> vmware's audio performance is - not so great. If you're just using ssh
> from the window side, it's not that much of an issue - since you can
> just play mp3s and such on windows.
> Just my $0.02,
> Tyler
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (FreeBSD)
>
> iD8DBQFGIv0aTsjaYASMWKQRAlKPAKCipLaMsamqAVNZS+fao/teB9jAXwCgqMUO
> QohLoGyCVLohffWcKd5ePpo=
> =fqyb
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



  parent reply	other threads:[~ UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 VmWare Zachary Kline
 ` VmWare Gregory Nowak
   ` VmWare Alex Snow
   ` VmWare Zachary Kline
     ` VmWare Gregory Nowak
       ` VmWare Tyler Spivey
         ` VmWare Zachary Kline
         ` Brent Harding [this message]
       ` VmWare Zachary Kline
       ` VmWare Alex Snow
 ` VmWare Doug Smith
   ` VmWare Christopher Moore
   ` VmWare Alex Snow
     ` VmWare Doug Smith
 ` VmWare Jeremy
   ` VmWare Alex Snow
   ` VmWare Brent Harding
     ` VmWare Ricky Enger
     ` VmWare Zachary Kline
       ` VmWare Brent Harding
     ` VmWare Alex Snow
     ` VmWare Gregory Nowak
       ` Re[2]: VmWare Farhan
       ` VmWare Alex Snow
         ` VmWare Jeremy
       ` VmWare Brent Harding
  -- strict thread matches above, loose matches on Subject: below --
 VmWare Jeremy
 vmware Dawes, Stephen
 vmware Sergey Fleytin
 vmware Scott Howell
 ` vmware Geoff Shang
   ` vmware Scott Howell
     ` vmware Kerry Hoath
       ` vmware scott howell
       ` vmware Bart Bunting
     ` vmware John Covici
 ` vmware Kris Van Hees
   ` vmware cpt.kirk
     ` vmware Scott Howell
       ` vmware cpt.kirk
     ` vmware Count Zero
       ` vmware Victor Tsaran
   ` vmware Scott Howell
 ` vmware Bart Bunting
 ` vmware John Covici
   ` vmware scott howell
     ` vmware John Covici
       ` vmware scott howell

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='000c01c78034$71fded70$224a5c46@brent827e59cc1' \
    --to=bharding@doorpi.net \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).