From: Linas Vepstas <linas@austin.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [Pcihpd-discuss] Hotplug SIG
Date: Mon, 23 Aug 2004 22:57:34 +0000 [thread overview]
Message-ID: <20040823225734.GB14002@austin.ibm.com> (raw)
In-Reply-To: <20040812191345.GA12936@parcelfarce.linux.theplanet.co.uk>
On Thu, Aug 12, 2004 at 12:58:28PM -0700, Greg KH was heard to remark:
>
> And yes, I completly agree that these need to be separate "SIGs". The
> only thing these three groups have in common is one word.
Greg, this is not entirely true. It would be very cool if there
was a gnome/KDE graphical client that drew some kind of topology/tree
diagram of all the various devices in ones system (be they memory, cpu,
pci, scsi, etc.) and then, by mouse-clicking on the matching icon,
you got info about that devices geographical location, an option
menu to add/remove, status bits, etc.
This kind of management client crosses the boundaries of the various
hotplug sigs.
--linas
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
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:[~2004-08-23 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-12 19:13 [Pcihpd-discuss] Hotplug SIG Matthew Wilcox
2004-08-12 19:32 ` Matthew Wilcox
2004-08-12 19:58 ` Greg KH
2004-08-12 20:15 ` Silbermann, Martine
2004-08-23 22:57 ` Linas Vepstas [this message]
2004-08-23 23:13 ` Greg KH
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=20040823225734.GB14002@austin.ibm.com \
--to=linas@austin.ibm.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).