This works great for user mode applications. Startup scripts and kernel
modules usually will require a reboot.
Creating a Module from an Entire Session
of Changes Using dir2lzm
Installing new software is sometimes not as simple as placing a new binary into /usr/
bin. For example, the video driver installation process for NVIDIA graphics cards is quite
involved and makes systemwide configuration changes. BackTrack does not include
NVIDIA drivers, so to use X at a resolution higher than 640?—480, we needed to build a
module that installs the drivers. A smart first step is to look for a downloadable module
at www.slax.org/modules.php. Unfortunately, at least the most recent NVIDIA driver
modules there do not correctly configure the BackTrack 2.0 system. One of the downloadable
modules could probably be debugged without too much work, but instead
let??™s explore the snapshot change management module creation technique.
As you already know, the actual files from the BackTrack CD are never modified. After
all, they might very well be stored on read-only media that cannot be modified. Any
changes made to the running system are written only to a directory on the mounted
RAM disk. This system makes it very easy to know the entire set of changes that have
been made to the running configuration since boot.
Pages:
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254