06-09-2009
In Solaris, from the command line run this command:
/usr/bin/isainfo -kv
If your OS is 64-bit, you will see output like:
64-bit sparcv9 kernel modules
If your OS is 32-bit, you will get this output:
32-bit sparc kernel modules
For Linux users
If you are running Linux, you can check your distribution with the uname command:
uname -m
The output will read x86_64 for 64-bit and i686 or similar for 32-bit.
10 More Discussions You Might Find Interesting
1. Programming
how to check the version of Library
version of Program &
version of file.
while compile pro*c program, I got error like elf error: no string table
if u have any suggestion then give me urgently. (1 Reply)
Discussion started by: dilipluhar
1 Replies
2. UNIX for Dummies Questions & Answers
i am using sunOS 5.8. What is the command to know the OS bit (8,32,64...) while the server is under production and is it possible to change from one bit to another??
replies appreciated
raguram R (2 Replies)
Discussion started by: raguramtgr
2 Replies
3. Solaris
Hello
1) How can I find what bit of OS I am running on? 16 bit, 64 bit?
2) What is the difference in having different bits?
3) Below is the output of /etc/release/ what are all these components meaning?
$ more /etc/release
Solaris 10 11/06 s10x_u3wos_10 X86
$
Thank... (7 Replies)
Discussion started by: panchpan
7 Replies
4. Solaris
Hi All,
Please advice me how i can check the Oracle version on my UNIX Solaris machine without logging in to oracle?
Thanks,
Am (1 Reply)
Discussion started by: am_yadav
1 Replies
5. Solaris
Hi All,
Looks a foolish question, but please can someone tell me the command to check version of Solaris OS?
Thanks,
Am (5 Replies)
Discussion started by: am_yadav
5 Replies
6. AIX
Hi all,
I am facing problem in porting to 64 bit AIX especially with compiling options to compile and run under 64 bit kernel.Can any one put some light on the issue
thanks in advance
vishal (14 Replies)
Discussion started by: vishalzone2002
14 Replies
7. Linux
Can someone try to compile this older version of xtide (attached) on 64-bit Intel/Linux and upload the xttpd binary? I have a friend who needs an older version up and running because the newer version does not support his required harmonic files.
Thanks! (7 Replies)
Discussion started by: Neo
7 Replies
8. Shell Programming and Scripting
Hi ,
While executing perl scripts , sometimes cpu consumption is going to 100% and perl script is asking to abort.
In perl script , iam having some powershell commnands.
out of 10 times , 9 times script runs fine and 1 time its throwing the above error.
Iam using windows 2008 64 bit... (2 Replies)
Discussion started by: penchal_boddu
2 Replies
9. Red Hat
How to check the installed OHS 10.1.3.3 web server is 32 bit or 64 bit on OLE 5.4 (64 bit) OS (7 Replies)
Discussion started by: nuthakki
7 Replies
10. Windows & DOS: Issues & Discussions
Hello everyone.
I bought a dell laptop (XPS M1330) online which came without a hard drive. There is a Windows Vista Ultimate OEMAct sticker with product key at the bottom case. I checked dell website (here) for this model and it says this model supports both 32 and 64-bit version of Windows... (4 Replies)
Discussion started by: milhan
4 Replies
LEARN ABOUT DEBIAN
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)