Hi, That sounds like a good idea to me, +1.
Cheers, Antonio Huete On 04/11/10 18:00, Venkatesh Srinivas (via DragonFly issue tracker) wrote: > Venkatesh Srinivas <[email protected]> added the comment: > > So mlockall/munlockall is a no-op in the kernel, but the syscall handler is > there. We should probably still expose it from libc and have the kernel > return > ENOSYS, right? > > _____________________________________________________ > DragonFly issue tracker <[email protected]> > <http://bugs.dragonflybsd.org/issue1712> > _____________________________________________________ > >
