Oliver Fromme <[EMAIL PROTECTED]> writes: > Gary W. Swearingen <[EMAIL PROTECTED]> wrote: > > ln [-fhinsv] linked_filename [link_filename] > > ln [-fhinsv] linked_filename ... dir_filename > > link existing_filename alternate_filename > > > > This is cleaner, but I think "filename" should be standard in filenames. > > But it is not a filename.
It's a string which is used by ln(1) and the kernel's directory software for a filename; if people want to misuse it for storing PIDs or control strings or MP3s, that's an abuse of the system which the manual shouldn't bother to accommodate. > > Yuck; malloc.conf is nasty. > > No, it's extremely useful and efficient. ... > Also, symlinks are an easy way to atomically check and create > lockfiles in shell scripts. Useful, efficient, easy -- and yucky, nasty, kludgy. Apt to break if the directory scheme changes or to prevent improvements to same. Maybe it should be: ln string_for_directory filename_to_access_string_by Just kidding. It can't end in a preposition. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message