>From a feature freeze POV, this is ok with me. I don't know that I agree it makes sense to reintroduce this log file now after so long if the information is available elsewhere, but I don't think I need to block this w/ release team hat.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1450588 Title: [FFe] /var/log/dmesg No Longer Being Updated Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: [FFe] * (re-)introduce a feature to ensure the initial (boot time) kernel messages are preserved * This existed up to Trusty (upstart) but was lost afterwards as it had no systemd coutnerpart. * It is a "new" feature since we have lacked it for so many releases and worth - a hopefully simple - ack by the release Team * It is not a new version or any change to the actual rsyslog code. Instead it just adds a new service "dmesg" that will achieve what was lost post trusty. Therefore the potential regression to the existing function should be minimal, if anything the new service might hit issues on some unexpected environments but atm that seems unlikely. * It does not add/remove Dependencies nor modify build * I ahve made upgrade/install tests as well as Ahasenack doing the same on the MP that is linked. --- After upgrading to Ubuntu 15.04 Vivid, /var/log/dmesg is no longer updated after boot. It appears that this was previously done via /etc/init/dmesg.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1450588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
