From: "Post, Mark K" <mark.post@eds.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: writeups for hotplugging S/390 chandev, PNP docking stations
Date: Tue, 02 Apr 2002 16:34:46 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101776596106387@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101774371113065@msgid-missing>
Rick, Dave,
I read the chandev.8 file, and while it's pretty poorly formatted, the
information seems relatively good, if presented in a scattered manner. As
you commented, the developers are probably concentrating on code for the
most part.
I normally use the "Device Drivers and Installation Commands" document when
I want to refresh my memory on a particular command for a particular type of
device.
(http://www10.software.ibm.com/developerworks/opensource/linux390/docu/l390d
d07.pdf) This seems pretty clear and reasonably well-written. If Dave
finds this more acceptable, then I guess we're done. Otherwise, I would
have to think about who might be willing to translate the chandev.8 file
into something more coherent.
Mark
-----Original Message-----
From: Rick Troth [mailto:rtroth@bmc.com]
Sent: Tuesday, April 02, 2002 10:30 AM
To: David Brownell
Cc: linux-hotplug-devel@lists.sourceforge.net; mark.post@eds.com
Subject: Re: writeups for hotplugging S/390 chandev, PNP docking
stations?
I've sent to Mark Post, one of the info reference people
in the S/390 (aka: zSeries) community. Mark should be able to
recommend someone who can clear-up the description. This "chandev.8"
probably came out of the lab that produces most of the S/390 patches.
Their focus is on code, I'm sure, not doc. But someone who
understands the princ. of ops can probably make it plain.
> Also, let us know if there are hotplug scripts that
> should be incorporated into the standard toolset.
>
> I'd suspect they'd be more generally useful for the
> laptop docking stations than for the mainframes,
> but I could easily get surprised! :)
Surprise! The mainframe plugs and un-plugs all the time.
Devices get "varied online" (or offline) on demand.
The situation only gets worse when you're running Linux in a
virtual machine where one could 'hcp attach' (or detach)
things on-the-fly, both virtual and real. It's fun!
Let's just say that the mainframe Linux crowd
has been waiting for hotplug for a long time. :-)
Rebooting just to recognize a dynamic device is ... sub-optimal. :-(
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2002-04-02 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-01 22:23 writeups for hotplugging S/390 chandev, PNP docking stations? David Brownell
2002-04-02 15:30 ` Rick Troth
2002-04-02 16:34 ` Post, Mark K [this message]
2002-04-03 3:44 ` David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-101776596106387@msgid-missing \
--to=mark.post@eds.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).