From: "John G. Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: duo boot systems...revisited, i think?
Date: Thu, 17 Jul 2008 09:57:59 -0500 [thread overview]
Message-ID: <005301c8e81d$81712270$5501a8c0@mcgee> (raw)
In-Reply-To: <Pine.BSF.4.64.0807170054350.59872@server1.shellworld.net>
I would recommend setting up a virtual machine instead of a dual boot
system. The difference is that with a dual boot system, you boot into either
linux or windows. With a virtual machine, either the linux or windows
operating system runs as a virtual machine in the other operating system.
But you don't have to reboot to get to the other operating system. I've
found that the only time I use the "other" operating system on my dual boot
machines is for testing purposes. For instance, I'm typing this message on
a machine that's dual boot but I haven't booted it into linux for months.
Really since I set it up. Most often what I do is boot my old dual boot
machine into linux and use that.
----- Original Message -----
From: "Karen Lewellen" <klewellen@shellworld.net>
Cc: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, July 17, 2008 12:02 AM
Subject: duo boot systems...revisited, i think?
> sigh,
> Just when I think I have a reasonable mind and the door to the hard ware,
> I have to start all over again.
> I thought there was a discussion once about the need for a duo boot
> system, but I cannot find this.
> pros cons, really needful?
> My goal remains for a number of reasons, a system with two separate
> drives, I know I need not do this, but just call me paranoid grin.
> for the foreseeable future, dos will remain my primary os, with the Linux
> distro I use on the second drive.
> I am building a different machine that will be a stand alone Linux server
> box, with some extras given the results of additional research.
> Sorry is this is a newbie question, but after reading that the *official*
> stock of Debian does not support speakup,...I am behind on reading the
> rest of that thread, I am being more careful than ever.
> Thanks,
> Karen
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
text console tools for audio processing Chuck Hallenbeck
` John covici
` Janina Sajka
` luke
` Chuck Hallenbeck
` luke
` Chuck Hallenbeck
` luke
` Georgina Joyce
` Janina Sajka
[not found] ` <Pine.LNX.4.64.0806161540510.3591@gube.gnpgvphfpbzzhavpngvbaf.arg>
` John covici
` John covici
` Chuck Hallenbeck
` John covici
` duo boot systems...revisited, i think? Karen Lewellen
` John covici
` John G. Heim [this message]
` Karen Lewellen
` Kristoffer Gustafsson
` luke
` Karen Lewellen
` Kerry Hoath
` Karen Lewellen
` luke
` Karen Lewellen
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='005301c8e81d$81712270$5501a8c0@mcgee' \
--to=jheim@math.wisc.edu \
--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).