typo in the doc "hp-ux virtual administrator's guide"?

[Hanry Zhou]

http://docs.hp.com/en/T1335-90098/T1335-90098.pdf

If you read through
"Page 165, and section 3", you will find that
all these commands were executed on the same "winona1" vpar server. I don't feel it is correct, the last two commands on PA-RISC and INTERITY platform really should be executed on "winona2" vpar server. Am I correct?

2nd question. I understand you would use "mkboot.." command to put bootable strings on the disk on PA-RISC platform, but what I don't understand is, how come here the same command is used on INTEGIRITY platform. I thought we should use "efi_cp -d.." command to copy the string over?

Please let me know. Thanks!

[sujit kumar singh]

hi Henry,

for the point no2 as stated please refer to the Manpages of the mkboot command.

mkboot if run on an Itanium system with -a "boot_string" option , creates the AUTO file in the /EFI/HPUX/AUTO of the disk and when run with -a "boot_string" on a PARISC machine creates or uodates the AUTO file in the LIF area of the disk.


for the point no2 as stated please refer to the Manpages of the mkboot command , i refereed to that on 11iv3, mkboot(1M) and can find out that in the examples sextion

EXAMPLES
Install default boot programs on the specified disk, treating it as an LVM disk:
mkboot -l /dev/dsk/c0t5d0
Use the existing layout, and install only SYSLIB and ODE files and preserve the EST file on the disk:
mkboot -i SYSLIB -i ODE -p EST /dev/rdsk/c0t5d0
Install only the SYSLIB file and retain the ODE file on the disk. Use the Whole Disk layout. Use the file
/tmp/bootlf to get the boot programs rather than the default. (The -i ODE option will be ignored):
mkboot -b /tmp/bootlf -i SYSLIB -i ODE -p ODE -W /dev/rdsk/c0t5d0
Install EFI utilities to the EFI partition on an Itanium-based system, treating it as an LVM or VxVM disk:
mkboot -e -l /dev/dsk/c3t1d0
Create AUTO file with the string autofile command on a device. If the device is on an Itanium-based
system, the file is created as /EFI/HPUX/AUTO in the EFI partition. If the device is on a PA-RISC system,
the file is created as a LIF file in the boot area.
mkboot -a "autofile command" /dev/dsk/c2t0d0



Regards
sujit

[Hanry Zhou]

Could anybody else please check out these two questions? Thanks!

[Eric SAUBIGNAC]

Bonjour Hanry,

2nd point : "mkboot -a" works the same way on PA-RISC or Itanium. Of course you need to be uptodate with the fileset that contains command mkboot. Here is a little test :

# efi_cp -u -d /dev/disk/disk10_p1 EFI/HPUX/AUTO /tmp
# cat /tmp/AUTO
boot vmunix
# mkboot -a "I will survive" /dev/disk/disk10
# efi_cp -u -d /dev/disk/disk10_p1 EFI/HPUX/AUTO /tmp
# cat /tmp/AUTO
I will survive

Eric

[Eric SAUBIGNAC · Accepted solution]

1st point. In a first reading, I do agree with you :

and after logging into winona2 which owns the alternate boot disk at 0/8/0/0.5.0,
execute:
â PA-RISC: winona1# mkboot -a "hpux /stand/vpmon -a" /dev/rdsk/c1t5d0
â Integrity: winona1# mkboot -a "boot vpmon -a" /dev/rdsk/c1t5d0

Should be :

and after logging into winona2 which owns the alternate boot disk at 0/8/0/0.5.0,
execute:
â PA-RISC: winona2# mkboot -a "hpux /stand/vpmon -a" /dev/rdsk/c1t5d0
â Integrity: winona2# mkboot -a "boot vpmon -a" /dev/rdsk/c1t5d0

In this page you are supposed to set boot path from 2 different vpar. So ...

[Hanry Zhou]

Here is why I feel confused. I thought following is the command I should use on INTEGRITY to create the boot string:

#print 'boot vpmon -a' > /tmp/AUTO
#efi_cp -d /dev/rdsk/s1 /tmp/AUTO /EFI/HPUX/AUTO

Now, you are saying "mkboot.." will do the same on INTEGRITY? or these two commands will perform different things?

[Eric SAUBIGNAC]

Yes. In the same way than under PA-RISC "mkboot -a ..." and "lifcp ..." will do the same thing : writing a string boot in file AUTO in the proper location. But my English is not so good, and maybe I missunderstand your question ?

[sujit kumar singh]

Hi


For Point no2,


Please refer to the man page of the command mkboot(1m). This is for 11iv2 Mar 2008.

Please look in the exapmles page 446.



As Eric Suggests it is always good to have the latest patches or patch bundles for the OS that runs your applications. So better to have the latest filesets for the mkboot command also .

Thanks Eric

Regards
Sujit

[sujit kumar singh]

Hi

I forgot to mention the MAn pages online link:

That is

http://docs.hp.com/en/B2355-90781docs/B2355-90781docs.pdf

Please look in the exapmles page 446.



Regards
Sujit

[Hanry Zhou]

My qeustion was not how to use "mkboot" command. On INTEGRITY platform, when I create boot string, which following command I should use? don't they perform the same thing?


#print 'boot vpmon -a' > /tmp/AUTO
#efi_cp -d /dev/rdsk/c1t5d0s1 /tmp/AUTO /EFI/HPUX/AUTO

AND

mkboot -a "boot vpmon -a" /dev/rdsk/c1t5d0