On 02/13/12 09:20, Dave Anderson wrote:
a "source" command. In my environment, we've got 16 (yes, *sixteen*) loadable modules that need to get "mod -s MODNAME /path/to/modname.ko" -ed. So not being a big fan of typing, my preference would be to: mod | script-to-look-for-modules> mod-s-commands source mod-s-commands
There are 3 possibilities... Put the mod commands in a .crashrc file in the current directory,
If it were static, I could. This is for analyzing crash dumps that have been created on other systems.
Or do it during a crash session by putting the commands in a file, and run the command's contents by redirecting:
crash> < input crash> mod -s< input
I gather that both of these are really the same in that the first case simply appends each input line to an empty string. This is exactly what I was asking for, plus a little bit. Since I wasn't expecting the "mod -s < input" formulation, I likely just didn't stumble over it. Anyway, since I won't know in advance which modules are loaded; and once I do know which ones they are, I won't know where they are; I will need to use a feedback loop. crash must tell a hunt-it-down script which modules are needed, then that script tells crash where to load up the .ko files. Perfect. Thank you so much!! Regards, Bruce -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility
