First, I'd like to know if being a shell programmer considered a "real" programmer. is it??
also, I do create a lot of shell programs which includes full scripts to create users and maintaining records. ie phone records.
now, I hear the programmer has to do some cleaning up after the... (3 Replies)
This is shell programming assignment.
It needs to create a file called .std_dbrc contains
STD_DBROOT=${HOME}/class/2031/Assgn3/STD_DB
(which includes all my simple database files)
and I am gonna use this .std_dbrc in my script file (read the data from the database files)
like this: .... (3 Replies)
1.if
2.then
3. # save the number of args and first argument in variables.
4. num_args=$#
5. id="$1"
6. echo "$id"
7. #echo "$1" > crapfile.txt
8. echo `sed 's/\*/'\*'/g' < crapfile.txt`
Above is a partial code.I would like to ask:
at line 1:... (1 Reply)
I created a file named q2.c in /home/tuan/Desktop/Shell_programming. I coded a script named "test" to check whether the file existed or not. My code :
#!/bin/sh
submitDir=/home/tuan/Desktop/Shell_programming/submit
if
then
echo "There is no q2.c"
else
echo "There is q2.c"
fi
After... (3 Replies)
Hi i would like to write a "script" which takes a directory as an argument and the script will output the content of a file in this directory.Here is my code
#!/bin/sh
#set an argument to be a specified path
$1=/home/tuan/Desktop/Shell_programming/directory
#check if an argument is a... (3 Replies)
I have 2 different directories. The first has 2 sub-folders A and B. The second as 2 sub-folders C and D and script named "script".There is a code of "script" to list 2 sub-folders C and D
#!/bin/sh
for file in *
do && echo $file
done
I would like to ask how can I make a change if I... (2 Replies)
In folder A i have a file "a' and text file named infile00.I would like to do redirection :a<infile01.
There is a code to do this
#get a file "a" in /home/A
for file in /home/A/*
do
if $file ]
then
#printing out if file is an execute file
echo $file "is an... (2 Replies)
Hello all,
I am currently try to learn the linux operating system as well as some bash programming. I have come across some online course work which has been very helpful, I have been working through some assignments and since I have no teacher to ask I have come to you experts.
So the... (6 Replies)
2- Write a bash shell script filestatic. The script should examine the number files in directories given as arguments (parameters) to this script.
a. if one argument is given, the script should count and report the number of files in this directory. Only regular files should be counted, not... (1 Reply)
2- Write a bash shell script filestatic. The script should examine the number files in directories given as arguments (parameters) to this script.
a. if one argument is given, the script should count and report the number of files in this directory. Only regular files should be counted, not... (1 Reply)
Discussion started by: tahseen_22334
1 Replies
LEARN ABOUT OPENSOLARIS
echo
echo(1B) SunOS/BSD Compatibility Package Commands echo(1B)NAME
echo - echo arguments to standard output
SYNOPSIS
/usr/ucb/echo [-n] [argument]
DESCRIPTION
echo writes its arguments, separated by BLANKs and terminated by a NEWLINE, to the standard output.
echo is useful for producing diagnostics in command files and for sending known data into a pipe, and for displaying the contents of envi-
ronment variables.
For example, you can use echo to determine how many subdirectories below the root directory (/) is your current directory, as follows:
o echo your current-working-directory's full pathname
o pipe the output through tr to translate the path's embedded slash-characters into space-characters
o pipe that output through wc -w for a count of the names in your path.
example% /usr/bin/echo "echo $PWD | tr '/' ' ' | wc -w"
See tr(1) and wc(1) for their functionality.
The shells csh(1), ksh(1), and sh(1), each have an echo built-in command, which, by default, will have precedence, and will be invoked if
the user calls echo without a full pathname. /usr/ucb/echo and csh's echo() have an -n option, but do not understand back-slashed escape
characters. sh's echo(), ksh's echo(), and /usr/bin/echo, on the other hand, understand the black-slashed escape characters, and ksh's
echo() also understands a as the audible bell character; however, these commands do not have an -n option.
OPTIONS -n Do not add the NEWLINE to the output.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscpu |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), echo(1), ksh(1), sh(1), tr(1), wc(1), attributes(5)NOTES
The -n option is a transition aid for BSD applications, and may not be supported in future releases.
SunOS 5.11 3 Aug 1994 echo(1B)