From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <54A6C072.7020303@web.de> Date: Fri, 02 Jan 2015 16:59:46 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <54A672BA.8090209@web.de> <54A679D5.20903@xenomai.org> <54A67CD1.10103@web.de> <54A69D42.2010408@xenomai.org> <54A69BFA.7060405@web.de> <54A6A506.3060504@xenomai.org> <54A6A387.4010109@web.de> <20150102141625.GD1492@daedalus> <20150102150638.GE1492@daedalus> In-Reply-To: <20150102150638.GE1492@daedalus> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable Subject: Re: [Xenomai] [Xenomai-git] Philippe Gerum: copperplate: add configuration tunable for registry moint point List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Xenomai On 2015-01-02 16:06, Gilles Chanteperdrix wrote: > To explain a bit more completely. We can not assume that xenomai > applications are running as root user. And non root user are not > allowed to create /run/xenomai or /var/run/xenomai (at least not on > debian or slackware). What is more, these directories being > typically non persistent, a script has to be modified somewhere to > add mkdir /var/run/xenomai at every boot. On the other hand, mkdir > /mnt/xenomai has to be done once and only once, in the "make > install" phase for instance, since "make install" is run as root, > except that if /mnt is read-only it will not work. But not many > users are running system where they compile and run things with root > filesystem read-only. Anyway, the two cases are really similar, no > one is advantageous over the other. We are going to see questions on > the mailing list about that, whatever we do. Perhaps adding a small > kernel module to create /proc/xenomai/registry would make things > simpler... > = Non-root users are indeed an interesting new aspect. However, the solution to make a central directory writable seems weird to me. If you want to allow non-root users to access the registry, it would be way more logical to either shoot up a single privileged sysregd that everyone can talk to or use private instances that also run against their own per-user mount points, likely located in $HOME. Jan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: