On 2024-02-15, b...@fea.st <b...@fea.st> wrote: > So I was curious, am I the only one using automatic OS updates > in cron to keep the fish fresh and the bits dust free? > > I think I read somewhere that it's not recommended but I'm not > running a server so it seems like a good idea to me. > > /etc/crontab: > > # Example of job definition: > # .---------------- minute (0 - 59) > # | .------------- hour (0 - 23) > # | | .---------- day of month (1 - 31) > # | | | .------- month (1 - 12) OR jan,feb,mar,apr ... > # | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR > sun,mon,tue,wed,thu,fri,sat > # | | | | | > # * * * * * user-name command to be executed > 0 3 * * * root sysupgrade
You should read upgrade notes (faq/current.html for -current, faq/upgradeXX.html for releases) *before* upgrading. For -current you should really be aware of commits (read src-changes) so you can identify times which would be bad to update (often best to hold off for a few days after a major library bump or major perl version update in order that new packages are available). -- Please keep replies on the mailing list.
