Carsten Otte wrote:
John Summerfied wrote:
No it will not _if_ the lock is done where it belongs: system kernel, not
flock or sysfs or whatever vehicle that locks in userspace.
That's what vmcp does, and that's what would work for other diagnoses in
a similar way.
so how's the VM return code getting back to a script? As I recall that
was one of the problems raised early in the thread.
The return code delivery to the script is a pure userspace problem. My
comment is about the interface to the system kernel.
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.
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/
do not reply off-list
----------------------------------------------------------------------
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
