tech-toolchain archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

proposal to remove backward compatibility



[Changing the subject because this issue is too important to be hidden
under an inappropriate subject line.]

On Fri, 15 Aug 2008, der Mouse wrote:
> > We simply need to make the decision, and from that point forward, no
> > more need for new compat code in the kernel.
> 
> No more ability to upgrade the kernel while running the previous
> userland?
> 
> I would consider that a crippling regression.

Me too.  My usual upgrade process involves:

   1) build new versions of everything;
   2) place a new kernel somewhere that the boot loader can find it,
      without interfering with the ability to boot an old kernel;
   3) boot new kernel with old userland;
      - if it fails, go back to old kernel;
   4) install new userland;
   5) boot new kernel with new userland.

Now, in between steps 2 and 4, I have the ability to boot either an old
or a new kernel.  If I had also installed a new libc in step 2, then I
would lose the ability to run the "old" system, because even with an old
kernel, I would get a new libc (which might not even work with the old
kernel).

--apb (Alan Barrett)


Home | Main Index | Thread Index | Old Index