Sure this is possible; but I won't be the one providing you support on how to do it <smile> Note the following points: Some of the documentation inside the speakup repository seems slightly out of date, I need to look at this more closely before I make this acersion with confidence. If you are managing your kernels yourself and not building them with kernel-package then you'll have to look after your boot loader, kernel image, modules tree and initrd image if you use it. If you use kernel-package and module-assistant then you can let the system manage the boot loader configuration (easy with grub, doable to a point with lilo it tracks vmlinuz and vmlinuz.old) and it'll handle the initrd image. If you are compiling a kernel that is not debian blessed, you'll have to insure that the compiler is using the right set of headers, i.e. the ones for your compiled kernel and speakup must link against these also. This will happen automatically if you compile from source if you succeed in patching speakup into the source tree, however after you reboot you need to insure that /lib/modules/kernelversion/build points to the include path of your kernel source tree. This usually involves keeping your kernel source around until you have compiled any and all out of tree kernel module packages. These would include a newer alsa if you want one, and other out of tree modules. I must say i'm mystified as to why most people seem to want to "get rid of" the distribution kernel; fearing that it is bloated and overloaded. Usually the initrd takes care of only loading modules you need for your hardware. Of course if you are compiling your own and you know what you are doing; then all this talk of include paths, configuration of boot loaders and similar should all be known ground. If it isn't; then perhaps a user should start by compiling out of tree kernel modules and work up from there. The following is directed at no particular person: If everyone documented what they did as they did it and submitted it to the site then we wouldn't have these problems to anywhere this degree. That said, often people are alergic to documentation, i've noticed this from my years of teaching. We have what we call the silver service brigade that seem to want every step and procedure handed to them on a silver platter. I conceed however there has to be a happy medium between no documentation and insert slot a into tab b documentation for every distribution of Linux. Personally; i'm part of the problem; as I allready have my speakup working the way I want, and with 15 years Linux experience this is not a problem for me. I've built my out of tree modules; and they work well enough for my purposes. If people want speakup included in distributions then they're going to have to work on it themselves or find someone to do the work for them (possibly greasing the wheels with financial contributions). Samuel does Debian and so do other people, Bill and Janina do an excellent job on Fedora, and apologies to others who did not make it onto this list. Bundling speakup in the default kernel is certainly potentially disruptive and causes more maintainance for the distribution maintainers. Just my 2 cents worth. Regards, Kerry. ----- Original Message ----- From: "Nick Gawronski" <nick@xxxxxxxxxxxxxxxxx> To: "Speakup is a screen review system for Linux." <speakup at braille.uwo.ca> Sent: Thursday, January 08, 2009 11:26 AM Subject: Re: Trouble Compiling modules/kernel Hi, As I am building my own kernel and have read the installation file is it still possible to just compile speakup and dectalk express driver in the kernel if I don't plan on giving away the kernel? It says in Installation that this can be done but I wonder how updated that file is. This way I could get rid of the kernels that debian produces and manage them on my own. ----- Original Message ----- From: "Kerry Hoath" <kerry@xxxxxxxxx> To: "Speakup is a screen review system for Linux." <speakup at braille.uwo.ca> Sent: Wednesday, January 07, 2009 6:43 PM Subject: Re: Trouble Compiling modules/kernel You'd have to build your modules with module-assistant and your kernel with kernel-package. This will build a .deb for your kernel and a headers package you can install. Alternatively you are managing the symbolic links for the include directories yourself and this gets tricky. I run the pre-compiled distribution kernels with the bundled initrds as I see no problem with the prebuilt kernels and modules outside the kernel tree cause me no problem. Someone else will have to sit down and document how to use an out of distribution kernel. I posted a guide to what I did to build the modules in late december, this will be in the list archives. The url for the list archives is in every message posted to this list in the headers. go take a look. the article you seak will be posted in late december from Kerry Hoath or use google. Regards, Kerry. ----- Original Message ----- From: "Nick Gawronski" <nick@xxxxxxxxxxxxxxxxx> To: "Kerry Hoath" <kerry at gotss.net> Sent: Thursday, January 08, 2009 9:16 AM Subject: Re: Trouble Compiling modules/kernel Hi, well the best way to do this would just be to remove all old information that is no longer usable and update it with the new git information and get rid of the cvs stuff. If I have a kernel source tar archive from kernel.org and want to use it with debian where can I put the sources where the speakup git modules will see them? ----- Original Message ----- From: "Kerry Hoath" <kerry@xxxxxxxxx> To: "Nick Gawronski" <nick at nickgawronski.com>; "Speakup is a screen review system for Linux." <speakup at braille.uwo.ca> Sent: Wednesday, January 07, 2009 5:57 PM Subject: Re: Trouble Compiling modules/kernel > cd /a/path/to/store/the/source > git clone http://linux-speakup.org/speakup.git > > cd speakup/src > make modules > make modules_install > > you'll need kernel and kernel-headers for your current running kernel > installed for this to work. > > Perhaps if someone was to mark up the instructions in html and submit them > to Kirk the website would get updated? > Regards, Kerry. > > ----- Original Message ----- > From: "Nick Gawronski" <nick at nickgawronski.com> > To: "Speakup is a screen review system for Linux." > <speakup at braille.uwo.ca> > Sent: Thursday, January 08, 2009 8:28 AM > Subject: Re: Trouble Compiling modules/kernel > > > Hi, I totally agree. No wonder lots of distributions don't have speakup > if > the information on the linux speakup site was updated then probably > speakup > could be back in versions of linux that it was in before and even more > versions that never had it. Can you quickly give me instructions on > getting > the git version I have debian and have already done apt-get install > git-core > so have git installed on my system. Why is the cvs version even still on > the site if it is no longer being maintained? > ----- Original Message ----- > From: "Samuel Thibault" <samuel.thibault at ens-lyon.org> > To: "Speakup is a screen review system for Linux." > <speakup at braille.uwo.ca> > Sent: Wednesday, January 07, 2009 5:23 PM > Subject: Re: Trouble Compiling modules/kernel > > > Zachary Kline, le Wed 07 Jan 2009 12:35:01 -0800, a ?crit : >> There are many detailed sets of instructions in the list archives on >> how to do this. > > Could these find their way to http://linux-speakup.org ? It's a problem > that information there is mostly outdated. > > Samuel > _______________________________________________ > 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 > _______________________________________________ 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
