> In effect (mainline) no. Linux 2.2 and 2.0 won't be fixed for the same
> reason; called deep maintenance. 2.6 has been on the road since Dec 2003,
> that's over 2 years. Do away with the old stuff.
we are in the process of switching, which is not unproblematic. on
the other hand, we have to support existing installations as well.
by the way ... "switching is not unproblematic": I just had to examine
a notebook which had problems with our software: a
"toshiba portege m400". 2.4 seems to work so far, as does 2.6.16.
I also tried 2.6.17, but get a strange problem: it simply hangs
after writing "PCI: probing hardware" (or similar). A closer look
reveals that it hangs in drivers/pci/probe.c, in pci_read_bases. What's
exactly going on, I don't know...
this shows that sometimes the old stuff works better than the new
stuff ;-)
kind regards,
h.rosmanith
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
