James,
Sorry for the delay in getting to this question - was in an all-day
meeting yesterday.
> The methodology in that book creates essentially a 2 disk system. A
system
> and a page disk. That is bad of course
Yes, I understand that argument. We used a one volume root file system
under the heading of "Keep it as simple as possible, but no simpler."
Perhaps this approach was too simple.
> The IPL device for the cloned system is 280. That will be /dev/dasda or
> /dev/dasdb (my clone isn't IPL'ed or I'd verify it) - Anything else I
bring
> into this with chccwdev will get numbered /dev/dasdc, /dev/dasdd, etc.
That's fine.
>
> I recall the root partition's /dev/dasd{n} label getting hard coded into
> the IPL parameters somewhere under SLES 8 - so when I remove device 280
> from this system everything moves up the tree by one letter. Is that
still
> true? Is this gonna screw things up to the point that I need to build a
> golden image that consists of many mini-disks and clone each HFS to
mirror
> what I want to exist on the target?
I would recommend putting the "dasd={vaddrs}" parameter into
/etc/zipl.conf if for no other reason than you know where to look for the
DASD that the sysadmin (that would be you, but it's possible to forget
what you wanted, like even a few weeks later :)) wants to be utilized.
>
> What are the implications of the the devices being read as 280 (at IPL)
> then 201 - 209...(220 is swap on both the single disk clone and the
> expanded clone). 201 - my new IPL target will be /dev/dasdc during the
copy
> but will be /dev/dasda when I am done....
Hmm...lot of futzing. Would it be possible to reinstall the golden image?
It may be a fair amount of work, but if you do it, I see two adavangages:
(1) You could take better better notes. These notes would be helpful in
documenting your systems.
(2) The disks you install to can be the disks you clone to, and you'll
probably spend less time debugging your modified script.
> What if anything does that do
> when I chroot to the 201-209 devs mounted where I want them under /mnt
and
> do the mkinitrd/zipl? It still seems to see dev 280....Will it fly
> correctly when I remove 280 from the configuration and IPL 202?
I wouldn't recommend mkinitrd and zipl under a chroot'ed system. It is
easy to shut down one system and IPL the other. Then mkinitrd and zipl on
the running system.
But, sometimes chrooting for other tasks is handy. In this case, you
would want the hierarchy of file systems correct. So if you mount the
root file system over /sles9golden/, you would want to mount other file
systems below that appropriately (e.g. mount /usr/ over /sles9golden/usr/,
/var/ over /sles9golden/var, etc.).
Hope this helps.
"Mike MacIsaac" <[EMAIL PROTECTED]> (845) 433-7061
----------------------------------------------------------------------
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
