Uname borked on ??-Release...

Kevin Kinsey kdk at daleco.biz
Mon Mar 3 17:35:18 UTC 2008


Been bashing myself on the head for a few days, so I'm
looking for a little help.  If you've a big stick, read
on (and apologies if poor formatting, I'm using an unfamiliar
keyboard, unfamiliar mailer, and I'm not even sure if this
system is running FreeBSD anymore :-D   )

I get the following from uname -a:

FreeBSD archangel.daleco.biz 6.2-RELEASE FreeBSD 6.2-RELEASE #6:
Sat Jun  2 09:22:50 CDT 2007  root at archangel.daleco.biz:
/usr/obj/backup/src/sys/GENERIC  i386

However, I rebuilt world, more or less without issues,
twice in February with "RELENG_6" in the supfile.  This
didn't change uname's output, and that worried me a bit.

So, to make matters bette^H^H^H^Hadder, I csup'ped
to RELENG_7_0 the day after it was release, read
/usr/src/UPDATING, and the webpage detailing the
upgrade, and did another buildworld/kernel cycle.
Now I have no idea if I'm on 6 or 7 (seems like
7, but many ports issues, and I've rebuilt them
all), and it's just becoming a major PITA.

"Uname -a" still shows the same string.  However,
file dates in /bin, /sbin, etc., are Feb 28, and:

#cd /bin && file grep
grep: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD),
for FreeBSD 7.0 (700055), dynamically linked (uses shared libs),
FreeBSD-style, stripped

Manpages also show "FreeBSD 7.0".


I blew away /usr/src and /usr/obj before the last
buildworld.  They are not symlinked now, but apparently
were back last summer; /usr is at /dev/ad0s1e.

I've not yet done any of the old-libs commands; I do
have lots of ports failing with "Bad system call" and
I've got a lot of ports that wouldn't build because
"configure" was failing ("C compiler cannot create
executables").  There's more, but I'll wait until
something moves with this data, I think.

Question:  why is uname reporting the {wrong} build?

Kevin Kinsey
I despise the pleasure of pleasing people whom I despise.

More information about the freebsd-questions mailing list