All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stamatis Mitrofanis <ewstam@softhome.net>
To: linux-hotplug@vger.kernel.org
Subject: Automatic download and installation of drivers.
Date: Tue, 16 Oct 2001 00:02:37 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-100319421829170@msgid-missing> (raw)

Automatic download and installation of drivers. That is definately a 
good thing to have (in general). What we need now is to find:
- the best way to to use HTTP for the task.
- the best way to organize scripts/programs to have a general framework 
for requesting drivers of all kinds.
- actual database servers which are globally accessible to do the work.
- actual manufacturers to simply provide downloads in their ftp servers.

For HTTP there can be simple name=value requests that are passed to the 
server's CGI. The server redirects the client to where the actual file 
resides. The following holds:


wget http://www.kernel.org/cgi-bin/getdriver?bus=usb&pid=0x1234&vid=0x5678 <http://www.kernel.org/cgi-bin/getdriver?bus=usb&pid=0x1234&vid=0x5678>

Afterwards, the driver will get installed.

For the hotplug scripts I suggest that we create a new driver.agent 
which will process four actions (fetch/toss/install/uninstall) with 
appropriate parameters. It will be triggered by any other hotplug agent 
requiring a certain "resource" to satisfy an important request. The key 
thing here is that it should be acceptable to use the standard 
input/output of an agent.script when its called (like an ordinary 
program -- diagnostics should be sent to either stderr or syslog of 
course). This will be useful here since it's not very convenient to pass 
name=value pairs in the form of environment variables. Defining std 
input/output as "may be useful" for the hotplug scripts should be a good 
thing. install/uninstall get the DRIVER_RESOURCE parameter which is the 
local filename of the downloaded file. If a .tar.gz, they can guess the 
directory it unpacks to.

If anyone has any better ideas/suggestions, please let me know. I'm 
already working on the client-side for this (done install/uninstall for 
"targz.agent" driver subagent). It should be pretty easy to make the 
server-side DB and CGI linking to it.

Anyone to help?


_______________________________________________
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

             reply	other threads:[~2001-10-16  0:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16  0:02 Stamatis Mitrofanis [this message]
2001-10-16  5:29 ` Automatic download and installation of drivers Greg KH
2001-10-16  7:35 ` David Brownell
2001-10-16  7:58 ` Tim Jansen
2001-10-16 11:38 ` Keith Owens
2001-10-16 16:52 ` Greg KH
2001-10-16 18:44 ` Tim Jansen
2001-10-16 18:58 ` Tim Jansen
2001-10-16 19:19 ` Greg KH
2001-10-17  2:01 ` David Brownell
2001-10-17  2:03 ` David Brownell
2001-10-17 18:47 ` Tim Jansen
2001-10-17 19:24 ` David Brownell
2001-10-17 23:31 ` Tim Jansen
2001-10-17 23:32 ` Greg KH
2001-10-18  0:07 ` Dmitri
2001-10-18  0:19 ` Stamatis Mitrofanis
2001-10-18  0:47 ` Tim Jansen
2001-10-18  2:17 ` Keith Owens
2001-10-18  2:35 ` Dmitri
2001-10-29 21:53 ` Greg KH
2001-10-30  8:26 ` Tim Jansen
2001-10-30 17:21 ` Greg KH
2001-10-30 21:24 ` Tim Jansen
2001-10-30 21:51 ` Dmitri
2001-10-31 12:36 ` Keith Owens
2001-10-31 20:49 ` 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=marc-linux-hotplug-100319421829170@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.