linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [PATCH] hotplug usb.rc changes
Date: Wed, 11 Jun 2003 06:29:52 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-105531347418847@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105529235705938@msgid-missing>

 On Tue, Jun 10, Bill Nottingham wrote:

> David Brownell (david-b@pacbell.net) said: 
> > Olaf Hering wrote:
> > > I missed /etc/sysconfig/hotplug in usb.rc, fixed patch:
> > > 
> > > - do not use /etc/sysconfig/usb anymore, use /etc/sysconfig/hotplug
> > >   instead
> > 
> > But is anything except USB using that?  This is an area it'd
> > be good to see RedHat, SuSE, and others agree, but I'd take
> > SuSE as a start.
> 
> We just have the stock references to /etc/sysconfig/{pci,usb};
> we don't use /etc/sysconfig/hotplug.

I see no /etc/sysconfig/{pci,usb} on a redhat system, but hotplug is
installed.

Such a sysconfig file would make sense to add static drivers that must
be loaded at hotplug start, but that may not trigger events.

The hostcontroller list is maybe not needed, pci hotplug could take care
of this. The potential problem that I see with pci hotplug is, that it
does load all drivers for a system, it loads them in a random order
(unverified), and it could load the wrong ones (uhci/usb-uhci).
Loading buggy drivers could lead to crashes, loading them in random
order could reorder your network interfaces if there are more than one
kind of network card (eth0 could become eth1), and so on.
I have an ieee1394.rc script for that reason, just to avoid pci.rc
usage.

Further, we have a patch to beep on /dev/console when a driver is
loaded. And also a patch that allows more verbose logging of hotplug
events.
So we have now 4 users of such a /etc/sysconfig/hotplug file.

Now, Debian has its stuff in /etc/default/... Too bad that the standard
leaves the sysconfig stuff undefined.



Gruss Olaf

-- 
USB is for mice, FireWire is for men!


-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.
_______________________________________________
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

  parent reply	other threads:[~2003-06-11  6:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11  0:43 [linux-usb-devel] Re: [PATCH] hotplug usb.rc changes David Brownell
2003-06-11  2:04 ` Bill Nottingham
2003-06-11  6:29 ` Olaf Hering [this message]
2003-06-11 16:22 ` Bill Nottingham
2003-06-11 17:00 ` Olaf Hering
2003-06-11 18:15 ` Bill Nottingham
2003-06-12 19:43 ` David Brownell
2003-06-12 19:45 ` Bill Nottingham
2003-06-12 20:10 ` David Brownell
2003-06-12 20:19 ` Olaf Hering

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-105531347418847@msgid-missing \
    --to=olh@suse.de \
    --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).