Well, Teej, I've tested it on my Hardy as you suggested after enabling backports and making a full update with it. No changes.
I mean after setting BOOTLOGD_ENABLE=yes in /etc/default/bootlogd and setting bottlogd to be started at boot time nothing was logged on my machine. The only thing I can see is the same sacramental phrase:"Nothing has been logged yet." One more detail if it helps. The Hardy on my laptop is not a clean install but an upgrade from Feisty to Gutsy and then to Hardy. I have a clean install on my desktop but I'm rather reluctant to use backports on it, since it is my main machine. I may change up my mind if you convince me though. :-) I do not know if it might make any difference. -- bootlogd not working (sysvinit) https://bugs.launchpad.net/bugs/125710 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
