On 15 Feb, 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?
it is one of the devices that are very useful to backup all your
windows software onto ;-)
/dev/zero produces infinite zero bytes when read from and should act as
a waste paper basket for data copied into (see the above suggestion ;-))
/dev/null is the "standard" waste basket, everything copied into
vanishes in data heaven. reading gains <eof>
you should be able to write to both devices. I do not understand the
default setting of 744 either.
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?
Juergen
--
--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
--
========================================== __ _
Jürgen Braukmann e-mail: brauki@cww.de | / / (_)__ __ ____ __
Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | / /__/ / _ \/ // /\ \/ /
========================================== /____/_/_//_/\_,_/ /_/\_\
--
To get out of this list, please send email to majordomo@suse.com with
this text in its body: unsubscribe suse-linux-e
brauki＠cww.de