public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Theodore Ts'o" <tytso@mit.edu>,
	Dustin Kirkland <dustin.kirkland@us.ibm.com>,
	Kylene Jo Hall <kjhall@us.ibm.com>,
	kbuild-devel@lists.sourceforge.net,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] make: add modules_update target
Date: Sun, 16 Apr 2006 20:24:59 +0200	[thread overview]
Message-ID: <20060416182459.GA4409@mars.ravnborg.org> (raw)
In-Reply-To: <20060415150208.GB19708@thunk.org>

On Sat, Apr 15, 2006 at 11:02:08AM -0400, Theodore Ts'o wrote:
> On Sat, Apr 15, 2006 at 10:40:58AM +0200, Sam Ravnborg wrote:
> > The problem to be solved is the long time it takes to do
> > "make modules_install" when working on a single module.
> > Instead of bringing in more or less complex solutions what about
> > extending "make dir/module.ko" to include the installation of the
> > module.
> > 
> > Something like:
> > "make MI=1 dir/module.ko"
> > where MI=1 tells us to install the said module.
> 
> Um, wouldn't that imply that either (a) the compile is being done as
> root, or (b) the /lib/modules/* is writeable by a non-root userid?  I
> suppose the install command could be prefixed by sudo, but that seems
> awkward (and not everyone uses sudo).

kbuild has support for the above scenario already - I just forgot.
Say you are hacking ext3.
Do a successfull make and install all modules.
Manually remove the ext3 module from /lib/modules/...
And use the external module support in kbuild like this:

# Got to relevant directory
$> cd fs/ext3

# To build the module:
$> make -C ../.. M=`pwd`

# To install the module:
$> make -C ../.. M=`pwd` modules_install

	Sam

      reply	other threads:[~2006-04-16 18:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 15:06 [PATCH] make: add modules_update target Kylene Jo Hall
2006-04-14 17:02 ` Theodore Ts'o
2006-04-14 18:00   ` Avi Kivity
2006-04-14 18:29     ` Dustin Kirkland
2006-04-14 19:02       ` Avi Kivity
2006-04-15  0:33         ` Dustin Kirkland
2006-04-15  0:33   ` Dustin Kirkland
2006-04-15  8:40     ` Sam Ravnborg
2006-04-15 15:02       ` Theodore Ts'o
2006-04-16 18:24         ` Sam Ravnborg [this message]

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=20060416182459.GA4409@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=dustin.kirkland@us.ibm.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=kjhall@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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