On Thu, 22 Feb 2001, Andrew T Chan wrote:

> After all a true bleeding edge Linux user (as in people that rush to the
> latest kernel just for the heck of it) should be able to do everything
> needed in Linux. Rushing to the latest kernel will probably give you a lot
> of problem on other legacy software, even if Win4Lin has a perfect version
> you will still need a bit of work to get everything else working.
> 
   Who's rushing to 2.4 just because it's there??  I'm not - I learned my
lesson about new kernels back around 1.3.60 somewhere, when a bug caused most
of my filesystems to become corrupted beyond repair.  Now, yeah, it wasn't as
mature a kernel as 2.4, but lesson learned nonetheless.  But I think it's
really obnoxious and obtuse to assume that no one "needs" 2.4 for what they
do, or that the people who "need" 2.4 don't "need" Win4Lin.  Once I figured
out how to patch USB and Win4Lin into a 2.2 kernel, I was actually up and
running quite contently for some time - but when it came down to having
DRI/GLX for my new video card and sticking to Win4Lin, Win4Lin lost out and I
haven't been able to use it since.  Of course, I was never able to get VPN
working in Win4Lin either, so I guess it's just as well.

   On a brighter note, I think it's nice that Netraverse is at least -talking-
about 2.4 now...  even if my shiny Win4Lin CD is stuck being just a coffee
coaster for a while.

> I am running 2.2.x and 2.4 on different machines, in general both give a
> standard (not the most sophisticated) user more than 90% of what they
> need. As a user I rather see stable product as time is precious, a
> bleeding edge user should probably not bother with anything associated
> with Windows.
> 
   You're overgeneralizing.  You don't have a clue what I, or anyone else,
needs Linux 2.4 or Win4Lin for.

---GEC
Projects page: http://tetsujin.sourceforge.net/
(M-x all-hail-emacs)

_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users

Reply via email to