John Summerfied wrote: > The kernel implementation can make it easy, or it can make it hard. > > The kernel support for loading blobs of firmware into devices makes it > easy to do in scripts; the use of devices and ioctls make it hard. As pointed out before, if userspace locks are used to lock a kernel resource this is either broken (deadlock when program crashed after the lock was aquired) or racy (no locking, or timeout scheme). The ease of use from a shell script or whatever program language is a pure userspace problem and should be solved there - not in the OS kernel. Shell scripts can call programs that handle the details for them. --
Carsten Otte IBM Linux technology center ARCH=s390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
