Sorry, it was ramib that picked up the thread and finally figured out fortune.Maybe the OP finally has changed? He was last time seen on the forums on Dec 11, 2021
Sorry, it was ramib that picked up the thread and finally figured out fortune.Maybe the OP finally has changed? He was last time seen on the forums on Dec 11, 2021
No reason for saying sorry.Sorry,
This sounds like you've been trying derivative projects. I'd suggest going upstream.Most new operating systems that were once good are now over-engineered which defeats the purpose of what they were.
cd /etc; rm motd; ln -s motd.template motdThis may not be the right audience, but I'm very displeased with FreeBSD 13 changing the traditional /etc/motd logic and turning it into what I see as over-engineered triviality which contradicts the unix philosophy. I don't know where is the right place to express my thoughts about it, sorry if this isn't one of them.
IMO, if someone wanted to make MOTD more generic/flexible - they should have written a port to automate that, rather than breaking half a century of unix motd implementations and deviating further from all other unix-like platforms; for what though? for motd? because they didn't want to periodically change a config in /etc/? I don't understand this, and until I do this will continue to seem whimsical and unnecessary.
Does anyone have a rationalization for changing something so simple yet fundamental at the cost of half century of unix lineage and interchangeability?
Lets get this fix pushed upstream!cd /etc; rm motd; ln -s motd.template motd
service motd restart
If the entire purpose was to eliminate changing /etc,
I also think the change was of dubious benefit. Having an motd service is such a pointless addition of complexity for something so trivial.If the entire purpose was to eliminate changing /etc, there was no reason for a service or template.
update_motd=NO
in /etc/rc.conf and do whatever you want with /etc/motd and/or /var/run/motd. They will never be touched by any automatism. This isn't new in FreeBSD 13 either; the “update_motd” switch exists for a very long time, dating back to the pre-rc-NG era, when /etc/rc did all of those jobs.How so, out of interest?(I am also happy the RCSID $FreeBSD$ tags have been removed.)
The same reason. I won't need to manage (unnecessary) "merge" conflicts around RCSID tags with every minor or major FreeBSD system upgrade with my versioned configuration files management.How so, out of interest?