On Sunday 31 August 2003 12:22 pm, Buchan Milne wrote: > On Sun, 31 Aug 2003, Greg Meyer wrote: > > > > > BTW, is there interest in having win4lin kernels in contrib? They would > > > > be small (~60k SRPM, ~1.2MB per win4lin-kernel package), and just > > > > require the kernel from main. > > > > > > I really don't care one way or the other. Usually I'm running kernels of > > > my own, FWIW... > > > > > Why? Netraverse is very good about making a win4lin enabled kernel available > > for every officially released Mandrake kernel, and they usually make it > > available within days of the release. > > Well, then we could have better integration (the win4lin-supplied kernel > RPMS only allow one win4lin kernel, whereas my packages on Club > allow up,smp,enterprise and multiple versions to co-exist), and why should > people who buy Powerpack/ProSuite have to download win4lin kernels, would > it not be more convenient to have them on the CDs? > > Also, it seems at least a few people here run win4lin on cooker, it might > save us all some time to have one package, than to all be building our own > kernels (and doing the patching, which often takes longer). > > Oh, my win4lin-utils package also provides menu entries for Win4lin (in > menu format, so they work when you use Mandake's menus). > You make some valid points. What would be the harm in just adding the win4lin support to the official kernel? Does it hurt anything if win4lin is nevr installed? That solves all the problems.
-- /g "Outside of a dog, a man's best friend is a book, inside a dog it's too dark to read" -Groucho Marx
