> > isn't there a pseudo file in /proc that maps your > > entire physical memory? Try cat'ing that th /dev/null
Yes. And cat'ing it to /dev/null would read the whole memory, but as all the read data is dumped straight away I don't see how it would "test" anything at all. Face it everyone, there's no way past memtest86[1]. It's straightforward to install on a floppy and use from a floppy. > /proc/kcore . Not a good idea... I've seen that cause very strange > behaviour. (Unexplained crashes, lockups, applications dying.. etc...) Any idea why? It shouldn't. Or was that a wrong question? Volker [1] If you wrote all zeroes to memory and read all locations and tested whether they're all zero, it would give you an idea of whether the memory was good or bad, nothing more. -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.orcon.net.nz/ Please do not CC list postings to me.
