[illumos-Developer] webrev: removal of closed kcfd
Garrett D'Amore
garrett at damore.org
Sun Sep 12 09:34:04 PDT 2010
On Sun, 2010-09-12 at 12:13 -0400, Richard Lowe wrote:
> Garrett D'Amore wrote:
> > I found one more problem, which is fixed by the following:
> >
> > http://pastebin.ca/1938665
> >
> > Assuming nobody has any further objections, I'll be working on
> > integrating this tomorrow.
> >
> > I have tested with a custom misc module that submits kernel crypto, with
> > userland crypto, and with ipsec. Its ready for general consumption.
> >
> > Note that this will create a significant flag day. You *must* remove
> > the closed bins tarball, and use the newly updated nightly. You must
> > also do a *full* build, to avoid leaving stale bits that are
> > incompatible behind.
>
> I'm assuming you mean the crypto tarball, not the closed tarball?
Yes, I meant the *crypto* tarball. Thanks for catching that.
- Garrett
>
> If you mean the closed tarball, I have not see a webrev which does close
> to enough to make that viable (in packaging, especially).
>
> -- Rich
>
> _______________________________________________
> Developer mailing list
> Developer at lists.illumos.org
> http://lists.illumos.org/m/listinfo/developer
More information about the Developer
mailing list