Roman, Thanks for the reply. I was thinking more in terms of anyone bound by the requirement to keep the 'Enterprise'ness that enjoy higher stability, well tested distros (RHEL/CentOS, SUSE, etc) compared to plain kernels + Run Click router on top. For instance, when I upgrade CentOS 5.3 (based on 2.6.18) to a higher kernel version (without waiting for, say, CentOS 6), I forgo a number of wider cherry-picked inter dependent fixes that RedHat had found and fixed. My new kernel-upgraded CentOS box is now suddenly not enterprise ready anymore and various drivers (modules and built-in) are now normalized to the new higher kernel version nullifying RH's changes. This may not be a big impact on PCs as much as on high end server boxes Dell, HP, etc make. Excuse me if I have been too wordy above for known facts. Just wanted to be unambiguous.
Thanks again. Best Regards, Rajaram ----- Original Message ---- From: Roman Chertov <[email protected]> To: Raj Sidh <[email protected]> Cc: Click <[email protected]> Sent: Thursday, October 1, 2009 7:21:28 PM Subject: Re: [Click] kernel patches for non-vannilla kenels Rajaram, Typically, people just upgrade the kernel on their distro of choice. I used to run a CentOS based lab, and I just upgraded the kernel to a vanilla one that was Click compatible. Roman Raj Sidh wrote: > Hi, > > What is the process within the Click project/community to contribute working > click patches for non-vanilla kernels? Like centos, etc. Also is/will there > be any need for such patches on such enterprise distros, given that Click > repository already has patch archives for most of the later kernels. Thank > you. > > Best Regards, > Rajaram > > > > > _______________________________________________ > click mailing list > [email protected] > https://amsterdam.lcs.mit.edu/mailman/listinfo/click > _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
