Error received when I was trying to check state of boot record
Hello,
This is a test/lab LPAR. Recently installed and updated the SP/TL. everything seems to be working fine. (ran all post install checks)
I checked the state of boot record, received the following error/failed message. Can you please explain what does this mean ?
I've tried re-created the boot image using bosboot -ad /dev/hdisk0. But still the same.
My home PC is dual boot with Linux and Win98. I want to upgrade both to a newer version, and have the Linux CD's now. What I need to know is does Win2K Pro stomp (write over LiLo) on the boot record like NT (2 Replies)
I am trying to code a ksh script that will check to see if all 26 incoming ftp files have been received before proceeding to the next function, which is to rename each file.
Here is the pseudo-code of what I am trying to do:
<<STEP_1>>
IF all ALS files have been transmitted then... (2 Replies)
Advance Thanks.
(1) I would like to know any unix/Linux command to check EOF char in a file.
(2) Or Any way I can check a file has been reached completely at machine B from machine A. Note that machine A ftp/scp the file to machine B at unknown time. (5 Replies)
Hello everyone,
I'm having some difficulty trying to convert a MBR file with hex codes into a "translated" version, where the output explains the contents of the file. For example, a table of primary partitions that I want to translate into plain english:
--- MBR: ---
Partition 1 - 80 01... (2 Replies)
Hello and thanks in advance for any help anyone can offer
Hopefully this is a simple question but is the Volume Boot Record (VBR) only used in Windows? I've seen references to it in relationship to Windows & not Linux... but I'm not sure if that means it's unique to Windows or not. If it is... (1 Reply)
Hello Guys,
Here is the requirement!!
I want to check the mail with attachment received or not through unix scripting.
And send an notification email when mail with attachment already received.
Any thoughts on this is much appreciated!!
Regards,
Harry (0 Replies)
I have a program that i need to get done that gets the person's name and his grade then prints it in this order "name-grade-gradeletter" so i wrote this code:
#!/bin/bash
while :; do
read -p "Enter the person's name: " name
read -p "Enter the grade of the person: " grade
case $grade in
)... (3 Replies)
Discussion started by: UniverseCloud
3 Replies
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES SEE ALSO mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)