HP-UX network Install from Linux Server

[C. David]

Hi,
Im working on a solution to install HP-UX systems by network from a linux server (without Ignite-UX).

Do you think it is technically possible to do it, i've searched on the net a similar solution, but i didnt find any thing, perhaps it's impossible?

thx in advance

[Jeff Schussele]

Hi,

I really don't think that dog will hunt.

Rgds,
Jeff

[Pete Randall]

Highly unlikely!


Pete

[Senthil Kumar .A_1]

Hi David,

I do not think it is possible.

By the way , who knows HP could be integrating Lin os istallation to be done from Ignite in future, now that Itanium ,can be installed with Linux or win 2003. I should say thats a great Idea, and secondly if this activity is assigned to you at your office, I should say will be an intersting one.

One more curious query, Why would you be interested in installing HPUX from a Ignite that should be running on Linux.

Regards,
Senthil Kumar .A

[Jeff Schussele]

The point here is that Ignite is very *far* removed from something like Glance or OV.
There's just no comparison.....

My 2 cents,
Jeff

[Senthil Kumar .A_1]

Hi Again,

Just reconsidering on my previous post, I would even doubt a solution of the kind to be provided by HP. Because , I see the remote installation as a feature of a OS rather than specific to Hardware. So if you need to have a product like Ignite in linux for remote installation of its clone itself, the Linux community need to be working on this,Let alone the fact - of installing HPUX from Linux server which is a secondary to the prime concern.

Regards,
Senthil Kumar .A

[Armin Kunaschik]

Think positive... possible is everything :-)
It's just a matter of time and ressources.

I think it's possible with a couple of drawbacks (this is not tested)
You need an Ignite-UX Installation to get the boot kernels.
Put them in the same directories as they reside on the HP-UX box.
Configure TFTP the same way and get bootp and NFS running.
Then you need to debug the inst_bootp service to find out how exactly to configure bootp (e.g. boot parameters).
I think this is the hardest part.
Finally put a make_net_recovery archive on a NFS server and install this instead from a depot source.

Personally I would not waste that time and just put the ignite software on a node with some spare disk space.
This diskspace is small compared to the space you need for your usual software/patch depots.

My 2 cents,
Armin