HPUX 32bit

[chula]

Hello, could anyone tell me if its possible to boot HPUX 11iV2 into 32bit kernel? If so, how?

Many thanks

[A. Clay Stephenson]

11iv2 (11.23) only exists as a 64-bit OS so that dog won't hunt. However, 11.23 is perfectly capable of producing and executing 32-bit code so there is no need for a 32-bit kernel.

[Torsten.]

"HP-UX 11i v2 supports only the 64-bit version of the HP-UX kernel."

see

http://docs.hp.com/en/5991-5526/ch02s03.html

[melvyn burnard]

In a word:
No!

It is 64 bit ONLY!

[rick jones]

The comments about the HP-UX 11iv2 kernel being a 64-bit only kernel are spot-on. What is prompting you to want to boot a 32-bit kernel? Do you have some sort of add-on kernel module which is not yet 64-bit? Or are you trying to run the bits on an older PA 1.1 (32-bit only) set of hardware?

[whiteknight]

Chula,

11iv2 is only for 64 bit kernel


WK


http://forums1.itrc.hp.com/service/forums/helptips.do?#33
please take a moment to give them credit for their assistance!

[chula]

Thank you for all your replys. I was given some software to test on PARISC 32bit HPUX, the SUN and AIX systems have 32bit kernal capabilities but I was unsure regarding HP.

I think the software for HPUX is labelled wrongly, I believe its actually 64bit.

Thanks again for your comment.

[Dennis Handly]

>I think the software for HPUX is labelled wrongly, I believe its actually 64bit.

As mentioned if this is user software it doesn't matter. It only matters if this is some type of kernel driver.

[Steven E. Protter]

Shalom,

32 bit applications will run, but the last OS that would install on a 32 bit system was 11.11 PA-RISC.

SEP

[Scott Donaldson]

Well,

Yes, 32 bit applications, that DON'T use shared memory will run fine on a 64 bit kernel. I had the opportunity to test a 32 bit flavour of a PICK database on a 64 bit kernel.

I had to work with the developer to hack out the shared memory feature so that it would work.

So its not just 'kernel drivers' that aren't compatible.

[Don Morris_1]

Wha-huh? 32-bit applications can use shared memory (Posix or SysV) just fine on a 64-bit kernel. I can assure you folks would be screaming bloody murder for years now if this weren't the case.

Now, 32-bit applications are still limited by their runtime environment when it comes to setting up shared memory, certainly. By default, a 32-bit application only gets 2Gb of shared address space [depending on OS and architecture -- PA prior to 11.31 would set aside 256Mb of that for shared Memory Mapped I/O] -- but that's even more true with a 32-bit kernel. Sharing between 32-bit and 64-bit is possible (and folks do it all the time), but you may have to use flags like MAP_GLOBAL when the 32-bit application also uses Memory Windows or MAP_ADDR32 if the 64-bit application creates the shared object so that the 32-bit application can still find it.

Perhaps you can be more clear on the problem you saw?