a good place to start might be a review of the forensic tools being developed in the security community. <><Randy <><Randall Grimshaw Room 203 Machinery Hall Syracuse University Syracuse, NY 13244 315-443-5779 rgrimsha@xxxxxxx >>> todbot88@xxxxxxxxx 08/23/06 05:18 AM >>> Hi All! I would like to start a project (OK, perhaps there is already one ongoing, if so, I would like to know about it) dedicated to recovery from a system crash (broken X, bad HW, anything making the machine non-functional). I am thinking of first a set of applications which gather information about the running system (or what one should look like when it is running)(HW list, SW list, Boot sector copy, config files, critical files md5s, results of lspci, lsmod, "normal" log files (/var/log) etc.... Then a set of applications designed to go in (not booting from the crippled system) and gather the same sorts of information for comparison and understanding the problem now crippling the computer in the shop. And then a set of applications which fix, flag, or tell the owner the bad news determined about the problem computer. Perhaps the process could make for the developers a standard "Crash Cart Packet" consisting of parts of the logs and command results (maybe an X-packet, Kernel-packet, Audio-packet, etc). Well, that is it. Just an idea. I really do not know how to start or be part of such a thing. I guess I will follow those before me and send an e-mail. If interested in the motivation - read on: Last night I wrote an e-mail to a gentleman who lost some computers. He thought it might be FC5 (He was doing a fresh install or upgrade). I have seen several on the lists needing crash help. I also responded to another gentleman who was experiencing an "updated" Xorg which broke (no GUI!!). I encouraged him to copy some of the basic log files and help us all heal from our very human tendency to break things. Today I woke up, pressed the on button on my computer, got a cup of coffee, and came back to an ncurses error screen partially obscured by an exit to a prompt. My silly old video card already has some irritations with X/Dapper (hash on the screen after monitor has put itself to sleep) so my prompt was without cursor and the screen was changing colors as I went (I think part of the ncurses applet was still running somehow along with the shell). I thought I had swallowed a bug! However when Puppy and then Dapper Live booted - xorg.conf the same but the Xorg binary of very recent date - I remembered the problems I commented on and replaced my Xorg from the live CD and was happy. Please let me know if there is interest! Thanks! Tod -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
