slocate prints a message to run /etc/cron.daily/slocate.cron when there isn't an existing slocate database. slocate.cron (which runs slocate -u) does as well :). After that point (as there is now a database), everything works fine, but that slocate warning message is going to end up getting sent to root in an e-mail from crond, telling him to run slocate.cron...
Winston Beta 4 does the same thing, and root is sent an email immediately upon the first system boot.
Hm, didn't see this in Pinstripe anymore (I've to confess that I didn't specially look for it, but more than 1 day is over and I did at least not get a mail). Can anybody confirm this? Think we can close this.
Yes, this got fixed.