Hi!
> > > I don't like potential userspace breakage any more than the next guy,
> > > but if the breakage only affects buggy applications then I think it's
> > > more acceptable.
> >
> > Yes, it only breaks buggy applications.
>
> But we live in the real world. There could be four-year-old applications
> which passed all their Linux QA and which work perfectly well.
>
> Then the kernel guys make some correctness change and that application
> totally fails on new kernels. Your choice is a) don't use new kernels or
> b) hold off the new kernel until your provider (if the company or internal
> group still exists) has put out a new version of the application and then
> you wear the (considerable) cost of upgrading what was a perfectly-running
> application.
>
> And whose fault was it? Ours. Because older kernels had the wrong
> checking (thus causing that app's QA to pass) and because later kernels
> changed the rules.
Can we do printk now and fix it after a while in feature-removal?
Or maybe we shoul create new bug-removal file :-).
Pavel
--
Thanks, Sharp!
-
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]
