From owner-freebsd-current Mon Jun 8 11:12:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08340 for freebsd-current-outgoing; Mon, 8 Jun 1998 11:12:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (daemon@smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08328 for ; Mon, 8 Jun 1998 11:12:21 -0700 (PDT) (envelope-from tlambert@usr04.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id LAA19031; Mon, 8 Jun 1998 11:12:20 -0700 (MST) Received: from usr04.primenet.com(206.165.6.204) via SMTP by smtp04.primenet.com, id smtpd018959; Mon Jun 8 11:12:14 1998 Received: (from tlambert@localhost) by usr04.primenet.com (8.8.5/8.8.5) id LAA11746; Mon, 8 Jun 1998 11:12:05 -0700 (MST) From: Terry Lambert Message-Id: <199806081812.LAA11746@usr04.primenet.com> Subject: Re: Variant Link implementation (Was: Re: lorder problem: ....... ) To: wjw@IAEhv.nl Date: Mon, 8 Jun 1998 18:12:04 +0000 (GMT) Cc: winter@jurai.net, mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: <199806081606.SAA29892@surf.IAEhv.nl> from "Willem Jan Withagen" at Jun 8, 98 06:06:31 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > => > Whoops; just to clarify; vlink_xlate(tok, dbuf, &dbofs) copies the > => > value of the token at (tok) into (dbuf) at (dbofs) presuming that > => > (dbofs) would not exceed the allowed size, updates (dbofs) and returns > => > 0 (all OK), 1 (not enough room) or 2 (no translation for tok available). > => > => Would it not be nicer to introduce a new file/link type? This would allow > => lower overall cost as you would not have to scan each link, only those > => links of the proper type. > > That's one way of doing it. Is was first thinking of doing it through sysctl > for the whole system on or off. But then that is a sort of blunt axe > solution. A new link type is overkill. The evaluation of symlinks uses FORTRAN-style mutual recursion (into the same buffer) anyway. The speed of symlink evaluation isn't really an issue unless the "${" / "}" is found to be there anyway (or shouldn't be). It seems to me that the code Mike did fails on the "${" but NOT "}" case. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message