I've liked debian for awhile, but tons of stuff won't compile, because the locations of files are a little screwy. Why put stuff in non standard places I don't know. How does one configure a redhat kernel when compiling anyways? I'm thinking about using it some time, suppose I need the 3c59x driver support for networking, can I config it like a normal kernel or does redhat have tools to make this easier? At 11:24 PM 9/22/00 -0400, you wrote: >Hi > It is possible to build a speakup kernel from the Red Hat source >RPM. Just skip the patches that can't find their files, they don't apply >to the i386. > However, the kernel will build, but unless you use a rh supplied >config, your modules will have unresolved symbols all over the place. I >don't think speakup agrees with some of the patches RH applied to their >kernel rpm, for it is not a clean source. They've applied all sorts of >stuff that are beta, or even alpha. Not wise, I believe they do it to try >to get their distro to support more hardware. > Personally, I think slackware is the best, closely followed by >debian. > >On Fri, 22 Sep 2000, Kirk Wood wrote: > >> I believe this is a kernel problem. Once the kernel starts expanding (you >> get the loading and the dots, then the kernel quickly takes over. My guess >> is that you used the kernell source provided by RedHat. If you did, then >> you should download the kernel (possibly from kernel.org) and apply the >> patch compile, etc.) RedHat doesn't provide the complete kernel and as a >> result the built images don't work correct. Sorry I can't give you more >> complete details. Just that it is common to discover you can't build a >> working kernel with speakup from the RedHat source package. >> > > >_______________________________________________ >Speakup mailing list >Speakup at braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >
