[lkml]   [2001]   [Jun]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: /dev/nvram driver
> 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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:55    [W:0.073 / U:2.476 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site