On Sun, Feb 15, 1998 at 02:42:08PM -0500, zentara stated: <snip>

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

Thanks. On a whim I started wabi after having the suseconfig run for some stuff I did. It reset the /dev/zero and I had to redo the permissions so that wabi would run. This does not seem to be a totally big deal. But its rather strange that suseconfig would reset the permissions on a file that is a null value according to the info you submitted above. What exactly are the rationales for the file permissions and wabi anyhow? I know there are wabi users on this list. How do you folks deal with /dev/zero? -- --Michael Perry-- mperry@basin.com -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e