Bodo Eggert <[EMAIL PROTECTED]> wrote: > Jamie Lokier <[EMAIL PROTECTED]> wrote: > > Miklos Szeredi wrote: > > >>���4)�Access�should�not�be�further�restricted�for�the�owner�of�the > >>������mount,�even�if�permission�bits,�uid�or�gid�would�suggest > >>������otherwise > >� > >�Why?��Surely�you�want�to�prevent�writing�to�files�which�don't�have�the > >�writable�bit�set?��A�filesystem�may�also�create�append-only�files�- > >�and�all�users�including�the�mount�owner�should�be�bound�by�that. > > That�will�depend�on�the�situation.�If�the�user�is�mounting�a�tgz�owned > by�himself,�FUSE�should�default�to�being�a�convenient�hex-editor.
If the user wants to edit a read-only file in a tgz owned by himself, why can he not _chmod_ the file and _then_ edit it? That said, I would _usually_ prefer that when I enter a tgz, that I see all component files having the same uid/gid/permissions as the tgz file itself - the same as I'd see if I entered a zip file. -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
