One - The Linux Kernel Archives

More documents

Recommendations

Info

194 • Linux Symposium 2004 • Volume One state. However, when a remove completes, you would be left in the Not in Tree state. Here are two sample remove commands: # dkms remove -m megaraid2 -v 2.10.3 -k 2.4.21-4.ELsmp # dkms remove -m megaraid2 -v 2.10.3 --all With the first example remove command, your module would be uninstalled and if this module/module-version were not installed on any other kernel, all traces of it would be removed from the DKMS tree all together. If, say, megaraid2/2.10.3 was also installed on the 2.4.21-4.ELhugemem kernel, the first remove command would leave it alone and it would remain intact in the DKMS tree. In the second example, that would not be the case. It would uninstall all versions of the megaraid2/2.10.3 module from all kernels and then completely expunge all references of megaraid2/2.10.3 from the DKMS tree. Thus, remove is what cleans your DKMS tree. 5.4 Miscellaneous DKMS Commands 5.4.1 Status DKMS also comes with a fully functional status command that returns information about what is currently located in your tree. If no parameters are set, it will return all information found. Logically, the specificity of information returned depends on which parameters are passed to your status command. Each status entry returned will be of the state: “added,” “built,” or “installed,” and if an original module has been saved, this information will also be displayed. Some example status commands include: # dkms status # dkms status -m megaraid2 # dkms status -m megaraid2 -v 2.10.3 # dkms status -k 2.4.21-4.ELsmp # dkms status -m megaraid2 -v 2.10.3 -k 2.4.21-4.ELsmp 5.4.2 Match Another major feature of DKMS is the match command. The match command takes the configuration of DKMS installed modules for one kernel and applies this same configuration to some other kernel. When the match completes, the same module/module-versions that were installed for one kernel are also then installed on the other kernel. This is helpful when you are upgrading from one kernel to the next, but would like to keep the same DKMS modules in place for the new kernel. Here is an example: # dkms match --templatekernel 2.4.21-4.ELsmp -k 2.4.21-5.ELsmp As can be seen in the example, the −−templatekernel is the “match-er” kernel from which the configuration is based, while the -k kernel is the “match-ee” upon which the configuration is instated. 5.4.3 dkms_autoinstaller Similar in nature to the match command is the dkms_autoinstaller service. This service gets installed as part of the DKMS RPM in the /etc/init.d directory. Depending on whether an AUTOINSTALL directive is set within a module’s dkms.conf configuration file, the dkms_autoinstaller will automatically build and install that module as you boot your system into new kernels which do not already have this module installed. 5.4.4 mkdriverdisk The last miscellaneous DKMS command is mkdriverdisk. As can be inferred from its name, mkdriverdisk will take the proper
Linux Symposium 2004 • Volume One • 195 sources in your DKMS tree and create a driver disk image for use in providing updated drivers to Linux distribution installations. A sample mkdriverdisk might look like: You have built the megaraid2 device driver, version 2.10.3, for two different kernel families (here 2.4.20-9 and 2.4.21-4.EL), on your master build system. # dkms mkdriverdisk -d redhat -m megaraid2 -v 2.10.3 -k 2.4.21-4.ELBOOT Currently, the only supported distribution driver disk format is Red Hat. For more information on the extra necessary files and their formats for DKMS to create Red Hat driver disks, see http://people. redhat.com/dledford. These files should be placed in your module source directory. 5.5 Systems Management with DKMS Tarballs As we have seen, DKMS provides a simple mechanism to build, install, and track device driver updates. So far, all these actions have related to a single machine. But what if you’ve got many similar machines under your administrative control? What if you have a compiler and kernel source on only one system (your master build system), but you need to deploy your newly built driver to all your other systems? DKMS provides a solution to this as well—in the mktarball and ldtarball commands. The mktarball command rolls up copies of each device driver module file which you’ve built using DKMS into a compressed tarball. You may then copy this tarball to each of your target systems, and use the DKMS ldtarball command to load those into your DKMS tree, leaving each module in the Built state, ready to be installed. This avoids the need for both kernel source and compilers to be on every target system. For example: # dkms status megaraid2, 2.10.3, 2.4.20-9: built megaraid2, 2.10.3, 2.4.20-9bigmem: built megaraid2, 2.10.3, 2.4.20-9BOOT: built megaraid2, 2.10.3, 2.4.20-9smp: built megaraid2, 2.10.3, 2.4.21-4.EL: built megaraid2, 2.10.3, 2.4.21-4.ELBOOT: built megaraid2, 2.10.3, 2.4.21-4.ELhugemem: built megaraid2, 2.10.3, 2.4.21-4.ELsmp: built You wish to deploy this version of the driver to several systems, without rebuilding from source each time. You can use the mktarball command to generate one tarball for each kernel family: # dkms mktarball -m megaraid2 -v 2.10.3 -k 2.4.21-4.EL,2.4.21-4.ELsmp, 2.4.21-4.ELBOOT,2.4.21-4.ELhugemem Marking /usr/src/megaraid2-2.10.3 for archiving... Marking kernel 2.4.21-4.EL for archiving... Marking kernel 2.4.21-4.ELBOOT for archiving... Marking kernel 2.4.21-4.ELhugemem for archiving... Marking kernel 2.4.21-4.ELsmp for archiving... Tarball location: /var/dkms/megaraid2/2.10.3/tarball/ megaraid2-2.10.3-manykernels.tgz Done. You can make one big tarball containing modules for both families by omitting the -k argument and kernel list; DKMS will include a module for every kernel version found. You may then copy the tarball (renaming it if you wish) to each of your target systems using any mechanism you wish, and load the modules in. First, see that the target DKMS tree does not contain the modules you’re loading: # dkms status Nothing found within the DKMS tree for this status command. If your modules were not installed with DKMS, they will not show up here. Then, load the tarball on your target system:
Page 1:
Proceedings of the Linux Symposium
Page 4 and 5:
The State of ACPI in the Linux Kern
Page 7 and 8:
Conference Organizers Andrew J. Hut
Page 9 and 10:
TCP Connection Passing Werner Almes
Page 11 and 12:
Linux Symposium 2004 • Volume One
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Cooperative Linux Dan Aloni da-x@co
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Build your own Wireless Access Poin
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Run-time testing of LSB Application
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Linux Block IO—present and future
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Linux AIO Performance and Robustnes
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Methods to Improve Bootup Time in L
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Linux on NUMA Systems Martin J. Bli
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Improving Kernel Performance by Unm
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Linux Virtualization on IBM POWER5
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
The State of ACPI in the Linux Kern
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Scaling Linux® to the Extreme From
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144: Linux Symposium 2004 • Volume One
Page 149 and 150: Get More Device Drivers out of the
Page 163 and 164: Big Servers—2.6 compared to 2.4 W
Page 167 and 168: Multi-processor and Frequency Scali
Page 187 and 188: Dynamic Kernel Module Support: From
Page 193: Linux Symposium 2004 • Volume One
Page 203 and 204: e100 Weight Reduction Program Writi
Page 207 and 208: NFSv4 and rpcsec_gss for linux J. B
Page 215 and 216: Comparing and Evaluating epoll, sel
Page 227 and 228: The (Re)Architecture of the X Windo
Page 239 and 240: IA64-Linux perf tools for IO dorks
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Carrier Grade Server Features in th
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Demands, Solutions, and Improvement
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Hotplug Memory and the Linux VM Dav
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
show all

One - The Linux Kernel Archives

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?