Date: Tue, 04 Mar 2008 22:05:49 +0100 From: Kris Kennaway <kris@FreeBSD.org> To: Kevin Kinsey <kdk@daleco.biz> Cc: FreeBSD-Questions <FreeBSD-Questions@FreeBSD.org> Subject: Re: Uname borked on ??-Release... Message-ID: <47CDB9AD.4070307@FreeBSD.org> In-Reply-To: <47CDB3D8.3020508@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47CDB9AD.4070307>