From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from server1.shellworld.net (shellworld.net [69.60.117.94]) by befuddled.reisers.ca (Postfix) with ESMTP id F33561EF6B4 for ; Wed, 8 May 2013 13:51:10 -0400 (EDT) Received: from server1.shellworld.net (localhost [127.0.0.1]) by server1.shellworld.net (Postfix) with ESMTP id 3F9792297A for ; Wed, 8 May 2013 13:51:10 -0400 (EDT) To: "Speakup is a screen review system for Linux." Subject: Re: the direction of speakup MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24780.1368035470.1@server1.shellworld.net> Date: Wed, 08 May 2013 12:51:10 -0500 From: "Martin G. McCormick" Message-Id: <20130508175110.3F9792297A@server1.shellworld.net> X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2013 17:51:11 -0000 The initrd idea for speakup is a great one because it should do what you discribe. It might even be possible to build enough of a kernel in initrd to support a thumb drive that could augment memory storage for systems that have less than 512 megabytes of RAM. I have a couple of those myself that are still otherwise good systems but don't have a lot of spare RAM. If speakup could be put in to initrd, it might also have a home in embedded systems which opens up a whole world of possibilities. Martin Devon Stewart writes: > I guess including Speakup in the initrd would solve this? Modules that > are loaded in the initrd are maintained when booting the rest of the > system, as far as I know, so once speakup is started everything should > speak from boot.