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:58:10 -0600	[thread overview]
Message-ID: <9694C2C0DC784726A006E1F6B7B268E3@LennyAcer5720> (raw)
In-Reply-To: <alpine.NEB.2.20.1603021104460.15230@panix1.panix.com>

Can that be done via SSH from another computer?
Installing the OS that is.
Glenn
----- Original Message ----- 
From: "Jude DaShiell" <jdashiel@panix.com>
To: "Speakup is a screen review system for Linux." 
<speakup@linux-speakup.org>
Sent: Wednesday, March 02, 2016 10:08 AM
Subject: Re: Installing Slackware Without Hardware Synthesizer


Download and use slackware_current as a base and basis point for this
work.  Slackware 14.1 doesn't even work with software speech and
slackware_current may have a more modern kernel or kernels for you to
use.  Another possibility may be you have to have generated a good
initrd file for any screen reader to work any more with slackware.  I
don't know that this is the case, but if so the speakup-install.txt and
speakup.txt files could certainly do with some updating.

On Wed, 2 Mar 2016, Haden Pike wrote:

> Date: Wed, 2 Mar 2016 10:38:52
> From: Haden Pike <haden.pike@gmail.com>
> Reply-To: Speakup is a screen review system for Linux.
>     <speakup@linux-speakup.org>
> To: Speakup is a screen review system for Linux. 
> <speakup@linux-speakup.org>
> Subject: Re: Installing Slackware Without Hardware Synthesizer
>
> Good idea. Any thoughts from others before I try this.
>
> Haden Pike
> Computer Science
> University of Kentucky
> Class of 2016
>
>
>
>> On Mar 2, 2016, at 9:45 AM, Cleverson Casarin Uliana <clcaul@gmail.com> 
>> wrote:
>>
>> Wouldn't it be possible to use a technique similar to that used to 
>> install Gentoo? You could enter into a distro already installed on your 
>> machine, then take the contents of the installation image and put each 
>> piece of software in its own place. More exactly, if you know a little of 
>> shell script, you could start reading the installer source code and 
>> manually reproduce what it does.
>>
>> Greetings,
>> Cleverson
>> _______________________________________________
>> 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
 Cleverson Casarin Uliana
 ` Haden Pike
   ` Jude DaShiell
     ` Glenn [this message]
       ` Jude DaShiell
   ` John G Heim
     ` Jude DaShiell
   ` John G Heim
     ` Gregory Nowak
       ` Haden Pike
         ` John G Heim
  -- strict thread matches above, loose matches on Subject: below --
 Mike Keithley
 Cleverson Casarin Uliana
 ` Rob
 ` Jude DaShiell
   ` Techswing33
 Haden Pike
 ` Jude DaShiell
   ` Haden Pike
 ` Kelly Prescott
   ` Haden Pike
     ` Glenn
       ` Jude DaShiell
         ` Gregory Nowak
       ` Gregory Nowak

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=9694C2C0DC784726A006E1F6B7B268E3@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).