But let??™s keep going.
Session 2 Reboot Previous zchanges.lzm processed; unable to apply the file.dat removal because
it does not exist.
No new changes detected??”/root/file.dat deletion not captured because it did
not exist in this session.
Session 3 Boot A module places file.dat into /root; zchanges.lzm knows nothing about /root/
file.dat and does not delete it.
At this point, the file.dat that had been deleted crept back into the system. The user
could re-delete it, which would work around this issue for the current boot and the next
boot, but on the subsequent boot the file would return again. If you plan to use this
method to preserve your BackTrack changes from session to session, keep in mind that
any file deletions will need to be propagated back to the module that placed the file originally.
In our case, the nvidia-install.lzm module placed the downloaded NVIDIA
installer into /root. This could have been resolved by deleting the nvidia-install.lzm
module and rebuilding it, remembering to delete the installer before capturing the
changes.
As you can see, the LiveCD module creation can be automated to preserve the changes
you??™d like to apply to every boot. There are some ???gotchas,??? especially regarding a module
that creates a file that is later deleted.
Pages:
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262