From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: writeups for hotplugging S/390 chandev, PNP docking stations ?
Date: Wed, 03 Apr 2002 07:10:50 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101784584525142@msgid-missing> (raw)
> 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/l390dd07.pdf)
Luckily Acrobat has a "find", and the hotplug discussion starts at the
front of chapter 8. (It's not in the index or TOC ... :)
The hotplug script there doesn't follow the conventions of the
linux-hotplug project; that'd involve "/etc/hotplug/chandev.agent"
as the script doing the magic. Which means that the network
hotplug events will get ignored ... why is that? Seems to me
more natural to do network administration through network
hotplug events, not chandev ones! (The /sbin/hotplug script
normally delegates the work to /etc/hotplug/$1.agent ...)
> This seems pretty clear and reasonably well-written. If Dave
> finds this more acceptable, then I guess we're done.
I believe there's a bunch left unsaid there about what the
device names indicate. I'd hope that eth0/eth1/eth2 are all
Ethernet, and that tr0 is token ring (it still lives? :), but I have
no clue what "ctc0" would be or, in general, how and what
those names are. Wouldn't disk drives show up there?
And tape backup units, etc?
What I'll do is stick a pointer to it, and update the linux-hotplug
webpage about "chandev" to present some of that info. My
understanding is that the management of mainframes has its
own families of idiosyncracies, developed over decades, that
it's not worth my time to master ... :) For now I'm happy just
to keep the subsystem information current on the web
- Dave
_______________________________________________
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 reply other threads:[~2002-04-03 7:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 7:10 David Brownell [this message]
2002-04-12 17:26 ` writeups for hotplugging S/390 chandev, PNP docking stations ? Rick Troth
-- strict thread matches above, loose matches on Subject: below --
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-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-101784584525142@msgid-missing \
--to=david-b@pacbell.net \
--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).