From owner-freebsd-hackers Tue Jun 30 20:03:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06374 for freebsd-hackers-outgoing; Tue, 30 Jun 1998 20:03:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA06304 for ; Tue, 30 Jun 1998 20:03:12 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id UAA11728; Tue, 30 Jun 1998 20:02:06 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: wjw@digi.digiware.nl (Willem Jan Withagen) cc: mike@smith.net.au (Mike Smith), hackers@FreeBSD.ORG Subject: Re: Variant Link implementation, continued In-reply-to: Your message of "Wed, 01 Jul 1998 01:03:37 +0200." <199806302303.XAA07485@digi.digiware.nl> Date: Tue, 30 Jun 1998 20:02:05 -0700 Message-ID: <11724.899262125@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have actual working code for this. > At the moment every variantlink gets replaced by '2.2.6', since that is my > current OS version. That's really cool! Apollo, here we come! ;-) > - How can I efficiently obtain the value of a sysctl value? > And should they look like 'variant.name', or would/should a > variant link be able to look like: > kern.osrelease: 2.2.6-STABLE I would expect any sysctl expansion to just use the current names, e.g. /usr/tmp/${kern.osrelease} would pretty much do what you'd expect. > - It seems that names are allocated from within the kernel > upon startup, nothing dynamic. Is there any work in progress to make > this more flexible? I could start by first creating a standard set > of names. I don't know if there's any work ongoing here or not. It's defintely a problem that they're currently created with a static linker set and I don't know of any way to create them at "runtime". > * An alternative would be: How do I obtain the environment of the > process using the link? (assuming it has nog messed with its > *env-pointer) Hooboy. That's the holy grail for variant symlink behavior, of course, but it's not information which is at all easy to get ahold of in the current implementation. :-( - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message