Sponsored Content
Full Discussion: Solaris (verify 64 or 32 bit
Top Forums UNIX for Dummies Questions & Answers Solaris (verify 64 or 32 bit Post 11118 by witt on Thursday 29th of November 2001 07:32:35 AM
Old 11-29-2001
Solaris (verify 64 or 32 bit

Hello !!

Does anyone know how can I verify if my Solaris is 32 or 64 bit ??

Thank you !

Witt
witt
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Is the solaris v9.For.x86 64 bit

Dear everyone: Could you tell me where is the 64 bit's solaris v9.0. :p (2 Replies)
Discussion started by: arwang
2 Replies

2. Solaris

64 bit solaris 9

How can I tell if im running a 64 bit version of solaris? (1 Reply)
Discussion started by: csaunders
1 Replies

3. Solaris

32 / 64 bit OS in Solaris

Dear All, This is Viswanadhan, new to Sun Solaris domain. In Sun Solaris ( SPARC ) has 32 bit and 64 bit OS. While insallation of OS there no specific option for 32 / 64 bit OS .On which basis OS installs for 32 / 64 bit OS ? Regards, Viswanadhan. (1 Reply)
Discussion started by: viswanadhan
1 Replies

4. Solaris

Which version and Bit of Solaris OS

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

5. Solaris

How to verify Sun Solaris installation

Does anybody have an idea, how to verify Sun Solaris installation? (3 Replies)
Discussion started by: agarwal
3 Replies

6. Solaris

Solaris 64-bit to 32-bit

I had previous implemented the following in my menu.lst to be able to get to 32-bit operations. # title Solaris 10 32-bit root (hd0,0,a) kernel /platform/i86pc/multiboot kernel/unix module /platform/i86pc/boot_archive </code> Now, it is not working as I get the following error : ... (0 Replies)
Discussion started by: praveenr
0 Replies

7. Shell Programming and Scripting

how to verify sqlplus not installed on solaris

i want to write shell script that exit by displaying error if sqlplus is not installed. The platform is oracle10g on solaris sparc. I tried the which sqlplus command, but it returns errorcode 0 even sqlplus is not installed. Kindly help? (3 Replies)
Discussion started by: mmunir
3 Replies

8. Solaris

Porting C++ 32-bit code on 64-bit Solaris

Hi, I am trying to convert 32-bit code to 64-bit. I have defined function int main() { int* l; size_t len1; fun(len1); return 0; } void fun(int* ptr) { cout<<"\nsizeof(ptr)"<<sizeof(ptr); } However while compiling getting error as : Error: Formal argument ptr... (2 Replies)
Discussion started by: amit_27
2 Replies

9. Solaris

Solaris os 32 bit or 64 bit

:confused: how to find out wether my os is 32 bit or 64 bit. I am using Solaris 5.6. also i want to know the difference between 32 bit and 64bit os. any help will be much appreciated as i am in urgent need of this information (6 Replies)
Discussion started by: asalman.qazi
6 Replies

10. HP-UX

Verify 4 GB Limit is overcome in 64 Bit Processor

We are moving from a 32 Bit PA-RISC processor to 64 Bit Itanium processor based System. I am aware that 64 Bit processor allows for memory (RAM) addressibility beyond the 4 GB memory (RAM) limit imposed by a 32 bit processor I have been asked to prove that the new systems are capable of... (6 Replies)
Discussion started by: allanbm
6 Replies
id32_alloc(9F)						   Kernel Functions for Drivers 					    id32_alloc(9F)

NAME
id32_alloc, id32_free, id32_lookup - 32-bit driver ID management routines SYNOPSIS
#include <sys/ddi.h> #include <sys/id32.h> uint32_t id32_alloc(void *ptr, int flag); void id32_free(uint32_t token); void *id32_lookup(uint32_t token); INTERFACE LEVEL
Solaris architecture specific (Solaris DDI). PARAMETERS
ptr any valid 32- or 64-bit pointer flag determines whether caller can sleep for memory (see kmem_alloc(9F) for a description) DESCRIPTION
These routines were originally developed so that device drivers could manage 64-bit pointers on devices that save space only for 32-bit pointers. Many device drivers need to pass a 32-bit value to the hardware when attempting I/O. Later, when that I/O completes, the only way the driver has to identify the request that generated that I/O is via a "token". When the I/O is initiated, the driver passes this token to the hardware. When the I/O completes the hardware passes back this 32-bit token. Before Solaris supported 64-bit pointers, device drivers just passed a raw 32-bit pointer to the hardware. When pointers grew to be 64 bits this was no longer possible. The id32_*() routines were created to help drivers translate between 64-bit pointers and a 32-bit token. Given a 32- or 64-bit pointer, the routine id32_alloc() allocates a 32-bit token, returning 0 if KM_NOSLEEP was specified and memory could not be allocated. The allocated token is passed back to id32_lookup() to obtain the original 32- or 64-bit pointer. The routine id32_free() is used to free an allocated token. Once id32_free() is called, the supplied token is no longer valid. Note that these routines have some degree of error checking. This is done so that an invalid token passed to id32_lookup() will not be accepted as valid. When id32_lookup() detects an invalid token it returns NULL. Calling routines should check for this return value so that they do not try to dereference a NULL pointer. CONTEXT
These functions can be called from user or interrupt context. The routine id32_alloc() should not be called from interrupt context when the KM_SLEEP flag is passed in. All other routines can be called from interrupt or kernel context. SEE ALSO
kmem_alloc(9F) Writing Device Drivers SunOS 5.11 12 Dec 2001 id32_alloc(9F)
All times are GMT -4. The time now is 08:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy