linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stamatis Mitrofanis <ewstam@softhome.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Unloading drivers, start-up, shut-down and some clean-ups
Date: Thu, 20 Dec 2001 21:28:34 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-100888380501845@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100190866102262@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 1834 bytes --]

Harald Barth wrote:

> A while ago Stamatis Mitrofanis wrote something about a rewrite of the
> hotplug scripts to support start/stop as the *.rc scripts do. As I
> think this is the right thing to do (This $REMOVE thingie looks ugly).
> I wonder what happened after the mail 10/05/2001 21:13:53.
> 
> Did someone consider the changes proposed?
> Did someone get to some conclusion?


If nothing else, then somebody at least do the *.agent *.rc script 
unification! (please?)

> Someone did save that tarball? ...

Well, I have... Sorry for not providing a series of patches but I started

rewriting the scripts from nothing (occasionally borrowing some code from

the old scripts, though, but mostly rewriting everything).


I have the newest tarball included as an attachment. Take a look at it. 
It doesn't want to be in just my hard disk any more.

I did all this because the scripts seemed a little ugly to me:
* redundant .rc scripts
* no uniform directory naming (.handmap .distmap .usbmap blacklist...)
* ugly indenting of scripts
* nonextensible, restrictive, RedHatish central hotplug.functions file
* no per-subsystem configuration files or subdirectories (pesky CVS 
subdirs...)
* no per-subsystem-driver map files (for drivers that don't provide the 
information internally)
* USB start event not trigerred by PCI driver-specific script
* didn't work well with a non-highly-modular kernel
* <your favorite inconvenience here>

To see the solutions I suggest, _just take a look at the scripts_. I've 
included a couple of example driver agents too.

Also on hotplug...

I set up the scripts to call wget and use a simple format for queries

to automatically download drivers from some central server. It's quite

a simple design, but flexible. See the scripts for more. I know I have

put plenty of descriptive comments.


[-- Attachment #2: linux-hotplug-2001_12_20.tar.gz --]
[-- Type: application/octet-stream, Size: 24357 bytes --]

  parent reply	other threads:[~2001-12-20 21:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01  1:13 Unloading drivers, start-up, shut-down and some clean-ups Stamatis Mitrofanis
2001-10-05  8:09 ` David Brownell
2001-10-06  4:13 ` Stamatis Mitrofanis
2001-12-18 14:25 ` Harald Barth
2001-12-20 21:28 ` Stamatis Mitrofanis [this message]
2001-12-26 22:49 ` Stamatis Mitrofanis
2001-12-27 17:20 ` 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-100888380501845@msgid-missing \
    --to=ewstam@softhome.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).