Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Jun 2012 14:39:17 +0200 (CEST)
From:      Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl>
To:        Robert Watson <rwatson@freebsd.org>
Cc:        bp@freebsd.org, Arnaud Lacombe <lacombar@gmail.com>, freebsd-hackers@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>, kby@freebsd.org, Chris Rees <utisoft@gmail.com>
Subject:   Re: sysctl filesystem ?
Message-ID:  <alpine.BSF.2.00.1206261437090.1407@wojtek.tensor.gdynia.pl>
In-Reply-To: <alpine.BSF.2.00.1206260954120.2004@fledge.watson.org>
References:  <CACqU3MXaa0R7fG6Q-EqS3h8PJh__tzNeugBxVyqKHxsCR-wTuQ@mail.gmail.com> <alpine.BSF.2.00.1206260805450.3572@wojtek.tensor.gdynia.pl> <CADLo83_hLe-MUJASLmx%2B8MBj12LOQ_-gsmWNjpzvzZdxwEgStw@mail.gmail.com> <alpine.BSF.2.00.1206260954120.2004@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
> and/or get it wrong.  sysctl has some file-system like properties, but on the 
> whole, it's not a file system -- it's much more like an SNMP MIB.
>
> While you can map anything into anything (including Turing machines), I think 
> the sysctl command line tool and API, despite its limitations, is a better 
me too.

i REALLY appreciate the way FreeBSD do this. pseudo-filesystems are 
sometimes good but making them default method is bad.

Current way is simple. Or actually - less complicated as i think for 
example - XML in system output is not.



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