[Ukfreebsd] uname -r issue

[O'Connor, Kevin]

> -----Original Message-----
> From: Ukfreebsd [mailto:ukfreebsd-bounces at uk.freebsd.org] On Behalf Of
> Sevan / Venture37
> Sent: 18 June 2015 15:24
> To: UK FreeBSD Users
> Subject: Re: [Ukfreebsd] uname -r issue
> 
> On 18 June 2015 at 14:51, O'Connor, Kevin
> <KevinO'Connor at merseyfire.gov.uk> wrote:
> > This is more of an annoyance than a technical issue but after a freebsd-
> update fetch install and several reboots uname -a is still reporting the
> previous build number on 10.1 release.
> > According to the handbook uname -a gets it's information from
> /usr/src/sys/conf/newvers.sh.
> > I've checked the file and it does indeed list it as RELEASE-p13 but
> > uname -r is still showing p10
> >
> > Anyone have an idea why the file is not getting read correctly, permissions
> are fine, or where the incorrect information is coming from?  Having to parse
> the file newvers.sh on every server would be a bit of a pain.
> >
> > Regards
> >
> > Kevin
> 
> Hi Kevin,
> uname gets its information from sysctl, newvers.sh is used when rolling a
> new kernel.
> https://svnweb.freebsd.org/base/head/usr.bin/uname/uname.c?revision=2
> 56557&view=markup
> Are you using a custom kernel?
No just the standard generic kernel. I'm well aware the freebsd-update cannot rebuild a custom kernel.
> Have you rebooted since updating?
Several times. I've also re-run freebsd-update install (Nothing to update)  and rebooted
> What does dmesg or the contents of /var/run/dmesg.boot say the kernel
> version is?
Yes I should have said that is also reporting p10
> 
> 
> Sevan
> 

I suppose it's remotely possible that as the generic kernel didn't need a rebuild it's still reporting the old one. I shall do a manual rebuild and see if that resolves the behaviour.

Thanks

Kevin
This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this e-mail in error please notify the originator of the message. 

Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority, states them to be the views of Merseyside Fire & Rescue Service, (MFRS).

Incoming and outgoing emails may be monitored in line with current legislation.

Steps have been taken to ensure that this email and attachments are free from any virus.  In keeping with good computing practice the recipient should ensure they are actually virus free.

http://www.merseyfire.gov.uk/