If your scheduler was truly generic and could (even just theoretically) be plugged into many kernels, then you might be free from copyright obligations.
But being serious, writing a generic scheduler isn't practical. That would be like writing a generic "chapter 8" that can replace chapter 8 of not just Harry Potter but also many other too :-) Making a generic sound file is practical, because it's not so intimately tied in, so as I said in my initial examples, a generic sound file could be inserted into the/any kernel without becoming GPL'd. But a scheduler, excluding toy proof-of-whacky-concept projects, no. Speaking of copyright and Harry Potter: http://stallman.org/harry-potter.html -- Ciarán O'Riordan, +32 477 36 44 19, http://ciaran.compsoc.com/ Support free software, join FSFE's Fellowship: http://fsfe.org Recent blog entries: http://fsfe.org/fellows/ciaran/ciaran_s_free_software_notes/links_gnu_osm_gnewsense_bangalore http://fsfe.org/fellows/ciaran/ciaran_s_free_software_notes/japanese_pdfs_part_2_xetex http://fsfe.org/fellows/ciaran/ciaran_s_free_software_notes/links_translation_bsod_orwell_releases http://fsfe.org/fellows/ciaran/ciaran_s_free_software_notes/fsfe_meeting_tonight_in_brussels_thurs_7th _______________________________________________ gnu-misc-discuss mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-misc-discuss
