Date: Wed, 9 Oct 2002 02:38:47 -0700 From: Adam Weinberger <adam@vectors.cx> To: freebsd-questions@FreeBSD.ORG Subject: Re: help with ln "linking" Please! [attn manpage authors!] Message-ID: <20021009093847.GJ81796@vectors.cx> In-Reply-To: <200210090909.g9999CW2083670@lurza.secnetix.de> References: <vgfzvg5acm.zvg@localhost.localdomain> <200210090909.g9999CW2083670@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
>> (10.09.2002 @ 0209 PST): Oliver Fromme said, in 1.2K: <<
> Gary W. Swearingen <swear@attbi.com> wrote:
> > ln [-fhinsv] linked_filename [link_filename]
> > ln [-fhinsv] linked_filename ... dir_filename
> > link existing_filename alternate_filename
"linked" should be avoided. this is the exact problem the current
documentation has. linked from? linked too?
i'd explain it like this: i'd give the synopsis, then an immediate
example. i'd LOVE to see a quick sample USEFUL and most common
invocation of a short command right there in the synopsis section. i
think many such utilities' manpages should do that.
ln [-b0rk] link_to [link_from]
"% ln file link" makes a link FROM "link" TO "file".
-Adam
--
"Oh good, my dog found the chainsaw."
-Lilo, "Lilo & Stitch"
Adam Weinberger
adam@vectors.cx
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021009093847.GJ81796>