Diana,
Thank you for your guidance.
Much appreciated.
Prior to following your kind advice, I figured I would tidy up with some basic maintanance and do a Red Hat Network update.
Weird things just started happening following the Red Hat Network update of sane-backends-1.0.8-5 --> 1.0.8-5.2
This file is supposedly in:
/var/spool/up2date/sane-backends-1.0.8-5.2.i386.rpm
except when I look there, this file is not there.
Tell me - do you think that a string of a hundred or more "fatal errors" might be a bad thing?
Just - uh - just curious.
This is new.
These error messages now show when when I do an apt-get update followed by and apt-get upgrade fot Red Hat. Previously, this had worked flawlessly.
Shut down and turned the computer back on (my universal fix-it method). No change.
Yet the compuer seems to be working fine.
I'm sitting down with fsck and "Running Linux, 4th Edition." Been working with them for a little while, this evening - guess it is time to learn fsck - looks like this must be the Linux equivalent of Disk First Aid / DiskWarrior / Norton / TechTool.
Fsck is command line and it is all new to me and it is slow and ugly and nasty and it is non-intuitive and it is an Orc and I do not like it. :-(
But it is free.
And I am beginning to learn how it works.
Maybe it is not too bad, after all. :-}
The Mac is easier.
Tell me - did you go from Mac to Linux (as I am doing - when the going is easy, anyway) or vice versa or did you start Wintel or what?
Going from the Mac to Linux is like dropping a music and entertainment major in college in order to switch over to a double major of physics/ pediatric dentisry.
It is a different mind-set.
But I always kinda liked physics.
The crying kids are a whole lot harder . . .
Guidance would be welcome.
Regards,
Epaminondas
__________________________________________________________
Imagine a hundred or two lines of this - looks like this might be the Linux equivalent of a Mac bomb symbol - except everything keeps working fine (scratches head):
<< error: db4 error(-30982) from db->close: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Sigmd5 index using bd3 - (-30982)
rpmbd: fatal region error detected; run recovery
repeats itself many times with small variations, then . . .
error: db4 error(-30982) form dbenv-> close: DB_RUNRECOVERY: Fatal error, run database recovery
E: Sup-process /bin/rpm returned an error code (1) >>
Uh - I think it wants me to run "database recovery."
Wazzat?
(using ext3 here, by the way).