I thin this exists in both -STABLE and -CURRENT, but I don't have a
bang up to date instalation of either, so appologies if it has been
fixed.
Tested on 5.2.1 and 4.8. may have some security implications in that
someone may think they have changed a shell (eg to /nonexistant) but
they haven't rea
> > A fix to somethign deep in ther kernel which is not
> > biteing many people?
> This is something for the commiters to decide and not me.
Indeed. Isn't the point of this thread, if any, that Marc Fournier was
complaining that a patch to the VM system was not put onto the RELEASE
branch. As y
> I think the answer is obviously, long time testing and monitoring.
> But you can have a -STABLE that is reliable and *critical* patches are
> applied quickly. I believe that this is what mostly this thread is about.
I refer the honourable gentleman to his above comment `long time
testing and mo
> I think the best thing is to keep things as simple as possible.
But no simpler.
> I personally think that a fix should always be a fix
that is like saying a cure for cancer should be a cure for
cancer. Fine. How do you know it is a cure and how do you know what
the side effects will be.
If l
