boot lan - install as opposed to boot lan install

[Sean McConkey_5]

On my PA-RISC boxes I have to use bo lan - install , not a big deal other then having to remember to use the dash but any ideas why? The RXIA64 boxes boot fine without the dash.

I'm running Ignite C.7.12.519

[Torsten.]

The question is not clear (to me).

Usually you use

boot lan.ip_address

with or without install option.

[Sean McConkey_5]

OK if I type boot lan install or boot lan.ip.add.re.ss install on a PA RISC machine it fails to find the Ignite server and errors after a long wait as if there is no LAN connection.

If I do boot lan install on a IA64 system it boots almost immediately.

To get it to work on a PA-RISC system I have to type boot lan - install , the dash is normally not required. As I said it's no show stopper but I am just curious as to why I have had to start inserting the dash.

[Steven E. Protter]

Shalom,

You have encountered a new feature.

I don't recall ever using a dash on PA-RISC.

You have the option of setting up an Ignite server and having the Ignite server Boot Client option taking care of this, if of course you are working with a system that is already on the LAN and configured.

Otherwise, you are using a verion of Ignite that is stable and your methodology is sound.

I've tested this Ignite version and the only thing I found is that if you disable legacy I/O you can't recover systems backed up with make_net_recovery

SEP

[Sean McConkey_5]

Shalom Steven

Yep Never had to use the dash in the past and I think I stumbled on it by having my Solaris Jumpstart head on when doing the Ignite boot.

Oh well it will remain a mystery no doubt just like HP's decision to shutdown itrc. :o)