> e2fsprogs-1.38/misc/fsck.c:check_all() repeatedly invokes fsck_device(),
> which invokes execute(), which does a perfectly normal fork()/exec().
> No threads here. Nor is there use of aio_*(), which might use threads
> (well, POSIX allows it).
Sorry, and what's the conclusion?
fork() calles set
On Sun, 11 Dec 2005, [EMAIL PROTECTED] whispered secretively:
> On Sunday 11 December 2005 07:34, Rob Landley wrote:
>> On Friday 09 December 2005 12:39, Antoine Martin wrote:
>> > I wasn't even thinking about that! So true, why on earth would fsck
>> > require threading!?
It doesn't, at least not
