Re: [S.u.S.E. Linux] Wabi, /dev/zero, and SuSe Config
![](https://seccdn.libravatar.org/avatar/615806c170b84aa66ba4c91bfc994007.jpg?s=120&d=mm&r=g)
Michael Perry wrote:
On Sun, Feb 15, 1998 at 12:08:23PM -0500, zentara stated:
Hi,
This isn't a big problem, but I want to know what is happening?
When I installed Wabi on SuSE, it requires me to chmod 666 on /dev/zero; in order for it to run.
That's fine.
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?
Hi, /dev/zero is kind of opposite to /dev/null. You can use /dev/zero as a source for null bytes. Gor example you can create a 10k file full of null bytes with the command: dd if=/dev/zero of=myfile bs=1024 count=10 SuSEconfig checks several file permissions (this is a security feature) and resets them if the don't fit /etc/permissions. To make the change of the permissions permanent change the line /dev/zero root.root 644 in /etc/permissions to /dev/zero root.root 666 They are set to 644 cause it doesn't make any sense to write to /dev/zero... Ciao, BB - Bodo Bauer S.u.S.E., LLC fon +1-510-835 7873 bb@suse.de 458 Santa Clara Avenue fax +1-510-835 7875 http//www.suse.com Oakland CA, 94610 USA -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (1)
-
bb@suse.de