On Thu, 07 Oct 2004, [EMAIL PROTECTED] wrote: > I've currently set fsck to run pretty much on every other boot.
Install the memtest86+ package, activate it in lilo/grub, reboot. Let it test your main memory for at least 12h. > 3. Could this be a bug in fsck ? Why doesn't fsck actually tell me > what the errors are !! It just says "fixed them - rebooting". > isn't this a Bad Thing (TM) ? Is this Debian? I have *never* seen something like this from the set of tools in Debian. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
