It does not actually "moves the control" but rather just keeps the path attached to the file name. Just run this on the command line and see what the output looks like:
1. Not like this. You could do this:
Which would list any .c file in the directory an one level lower.
Otherwise you would have to do something like this:
2. Sure you can do, this for example:
to list all *.c and *.h files
Hi,
I'm having a problem with the while loop in bash. I try the following script:
#!/bin/bash
while true
do
echo "test"
done
When I try this, it gives me this error:
while: Too few arguments.
What am I doing wrong?
Thanks (5 Replies)
Hello there, I'm a beginner in bash programining and I have a problem with the interpretetion of the code: sed -e "s/\(*\):.*/\1/" in this for loop:
for process in $(sed -e "s/\(*\):.*/\1/" /etc/passwd)
thx for any help
edgehead (3 Replies)
There is an interview question about UNIX bash:
Some shells like bash try to make '..' always work propery, namely, from home directory, cd ../$USER will place you in your home directory. Does bash always get this behavior correct?
Anyway can provide any example that bash doesnt work well? ... (4 Replies)
I have a ksh script with the following code and working fine under ksh.
IFS=$IFS
IFS=:
while read a b c
do
test "$a" = "$oraserver" && { orahome=$b; break; }
echo $orahome
done < /var/opt/oracle/oratab2
IFS=$_IFS
... (13 Replies)
hello i am new with linux
hello unix forum.
i have big problem i want to install the samp server for every user folder for ex..
samp for my frined name fred fredsamp
then i want create more samp to my firend lee
i want folder name will be leesamp
i want to know how make the script put the... (0 Replies)
I am using SunOS 5.9 and have the following outcome when using the sh and bash shells; has anyone else had this:
(tests behave differently)
bash-2.05$ ksh
$ if echo $SHELL; uname -a;; then echo yessssssssssssss; else echo nooooooooooooooo; fi
SunOS s036cln001014 5.9 Generic_118558-27 sun4u... (4 Replies)
Hi, i am making a little script that when its invoked with p or f, it will do different things (p will ask the user to input an string and it will count its words , and f will ask the user a directory and will list the number of files in that directory. But if wont get the comparation string... (1 Reply)
Hi there,
I need to loop some values,
for i in $(seq $first $last)
do
does something here
donefor $first and $last, i need it to be of fixed length 5. so if the input is 1, i need to add zeros in front such that it becomes 00001. It loops till 99999 for example, but the length has to be... (4 Replies)
What's up guys,
I am currently trying to figure out the answer to this question and I cannot for the life of me! The question is : "Explain how to do the following in UNIX/Linux shell script. You are not expected to remember the exact command syntax, but explain approximately how you would... (1 Reply)
Hi,
I'm fairly new to unix, and I have the following problem:
I know that if I type, "ps -ef | grep process", this will return some information about the process named 'process'. What I need this to do is be piped to an extra search that pick's out process' PID. How do I do this?
Thanks in... (5 Replies)
Discussion started by: bogof_tom
5 Replies
LEARN ABOUT XFREE86
libbash
LIBBASH(7) libbash Manual LIBBASH(7)NAME
libbash -- A bash shared libraries package.
DESCRIPTION
libbash is a package that enables bash dynamic-like shared libraries. Actually its a tool for managing bash scripts whose functions you may
want to load and use in scripts of your own.
It contains a 'dynamic loader' for the shared libraries ( ldbash(1)), a configuration tool (ldbashconfig(8)), and some libraries.
Using ldbash(1) you are able to load loadable bash libraries, such as getopts(1) and hashstash(1). A bash shared library that can be loaded
using
ldbash(1) must answer 4 requirments:
1. It must be installed in $LIBBASH_PREFIX/lib/bash (default is /usr/lib/bash).
2. It must contain a line that begins with '#EXPORT='. That line will contain (after the '=') a list of functions that the library
exports. I.e. all the function that will be usable after loading that library will be listed in that line.
3. It must contain a line that begins with '#REQUIRE='. That line will contain (after the '=') a list of bash libraries that are
required for our library. I.e. every bash library that is in use in our bash library must be listed there.
4. The library must be listed (For more information, see ldbashconfig(8)).
Basic guidelines for writing library of your own:
1. Be aware, that your library will be actually sourced. So, basically, it should contain (i.e define) only functions.
2. Try to declare all variables intended for internal use as local.
3. Global variables and functions that are intended for internal use (i.e are not defined in '#EXPORT=') should begin with:
__<library_name>_
For example, internal function myfoosort of hashstash library should be named as
__hashstash_myfoosort
This helps to avoid conflicts in global name space when using libraries that come from different vendors.
4. See html manual for full version of this guide.
AUTHORS
Hai Zaar <haizaar@haizaar.com>
Gil Ran <ril@ran4.net>
SEE ALSO ldbash(1), ldbashconfig(8), getopts(1), hashstash(1)colors(1)messages(1)urlcoding(1)locks(1)Linux Epoch Linux