Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 15 Nov 1995 13:55:11 -0800 (PST)
From:      Julian Elischer <julian@ref.tfs.com>
To:        phk@critter.tfs.com (Poul-Henning Kamp)
Cc:        peter@jhome.dialix.com, bde@zeta.org.au, CVS-commiters@freefall.freebsd.org, cvs-sys@freefall.freebsd.org
Subject:   Re: cvs commit: src/sys/kern kern_sysctl.c
Message-ID:  <199511152155.NAA01351@ref.tfs.com>
In-Reply-To: <2525.816427167@critter.tfs.com> from "Poul-Henning Kamp" at Nov 15, 95 10:19:27 am

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> Another thing I would love to make is a ability to create variables for
> user-land purposes:
> 
> 	0.5.<oid>	Create a variable, "new" holds info.
> 
> This would allow us to use sysctl as a miniature registry for information,
> for instance:
> 	domainname 
> 	which crypt to use as default.
> 	what to do in malloc in case of an allocation error.
> 	anything else you can thing off...
> 
> What do you people think ?

ok this is like "System-wide" environment variables..

it also means we are going to have 4 ways of doing similar things..
1/ environment variables passwd from init
2/ sysctl variables
3/ /proc and /kern could be extended to store these things
4/ I've considered extending devfs to allow access to
system stuff
I thought about being able to extend the sysctl interface into a f/s interface
(just replace them dots with /)

:)



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