From owner-freebsd-hackers  Tue Mar 21 05:04:36 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA19554 for hackers-outgoing; Tue, 21 Mar 1995 05:04:36 -0800
Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id FAA19546 for <hackers@freebsd.org>; Tue, 21 Mar 1995 05:04:31 -0800
Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA04921
  (5.67a/IDA-1.5); Tue, 21 Mar 1995 06:57:12 -0600
Received: by bonkers.taronga.com (smail2.5p) id AA22057; 21 Mar 95 06:21:38 CST (Tue)
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.6) id GAA22054; Tue, 21 Mar 1995 06:21:38 -0600
From: Peter da Silva <peter@bonkers.taronga.com>
Message-Id: <199503211221.GAA22054@bonkers.taronga.com>
Subject: Re: sym links
To: davidg@Root.COM
Date: Tue, 21 Mar 1995 06:21:38 -0600 (CST)
Cc: hackers@FreeBSD.org
In-Reply-To: <199503210923.BAA00144@corbin.Root.COM> from "David Greenman" at Mar 21, 95 01:23:28 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 347       
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

>    Well, that's how POSIX would have it...but in FFS they are stored in the
> inode if short and in a regular disk block if long. They're only made to
> appear like they have no inode associated with them.

That's bogus. Really. Hiding implementation details like this is a VMSish
thing to do, IMHO. If the symlink's really got an inode use it.