 |
» |
|
|
|
Before 10.0, HP-UX provided different I/O subsystems on different
hardware platforms. This meant, for example, that the Series 700
did not support Series 800 drivers. HP-UX 10.0 introduced a single,
unified I/O subsystem that allows both Series 700 and Series 800
I/O drivers to run in the same kernel. Major Changes for I/O Convergence | |
The major features of I/O convergence are: A single set of kernel configuration
utilities. SAM will do kernel builds via config(1M).
You can also use config
yourself, or, preferably, mk_kernel(1M).
SAM, mk_kernel
and config are
supported on both Series 700 and 800. uxgen
is not supported on 10.x. See “Kernel Convergence ” for more information. A single convention for creating and naming device
files. The convention comprises: A single scheme for disk layout. See “Disk Management ”. Some changes in driver naming and support. See “Drivers ”.
Major and Minor Numbers | |
As of 10.0, HP-UX supports a single set of major numbers,
and a single method for assigning minor numbers, across the Series
700 and 800 platforms. This means, for example, that the device
file for a SCSI disk will look the same on both kinds of system,
in some cases allowing devices to be interchanged freely between
Series 700 and 800 systems, and in general making it easier to write
drivers and applications for HP systems. Converging major and minor numbers entails the following specific
changes: Series 800 Logical Unit (LU)
numbers are no longer supported. They are replaced by instance numbers. See “LU Numbers and Instance Numbers” below. Peripherals must be accessed via different major
and minor numbers in 10.x from those that would be used on a 9.x
system. This should not cause you problems unless you use mknod
in code or scripts; run prepare(update_aid)
to check for instances of mknod. See the Configuring HP-UX for Peripherals
manual for details of the new numbering scheme. Some major numbers are being reserved for HP drivers. But major numbers that have been reserved for non-HP drivers
in the past have not been touched. Some major numbers will be assigned dynamically
at boot time. But device files that use these major numbers will keep the
same name in 10.x as they have on your current 9.x system.
See “How This Affects Your System”,
“I/O Convergence and 9.x Code
and Scripts ”, and “Avoid mknod ” for more information. LU Numbers and Instance NumbersLU numbers
were assigned to all devices on Series 800 systems at the time of
bootup. As of 10.0, this no longer happens. Instead, on both Series
700 and 800 systems, the HP-UX I/O system assigns each device an
instance number, which (like LU
numbers) does not change when you reboot the system. Instance numbers of interface cards (that is, the cards to
which peripherals such as disks and printers are connected) play
an important role in binding the device driver to the device; they
are represented in the minor number and, by the 10.x naming convention,
in the device file name (see “Device File Naming Convention ” later in this section). Instance numbers are used (and can
be seen in ioscan)
on all HP-UX 10.x systems, whereas LU
numbers were assigned only on Series 800 systems. LU
numbers on pre-10.0 systems are comparable to device instance numbers
on 10.x systems, in that they identify each device type uniquely
at bootup. But the only instance numbers you as a system administrator
need to be concerned with are those assigned to interface cards. LU
numbers changed at each boot. Instance numbers for interface cards
are preserved across bootups, in the ioconfig
files.
As you can see by running ioscan(1M)
on a 10.x system, the INTERFACE
hardware type is subdivided into classes.
Examples of interface classes are ext_bus,
lan, tty,
ps2, graphics,
lantty, lanmux,
audio, pc,
and hil. The
I/O system assigns separate sets of instance numbers to each class
of interface; you can see this by looking in the I
column in the output from ioscan -f. The following are some points to note about interface numbers
and classes: Class is assigned by interface driver
that claims a card, not by the card itself. This allows driver developers to introduce their own classes. Instance numbers are repeated between classes but
are always unique within a class. Instance numbers are not necessarily consecutive. Instance numbers are assigned in the order cards
are bound to their drivers.
Guidelines for Working with 10.x Device Files Always check the output of ioscan(1M)
before interpreting an instance number. Use insf(1M),
mksf(1M) or SAM
whenever possible to create device files; this will protect you
from making mistakes with major and minor numbers. When creating a device special file, use the instance
number of the interface card to which the device is attached,
not the instance number of the device itself.
For more information, see the section “insf(1M), lssf(1M), mksf(1M), rmsf(1M)” in this document, the manpages, and the Configuring
HP-UX for Peripherals manual. How This Affects Your SystemWhen you upgrade from 9.x, the upgrade software will create
new device files for the devices on your system, changing the names
and major and minor numbers to conform to the 10.0 conventions.
(See the Upgrading from HP-UX 9.x to 10.x
manual for details and exceptions. See “Device File Naming Convention ” for information on the new naming convention.) The upgrade software will also set symbolic links that link
the old device-file names on your system to the new 10.01 device
files. But you need to check code and scripts for calls to mknod;
these will probably create device files that are invalid for 10.01. I/O Convergence and 9.x Code
and Scripts 9.x code and scripts that deal explicitly with I/O devices
and drivers will probably need to be modified before you can run
them on a 10.x system. When checking for compatibility, remember
that: Many 9.x device-file names are not
valid on 10.x. See “Device File Naming Convention ”. 9.x device files, and 9.x calls to mknod(1M),
probably use major or minor numbers that are not valid on 10.x. Not all drivers supported before 10.0 are supported
on 10.x. See “Drivers ”.
HP has provided tools to help you make these checks. See “Preparing for I/O Convergence”. Also see “Avoid mknod ”
for more information. When you add a new peripheral to a 10.01 system, you should
normally use insf(1M)
or mksf(1M),
or SAM, rather than mknod,
to create the device file for you. This will keep you from having
to make literal reference to unfamiliar major and minor numbers. See the Configuring HP-UX for Peripherals
manual for instructions on configuring new devices into your 10.x
system, and a full explanation of the new major and minor numbering
scheme. Device File Naming Convention | |
In all past releases, device files on the Series 700 have
been named by one convention, and device files on the Series 800
by another. For example, a printer connected to a serial interface
on a Series 800 would have a device file name such as /dev/tty6p1,
whereas on a Series 700 the name would be something like /dev/ptr_rs232a. In HP-UX 10.x, device file names on both the Series 700 and
800 have the form: prefix [id | devspec] [options] where: - prefix
is /dev/
or a directory relative to it (/dev/diag/,
for example) - id
is an arbitrary number or designator, for example
0m in the default
tape device file /dev/rmt/0m.
id should be
used only for system default device files or device files used by
pseudo drivers that have no direct relationship to hardware. In
all other cases, use devspec. - devspec
indicates the hardware path, in the form, where: - c#
is the instance number of the card to which the
device is attached (unique per SPU). The number is base-10 and can
be from one to three digits. It is assigned by the I/O system and
does not change when you reboot. It is the number in the I
column in the output of ioscan(1M).
(See “Major and Minor Numbers ” earlier in
this section.) - t#
is the address set on the device (for example the
HP-IB address, or SCSI "target" number). The number is base-10 and
can be one or two digits; the typical range is 0-15. - d#
is the device unit number (for example, SCSI LUN
or HP-IB unit).
id or devspec (preferred)
must form part of the name unless prefix is
sufficient to specify the device. - options
are device specific, for example, _lp
to indicate a printer, or s#
to indicate a disk section number. (Leaving the s#
out of a disk device file name implies that the file addresses the
whole disk.)
The following section shows some examples. - /dev/rdsk/c0t6d0
SCSI disk on interface card 0, SCSI address 6, SCSI
LUN 0 (whole disk access indicated by absence of s#). - /dev/c0t1d0_lp
SCSI printer on interface card 0, SCSI address 1,
SCSI LUN 0. - /dev/rmt/c0t2d0m
SCSI tape drive on interface card 0, SCSI address
2, SCSI LUN 0, medium density.
System Default File Names System default file names such as /dev/lp
and /dev/rmt/0m
will continue to exist in 10.x; they will be symbolic links to the
actual device files named according to the convention just described.
For example, /dev/rmt/0m
might be a link to /dev/rmt/c0t2d0BEST. How This Affects Your SystemWhen you upgrade your system to 10.01, the upgrade software
will modify both the contents of most device
files (because major and minor numbers are changing — see
“Major and Minor Numbers ”) and their names
(in accordance with the new convention described in this section).
But the upgrade software will set symbolic links that link the old
names to the new device files. So code and scripts that invoke the old names will continue
to work, but you need to check for calls to mknod.
HP has provided tools to help you do this. See “Preparing for I/O Convergence”. The upgrade software will also remove device files used by
drivers that are no longer supported (see “Drivers ”). You should normally avoid using mknod(1M)
to create device files on 10.01. Use insf(1M)
or mksf(1M),
or SAM, instead. This will keep you from having to make literal
reference to unfamiliar major and minor numbers. See the Configuring HP-UX for Peripherals
manual for instructions on configuring new devices into your 10.x
system. Disk Management | |
Logical Volume Manager (LVM) is offered on both the Series
700 and the Series 800 as of 10.0, and HP encourages you to adopt
this method of disk management. Older methods, such as hard partitions
(Series 800) and SDS (Series 700) are being phased out; see “Support Matrix for Disk Management
Methods ” later in this
section for more information. New Features and Capabilities
of LVM Supported on Series 700. All features of LVM (including root, dump and swap, and the
new features in this list) are available on both the Series 700
and the Series 800. For LVM commands that are new on the Series
700, and changed on the Series 800, see “LVM Commands ” later in this section. Disk striping of a logical volume. LVM striping replaces SDS (Software Disk Striping). Under
LVM you can set the stripe size to 4, 8, 16, 31, or 64 KB. The default
is 8 KB. The number of disks you can stripe across must be at least
two but cannot exceed the number of disks in your volume group. Disk mirroring. LVM and the MirrorDisk/UX product support all features of
DataPair/800. DataPair/800 itself is no longer supported. New features
include: lvsplit(1M)
can operate on more than one logical volume. A volume group can be activated as read-write on
one system and read-only on another. This allows you to do backups on the read-only system; but
note that a single logical volume can be accessed
from only one system at a time.
For more information, see Chapter 7, "Mirroring Data Using
LVM," in the HP-UX System Administration Tasks
manual. Physical volume links for HP High Availability Disk
Arrays. Allows dual links (or paths) to the same disk, such that if
one link to the disk fails, LVM automatically routes the I/O to
an alternate link. Disk locking (Series 800). The optional product MC/ServiceGuard,
available at 10.0 on the Series 800 only, provides a disk locking
mechanism within LVM to ensure that disks that are connected to
two or more systems are accessed by only one system at a time. For
more information, see the Managing MC/ServiceGuard
manual (part number B3936-90001).
The following commands were new on the Series 700 at 10.0
and, where noted, changed on the Series 800. Refer to the manpages
for more details. lvcreate(1M)
— revised to support disk striping lvdisplay(1M)
— revised to support disk striping lvmerge(1M)
— revised to support addition of atomic sync lvsplit(1M)
— revised to support addition of atomic sync vgchange(1M)
— revised to support addition of off-line backup vgdisplay(1M)
— revised to support addition of off-line backup
In addition, LVM commands have been modified to call vgcfgbackup
automatically whenever you make a configuration change; see Chapter
3 in the HP-UX System Administration Tasks
manual for details. Products and Features No
Longer Supported DataPair/800 This product was no longer supported as of 10.0, but 10.x
LVM supports its features on both the Series 700 and Series 800
via the optional product MirrorDisk/UX. See
“Preparing for I/O Convergence”. Mirrored striped disks are not supported
on 10.x. Software Disk Striping (SDS) (Series 700). This product was replaced by LVM disk striping as of 10.0.
New SDS disks cannot be configured into 10.01, but: Existing single
SDS striped disks will continue to be supported by means of a compatibility
driver (cpd)
which will be automatically bound into the new kernel when you upgrade
from 9.x if you have disks in this configuration. (This does not
apply to SDS on the root disk because that configuration has never
been supported.) Existing SDS disk arrays will
be automatically converted for you to LVM volume groups during the
upgrade from 9.x.
Hard partitions. Hard partitions are supported on 10.x for all disks that supported
them as of 9.04. They are not supported for new disks introduced
at 10.0 or later, or for disks that did not support them at 9.04. For 10.01: insf(1M)
will not create device files for disk partitions (it will create
a single device file for the whole disk) but you can create them
yourself, for disks that support them, using mksf(1M). The definitions of sections 0 and 2 were swapped
as of 10.0; see “Other Changes ”
later in this section. You cannot install 10.x to
a hard-partitioned root disk (that is, "cold install" as opposed
to upgrading); SD will offer you the choice of two types of access
to the root disk: You can upgrade from 9.x to
10.x using a hard-partitioned disk that was supported as of 9.04.
Support Matrix for Disk Management
Methods Logical Volume Manager (LVM) is the disk management scheme
HP recommends for 10.0 and later releases running on both the Series
700 and 800. Older methods are being phased out. The following table shows what level of support, if any, HP-UX
10.x provides for disk management schemes that were supported in
9.x: SDS, hard partitions, whole-disk, and LVM. Management 10.x Can Convert Can Install
Scheme Supports? to LVM? 10.x to?
=========================================================
SDS: yes yes (arrays) no
Hard partitions: yes yes no
Whole disk: yes yes yes
LVM: yes - yes |
The names and contents of your disk
device files will change when you upgrade to 10.01. See “Device File Naming Convention ” and “Major and Minor Numbers ”. For hard-partitioned disks (Series 800), the definitions
of sections 2 and 0 have been swapped: Section 0 = whole disk access (old
section 2) Section 2 = old section 0
This is to create consistency between the Series 700 and the
Series 800.
No data will be moved or overwritten. Transition
links created by the upgrade software will ensure that
code accessing the whole disk via section 2 at 9.x will continue
to read and write to the whole disk at 10.01, and that disk access
to 9.x section 0 is redirected to 10.01 section 2. How This Affects Your SystemThe favored disk-management method for 10.01 is LVM. But if
you want to continue as before, and you are not using DataPair/800
for disk mirroring, you do not need to do anything to prepare your
disks for the upgrade to 10.01: your 9.x configuration will either
be supported by compatibility drivers or, in the case of SDS disk
arrays, automatically converted for you when you upgrade. If you are using DataPair/800, you must
migrate to MirrorDisk/UX before you upgrade.
MirrorDisk/UX is an optional product that runs
under LVM. For instructions on migrating from DataPair/800
see Chapter 8, "Managing Logical Volumes," in the 9.0 Series 800
version of the HP-UX System Administration Tasks
manual. If you want to make broad disk-management changes (for example
from hard partitions to LVM), the upgrade to 10.01 may or may not
be a good time to do it. For information and advice, see "Disk Configurations
in 9.x and 10.01". Disk Configurations
in 9.x and 10.01 The table below shows existing (9.x) configurations and possible
10.01 configurations. The "Action Needed" column shows what, if
anything, you need to do to get from one to the other. Series 700:
===========
- 9.x - - 10.x- Action
Root Disk Data Disks Root Disk Data Disks What HP-UX Does Needed
========= ========== ========= ========== =============== ======
Single disk Single disks Single disk Single disks Same as 9.x None
Single disk SDS array Single disk LVM striped Converts SDS None
volumes array to LVM
during upgrade
via sdstolvm
See Note 1.
Single disk SDS single Single disk Single disk Supports SDS None
disk disk via com-
patibility
driver
Single disk SDS single Single disk LVM striped Supports disk Convert
disk volumes via LVM disk to LVM.
See Note 2.
Single disk Any LVM disk Any Supports See Note 3.
disk via LVM
Single disk Single disks Single disk LVM disks Supports disks Convert
via LVM disks to
LVM.
See Note 2. |
|
|
Series 800:
===========
- 9.x - - 10.01- Action
Root Disk Data Disks Root Disk Data Disks What HP-UX Does Needed
========= ========== ========= ========== =============== ======
Partitions Partitions Partitions Partitions Supports disks None
via compat-
ibility driver
Partitions LVM Partitions LVM Supports disks None
via compat-
ibility driver,
LVM
LVM LVM LVM LVM Supports disks None
via compat-
ibility driver,
LVM
Partitions Partitions Partitions LVM Supports disks Convert
via compat- disks
ibility driver, to LVM.
LVM See Note 2.
LVM Any LVM LVM striped Supports disks Convert
via LVM disks to
LVM.
See Note 2.
Partitions Any LVM Any Supports disk See Note 3.
via LVM |
Configurations Not Supported in 10.x SDS arrays. These will be converted to LVM during the upgrade. See Note
1. SDS root disk. This configuration has never been supported.
Notes 1. SDS disk arrays. During the upgrade to 10.01, the sdstolvm
utility runs automatically and converts SDS disk arrays to an LVM
volume group, removing SDS device files and updating /etc/fstab
(the 10.x version of /etc/checklist). These disks will be managed by the Logical Volume Manager
(LVM) under 10.01. See Chapter 3, "Managing Disks Using the Logical
Volume Manager (LVM)," in the HP-UX System Administration
Tasks manual. 2. Data disks (other than SDS disk arrays). You do not have to convert these disks to LVM in order to
upgrade to 10.x. If you want to convert your disks, do the following: a. Upgrade to 10.x. b. Back up the data on the disks. c. Configure the disks as LVM (or LVM striped) disks. Use SAM if you have not done this before. For more information,
see Chapter 3, "Managing Disks Using the Logical Volume Manager
(LVM)," in the HP-UX System Administration Tasks
manual. d. Recover the data. 3. Root (system) disk. You do not have to convert your root disk to LVM in order
to upgrade to 10.01, and you cannot do it during the upgrade. If you want to convert the root disk, you must do it either
before or after upgrading to 10.01 on a Series 800. See the Upgrading
from HP-UX 9.x to 10.x manual for instructions on converting
the root disk while running 9.x. On a Series 700, you must upgrade
to 10.01 before you can use LVM. See the HP-UX System
Administration Tasks manual for directions for converting
once you are on 10.01. Drivers | |
HP-UX 10.x allows drivers written for both the Series 700
and the Series 800 to run in the same kernel. This implies some
modifications for existing drivers. Checklist for Driver
Developers Developers of 9.x in-house and third-party drivers should
modify these drivers as follows: Take account of the new converged
minor number scheme. Include new header information and an install entry
point. Remove hard-coded bus-dependent service calls. Remove calls to services that directly access the
I/O tree or manipulate manager indices. Modify the way the driver obtains and stores device
instance numbers (see “LU Numbers and Instance Numbers” earlier in this chapter). Associate the driver header with the isc
entry for the hardware. Take account of the U2 I/O adapter and cache coherence
on the Series 800 Model K and the Series 700 Model J if the driver
needs to run on those platforms.
For detailed guidance, Series 700 driver developers should
refer to the 10.01 version of the Driver Development
Guide. HP does not publish guidelines for Series 800
drivers. Unmodified 9.x drivers will continue to run on 10.01 if they are EISA, non-SCSI drivers; and were written in accordance with HP's guidelines
in the then-current version of the Driver Development
Guide and do not use a major number that is pre-empted by
an HP driver in 10.01 (see “Major and Minor Numbers ” earlier in this chapter).
But developers will need to do some work to take account of
the restructuring of the information that is stored in /etc/master
in 9.x. A new scheme is in effect as of 10.0; see “Kernel Convergence ” later in this chapter. HP has added the following drivers: System New Driver Description
===========================================================
700/800 cpd Compatibility pseudo-driver (for
compatibility with 9.x SDS and hard
partitions).
700/800 kepd Kernel entry point driver. |
For more information on compatibility between 9.x and 10.01
disk management schemes, see “Disk Management ” earlier in this chapter. System Old Name New Name Description
===========================================================
700 parallel centif Centronics parallel port driver.
700/800 autoch ssrfc MO surface driver.
700 scsi sdisk SCSI disc driver.
700 autox schgr MO autochanger driver. |
The MO autochanger driver will still be named autox
on the Series 800. See also “Autochanger Driver and Device
Files ”. System Driver Description
===========================================================
700 sds Software Disk Striping.
800 mirror DataPair.
800 gpio0 CIO GPIO driver.
800 gpio1 NIO GPIO LDM.
800 gpio11 NIO GPIO DM.
800 pdisc Superseded by cpd (see
"New Drivers").
700 s2tape SCSI-2 tape (functions taken
over by scsi_tape driver). |
Autochanger Driver and Device
Files Autochanger driver behavior has changed. As of 10.0, you can
mount only as many platters as there are actual autochanger drives,
and HP-UX creates only as many device files as are needed to communicate
with those drives. In addition, hard-partitioning on autochanger
surfaces is no longer supported, and the device-file naming convention
has changed, as explained under “Device File Naming Convention ” earlier in this section. 9.x autochanger device files will be removed during the upgrade
to 10.01. Because there have been major changes in the 10.0 autochanger
driver, HP recommends that you consult the manual Installing
and Administering Optical Jukeboxes on HP 9000 Series 700 and 800
Systems, HP part number 5960-7624 (Edition 3) to determine
what changes, if any, you will need to make to your applications. Autochanger Virtual Mounting The single largest change in autochanger functionality is
that virtual mounting is no longer supported. Specifically, with
the 10.0 ssrfc
driver, you can have only as many surfaces simultaneously mounted
(open) as there are drives in the autochanger. Additionally, the
"A" and "B" sides of the same cartridge cannot be opened at the
same time using the ssrfc
driver. The 9.x driver allowed you to virtually mount any or all of
the surfaces in the autochanger, and would handle the details of
physically mounting surfaces in drives when they were accessed for
I/O. With ssrfc,
when a surface is opened, it is placed in a drive if possible. If
no drives are available, the process requesting the surface will
block (sleep) unless the request is performed with an O_NDELAY
(nonblocking) flag, in which case the open request will fail with
EBUSY. This change may affect scripts or applications that invoked
the 9.x autoch
driver, and now need to invoke the 10.0 ssrfc
driver. Series 700 SCSI Subsystem
and Disk Driver The HP-UX 10.x Series 700 SCSI Subsystem and Disk Driver have
been converged with the Series 800 SCSI Disk Driver in the following
ways: Default Immediate Reporting
behavior Some new Series 800 systems are capable of using sdisk,
the SCSI disk driver primarily designed for the Series 700. Immediate Reporting,
or WCE (Write
Cache Enable) behavior is now controlled by a new tunable parameter,
default_disk_ir.
This parameter has a profound effect on file system (and raw disk)
performance and, conversely, on data integrity if the drive is powered
down. Immediate Reporting
can be turned either ON
(set to 1) or OFF
(set to 0). If default_disk_ir
is not explicitly set in the /stand/system
file used to create the kernel, it is assumed to be OFF
(0). On new systems, systems on which you "cold install" 10.01,
and systems you upgrade from 9.x to 10.01, default_disk_ir
is set to ON
(1) on Series 700s and OFF
on Series 800s. With Immediate Reporting
set to ON, disk
drives which have data caches complete writes when the data is cached,
rather than completing once the data is on the disk. This may improve
write performance, especially for sequential transfers. But cached
data may be lost if a device powerfailure or reset occurs before
the device moves the data to the disk. On Series 800 systems, HP
recommends that you set this value to OFF
(0). default_disk_ir
also affects delayed-write versus write-through file system behavior. Support for LVM High Availability features The disk driver can return error codes for which the Logical
Volume Manager (LVM) has recoverability mechanisms. This behavior
is similar to that of the Series 800 disk drivers.
Series 700/800 Tape DriverThe HP-UX 10.x tape driver incorporates into one common set
of options the configuration options previously offered by only
the Series 700 or 800 driver (with the exceptions listed under “Tape Driver Differences
on the Series 700 and 800 ”
later in this section). Other changes: Configuration bits redefined. The new scheme includes a configuration Property Table containing
an array of user-definable configuration choices. You can invoke
the Property Table as an option through the minor number. Major numbers changed. Series 700: Major numbers 54 and 121 are not supported on 10.x. The new
major number 205 provides the configuration options previously available
through 54 or 121. Series 800: Major number 212 replaces major number 5.
Naming convention. 10.x tape device-file names reflect the configuration options
now available in the minor number.
For information on configuring tape drives, see the Configuring
HP-UX for Peripherals manual and the 10.01 mt(7),
scsi_tape(7),
mksf(1M), insf(1M),
rmsf(1M), and
lssf(1M) manpages. The new conventions for device-file naming and major and minor
numbers are discussed earlier in this section: see “Device File Naming Convention ” and “Major and Minor Numbers ”. Tape Driver Differences
on the Series 700 and 800 Series 700 options not available on
Series 800 (except Model K): Series 800 modes not available on Series 700:
The driver also differs between Series 700 and 800 systems
in its approach to devices it does not recognize. On the Series 700, the driver will attempt to open any tape
device, even if it is a model it does not recognize; whereas on
the Series 800, the driver will try to open only the devices that
are on its list. This means that the list of devices that will work with the
Series 800 driver is fixed, but the Series 700 list includes devices
that "might work" but have not been certified as supported by Hewlett-Packard. See the Configuring HP-UX for Peripherals
manual for more information. How This Affects Your SystemWhen you upgrade to 10.01, the upgrade program will remove
non-HP drivers (and HP drivers in filesets currently not loaded).
The 9.x dfile
or gen file that
includes the drivers is saved in /stand/system.old.
The 9.x /etc/master
file is saved in /etc/upgrade/save/hostname/etc/master. The upgrade program will also remove the device files associated
with these drivers. (You may still be able to use in-house and third-party
drivers; see “Unmodified Drivers ”.) Preparing for I/O Convergence | |
Before upgrading from a 9.x to a 10.x system, do the following: Contact application vendors and in-house
developers to make sure that any non-HP drivers you depend on will
port smoothly to 10.01. Use the tools supplied in the Upgrade Preparation
Media Tools package to identify references to 9.x device file names
(except system default names such as /dev/lp,
which are still recognized on 10.01 systems), and calls to mknod
that use major and minor numbers that are invalid on 10.01. Replace
these with calls to mksf
or insf. For details, see the Upgrading from HP-UX 9.x to
10.x manual. If you are using DataPair/800,
you must migrate to MirrorDisk/UX before you
upgrade. MirrorDisk/UX is an optional product
that runs under LVM. For instructions on migrating from DataPair/800,
see Chapter 8, "Managing Logical Volumes," in the 9.0 Series 800
version of the HP-UX System Administration Tasks
manual.
|
Printable version
