> Well, I'd first be very interested to know if anyone has even seen
> this work. :)
>
> I have seen regrettably little feedback about it so far.
>
> - Jordan
I can understand part of the reason for this... 4.0-RELEASE is right
arround the corner, and people are focusing on delivering a stable product,
not introducing alpha code into the system at the last second. the current
rpc.lockd is a known value, placing a "maybe" version into the stream at
this point would do no one any good.
> > I'm suprised no one has gotten back to you on this, since it seems to
> > need no kernel changes and the fact that the existing lockd just
> > doesn't really do anything...
> >
> > But then again we are 'frozen'. (hello Jordan :) )
> >
> > I think that having "we now serve locks" in 4.0-release as a real
> > step forward. I would like to see it go in before the release is
> > cut.
Again, I feel that this isn't woth it at this point... it should be something
we strive for in 4.1-RELEASE.
> >
> > Can anyone comment?
> >
> > More importantly can any of the people that have been _begging_
> > for this please take a moment and test or at least give David the
> > courtisy of a responce?
> >
> > You guys do want this right?
> >
> > You guys don't want to have to run -current for another year just to
> > have lockd right? (the reason I cc'd -stable)
> >
> > *hello? is this thing on?*
Mmmm.... feedback would be very good. Also, what are the chanches of
getting the 3 required functions MFC-ed? fh{open|stat|statfs} ?
--
David Cross | email: [EMAIL PROTECTED]
Acting Lab Director | NYSLP: FREEBSD
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Computer Science | Fax: 518.276.4033
I speak only for myself. | WinNT:Linux::Linux:FreeBSD
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
