Thanks for the quick reply. Since my first post, I re-wrote the whole script following the man pages on my server rather than on the mac and it works perfectly.
What I'm still lost on however is the difference between the bash flavors. I understand that Mac OSX 10 is BSD unix based and my server is running a GNU/Linux bash, but other than finding different entries for certain man pages, I cant find any other references to shell scripts not being compatable between the two systems. Even more confusing for me is that the environment was set to the Bourne Shell. Shouldn't this be 100% compatible?
The bash versions as reported by each bash:
Macbook pro:
Media temple gridserver:
Hi all ---
I have the need to manage multiple versions of a set of utility scripts -- both shell and SQL and other .dat files. I am wondering if anyone out there knows of a good way to "PATH" to SQL and text files in a way similar to how PATH facilitates finding executables in a pre-specified... (2 Replies)
Hello,
Can you tell me a command to tell how many disk arrays are installed in the system, their RAID types and versions. I am working on Solaris 9.
Thanks very much in advance.
Mohammed (1 Reply)
Hi,
I have a c file in my repository. We are using RCS(Revision Control System) to control and manage the versions. I need to find
1. Difference between the current version with a different version
2. Difference between any two different versions of a file. Ex Difference between 1.14 and... (1 Reply)
I need some help with the logic and syntax for a shell script (ksh) that will search a directory and look for similar files and save only the last two versions. The version number is in the file name. However, the files are of varying name lengths and may have 1 or many files, with no limit to... (6 Replies)
i was faced by a question from a friend. i found it very tricky. all my months of learning unix i never can figure it out still. heres the question he faced me with. wondering if you all can help me figure a solution.
ill let him know the forums helped me out :D
What command would you use... (10 Replies)
I want to write a korn shell script to get the latest three versions for a file in the directory having lot of files with various versions (files with prefix as same but time stamp as suffix) and compress it and at the same time have to remove the remaining versions of the file (other than latest... (4 Replies)
Hi Experts,
I would like to know in Linux any command which will replace a file without affecting the running process.
I tried the mv command bug the running process is not taking the new file.
Any rsync option is available like this for not affecting the current process.
Thanks in... (7 Replies)
Discussion started by: ThobiasVakayil
7 Replies
LEARN ABOUT DEBIAN
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