Hi,People usually have the opportunity to rerun the os-prober/grub-mkconfig in case of trouble; the only exception which I can think of is when they are run by an installer (which can set the variable beforehand).Hi, and thanks for the patch. Hedayat Vatankhah <hedayatv@gmail.com> (21/01/2013):This bug is reported by one of our users, and also the patch is provided by him. And this is his comments on the provided patch: Currently, os-prober generates a great deal of debug messages to syslog. While these are certainly useful when debugging, they are just cluttering the syslog when not debugging.Except people finding themselves having some troubles with os-prober might not have set this variable, and might be happy to have logs by default. Can be (re)considered after wheezy is out, though. However, if not having the logs by default is not desirable, changing the default but letting users to disable the logging by setting a variable is still better than the current situation. At least users which want to run os-prober/grub-mkconfig regularly can disable the logging. Thanks Mraw, KiBi. |