Hi Mark, My task and problem is not: having to bring a device online, and yes, we are running on kernel 2.6.
We worked out a method to clone the system (for different purposes, involving different DASD and networking hardware) . But we do not do this by the known clone procedure that involves mount-and-modify the copied system as to DASD and network-scripts (see PS). Our method consists of 1. a fake initramdisk with changed DASD addresses that can be accessed via boot menu parameter 2. a network script in init.d that routes to different /network-scripts/-directories with the appropriate (different) configuration depending on a parameter given to the system at IPL time also via (modified) boot menu In this way we have a boot menu that enables us to boot different systems with different hardware, governed by zipl.conf paramaters. Well ... but: When trying this configuration, I ended up with "kernel panic" ;-)) Next thing I thought of was: I forgot about modprobe conf. I remembered that when establishing a new device in a running system one has to modify - among others - modprobe.conf. So now I am trying to copy my system to new DASD and IPL there. This different DASD is established by means of a different intrd that can be accessed by way of this new zipl.conf. But it is not established by way of modprobe.conf. And I think this might be the reason for the kernel panicking. And this is why I wanted to change modprobe.conf just for the time the system gets copied over ... PS Why I am afraid of the "semi-official" clone method: mounting the DASD where I copied the system and wanting to change configuration files this way may be risky because the home system and the mounted system both have the very same LogVol-setup. Same setup, meaning also same names/labels. So even if I edit a config file accessing it with an explicit path, the LogVol-manager may get upset or confused because it can find these files on both LogVols. But maybe you have an idea ...? Kind regards Anna -----Original Message----- From: Linux on 390 Port on behalf of Mark Post *EXTERN* Sent: Thu 3/27/2008 3:44 PM To: [email protected] Subject: Re: modprobe.conf >>> On Thu, Mar 27, 2008 at 6:26 AM, in message <[EMAIL PROTECTED]>, Fuhrmann Anna <[EMAIL PROTECTED]> wrote: -snip- > Can I modify modprobe.conf so that in contains the *wrong* DASD addresses > for a while > (this should happen for the sake of copying the system DASD as a whole so > that the ready copy > contains the modified modprobe.conf for another LPAR with a different DASD > config. Anna, Why do you think you have to modify modprobe.conf to do this? I have to believe that you're running on a 2.6 kernel, so you should be able to use chccwdev to bring the devices online and offline without modifying any configuration files. Mark Post ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
