I have a FC4 system that every time it reboots the permissions on /dev/null change from 0666 to 0660. This causes boot errors and the system will not boot.
That seemed to me to be a udev error so I looked in: /etc/udev/rules.d/50-udev.rules and the mode of null seems correct.
Am I looking in the wrong place or what can I do to fix this problem?
On Mon, 2005-12-26 at 11:20 -0600, akonstam@trinity.edu wrote:
I have a FC4 system that every time it reboots the permissions on /dev/null change from 0666 to 0660. This causes boot errors and the system will not boot.
That seemed to me to be a udev error so I looked in: /etc/udev/rules.d/50-udev.rules and the mode of null seems correct.
Am I looking in the wrong place or what can I do to fix this problem?
Its probably pam related. look under /etc/security, but I am not sure that's it
check console.perms
On Mon, Dec 26, 2005 at 12:01:49PM -0600, David Gomez wrote:
On Mon, 2005-12-26 at 11:20 -0600, akonstam@trinity.edu wrote:
I have a FC4 system that every time it reboots the permissions on /dev/null change from 0666 to 0660. This causes boot errors and the system will not boot.
That seemed to me to be a udev error so I looked in: /etc/udev/rules.d/50-udev.rules and the mode of null seems correct.
Am I looking in the wrong place or what can I do to fix this problem?
Its probably pam related. look under /etc/security, but I am not sure that's it
check console.perms
I can see why you would suggest console.perms as the place to look for a solution to this problem. But: 1. I can find no reference to /dev/null in console.perm related files. 2. We have ~50 machines with the same copnfiguration of console.perms and do not have the same problem.
If anyone has further assistance on where to look I would appreciate it.
I posted the problem stated below and did not get any solutions but a solution described below showed up.
On Mon, Dec 26, 2005 at 11:20:56AM -0600, akonstam wrote:
I have a FC4 system that every time it reboots the permissions on /dev/null change from 0666 to 0660. This causes boot errors and the system will not boot.
I mention this so if this happens to anyone else they will know what the problem was. It was that I managed to create a FC4 system without a /sys file.
To get this solution I had to use the wisdom of a Volvo mechanic that I called in a panic. I told him that as I was driving on the Interstate my gas gage was heading quickly toward empty. He asked the critical question, "What else is not working?". As soon as I told him the windshield wipers were not working he diagnosed the problem. A fuse is blown.
So in this case I asked myself what else was not working? The /media directory was missing. And so on. I recommend this approach to anyone else who is faced with similar impossible behavior. ------------------------------------------- Aaron Konstam Computer Science Trinity University telephone: (210)-999-7484