-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've never seen that as you describe below. I thought CVS was completely down like bumpy is currently. When CVS is up and running, It has always worked OK for me unless they left a buggy in there:). On Sun, Feb 06, 2005 at 08:58:47AM -0600, Stephen Clower wrote: > Hello Steve, > > Yes, for some reason the CVS downloads are continuously trying to access Linux 2.4.28 instead of the traditional symlink to /usr/src/linux. Were these files modified in some way that they could only be applied to a specific kernel? > > As a side note, I downloaded 2.4.28 just for kicks and the patch still failed. > > On Sunday, February 6, 2005, 8:32:03 AM, you stood on a roof and loudly proclaimed: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > This does bring up a slightly different angle on this question. Is > > there a simple way to isolate the speakup patches and hand apply them > > to my newest kernel of choice? I recall trying something like this a > > ways back unsuccessfully. The resulting download from CVS is > > apparently not exactly like the tarball that gets built about every 3 > > years <sigh>. I guess another question might be: how can we build our > > own tarballs of speakup that we might be able to apply at any time CVS > > is unavailable like now? > > > On Fri, Feb 04, 2005 at 08:14:03PM -0700, Joseph C. Lininger wrote: > >> Hello, > >> I would be happy to send you a 2.6.10 kernel tree with speakup patches > >> as well as other patches that I use on my system. Most of them come > >> from the gentoo-dev-sources package from Gentoo Linux, but there are > >> a couple that I have applied by hand like grsecurity. Let me know if > >> you're interested. > >> > >> -- > >> Profanity is the language all programmers know best. > >> Joseph C. Lininger > >> jbahm at pcdesk.net > >> Verification: 5eab38a77ac40416e075be8f50607ff7 > >> > >> On Thu, 3 Feb 2005, Stephen Clower wrote: > >> > >> >Hello folks, > >> > > >> > Normally I wouldn't be asking this question, but since Linux-Speakup > >> > appears to be down indefinitely I could use some pointers. I am > >> > running Slackware 10.0 with the Speakup enabled 2.4.26 kernel compiled > >> > by Joseph C. Lininger. Currently, there is no software synth support > >> > in the kernel, so I figured that if I'm going to recompile the kernel, > >> > I might as well upgrade to 2.6.7 for the sake of being up-to-date. > >> > > >> > Normally I would download the kernel sources from kernel.org and run > >> > the Speakup CVS checkout script, but for obvious reasons this won't > >> > work. Consequently, I've decided to download the 2.6.7 kernel source > >> > package from a Slackware 10.0 mirror along with the Speakup-2.4.26 > >> > folder from the sources directory. Will I still be able to patch the > >> > 2.6.7 kernel with the Speakup source, or will there be something else > >> > I need to do? > >> >Thanks, > >> >Steve > >> > > >> > > >> > > >> >---------- > >> >Stephen Clower > >> >Email/.Net Messenger: steve at steve-audio.net > >> >AIM: AudioRabbit03 > >> >Skype: sclower > >> > > >> >Check out my little home on the web at http://www.steve-audio.net > >> > > >> > > >> >_______________________________________________ > >> >Speakup mailing list > >> >Speakup at braille.uwo.ca > >> >http://speech.braille.uwo.ca/mailman/listinfo/speakup > >> > > >> > >> _______________________________________________ > >> Speakup mailing list > >> Speakup at braille.uwo.ca > >> http://speech.braille.uwo.ca/mailman/listinfo/speakup > >> > >> > > > > ---------- > Stephen Clower > Email/.Net Messenger: steve at steve-audio.net > AIM: AudioRabbit03 > Skype: sclower > > Check out my little home on the web at http://www.steve-audio.net > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFCBmXOWSjv55S0LfERAojTAJ92wheMy8exuVs1k3J0wylGOs1jUwCg8feb TRvZIIxCNyj0FUSxeZ5aPRk= =J4gP -----END PGP SIGNATURE-----
