>     effects of the I/O being in-progress.  If a user program doesn't access
>     any of the information it recently wrote the whole mechanism winds up
>     operating asynchronously in the background.  If a user program does, 
>     then the write behind mechanism breaks down and you get a stall.

What makes no sense is that it should be perfectly ok to _read_ this 
information back.

-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime.             \\  [EMAIL PROTECTED]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to