Don't fix /dev/null permissions if it fails in creation

By doing so we'll be masking a symptom of the problem instead of fixing
it. If permissions of /dev/null fail, most likely other problems will
also happen (e.g. pts permissions). Keep /dev/null alarm (which leads
to X server starting problems) to alert us if something is wrong.

Signed-off-by: Claudio Matsuoka <cmatsuoka@gmail.com>
This commit is contained in:
Claudio Matsuoka
2008-06-18 11:39:38 -03:00
parent 7d10388158
commit 765bef0991
+1 -1
View File
@@ -316,7 +316,7 @@ int main()
chardev("/dev/urandom", 0666, 1, 9);
chardev("/dev/ptmx", 0666, 5, 2);
chardev("/dev/null", 0666, 1, 3);
chmod("/dev/null", 0666); /* blino's sanity check */
//chmod("/dev/null", 0666); /* blino's sanity check */
chardev("/dev/mem", 0640, 1, 1);
chardev("/dev/tty0", 0660, 4, 0);
chardev("/dev/input/mice", 0660, 13, 63);