Oops msgs and RAM

Oops msgs and RAM

Post by Ed Hurs » Sun, 31 Dec 1899 09:00:00



Being a complete duffer, I have some vague idea that "oops messages" can
help trace errors in modules and other kernel problems. What I'd like to
know is, if I get these messages with varying addresses at boot time,
could it indicate a bad DIMM?

I'd count it a real favor if you could also post a reply to

Ed

 
 
 

1. /usr/bin/msgs and permissions on /var/msgs

When I tried using msgs vie the sendmail-aliases I keep getting
"permission denied" errors on /var/msgs. It seems msgs is right:
sendmail is running as root but permissions are
drwxr-xr-x   2 daemon  wheel      512 Jan 12 19:41 msgs

As this is an almost freshly installed system, I dont think I changed
permission accidently. Any comments on this before I file a PR?
What should be the fix? Changing the group or the owner?
--
\usepackage[latin1]{inputenc}!

2. Bootmanager for dos/linux....

3. system msgs (/var/msgs)

4. mandrake-linux for PPC

5. Matrox Mystique ands X.

6. 15th Testing Computer Software '98 Conference -- Call for Papers

7. kernel oops with more ram

8. Linux for Sun Sparcstation $

9. kernel Oops message -2.4.x - contains ksymoops <oops.txt

10. Oops counter (was Re: ntfs OOPS (2.5.63))

11. use /dev/ram as RAM-DISK

12. 900 mb RAM, Are there any kernals that support this amount of RAM???

13. qty free ram on rescue system for small ram i386?