From: McCracken, Denise (Denise.McCracken@misyshealthcare.com)
Date: Thu Apr 08 2004 - 19:46:09 EDT
I have a script that creates install.cdf files for upgrades from
4.0f to 5.1a, and I just noticed something funny.
It always sets the controller_number parameter to 0, no matter which
bus the target root drive is on. The reason this seems funny to me is that
the install still works.
I'm doing one now with the root on bus1, controller_number set to 0
and the target disk as dsk0 in the cdf file, and the install works just
fine. I looked at the original install.cdf from when a fresh start was done
and controller_number was set to 1.
I've fixed the script so that it writes the bus number as
controller_number. Is this the correct thing to do? Does 5.1a ignore this
parameter since the new device naming convention?
thanks
-denise
PS, thanks to everyone who sent me followups about suppressing the
voldisk output. I had it backwards, and I should have to put the 2&>1 after
the redirection to /dev/null and not before.
"Customer service may be the only way that a
company can distinguish itself from its
competition these days." -H. Frank Gibbard
Denise McCracken, Systems Software Specialist
Misys Health Care, Tucson, AZ
Certified Tru64 v5 Systems Administrator
Comptia Network+ Certified Professional
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:56 EDT