I am not an expert but the "getconf" command may be what you need:
PLEASE NOTE. I am retracting my answer above, because it's stupid. "getconf -a" does give some good info though all by itself, just not what you are looking for.
Whats the difference between 32bit and 64bit OS's or applications. I understand it a little but its just not clicking the way the teacher explained to me
thanks, any info would be much appreciated (1 Reply)
when using the command :
cat /proc/cpuinfo I get some basic info back on the cpu..
but it doesn't tell me if I am using a 64 or 32 bit processor ..
a) is this the right command to find this ?
b) if it is not what is ? and how do I get that information..
thanx moxxx68 (2 Replies)
Where can I get a list that maps the each Linux version to corresponding 32/64 bits model?
e.g.
OS -> Model (ILP32, LP64, ...)
RHLE3 -> ?
RHLE4 -> ?
RHLE5 -> ?
...
It would be better if there is such a list that contains most of current UNIX OS versions.
... (1 Reply)
Is there an 'easy' way to convert 32Bit code to 64Bit code. I have this benchmark i need to run on different machines and it would be nice if i could run it on the 64 bit machines ass wel.
The output when compiling(1) and running(2) are the following:
(1)
linux:/home/user1/subbench/heapsort #... (7 Replies)
i have solaris 10 x86 64bit installed on my pc (dell 3100). i then decided to move my hard drive to another pc (dell 4600). I noticed that each time i boot up, the OS show as 32 bit (instead of 64bit) and i can't even get past this stage to the login page.
when i moved it back to dell 3100 it... (13 Replies)
Friends ,
Would u plz tell me what is the difference between 32-bit Linux o/s and the 64 bit Linux o/s .
Is there any RAM limitation in this two types of o/s .
Waiting for kind reply ... ... (7 Replies)
I have an application which builds and executes without error on a 32bit implementation of Linux. When I transferred the code to a new project on a 64bit implementation, the code will build without error, but the pthread functions, such as pthread_attr_setschedparam() return an 'Invalid Argument'... (3 Replies)
Hi Gurus,
I need to check whether the compiler installed in my system supports 64bit compilation.
Server - Sun fire v490
OS - Solaris 5.9
Processor - Sparcv9 (64bit)
Install Directory - /opt/SUNWSpro
Compiler Model - Sun Forte C Compiler.
My development team is claiming that there... (20 Replies)
How to enable more than 4GB RAM support on Linux 32bit OS?
OS: CentOS release 5.4 (Final)
Kernel version: 2.6.18-53.el5
Arch: 32Bit
I got solution at Innovationframes.com • View topic - How to enable more than 4GB RAM support on Linux 32bit OS? but my question is the steps given... (5 Replies)
Hi,
I have a C code which builds and works fine on 32bit linux machine.
Now i want to convert that code to build and run on 64 bit linux machine. I dont want to maintain two separate sources for 32 and 64 bit build. Same source should get build on 32 as well as 64 bit machine (when a... (2 Replies)
Discussion started by: bhushan123
2 Replies
LEARN ABOUT FREEBSD
getconf
GETCONF(1) BSD General Commands Manual GETCONF(1)NAME
getconf -- retrieve standard configuration variables
SYNOPSIS
getconf [-v environment] path_var file
getconf [-v environment] system_var
DESCRIPTION
The getconf utility prints the value of a POSIX or X/Open path or system configuration variable to the standard output. If the specified
variable is undefined, the string ``undefined'' is output.
The first form of the command, with two mandatory arguments, retrieves file- and file system-specific configuration variables using
pathconf(2). The second form, with a single argument, retrieves system configuration variables using confstr(3) and sysconf(3), depending on
the type of variable. As an extension, the second form can also be used to query static limits from <limits.h>.
All sysconf(3) and pathconf(2) variables use the same name as the manifest constants defined in the relevant standard C-language bindings,
including any leading underscore or prefix. That is to say, system_var might be ARG_MAX or _POSIX_VERSION, as opposed to the sysconf(3)
names _SC_ARG_MAX or _SC_POSIX_VERSION. Variables retrieved from confstr(3) have the leading '_CS_' stripped off; thus, _CS_PATH is queried
by a system_var of ``PATH''.
Programming Environments
The -v environment option specifies a IEEE Std 1003.1-2001 (``POSIX.1'') programming environment under which the values are to be queried.
This option currently does nothing, but may in the future be used to select between 32-bit and 64-bit execution environments on platforms
which support both. Specifying an environment which is not supported on the current execution platform gives undefined results.
The standard programming environments are as follows:
POSIX_V6_ILP32_OFF32 Exactly 32-bit integer, long, pointer, and file offset. Supported platforms: None.
POSIX_V6_ILP32_OFFBIG Exactly 32-bit integer, long, and pointer; at least 64-bit file offset. Supported platforms: IA32, PowerPC.
POSIX_V6_LP64_OFF64 Exactly 32-bit integer; exactly 64-bit long, pointer, and file offset. Supported platforms: Alpha, SPARC64.
POSIX_V6_LPBIG_OFFBIG At least 32-bit integer; at least 64-bit long, pointer, and file offset. Supported platforms: None.
The command:
getconf POSIX_V6_WIDTH_RESTRICTED_ENVS
returns a newline-separated list of environments in which the width of certain fundamental types is no greater than the width of the native C
type long. At present, all programming environments supported by FreeBSD have this property. Several of the confstr(3) variables provide
information on the necessary compiler and linker flags to use the standard programming environments described above.
EXIT STATUS
The getconf utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
The command:
getconf PATH
will display the system default setting for the PATH environment variable.
The command:
getconf NAME_MAX /tmp
will display the maximum length of a filename in the /tmp directory.
The command:
getconf -v POSIX_V6_LPBIG_OFFBIG LONG_MAX
will display the maximum value of the C type long in the POSIX_V6_LPBIG_OFFBIG programming environment, if the system supports that environ-
ment.
DIAGNOSTICS
Use of a system_var or path_var which is completely unrecognized is considered an error, causing a diagnostic message to be written to stan-
dard error. One which is known but merely undefined does not result in an error indication. The getconf utility recognizes all of the vari-
ables defined for IEEE Std 1003.1-2001 (``POSIX.1''), including those which are not currently implemented.
SEE ALSO pathconf(2), confstr(3), sysconf(3)STANDARDS
The getconf utility is expected to be compliant with IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
The getconf utility first appeared in FreeBSD 5.0.
AUTHORS
Garrett A. Wollman <wollman@lcs.mit.edu>
BSD September 18, 2002 BSD