kernel config hacking on Tru64 v5.1

From: Mark Scarborough <mscar-osf_at_cactus.org>
Date: Sat, 24 Feb 2001 08:10:00 -0600

I'm trying to update my "largest" box from 4.0G to 5.1.

This box is an 8400 with 4 PCI busses, 26 SCSI busses (mostly going to EMC Symmetrix's),
and about 670 total disk devices totaling approximately 3 TB. This is our Data
Warehouse...

Ever since I took over the management of this box it has been necessary to "hack" the
kernel config file to keep the SCSI busses in a particular order so that the device names
would not change. It's a real pain, but it isn't that hard.

I was fully expecting this time to be more involved because of Tru64 v5.x's new disk
naming scheme, but I wasn't expecting the kernel config file to be so completely
different! The config file generated by the 'installupdate' procedure doesn't contain
_any_ of the familiar lines like:

bus isp5 at pci6...
controller scsi20 at isp5...

Instead, it has lines like this:

config_driver isp
config_driver scsi

This appears to be configuring the controllers and busses "automagically". This is kind
of cool but it doesn't give me the ability to control the order of the busses.

So what am I going to do? So many of the devices are re-named that LSM refuses to start.

I tried copying back my 4.x config file but the 'doconfig' failed immediately because of
differences in the config file.

Suggestions?

Thanks,

Mark


-- 
Mark Scarborough
Lead Unix Admin
Broadwing Communications
Mark.Scarborough_at_broadwing.com	(mailto:Mark.Scarborough_at_broadwing.com)
Received on Sat Feb 24 2001 - 14:11:18 NZDT

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:41 NZDT