Christoph Hellwig wrote:
On Thu, Oct 13, 2005 at 08:12:57AM +0800, John Summerfied wrote:
David Boyes wrote:
If process acquires lock on /sysfs/zvm/diag/8/lock (ie flock succeeds),
then
write CP command into cmdstring to prepare for call. Once parameters are
loaded, open of /dev/diag8 and write a 1 to /dev/diag8 to execute the
I don't understand why you would use a device for this which seems to me
is just another control function. Doesn't this function belong in sysfs too?
Because sysfs exposes attributes. Everything that's a request / reponse
just like the pcmcia stuff that's already there.
call to some underlying layer (be it hardware or software) is
fundamentally ill-suite for sysfs.
I don't see how proposed diagnose instructions are inherently different
from what seems to be in sysfs now.
I note that hotplug uses sysfs on 2.6 kernels to load firmware on my
Debian-based access point.
I do not see any devices on this system whose primary purpose is to
control the environment. I won't rule out the possibility of something
loading firmware into SCSI cards there, but USB is more recent and the
evidence before me is that sysfs is the way it's going.
Or, is someone going to tell me hotplug's doing it wrongly?
--
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
