On Mon, Aug 27, 2007 at 05:35:30PM +0200, Joachim K?nig wrote:
> Eric Haszlakiewicz wrote:
> >Actually a little of both.  You can get close to the current emulation code
> >by doing a union mount with / _under_ /emul/linux (mount_union -b), then
> >chroot'ing into it.  (not quite the same though)
> >  
> So no matter if it's more like chroot or an overlay mount:
> 
> - root permissions are required to accept a certain emulation root
>  (either by design, in /emul or by explictely allowing it via a new
>   sysctl call or similar mechanism)
> 
> - root permission is (or should not be required) to run a binary in
>  any of the accepted emulation roots

Why?  root permissions should only be needed for something would let the
user do something they aren't normally allowed to do.
If the user has write access to any executable filestore, then allowing
the 'emulation root' of a process to be user settable shouldn't be an issue
(apart from suid executables).

	David

-- 
David Laight: david@l8s.co.uk