Actually thinking about this, I believe Tux would only show on kernels newer than 2.6.20, released in 2007, or at least CONFIG_LOGO was. So it seems that kernel is a lot newer than those modules it’s loading.
It’s probably good old 2.6.32. Still deployed in heaps of places even though it’s getting close to 15 years old and has been EOL since 2016 for official support and 2018 for RHEL6/CentOS6.
Not if the kernel was built around the time of that geodeoss module from 2004.
It might have been 2.4 or maaybe 2.6 if they were on the bleeding edge (I somehow doubt it), but 2.6.32 came out five years later and I can’t believe they would have recertified a new kernel for the fun of it.
What kernel is that, 0.1?
The image I probably pretty old
Actually thinking about this, I believe Tux would only show on kernels newer than 2.6.20, released in 2007, or at least
CONFIG_LOGOwas. So it seems that kernel is a lot newer than those modules it’s loading.I think V4L was kernel 2.3 or something like that anyway.
It’s probably good old 2.6.32. Still deployed in heaps of places even though it’s getting close to 15 years old and has been EOL since 2016 for official support and 2018 for RHEL6/CentOS6.
Not if the kernel was built around the time of that
geodeossmodule from 2004.It might have been 2.4 or maaybe 2.6 if they were on the bleeding edge (I somehow doubt it), but 2.6.32 came out five years later and I can’t believe they would have recertified a new kernel for the fun of it.
I’ve never heard of that module but is it possible they’re using an older module with a newer Linux version?
Or it could be 2.4 like you said!