[arch-dev-public] rootprefix change for kmod 10
d at falconindy.com
Fri Sep 7 11:02:04 EDT 2012
On Fri, Sep 07, 2012 at 04:39:09PM +0200, Thomas Bächler wrote:
> Am 06.09.2012 21:30, schrieb Dave Reisner:
> > Hi all,
> > I've been talking to Thomas about this, and we've come to the conclusion
> > that it's probably just broken to continue shipping kmod built with a
> > rootprefix. I think there's been two recurring problems coming up that
> > make this revert warranted:
> > - It makes building kernels for other distros not fun
> > - The kernel doesn't really support it. Various Kbuild targets just
> > break with no clean fix available.
> > kmod 10 is to be released quite soon, and I'm planning on building
> > without the rootprefix. It should not affect us in any real way at this
> > point, given that /lib is now a symlink. It does mean that for the next
> > kernel built, we'll need to make a minor adjustment to the kernel
> > PKGBUILDs: running depmod before moving the module dir instead of vice
> > versa. I can fix this myself in SVN when I push kmod-10 to [testing].
> Whatever, go ahead.
> Any thoughts about a proper fix in kmod yet?
I think the proper way to do this is to introduce a new flag to
give the full path to the module dir, e.g.
depmod -M /some/chroot/usr/lib/modules -k 3.5.3-1-ARCH
...would refer to modules in /some/chroot/usr/lib/modules/3.5.3-1-ARCH
This might even get rid of rootprefix entirely, and kmod will "forever"
default to /lib/modules. Maybe in a decade this could change.
kmod-10 is in testing, and I've fixed linux and linux-lts packages in
SVN. I did a compile test of linux, installed it, and made sure kmod
still found modules. I trusted that the exact same change in linux-lts
would yield the same results. This has _not_ been archrelease'd yet, but
it will be when we move kmod to [core] (there will not be a pkgrel
bump). This of course assumes that there isn't a release of 3.5.4 before
More information about the arch-dev-public