12-31-2008
features of a new SHELL
Hello,
My team and I planing to create a new shell. We are including features like handing the "command not found" exception, etc....
1)Can you please give some suggestions on what do do while writing a new shell.....
2)can you please give me your problems with the existing shells..My platform is RED HAT 9 and FEDORA 8.
please list them out in points so that we can understand better......
![Big Grin Smilie](https://www.unix.com/images/smilies/biggrin.gif)
Last edited by otheus; 01-06-2009 at 06:27 PM..
Reason: changed post icon
8 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
Neo, can you tell us about some of the new features since the upgrade, or are they mostly "behind the scenes"? (1 Reply)
Discussion started by: PxT
1 Replies
2. UNIX for Advanced & Expert Users
Hello:
I have a customer who is requesting the following security features on a Solaris 8 system:
1. Password history for the three previous passwords.
2. User account lockout after 3 failed login attempts.
Can anyone help provide me with a solution or direction for the above? (1 Reply)
Discussion started by: rambo15
1 Replies
3. AIX
Hi Unix Experts,
I like to compile and compare all the features that AIX OS (541L) and Solaris OS (Solaris 10) provide.
If somebody can shed on this topic would be highly appreciated.
Thank you,
Khan (0 Replies)
Discussion started by: hkhan12
0 Replies
4. Windows & DOS: Issues & Discussions
I need to select the main features of shell scripting on UNIX and evaluate their MSDOS equivalent.
can anyone suggest some online resources articles anything??
Thanks in advance (0 Replies)
Discussion started by: deemon111
0 Replies
5. UNIX for Dummies Questions & Answers
Hi
Can anybody explain the following shell features with example
a) Command line editing
b) filename completion
c) job control (1 Reply)
Discussion started by: skyineyes
1 Replies
6. UNIX for Dummies Questions & Answers
HI
Can anybody explain following UNIX features?
Removable file system
Dynamic file space allocation
Thanks (1 Reply)
Discussion started by: skyineyes
1 Replies
7. Programming
hii to all
i am developing a simple unix shell in c i want to add history feature in that how could i do that plz help if there is any tutorial or website plz put it here
history feature should be like that in bash, when press up key show the previous command typed in console
plz be... (1 Reply)
Discussion started by: vipin_jss
1 Replies
8. Ubuntu
Hi, I need to create a user from a bash script so i have to use useradd. The problem is that when i create a user with:
useradd -d /home/sample -m sample
after i login with that user I have no history in bash, path do not appears, i can't use arrows and so on. When I use adduser everything is... (5 Replies)
Discussion started by: ktm
5 Replies
LEARN ABOUT CENTOS
shell-quote
SHELL-QUOTE(1) User Contributed Perl Documentation SHELL-QUOTE(1)
NAME
shell-quote - quote arguments for safe use, unmodified in a shell command
SYNOPSIS
shell-quote [switch]... arg...
DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands
or files with embedded white space or shell globbing characters safely. Here are a few examples.
EXAMPLES
ssh preserving args
When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and
passes them to "$SHELL -c". This doesn't work as intended:
ssh host touch 'hi there' # fails
It creates 2 files, hi and there. Instead, do this:
cmd=`shell-quote touch 'hi there'`
ssh host "$cmd"
This gives you just 1 file, hi there.
process find output
It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to
split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote:
eval set -- `find -type f -print0 | xargs -0 shell-quote --`
debug shell scripts
shell-quote is better than echo for debugging shell scripts.
debug() {
[ -z "$debug" ] || shell-quote "debug:" "$@"
}
With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can.
save a command for later
shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command
you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are
things the user can't pass through), you can do something like this:
user_switches=
while [ $# != 0 ]
do
case x$1 in
x--pass-through)
[ $# -gt 1 ] || die "need an argument for $1"
user_switches="$user_switches "`shell-quote -- "$2"`
shift;;
# process other switches
esac
shift
done
# later
eval "shell-quote some-command $user_switches my args"
OPTIONS
--debug
Turn debugging on.
--help
Show the usage message and die.
--version
Show the version number and exit.
AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions.
AUTHOR
Roderick Schertler <roderick@argon.org>
perl v5.16.3 2010-06-11 SHELL-QUOTE(1)