assuming the entire directory structure is under /mnt (including /boot)

chroot /mnt
zipl

> -----Original Message-----
> From: James Melin [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, September 10, 2003 1:51 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Slightly fuzzy on what to do next in making a copy of a
> system on new volumes IPL-able
>
>
> So what do I do in a situation like this then? Sounds like a
> catch-22.  The
> dasd in question is not bootable as is. I need to make it
> bootable using
> zipl, and I don't want to have to boot an installl/recovery disk to do
> these things because I'm rather trying to keep the DR
> recovery of Linux out
> of the hands of the venodor staff (having them boot the initrd)
>
>
>
> |---------+---------------------------->
> |         |           Adam Thornton    |
> |         |           <[EMAIL PROTECTED]|
> |         |           mine.net>        |
> |         |           Sent by: Linux on|
> |         |           390 Port         |
> |         |           <[EMAIL PROTECTED]|
> |         |           IST.EDU>         |
> |         |                            |
> |         |                            |
> |         |           09/10/2003 01:45 |
> |         |           PM               |
> |         |           Please respond to|
> |         |           Linux on 390 Port|
> |         |                            |
> |---------+---------------------------->
>
> >-------------------------------------------------------------
> -----------------------------------------------------------------|
>   |
>                                                                    |
>   |       To:       [EMAIL PROTECTED]
>                                                                    |
>   |       cc:
>                                                                    |
>   |       Subject:  Re: Slightly fuzzy on what to do next in
> making a copy of a system on         new volumes IPL-able           |
>
> >-------------------------------------------------------------
> -----------------------------------------------------------------|
>
>
>
>
> On Wed, 2003-09-10 at 13:30, James Melin wrote:
> > I have created copies of my original system, and mounted them in
> approriate
> > relative positions under /mnt (/mnt/var /mnt/usr, etc).
> >
> > This makes my 'new IPL device'  address b213 - which is
> mounted as dasdg1
> >
> > in /mnt/boot I have the original parm file.  Yast, of
> course moved my
> swap
> > device to dasda.. Anyway....
> >
> > rockhopper:/mnt/boot # more parmfile
> > dasd=a240,b217,b219,b21a,b218,a241 root=/dev/dasdb1 noinitrd
> > rockhopper:/mnt/boot #
> >
> > I know to change all the device numbers to their
> corresponding deviuces,
> > but root= parameter?do I leave it as /dev/dasdb1 and run
> zipl, or do I
> > change it to /dev/dasdg1 for the running of zipl. I just
> wanna make sure
> > the boot record goes to the right place.
>
> Whatever you make it, that has to be where it's found at IPL.
>  It *also*
> has to be where it's found when you run zipl to get the boot signature
> correctly written.
>
> Adam
>

Reply via email to