Re: Clone SUSE 10

2009-01-28 Thread Undetermined origin c/o LISTSERV administrator
elp, Russell Jones ANPAC System Programmer rjo...@anpac.com -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Tom Duerbusch Sent: Wednesday, January 28, 2009 1:08 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Clone SUSE 10 There are two places w

Re: Clone SUSE 10

2009-01-28 Thread Mark Post
>>> On 1/28/2009 at 1:15 PM, "Jones, Russell" wrote: -snip- > I changed my dasd fstab setting to use device path, ipl'ed my base > system, shut it down, copied the volume using mvs dss copy, ipl'ed the > base system and mounted the cloned file system on the base system. I > then did a chroot to

Re: Clone SUSE 10

2009-01-28 Thread Tom Duerbusch
om -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Wednesday, January 28, 2009 10:12 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Clone SUSE 10 >>> On 1/28/2009 at 9:58 AM, "Jones, Russell" wrote: > Should th

Re: Clone SUSE 10

2009-01-28 Thread Jones, Russell
om -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Wednesday, January 28, 2009 10:12 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Clone SUSE 10 >>> On 1/28/2009 at 9:58 AM, "Jones, Russell" wrote: > Shou

Re: Clone SUSE 10

2009-01-28 Thread Mark Post
>>> On 1/28/2009 at 9:58 AM, "Jones, Russell" wrote: > Should the parameters in /etc/zipl.conf look like: > > root=/dev/dasda1 ro noinitrd No. If you do, your system won't boot. Just add 'dasd=addr1,addr2" to what is there now. Mark Post -

Re: Clone SUSE 10

2009-01-28 Thread Tom Duerbusch
st.edu] On Behalf Of Tom Duerbusch Sent: Tuesday, January 27, 2009 5:08 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Clone SUSE 10 When you installed you SLES 10 system, you took the defaults for FSTAB. Change you base system: yast System Partitioner, yes edit each disk fstab options

Re: Clone SUSE 10

2009-01-28 Thread Jones, Russell
: LINUX-390@VM.MARIST.EDU Subject: Re: Clone SUSE 10 When you installed you SLES 10 system, you took the defaults for FSTAB. Change you base system: yast System Partitioner, yes edit each disk fstab options change Device ID to Device Path, ok ok apply

Re: Clone SUSE 10

2009-01-27 Thread Tom Duerbusch
on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Tuesday, January 27, 2009 3:43 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Clone SUSE 10 >>> On 1/27/2009 at 4:38 PM, "Jones, Russell" wrote: -snip- > I want 322b to be my ipl volume and also brin

Re: Clone SUSE 10

2009-01-27 Thread Mark Post
>>> On 1/27/2009 at 4:54 PM, "Jones, Russell" wrote: > I do mean root file system. Here is my zipl.conf. I don't see any device > address in this file. -snip- > [SLES_10_SP1] > image = /boot/image-2.6.16.54-0.2.10-default > target = /boot/zipl > ramdisk = /boot/initrd-2.6.16.54-0.2.

Re: Clone SUSE 10

2009-01-27 Thread Jones, Russell
st.edu] On Behalf Of Mark Post Sent: Tuesday, January 27, 2009 3:43 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Clone SUSE 10 >>> On 1/27/2009 at 4:38 PM, "Jones, Russell" wrote: -snip- > I want 322b to be my ipl volume and also bring 322f online at startup. By IPL volum

Re: Clone SUSE 10

2009-01-27 Thread Mark Post
>>> On 1/27/2009 at 4:38 PM, "Jones, Russell" wrote: -snip- > I want 322b to be my ipl volume and also bring 322f online at startup. By IPL volume, do you mean root file system? (The two are completely different things.) What do you have in /etc/zipl.conf? Mark Post

Re: Clone SUSE 10

2009-01-27 Thread Jones, Russell
ssell Jones ANPAC System Programmer rjo...@anpac.com -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Tuesday, January 27, 2009 1:43 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Clone SUSE 10 >>> On 1/27/2009 at 1:54 PM, &

Re: Clone SUSE 10

2009-01-27 Thread Mark Post
>>> On 1/27/2009 at 1:54 PM, "Jones, Russell" wrote: > Thanks, that looks like what I need. How about changing the dasd > addresses? Start here: http://www2.marist.edu/htbin/wlvtype?LINUX-VM.71317 Mark Post -- For LINUX-390

Re: Clone SUSE 10

2009-01-27 Thread Jones, Russell
@VM.MARIST.EDU Subject: Re: Clone SUSE 10 >>> On 1/27/2009 at 11:21 AM, "Jones, Russell" wrote: > I am in the process of cloning an existing SUSE 10 system to run in > different LPAR. I have copied the file system and mounted it on a > running system. I need to change the

Re: Clone SUSE 10

2009-01-27 Thread Mark Post
>>> On 1/27/2009 at 11:21 AM, "Jones, Russell" wrote: > I am in the process of cloning an existing SUSE 10 system to run in > different LPAR. I have copied the file system and mounted it on a > running system. I need to change the device address for eth0 and I am > not sure where/how to make the

Clone SUSE 10

2009-01-27 Thread Jones, Russell
I am in the process of cloning an existing SUSE 10 system to run in different LPAR. I have copied the file system and mounted it on a running system. I need to change the device address for eth0 and I am not sure where/how to make the change. Thanks in advance for your help, Russell Jones ANPA

Re: Clone SUSE 10

2008-12-18 Thread Michael MacIsaac
Mark, > If you really want to do cloning anyway, check out the Virtualization > Cookbook for SLES10 SP2: http://www.redbooks.ibm.com/abstracts/sg247493.html Yes, thanks. The cloning method described in the cookbooks makes a lot of assumptions about z/VM being the underlying hypervisor. However,

Re: Clone SUSE 10

2008-12-17 Thread Mark Post
>>> On 12/17/2008 at 2:02 PM, "Jones, Russell" >>> wrote: > I am running SUSE 10 in an LPAR. I would like to clone the system on a > different volume and run it in a different LPAR. I have been through > this process before with a Slackware system. I was wondering if SUSE > ships with tools to

Clone SUSE 10

2008-12-17 Thread Jones, Russell
I am running SUSE 10 in an LPAR. I would like to clone the system on a different volume and run it in a different LPAR. I have been through this process before with a Slackware system. I was wondering if SUSE ships with tools to make the process more automated. Thanks, Russell Jones ANPAC S