Above was merely a tip to simplify what is often unclear to a user new to the CLI of Linux
NAME.sh, and run as root
HOW to "run" a Bash script
Please compare - which is less keystrokes, less prone to typos
It is also
NOT required to open a terminal - of which a new user then has evey right to ask "WTH is a terminal".
and when, why, how do I "run as root"
In the same vein, the sooner they are aware of usefulness of Bash wildcards, it eases the whole learning process
Side benefit ~ lessening chance of omissions or typos, Esp. in long strings of text
http://www.tuxfiles.org/linuxhelp/wildcards.htmlIMNHO, if/when offering procedure tips - be as clear/unambiguous as possible
(experienced users often forget basic lessons suffered through upon entering into the powerful
world of Linux complexities)
Stressing use of scripted behaviours, or GUI front-ends DELAY those insights
As convenient as it now is, running Linux will never be as simplistic as turning on a TV,
with the expectation of "everything just works out_of_the_box"
Teaching by rote does not explain *why* a process is used/works, often becomes misinterpreted
~ only to discover much later, they had scant grasp of disciplines involved
Please
excuse the verbosity of above - I adhere to:
Knowing vs ability to instruct ~ especially in manner best suited to achieve full understanding,
is the prime goal to sharing knowledge
Best wishes
