Re: Boot from FCP on vintage hardware

[Richard Troth]

Since you're on VM, you could present the boot disk as EDEV and stamp
an FBA bootstrap on it.






On 2010-03-18, Moeur Tim C  wrote:
> Hey list -
>
> I've been hunting through IBM documents for this answer but so far no
> gold.  Perhaps one of you will save me a lot of time.
>
> I'm building zLinux images to use zfcp file systems as the /boot
> directory.  This works well here at home on our Z10.  Our DR machine,
> however, is an older z-890, code level unknown.  I'm able to mount the
> zfcp devices on already running booted-from-3390-dasd images, but when I
> attempt to ipl (this is as a VM guest) the boot-from-zfcp image it
> instantly drops into a CP Program interrupt wait error.  There appears
> to be no attempt (or messages) to resolve the wwpn and lun path
> information that I've build into the image with mkinitrd.
>
> I'm thinking that the z890 doesn't support a boot from zfcp.  Can anyone
> confirm this?
>
> Tim
> tim.mo...@srpnet.com
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>

--
Sent from my mobile device

-- R;   <><

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Boot from FCP on vintage hardware

[Raymond Higgs]

Tim,

I haven't looked at an old OS/2 base console in years, but if I remember
correctly   There are 2 versions of the load panel.  There's the base
panel.  It'll only have 2 radio buttons at the top for normal and clear.
When the SCSI IPL feature is active, the load panel has 2 more radio
buttons for scsi, scsi dump, and some other fields for wwpn and lun.  If
you don't have the second panel, I don't think SCSI IPL'ing a guest will
work.  I'm not a VM expert though.

Regards,

Ray Higgs
System z FCP Development
Bld. 706, B24
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666,  T/L 295-8666
rayhi...@us.ibm.com



Moeur Tim C 
Sent by: Linux on 390 Port 
03/18/2010 08:00 PM
Please respond to
Linux on 390 Port 


To
LINUX-390@vm.marist.edu
cc

Subject
Re: Boot from FCP on vintage hardware






I do not - I did discover an IBM presentation that included notes of
loading from SCSI from the HMC, but as you suggest, no such panels exist
on my old z-390.  I wasn't certain if that missing panel also meant that
zVM would also fail to IPL from SCSI.

Thanks both Mark and Ray.

Tim

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Raymond Higgs
Sent: Thursday, March 18, 2010 4:55 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Boot from FCP on vintage hardware

Tim,

SCSI IPL was an separate, orderable feature until z10.  If you open up
the
load panel on your z890 HMC/SE, do you see SCSI stuff?

Regards,

Ray Higgs
System z FCP Development
Bld. 706, B24
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666,  T/L 295-8666
rayhi...@us.ibm.com



Moeur Tim C 
Sent by: Linux on 390 Port 
03/18/2010 07:19 PM
Please respond to
Linux on 390 Port 


To
LINUX-390@vm.marist.edu
cc

Subject
Boot from FCP on vintage hardware






Hey list -

I've been hunting through IBM documents for this answer but so far no
gold.  Perhaps one of you will save me a lot of time.

I'm building zLinux images to use zfcp file systems as the /boot
directory.  This works well here at home on our Z10.  Our DR machine,
however, is an older z-890, code level unknown.  I'm able to mount the
zfcp devices on already running booted-from-3390-dasd images, but when I
attempt to ipl (this is as a VM guest) the boot-from-zfcp image it
instantly drops into a CP Program interrupt wait error.  There appears
to be no attempt (or messages) to resolve the wwpn and lun path
information that I've build into the image with mkinitrd.

I'm thinking that the z890 doesn't support a boot from zfcp.  Can anyone
confirm this?

Tim
tim.mo...@srpnet.com


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Boot from FCP on vintage hardware

[Moeur Tim C]

I do not - I did discover an IBM presentation that included notes of
loading from SCSI from the HMC, but as you suggest, no such panels exist
on my old z-390.  I wasn't certain if that missing panel also meant that
zVM would also fail to IPL from SCSI.

Thanks both Mark and Ray.   

Tim

-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
Raymond Higgs
Sent: Thursday, March 18, 2010 4:55 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Boot from FCP on vintage hardware

Tim,

SCSI IPL was an separate, orderable feature until z10.  If you open up
the
load panel on your z890 HMC/SE, do you see SCSI stuff?

Regards,

Ray Higgs
System z FCP Development
Bld. 706, B24
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666,  T/L 295-8666
rayhi...@us.ibm.com



Moeur Tim C 
Sent by: Linux on 390 Port 
03/18/2010 07:19 PM
Please respond to
Linux on 390 Port 


To
LINUX-390@vm.marist.edu
cc

Subject
Boot from FCP on vintage hardware






Hey list -

I've been hunting through IBM documents for this answer but so far no
gold.  Perhaps one of you will save me a lot of time.

I'm building zLinux images to use zfcp file systems as the /boot
directory.  This works well here at home on our Z10.  Our DR machine,
however, is an older z-890, code level unknown.  I'm able to mount the
zfcp devices on already running booted-from-3390-dasd images, but when I
attempt to ipl (this is as a VM guest) the boot-from-zfcp image it
instantly drops into a CP Program interrupt wait error.  There appears
to be no attempt (or messages) to resolve the wwpn and lun path
information that I've build into the image with mkinitrd.

I'm thinking that the z890 doesn't support a boot from zfcp.  Can anyone
confirm this?

Tim
tim.mo...@srpnet.com


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Boot from FCP on vintage hardware

[Raymond Higgs]

Tim,

SCSI IPL was an separate, orderable feature until z10.  If you open up the
load panel on your z890 HMC/SE, do you see SCSI stuff?

Regards,

Ray Higgs
System z FCP Development
Bld. 706, B24
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666,  T/L 295-8666
rayhi...@us.ibm.com



Moeur Tim C 
Sent by: Linux on 390 Port 
03/18/2010 07:19 PM
Please respond to
Linux on 390 Port 


To
LINUX-390@vm.marist.edu
cc

Subject
Boot from FCP on vintage hardware






Hey list -

I've been hunting through IBM documents for this answer but so far no
gold.  Perhaps one of you will save me a lot of time.

I'm building zLinux images to use zfcp file systems as the /boot
directory.  This works well here at home on our Z10.  Our DR machine,
however, is an older z-890, code level unknown.  I'm able to mount the
zfcp devices on already running booted-from-3390-dasd images, but when I
attempt to ipl (this is as a VM guest) the boot-from-zfcp image it
instantly drops into a CP Program interrupt wait error.  There appears
to be no attempt (or messages) to resolve the wwpn and lun path
information that I've build into the image with mkinitrd.

I'm thinking that the z890 doesn't support a boot from zfcp.  Can anyone
confirm this?

Tim
tim.mo...@srpnet.com


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Move root from LVM to Non-LVM File System

[Shane G]

Generally I'm with Christian on this one.
The procedure Mark linked is appropriate for (most) *sub*-directories of
the the root - not the entire root itself. The pseudo directories need
to be excluded, and things like logs, even in single user, are
problematic - that may not be an issue on test systems.
Unless the VGs and/or LVs are the same name I'd do it from another
system - else I might be inclined to figure out what needs to be
excluded and try a copy from the running system.
Has plenty of scope to get ugly.

Shane ...

On Fri, Mar 19th, 2010 at 7:30 AM, Mark Post  wrote:

> I don't this as being necessary at all.  Get another disk added to
> the Linux guest.  Format it, put a file system on it, use the
> document at http://linuxvm.org/Info/HOWOTs/movefs.html to populate
> it.  Update /etc/fstab on the new root file system, bind mount the
> rest of the file systems top of it, chroot to it, re-run mkinitrd and
> zipl, and you should be fine.  Iterate a biit if not.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Boot from FCP on vintage hardware

[Mark Post]

>>> On 3/18/2010 at 07:19 PM, Moeur Tim C  wrote: 
> I'm thinking that the z890 doesn't support a boot from zfcp.  Can anyone
> confirm this?

Not directly, but one way to check is to go to the HMC and see if it's a 
possibility there.  If not, you're out of luck.  It may be available by an HMC 
upgrade, but that would be something to ask your IBM hardware rep.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Boot from FCP on vintage hardware

[Moeur Tim C]

Hey list - 

I've been hunting through IBM documents for this answer but so far no
gold.  Perhaps one of you will save me a lot of time.  

I'm building zLinux images to use zfcp file systems as the /boot
directory.  This works well here at home on our Z10.  Our DR machine,
however, is an older z-890, code level unknown.  I'm able to mount the
zfcp devices on already running booted-from-3390-dasd images, but when I
attempt to ipl (this is as a VM guest) the boot-from-zfcp image it
instantly drops into a CP Program interrupt wait error.  There appears
to be no attempt (or messages) to resolve the wwpn and lun path
information that I've build into the image with mkinitrd.

I'm thinking that the z890 doesn't support a boot from zfcp.  Can anyone
confirm this?

Tim
tim.mo...@srpnet.com


--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Move root from LVM to Non-LVM File System

[Christian Paro]

I should add that you do the bind mount *before* you chroot. And that the
same directories should be excluded from what you try to copy across file
systems.

On Thu, Mar 18, 2010 at 6:45 PM, Christian Paro wrote:

> If you're going the chroot route, you'll want to bind-mount /dev /proc and
> /sys into the directory that you'll chroot into. This will make these
> in-memory-only filesystems accessible within your chrooted environment.
>
> See here:
>
> http://fermilinux.fnal.gov/documentation/tips/mount-bind-chroot
>
>
> On Thu, Mar 18, 2010 at 6:30 PM, Victor Echavarry Diaz <
> vechava...@evertecinc.com> wrote:
>
>> Mark:
>>
>> I try this
>>
>> L104M:/# mount /var
>> mount /var
>> mount: special device /dev/system/var does not exist
>> L104M:/#
>>
>> And this
>>
>> L104M:/# ls
>> ls
>> --one-file-system  bin   dismount  lib media  opt   roottmp  sys
>>  var
>> Oracle boot  etc   lib64   mntproc  sbin tmp
>> THIS_IS_THE_NEWdev   home  lost+found  netiq  root  srv  usr
>> L104M:/# mount /dev/system/var /var
>> mount /dev/system/var /var
>> L104M:/#
>>
>> And get the same error message
>>
>> Regards,
>>
>> Víctor Echavarry
>> System Programmer
>> Technology Systems & Operations Division
>> EVERTEC
>>
>>
>>
>> -Original Message-
>> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of
>> Mark Post
>> Sent: Thursday, March 18, 2010 6:17 PM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: Move root from LVM to Non-LVM File System
>>
>> >>> On 3/18/2010 at 05:53 PM, Victor Echavarry Diaz <
>> vechava...@evertecinc.com>
>> wrote:
>> > After chroot, I do mkinitrd and receive the following message
>> >
>> > /var/tmp is not a directory
>>
>> OK, then, after the chroot, but before the mkinitrd:
>> mount /var
>>
>> and try again.
>>
>>
>> Mark
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
>>
>>
>>
>> -
>> CONFIDENTIALITY NOTE: This email communication and its attachments
>> contain information that are proprietary and confidential to
>> EVERTEC, INC., its affiliates or its clients.  They may not be
>> disclosed, distributed, used, copied or modified in any way without
>> EVERTEC, Inc.’s authorization. If you are not the intended
>> recipient of this email, you are not an authorized person.  Please
>> delete it and notify the sender immediately. EVERTEC, Inc. and its
>> affiliates do not assume any liability for damages resulting from
>> emails that have been sent or altered without their consent.
>> Moreover, EVERTEC, Inc. has taken precautions to safeguard its
>> email communications, but cannot assure that such is the case and
>> disclaim any responsibility attributable thereto.
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Move root from LVM to Non-LVM File System

[Christian Paro]

If you're going the chroot route, you'll want to bind-mount /dev /proc and
/sys into the directory that you'll chroot into. This will make these
in-memory-only filesystems accessible within your chrooted environment.

See here:

http://fermilinux.fnal.gov/documentation/tips/mount-bind-chroot

On Thu, Mar 18, 2010 at 6:30 PM, Victor Echavarry Diaz <
vechava...@evertecinc.com> wrote:

> Mark:
>
> I try this
>
> L104M:/# mount /var
> mount /var
> mount: special device /dev/system/var does not exist
> L104M:/#
>
> And this
>
> L104M:/# ls
> ls
> --one-file-system  bin   dismount  lib media  opt   roottmp  sys
>  var
> Oracle boot  etc   lib64   mntproc  sbin tmp
> THIS_IS_THE_NEWdev   home  lost+found  netiq  root  srv  usr
> L104M:/# mount /dev/system/var /var
> mount /dev/system/var /var
> L104M:/#
>
> And get the same error message
>
> Regards,
>
> Víctor Echavarry
> System Programmer
> Technology Systems & Operations Division
> EVERTEC
>
>
>
> -Original Message-
> From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark
> Post
> Sent: Thursday, March 18, 2010 6:17 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Move root from LVM to Non-LVM File System
>
> >>> On 3/18/2010 at 05:53 PM, Victor Echavarry Diaz <
> vechava...@evertecinc.com>
> wrote:
> > After chroot, I do mkinitrd and receive the following message
> >
> > /var/tmp is not a directory
>
> OK, then, after the chroot, but before the mkinitrd:
> mount /var
>
> and try again.
>
>
> Mark
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>
>
>
> -
> CONFIDENTIALITY NOTE: This email communication and its attachments
> contain information that are proprietary and confidential to
> EVERTEC, INC., its affiliates or its clients.  They may not be
> disclosed, distributed, used, copied or modified in any way without
> EVERTEC, Inc.’s authorization. If you are not the intended
> recipient of this email, you are not an authorized person.  Please
> delete it and notify the sender immediately. EVERTEC, Inc. and its
> affiliates do not assume any liability for damages resulting from
> emails that have been sent or altered without their consent.
> Moreover, EVERTEC, Inc. has taken precautions to safeguard its
> email communications, but cannot assure that such is the case and
> disclaim any responsibility attributable thereto.
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Move root from LVM to Non-LVM File System

[Victor Echavarry Diaz]

Mark:

I try this

L104M:/# mount /var
mount /var 
mount: special device /dev/system/var does not exist   
L104M:/#   

And this 

L104M:/# ls 
ls  
--one-file-system  bin   dismount  lib media  opt   roottmp  sys  var   
Oracle boot  etc   lib64   mntproc  sbin tmp
THIS_IS_THE_NEWdev   home  lost+found  netiq  root  srv  usr
L104M:/# mount /dev/system/var /var 
mount /dev/system/var /var  
L104M:/#

And get the same error message

Regards,

Víctor Echavarry 
System Programmer
Technology Systems & Operations Division
EVERTEC



-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post
Sent: Thursday, March 18, 2010 6:17 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Move root from LVM to Non-LVM File System

>>> On 3/18/2010 at 05:53 PM, Victor Echavarry Diaz 
wrote: 
> After chroot, I do mkinitrd and receive the following message
> 
> /var/tmp is not a directory

OK, then, after the chroot, but before the mkinitrd:
mount /var

and try again.


Mark

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390



-
CONFIDENTIALITY NOTE: This email communication and its attachments
contain information that are proprietary and confidential to
EVERTEC, INC., its affiliates or its clients.  They may not be
disclosed, distributed, used, copied or modified in any way without
EVERTEC, Inc.’s authorization. If you are not the intended
recipient of this email, you are not an authorized person.  Please
delete it and notify the sender immediately. EVERTEC, Inc. and its
affiliates do not assume any liability for damages resulting from
emails that have been sent or altered without their consent.
Moreover, EVERTEC, Inc. has taken precautions to safeguard its
email communications, but cannot assure that such is the case and
disclaim any responsibility attributable thereto.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Move root from LVM to Non-LVM File System

[Mark Post]

>>> On 3/18/2010 at 05:53 PM, Victor Echavarry Diaz 
wrote: 
> After chroot, I do mkinitrd and receive the following message
> 
> /var/tmp is not a directory

OK, then, after the chroot, but before the mkinitrd:
mount /var

and try again.


Mark

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Move root from LVM to Non-LVM File System

[Victor Echavarry Diaz]

Mark:

After chroot, I do mkinitrd and receive the following message

/var/tmp is not a directory

Regards,

Víctor Echavarry 
System Programmer
Technology Systems & Operations Division
EVERTEC


-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post
Sent: Thursday, March 18, 2010 4:31 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Move root from LVM to Non-LVM File System

>>> On 3/18/2010 at 04:10 PM, Christian Paro  wrote: 
> It's not the simplest procedure ever, and I don't know of a tutorial the
> directly addresses what you're trying to do, but essentially you need to:
> 
> - Shut down and log off of the Linux whose root filesystem you wish to
> transfer.
> - Bring up the volume group containing that root filesystem on another Linux
> instance (so you can access the root file system in a quiesced state).
> - Mount the target partition on that same Linux instance.
> - Use `cp -a` to copy the filesystem contents.
> - Chroot into the new root partition.
> - Run `zipl`.
> - Exit chroot and unmount, offline, and detach the disks for the system
> whose root filesystem you were transferring.

I don't this as being necessary at all.  Get another disk added to the Linux 
guest.  Format it, put a file system on it, use the document at 
http://linuxvm.org/Info/HOWOTs/movefs.html to populate it.  Update /etc/fstab 
on the new root file system, bind mount the rest of the file systems top of it, 
chroot to it, re-run mkinitrd and zipl, and you should be fine.  Iterate a biit 
if not.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390



-
CONFIDENTIALITY NOTE: This email communication and its attachments
contain information that are proprietary and confidential to
EVERTEC, INC., its affiliates or its clients.  They may not be
disclosed, distributed, used, copied or modified in any way without
EVERTEC, Inc.’s authorization. If you are not the intended
recipient of this email, you are not an authorized person.  Please
delete it and notify the sender immediately. EVERTEC, Inc. and its
affiliates do not assume any liability for damages resulting from
emails that have been sent or altered without their consent.
Moreover, EVERTEC, Inc. has taken precautions to safeguard its
email communications, but cannot assure that such is the case and
disclaim any responsibility attributable thereto.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: SLES11 - error when trying to compile snipl

[Mark Post]

>>> On 3/18/2010 at 04:31 PM, Bernie Wu  wrote: 
> # patch < patchfile
> patching file Makefile
> patch:  malformed patch at line 22: $(INCDIR) -I$(STONITHINCDIR)
> 
> Am I missing something ?

Not exactly,  The listserver wrapped a couple of lines so that they looked like 
four lines instead of two.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: SLES11 - error when trying to compile snipl

[Bernie Wu]

Hi Ursula,
A couple of questions:
1.  After downloading the 3 tarballs from linux-ha.org, I'm not sure where 
to un-tar them to .  Currently, I put them into /tmp, but I'm sure "make" 
doesn't know about /tmp.
2.  I cut and pasted your email and put it into a file called patchfile and 
tried to apply it and this is what I got:

# cd /tmp/snipl-0.2.1.7
# patch < patchfile
patching file Makefile
patch:  malformed patch at line 22: $(INCDIR) -I$(STONITHINCDIR)

Am I missing something ?

The information contained in this e-mail message is intended only for the 
personal and confidential use of the recipient(s) named above. This message may 
be an attorney-client communication and/or work product and as such is 
privileged and confidential. If the reader of this message is not the intended 
recipient or an agent responsible for delivering it to the intended recipient, 
you are hereby notified that you have received this document in error and that 
any review, dissemination, distribution, or copying of this message is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by e-mail, and delete the original message.

Re: Move root from LVM to Non-LVM File System

[Mark Post]

>>> On 3/18/2010 at 04:10 PM, Christian Paro  wrote: 
> It's not the simplest procedure ever, and I don't know of a tutorial the
> directly addresses what you're trying to do, but essentially you need to:
> 
> - Shut down and log off of the Linux whose root filesystem you wish to
> transfer.
> - Bring up the volume group containing that root filesystem on another Linux
> instance (so you can access the root file system in a quiesced state).
> - Mount the target partition on that same Linux instance.
> - Use `cp -a` to copy the filesystem contents.
> - Chroot into the new root partition.
> - Run `zipl`.
> - Exit chroot and unmount, offline, and detach the disks for the system
> whose root filesystem you were transferring.

I don't this as being necessary at all.  Get another disk added to the Linux 
guest.  Format it, put a file system on it, use the document at 
http://linuxvm.org/Info/HOWOTs/movefs.html to populate it.  Update /etc/fstab 
on the new root file system, bind mount the rest of the file systems top of it, 
chroot to it, re-run mkinitrd and zipl, and you should be fine.  Iterate a biit 
if not.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Pure-FTP & uploadd-script

[Frank M. Ramaekers]

I have been unsuccessful in porting Pure-FTPD over to zSeries.  It
compiles clean (with -with-uploadscript), but never creates the
/var/run/pure-ftpd.upload.pipe.  In fact, from the strace, it never
executes this portion of the code.  I'd like to port a server, that's on
an Intel platform over to the zSeries.  The reason I prefer Pure-FTPD is
the upload-script capability.

 

I've looked at the supplied vsftpd, but it doesn't appear to have this
capability.

 

Any help or suggestions would be appreciated,

 

 Frank M. Ramaekers Jr.

 

Systems Programmer

MCP, MCP+I, MCSE & RHCE

American Income Life Insurance Co.

Phone: (254)761-6649

1200 Wooded Acres Dr.

Fax: (254)741-5777

Waco, Texas  76701

 

 


_
This message contains information which is privileged and confidential and is 
solely for the use of the
intended recipient. If you are not the intended recipient, be aware that any 
review, disclosure,
copying, distribution, or use of the contents of this message is strictly 
prohibited. If you have
received this in error, please destroy it immediately and notify us at 
privacy...@ailife.com.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Move root from LVM to Non-LVM File System

[Christian Paro]

It's not the simplest procedure ever, and I don't know of a tutorial the
directly addresses what you're trying to do, but essentially you need to:

- Shut down and log off of the Linux whose root filesystem you wish to
transfer.
- Bring up the volume group containing that root filesystem on another Linux
instance (so you can access the root file system in a quiesced state).
- Mount the target partition on that same Linux instance.
- Use `cp -a` to copy the filesystem contents.
- Chroot into the new root partition.
- Run `zipl`.
- Exit chroot and unmount, offline, and detach the disks for the system
whose root filesystem you were transferring.

The tricky part in all this is getting the LVM volume group containing your
original root file system to work on another guest. To do this, you need all
of the underlying physical disks linked and set online on the second Linux
that you're using to do the transfer.

You also need to run `vgcfgbackup` on the first Linux prior to attempting
the transfer to get a current configuration file for your LVM setup. This
file can then be copied over to the second Linux so you can issue
`vgcfgrestore` against it and access the LVM volume group(s) from the first
Linux.

This article has some more detail on the LVM volume group backup/restore
process (along with instructions on RAID recovery which, while irrelevant
for the task at hand, might be useful on other occasions). Note that there
are also a few additional commands (like `vgchange` needed to online/offline
the volume group before you can mount it or safely detach the underlying
disks).

http://www.linuxjournal.com/article/8874

The trick here is that you're "restoring" the volume group to another Linux
instance so you can do a clean copy rather than taking your chances copying
an active root filesystem.

On Thu, Mar 18, 2010 at 3:49 PM, Victor Echavarry Diaz <
vechava...@evertecinc.com> wrote:

> I'm a Linux newbie. Our test servers are all LVM except /boot.  I want to
> move the LVM / file system only to a non-LVM / file system. Is there a
> tutorial to do that?
>
> Regards,
>
> Víctor Echavarry
> System Programmer
> Technology Systems & Operations Division
> EVERTEC
>
>
>
>
>
>
>
> -
> CONFIDENTIALITY NOTE: This email communication and its attachments
> contain information that are proprietary and confidential to
> EVERTEC, INC., its affiliates or its clients.  They may not be
> disclosed, distributed, used, copied or modified in any way without
> EVERTEC, Inc.’s authorization. If you are not the intended
> recipient of this email, you are not an authorized person.  Please
> delete it and notify the sender immediately. EVERTEC, Inc. and its
> affiliates do not assume any liability for damages resulting from
> emails that have been sent or altered without their consent.
> Moreover, EVERTEC, Inc. has taken precautions to safeguard its
> email communications, but cannot assure that such is the case and
> disclaim any responsibility attributable thereto.
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Move root from LVM to Non-LVM File System

[Victor Echavarry Diaz]

I'm a Linux newbie. Our test servers are all LVM except /boot.  I want to move 
the LVM / file system only to a non-LVM / file system. Is there a tutorial to 
do that?

Regards,

Víctor Echavarry
System Programmer
Technology Systems & Operations Division
EVERTEC







-
CONFIDENTIALITY NOTE: This email communication and its attachments
contain information that are proprietary and confidential to
EVERTEC, INC., its affiliates or its clients.  They may not be
disclosed, distributed, used, copied or modified in any way without
EVERTEC, Inc.’s authorization. If you are not the intended
recipient of this email, you are not an authorized person.  Please
delete it and notify the sender immediately. EVERTEC, Inc. and its
affiliates do not assume any liability for damages resulting from
emails that have been sent or altered without their consent.
Moreover, EVERTEC, Inc. has taken precautions to safeguard its
email communications, but cannot assure that such is the case and
disclaim any responsibility attributable thereto.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: SLES11 - error when trying to compile snipl

[Ursula Braun]

On Thu, 2010-03-18 at 12:02 -0300, Frank Pani wrote:
> Hi - we have the very same issue.
>
>
> We are interested in stonith/heartbeat and have the following Heartbeat,
> Cluster Glue, and Resource Agents.  We have download v3.0.2 for heartbeat.
>
>
> For us, we are using RHEL v5.3 and because these components are not
> available in binary form from the distributor we have compiled these
> components ourselves with success.
>
>
> Ursula, any direction on this would be grateful.  Seems that simply a file
> is just missing in the latest build.  Thanks.
>
>
> - Frank Pani

Frank,

looks like the snipl stonith part requires adaptions to the latest
download files on linux-ha.org.

After downloading these files to my system, I could compile snipl after
applying this patch to the snipl Makefile (see the new include directory
HEARTBEATINCDIR):


---
 Makefile |3 ++-
 1 files changed, 2 insertions(+), 1 deletion(-)

Index: src/Makefile
===
--- src.orig/Makefile
+++ src/Makefile
@@ -26,6 +26,7 @@ LIBDIR  = ${PREFIX}/${LIB_STRING
 STONITHLIBDIR  = ${PREFIX}/${LIB_STRING}/stonith
 INCDIR  = ${PREFIX}/include
 STONITHINCDIR   = ${INCDIR}/stonith
+HEARTBEATINCDIR = ${INCDIR}/heartbeat
 MANDIR  = ${PREFIX}/share/man
 LIB_LPAR=
 LIB_VM  =
@@ -38,7 +39,7 @@ OWNER   = $(shell id -un)
 GROUP   = $(shell id -gn)

 GLIB2_HEADERS   = `pkg-config --cflags glib-2.0`
-CFLAGS  += -DUNIX=1 -DST_TEXTDOMAIN='"stonith"' -g -O2 -Wall -I. -I
$(INCDIR) -I$(STONITHINCDIR)
+CFLAGS  += -DUNIX=1 -DST_TEXTDOMAIN='"stonith"' -g -O2 -Wall -I. -I
$(INCDIR) -I$(STONITHINCDIR) -I$(HEARTBEATINCDIR)

 all: all_config all_sniplapi all_vmsmapi all_snipl all_stonith
 install: install_subdirs install_config install_sniplapi
install_vmsmapi install_snipl install_stonith

Regards, Ursula Braun

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: DS8300, NPIV, setup...

[Brian France]

Well I got it down to JUST the following commands - What I found is
something somewhere changed, either us now being sles10, not sles9,
and/or going from SVC to native along with no NPIV and now NPIV. Dunno
and at this point, I got it working smoothly so I'm happy.

AFTER the lun is expanded -

 1. Reboot the image OR Remove the devices COMPLETELY from zFCP

  I've found that I personally like the ( sorry to say this )
microsloth touch here and just reboot otherwise the next step becomes
your first.

 2. umount thefilesystem

 3. e2fsck -f /dev/mapper/lunofchoice

 4. resize2fs /dev/mapper/lunofchoice

 5. mount thefilesystem



Robert J Brenneman wrote:

oops - re lun expansion:

I've done it, but I've always had to drive all the devices completely
out of the SCSI stack and re add them to get them to rescan and find
the extra space. I don't think Linux normally supports lun expansion
gracefully.

I'm sure someone will speak up to correct me if I'm mistaken, or just
don't know the right magic.



--
Jay Brenneman

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390





--

--

Brian W. France
Systems Administrator (Mainframe)
Pennsylvania State University
Administrative Information Services - Infrastructure/SYSARC
Rm 25 Shields Bldg., University Park, Pa. 16802
814-863-4739
b...@psu.edu 

"To make an apple pie from scratch, you must first invent the universe."

Carl Sagan

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: SLES11 - error when trying to compile snipl

[Bernie Wu]

Thanks Ursula for your response.
The truth is, we really don't know what we need at this point in time.
We are trying to setup a test HA environment using the SLES11-HAE package.  I 
have also downloaded and installed all the HA patches.
The documentation says we need stonith which needs snipl and snipl is not in 
the iso(s) I downloaded, but I find it at IBM's developerworks. So I download 
the tarball and try to compile it.

Our current setup:
zVM 5.4
SLES11 (2.6.27.45-0.1)

# rpm -qa | egrep "heart|pace|ais|clvm" | sort
heartbeat-common-3.0.0-0.6.5
heartbeat-ldirectord-3.0.0-0.2.8
heartbeat-resources-3.0.0-0.2.8
libheartbeat-devel-3.0.0-0.6.5
libheartbeat2-3.0.0-0.6.5
libopenais-devel-0.80.3-26.8.1
libopenais2-0.80.3-26.8.1
libpacemaker-devel-1.0.5-0.5.6
libpacemaker3-1.0.5-0.5.6
lvm2-clvm-2.02.39-18.11.17
openais-0.80.3-26.8.1
pacemaker-1.0.5-0.5.6
pacemaker-pygui-1.99.2-0.2.6
perl-XML-NamespaceSupport-1.09-1.22


I will get the 3 tarballs from linux-ha.org and see what's in there.

Bernie Wu

The information contained in this e-mail message is intended only for the 
personal and confidential use of the recipient(s) named above. This message may 
be an attorney-client communication and/or work product and as such is 
privileged and confidential. If the reader of this message is not the intended 
recipient or an agent responsible for delivering it to the intended recipient, 
you are hereby notified that you have received this document in error and that 
any review, dissemination, distribution, or copying of this message is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by e-mail, and delete the original message.

Re: SLES11 - error when trying to compile snipl

[Frank Pani]

Hi - we have the very same issue.


We are interested in stonith/heartbeat and have the following Heartbeat,
Cluster Glue, and Resource Agents.  We have download v3.0.2 for heartbeat.


For us, we are using RHEL v5.3 and because these components are not
available in binary form from the distributor we have compiled these
components ourselves with success.


Ursula, any direction on this would be grateful.  Seems that simply a file
is just missing in the latest build.  Thanks.


- Frank Pani



  From:   Ursula Braun 

  To: LINUX-390@vm.marist.edu

  Date:   03/18/2010 11:37 AM

  Subject:Re: SLES11 - error when trying to compile snipl






On Thu, 2010-03-18 at 08:04 -0400, Bernie Wu wrote:
> Mark,
> I picked up snipl-0.2.1.6.tar.gz from IBM's developerworks.
> The original make error :
> # make
> 
> ***  WARNING ***
> ***  ***
> *** vmsmapi cannot be built without dmsvsma.x***
> 
> gcc -DUNIX=1 -DST_TEXTDOMAIN='"stonith"' -g -O2 -Wall -I. -I/usr/include
> -I/usr/include/stonith -o snipl -L. -L/usr/lib64 -lnsl -ldl  -lsniplapi
-lhwmcaapi
> -lconfig snipl.o prepare.o
> /bin/sh libtool --mode=compile gcc \
> -DUNIX=1 -DST_TEXTDOMAIN='"stonith"' -g -O2 -Wall -I.
-I/usr/include
> -I/usr/include/stonith -DLPAR_INCLUDED=1  `pkg-config --cflags glib-2.0`
\
> -c lic_vps.c -o lic_vps.lo
> libtool: compile:  gcc -DUNIX=1 -DST_TEXTDOMAIN=\"stonith\" -g -O2 -Wall
-I.
> -I/usr/include -I/usr/include/stonith -DLPAR_INCLUDED=1
-I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -c lic_vps.c  -fPIC -DPIC
-o .libs/lic_vps.o
> In file included from /usr/include/stonith/stonith.h:47,
>  from ./snipl_stonith_plugin.h:31,
>  from lic_vps.c:17:
> /usr/include/pils/plugin.h:24:27: error: glue_config.h: No such file or
directory
> make: *** [lic_vps.lo] Error 1

Bernie,

lic_vps is the snipl plugin for stonith/heartbeat. If you are just
interested in snipl command line functionality, you can remove this part
of the Makefile.

If you are interested in stonith/heartbeat, there are 3 downloadable tar
files on linux-ha.org: Heartbeat, Cluster Glue, and Resource Agents. Are
all of them available on your system? Which versions?

Regards, Ursula Braun
IBM Germany
Linux on System z development

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: SLES11 - error when trying to compile snipl

[Ursula Braun]

On Thu, 2010-03-18 at 08:04 -0400, Bernie Wu wrote:
> Mark,
> I picked up snipl-0.2.1.6.tar.gz from IBM's developerworks.
> The original make error :
> # make
> 
> ***  WARNING ***
> ***  ***
> *** vmsmapi cannot be built without dmsvsma.x***
> 
> gcc -DUNIX=1 -DST_TEXTDOMAIN='"stonith"' -g -O2 -Wall -I. -I/usr/include
> -I/usr/include/stonith -o snipl -L. -L/usr/lib64 -lnsl -ldl  -lsniplapi 
> -lhwmcaapi
> -lconfig snipl.o prepare.o
> /bin/sh libtool --mode=compile gcc \
> -DUNIX=1 -DST_TEXTDOMAIN='"stonith"' -g -O2 -Wall -I. -I/usr/include
> -I/usr/include/stonith -DLPAR_INCLUDED=1  `pkg-config --cflags glib-2.0` \
> -c lic_vps.c -o lic_vps.lo
> libtool: compile:  gcc -DUNIX=1 -DST_TEXTDOMAIN=\"stonith\" -g -O2 -Wall -I.
> -I/usr/include -I/usr/include/stonith -DLPAR_INCLUDED=1 
> -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -c lic_vps.c  -fPIC -DPIC -o .libs/lic_vps.o
> In file included from /usr/include/stonith/stonith.h:47,
>  from ./snipl_stonith_plugin.h:31,
>  from lic_vps.c:17:
> /usr/include/pils/plugin.h:24:27: error: glue_config.h: No such file or 
> directory
> make: *** [lic_vps.lo] Error 1

Bernie,

lic_vps is the snipl plugin for stonith/heartbeat. If you are just
interested in snipl command line functionality, you can remove this part
of the Makefile.

If you are interested in stonith/heartbeat, there are 3 downloadable tar
files on linux-ha.org: Heartbeat, Cluster Glue, and Resource Agents. Are
all of them available on your system? Which versions?

Regards, Ursula Braun
IBM Germany
Linux on System z development

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Question from a UNIX newbie.

[John Campbell]

I kind of wonder whether an open_via( path_string, file_name, mode)
kind of routine would be worth sneaking into the stdio (libc.a)
library making fopen_via() a slam-dunk.  I don't see it becoming a
syscall since the shell doesn't do that, but this would make the use
of a path variable overt rather than covert.

The key, of course, is that the shell, Perl, Java (and likely a couple
of others) aren't using syscalls to do these opens, they are using
their own code to handle the path-scanning.

Path management is, to my eye, almost as frightening as the early
years of "DLL Hell" as well as Java's "Write Once, Debug
Everywhere"...  and, for the latter, I recall one app I supported that
had to have THREE DIFFERENT versions of JAVA running at one time.

This is one of those trade-offs, y'know?

But, in any case, you DO NOT want open() or fopen() walking a path
tree to get at a file.

As it is, you want to manage this carefully because open() time
(performance!) is impacted, linearly, by the size of a directory,
since a search is linear, just to find the inode number.  Add pathing
to that and open() times won't be predictable.

Having a "standard API" layer to support this for Perl, Shell, Java,
etc, might not be quite so terrible.

(laughs)

I once suggested, in comp.lang.c, that "long int" and "long long int"
needed a little bit of help so I suggested that a 1024bit integer be
considered a "ludicrous long int".

(smirks)

- soup

On Thu, Mar 18, 2010 at 5:25 AM, Roger Evans  wrote:
> And the biggest reason: there are maybe millions of programs and scripts
> that are written to assume that fopen DOESN'T search a path variable,
> and might break if the behavior were changed.  Users are also
> 'programmed' to assume that commands will look where they're told to
> look and nowhere else. It's bad enough having to  'reprogram' when
> switching from an MSDOS command line (which has '.' implicitly in its
> PATH) and linux, which doesn't.
>
> You could even be able to make a case for dropping this behavior on the
> part of exec and ld, and forcing the user/programmer to specify where
> the files are.   But that would break a lot of things, too.
>
> Roger
>
> On Thu, 2010-03-18 at 09:36 +0100, Rob van der Heij wrote:
>> On Thu, Mar 18, 2010 at 5:39 AM, William D Carroll
>>  wrote:
>>
>> > Biggest reason I can think against it (just devil's advocate) is 
>> > performance
>> > if you had a search path that fopen/fdopen used then for every call of 
>> > fopen/fdopen
>> > they would search the path (or could potentially search they path)
>> > this could cause excessive overhead on the lpar.
>> > think of the extra IO that would be occurring performing searches
>>
>> "When other things equal, performance rules. Otherwise often too" :-)
>>
>> I think you're right that the cost of searching other directories is
>> is to be avoided. And just like with $PATH there is a trojan horse
>> around the corner...
>>
>> The idea smells like the CMS "file mode extension" where you want to
>> fake things and allow the program to think the file is somewhere else.
>> With CMS mini disks you have no other options but copying the files
>> when the program was not prepared to look on other file modes. The
>> mechanisms in Unix are a bit different. I don't think I've seen a
>> program that took a file name as an argument but could not handle a
>> path. But if it really happens you do tricks with links.
>>
>> Really just command line. I see an analogy with "address command"
>> religion in CMS. When you write a program in Linux you should not rely
>> on the path but state which program you run and what files you use. I
>> would not like to see "sshd" pick up a different config file because I
>> installed some Java stuff that injected some directories (at the
>> start) of my $DATAPATH environment variable.
>>
>> Rob
>>
>> --
>> For LINUX-390 subscribe / signoff / archive access instructions,
>> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
>> visit
>> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> Roger Evans, http://www.autodata.no tel: +47 23 17 20 46 GSM: 93 25 92
> 36
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
>



-- 
John R. Campbell Speaker to Machines  souperb at gmail dot com
MacOS X proved it was easier to make Unix user-friendly than to fix Windows

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: SLES11 - error when trying to compile snipl

[Bernie Wu]

Mark,
I picked up snipl-0.2.1.6.tar.gz from IBM's developerworks.
The original make error :
# make

***  WARNING ***
***  ***
*** vmsmapi cannot be built without dmsvsma.x***

gcc -DUNIX=1 -DST_TEXTDOMAIN='"stonith"' -g -O2 -Wall -I. -I/usr/include
-I/usr/include/stonith -o snipl -L. -L/usr/lib64 -lnsl -ldl  -lsniplapi 
-lhwmcaapi
-lconfig snipl.o prepare.o
/bin/sh libtool --mode=compile gcc \
-DUNIX=1 -DST_TEXTDOMAIN='"stonith"' -g -O2 -Wall -I. -I/usr/include
-I/usr/include/stonith -DLPAR_INCLUDED=1  `pkg-config --cflags glib-2.0` \
-c lic_vps.c -o lic_vps.lo
libtool: compile:  gcc -DUNIX=1 -DST_TEXTDOMAIN=\"stonith\" -g -O2 -Wall -I.
-I/usr/include -I/usr/include/stonith -DLPAR_INCLUDED=1 -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -c lic_vps.c  -fPIC -DPIC -o .libs/lic_vps.o
In file included from /usr/include/stonith/stonith.h:47,
 from ./snipl_stonith_plugin.h:31,
 from lic_vps.c:17:
/usr/include/pils/plugin.h:24:27: error: glue_config.h: No such file or 
directory
make: *** [lic_vps.lo] Error 1


-Original Message-
From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mark Post
Sent: Wednesday, March 17, 2010 6:33 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SLES11 - error when trying to compile snipl

I don't see any reference to glue_config.h in the source code for snIPL.  What 
version of the source code do you have, and where did you get it from?


Mark Post

>>> Bernie Wu  03/17/10 11:04 AM >>>
Hi List,
Can anyone tell me where I can get my hands on libglue-devel  so that I can 
compile snIPL.
My compile error is : glue_config.h: No such file or directory.

TIA
Bernie Wu

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

The information contained in this e-mail message is intended only for the 
personal and confidential use of the recipient(s) named above. This message may 
be an attorney-client communication and/or work product and as such is 
privileged and confidential. If the reader of this message is not the intended 
recipient or an agent responsible for delivering it to the intended recipient, 
you are hereby notified that you have received this document in error and that 
any review, dissemination, distribution, or copying of this message is strictly 
prohibited. If you have received this communication in error, please notify us 
immediately by e-mail, and delete the original message.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Question from a UNIX newbie.

[Roger Evans]

And the biggest reason: there are maybe millions of programs and scripts
that are written to assume that fopen DOESN'T search a path variable,
and might break if the behavior were changed.  Users are also
'programmed' to assume that commands will look where they're told to
look and nowhere else. It's bad enough having to  'reprogram' when
switching from an MSDOS command line (which has '.' implicitly in its
PATH) and linux, which doesn't.

You could even be able to make a case for dropping this behavior on the
part of exec and ld, and forcing the user/programmer to specify where
the files are.   But that would break a lot of things, too.

Roger

On Thu, 2010-03-18 at 09:36 +0100, Rob van der Heij wrote:
> On Thu, Mar 18, 2010 at 5:39 AM, William D Carroll
>  wrote:
>
> > Biggest reason I can think against it (just devil's advocate) is performance
> > if you had a search path that fopen/fdopen used then for every call of 
> > fopen/fdopen
> > they would search the path (or could potentially search they path)
> > this could cause excessive overhead on the lpar.
> > think of the extra IO that would be occurring performing searches
>
> "When other things equal, performance rules. Otherwise often too" :-)
>
> I think you're right that the cost of searching other directories is
> is to be avoided. And just like with $PATH there is a trojan horse
> around the corner...
>
> The idea smells like the CMS "file mode extension" where you want to
> fake things and allow the program to think the file is somewhere else.
> With CMS mini disks you have no other options but copying the files
> when the program was not prepared to look on other file modes. The
> mechanisms in Unix are a bit different. I don't think I've seen a
> program that took a file name as an argument but could not handle a
> path. But if it really happens you do tricks with links.
>
> Really just command line. I see an analogy with "address command"
> religion in CMS. When you write a program in Linux you should not rely
> on the path but state which program you run and what files you use. I
> would not like to see "sshd" pick up a different config file because I
> installed some Java stuff that injected some directories (at the
> start) of my $DATAPATH environment variable.
>
> Rob
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
--
Roger Evans, http://www.autodata.no tel: +47 23 17 20 46 GSM: 93 25 92
36

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Re: Question from a UNIX newbie.

[Rob van der Heij]

On Thu, Mar 18, 2010 at 5:39 AM, William D Carroll
 wrote:

> Biggest reason I can think against it (just devil's advocate) is performance
> if you had a search path that fopen/fdopen used then for every call of 
> fopen/fdopen
> they would search the path (or could potentially search they path)
> this could cause excessive overhead on the lpar.
> think of the extra IO that would be occurring performing searches

"When other things equal, performance rules. Otherwise often too" :-)

I think you're right that the cost of searching other directories is
is to be avoided. And just like with $PATH there is a trojan horse
around the corner...

The idea smells like the CMS "file mode extension" where you want to
fake things and allow the program to think the file is somewhere else.
With CMS mini disks you have no other options but copying the files
when the program was not prepared to look on other file modes. The
mechanisms in Unix are a bit different. I don't think I've seen a
program that took a file name as an argument but could not handle a
path. But if it really happens you do tricks with links.

Really just command line. I see an analogy with "address command"
religion in CMS. When you write a program in Linux you should not rely
on the path but state which program you run and what files you use. I
would not like to see "sshd" pick up a different config file because I
installed some Java stuff that injected some directories (at the
start) of my $DATAPATH environment variable.

Rob

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390