|
|
Sponsored Content
Top Forums
UNIX for Dummies Questions & Answers
will I be able to do it ?
Post 4480 by Neo on Wednesday 25th of July 2001 05:26:04 AM
07-25-2001
Administrator
Microsoft networking is 'graphical click and popup based' and assumes that the user is not interested in learning about the detail of how the actual network processes work. The overal philosophy is 'users don't care about the details, they want it to be spoon fed to them'.
UNIX is built on a quite different philosophy. One of the tenants of that philosophy is that the user needs to "command the system" and not "the system commands the user." This results in the need to learn an incredible amount of detail about the underlying processes and structures.
This board assumes that newbies are self-motivated with a strong desire to learn. We cannot motivate nor advise folks on how to make a mental shift from the mindset created by point-and-click experience.
I can tell you that on the server-side, point-and-click is normally risky and takes much more time than understanding the command line side. However, on the desktop side, point-and-click has merit.
I'm very suprised to read you are an electrical engineer and a C programmer but are not inclined to dig in a learn UNIX from the posts you reference.
Perhaps a nice expresso machine and a month in isolation with your favorite UNIX platform? This is how most of us got started
UNIX is built on a quite different philosophy. One of the tenants of that philosophy is that the user needs to "command the system" and not "the system commands the user." This results in the need to learn an incredible amount of detail about the underlying processes and structures.
This board assumes that newbies are self-motivated with a strong desire to learn. We cannot motivate nor advise folks on how to make a mental shift from the mindset created by point-and-click experience.
I can tell you that on the server-side, point-and-click is normally risky and takes much more time than understanding the command line side. However, on the desktop side, point-and-click has merit.
I'm very suprised to read you are an electrical engineer and a C programmer but are not inclined to dig in a learn UNIX from the posts you reference.
Perhaps a nice expresso machine and a month in isolation with your favorite UNIX platform? This is how most of us got started
|
|
LEARN ABOUT HPUX
sh
sh(1) General Commands Manual sh(1) NAME
sh - overview of various system shells SYNOPSIS
POSIX Shell option] ... string] [arg ...] option] ... string] [arg ...] Korn Shell option] ... string] [arg ...] option] ... string] [arg ...] C Shell [command_file] [argument_list ...] Key Shell DESCRIPTION
Remarks The POSIX .2 standard requires that, on a POSIX-compliant system, executing the command activates the POSIX shell (located in file on HP-UX systems), and executing the command produces an on-line manual entry that displays the syntax of the POSIX shell command-line. However, the command has historically been associated with the conventional Bourne shell, which could confuse some users. To meet stan- dards requirements and also clarify the relationships of the various shells and where they reside on the system, this entry provides com- mand-line syntax and a brief description of each shell, and lists the names of the manual entries where each shell is described in greater detail. The Bourne shell is removed from the system starting with HP-UX 11i Version 1.5. Please use the POSIX shell as an alternative. Shell Descriptions The HP-UX operating system supports the following shells: POSIX-conforming command programming language and command interpreter residing in file Can execute commands read from a terminal or a file. This shell conforms to current POSIX standards in effect at the time the HP-UX system release was introduced, and is similar to the Korn shell in many respects. Similar in many respects to the Korn shell, the POSIX shell contains a history mechanism, supports job control, and provides various other useful features. Korn-shell command programming language and commands interpreter residing in file Can execute commands read from a terminal or a file. This shell, like the POSIX shell, contains a his- tory mechanism, supports job control, and provides various other useful features. A command language interpreter that incorporates a command history buffer, C-language-like syntax, and job control facilities. Restricted version of the POSIX shell command interpreter. Sets up a login name and execution environment whose capabilities are more controlled (restricted) than normal user shells. restricted version of the Korn-shell command interpreter Sets up a login name and execution environment whose capabilities are more controlled (restricted) than normal user shells. An extension of the standard Korn Shell that uses hierarchical softkey menus and context-sensitive help. +--------------+--------------------+ | To obtain: | Use the command: | +--------------+--------------------+ | POSIX Shell | /usr/bin/sh ... | | Korn Shell | /usr/bin/ksh ... | | C Shell | /usr/bin/csh ... | | Key Shell | /usr/bin/keysh | +--------------+--------------------+ These shells can also be the default invocation, depending on the entry in the file. See also chsh(1). WARNINGS
Many manual entries contain descriptions of shell behavior or describe program or application behavior similar to ``the shell'' with a ref- erence to ``see sh(1)''. SEE ALSO
For more information on the various individual shells, see: keysh(1) Key Shell description. ksh(1) Korn Shell description. sh-posix(1) POSIX Shell description. csh(1) C Shell description. sh(1)