Date: Sat, 12 Apr 2008 12:42:46 -0500 From: "Jeremy Messenger" <mezz7@cox.net> To: "Joe Marcus Clarke" <marcus@marcuscom.com> Cc: gnome@freebsd.org, cokane@freebsd.org Subject: Re: Seahorse issues Message-ID: <op.t9id5keu9aq2h7@mezz.mezzweb.com> In-Reply-To: <1207807915.61729.40.camel@shumai.marcuscom.com> References: <47FD09AC.2020907@FreeBSD.org> <1207776230.61729.28.camel@shumai.marcuscom.com> <47FD34E8.2000005@FreeBSD.org> <1207807915.61729.40.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 10 Apr 2008 01:11:55 -0500, Joe Marcus Clarke <marcus@marcuscom.com> wrote: <snip> > The problem is the fact that FreeBSD's mlock() requires setuid > privileges, and thus seahorse cannot allocate secure memory. The Yesterday, I have found archives about mlock() in freebsd-arch@. http://lists.freebsd.org/pipermail/freebsd-arch/2006-July/005496.html It leads to: http://people.freebsd.org/~kib/overcommit/index.html I am not sure if it's useful for this issue. Cheers, Mezz > Joe -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.t9id5keu9aq2h7>