linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Hilst Selli <danielhilst@gmail.com>
To: linux-modules@vger.kernel.org
Subject: Re: [PATCH] depmod: New option for m-i-t prior 3.6 compatibility
Date: Wed, 23 Jul 2014 10:27:05 -0300	[thread overview]
Message-ID: <53CFB829.7060006@gmail.com> (raw)
In-Reply-To: <53CFB7FC.5020906@gmail.com>


On 07/22/2014 06:27 PM, Lucas De Marchi wrote:
> On Mon, Jul 21, 2014 at 4:33 PM, Daniel Hilst SellI
> <danielhilst@gmail.com> wrote:
>> New option (-N, --no-relative) create databases with absolute paths.
>> This option is made to create databases compatible with
>> module-init-tools prior 3.6 version.
>
> What's the use case here? Do you want a newer depmod to create a
> database to be read by ancient modprobe (from 2008 as far as I could
> check)? Why?
>
> If it was the opposite (make modprobe to work with old database), I
> could understand. But I can't really see why you are doing this here
> and it just sounds crazy to me.
>
>
> Lucas De Marchi
>
I work with embedded systems from 2009, which use modprobe from m-i-t
3.4, updating m-i-t means update tons of nodes. Of course I can simply
run depmod from target and get everything fixed, but this creates a
dependence of running stuff after installing the image, which is
unproductive. I want images working out-of-box after generated.

So I patched depmod to generate databases compatible with my old
systems, without harming new features.

Cheers,



       reply	other threads:[~2014-07-23 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53CFB7FC.5020906@gmail.com>
2014-07-23 13:27 ` Daniel Hilst Selli [this message]
2014-07-21 19:33 [PATCH] depmod: New option for m-i-t prior 3.6 compatibility Daniel Hilst SellI
2014-07-22 21:27 ` Lucas De Marchi

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=53CFB829.7060006@gmail.com \
    --to=danielhilst@gmail.com \
    --cc=linux-modules@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).