motd: stop prepending "uname -v" output dynamically

[michaelo]

Summary

Make the motd generation completely static with this change.
Prepending the output of uname(1) may lead to confusing and/or incorrect
output if you are in a jail which has a different version of world
compared to the jailhost kernel/world. For those who need a fully
dynamic motd can still use sysutils/dynamic_motd port.

PR: 276763
Approved by: jrm (mentor), otis (mentor), emaste

[michaelo]

This one comes from: https://github.com/BastilleBSD/bastille/issues/393

Feel free to add someone you think appropriate to review.

[jrm]

I don't have strong options either way. On the one hand, I can appreciate how this would confuse some users when they log in to a jail. On the other hand, I expect some users would miss seeing this information (by default) when they log in. While it may also be confusing, it's reporting accurate information that many would expect, i.e., version information about the running kernel.

Brainstorming ideas, what about appending something like this to /var/run/motd?

echo "$(hostname) $(uname -smi) running kernel/userland: $(uname -r)/$(freebsd-version -u)"

In a 14 jail running on a 15-CURRENT host, the output looks like this.

myhostname FreeBSD amd64 GENERIC-NODEBUG running kernel/userland: 15.0-CURRENT/14.0-RC4

[michaelo]

In D43703#1000910, @jrm wrote:

I don't have strong options either way. On the one hand, I can appreciate how this would confuse some users when they log in to a jail. On the other hand, I expect some users would miss seeing this information (by default) when they log in. While it may also be confusing, it's reporting accurate information that many would expect, i.e., version information about the running kernel.

Brainstorming ideas, what about appending something like this to /var/run/motd?

echo "$(hostname) $(uname -smi) running kernel/userland: $(uname -r)/$(freebsd-version -u)"

In a 14 jail running on a 15-CURRENT host, the output looks like this.

myhostname FreeBSD amd64 GENERIC-NODEBUG running kernel/userland: 15.0-CURRENT/14.0-RC4

Yeah, I am open as well. What I would like to see is consistency: either no information or always correct information. What I don't know whether we should try to add something which is done by sysutils/dynamic_motd already. I also wonder whether both freebsd-version -r/freebsd-version -u can also confuse users. While we could introduce a parameter with none, kernel, userland, both, but then we are back with sysutils/dynamic_motd.

[michaelo]

Any other opinions?

[michaelo]

Remove MFC since it might violate POLA.

How to proceed with this review? I still have the feeling that we shouldn't try
two replicate the dynamic motd port here.

[ziaee]

How to run commands in the motd?

[michaelo]

In D43703#1115554, @ziaee wrote:

How to run commands in the motd?

You can't, you have to switch to sysutils/dynamic_motd.

[michaelo]

Folks, is this change something we should abandon or still worth considering for 15?

[michaelo]

Rebase...

Should we (re)consider this for 16-CURRENT or abandon?