12-17-2009
Another way would be to use dtksh (Desk Top Korn Shell) , which ships on Solaris as part of CDE. dtksh evolved from wksh (Windowing Korn Shell). It has a full graphical X-Window toolkit and can be used to write a GUI wrapper for a shell script.
10 More Discussions You Might Find Interesting
1. Programming
In Unix, is there any way in which I can create a GUI like Realplayer? I mean the Windows Look & Feel.
Borded with buttons, windows, dialogs and other predefined widgets, I am wondering how to create my own buttons that come in different shapes and fashions or even draw images/control objects... (2 Replies)
Discussion started by: hirosima
2 Replies
2. Shell Programming and Scripting
Hi All,
I am not new to unix but just begin to realizing the power of unix shell programming..
i need to create a shell script that can provide a graphical interface to me to enter information.. and this script i ll run through telnet program remotly..
is this possible ...
plz guide me (1 Reply)
Discussion started by: johnray31
1 Replies
3. Programming
Hi ,
While trying to compile a PRO*C code on unix using makefile i get the following errors. i am now working on a 10g migration (from 8i) ...
these makefile perfectly work in previous version.
ld: fatal: file... (7 Replies)
Discussion started by: sivalives
7 Replies
4. Shell Programming and Scripting
Hi all! Im wondering if its possible to create a GUI for a shell script I just got done writing as the people that will be using it dont like the command line all to well. Just something simple with radio buttons to select options, maybe a text field to enter a location to save the file generated... (1 Reply)
Discussion started by: Grizzly
1 Replies
5. Shell Programming and Scripting
I know shell is an interpreter language, but can I make an executable file just like in folder /bin, /usr/bin, etc which source code was from a .sh file or from some .sh files??
My main purpose is to hide the source code.
thanks. (1 Reply)
Discussion started by: 14th
1 Replies
6. Shell Programming and Scripting
Hello Experts,
In my current job I need to upgrade a web GUI to execute Unix commands in a server....I am completely new to programming--So can anyone here help me out with initial steps...
Please notice that statement completely new to programming means-I never did it, SO I might keep on coming... (1 Reply)
Discussion started by: mhadi
1 Replies
7. Solaris
All,
I would like to know if there is a command which will list all the header files which were used while creating the executable. (1 Reply)
Discussion started by: helper
1 Replies
8. Shell Programming and Scripting
I wish to create an executable bash script that will run the following commands as root, that is, using sudo su
iptables-save | awk '/^
/ { print $1 }
/^:+ / { print $1 " ACCEPT" ; }
/COMMIT/ { print $0; }' | iptables-restoreMy first attempt at bash... (9 Replies)
Discussion started by: thixeqi
9 Replies
9. Red Hat
Hello experts,
I would like to know if is possible to create a default acl rule to a directory.
in this directory all files created should have executable permissions by the group IT.
i tried setfacl -m d:g:it:rwx /files
tried to change the mask setfacl -m m::rwx /files
but i still... (3 Replies)
Discussion started by: berveglieri
3 Replies
10. UNIX for Beginners Questions & Answers
Motif GUI example. Unix executable ready.
Hi ,
i have attached my executable GUI example file in form of a .gz file.
please gunzip file before.
May i ask you for check it out that it is running on your machine ?
You should have "Motif" package installed.
when you klick the unix executable... (4 Replies)
Discussion started by: Sennenmut
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)