I've read the link you've posted; but the question there has been, how to deactivate avahi-daemon. In Knoppix the daemon isn't active.

But it isn't worth to wail over avahi. In my example of syslog you can see the last successfull action of dbus at 17:24:32. Many things happen in the intervall from 17:24:32 to 17:24:49. (There is no printer connected to Knoppix.)

At 17:25:03 I get the "failed" message from dbus. Therefore the "lost" time is about 14 seconds for me.

Code:
Jun 30 17:23:59 Microknoppix syslogd 1.5.0#6.2: restart.
<snip>
Jun 30 17:24:32 Microknoppix dbus[2059]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jun 30 17:24:32 Microknoppix dbus[2059]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 30 17:24:38 Microknoppix kernel: [   49.241598] lp0: using parport0 (interrupt-driven).
Jun 30 17:24:38 Microknoppix kernel: [   49.241609] lp0: console ready
Jun 30 17:24:38 Microknoppix kernel: [   49.360701] ppdev: user-space parallel port driver
Jun 30 17:24:38 Microknoppix udev-configure-printer: add /devices/pnp0/00:07/printer/lp0
Jun 30 17:24:38 Microknoppix udev-configure-printer: Failed to get parent
Jun 30 17:24:38 Microknoppix udev-configure-printer: add /module/lp
Jun 30 17:24:38 Microknoppix udev-configure-printer: Failed to get parent
Jun 30 17:24:49 Microknoppix NetworkManager[2184]: <info> (wlan0): IP6 addrconf timed out or failed.
Jun 30 17:24:49 Microknoppix NetworkManager[2184]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Jun 30 17:24:49 Microknoppix NetworkManager[2184]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Jun 30 17:24:49 Microknoppix NetworkManager[2184]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jun 30 17:25:03 Microknoppix dbus[2059]: [system] Failed to activate service 'org.freedesktop.Avahi': timed out