Visit The New, Modern Unix Linux Community


Portable scripting


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Portable scripting
# 1  
Portable scripting

Quote:
Originally Posted by bakunin
"How to achieve a maximum of standardization while at the same time recognizing newer developments in the Unix systems programming area?"
For historical, simple, practical and portable reasons my scripts start normally with "#!/bin/sh", hence I restrict myself to those features available in the Bourne Shell.

The few cases where I would use ksh or bash is if I know this script is targetted at some subset of platforms where that is available and required for the job. If it's not required, then back to good old sh.

I also use "test" rather than [ or [[ as I like to see blatently what a script is really doing. Ie, my model is that

Code:
"if" uses it's arguments as a command line and will use the 
then or else clause depending on zero or non zero 
return code of that command.

hence I am more than happy to use "if" with many other programs, not just test or some link to it.

Previous Thread | Next Thread
Thread Tools Search this Thread
Search this Thread:
Advanced Search

Test Your Knowledge in Computers #868
Difficulty: Medium
Maclisp is a successor to Common Lisp.
True or False?

10 More Discussions You Might Find Interesting

1. Programming

Is There a Portable Way to Kill a Process in C++

Hi. I am looking for a way to write C++ code that will kill a process, and works just the same way in both Unix and Windows. For my particular situation, it cannot be hundreds of lines of code, either. Thanks in advance for any light you can shed on this. Brandon (5 Replies)
Discussion started by: BrandonShw
5 Replies

2. UNIX and Linux Applications

urgent help in Portable Applications

Hello Im stuck with a project on converting existing applications in to their portable versions, What i mean is that i want an application to run on a Linux OS without the need of actually installing the application on that machine. My preffered OS is fedora as it is used on most machines in my... (1 Reply)
Discussion started by: engineeringme
1 Replies

3. Linux

Portable Applications

Hello Im stuck with a project on converting existing applications in to their portable versions, What i mean is that i want an application to run on a Linux OS without the need of actually installing the application on that machine. My preffered OS is fedora as it is used on most machines in my... (1 Reply)
Discussion started by: engineeringme
1 Replies

4. UNIX for Advanced & Expert Users

Urgent help in portable applications

Hello Im stuck with a project on converting existing applications in to their portable versions, What i mean is that i want an application to run on a Linux OS without the need of actually installing the application on that machine. My preffered OS is fedora as it is used on most machines in my... (1 Reply)
Discussion started by: engineeringme
1 Replies

5. Programming

urgent help in portable applications

Hello Im stuck with a project on converting existing applications in to their portable versions, What i mean is that i want an application to run on a Linux OS without the need of actually installing the application on that machine. My preffered OS is fedora as it is used on most machines in my... (0 Replies)
Discussion started by: engineeringme
0 Replies

6. Linux

A portable bootable version?

What I have been doing for some time now is installing linux on my tech machine at work, plugging in devices and transferring data with dd_rescue. What I need now is a version of linux that I can install on a laptop sata hard drive and be able to plug it into any machine to transfer data off of... (1 Reply)
Discussion started by: Methal
1 Replies

7. UNIX and Linux Applications

ClamAV/other AV. Possible to make portable?

Hey guys/gals, I work with a large amount of servers, and was just curious if it is possible to make a linux AV app, portable. What i mean is, I go to a user's home directory and do something like ./clamavscan (I suppose an alias for clamscan..), and it scans the user's home directory for... (2 Replies)
Discussion started by: Rhije
2 Replies

8. Shell Programming and Scripting

Query regarding portable script

Dear Experts, I want to write a script which has to work on Solaris & Linux sytems. The problem which i am facing is, there are commands whose options are different on both OS's. For example ping. On Solaris i have to write: ping $host 1 to check if the host is alive On Linux i... (4 Replies)
Discussion started by: dhiraj4mann
4 Replies

9. Linux

Apache Portable Runtime

Hi I am starting a project in which I want to use APR for portability. I download APR version 1.2.2 from "http://apr.apache.org/download.cgi#apr1" and I am using Redhat/Linux 9. As I am a newbie to APR and I have no prior experience of using APR, so I started learning it from:... (0 Replies)
Discussion started by: sumsin
0 Replies

10. Windows & DOS: Issues & Discussions

Portable GUI shell scripting?

I have some scripts that run in Windows, and the ability to put a GUI layer over them is kind of appealing. So when I stumbled over http://wizapp.sourceforge.net/ I thought that was rather cute. (Reading the "advanced batch scripting" art of the manual impresses upon me that no sane person... (2 Replies)
Discussion started by: luke
2 Replies
EXPORT(1P)						     POSIX Programmer's Manual							EXPORT(1P)

PROLOG
This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the correspond- ing Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux. NAME
export - set the export attribute for variables SYNOPSIS
export name[=word]... export -p DESCRIPTION
The shell shall give the export attribute to the variables corresponding to the specified names, which shall cause them to be in the envi- ronment of subsequently executed commands. If the name of a variable is followed by = word, then the value of that variable shall be set to word. The export special built-in shall support the Base Definitions volume of IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines. When -p is specified, export shall write to the standard output the names and values of all exported variables, in the following format: "export %s=%s ", <name>, <value> if name is set, and: "export %s ", <name> if name is unset. The shell shall format the output, including the proper use of quoting, so that it is suitable for reinput to the shell as commands that achieve the same exporting results, except: 1. Read-only variables with values cannot be reset. 2. Variables that were unset at the time they were output need not be reset to the unset state if a value is assigned to the variable between the time the state was saved and the time at which the saved output is reinput to the shell. When no arguments are given, the results are unspecified. OPTIONS
See the DESCRIPTION. OPERANDS
See the DESCRIPTION. STDIN
Not used. INPUT FILES
None. ENVIRONMENT VARIABLES
None. ASYNCHRONOUS EVENTS
Default. STDOUT
See the DESCRIPTION. STDERR
The standard error shall be used only for diagnostic messages. OUTPUT FILES
None. EXTENDED DESCRIPTION
None. EXIT STATUS
Zero. CONSEQUENCES OF ERRORS
Default. The following sections are informative. APPLICATION USAGE
None. EXAMPLES
Export PWD and HOME variables: export PWD HOME Set and export the PATH variable: export PATH=/local/bin:$PATH Save and restore all exported variables: export -p > temp-fileunset a lot of variables... processing. temp-file RATIONALE
Some historical shells use the no-argument case as the functional equivalent of what is required here with -p. This feature was left unspecified because it is not historical practice in all shells, and some scripts may rely on the now-unspecified results on their imple- mentations. Attempts to specify the -p output as the default case were unsuccessful in achieving consensus. The -p option was added to allow portable access to the values that can be saved and then later restored using; for example, a dot script. FUTURE DIRECTIONS
None. SEE ALSO
Special Built-In Utilities COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol- ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html . IEEE
/The Open Group 2003 EXPORT(1P)

Featured Tech Videos