On Sat, Mar 23, 2002 at 01:07:52PM +0000, Aaron Sloman wrote:
> No !! This was missing, so I just copied it across from the other partition's
> installation.
> If this 'got removed', statisatically other important files will be missing?!
It's entirely possible that more files will be missing. If you ran 'fsck'
on your system after the crash, and it detected bad blocks, it should have
put them in /lost+found (and the 'lost+found' directory for each partition
you have on your system). You can probably get some idea of how much/what
was lost like that.
If it's a lot (which has happened to me before now), you might want to
think about exhaustively re-installing all packages, to be safe. Under
RPM-based distributions, you can do this with a command something like:
cd <YOUR_RPM_DIRECTORY_HERE>
rpm -Uvh `rpm -qa | sed 's/$/.i386.rpm/'`
If you're running Debian, it should be something like:
apt-get install `dpg -l | cut -d\ -f 1"`
Note that both of these scripts are written off the top of my head, so you
should check them out before running them. Also, modern versions of
RedHat/Mandrake have tools which can download files before installing
them, so you might want to change the script to use whichever program you
prefer.
Of course, this will only help with program files - any deleted personal
files and alterations to configuration files, are (short of
extraordinary measures) not coming back. Two things you can do to stop
this happening in future are keeping regular back-ups (a lot of work, and
difficult to keep to the strict discipline, but occasionally worth it) and
using "journaling" file-systems (which can be set to correct exactly this
kind of error). "Ext3" and "ReiserFS" are the most common journalling
file-systems, and I'm told that ext3 provides a nearly trivial
upgrade-path from ext2.
This message really has nothing to do with poplog any more, so if want to
reply to this, it's probably better you do it personally.
- Andrew
|