Upgrade 2.1.3 -> 2.1.4 odd uname output



  • On 2.1.3 my uname's output came back with the system's DNS name, on 2.1.4 I get this:

    [2.1.4-RELEASE][root@602ad0be6079]/root(1): uname -a
    FreeBSD 602ad0be6079 8.3-RELEASE-p16 FreeBSD 8.3-RELEASE-p16 #0: Fri Jun 20 13:19:04 EDT 2014     root@pf2_1_1_i386.pfsense.org:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386  i386
    

    Any ideas?



  • Hi athurdent,

    Probably related to:

    "/etc/version_kernel and /etc/version_base no longer exist, use php_uname to get the version for XMLRPC check instead."

    https://blog.pfsense.org/?p=1377



  • On a 2.1.4 full install test in a VM, I get:

    [2.1.4-RELEASE][admin@test123.mydomain.blah]/root(1): uname -a
    FreeBSD test123.mydomain.blah 8.3-RELEASE-p16 FreeBSD 8.3-RELEASE-p16 #0: Fri Jun 20 13:17:08 EDT 2014     root@pf2_1_1_i386.pfsense.org:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_SMP.8  i386
    
    

    which looks the same format as on 2.1.3



  • I have upgraded some other systems now. All OK. Maybe it's related to the fact, that this is my only system running i386 embedded kernel on a full install (Lanner Desktop FW with no VGA on a 128G SSD)?



  • @athurdent:

    On 2.1.3 my uname's output came back with the system's DNS name, on 2.1.4 I get this:

    [2.1.4-RELEASE][root@602ad0be6079]/root(1): uname -a
    FreeBSD 602ad0be6079 8.3-RELEASE-p16 FreeBSD 8.3-RELEASE-p16 #0: Fri Jun 20 13:19:04 EDT 2014     root@pf2_1_1_i386.pfsense.org:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_wrap.8.i386  i386
    

    Any ideas?

    You're not alone.  Same issue after updating from 2.1.3 to 2.1.4 (amd64)

    FreeBSD CPE00e0666e16dd 8.3-RELEASE-p16 ... 
    

    Tried to update the hostname, but it does not persist.  All the system log file entries have this name appended as well.



  • @paradigm13: What kernel are you using (VGA or Serial)? Is this a full install or Nano? What architecture, i386 or amd64?



  • Just update 2.1.3 to 2.1.4 and its all oki.. but i dont feel the difference between my previous 2.1.3 and 2.1.4



  • Issue has been resolved:
    https://github.com/pfsense/pfsense/commit/7b15d22967a9f9fefe7b8b11fa2d68c762c55219

    Applied it via System Patches and rebooted, problem gone.
    Thanks to the pfSense team!