From: Jonas Wielicki <j.wielicki_at_sotecware.net>
Date: Sun, 08 Jul 2012 19:16:30 +0200

On 08.07.2012 19:08, Thomas Martitz wrote:
> Am 06.07.2012 23:53, schrieb Mike Giacomelli:
>> We can leave the actual logf code in git, and just convert the stuff
>> that makes sense over to the new system.
>
> Any log to disk would trigger Jonas' storage-related problems. I guess
> he asks if a read-only build would be possible.
Right, thats what I meant.

To add some clarification: As posted on the list before, I am struggling
with debugging issues related somehow to writing to or reading from the
SSD i built into my iriver.

Obviously, it would be nice to have a proper logger (especially since
the current logging system makes my player freeze after boot, posted
that on this list too), but if that logging system would perform disk
access, it would not only trigger an infinite recursion (I have log
calls in ata_* functions, which are used to write the log files -> log
calls -> writing -> ...).

The latter problem is intrinsic to have a logger which writes to disk or
actually uses any subsystem which uses logging. That is why one has to
take great care when implementing a sophisticated logging system.

cheers,
Jonas
Received on 2012-07-08