• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 270
  • Last Modified:

RH 7.3 reboot problem with /dev/null

Hello,
I have a RedHat 7.3 kernel 2.4.20-13.7 system. everytime I reboot I end up in maintenace mode with /dev/null in read-only mode.

Here is how I fix it:
mount / -o remount,rw ; rm -fr /dev/null* ; cd /dev/ ; ./MAKEDEV null ; reboot
 but doing this everytime is impractical. Does anyone know of a workaround or kernel patch etc... that addresses this?

Thanks,
Q
0
qwyjibojones
Asked:
qwyjibojones
  • 2
1 Solution
 
Alf666Commented:
This will not be easy to find. There must be something (most probably a shell script) that has done something like :

rm /dev/null
whatever > /dev/null

or, much simpler :

cp whatever /dev/null

What you should do is check whether /dev/null is a file or is still a character device *before* rebooting.

If it's still a character device, then it's most probably f*** up by a boot script. Which will be easier to debug.

If it's already a file, then something during your using of your system is messing with it. It's going to be much harder to find.
But there's a slight chance that it's a shell script (or a proggie) you wrote yourself.

If it happens during boot, please tell me when (when does the message first appear).

Please, check this, and come back to me.
0
 
qwyjibojonesAuthor Commented:
Hmmm...
Now that I need to re-create the problem, it seems to have stopped misbehaving.
I am using the system out of the box, and  haven't had a chance to do any scripting on it,( but it looks as though I am going to have to). I am guessing that some application is trying to use the bit bucket incorrectly, and is corrupting the file.

Are you saying that /dev/null starts out life as a character device and should get chaged once the system is up, to a file?

Do you think it wise to create a kill -or- start script that re-creates /dev/null?

Thanks,
Q


0
 
Alf666Commented:
No. It should *always* be a character device.
But some script corrupts it. Most probably deletes it. Then, the next script that uses it creates the file.

Yes. It's wise. But it's a problem you'd better resolve. As a second thought, I'd say it's not wise. It's a patch. And if it bothers you, it will force you to fix it. That's wise ! :-)

0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now