Updated RC contains latest knot resolver, fixed localrepo from updater and few minor updates.
1 Like
update from 3.11.1 stable went without a hitch and thus far nothing in the logs, except the earlier reported btrfs output, indicating any issue with the setup/conf this end.
I find the release notes way to scarce. E.g. those package updates discovered earlier I found now others in addition such as tor.
IMHO TO owes its user base a better transparency of which packages are being updated, perhaps also a version history of TOS, and not just those cryptic snippets.
The TurrisOS 3.11.2 RC3 was downloaded and installed on my router without any problems.
Everything works fine.
2 Likes
Yesterday’s update did not start syslog-ng after stopping it to update (however, no router reboot was requested).
2019-01-11 17:44:04 info updater[20979]: transaction.lua:141 (fun): Checking for file collisions between packages
2019-01-11 17:44:05 info updater[20979]: transaction.lua:159 (fun): Running pre-install scripts and merging packages to root file system
2019-01-11 17:44:06 warning updater[20979]: backend.lua:861 (pkg_merge_files): Config file /etc/syslog-ng.conf modified by the user. Backing up the new one into /etc/syslog-ng.conf-opkg
2019-01-11 17:44:08 warning updater[20979]: backend.lua:861 (pkg_merge_files): Config file /etc/tor/torrc modified by the user. Backing up the new one into /etc/tor/torrc-opkg
2019-01-11 17:44:11 info updater[20979]: transaction.lua:205 (fun): Running post-install and post-rm scripts
2019-01-11 17:44:11 notice syslog-ng[5567]: syslog-ng shutting down; version='3.10.1'
# manual start
2019-01-12 02:23:30 notice syslog-ng[26320]: syslog-ng starting up; version='3.19.1'there are now these entries in the kernel log appearing which were never seen prior
ieee80211 phy0: failed to reallocate TX buffer
ieee80211 phy1: failed to reallocate TX buffer
Updated yutube-dl and little bit of polishing for syslog-ng.
The final version is out!