Radek Podgorny

> If the mount_point is within a branch ...what would be the use-case for doing this?

hmmm, this seems to be an issue deeper in fuse itself. the passthrough example from the libfuse examples behaves the same...

not sure, yet. maybe it's some kind of internal limitation that fuse is unable to work with character devices (or maybe no special files at all?)... or maybe i'm just...

nikolaus, what would be needed to implement proper special device handling in fuse (so it could be implemented without the "as regular" hacks)? some kernel side changes or is only...

it's more like nobody just has time rather than not really caring... ;-) ...reopening until this bug proves false or someone fixes it (just writing a test case to reproduce...

yeah, i've removed mentions of "use_ino" from examples and documentation. will be in next release.

@aakefbs hmmm, actually i'm quite hesitant in doing so - i am afraid that by requiring a c++ compiler (with its lots-of-memory-required-during-compilation, some-exotic-platforms-not-fully-supported, etc.) we'll be limiting the number of...

ok, then, i agree... ...so let's make this a two-phase thing: first, let's make usyslog compile-time selectable (with the current buggy implementation). second, if you feel like replacing the current...

> I hope I get a patch ready in the next 3 days - I think I found an easy splice way in plain C. Just very hard to find...

thanks for the (independent) feedback! ...i'll try to spare some to review the patch. first impressions from a quick look: 1) why the heuristic? why not just strictly decide by...