hi,
I am pretty new both to unix and this forum, can anyone help me to give shortcuts to my commands...
eg:-
instead of "cd /usr/bin"
i want to to give " bin " and get to that path.
I'm using HP-UX 11.0
abey (2 Replies)
hi,
I am pretty new both to unix and this forum, can anyone help me to give shortcuts to my commands...
eg:-
instead of "cd /usr/bin"
i want to to give " bin " and get to that path.
I'm using HP-UX 11.0
abey (2 Replies)
Hi Guys,
I very new to bt-basic even I got 8 years experience on UNIX. I searched through google about bt-basic but nothing really give me solid documentation. Anybody have documentation or manual for this bt-basic? Pls help me (2 Replies)
Hi everyone, I need some help! I know that this is a very simple little problem but I seem to be stuck. I was just wondering if you could show me the right way.
I basicly have to write a single line of commands (using piping) to do the following:
From the file data.txt, select all of the... (2 Replies)
Hi,
Good morning
I want to install HP-Unix in my PC.
I already have windows XP home edition in my PC.
I do not want remove XP,But I need HP-Unix in the same system.
Is it posssible?
If it is what is the name and version of HP-Unix cd?
Where can I get the CD to install.
I have... (4 Replies)
Hi ,
I need to know the difference between $((command)) and $(command) and $(($(command))).
"" and '' and ``.
I have tried searching the help files but cant able to find this.
Could you let me knoq about any document.
Thanks (4 Replies)
There isn't much of a relation between 80's BASIC and today's BASIC.
A lot of languages seem similar. The BASIC I worked with was Dartmouth or VSBASIC. Now existing as ATARI BASIC. PERL and JULIA look appealing, it would be nice if there where a program like VSBASIC. 80's... (7 Replies)
Discussion started by: teak
7 Replies
LEARN ABOUT LINUX
checkbashisms
CHECKBASHISMS(1) General Commands Manual CHECKBASHISMS(1)NAME
checkbashisms - check for bashisms in /bin/sh scripts
SYNOPSIS
checkbashisms script ...
checkbashisms --help|--version
DESCRIPTION
checkbashisms, based on one of the checks from the lintian system, performs basic checks on /bin/sh shell scripts for the possible presence
of bashisms. It takes the names of the shell scripts on the command line, and outputs warnings if possible bashisms are detected.
Note that the definition of a bashism in this context roughly equates to "a shell feature that is not required to be supported by POSIX";
this means that some issues flagged may be permitted under optional sections of POSIX, such as XSI or User Portability.
In cases where POSIX and Debian Policy disagree, checkbashisms by default allows extensions permitted by Policy but may also provide
options for stricter checking.
OPTIONS --help, -h
Show a summary of options.
--newline, -n
Check for "echo -n" usage (non POSIX but required by Debian Policy 10.4.)
--posix, -p
Check for issues which are non POSIX but required to be supported by Debian Policy 10.4 (implies -n).
--force, -f
Force each script to be checked, even if it would normally not be (for instance, it has a bash or non POSIX shell shebang or appears
to be a shell wrapper).
--extra, -x
Highlight lines which, whilst they do not contain bashisms, may be useful in determining whether a particular issue is a false posi-
tive which may be ignored. For example, the use of "$BASH_ENV" may be preceded by checking whether "$BASH" is set.
--version, -v
Show version and copyright information.
EXIT VALUES
The exit value will be 0 if no possible bashisms or other problems were detected. Otherwise it will be the sum of the following error val-
ues:
1 A possible bashism was detected.
2 A file was skipped for some reason, for example, because it was unreadable or not found. The warning message will give details.
SEE ALSO lintian(1).
AUTHOR
checkbashisms was originally written as a shell script by Yann Dirson <dirson@debian.org> and rewritten in Perl with many more features by
Julian Gilbey <jdg@debian.org>.
DEBIAN Debian Utilities CHECKBASHISMS(1)