Uname borked on ??-Release...

[Mel]

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.