Date: Wed, 5 Mar 2008 03:11:42 -0600 From: Joshua Isom <jrisom@gmail.com> To: Kris Kennaway <kris@FreeBSD.org> Cc: philip@ridecharge.com, FreeBSD-Questions <FreeBSD-Questions@FreeBSD.org> Subject: Re: Uname borked on ??-Release... Message-ID: <e03d0d306070491b32db3b604c814739@gmail.com> In-Reply-To: <47CDAD96.8080301@FreeBSD.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 4, 2008, at 2:14 PM, Kris Kennaway wrote: > Kevin Kinsey wrote: >> Kris Kennaway wrote: >>> Kevin Kinsey wrote: >>> >>> What about strings /boot/kernel/kernel | grep 6.2-RELEASE? >>> >>> Kris >> As I would expect, it returns nothing at all. > > Your problem makes no sense then :) 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. > > Kris So, have you checked to make sure your uname is accurate and not just an echoing shell script of sorts? You never know, maybe someone hijacked your uname before you upgraded and the hijacked version wasn't written properly(which is odd since it's BSD licensed, where if it were GPL they'd have to release the code for their evil uname so can't use a GPL version). You could try greping over the entire filesystem for 6.2-RELEASE to find out where it could be coming from. Depending on the setup of your system, you could try zeroing all the spare blocks(I imagine `dd if=/dev/zero of=zero` would do the trick) and then seeing if the string's from some really hidden file. So many ways to have fun, but I don't want to be in your shoes.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e03d0d306070491b32db3b604c814739>