* broke Speakup
@ Scott Howell
` Steve Holmes
0 siblings, 1 reply; 4+ messages in thread
From: Scott Howell @ UTC (permalink / raw)
To: speakup
Friends,
Well not sure what happen and exactly what broke what. I noticed that I
couldn't get ssh to let me into any machines on the network, notice I
couldn't get Speakfreely or any ftp client functioning, but I could ping
machines in and out of the network. So I assumed something got broken
when I did an dist-upgrade on my box; this is Debian Sid. In any case
after the upgrade things seemed ok so assumed all was well. These
problems showed up nearly 12 hours later. In any case I couldn't figure
out what the deal was and so recalled I needed ip multi-casting in the
kernel so went ahead and cooked a new kernel. That was the only option I
added in. So upon reboot I found the doubletalk external came up
chattering, but then I couldn't get it to shutup for nothing and then
the box just seem to hang after the buffer ran out of chatter.
I got the box up with the old kernel and all seemed back to normal.
The old kernel is 2.4.19 the new was 2.4.20. Now the 2.4.20 was working
yesterday so I wonder if compiling a new kernel caused a problem. I did
notice the symlinks for linux, asm, and scsi were no longer in
/usr/include, but instead actual directories were there. I don't know if
this matters, but I went ahead and removed them and pointed the symlinks
back to the kernel tree.
So, any thoughts? I'll report if I can get the new 2.4.20 kernel working
that I'm creating now.
tia,
Scott
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: broke Speakup
broke Speakup Scott Howell
@ ` Steve Holmes
` Ryan Mann
0 siblings, 1 reply; 4+ messages in thread
From: Steve Holmes @ UTC (permalink / raw)
To: speakup
I don't recall exactly when the deal changed but by default linux
untars directly into linux-2.4.20 (or whatever version it is). I then
use syn links for linux to point to the actual directory. Speakup 1.5
would patch into this perfectly. The new CVS checkout scripts can now
be run from with in /usr/src/linux-version. or from just about
anywhere else if the path is specified with the command line.
Somewhere between 2.4.18 and 20 this changed from the old linux top
level default.
HTH.
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: broke Speakup
` Steve Holmes
@ ` Ryan Mann
` Steve Holmes
0 siblings, 1 reply; 4+ messages in thread
From: Ryan Mann @ UTC (permalink / raw)
To: speakup
Instead of using symbolic links, can't you just rename
/usr/src/linux-2.4.20 to /usr/src/linux?
On Sat, 17 May 2003, Steve Holmes wrote:
> I don't recall exactly when the deal changed but by default linux
> untars directly into linux-2.4.20 (or whatever version it is). I then
> use syn links for linux to point to the actual directory. Speakup 1.5
> would patch into this perfectly. The new CVS checkout scripts can now
> be run from with in /usr/src/linux-version. or from just about
> anywhere else if the path is specified with the command line.
> Somewhere between 2.4.18 and 20 this changed from the old linux top
> level default.
>
> HTH.
> --
> Please avoid sending me Word or PowerPoint attachments.
> See http://www.fsf.org/philosophy/no-word-attachments.html
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: broke Speakup
` Ryan Mann
@ ` Steve Holmes
0 siblings, 0 replies; 4+ messages in thread
From: Steve Holmes @ UTC (permalink / raw)
To: speakup
I suppose you could but this way one could maintain several source
trees, if necessary and according to the README for the kernel you can
now configure and compile the kernel all as a normal user now and just
do the install as root. Of course, the normal user would have to have
write privileges to that directory. Yes you could do that with
/usr/src/linux likewise but...
I think one of the best reasons for the symlink is the multi version
kernel maintanence. I have, for example, two source trees; one with
2.4.20 patched with speakup-1.5 and the other I play with the CVS
versions. If the CVS version should go south or some such, I can
change the symlink to the old 1.5 tree and recompile and I'm back in
the saddle again.
On Sat, May 17, 2003 at 05:56:40PM -0500, Ryan Mann wrote:
> Instead of using symbolic links, can't you just rename
> /usr/src/linux-2.4.20 to /usr/src/linux?
>
>
> On Sat, 17 May 2003, Steve Holmes wrote:
>
> > I don't recall exactly when the deal changed but by default linux
> > untars directly into linux-2.4.20 (or whatever version it is). I then
> > use syn links for linux to point to the actual directory. Speakup 1.5
> > would patch into this perfectly. The new CVS checkout scripts can now
> > be run from with in /usr/src/linux-version. or from just about
> > anywhere else if the path is specified with the command line.
> > Somewhere between 2.4.18 and 20 this changed from the old linux top
> > level default.
> >
> > HTH.
> > --
> > Please avoid sending me Word or PowerPoint attachments.
> > See http://www.fsf.org/philosophy/no-word-attachments.html
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
broke Speakup Scott Howell
` Steve Holmes
` Ryan Mann
` Steve Holmes
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).