From owner-freebsd-questions@FreeBSD.ORG  Tue Mar  4 21:05:51 2008
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: FreeBSD-Questions@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 41AC01065672
	for <FreeBSD-Questions@FreeBSD.org>;
	Tue,  4 Mar 2008 21:05:51 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 165998FC17;
	Tue,  4 Mar 2008 21:05:49 +0000 (UTC)
	(envelope-from kris@FreeBSD.org)
Message-ID: <47CDB9AD.4070307@FreeBSD.org>
Date: Tue, 04 Mar 2008 22:05:49 +0100
From: Kris Kennaway <kris@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Kevin Kinsey <kdk@daleco.biz>
References: <47CC36C9.7020402@daleco.biz> <47CC5E2A.8090800@FreeBSD.org>
	<47CC72C8.5070905@daleco.biz> <47CC782D.3090005@FreeBSD.org>
	<47CC81FE.6050206@daleco.biz> <47CD9E82.9030606@FreeBSD.org>
	<47CDAA50.2060104@daleco.biz> <47CDAD96.8080301@FreeBSD.org>
	<47CDB3D8.3020508@daleco.biz>
In-Reply-To: <47CDB3D8.3020508@daleco.biz>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: FreeBSD-Questions <FreeBSD-Questions@FreeBSD.org>
Subject: Re: Uname borked on ??-Release...
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Mar 2008 21:05:51 -0000

Kevin Kinsey wrote:
>>
>> Your problem makes no sense then :)  
> 
> Up until now, you've told me a couple things
> I might not have already known :-D
> 
>> The kern.osrelease returns a string compiled into the kernel (see 
>> conf/newvers.sh), so if it returns 6.2-RELEASE then that string must 
>> be present.
>>
> 
> I'd like to think so, but, I don't.  If you've feeling masochistic,
> you can see that evidence below.  When does the sysctl get set?

The string is set at kernel compile time and the sysctl that points to 
it is read-only.

> During boot, I assume?  Is there any "caching" of sysctl data
> that might persist over a reboot?
> 
> Even better, have I been h@X0red?  lol.  Be the first time in
> forever, but I've griped and griped to my ISP about the security
> of their CPE, to no avail.

It is possible, I guess it makes more sense than anything else.

Kris