linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Jansen <tim@tjansen.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Automatic download and installation of drivers.
Date: Tue, 30 Oct 2001 08:26:48 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-100443029114140@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100319421829170@msgid-missing>

On Monday 29 October 2001 22:53, you wrote:
> But I don't keep my kernels in /usr/src/linux, and neither do most
> people.  And vendor kernels include a number of different .config files,
> all of them placed in a different file within the .src.rpm.  Work with
> the LSB if you want to push for this kind of standardization.

You don't have to use /usr/src/linux, the system would need its own kernel 
tree at different location (installed by the distribution or copied by a make 
target similar to modules_install when you compile the kernel yourself). You 
shouldn't even access it yourself.

For each kernel release there must be a gcc version defined, and the 
compilation system must have this gcc available. This could mean that you 
have 10 gccs (if you have 10 different kernels installed). These gcc's should 
not be in the usual PATH directories (/usr/bin..) but in a private directory.


> How would you describe the fact that between kernels x and y, the struct
> usb_serial_device changed the field "lock" from being a "struct
> spinlock_t" to being a "struct semaphore"?  Changes that that _have_ to
> have code changes to the driver made.  That's the main problem that you
> are going to run into here.

IMHO it is neccessary that stable kernels keep source compatibility.


> Remember /sbin/hotplug runs as root.  You do _not_ want to be doing any
> of these actions as root :)

But it shouldn't be a problem to su to a special user for compiling.

bye...

_______________________________________________
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:[~2001-10-30  8:26 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16  0:02 Automatic download and installation of drivers Stamatis Mitrofanis
2001-10-16  5:29 ` 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 [this message]
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-100443029114140@msgid-missing \
    --to=tim@tjansen.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).