OS <[EMAIL PROTECTED]> writes:
> By non blocking I meant the blocking of synchronous calls to the OS., thereby
> effectively freezing other OS calls while the OS believes it is blocked.
>
As I stated in my previous mail, yes, there are locks, but they're
here in order to prevent races. You won't let two syscalls modifying
the same directory. There is also a big kernel lock, but it's seldomly
used. And the more it goes on, the more finegrained the locks are.
> Surely OO is more than fad of the day. However it sounds like Linux is more or
> less OO by the mere fact that it is comprised of so many packages (assuming
> these packages do one thing and do it well !).
>
Yeah, but speaking of the kernel, it *is* OO. Each file/inode/block
device/whatever else has ops associated to it. OK, it's C and not true
OO as OO fanatics see it, but the fact is here.
--
fg
# rm *;o
o: command not found
