public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Glenn" <glennervin@cableone.net>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: Installing Slackware Without Hardware Synthesizer
Date: Wed, 2 Mar 2016 20:09:54 -0600	[thread overview]
Message-ID: <B15B952BFB964C3AA5C5B32213E6C1B2@LennyAcer5720> (raw)
In-Reply-To: <7C3630FF-F2DE-46AF-9D92-E402671A6E43@gmail.com>

There used to be a slackware for DOS that I had for my first Linux 
experience.
It installed on FAT32.
Whatever happened to that project?
Glenn
----- Original Message ----- 
From: "Haden Pike" <haden.pike@gmail.com>
To: "Speakup is a screen review system for Linux." 
<speakup@linux-speakup.org>
Sent: Tuesday, March 01, 2016 10:40 AM
Subject: Re: Installing Slackware Without Hardware Synthesizer


I already have a TalkingArch install on one of my machines here. I was going 
to install Slackware in a virtual machine, because it’s not a distribution I’ve 
used before.

Haden Pike
Computer Science
University of Kentucky
Class of 2016



> On Mar 1, 2016, at 12:56 AM, Kelly Prescott <kprescott@coolip.net> wrote:
>
> Haden, If you just want Linux and do not specifically need slackware, try 
> TalkingArch Linux.
> http://talkingarch.tk
> It talks from the start, and while there is a bit of a curve to learn it, 
> you can not only do the install yourself, but you can learn a great deal 
> about Linux in the process.
> Let me know if you have any questions about it.
>
> -- Kelly Prescott
>
>
>
>
> -----Original Message-----
> From: Speakup [mailto:speakup-bounces@linux-speakup.org] On Behalf Of 
> Haden Pike
> Sent: Monday, February 29, 2016 6:32 PM
> To: speakup@linux-speakup.org
> Subject: Installing Slackware Without Hardware Synthesizer
>
> Hi all,
>
> I do not have a hardware synthesizer. Do I have any other options for 
> performing an install of Slackware that do not involve me finding a 
> sighted person to install it for me?
>
> Thanks,
> Haden Pike
> Computer Science
> University of Kentucky
> Class of 2016
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup


  reply	other threads:[~ UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Haden Pike
 ` Jude DaShiell
   ` Haden Pike
 ` Kelly Prescott
   ` Haden Pike
     ` Glenn [this message]
       ` Jude DaShiell
         ` Gregory Nowak
       ` Gregory Nowak
 Cleverson Casarin Uliana
 ` Haden Pike
   ` Jude DaShiell
     ` Glenn
       ` Jude DaShiell
   ` John G Heim
     ` Jude DaShiell
   ` John G Heim
     ` Gregory Nowak
       ` Haden Pike
         ` John G Heim
 Cleverson Casarin Uliana
 ` Rob
 ` Jude DaShiell
   ` Techswing33
 Mike Keithley

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=B15B952BFB964C3AA5C5B32213E6C1B2@LennyAcer5720 \
    --to=glennervin@cableone.net \
    --cc=speakup@linux-speakup.org \
    /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).