Hi all,
I need to run UML ower sub-directory (where
a copy of debian distribution is) mounted as hostfs.
(the NFS or a filesystem in file is not efficient anought).
I just find correct options to run:
root=/dev/root rootflags=<my_dir> rootfstype=hostfs
and run it as user: root
But all files which are created by any user inside
the uml are owned by root (the user id with uml is running). But the the root inside uml can change this file by chown. I thing that the patch to hostfs can
be done to avoid mounting hostfs (with some special atribute) to do this well. (If the users's ids are equiv inside and outside uml).
Sorry my english and help me please.
Is this possible to do such a patch to hostfs implementation?
With regards
--mara
my problem :
1) run uml as a root with some chroot filesystem subdir
as a hostfs-root
2) su - someuser
3) touch /tmp/somefile
#some error is anounced, but
-> /tmp/file is createt, but owned by root :-(
and the user 'someuser' cannot write
to it
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
I need to run UML ower sub-directory (where
a copy of debian distribution is) mounted as hostfs.
(the NFS or a filesystem in file is not efficient anought).
I just find correct options to run:
root=/dev/root rootflags=<my_dir> rootfstype=hostfs
and run it as user: root
But all files which are created by any user inside
the uml are owned by root (the user id with uml is running). But the the root inside uml can change this file by chown. I thing that the patch to hostfs can
be done to avoid mounting hostfs (with some special atribute) to do this well. (If the users's ids are equiv inside and outside uml).
Sorry my english and help me please.
Is this possible to do such a patch to hostfs implementation?
With regards
--mara
my problem :
1) run uml as a root with some chroot filesystem subdir
as a hostfs-root
2) su - someuser
3) touch /tmp/somefile
#some error is anounced, but
-> /tmp/file is createt, but owned by root :-(
and the user 'someuser' cannot write
to it