From owner-freebsd-hackers Sun Jul 5 15:20:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20796 for freebsd-hackers-outgoing; Sun, 5 Jul 1998 15:20:52 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from shrimp.dataplex.net (shrimp.dataplex.net [208.2.87.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA20744 for ; Sun, 5 Jul 1998 15:20:41 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from [208.2.87.10] (user10.dataplex.net [208.2.87.10]) by shrimp.dataplex.net (8.8.8/8.8.5) with ESMTP id RAA00623; Sun, 5 Jul 1998 17:24:55 -0500 (CDT) X-Sender: rkw@mail.dataplex.net Message-Id: In-Reply-To: <199807051826.NAA10291@bonkers.taronga.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 5 Jul 1998 17:13:47 -0500 To: peter@taronga.com (Peter da Silva) From: Richard Wackerbarth Subject: Re: A really hoopy idea for variant symlinks. Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:26 PM -0500 7/5/98, Peter da Silva wrote: >So yours would be under /proc/curproc/syms. and if you had permission you >could browse other processes you own and examine them under /proc/pid/syms. > >AND, because you're exposing them as symlinks, you don't have to change >how symlinks work. > >Instead of going through .../${USER}/... you'd just set up a symlink in >the proper place to /proc/curproc/syms/user. > >And instead of creating new system calls, you could examine the buggers >using "ls". > >Or diddle them from scripts. As for the mechanism to interogate and set them, this proposal seems OK to me. However, to have appropriate value, we need to have A SINGLE VALUE (eg: osversion) that can be referenced from multiple places. Thus changing a single value would change a number of links at the same time. Richard Wackerbarth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message