From: Jon Masters <jonathan@jonmasters.org>
To: maximilian attems <max@stro.at>
Cc: Frans Pop <elendil@planet.nl>,
518412@bugs.debian.org, md@linux.it,
Jon Masters <jcm@jonmasters.org>,
linux-kernel@vger.kernel.org,
linux-modules <linux-modules@vger.kernel.org>
Subject: Re: linux-2.6 install errors due to incompatible depmod files [was Re: Bug#518412: initramfs-tools: must support relative paths in modules.dep ]
Date: Thu, 19 Mar 2009 16:30:30 -0400 [thread overview]
Message-ID: <1237494630.31294.31.camel@perihelion.bos.jonmasters.org> (raw)
In-Reply-To: <20090319201310.GI3901@baikonur.stro.at>
On Thu, 2009-03-19 at 21:13 +0100, maximilian attems wrote:
> [ adding jcm and lkml to Cc: ]
[ You want linux-modules@vger.kernel.org rather than LKML. I've added
the former to the CC list, we can kill LKML off the CC shortly. ]
> > That would mean that m-i-t has created a backwards incompatibility problem
> > _with itself_ and that the problem actually is "installing a kernel, that
> > was built on a system with new m-i-t, on a system with old m-i-t".
Looks like the problem is actually that depmod was run under the newer
version and then you tried to use the generated files with an older
modprobe. I'm not sure that's actually an error - it was noted that the
slight format change was unideal for such unlikely cases and in fact we
won't do that again in the future. But if you were just moving forwards
from one release to the next you would have been fine - you're talking
lack of forward compatibility actually.
Unless I'm missing something, in which case please clarify. I would like
it also if you'd send me the generated files, distro info, etc.
Jon.
prev parent reply other threads:[~2009-03-19 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090319153604.GB7954@stro.at>
[not found] ` <200903191843.28437.elendil@planet.nl>
[not found] ` <20090319181031.GH3901@baikonur.stro.at>
[not found] ` <200903191940.47726.elendil@planet.nl>
2009-03-19 20:13 ` maximilian attems
2009-03-19 20:30 ` Jon Masters [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=1237494630.31294.31.camel@perihelion.bos.jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=518412@bugs.debian.org \
--cc=elendil@planet.nl \
--cc=jcm@jonmasters.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=max@stro.at \
--cc=md@linux.it \
/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
all inboxes | Powered by JetHome®