Sorry, not being clear again. By a sacrificial box, I mean a box that if the kernel or a driver explodes and crashes the box nothing important is lost. Also, since the kernel may crash while testing, hardware that is somewhat resilient to destruction due to system crashes that require cold reboots would be desirable. I run the 2.6 kernel also and find it to be plenty stable. I only meant that since the book I'm reading is specific to 2.6 driver develpoment I want to build a box on which to develop and want to build one that can I can sacrifice the files on and can take the punishment of frequent crashing, hence "sacrificial". Brian D. --- Tom Bruno <crweb@vwords.com> wrote:
I personally don't find running kernel 2.6 to be "sacrificial". I find it quite a bit nicer than 2.4. Especially on multi-cpu machines.
Jack wrote:
It's awfully quiet out there. Is the list still up? Am I still subscribed?
Well, let's find out. Is anyone running a sacrificial Linux box for testing such things as kernel patches, contributions or drivers? I'm going to set one up for a 2.6 debian box, so I can follow along with this book on Linux device drivers. So I'm looking for some ideas for what to load into this box on a hardware level and ask anyone if they have a particular device that needs to be written for or improved on. My budget is limited as I am still doing the Mr. Mom bit.
Brian D.
__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
_______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
__________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/