Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Differences in BASH and ASH shells regarding if command? Post 302452185 by Scrutinizer on Thursday 9th of September 2010 01:34:46 PM
Old 09-09-2010
ash is (almost) a posix shell and offers no additional functionality and as such does not support [[ ]] with pattern matching (which is ksh/bash)
use:
Code:
case $TARGETLIST in
  *$QUERYVALUE*) blah blah blah
esac

 

10 More Discussions You Might Find Interesting

1. BSD

BSD, Bash and Shells?

When I use Mac OS X's Terminal the UI is some what easier than that of Linux... I this just a shell or something because using Bash is a pain in RH's Linux 9. It's so sensitive about case etc. ??? In that way what is the shell that OS X uses as it's default Bash is on OS X (OK Duh) and... (3 Replies)
Discussion started by: RedVenim
3 Replies

2. Shell Programming and Scripting

Why generate "ash and bash" different output for same bash script?

Hi, For my bash script, terminal with bash is generate an OK output and program works right. already, terminal with ash have "line 48: syntax error: Bad substitution" output and program don't work. :confused: (0 Replies)
Discussion started by: s. murat
0 Replies

3. Shell Programming and Scripting

Interacting with two BASH shells

Hi. I'm working with two BASH shells in order to perform two tasks. For simplicity, suppose that at Shell #1 I'm executing this program: sleep 100 whose PID is 263. Meanwhile Shell #2 is waiting for its termination to follow with a second one. I tried with: wait 263 # Script for second... (4 Replies)
Discussion started by: hresquivelo
4 Replies

4. Shell Programming and Scripting

Bash shells communication

Hello all, I have the following problem. In a Bash shell I run a program (I don't have the source code) which will execute some steps. At every step the program will wait for a user input. So I would like that another script which is running on a different shell will send these input togheter with... (4 Replies)
Discussion started by: alohisius
4 Replies

5. Shell Programming and Scripting

Differences between shells

What is the practical difference among the different shell like csh , ksh , bash etc.:confused::confused: Please use descriptive subjects instead of single words (2 Replies)
Discussion started by: hiten.r.chauhan
2 Replies

6. Shell Programming and Scripting

ash busybox read command not working inside function....

I have a script that has to execute a read command in a function, this is in an ash busybox. The code is... trapcatch () { echo "Ctl-c Detected, what do you want to do?" echo "Please choose the number of one of the following options" echo "1. Jump past this Set" echo "2. Exit... (8 Replies)
Discussion started by: tesser
8 Replies

7. Shell Programming and Scripting

Bash Script to Ash (busybox) - Beginner

Hi All, I have a script that I wrote on a bash shell, I use it to sort files from a directory into various other directories. I have an variable set, which is an array of strings, I then check each file against the array and if it is in there the script sorts it into the correct folder. But... (5 Replies)
Discussion started by: sgtbobie
5 Replies

8. Ubuntu

Bash to Ash, errors and adjustments

I wrote Bash script and now I want to convert it to Ash. One headache is this function: do_adduser() { setaddprompt _arr_add=("Add manually" "Add via TXT" "return to main menu" "exit program") select add_action in "${_arr_add}" do case "$REPLY" in 1)... (7 Replies)
Discussion started by: fzivkovi
7 Replies

9. Ubuntu

Bash to ash port, character-matching problem

I'm trying to convert this working bash script into an Ash script, read -p "Username:" _username if ! ]]; then echo "Valid" else echo "INVALID" fi However, Ash does not recognize the "=~" character. How can I do this? Also, is there a good reference guide, so I... (5 Replies)
Discussion started by: fzivkovi
5 Replies

10. Ubuntu

Convert a bash to ash

hello everybody, i'm a beginner in ash and i want to convert this bash script to ash. this script send a xml file to a nagios server : #!/bin/bash PROGNAME=$(basename $0) RELEASE="Revision 0.3" print_release() { echo "$RELEASE" } print_usage() { echo "" echo "$PROGNAME... (6 Replies)
Discussion started by: mdijoux25
6 Replies
cd(1)							      General Commands Manual							     cd(1)

NAME
cd - change working directory SYNOPSIS
[directory] DESCRIPTION
If directory is not specified, the value of shell parameter is used as the new working directory. If directory specifies a complete path starting with or directory becomes the new working directory. If neither case applies, tries to find the designated directory relative to one of the paths specified by the shell variable. has the same syntax as, and similar semantics to, the shell variable. must have execute (search) permission in directory. exists only as a shell built-in command because a new process is created whenever a command is executed, making useless if written and pro- cessed as a normal system command. Moreover, different shells provide different implementations of as a built-in utility. Features of as described here may not be supported by all the shells. Refer to individual shell manual entries for differences. If is called in a subshell or a separate utility execution environment such as: (which invokes on accessible directories) does not affect the current directory of the caller's environment. Another usage of as a stand- alone command is to obtain the exit status of the command. EXTERNAL INFLUENCES
International Code Set Support Single- and multi-byte character code sets are supported. Environment Variables The following environment variables affect the execution of The name of the home directory, used when no directory operand is specified. A colon-separated list of pathnames that refer to directories. If the directory operand does not begin with a slash character, and the first component is not dot or dot-dot, searches for directory relative to each directory named in the variable, in the order listed. The new working directory is set to the first matching directory found. An empty string in place of a directory pathname represents the current direc- tory. If is not set, it is treated as if it was an empty string. EXAMPLES
Change the current working directory to the directory from any location in the file system: Change to new current working directory residing in the current directory: or Change to directory residing in the current directory's parent directory: Change to the directory whose absolute pathname is Change to the directory relative to home directory: RETURN VALUE
Upon completion, exits with one of the following values: The directory was successfully changed. An error occurred. The working directory remains unchanged. SEE ALSO
csh(1), pwd(1), ksh(1), sh-posix(1), sh(1), chdir(2). STANDARDS CONFORMANCE
cd(1)
All times are GMT -4. The time now is 12:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy