i was over a week unable to use debian/fso, since fsousaged kept
segfaulting.
yesterday i learned that in frameworkd.conf there have to be new entries
to make fsousaged work as expected:
instead of
[fsousage]
[fsousage.controller]
it has to read
[fsousage]
lowlevel_type = openmoko
[fsousage.controller]
[fsousage.lowlevel_openmoko]
most likely i missed the announcement of these changes, but i checked
beside other the log, to see if either frameworkd or fsousaged would print
something useful -- to no avail.
so, what i am trying to say: fso should print WARN messages if it misses
important/sensible entries in the configs, to make it easier to detect
these faults.
i guess, fsousaged segfaulting was not really the intended reaction when
missing the entries cited above, but if it depends on these entries it
should be able to print something like:
"
WARN: lowlevel_type not defined in section fsousage -- possible
lowlevel_types could be ...
WARN: include a new section [fsousaged.lowlevel_<type>] in frameworkd.conf
"
which holds true for othter parts of fso as well, of course.
_______________________________________________
smartphones-standards mailing list
smartphones-standards@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-standards
