Jens Benecke writes:
> > So my question is: what is the easiest way to get win4lin on a desktop?
> > and my answer is: dump the distro kernel, use the kernel.org kernel.
>
> No.
>
> Guess what happens when SuSE 7.2 comes out and formats your disk
> with ReiserFS by default and the kernel.org kernel doesn't include
> the same versions of the ReiserFS tools. Or if you need a BigMEM
> patch or whatever and install win4lin.
>
> Providing ready-made kernels for the popular distros is necessary
> (and I still want a Debian kernel! ;), and whoever uses kernel.org
> kernels
Building a kernel under debian is pretty easy, using the make-kpkg
appp. It could be a bit easier, but not much.
> > Most of the distro kernel mods are for things like file systems (raid and
> > reiserfs) or multimedia stuff, neither of which I need on a production
> > workstation.
>
> Well, how do you know what other people need? I for one *NEED* USB
> and ReiserFS support, which isn't in any 2.2.x kernel by default.
Back to make-kpkg, it will apply the patches that it finds, providing
you put the patches in the right directory and tell it to use them.
from the man page:
--added_patches foo
The argument should be a comma or space separated
list of additional patches to the kernel sources.
This requires the patch_the_kernel configuration
option to be set to YES. Unlike the treatment of
the modules, you may only give the patch name (not
the full path name of the patch file). It shall be
applied during the configure phase (and removed in
the clean phase) if it can be found in the directo-
ries ALL_PATCH_DIR/{apply,unpatch}/, which defaults
to a subdirectory of /usr/src/kernel-patches/. The
default is that all patches are applied if
requested (By setting the env variable
PATCH_THE_KERNEL to YES).
> > I still keep all of the RH niceties, without the sometimes funky behavior
> > of patched kernels. After RH's glibc fiasco, I'm not sure I'd trust one
> > of their kernels anyway ;-)
>
> Well, I've been using Debian's standard kernel for over a year
> (before I needed ReiserFS), and everything worked fine.
and you could still create a kernel using the debian tools, then your
kernel/source/headers/pcmcia/alsa would all be .debs, and you would
also be able to put it on hold so that no new debian packages would
overwrite those packages.
rob
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
