-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
motd: maintain a /etc/motd file with interesting info about the TAC #57
Conversation
I think a structured list with colored |
Hi, I've re-worked this PR now and think it is ready for review. The failing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one minor nitpick on the actual messages.
Overall I like the way to present the user with some useful information at login.
(Maybe this will even increase the number of installed updates?)
f11ed81
to
d3939dd
Compare
b1efe81
to
6d01998
Compare
Hi @KarlK90, could you have a look at this PR? |
Not anyone looks at the web interface or the display of the TAC. This gives us a third vector to convey information to the user, by showing messages on ssh login. Use bind-mounts to put the highly volatile file itself to /var/run and point to it from /etc. Signed-off-by: Leonard Göhrs <[email protected]>
Not anyone looks at the web interface or the display of the TAC.
These users will not be notified about updates or issues with the TAC.
Add a third information vector so we can reach these users as well.
This will result in messages like these when a user logs into the TAC via ssh and there is some information to display:
I think it would be nice to show a random tip if we have nothing else to say, but that should go into a separate PR.
TODO before merging: