[systemd-devel] Problems with systemd master

Koen Kooi koen at dominion.thruhere.net
Sat Feb 15 02:22:16 PST 2014

Op 14 feb. 2014, om 19:16 heeft Greg KH <gregkh at linuxfoundation.org> het volgende geschreven:

> On Fri, Feb 14, 2014 at 02:30:00PM -0300, Cristian Rodríguez wrote:
>> El 14/02/14 13:32, Richard Purdie escribió:
>>>> Both conditions are checked, can you find out why the second seems to
>>>> fail too, it shouldn't?
>>>> CONFIG_FHANDLE is in your kernel?
>>> No, it wasn't. I enabled that and that image started working better,
>>> thanks!
>> I believe we should throw a big fat warning when this feature is disabled..
>> I wonder what 's the most proper way to test this at runtime though.
> Just test if the syscall is actually there or not, should be easy enough
> to test for, unless glibc wraps it up and "emulates" it if it is not in
> the kernel.

I wish CONFIG_IKCONFIG_PROC=y was mandatory, it would make debugging (and checking) these kind of things a lot easier!



More information about the systemd-devel mailing list