> closed. But more importantly further access to it can be blocked until
> appropriate actions are taken which also applies with your example, no? Is
That bit is hard- very hard.
> it possible to open for execute and have dirty mappings (or open for
> write) on a file at the same time?
If I want I can have 16 threads executing code in a shared object being
written to by ten other programs at once and shared over a network while
we are at it. Its probably not a good idea but I can do it if I have
reason to.
Unix and Linux likewise take the basic view that locking is a problem for
the user, while file permissions prevent it being made a problem for
other users.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
