Re: "stable" vs "security stable"

Valdis.Kletnieks_at_vt.edu
Date: 10/09/05

  • Next message: Stefan Lucke: "touchkit PS/2 touchscreen driver" 
    To: Coywolf Qi Hunt <coywolf@gmail.com>
Date:	Sun, 09 Oct 2005 03:14:45 -0400

    On Sun, 09 Oct 2005 14:07:19 +0800, Coywolf Qi Hunt said:
    > Hello,
    >
    > I find the kernel.org first page inconvenient for some people somehow
    > since the security stable came.

    Unfortunately, it's a "stable", not "security stable" release. Although
    a large proportion of the fixes are security-related, the aren't *all*
    security - there's also the occasional brown-bag bug or unexpected side
    effect that simply causes incorrect operation of the kernel.

    Having said that, Coywolf *is* right in that it's a bit unclear that
    you have to fetch the 'F'(ull) 2.6.13.3, then get the patch, put that
    on with patch -R to get a 2.6.13 tree, and then apply the 2.6.14-rc3 patch.
    (Although if you realize that 14-rc3 is diffed off 13.0, not 13.3, it's not
    that bad at all)...

    I admit being torn between encouraging more people to try -rc kernels, and
    wanting to enforce a minimum clue level on those trying to do so....

    Hmm.. what if we did something like this:

    diff -rup linux-2.6.13/dot.release linux-2.6.13.3/dot.release
    --- linux-2.6.13/dot.release 2005-10-09 03:09:54.000000000 -0400
    +++ linux-2.6.13.3/dot.release 2005-10-09 03:12:02.000000000 -0400
    @@ -1,2 +1,2 @@
    -This is a base release 2.6.13. Stable patches, 2.6.14-rc patches,
    -and the final 2.6.14 patch should be applied to this.
    +This is a dot release. You need to patch -R the .3 patch before
    +attempting to apply a .14-rc or .14 patch.

    And then build the 14-rc3 patch:

    diff -rup linux-2.6.13/dot.release linux-2.6.14-rc3/dot.release
    --- linux-2.6.13/dot.release 2005-10-09 03:09:54.000000000 -0400
    +++ linux-2.6.14-rc3/dot.release 2005-10-09 03:03:40.000000000 -0400
    @@ -1,2 +1,3 @@
    -This is a base release 2.6.13. Stable patches, 2.6.14-rc patches,
    -and the final 2.6.14 patch should be applied to this.
    +This is a 14-rc3 release. The patch will bomb out if you try
    +to apply it to anything other than a 2.6.13.0 tree. Did you
    +remember to 'patch -R' any 2.6.13.N 'stable' patch first?

    Now if we arrange for that to be the first diff in the patchfile, and
    they get it wrong, they'll see:

    % patch -p1 < 2.6.14-rc3.patch
    patching file dot.release
    Hunk #1 FAILED at 1.
    1 out of 1 hunk FAILED -- saving rejects to file dot.release.rej
    % cat dot.release.rej
    ***************
    *** 1,2 ****
    - This is a base release 2.6.13. Stable patches, 2.6.14-rc patches,
    - and the final 2.6.14 patch should be applied to this.
    --- 1,3 ----
    + This is a 14-rc3 release. The patch will bomb out if you try
    + to apply it to anything other than a 2.6.13.0 tree. Did you
    + remember to 'patch -R' any 2.6.13.N 'stable' patch first?

    (OK, it's a silly 3AM idea. ;)

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Stefan Lucke: "touchkit PS/2 touchscreen driver"

    Relevant Pages