Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Saturday 2007-11-24 at 20:21 -0600, Rajko M. wrote:
It appears to me that just about everything in YaST is pretty much self
explanatory.
Okay... so, as an example, in Yast > Network Services > NIS Server. How
does that become self-explanatory to someone who has never heard of NIS
before?
This is the case where should be applied: "Don't touch what you don't
understand." Though, you know kids, they never listen this particular
advice.
No, such a thing has no place in Yast.
Even further... Click on Help in the NIS Server module and the
following message comes up:
"Select whether to configure the NIS server as a master or a slave or
not to configure a NIS server."
For this is applicable sentence from kernel help that is repeated
often for
exotic options:
"If you don't know what this means, you don't need it."
This is accompanied with URL where you can pick up more information what
particular option means and decide whether you need it or not.
But to find that in the kernel you have to "go inside". Yast is a tool
that makes administrators out of users: it must explain, it must be
easy, it must be accessible and non dangerous.
FORTUNATELY, if someone is in a home environment, and just
decide to create an NIS master or an NIS slave, without
the other, there will be no ill effect (other than a few
extra disk-head seeks on boot up, and a little bit of
memory wasted on a server that doesn't need to be running)
So, as far as danger is concerned, the current YaST
implementation of the NIS module is *NOT* dangerous.
It can be as easy as firing up the browser pointed at the relevant page
of the suse administration or reference manual that explains what a NIS
server is, or what setting up a printer involves, at the click of mouse
on a help button.
That could be nice -- just fork off a browser.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
