[PATCH] use HAL property to set mount root in callouts

Kay Sievers kay.sievers at vrfy.org
Sat Jan 7 10:33:46 PST 2006


On Sat, Jan 07, 2006 at 08:43:16PM +0300, Andrey Borzenkov wrote:
> On Saturday 07 January 2006 15:29, Kay Sievers wrote:
> > On Sat, Jan 07, 2006 at 03:08:30PM +0300, Andrey Borzenkov wrote:
> > > Is there any reason callouts do not use storage.policy.default.mount_root
> > > and harcdcode /media instead?
> >
> > Yes, all storage policy stuff along with fstab sync will go away some day.
> >
> 
> OK so all options are supposed to come from client, right?

Yes, from the user session.

> Why are iocharset, 
> codepage, utf8 and mode are blacklisted then?

They are just not whitelisted. They will be there if we are ready.

> Blacklisting first three breaks 
> any non-iso-8859-1 user;

There will be a "allowed options" list that will be checked against in
the end.

> blacklisting mode does not allow user to restrict 
> access to inserted media (user may not want USB key with bank certificate and 
> transactions be readable to everyone).

Filesystems have permissions or things like FAT is mounted with the uid of
the requesting user.

Kay


More information about the hal mailing list