Hi Martin,
Od: Martin Sucha "this is a side effect of my change in mainline,2054. The log messages are stored both to kernel log buffer, kernel text output buffer and file(s), but mere printing uses just kernel text output (it does not make sense to log every print call to stdout as individual log message)." I see. "My intention was to convert all the servers to use logger instead of printing messages to stdout/stderr (taskdump should probably use it too if not called interactively). I just have not managed to work on converting the servers yet, sorry."So are you planning to remove the ability to direct stdout/stderr to kernel log altogether? I think it's still useful and so I would like to see the text not only in kcon, but also logged to a file. "" "You can either add KLOG_PRINTF call to uspace/lib/c/generic/io/io.c:385 as a workaround (this will log each write to the stream as a separate kernel log message, which would end up in /log/kernel) or alter the server(s) you are interested in to use the userspace logger." Yes, but what about *kernel* messages? The kernel itself prints messages during boot, when a task is killed (not taskdump, but kernel itself prints a message and stacktrace) and on other occasions. These are now only seen in kcon. Also if I go to kcon and run some commands - e.g. tests, my input and the output used to be logged to a file aswell, but now it's not. That's not acceptable, really. Kernel console output must be viewable from a GUI terminal (ideally I would *control* kcon from the terminal). All in all I think some serious gaps have been introduced here that need to be addresses before 0.6.0. Cheers, Jiri
_______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
