Patrick Mauritz wrote: > > On Fri, Jun 29, 2001 at 08:17:25AM -0500, Brent D. Norris wrote: > > Instead of forking the kernel or catering only to one group, instead why > > not try this: Using the new CML2 tools and rulesets, make it possible to > > have the kernel configured for the type of job it will be doing? Just > > like CML2 asks our CPU type (i386, alpha, althon ...) and then goes out > > and configures options for that, have it ask people "Is your machine a > > server, workstation, embedded/handheld?" and configure things in the > > kernel like the VM, bootup and others to optimize it for that job type? > that could be the "easy == end-user" setup > why can't there be two (possibly similar but tweaked) VMs (and other stuff as well) > be in the source so everyone has to choose exactly one for his kernel? > there are patches for plug-able TCP/IP stacks. filesystems are already plug-able (someone need journaling, some one needs quoatas, some needs nothing). there are patches for plug-able task scheduler. If I could choose what filesystem to run on / - it impact performance greatly - why can't I choose how my tasks are scheduled? how my packets are going to NIC? IMHO great idea. I think this will improve portability. And embeded guys will be in permanent satisfaction ;-) But I'm afraid this won't happen in 2.5 - this kind of change require well defined and stable internal interfaces. So this is really huge amount of work. This would be one little step toward the microkernel architecture (like Hurd). Good again :-)
begin:vcard n:Filiapau;Ihar tel;pager:+375 (0) 17 2850000#6683 tel;fax:+375 (0) 17 2841537 tel;home:+375 (0) 17 2118441 tel;work:+375 (0) 17 2841371 x-mozilla-html:TRUE url:www.iph.to org:Enformatica Ltd.;Linux Developement Department adr:;;Kalinine str. 19-18;Minsk;BY;220012;Belarus version:2.1 email;internet:[EMAIL PROTECTED] title:Software Developer note:(none) x-mozilla-cpt:;18368 fn:Philips end:vcard