On Fri, Jun 01, 2001 at 09:44:54 -0500, Jeff Dike wrote:
> hno@... said:
> > Which is the whole point of a scheme like what umsdos uses. It
> > would allow the UML to assign whatever permissions and filetypes
> > it wants for it's own use while everything is actually stored as
> > plain files with no special permissions on the host.
> OK, that makes some sense. But if you just want access to normal
> stuff on the host, you don't want to turn on all the permissions.
> This seems to make sense only for files which will be accessed only
> from inside a UML.
With the mapping I suggested, you can still access normal files on the
host. They don't have a .__HOSTFS__-file, so UML will treat them as
owned by root but accept their permissions/file type/devnumbers on the
Files accessed primarily from inside a UML will have a
.__HOSTFS__-file when needed, which tells the UML the uid/gid, file
type and device numbers.
When UML itself runs as root, you might want it to behave
different. No need to use .__HOSTFS__-files then, just use a 1-1
mapping. UML could turn on this behaviour automatically if it is
started as root, and you could override the mode with an mount-time