Re: [PATCH 8/8] startup: bind the startup server to /servers/startup

2014-10-15 Thread Justus Winter
Hi Roland :) Quoting David Michael (2014-09-18 23:14:17) > On Wed, Sep 3, 2014 at 8:33 AM, Justus Winter > <4win...@informatik.uni-hamburg.de> wrote: > > Bind the startup server to /servers/startup instead. Use this to > > contact the startup server. > > I'm trying to test this patch, and glibc

Re: bug in puts(3) affecting /hurd/init

2014-10-15 Thread Samuel Thibault
Samuel Thibault, le Thu 16 Oct 2014 01:07:13 +0200, a écrit : > Does the puts() call return some error? I mean perhaps _IO_puts stops early because _IO_vtable_offset or _IO_fwide() fail. Samuel

Re: bug in puts(3) affecting /hurd/init

2014-10-15 Thread Samuel Thibault
Does the puts() call return some error? Justus Winter, le Wed 15 Oct 2014 16:46:50 +0200, a écrit : > So, startup calls setbuf while libdiskfs does not. Does libdiskfs really do some puts that is working? > Also, startup only passes D_WRITE to device_open, while libdiskfs uses > D_READ|D_WRITE.

bug in puts(3) affecting /hurd/init

2014-10-15 Thread Justus Winter
Hello, there is a strange bug in puts(3) affecting /hurd/init (or /hurd/startup if you live on the edge). It is also sometimes affecting printf(3), as it is replaced by gcc with a call to puts under certain conditions (e.g. with a format string ending in '\n' without any conversion specifiers).

Re: Failing {lib,}gnome-keyring tests: How to make mlock/munlock available to non-root?

2014-10-15 Thread Samuel Thibault
Svante Signell, le Wed 15 Oct 2014 10:56:41 +0200, a écrit : > On Wed, 2014-10-15 at 10:06 +0200, Samuel Thibault wrote: > > Svante Signell, le Wed 15 Oct 2014 09:57:21 +0200, a écrit : > > > See also https://lists.debian.org/debian-devel/2014/10/msg00201.html for > > > a discussion on the topic. >

Re: Failing {lib,}gnome-keyring tests: How to make mlock/munlock available to non-root?

2014-10-15 Thread Svante Signell
On Wed, 2014-10-15 at 10:06 +0200, Samuel Thibault wrote: > Svante Signell, le Wed 15 Oct 2014 09:57:21 +0200, a écrit : > > See also https://lists.debian.org/debian-devel/2014/10/msg00201.html for > > a discussion on the topic. > > I can't understand why you proposed to use setuid in order to kee

Re: Failing {lib,}gnome-keyring tests: How to make mlock/munlock available to non-root?

2014-10-15 Thread Samuel Thibault
Samuel Thibault, le Wed 15 Oct 2014 10:06:33 +0200, a écrit : > The amount of such locked memory shall however be accounted and > limited. The default on my Linux system is 64KB. And it should be configurable per-process through ulimit -l. Samuel

Re: Failing {lib,}gnome-keyring tests: How to make mlock/munlock available to non-root?

2014-10-15 Thread Samuel Thibault
Svante Signell, le Wed 15 Oct 2014 09:57:21 +0200, a écrit : > See also https://lists.debian.org/debian-devel/2014/10/msg00201.html for > a discussion on the topic. I can't understand why you proposed to use setuid in order to keep secrets, but oh well. To get mlock available to user should be a

Re: Failing {lib,}gnome-keyring tests: How to make mlock/munlock available to non-root?

2014-10-15 Thread Svante Signell
On Wed, 2014-10-15 at 09:52 +0200, Svante Signell wrote: > Hi, > > Currently libgnome-keyring and gnome-keyring secmem related tests fail, > falling back to mlock/munlock requiring root permissions to lock > memory. > In the code we have: > err = __get_privileged_ports (&hostpriv, NULL); > if

Failing {lib,}gnome-keyring tests: How to make mlock/munlock available to non-root?

2014-10-15 Thread Svante Signell
Hi, Currently libgnome-keyring and gnome-keyring secmem related tests fail, falling back to mlock/munlock requiring root permissions to lock memory. In the code we have: err = __get_privileged_ports (&hostpriv, NULL); if (err) return __hurd_fail (EPERM); How to make mock/munlock availabl