Messages in this thread |  | | Subject | Re: /dev/nvram driver | Date | Fri, 22 Jun 2001 23:07:10 +0100 (BST) | From | Alan Cox <> |
| |
> Currently it tracks O_EXCL on open() and sets a flag, whereby no other > open() calls can succeed. Is this functionality really needed? Perhaps it > should just be a reader/writer model : n readers or 1 writer. In that > case, should open() block on a writer, or return -EBUSY?
Several tools expect that mode of behaviour so that they can atomically recompute the checksum when writing low bytes of the CMOS - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |