Nick: 'dasdfmt' does not care if you have already formatted with CMS. Pre-format with CMS allows you to skip 'dasdfmt' in some cases.
There is a boot parm token of the form "dasd=220-22f" which gets consumed by the DASD driver if it is statically compiled into the kernel, or must be supplied to the DASD driver when loaded after-the-fact as a module. Either way, the DASD driver needs to be told what addresses to use. If you're adding disks without bouncing Linux (or without unload/reload of the module), then you have to do the echo trick, which is the moral equivalent of a kernel command telling the driver, "you've got more!". For the disks to be usable, they most certainly will have to show up in /proc/dasd/devices. You should also see at least one entry for each disk in /proc/partitions (up to for lines for some disks). Look at /proc/partitions and /proc/dasd/devices. It will begin to make sense (after your eyes get adjusted to the glare). ;-) You will also want the "device file" in /dev, but it is useless if there is nothing behind it, nothing really there for the driver to do I/O with. Most installers will sort-of as a courtesy pre-populate /dev with a boat load of device files. To complicate matters, there is this concept of "devfs", which replaces the normal directory /dev with a pseudo directory /dev that changes under kernel control. You can tell if you're using devfs with a 'df' command. Specifically, if 'df /dev' reports stats for the root, then you are NOT using devfs and life is "easier". -- R; ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
