03-31-2008
I'm going to guess that the file name extension is just incorrectly mapped to OmniOutliner.
Check out the "Top Forums" section of The Unix Forums for shell scripting.
Answers to Frequently Asked Questions,
Unix for Dummies Questions and Answers,
and Shell Programming and Scripting.
What is the file name extension? ".command" or ".sh"?
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I am trying to run simple client server c program in unix.At the compling stage server is creating an executable but the client is not.
below is the link to the source codes:
http://www.cs.rpi.edu/courses/sysprog/sockets/server.c
http://www.cs.rpi.edu/courses/sysprog/sockets/client.c
... (2 Replies)
Discussion started by: konas
2 Replies
2. UNIX for Dummies Questions & Answers
Hey Every one
I have a find statement which find the files and deletes them
find /web/local/orderlink/batchmanaged01/scripts/SMOappLogs/log -name 'orderlink.log.*' -type f -mtime +$10-exec rm -f {} \;
This statement if finds a file at the given location it will delete the files but if it... (4 Replies)
Discussion started by: pinky
4 Replies
3. UNIX for Dummies Questions & Answers
Hi, I know nothing about Unix. Recently received image files from a client. Mac sees it as a Unix executable file. How do I convert these files to Tiff?
Thanks for helping. (1 Reply)
Discussion started by: Pet Teoh
1 Replies
4. UNIX for Dummies Questions & Answers
hello Folks,
once we compile any C code on Linux, we run the code using "./a.out"..
but can we have an executable for every program so that we can run the code directly without compiling the code every time.
just run the executable and get the output!
Thanks! (7 Replies)
Discussion started by: compbug
7 Replies
5. UNIX for Advanced & Expert Users
The binary file is
ELF-64 executable object file - IA64.
How i know that the source is
Is there any comamnd in unix i can read these kind of files or use a thirty party software?
Thanks for your help (8 Replies)
Discussion started by: alexcol
8 Replies
6. Shell Programming and Scripting
Hi - How can I find out under sh whitch file is an unix executable file? Need it for an software inventory. Thanks in advance. Regards - Lazybaer (6 Replies)
Discussion started by: lazybaer
6 Replies
7. Shell Programming and Scripting
Hi,
I want to write an executable file in unix env to go to a particular path instead of always typing the long path cd /app/oracle/product/10.2.0/Db_1/scripts/prejib/sample.
I have tried with the below script in but not working . please help me
bash-3.00$ cat a.sh
#!/bin/sh ... (3 Replies)
Discussion started by: prejib
3 Replies
8. UNIX Desktop Questions & Answers
Hi Friends,
I have a shell script which does some operations etc, would it be possible to create an executable file out from this shell script? meaning the executable file is not editable, thus the source code will not be visible to other users for copyright reasons.
Please help, thanks! (1 Reply)
Discussion started by: kokoro
1 Replies
9. Shell Programming and Scripting
Hi group,
I am very beginner in shell scripting and self learning.
I am trying to create and executable script to run awk from user defined variables.
e.g. suppose from a given file I want to delete some rows or some columns
We need to repeat this process for many files. Thus I was... (4 Replies)
Discussion started by: smitra
4 Replies
10. OS X (Apple)
Hi all...
Had an idea tonight which could really enhance shell scripting for me.
Yes I am aware there could be difficulties but......
Creating a C script inside the shell script to do a task, (a simple text print to stdout in
this example), compiling it on the fly, making sure it is... (4 Replies)
Discussion started by: wisecracker
4 Replies
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)