On Sat, 2003-06-14 at 00:26, Ronald J. Hall wrote: > Okay, a bit of an update. I deleted the slocate.db.tmp file in > /var/lib/slocate, and reran updatedb. Crash - spont. reboot. > > I did a urpme slocate, then a urpmi slocate. Reran updatedb. > Crash - spont. reboot. > > I turned DMA off to /dev/hda, then reran updatedb. Crash -spont. reboot. > > <sigh> Thank goodness for jounaling FSs! > > Let me thank everyone who's tried to help so far. I guess I ought to mention > that under v9.0 of Mandrake, this same hardware setup did not have this > problem at all.
DL, That means that you've troubleshot the problem down to either a bad package, a configuration problem, or a compatibility issue. If the hardware was pristine on a previous distro, that basically means you've already run a battery of tests on it and it passed. Assuming that the use of the hardware was over a sufficiently long time; say at least over a month or two. <g> Seems like I remember some kind of difficulty with updatedb and the /proc directory; but that was a looong time ago and the specifics elude me. The logic of this says to me that if your system is installed off the cd's just like everybody else's is, then you should be getting the results that everyone else is getting. Since we know your hardware is pristine, and since you are NOT getting the results you should be, that leans me towards some kind of compatibility problem. Which possibly can be resolved by tweaking the configuration in some way. Have you checked the system logs for clues? --LX -- ������������������������������������������������ Kernel 2.4.21-0.13mdk Linux Mandrake 9.1 Enlightenment-0.16.5-12mdk Evolution 1.2.4-1.1mdk Linux User #268899 http://counter.li.org/ ������������������������������������������������
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
