Make_boot_tape to cd

[Mark Blonde]

Hello,

I'm trying to find a method to make a make_boot_tape and transfer that information to cd. We require a bootable cd that will allow us to point to an ignite server on a different subnet.

I searched ITRC and found a couple of threads that answered this question; however, the answers all pointed to dead links or documents that no longer exist.

Thanks and happy New Year,
Mark

[Steven E. Protter · Accepted solution]

I think you got dead links because make_boot_tape is way out of date. Are we talking 10.20 or before.

make_tape_recvoery is the current way of making a bootable tape with current versions of Ignite.

There are good procedures for making bootable cd's in the current Ignite documentation. These don't use make_tape_recvovery, they use make_sys_image/Golden Image, but if you watch make_tape_recovery run, its useing make_sys_image with different command line options.

Do you want a link to the cd procedure for a current version of Ignite?

SEP

[Mark Blonde]

Thanks for the info. We're using HP-UX 11 so I guess we should be using make_tape_recovery. It sounds like I was looking for the wrong thing.

If you wouldn't mind supplying the link I would really appreciate it.

Thanks for setting me on the right track!

[Pete Randall]

http://www.software.hp.com/products/IUX/index.html

[Mark Lien]

If make_boot_tape is so out of date, why is it included in the latest documentation for ignite, as indicated by your own link (which is also out of date, but had a forwarding link)?

[Bill Hassell]

make_boot_tape is not obsolete, the command make_recovery (instead of make_tape_recovery) is the deprecated command. With current versions of Ignite/UX, the make_recovery command is gone. The make_boot_tape command does *NOT* backup any files. It's sole purpose is to boot a mini-opsystem so you can communicate to a remote (network) Ignite server. While most 9000 servers can boot from the network, the Ignite server must be local because the processor ROMs know nothing about routing.

As far as a forwarding link, the original link has remained unchanged for many years, but like any large company, there are hundreds of web servers and organizational changes dictate (however dubious for the end user) web site name changes.

As far as making a bootable CD/DVD for Ignite usage, checkout the man page for make_medialif. NOTE: Ignite/UX is *always* being updated, both for new hardware (disk, tape, CPU) which is mandatory, and also for new features. Always schedule new Ignite/UX version downloads at least twice yearly, or quarterly. Ignite/UX does not require a reboot and updating will not affect existing backup images.