flush and buffering updates -- please test.

[luke]

On Wed, 25 Jun 2008, William Hubbs wrote:

> On Wed, Jun 25, 2008 at 04:07:57AM -0400, luke wrote:
> > Something else: double review keys (numpad 5 numpad 5, for example, to 
> > spell a word) stop working all together.
>  
>  I just tested these here and they still work fine on my system.  When
>  they stop working?

They never start working in current git version.

Lot more problems as well, now that I am testing with 2.6.24.7:

* If I type:

cd /sys/mod

and hit tab for the completion, I hear nothing, even though the word 
"modules" completes.

* Same if I type "spe" tab, to get "speakup" after that.

* Shell prompts are spoken if I press enter, and the results of echo are 
spoken ("echo this is a test." has "this is a test" spoken).
However, if in, for example, /sys/module/speakup, and I type "ls" enter, 
where I should here "parameter/", I hear nothing, not even the shell 
prompt.

* Random seeming other commands behave the same way.  If I type "sudo 
bash" to get a root bash, I hear nothing spoken, even though review read 
current line, after a suitable half second delay, will read "root at thor:~#" 
as it is supposed to have done before.  Typing "exit" from there, will 
return me to "luked at thor:~#", which is read.

* Running "less /var/log/kern.log" gets me no output, except in review.

* Testing with 2.6.24.7, now all key echo has the same delay as only 
review keys had on 2.6.18 with current git speakup.

> > I should note that I am testing with 2.6.18.  If you think it is relevant 
> > for me to test with a later version, I will, but currently later versions 
> > break loopmount encryption on my system, which is not acceptable for 
> > anything other than testing, so I haven't been using them.
> 
> Yes, it would be helpful for you to test with a current kernel to see if
> these issues still happen for you.

Have done (2.6.24.7), and not only do they still happen, they are worse.

I will send you and Samuel, off list, a tar file containing a bunch of 
data: a kern.log sample, the kernel config, the contents of the speakup 
parameter directory while this is all happening, etc.

> I have never used loop mount encryption, so I'm not sure how that works.
> Can you explain what you are using that for?  Also, is there not
> something in current kernels that provides the same functionality?

Similar to the way in which one can loop mount an iso file, one can use, 
for example, the "cryptmount" package, to create encrypted files, which 
can be mounted as normal loop file systems, and accessed on the fly, 
remaining encrypted for all storage.  I believe it uses the md_crypto 
module, which wasn't compiling properly for me in 2.6.24.7.

That is probably a kernel config issue.

I am going to try the pre-flush-changes version of speakup with 2.6.24.7 
using the same config, and see what my results are.

Luke