Terry Lambert <[EMAIL PROTECTED]> writes:
> Flags are associated with inodes, and symlinks do not have
> inodes in the common case, as they exist solely in the
> directory entry, unless they are too long.
Hu? The contents of the link will be stored in the inode itself
rather than in data blocks if it's short enough.
> Pretty clearly, there should _NOT_ be a seperate system call;
> the damn thing should just work. Adding a seperate system call
> means theaching everything that deals with flags about it (ls,
> chflags,
Of course chflags has to know about it to call chflags or lchflags.
But ls should just behave as usual with `-l':
datan# ls -lo
total 0
-rw-r--r-- 1 root wheel nodump 0 Jul 22 23:31 bar
lrwxr-xr-x 1 root wheel schg 3 Jul 22 23:31 foo -> bar
datan# ls -loL
total 0
-rw-r--r-- 1 root wheel nodump 0 Jul 22 23:31 bar
-rw-r--r-- 1 root wheel nodump 0 Jul 22 23:31 foo
> every FS supporing symlinks, etc.).
Why?
/assar
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
