developmental kernels are not for the faint of heart, not saying that brian
is, but these kind of things is what comes.
you have to ask yourself, you want ppl spending their time redoing the config
when it isn't broken, or writing new drivers/fixing bugs?
-basit
Brian Gerst wrote:
> Thanks for using NetForward!
> http://www.netforward.com
> v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v^v
>
> Bob Lorenzini wrote:
> >
> > On Tue, 14 Apr 1998, Brian Gerst wrote:
> >
> > > I am getting damn tired of SMP=1 being the default. If you have a
> > > broken MP BIOS (Tyan Tomcat IV), it sees a phantom second cpu which it
> > > fails to start. THEN, it tries to access the IO-APIC, which doesn't
> > > exist on a K6, and completely crashes the machine. Somebody, please
> > > change this so that if there is not an Intel processor, regardless if
> > > the mobo is SMP capable, DO NOT enable the SMP extras.
> > >
> > > SMP kernels should work on all UP machines, not just Intels.
> >
> > I really HATE to repeat this but: If you want to run development kernels
> > you going to get by default what linus runs. If you don't like this I
> > guess you know what your options are. If not why don't you just diff the
> > config and patch.
> >
> > Bob
>
> I realise this, but it's a general pain in the ass because of where the
> SMP config is. In the Makefile it's out of sight and out of mind, only
> to be found out when you boot the new kernel, which promptly crashes.
> What's holding up moving CONFIG_SMP to the Config.in? Smart congfig
> should already be able to handle this.
>
> --
>
> Brian Gerst
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu