CAVMEN Meeting on Thursday, June 23, 2005 - Agenda Update - Session added
A 3:30pm session has been added. Please see the agenda below. -- Meeting Location: This quarter's meeting will be held at the Hewitt Associates 'East Campus' located at 100 Half Day Road, in Lincolnshire, IL. We will meet in Conference Room 100-M3, just off the Cafeteria. If you have not attended a meeting at this location before, or you are not familiar with the area, http://cavmen.home.comcast.net/hewittb99.htmlClick here for additional information on directions, maps, lodging and dining. -- Attendance: Our host site has requested a count of expected attendees by the Monday before the meeting, so that they can plan appropriately for refreshments, etc. If you are planning to attend, PLEASE send an E-Mail by that date to mailto:[EMAIL PROTECTED][EMAIL PROTECTED] with a subject line of Meeting Attendance. This is meant to be a facilities planning aid and should not be interpreted as a registration requirement. If you suddenly become available at the last minute, please feel free to attend even if you have not responded. Thank you in advance for your cooperation in this matter. -- Final Meeting Agenda: 9:00 AM Bacula, No Silver Data Cartridges, Please... In previous sessions, I've talked about Linux backups with Amanda, and integrating Amanda and HSM processing. Bacula is a rapidly developing open-source backup and recovery utility that is considerably more sophisticated than Amanda, bordering on being competitive with the commercial backup utilities, and has recently received a number of mainframe-specific enhancements that make it very attractive as a backup solution for Linux guests on VM and other systems throughout the enterprise. In this session, I'll give an overview of Bacula, the integration code SNA has contributed to add tape library support and ANSI label support, and how to set up a Bacula server using the tools provided. The speaker will be David Boyes of Sine Nomine Associates. 10:30 AMCoffee Break 11:00 AMLow-Cost File Level Backup for Linux on the Mainframe: A Backup Appliance for Linux on zSeries (new updates!) This session describes a method for doing file and DR backups for Linux systems to VM and/or z/OS-controlled tape drives without connecting tape drives directly to Linux. The session describes Linux tools, z/OS and VM configuration, interaction with SMS on both platforms, and includes a configuration that can back up virtual machines and discrete machines using the existing mainframe tape resources. . The speaker will be David Boyes of Sine Nomine Associates. 12:30 PMLunch Break 1:30 PM Administration and Vendor Announcements 2:00 PM Linux appliance to cross-communicate with z/OS or other Operating Systems Bringing TCPNJE To The Rest of the World: Our Latest Research Widget NJE services are deeply embedded in almost all the IBM operating systems, and there are many useful services that can be provided message logging, unattended file transfer, printing to open-systems printers... if only there were a way to allow open systems to play in the NJE world! Also, the z/OS folks are still stuck in the Dark Ages requiring SNA communications links and VM/VTAM just to play in the NJE world. We've been working on a Linux-based NJE appliance to demonstrate some of the techniques required to build focused Linux systems that augment traditional mainframe applications, and a full-scale NJE implementation for open systems (including Linux Intel, Windows and Palm client/servers!) fell out of the solution to the problem. I'll talk about some of the requirements for constructing a NJE appliance, the addition of a CTC driver to Linux on zSeries, outline some of the interesting system management and automation that is possible once NJE connectivity is present, and hopefully (network connection permitting) demonstrate a direct connection between RSCS and a Intel Linux system to show off our new toy. The speaker will be David Boyes of Sine Nomine Associates. 3:15 PM Coffee Break 3:30 PM Managing Performance in z/VM Mac Holloway is a development manager for IBM Tivoli. He will be presenting the Tivoli history and roadmap for managing performance in the z/VM environment. This will include both the long-time IBM and Candle products. The future will be based on the OMEGAMON XE/DE infrastructure and address the z/VM and Linux guest performance data correlation. The OMEGAMON XE/DE infrastructure provides an extensible framework for identifying and debugging performance problems across platforms and applications. The speaker will be Mac Holloway of IBM/Tivoli. 4:45 PM Free-for-All Members will attempt to answer any reasonable VM or hardware related questions. If you are having a problem and want to find out if others are experiencing it, or you are installing new hardware or software and want to find out what types of problems others have experienced, here is the
Re: Fwd: SLES9 losing network connectivity
Do you have QIOASSIST on ? After setting NOQIOASSIST on the OSA addresses, we got rid of a similar problem under zVM440. 'DEDICATE 710 710 NOQIOASSIST'. There should be some pfts comming soon. Regards, Kurt. - Confidentiality Notice - This communication and the information it contains is intended (a) for the person(s) or organization(s) named above and for no other person or organization, and (b) may be confidential, legally privileged and protected by law. Unauthorized use, copying or disclosure of any of it may be unlawful! If you receive this communication in error, please notify us immediately, destroy any copies and delete it from your computer system. Please consult our disclaimer on our site www.securex.be Thank you. -- 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
AW: Fwd: SLES9 losing network connectivity
HI, the QIOASSIST problem occured in our installation with VM440. We installed PTFs: UM31170, UM31340, UM31370 Due to the conversion to VM510 we ran only 3 weeks with these ptf's - without a new occurrence of the error. VM510 was shipped with the appropriate ptf's installed (I don't know the numbers). So I don't know if there are any more needed/available. Regards Leonard -Ursprungliche Nachricht- Von: Kurt Verhofstadt [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 21. Juni 2005 10:59 An: LINUX-390@VM.MARIST.EDU Betreff: Re: Fwd: SLES9 losing network connectivity Do you have QIOASSIST on ? After setting NOQIOASSIST on the OSA addresses, we got rid of a similar problem under zVM440. 'DEDICATE 710 710 NOQIOASSIST'. There should be some pfts comming soon. Regards, Kurt. - Confidentiality Notice - This communication and the information it contains is intended (a) for the person(s) or organization(s) named above and for no other person or organization, and (b) may be confidential, legally privileged and protected by law. Unauthorized use, copying or disclosure of any of it may be unlawful! If you receive this communication in error, please notify us immediately, destroy any copies and delete it from your computer system. Please consult our disclaimer on our site www.securex.be Thank you. -- 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 -- 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
Re: AW: Fwd: SLES9 losing network connectivity
At 05:47 AM 6/21/2005, you wrote: HI, the QIOASSIST problem occured in our installation with VM440. We installed PTFs: UM31170, UM31340, UM31370 Due to the conversion to VM510 we ran only 3 weeks with these ptf's - without a new occurrence of the error. VM510 was shipped with the appropriate ptf's installed (I don't know the numbers). While we haven't lost connectivity with our SLES9 and or SLES8 images, installing SLES9 is/has been an adventure for connectivity. It takes several to many tries to install a SLES9 image in that pinging the gateway doesn't happen until after several tries. Once past that, we've seen no problems and we are a z/VM 5.1 shop. Now not knowing where the problem is I'd still say something in either SLES9, z/VM 5.1 or the OSA code needs fixed. So I don't know if there are any more needed/available. Regards Leonard -Ursprungliche Nachricht- Von: Kurt Verhofstadt [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 21. Juni 2005 10:59 An: LINUX-390@VM.MARIST.EDU Betreff: Re: Fwd: SLES9 losing network connectivity Do you have QIOASSIST on ? After setting NOQIOASSIST on the OSA addresses, we got rid of a similar problem under zVM440. 'DEDICATE 710 710 NOQIOASSIST'. There should be some pfts comming soon. Regards, Kurt. - Confidentiality Notice - This communication and the information it contains is intended (a) for the person(s) or organization(s) named above and for no other person or organization, and (b) may be confidential, legally privileged and protected by law. Unauthorized use, copying or disclosure of any of it may be unlawful! If you receive this communication in error, please notify us immediately, destroy any copies and delete it from your computer system. Please consult our disclaimer on our site www.securex.be Thank you. -- 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 -- 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 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 [EMAIL PROTECTED] -- 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
New URL for Linux on zSeries developerWorks web pages
Some of you may already have noticed that the Linux on zSeries developerWorks-pages are available at the new URL: http://www-128.ibm.com/developerworks/linux/linux390/ Some time later today (Tuesday 2005-06-21), re-directs from our old URLs will start to be effective, re-routing links to pages on: http://awlinux1.alphaworks.ibm.com/developerworks/linux390 http://www10.software.ibm.com/developerworks/opensource/linux390 http://oss.software.ibm.com/developerworks/oss/linux390 to the corresponding page at the new URL. It may be a while until the re-directs are effective, completely, but it is time to start changing your bookmarks and links on web-pages to Linux on zSeries developerWorks (if you haven't already done so), as the re-directs will not be in place for ever. Please use: http://www.ibm.com/developerworks/linux/linux390/ ...for online links ibm.com/developerworks/linux/linux390/ ...in print Note: We strongly advise to *NOT* use the www-128.ibm.com, but leave the -128 out and type it as above. Here is a summary of the changes effective on our new URL: - Previously, our web-pages were *.shtml, now they are *.html. -- The re-routes being set up should handle this change. - For the web-pages, directory-structure and [file-]names of the web-pages remain as before (except for the URL-handle, of course). - All patches, packages, OCO-modules will remain on the awlinux1-server for a while - but will be moved to an ftp-server in the next few months. - The PDFs with the manuals for our streams and documentation-downloads from the Tuning hints tips are available on an ftp-server. Here is some guidance for linking to our pages: - Please do not link to downloads (patches, OCO-modules, PDFs, etc.) from our pages, directly, but refer to the html-page where the link is shown. - Specifically, please do not link to PDFs, but to the Documentation page of the stream. As we found a lot of references to (old versions of) PDFs, we have established documentation archives for the active April 2004 and June 2003 streams (referenced on the Documentation page), with links to superseded (but still available) editions of the PDFs. * end of message Mit freundlichem Gruß / Kind regards, Gerhard Hiller eServer Software Management, D4357 IBM Development Lab, Boeblingen/Germany Phone ext. +49-(0)7031 - 16 - 4388 Internet: [EMAIL PROTECTED] -- 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
Install problem again
Hi, I can´t get by the initrd 75% problem when installing. I got an answer tht it is a relative path problem. I use NFS and mounts the /space/SLES9 Here is ls -l # ls -l /space/SLES9 total 18 lrwxrwxrwx 1 root other 19 Feb 2 16:09 boot - sles9-i386/CD1/boot lrwxrwxrwx 1 root other 22 Feb 2 16:08 content - sles9-i386/CD1/content lrwxrwxrwx 1 root other 26 Feb 2 16:08 control.xml - sles9-i386/CD1/control.xml drwxr-xr-x 7 root other512 Nov 8 2004 core9-i386 lrwxrwxrwx 1 root other 22 Feb 2 16:08 media.1 - sles9-i386/CD1/media.1 drwxr-xr-x 3 root other512 Oct 27 2004 sles9-i386 drwxr-xr-x 2 v065735 staff512 Feb 3 13:44 sles9_SP1 drwxr-xr-x 3 root other512 Feb 2 16:23 yast drwxr-xr-x 2 root other512 Oct 27 2004 yast_samba Here is the instorder file in yast directory /sles9-i386/CD1 /core9-i386/CD1 Here is the order file in yast directory /sles9-i386/CD1 /sles9-i386/CD1 /core9-i386/CD1 /core9-i386/CD1 Please help what do i do wrong BR // Claes -- 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
Re: Install problem again
I can´t get by the initrd 75% problem when installing. Is this for x86? Was a little confused at all the i386 talk in your email. Otherwise, this sounds similar to an experience we recently had. When using either the SLES9 or SLES9-SP1 installation images the process would hang with zipl (would stall at 75% on the progress bar). This problem was z/VM related. Sometime earlier in the install process pdflush would die with an illegal operation in do_writepages (calltrace was printed to the z/VM guest's console). One workaround might be to turn off all linux swap during the install (and run the install with at least 512MB storage). At IBM's recommendation we switched the root installation filesystem from cramfs to ext2 (replacing sles9/CD1/boot/root and increasing the ramdisk size appropriately in sles9/CD1/boot/parmfile). If this sounds like the same situation and disabling swap doesn't help you, you can email me offlist for instructions to create the ext2 root. Or if it hasn't been removed yet you might still be able to wget ftp://testcase.boulder.ibm.com/linux/fromibm/24487/root.ext2 and save yourself some time. This fs created for the SLES9 GA installation process. The new parmfile should read: ramdisk_size=196608 root=/dev/ram1 ro init=/linuxrc TERM=dumb ~ Daniel -- 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
Redbook From LPAR to Virtual Servers in Two Days is available
Hello list, The redbook z/VM and Linux on zSeries: From LPAR to Virtual Servers in Two Days is on the Web (finally! 52 days late) at: http://www.redbooks.ibm.com/abstracts/sg246695.html The files associated with this book are on the Web at: ftp://www.redbooks.ibm.com/redbooks/SG246695/ The book describes how to roll your own Linux virtual servers on IBM eServer zSeries under z/VM. It adopts a cookbook format that provides a clearly documented set of procedures for installing and configuring z/VM in a logical partition (LPAR) and then installing and customizing Linux. This book is based on SUSE LINUX Enterprise Server 9 (SLES9) for zSeries. In addition, it addresses both 31-bit and 64-bit distributions. This redbook also covers the associated REXX EXECs and Linux scripts to help speed the process. These tools are not IBM products, nor are they formally supported. However, they will be informally supported. You can find these scripts on the ITSO Web site as explained in Appendix B, Additional material on page 221. This IBM Redbook is written for those who want to achieve a quick start with z/VM and Linux. Prior to reading this IBM Redbook, you must have a general familiarity with zSeries technology and terminology. You do not need an in-depth understanding of z/VM and Linux. And to properly follow the procedures documented in this book, you need a zSeries LPAR with associated resources, z/VM 5.1 media, and a Linux distribution. Following is the table of Contents Chapter 1. Introduction to running z/VM and Linux on zSeries Chapter 2. Planning Chapter 3. Configuring a desktop machine Chapter 4. Installing and configuring z/VM Chapter 5. Configuring an NFS server Chapter 6. Installing and configuring Linux Chapter 7. Configuring NFS on the controller Chapter 8. Configuring Linux for cloning Chapter 9. Basic Linux virtual servers Chapter 10. Virtual communications server Chapter 11. Virtual communications controller server Chapter 12. Monitoring z/VM and Linux Chapter 13. Backup and restore Appendix A. z/VM options Appendix B. Additional material Thanks to all who contributed. It was a long haul: hopefully the fruits are worth the effort. 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
Linux 2.6 and zVM 4.4
Hi I've noticed that Linux kernel 2.6 requires zVM 4.4. Can someone tell me what support , in short words, 2.6 needs in 4.4 that 4.3 lacks. TIA Thomas Broman Systems Engineer Pulsen Productions AB [EMAIL PROTECTED] -- 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
Which file system?
We are migrating a DB2-UDB LINUX/390 SLES 7 server with the EXT2 filesystem to a SLES 9 server. Because of the nature and size of the databases we encounter a lot of issues with the 2 GIG file size limit (database containers, backups to disk, export and load files etc.). The long restarts after a failure on EXT2 is also an issue. We're looking for comments? insights? on the journaled filesystems EXT3, ReiserFS, XFS and JFS. Which is the best filesystem to support large database files with good performance and good reliability? -- 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
Re: Which file system?
Hearsay says that ReiserFS is a very poor performer on the zSeries. EXT3 would be easiest because EXT3 is simply EXT2 + journelling. You can convert your EXT2 to EXT3 in place. But I don't understand the comment about the 2 Gb file size limit. I no longer have Linux on zSeries, but there is no such limit on my Intel box (kernel 2.4.20). -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -Original Message- From: Linux on 390 Port [SMTP:[EMAIL PROTECTED] On Behalf Of Joe Nocket Sent: Tuesday, June 21, 2005 9:07 AM To: LINUX-390@VM.MARIST.EDU Subject: Which file system? We are migrating a DB2-UDB LINUX/390 SLES 7 server with the EXT2 filesystem to a SLES 9 server. Because of the nature and size of the databases we encounter a lot of issues with the 2 GIG file size limit (database containers, backups to disk, export and load files etc.). The long restarts after a failure on EXT2 is also an issue. We're looking for comments? insights? on the journaled filesystems EXT3, ReiserFS, XFS and JFS. Which is the best filesystem to support large database files with good performance and good reliability? -- 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 -- 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
Re: Which file system?
We only have Linux on zSeries and at SLES 7 with EXT2 there is a 2G file size limitation. I'm assuming EXT3 being EXT2 and journel would not get us over the size limit -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Tuesday, June 21, 2005 10:15 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Which file system? Hearsay says that ReiserFS is a very poor performer on the zSeries. EXT3 would be easiest because EXT3 is simply EXT2 + journelling. You can convert your EXT2 to EXT3 in place. But I don't understand the comment about the 2 Gb file size limit. I no longer have Linux on zSeries, but there is no such limit on my Intel box (kernel 2.4.20). -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -Original Message- From: Linux on 390 Port [SMTP:[EMAIL PROTECTED] On Behalf Of Joe Nocket Sent: Tuesday, June 21, 2005 9:07 AM To: LINUX-390@VM.MARIST.EDU Subject: Which file system? We are migrating a DB2-UDB LINUX/390 SLES 7 server with the EXT2 filesystem to a SLES 9 server. Because of the nature and size of the databases we encounter a lot of issues with the 2 GIG file size limit (database containers, backups to disk, export and load files etc.). The long restarts after a failure on EXT2 is also an issue. We're looking for comments? insights? on the journaled filesystems EXT3, ReiserFS, XFS and JFS. Which is the best filesystem to support large database files with good performance and good reliability? -- 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 -- 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 -- 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
Re: Which file system?
There is not a 2G file size limit on EXT2. I suspect that you are using an old version of DB2 that is not compiled with large file support. If this is true then it does not matter what filesystem you use. Another possibility is that you are using a very old kernel. I think the 2.2 kernel has a 2G limit. I am not sure about 2.4. I know that 2.6 does not have a 2G limit. When you move to SLES9 you should be running a kernel without a 2G limit, so you might want to test and make sure that you are hitting a 2G limit on SLES9. If you are hitting a 2G limit with EXT2 on SLES9 then DB2 would definitely be the problem. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Joe Nocket Sent: Tuesday, June 21, 2005 7:20 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Which file system? We only have Linux on zSeries and at SLES 7 with EXT2 there is a 2G file size limitation. I'm assuming EXT3 being EXT2 and journel would not get us over the size limit -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Tuesday, June 21, 2005 10:15 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Which file system? Hearsay says that ReiserFS is a very poor performer on the zSeries. EXT3 would be easiest because EXT3 is simply EXT2 + journelling. You can convert your EXT2 to EXT3 in place. But I don't understand the comment about the 2 Gb file size limit. I no longer have Linux on zSeries, but there is no such limit on my Intel box (kernel 2.4.20). -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. -Original Message- From: Linux on 390 Port [SMTP:[EMAIL PROTECTED] On Behalf Of Joe Nocket Sent: Tuesday, June 21, 2005 9:07 AM To: LINUX-390@VM.MARIST.EDU Subject: Which file system? We are migrating a DB2-UDB LINUX/390 SLES 7 server with the EXT2 filesystem to a SLES 9 server. Because of the nature and size of the databases we encounter a lot of issues with the 2 GIG file size limit (database containers, backups to disk, export and load files etc.). The long restarts after a failure on EXT2 is also an issue. We're looking for comments? insights? on the journaled filesystems EXT3, ReiserFS, XFS and JFS. Which is the best filesystem to support large database files with good performance and good reliability? -- 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 -- 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 -- 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 -- 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
Re: Linux 2.6 and zVM 4.4
I haven't seen anything as such. I ran a 2.6 kernel while on 4.3. -Original Message- From: Thomas Broman [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 21, 2005 8:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Linux 2.6 and zVM 4.4 Hi I've noticed that Linux kernel 2.6 requires zVM 4.4. Can someone tell me what support , in short words, 2.6 needs in 4.4 that 4.3 lacks. TIA Thomas Broman Systems Engineer Pulsen Productions AB [EMAIL PROTECTED] -- 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 -- 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
Re: Linux 2.6 and zVM 4.4
On Tuesday, 06/21/2005 at 03:58 ZE2, Thomas Broman [EMAIL PROTECTED] wrote: I've noticed that Linux kernel 2.6 requires zVM 4.4. Where did you see this, Thomas? Can you point me to a URL? Alan Altmark z/VM Development IBM Endicott -- 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
Re: Linux 2.6 and zVM 4.4
I'm z/VM 4.2 running SLES9 with SP1. Do you have any indication on what kind of problems I may be having running Linux? I'm not saying that I don't have problems, just I'm not sure what problems are mine and what problems are due to z/VM 4.2G. The only think I can think of is in the realm of communications. Guest LAN support, OSA and that sort of thing. Need PTFs to CP to be able to use Guest LAN support for example. But I don't think that is really a Linux thing. More of fixing the support in CP type of thing. Tom Duerbusch THD Consulting [EMAIL PROTECTED] 06/21/05 10:49 AM On Tuesday, 06/21/2005 at 03:58 ZE2, Thomas Broman [EMAIL PROTECTED] wrote: I've noticed that Linux kernel 2.6 requires zVM 4.4. Where did you see this, Thomas? Can you point me to a URL? Alan Altmark z/VM Development IBM Endicott -- 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 -- 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
3390 mod 9
Can someone tell me if SUSE 8.0 will recognize a 3390 mod 9 disk drive or not? -- 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
Re: 3390 mod 9
Thanks for the info. Does SuSE pick them up as mod 9 or do you configure them as mod 9? [EMAIL PROTECTED] 6/21/2005 11:09:13 AM yep. 3390-3 3390-9 3390-27. use all of them here. -Original Message- From: Mike Lovins [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 21, 2005 11:08 AM To: LINUX-390@VM.MARIST.EDU Subject: 3390 mod 9 Can someone tell me if SUSE 8.0 will recognize a 3390 mod 9 disk drive or not? -- 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 -- 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 -- 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
Re: AW: Fwd: SLES9 losing network connectivity
Thanks, I will give the NOQIOASSIST a try and get back with the results. Regards, Darren On Tuesday 21 June 2005 04:47, Leonard Janus wrote: HI, the QIOASSIST problem occured in our installation with VM440. We installed PTFs: UM31170, UM31340, UM31370 Due to the conversion to VM510 we ran only 3 weeks with these ptf's - without a new occurrence of the error. VM510 was shipped with the appropriate ptf's installed (I don't know the numbers). So I don't know if there are any more needed/available. Regards Leonard -Ursprungliche Nachricht- Von: Kurt Verhofstadt [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 21. Juni 2005 10:59 An: LINUX-390@VM.MARIST.EDU Betreff: Re: Fwd: SLES9 losing network connectivity Do you have QIOASSIST on ? After setting NOQIOASSIST on the OSA addresses, we got rid of a similar problem under zVM440. 'DEDICATE 710 710 NOQIOASSIST'. There should be some pfts comming soon. Regards, Kurt. - Confidentiality Notice - This communication and the information it contains is intended (a) for the person(s) or organization(s) named above and for no other person or organization, and (b) may be confidential, legally privileged and protected by law. Unauthorized use, copying or disclosure of any of it may be unlawful! If you receive this communication in error, please notify us immediately, destroy any copies and delete it from your computer system. Please consult our disclaimer on our site www.securex.be Thank you. -- 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 -- 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 -- 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
Re: 3390 mod 9
It really doesn't know what a mod x is. Just see is as dasd with 10017 (16?) cylinders. -Original Message- From: Mike Lovins [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 21, 2005 11:16 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: 3390 mod 9 Thanks for the info. Does SuSE pick them up as mod 9 or do you configure them as mod 9? [EMAIL PROTECTED] 6/21/2005 11:09:13 AM yep. 3390-3 3390-9 3390-27. use all of them here. -Original Message- From: Mike Lovins [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 21, 2005 11:08 AM To: LINUX-390@VM.MARIST.EDU Subject: 3390 mod 9 Can someone tell me if SUSE 8.0 will recognize a 3390 mod 9 disk drive or not? -- 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 -- 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 -- 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 -- 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
FCP tapes
Has anyone tried adding FCP tapes to linux. I was able to add FCP dasd to Suse v8 and I'm in the process of adding them to Suse v9, but I'm getting nothing but error messages when I try to add an FCP tape device to either system. I suspect, but I'm not sure, that I've probably got a problem with the device lun (aka FCP lun in v9). Is there any way to find out what the device lun really is? Both versions of Suse are running under z/VM 5.1, and as far as I can tell VM can see the mainframe device numbers (ucbs?) and recognizes that they're FCP. Sue -- Suzanne Sivets Systems Programmer Innovation Data Processing 275 Paterson Ave Little Falls, NJ 07424-1658 973-890-7300 Fax 973-890-7147 [EMAIL PROTECTED] -- 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
Re: 3390 mod 9
Sure, since SUSE 7.0 recognize it. Carlos Alberto Bodra S/390 System Programmer Sao Paulo - Brazil -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mike Lovins Sent: Tuesday, June 21, 2005 1:08 PM To: LINUX-390@VM.MARIST.EDU Subject: 3390 mod 9 Can someone tell me if SUSE 8.0 will recognize a 3390 mod 9 disk drive or not? -- 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 -- 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
Re: 3390 mod 9
Yes, it will. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mike Lovins Sent: Tuesday, June 21, 2005 12:08 PM To: LINUX-390@VM.MARIST.EDU Subject: 3390 mod 9 Can someone tell me if SUSE 8.0 will recognize a 3390 mod 9 disk drive or not? -- 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 -- 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
Re: 3390 mod 9
On Tue, Jun 21, 2005 at 11:07:30AM -0500, Mike Lovins wrote: Can someone tell me if SUSE 8.0 will recognize a 3390 mod 9 disk drive or not? Yes. Adam -- 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
Re: Which file system?
The ext3 file system does not have that limitation when running on a 2.6 kernel. In your place, I would be using ext3. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Joe Nocket Sent: Tuesday, June 21, 2005 10:20 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Which file system? We only have Linux on zSeries and at SLES 7 with EXT2 there is a 2G file size limitation. I'm assuming EXT3 being EXT2 and journel would not get us over the size limit -- 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
Re: Which file system?
We did some experimenting and found that it's DB2 (V7) that has the 2G file size limitation and not the ext2 filesystem, I believe DB2 V8 will lift this restriction. We are probably going to use ext3, but I am still curious if anyone has any experience using JFS on zSeries Linux since it's IBM support team claims the Linux implementation outperforms ext3. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Tuesday, June 21, 2005 2:50 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Which file system? The ext3 file system does not have that limitation when running on a 2.6 kernel. In your place, I would be using ext3. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Joe Nocket Sent: Tuesday, June 21, 2005 10:20 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Which file system? We only have Linux on zSeries and at SLES 7 with EXT2 there is a 2G file size limitation. I'm assuming EXT3 being EXT2 and journel would not get us over the size limit -- 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 -- 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
Re: Which file system?
http://www-128.ibm.com/developerworks/linux/linux390/perf/tuning_res_journal ing.html#begin or if you get a line break in that . . . http://tinyurl.com/8fg67 -Original Message- From: Joe Nocket [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 21, 2005 3:21 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Which file system? We did some experimenting and found that it's DB2 (V7) that has the 2G file size limitation and not the ext2 filesystem, I believe DB2 V8 will lift this restriction. We are probably going to use ext3, but I am still curious if anyone has any experience using JFS on zSeries Linux since it's IBM support team claims the Linux implementation outperforms ext3. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Tuesday, June 21, 2005 2:50 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Which file system? The ext3 file system does not have that limitation when running on a 2.6 kernel. In your place, I would be using ext3. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Joe Nocket Sent: Tuesday, June 21, 2005 10:20 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Which file system? We only have Linux on zSeries and at SLES 7 with EXT2 there is a 2G file size limitation. I'm assuming EXT3 being EXT2 and journel would not get us over the size limit -- 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 -- 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 -- 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
risk if I relabel an LVM DASD Volume
Question: would my volume-group and logical-volume (LVM) be in trouble if I re-label one or more of the physical volumes allocated to the lv? I forgot to label the volumes when I created them and my zOS guy is getting them in his reports (bad label). We use zOS DF/DSS for backups so I am very much forced into having the correct label. I was thinking to IPL SLES-9 without the LVM's in /etc/fstab. That way I could do the fdasd -l xxx. My other option is to backup the data, delete the LV-group/volume. Re-label. Then put it back. A lot of work. any suggestions are welcome, except killing the zOS guy. Regards, [EMAIL PROTECTED] NCCI Boca Raton, Florida 561.893.2415 greetings / avec mes meilleures salutations / Cordialmente mit freundlichen Grüßen / Med vänlig hälsning 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: risk if I relabel an LVM DASD Volume
My initial guess is that it doesn't use the volume label. I know that you can change device numbers, and device names and lvm will still find it. However, don't take my word for it. i've screwed up before. -Original Message- From: Uriel Carrasquilla [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 21, 2005 5:00 PM To: LINUX-390@VM.MARIST.EDU Subject: risk if I relabel an LVM DASD Volume Question: would my volume-group and logical-volume (LVM) be in trouble if I re-label one or more of the physical volumes allocated to the lv? I forgot to label the volumes when I created them and my zOS guy is getting them in his reports (bad label). We use zOS DF/DSS for backups so I am very much forced into having the correct label. I was thinking to IPL SLES-9 without the LVM's in /etc/fstab. That way I could do the fdasd -l xxx. My other option is to backup the data, delete the LV-group/volume. Re-label. Then put it back. A lot of work. any suggestions are welcome, except killing the zOS guy. Regards, [EMAIL PROTECTED] NCCI Boca Raton, Florida 561.893.2415 greetings / avec mes meilleures salutations / Cordialmente mit freundlichen Grüßen / Med vänlig hälsning 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: /tmp as a logical volume
go for it. you'll be fine. you'll have the same risks as any other mounted filesystem. -Original Message- From: Uriel Carrasquilla [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 21, 2005 5:10 PM To: LINUX-390@VM.MARIST.EDU Subject: /tmp as a logical volume We have /tmp as part of the / (root) file system in one 3390 volume (m9). I was wondering what reaction I would get from this list if I was to create a logical-volume (lvtmp), part of an existing volume-group (vgsys01) and mount it as /tmp. Would SuSE SLES-9 be ok with it? what are my risks if under LVM? would I be able to IPL if the LVM gets damaged and I just change my /etc/fstab to remove the reference to /tmp? any suggestions, comments and ideas are welcome. Regards, [EMAIL PROTECTED] NCCI Boca Raton, Florida 561.893.2415 greetings / avec mes meilleures salutations / Cordialmente mit freundlichen Grüßen / Med vänlig hälsning 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: risk if I relabel an LVM DASD Volume
I have run fdasd against LVM minidisks and recreated the VTOC from 0x0300 (for example) to a standard pack name that can be read by the z/OS systems. Betsie Little, Chris wrote: My initial guess is that it doesn't use the volume label. I know that you can change device numbers, and device names and lvm will still find it. However, don't take my word for it. i've screwed up before. -Original Message- From: Uriel Carrasquilla [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 21, 2005 5:00 PM To: LINUX-390@VM.MARIST.EDU Subject: risk if I relabel an LVM DASD Volume Question: would my volume-group and logical-volume (LVM) be in trouble if I re-label one or more of the physical volumes allocated to the lv? I forgot to label the volumes when I created them and my zOS guy is getting them in his reports (bad label). We use zOS DF/DSS for backups so I am very much forced into having the correct label. I was thinking to IPL SLES-9 without the LVM's in /etc/fstab. That way I could do the fdasd -l xxx. My other option is to backup the data, delete the LV-group/volume. Re-label. Then put it back. A lot of work. any suggestions are welcome, except killing the zOS guy. Regards, [EMAIL PROTECTED] NCCI Boca Raton, Florida 561.893.2415 greetings / avec mes meilleures salutations / Cordialmente mit freundlichen Grüßen / Med vänlig hälsning 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: /tmp as a logical volume
I build all my systems with /tmp separate from /. That goes for Linux/390 and Intel Linux. SLES9 will handle it nicely. I'm beginning to have doubts about LVM (version 1 at least) on 64-bit systems. I've had two cases where my volume groups have disappeared after an IPL, and hence all my logical volumes. Emails to the linux-lvm mailing list have gone unanswered. I don't know if it's because I'm running Linux/390, LVM 1 or what. Having said that, if you're going to use LVM, using it for /tmp is certainly the safest. According to the FHS, the contents of /tmp are not guaranteed across a reboot anyway. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Uriel Carrasquilla Sent: Tuesday, June 21, 2005 6:10 PM To: LINUX-390@VM.MARIST.EDU Subject: /tmp as a logical volume We have /tmp as part of the / (root) file system in one 3390 volume (m9). I was wondering what reaction I would get from this list if I was to create a logical-volume (lvtmp), part of an existing volume-group (vgsys01) and mount it as /tmp. Would SuSE SLES-9 be ok with it? what are my risks if under LVM? would I be able to IPL if the LVM gets damaged and I just change my /etc/fstab to remove the reference to /tmp? any suggestions, comments and ideas are welcome. Regards, [EMAIL PROTECTED] NCCI Boca Raton, Florida 561.893.2415 greetings / avec mes meilleures salutations / Cordialmente mit freundlichen Grüßen / Med vänlig hälsning 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
