Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 6 Jul 1998 10:01:18 +0200 (MET DST)
From:      Willem Jan  Withagen <wjw@surf.IAE.nl>
To:        rkw@dataplex.net
Cc:        hackers@FreeBSD.ORG
Subject:   Re: A really hoopy idea for variant symlinks.
Message-ID:  <199807060801.KAA16227@surf.IAE.nl>
In-Reply-To: <l03130300b1c5a9ee1886@[208.2.87.10]>
References:  <199807051826.NAA10291@bonkers.taronga.com>

next in thread | previous in thread | raw e-mail | index | archive | help
In article <l03130300b1c5a9ee1886@[208.2.87.10]> you write:
>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.

Also, an hierarchy in the name-space will be much more difficult.
Your favorite link will be either in /proc/pid/syms, or not.....
In which case access will just fail.

And then we'de have to start doing special things anyway, next to the thing
that I'm not so into /proc-items
But then as it goes with code here, I you like it this way... feel free

--WjW

-- 
Internet Access Eindhoven BV.,  voice: +31-40-2 393 393, data: +31-40-2 606 606
P.O. 928, 5600 AX Eindhoven, The Netherlands
Full Internet connectivity for only fl 12.95 a month.
Call now, and login as 'new'.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807060801.KAA16227>