From owner-freebsd-hackers Tue Mar 21 02:17:16 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA14276 for hackers-outgoing; Tue, 21 Mar 1995 02:17:16 -0800 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA14262 for ; Tue, 21 Mar 1995 02:17:12 -0800 Received: by sequent.kiae.su id AA29814 (5.65.kiae-2 ); Tue, 21 Mar 1995 13:08:50 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Tue, 21 Mar 95 13:08:49 +0300 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id NAA00784; Tue, 21 Mar 1995 13:06:46 +0300 To: davidg@Root.COM, "Justin T. Gibbs" Cc: freebsd-hackers@FreeBSD.org, Steven Wallace References: <199503210923.BAA00144@corbin.Root.COM> In-Reply-To: <199503210923.BAA00144@corbin.Root.COM>; from David Greenman at Tue, 21 Mar 1995 01:23:28 -0800 Message-Id: Organization: Olahm Ha-Yetzirah Date: Tue, 21 Mar 1995 13:06:45 +0300 X-Mailer: Mail/@ [v2.32 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: sym links Lines: 29 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1384 Sender: hackers-owner@FreeBSD.org Precedence: bulk In message <199503210923.BAA00144@corbin.Root.COM> David Greenman writes: > 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 POSIX says a little about simlinks, they tends to ignore them when possible and this intention cause such situation, I think. In any case POSIX is _standard_ commitee (I mean they don't discover completely new things) and NO so-called POSIX-symlinks exists in the world when this draft was written, so it is obviously misinterpretation. >appear like they have no inode associated with them. I wouldn't object if we >went back to the old way of doing this - with symlinks having an inode. The >problem of a regular user not being able to delete a symlink he created in >/tmp is one of the many problems with the way we have it now. You point to serious problem, even for it alone is worse to revert to previous behaviour. I vote YES for restoring canonical thing, so many problems with new symlinks, better to return to standard BSD way. Let's start voting? -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849