Perry Hutchison wrote:
So the sort of write access being validated here would be writing to
the symlink itself (i.e. the definition)?
symlinks are dereferenced during name lookup and are not affected by
the write mount options of the filesystems they reside on.
you can open a file for write by
> > Is the inclusion of VLNK here correct? I would think that
> > only the target of the symlink should matter: if it happens
> > to point onto a writable FS, the fact that the symlink itself
> > is on a ROFS should not matter.
>
> yes, it is correct.
> short symbolic links are stored in the inod
Perry Hutchison wrote:
Is the inclusion of VLNK here correct? I would think that
only the target of the symlink should matter: if it happens
to point onto a writable FS, the fact that the symlink itself
is on a ROFS should not matter.
yes, it is correct.
short symbolic links are stored in th
I've just noticed this, in ufs/ufs/ufs_vnops.c:ufs_access()
/*
* Disallow write attempts on read-only filesystems;
* unless the file is a socket, fifo, or a block or
* character device resident on the filesystem.
*/
if (mode & VWRITE) {
switch (vp->v_type) {
4 matches
Mail list logo
