Date: Wed, 5 Mar 2008 15:16:18 +0100 From: Mel <fbsd.questions@rachie.is-a-geek.net> To: freebsd-questions@freebsd.org Cc: Kris Kennaway <kris@freebsd.org>, Joshua Isom <jrisom@gmail.com>, philip@ridecharge.com Subject: Re: Uname borked on ??-Release... Message-ID: <200803051516.19941.fbsd.questions@rachie.is-a-geek.net> In-Reply-To: <e03d0d306070491b32db3b604c814739@gmail.com> References: <47CC36C9.7020402@daleco.biz> <47CDAD96.8080301@FreeBSD.org> <e03d0d306070491b32db3b604c814739@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 05 March 2008 10:11:42 Joshua Isom wrote:
> 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).
>
Then sysctl would be a shell script too.
The only way I can see this happening, is that /boot at loader time, is not
the same /boot after kernel is loaded.
For this reason, it would be nice if kern.bootfile would list
ad0s1a:/boot/kernel/kernel.
--
Mel
Problem with today's modular software: they start with the modules
and never get to the software part.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200803051516.19941.fbsd.questions>