From: "Rick Troth" <Rick_Troth@bmc.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: writeups for hotplugging S/390 chandev, PNP docking stations ?
Date: Fri, 12 Apr 2002 17:26:08 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101863246509593@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101784584525142@msgid-missing>
> 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 ...)
I can't speak to this,
but I'm sure the S/390 subdivision of the Linux community
would like to see it fixed.
> 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,
Yes.
> and that tr0 is token ring (it still lives? :), but I have
Token ring, yes. Still lives in some corners.
> 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?
CTC is "channel-to-channel" which is a point-to-point thing
conceptually like two SCSI chains having a bridge between them.
Mainframe also has a network interface known as IUCV
(iucv0, iucv1, etc), but that has no representation in real hardware
so I don't know if it would really fit in the "chandev" suite.
> 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
Thanks for keeping it current.
I for one very much value the commonality
and hope that S/390 will be able to use most of this infrastructure
rather than re-invent it.
_______________________________________________
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-12 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-03 7:10 writeups for hotplugging S/390 chandev, PNP docking stations ? David Brownell
2002-04-12 17:26 ` Rick Troth [this message]
-- 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-101863246509593@msgid-missing \
--to=rick_troth@bmc.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).