If I open a device like /dev/loop0 or /dev/console from a hostfs mount, I'll get the UML device, not the host device, right?
So why are the permissions checks on hostfs devices done relative to the _host_ user? If /dev/console doesn't belong to the current user, the system can't even open the initial console, despite the fact the output does NOT go to TTY1 if I'm running it an xterm. Similarly, if /dev/loop0 is chmod 600 and I run UML as a normal user and try to do a mount -o loop, it says it can't find a loop device. Yet if I run UML as root, it doesn't allocate one of the parent's loop devices, UML does it internally... I'm told there's a major rewrite of hostfs underway. Is it worth me trying to patch the existing hostfs code, or should I go try to track down the new stuff and try it out? Rob ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
