Re: Boot from FCP on vintage hardware
Maybe you have to specifically enter a boot option number with the SET LOADDEV command? This was sometimes needed to make the selection for the boot menu, ex: Ready; T=0.01/0.01 16:15:29 set loaddev bootprog 2 Ready; T=0.01/0.01 16:16:40 q loaddev PORTNAME 50050763 00C1AFC4LUN 5734 BOOTPROG 2 BR_LBA This would try to boot what would have been option 2 on the boot menu. - Mark Ver office: Building 710 / Room 2-RF-10 phone: (845) 435-7794 [tie 8 295-7794] -- 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
If you have access to the SLES-11 HAE and SLES-11 SDK DVDs, you can just install pacemaker and openais material (from High Availability pattern via yast) libheartbeat-devel (from the HAE DVD manually) glib2-devel (from the SDK) hwmcaapi-devel (from IBM) hwmcaapi(from IBM) dmsvsma.x (from a z/VM system) Along with the normal build tools (libnet, libtool, autoconf, etc) these should let you compile all components of the snipl source. If you're not happy with openais / pacemaker as is and really want to build heartbeat from scratch ... The glue_config.h is from the Reusable-Cluster-Components-glue, ex: LAC0031:~/Reusable-Cluster-Components-glue-1.0.3 # find | grep glue_config.h ./include/glue_config.h ./include/glue_config.h.in LAC0031:~/Reusable-Cluster-Components-glue-1.0.3 # LAC0031:~/Reusable-Cluster-Components-glue-1.0.3 # cd include LAC0031:~/Reusable-Cluster-Components-glue-1.0.3/include # grep i_HEADERS Makefile DIST_COMMON = $(i_HEADERS) $(noinst_HEADERS) $(srcdir)/Makefile.am \ HEADERS = $(i_HEADERS) $(noinst_HEADERS) i_HEADERS = compress.h glue_config.h ha_msg.h install-iHEADERS: $(i_HEADERS) @list='$(i_HEADERS)'; for p in $$list; do \ @list='$(i_HEADERS)'; for p in $$list; do \ LAC0031:~/Reusable-Cluster-Components-glue-1.0.3/include # And to get the correct Makefile ... need some magic fairy dust ... On my system, just to get /usr/include/heartbeat/glue_config.h, I think it required at least these packages: e2fsprogs-devel-1.41.1-13.9 libuuid-devel-1.41.1-13.9 libext2fs-devel-1.41.1-13.9 libcom_err-devel-1.41.1-13.9 libblkid-devel-1.41.1-13.9 libxml2-devel-2.7.1-10.8 libbz2-devel-1.0.5-34.246 readline-devel-5.2-147.3 glib2-devel-2.18.2-7.6 zlib-devel-1.2.3-106.34 And following the pacemaker build info down to the letter. http://clusterlabs.org/wiki/Install#From_Source - Mark Ver office: Building 710 / Room 2-RF-10 phone: (845) 435-7794 [tie 8 295-7794] -- 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
linux-390@vm.marist.edu
http://www.zdnet.com.au/allianz-cio-lost-hair-over-linux-upgrade-339301891.h tm Allianz Australia Insurance chief information officer (CIO) Steve Cole said yesterday he had done the equivalent of losing hair while undertaking an upgrade that saw the company move from multiple Wintel servers to a Linux mainframe. The insurance company had over one weekend moved from the Wintel environment of 60 plus servers over two separate datacentres onto a mainframe running Z Linux. : : "[I'm] very pleased to say it was a highly successful roll in terms of establishing a foundation from an infrastructure perspective that's really reduced complexity and we've been able to really establish a level of robustness around what we couldn't have in the previous environment," he said. "It took a huge amount of cost out of our bottom line. So that was a real learning experience in multiple ways as well. -- 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
Thanks for your help. It works. 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 Shane G Sent: Thursday, March 18, 2010 7:53 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Move root from LVM to Non-LVM File System 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 - 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
On Thu, 2010-03-18 at 16:31 -0400, Bernie Wu wrote: > 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. Bernie, it should not matter where you un-tar the downloaded tarballs. But they use different configuration commands. For Heartbeat you start with "ConfigureMe configure", for the others with "autogen.sh" (followed by "configure", "make", "make install"). I am sending you the snipl Makefile patch in a separate file to avoid listserver wrapping. 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
