Date: Sun, 5 Jul 1998 13:26:00 -0500 From: peter@taronga.com (Peter da Silva) To: hackers@FreeBSD.ORG Subject: A really hoopy idea for variant symlinks. Message-ID: <199807051826.NAA10291@bonkers.taronga.com>
next in thread | raw e-mail | index | archive | help
Stop me if you've heard this one.
OK, the thing you need for variant symlinks is a per-process inherited
namespace, like the environment, but one that's in the kernel so symlinks
can get to it, unlike the environment.
IK, let's say you built one and hung it off the process structure. How
are you going to access it? Well, you could create a couple new system
calls to browse the namespace, or... and here's the hoopy idea... you
hang it off /proc/*/syms. As symlinks.
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.
Does that look like a workable low-impact almost-transparent way to do
this that works really well with the way UNIX already works or what?
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?199807051826.NAA10291>