"Kevin Cheng" <[EMAIL PROTECTED]> writes: > Hi Darrin, > > Thanks for reply. > > The reason is that we have bunch of files integrated with 4.0 and it would > take us months to upgrade to 4.2 again. we just finished from 3.3 to 4.0 of > upgrade few months ago, plus months of test to stabilize our 4.0 based > applications. > > Should we just isolate one by one manually as safety approach? Any CVS that > we can trace for what files been changed for specific drivers? E.g., > 4.0->4.1.
this is such a bad idea. >From experience I can tell you that it's much easier (in total) to upgrade your code once every 6 months than to do huge projects to do the same once every few years. //art > Thanks, > > Kevin > > > > > > -----Original Message----- > > From: Darrin Chandler [mailto:[EMAIL PROTECTED] > > Sent: Monday, August 27, 2007 2:19 AM > > To: Kevin Cheng > > Cc: misc@openbsd.org > > Subject: Re: Backport drivers from 4.1 to 4.0 > > > > On Mon, Aug 27, 2007 at 01:33:34AM +0800, Kevin Cheng wrote: > > > What would be the safe way to backport driver codes from > > 4.1 to 4.0, such as > > > (/usr/src/sys/dev) ci, pcmcia, usb? > > > > For most values of "safe" the answer is none. > > > > With the upcoming 4.2 release, 4.0 will be unsupported. Your backports > > will be unsupported immediately. Is there some pressing reason why you > > can't upgrade/reinstall to a newer version? > > > > -- > > Darrin Chandler | Phoenix BSD User Group | MetaBUG > > [EMAIL PROTECTED] | http://phxbug.org/ | > > http://metabug.org/ > > http://www.stilyagin.com/ | Daemons in the Desert | > > Global BUG Federation
