10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
All,
We have a physical server (Lenovo 3950) that we need to upgrade the OS from RHEL 6 to RHEL 7. We do not want to do an in-place upgrade but rather start with a fresh OS install. The plan is to remove the two local drives (Raid 1) and install two new drives for the fresh RHEL 7 install. ... (4 Replies)
Discussion started by: hburnswell
4 Replies
2. UNIX for Beginners Questions & Answers
Hi All,
Now we are migrating oracle 11G from Solaris Sparc 10 to RHEL 7. We have 1000+ ksh scripts..
Could you please let em know what would be the best way to use exiting scripts in RHEL with minimal changes,.
my concern was "Is it all Solaris command work in RHEL". (3 Replies)
Discussion started by: mssprince
3 Replies
3. Red Hat
Hi Gurus,
We are migrating Oracle from Solaris to RHEL 7 and looking for Solaris equivalent commands for Linux.
we are using lot of korn shell scripts built on Solaris so, i am looking for equivalent commands which are using in Solaris..
Could you please help me here by proving any info ... (4 Replies)
Discussion started by: mssprince
4 Replies
4. Shell Programming and Scripting
Hi Gurus,
We are migrating Oracle from Solaris to RHEL 7 and looking for Solaris equivalent commands for Linux.
we are using lot of korn shell scripts built on Solaris so, i am looking for equivalent commands which are using in Solaris..
Could you please help me here by proving any info... (1 Reply)
Discussion started by: mssprince
1 Replies
5. Red Hat
Hi All,
I have one logical volume with size as 900G and it is mounted as xfs file system.
Now I want to reduce this partition to 500G.
So I followed the below steps.
unmount the mount point /home
Reduced the volume using the command
Now I remounted the partition.
But the problem... (3 Replies)
Discussion started by: kalpeer
3 Replies
6. UNIX for Advanced & Expert Users
We are in the process of migrating storage from one array to another. I know the commands I would use in LVM but I am not very familiar with VxVM.
The goal is to attach the new LUNs from the new array and add them to the disk group. Then mirror the data online to these new LUNs using VxVM... (4 Replies)
Discussion started by: keelba
4 Replies
7. SuSE
Hi,
I'm trying to migrate the content of disk 'A' to disk 'B', that they belong to the same vg 'data'_vg'. Whe using pvmove, I get the following error: 'device-mapper: suspend ioctl failed: Interrupted system call'. I put down the whole trace:
pvmove -v "source_disk" "sink_disk"
... (0 Replies)
Discussion started by: Begnux
0 Replies
8. UNIX for Dummies Questions & Answers
Hi Guys,
I m using redhat 6, I have installed root partition as non-LVM .
Is there any way i can convert it to LVM? (1 Reply)
Discussion started by: pinga123
1 Replies
9. AIX
Hi,
I'm able to migrate UNIX users/groups from Solaris to AIX (with same password using 13-char encrypted password from shadow file) but no luck with RHEL 5 to AIX.
I see encrypted password in RHEL 5 is bit lengthier than 13-char. Is there any way to convert encrypted password such that same... (1 Reply)
Discussion started by: reddyr
1 Replies
10. Filesystems, Disks and Memory
Hiya,
Is there a known method from converting LVM data to VxVM data..
ie we have a load of local and SAN (HPDM) mounts on RHEL 4u5/5u1 servers which are now required to be clustered with SFS (VxFS,VxVM,CFS,VCS etc)
I've come across the vxvmconvert, but thought that was HP-UX only?
Many... (3 Replies)
Discussion started by: itsupplies
3 Replies
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)
