Using the new 'extramodules' directory in linux-* packages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



I'm the maintainer of nvidia-beta-all -
https://aur.archlinux.org/packages.php?ID=31123

The nature of the package is that to provide the nvidia-beta driver
for all currently installed kernels. I use some horrible tricks to
accomplish that involving scanning the kernel images in /boot

With the recent changes to include the 'extramodules' directory, I
recently found time to modify a small portion of the PKGBUILD to place
the nvidia.ko files in /lib/modules/extramodules-3.1.*/ directories
instead of in /lib/modules/3.1.*/kernel/drivers/video. Saves me (and
others) re-building of the package.

I also have my own script which does the same module-building for
virtualbox (for all kernels instead of only the running one) which
I've been using since before virtualbox-source existed (with its own
highly complete and complicated vboxbuild script). While looking at my
script and comparing it with vboxbuild from virtualbox-source, I
noticed that that script placed modules in
/lib/modules/3.1.*-*-ARCH/extramodules rather than in
/lib/modules/extramodules-3.1.*-*-ARCH

Is this (the former) location recommended over what I'm currently
doing (the latter)?

If I'm not mistaken, placing the module in the former would result in
'left-behind' symlinks/directories in /lib/modules which placing the
module in the latter would not?

Thanks for the clarification (and for reading this).


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux