Mailinglist Archive: opensuse (5100 mails)

["Matt T." <Matt@xxxxxxxxx>]

On Tuesday 08 June 2004 16:00, Basil Chupin wrote:
> Matt T. wrote:
> > OK, I understood that netraverse is not making dist-specific kernels
> > anymore, so there is no win4lin kernel for suse 9.1. Instead netraverse
> > says to use the generic 2.6.x kernel they provide. I read also some
> > reports that it would work fine.
> >
> > My question now is: What will not work anymore / what will I be missing
> > if I replace my SuSE kernel with the win4lin generic 2.6.x kernel?
> >
> > I can't imagine that SuSE does all that work to customize the kernel and
> > then it will be the same to use the generic one.
> >
> >
> > And then the next question is if it works fine to install both kernels,
> > using grub to boot the one or the other, depending if I need to run one
> > of these old legacy windose apps... if yes, is there a kernel 2.6
> > specific howto somewhere?
>
> The point here is: if it becomes necessary to boot with a second linux
> kernel in order to be able to use Win4Lin then Win4Lin have shot
> themselves in the foot because it is much easier to simply boot into a
> system running Windows. Right?
>

That's what I'm trying to understand. According to Netraverse it is no problem 
to use their kernel, but they recommend to use a distribution which has their 
kernel already build in. I understand that it is much better to have the 
win4lin hooks already build in the kernel by the distribution, instead of 
having the user installing a new kernel to be able to use win4lin. But how 
about the users of SuSE and other distributions without pre-build in win4lin 
hooks?

I hope that using the generic win4lin 2.6.x  kernel does not cause too many 
annoyances. Otherwise Netraverse did a bad move, indeed. 

Or, just wait another year, and wine / crossover is there, or gimp, quanta 
etc... ;-)  there is not much missing anymore!