Committing PEFS to CURRENT
John-Mark Gurney
jmg at funkthat.com
Fri Dec 27 19:51:12 UTC 2013
Alexandre Biancalana wrote this message on Fri, Dec 27, 2013 at 17:20 -0200:
> On Tue, Oct 8, 2013 at 12:12 AM, Gleb Kurtsou <gleb.kurtsou at gmail.com>wrote:
>
> > On (07/10/2013 21:59), Outback Dingo wrote:
> > > On Mon, Oct 7, 2013 at 9:42 PM, Gleb Kurtsou <gleb.kurtsou at gmail.com>
> > wrote:
> > >
> > > > On Mon, Oct 7, 2013 at 6:24 PM, John-Mark Gurney <jmg at funkthat.com>
> > wrote:
> > > > >
> > > > > But will the work get done to clean it up after the freeze is over?
> > What
> > > > > happens if it doesn't, will it get removed before 10.1 or will we
> > have
> > > > > to live w/ the code?
> > > >
> > > > I still hope not to get hit by bus any time soon..
> > > >
> > >
> > > on a side note, i applied the patch to stable/9 out of curiosity and the
> > > kernel failed to build the module
> > > however i could install fine from ports.
> >
> > Correct, there is no support for old kernels in the patch.
> > Port will be maintained and will provide support for older versions in
> > case PEFS finds its way to 10.0.
>
> Are there any news about PEFS commit ?
It's definately not going into 10.0, but it could make it in a future
release, but...
I haven't heard back about plans for moving forward on the project.
I'm definately interested in getting this in the tree, but have other
work that is higher priority right now.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
More information about the freebsd-current
mailing list