In addition, there are problems with several types of SCSI tape drives,
which hang up and cannot be reset by anything short of a reboot. The
problem is said to be in st.c, but that's all I know. The point is that
this is another facility that worked fine in earlier kernels, and is now
seriously broken.
Finally, there are still some oddities in the xconfig menus, like having
the QIC-02 tape driver and watchdog timer support items show up under
"Mice".
I don't know about Linus, but I would be embarrassed to release a kernel
with that many formerly-working things broken in it. If I were a
Microsoft publicist, I would be rubbing my hands in anticipation of the
excellent FUD fodder in the new Linux kernel. New features and new
devices are one thing, but breaking stuff that used to
work--particularly if it prevents systems from booting, like the
aic7xxx-DC20246 conflict does--should be an absolute no-no.
How about having a *real* code freeze, as in: the only fixes allowed are
those that deal with disabling problems in subsystems that worked
properly in 2.0.xx? Things like swapper optimizations and fixes to
platforms and devices that were not supported previously don't qualify.
-Randy
-- http://www.cnbc.cmu.edu/~gobbel/ PGP fingerprint: 32 8A E8 24 A1 46 26 BC F9 9D 0E B6 81 A9 02 0CNOTICE: I DO NOT ACCEPT UNSOLICITED COMMERCIAL EMAIL MESSAGES OF ANY KIND.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/