![](https://seccdn.libravatar.org/avatar/a31fc9c368e52cab0e26446d5591f065.jpg?s=120&d=mm&r=g)
Michael Perry wrote:
On Sun, Feb 15, 1998 at 12:08:23PM -0500, zentara stated:
What's unusual is whenever I start Yast, and do some system change, and Suse config starts when I exit; the mod on /dev/zero gets reset. It's no problem to do the chmod again, but why does SuSe config do this. Is it part of security?
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
I dont have an answer but am quite curious about /dev/zero since when I upgraded to 5.1 it reset permissions on /dev/zero and rendered wabi unable to run until I figured out exactly the problem. What in heck is /dev/zero? Why does wabi want to find /dev/zero with certain permissions set? Why does SuSE 5.1 reset permissions on files like this when I upgraded?
Here is something I found about /dev/zero. It seems to be a common problem. 888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888 Back to the directory for section 4 null(4) NAME null, zero - data sink DESCRIPTION Data written on a null or zero special file is discarded. Reads from the null special file always return end of file, whereas reads from zero always return \0 characters. null and zero are typically created by: mknod -m 666 /dev/null c 1 3 mknod -m 666 /dev/zero c 1 5 chown root.mem /dev/null /dev/zero NOTES If these devices are not writable and readable for all users, many programs will act strange. FILES /dev/null /dev/zero SEE ALSO mknod(1), chown(1) 8888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888 -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e