09-01-2008
Quote:
Originally Posted by
agasamapetilon
Is the Korn shell compatible with Bash? I make this question because I created the .profile and I want no problems with it. I made a check also at $HOME/ and I only have: .profile (the one I created), .vi_history and .sh_history but no more of the likes of $HOME/.shrc that you mentioned. Should I create a file for this specific shell?
I think the correct answer is that bash and korn are compatible with sh (the Bourne Shell), a kind of reference/standard/basic shell.
And the ~/.profile is the correct place to put a command You want to have executed each time You start a new shell, for example when You log in.
This will be read by all sh-compatible shells. As a contrast, if You have a .bashrc, it will only be read by Bash, not ksh (Korn) and so on.
/Lakris
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I just want to know ow I can set permanent pathes or whatever using setenv command. I'm using c shell .
regards,
me (1 Reply)
Discussion started by: geoquest
1 Replies
2. UNIX for Dummies Questions & Answers
I have a script that I'm trying to shorten (below) by removing repetitive code.
if ]
then
commodity_ndm_done=Y
fi
if ]
then
customer_ndm_done=Y
fi
if ]
then
department_ndm_done=Y
fi
if ]
then
division_ndm_done=Y
fi (3 Replies)
Discussion started by: superdelic
3 Replies
3. UNIX for Advanced & Expert Users
hi,
I am writing c++ code in unix operating system.In that i need to set the environment variable in unix.
suppose previously i have environment variable like path="something" now i need to change the path value to some othervalue . so that some other program will access that path value... (1 Reply)
Discussion started by: sada@123
1 Replies
4. UNIX for Dummies Questions & Answers
Hi,
Im using csh and sometimes bash.
I accidentally typed SET and looks like it has resetted some enviroment variables as im not able to run autosys jobs etc ..
So i wanted to know how i can put it back to normal by replacing any profile files from another user or by editing the file which... (2 Replies)
Discussion started by: spectator
2 Replies
5. Solaris
Hi,
I've read forums far and wide trying to learn how to append to my PATH in Solaris 9 and every time I think I am close I discover my system is not configured the same. Its so frustrating because this all stems from a new server I am trying to setup identical to the production machine. (Of... (5 Replies)
Discussion started by: thoraddict
5 Replies
6. HP-UX
Hi all
I have a request from user to change the file descriptors limit to 8192. The current setting are:
root@xxxxx:(wmdev)> ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 1048576
stack(kbytes) 131072
memory(kbytes) unlimited... (3 Replies)
Discussion started by: hedkandi
3 Replies
7. Shell Programming and Scripting
Hi
Could you please tell me how to set environment variables in Unix ksh.
And how can acess those varibles in shell scripts
( Please give the code with an example)
For my scenario.
We have written number of shell scripts with hard coded username and password.
But if we want to... (1 Reply)
Discussion started by: shyamu544
1 Replies
8. Solaris
Hi All
On my Solaris 10 X86, under my root directory I have a file called Aliases. It is owned by root (root:root) and the user (I mean root) has rwx permissions. In this file I have set some aliases like the following
alias a="cd /opt/IBM/WebSphere/AppAerver/Profiles"
When I run the above... (0 Replies)
Discussion started by: chrs0302
0 Replies
9. Shell Programming and Scripting
Experts,
I want to set value of variables like this in bash shell:
i=5 ; L=100
I want variable d5 (that is d(i) ) to be assign the value of $L ,
d$i=$L ; echo $d5
Not working
Thanks., (3 Replies)
Discussion started by: rveri
3 Replies
10. Shell Programming and Scripting
We are using csh on our AIX platform, if we have to export/set a specific environment variable we use setenv command but its only valid till session.
How do we set that variable permanent in our csh AIX? Do we put it in userprofile file or something else? (1 Reply)
Discussion started by: aixusrsys
1 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)