Jim, Since you are using a 2.2 kernel, any DASD changes you make will require a re-boot of your system. Depending on how extensive the changes are you plan to make, it may very well be simpler to just do a re-install. (You won't learn as much, perhaps, but it might be quicker.)
To "turn off" a swap device issue a "swapoff /dev/dasda1" and it will stop using it as a swap device. If you then edit /etc/fstab to remove the line that pointed to it, it will not be used on the next system startup. To "turn on" a swap device, it needs to be already accessible (see below) to your system. A "mkswap /dev/dasd?1" followed by "swapon /dev/dasd?1" will do the job. Update /etc/fstab to point to it for future system startups, and you're done. To add or remove DASD volumes, you need to edit /boot/parmfile, then re-run silo. Understand that how you do this is important. Linux will assign device names in the order they are specified in your parmfile. /dev/dasda will be the first one, _always_. /dev/dasdb will be the second one, _always_. And so on. For example, if device number B040 moves from being the first number specified to the third number, it will go from being /dev/dasda to /dev/dasdc. So, you need to think about what your device names are now, and what they're going to be after you make your changes. Updating /etc/fstab to have the correct information for the next reboot will be critical. What you want to do is very doable, it's just going to require some thought and planning. Mark Post -----Original Message----- From: James Melin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 19, 2002 9:19 AM To: [EMAIL PROTECTED] Subject: Follow up to "Cant IPL after install" Mark Post: This is a follow up for you on the unanswered question of PAV volumes in the HFS but not as root volume. In the native LPAR configuration with FICON and a switch, under which I was unable to boot a freshly installed system installed on a PAV device, I have successfully used a PAV volume as swap and as part of the file system. This demonstrates PAV access once booted is NOT a problem (as I suspected since I could install to them). I wanted you to know that the theoretical had been tested, For the list at large: I now must resolve the fact that I have the PAV devices in my HFS and as a swap volume and I'd like to change them without burning down the house. It appears that yast made my swap volume dasda, but in any case I have dasdb1 mounted at /, dasdd1 mounted at /usr and dasdc1 mounted at /var I intend to copy the /var tree to dasdb1 and unmount dasdc1. I would then like to add a swap volume using a 1 gb custom volume in the shark box. So I need to know the following: First, how do I go about changing the swap volume so that on the next IPL it uses the new swap volume and releases the old one. Secondly, how do I remove dasdc1 and dasda1 (the devices are B040 and B041) from the installed configuration so they will not be accessed on the next IPL, Third, how do I make other volumes available once I've got an installed configuration. The other complication is that the head systems programmer wants to give me a dedicated escon channel with only the devices I've been given for current and future use (a total of 8 devices, 4 - 9 gig devices and 4 - 1 gig devices) so that's going to mess things up more isn't it? Any advice in coping with this situation or would it be easier to rebuild the universe ?
