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 as of e2fsprogs-1.38. >> fsck -A does all filesystems in fstab in one run, and the single case >> apparently defaults to one thread. >> >> I didn't say it was a good design... :) 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). > In fact, I expect a core Unix utility to be grown up in the good old Unix > school, i.e. fork() and exec()! It is. :) > We met The One* Unix coder thinking "I like new things!". Thankfully, Ted Ts'o is not a Nazgul (despite his close involvement in the flashy new things of Kerberos and IPSec). -- `I must caution that dipping fingers into molten lead presents several serious dangers.' --- Jearl Walker ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
