FCP Access Control
One of the interesting items for SCSI users is the following: Configuration Utility: The Configuration Utility for FCP LUN Access Control is designed to be a Linux user space application which may be used to configure the FCP LUN Access Control. To define and activate LUN Access Control, you would create an access control table that describes the access rights in XML format. In this table, you would define access rights to storage controllers and devices in the SAN and identify devices to be shared in read-only mode. The Configuration Utility for FCP LUN Access Control is required to process the access control table, verify proper specification of the rules, and activate the access control functions in the FCP channel. The Configuration Utility for FCP LUN Access Control is designed to be a package consisting of user documentation and sample files with a skeleton to help you generate an XML-format access control table, and the utility program itself. The program is intended to provide a command line interface (CLI) and be supported by Linux on zSeries. The Configuration Utility will be provided for download by registered users via Resource Link (TM) http://www.ibm.com/servers/resourcelink/ A user's guide for this function is available, and is named Configuration Utility for FCP LUN Access Control User's Guide, publication SC33-8280-00. FCP LUN Access Control will be supported by the FICON Express2 and FICON Express features when configured as CHPID type FCP, will be exclusive to z990 and z890, and is planned to be available in the z/VM and Linux on zSeries environments. Refer to the Software requirements section for further information. This statement represents IBM's current intentions. IBM development plans are subject to change or withdrawal without further notice. To obtain the authorization code for downloading both the configuration tool and the user's manual via Resource Link, contact via e-mail: [EMAIL PROTECTED] You must include your Resource Link ID, the customer name, the z990/z890 machine serial number, and a short description of intended usage. In the subject line, place "Requesting access to FCP LUN Access Configuration Utility." Once approved, you will be given access to download the tool. -- 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
Interesting z890/z990 enhancements
See: http://www.vm.ibm.com/siteinfo/change.html for January 25 announcements. -- 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: SuSE Installation Server
Found ans. to my question: # SPident CONCLUSION: ServicePack Level: SLES-9-s390-SP1 => up-to-date == Other info = # cat /etc/*-release SUSE LINUX Enterprise Server 9 (s390) VERSION = 9 # uname -a Linux lnxtest1 2.6.5-7.97-s390 #1 SMP Fri Jul 2 14:21:59 UTC 2004 s390 s390 s390 GNU/Linux Ismael -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: Wednesday, January 26, 2005 3:21 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SuSE Installation Server cat /etc/*-release Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ifurung, [EMAIL PROTECTED] Sent: Wednesday, January 26, 2005 5:56 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SuSE Installation Server -snip- Question: How can I tell that my system is sles9 SP1 ? -- 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: appropriate value of "LOAD AVERAGE"
--- Rob van der Heij <[EMAIL PROTECTED]> wrote: > > My client asked me what is the appropriate value of "LOAD AVERAGE" value when the system is IDLE. (well i think he meant idle "NO MIDDLEWARE (and some DBs) RUNNING") > The answer is 0. :-) I thought so, too. However somewhat this value is around 1〜2 on the client's system. I read that when you submit a "vmstat" command, then [cpu us] value sometimes could contain other Linux Guest OS's operation, so vmstat is not really helpful for performance monitoring. I just wander and want to know could this be true to "uptime" too? Tomoyuki Yatsunami, Tokyo, Japan, [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: SuSE Installation Server
cat /etc/*-release Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Ifurung, [EMAIL PROTECTED] Sent: Wednesday, January 26, 2005 5:56 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SuSE Installation Server -snip- Question: How can I tell that my system is sles9 SP1 ? -- 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: SuSE Installation Server
Mike, The procedure you provided ( http://mikemacisaac.com/configureNFS.pdf ) for setting up a linux install server worked well. I did have to change one little thing: blanked out the "\t" from the files yast/instorder; yast/order. So with the prepared linux (desktop) install server, I was able to successfully install a base SLES9 on z/VM . For SP1 upgrade, I used the following procedure: In the Install server: 1) download SP1 iso images for CD1, CD2 2) mount loop iso images to tmp dir 3) created diretory: /sles9-s3900-sp1/CD1, /sles9-s3900-sp1/CD2 4) copied iso files from tmp to above directories 5) using yast, NFS export /sles9-s3900-sp1 In target Image: 1) register new install source: -yast software / Change source of Installation add: install_server / sles9-s3900-sp1/CD1 (CD1 only, CD2 not reqd) move to top of list 2) do the upgrade: - yast software / system update (take all defaults) 3) re-boot == So the upgrade appears to have worked. Question: How can I tell that my system is sles9 SP1 ? Uname -a : Linux lnxtest4 2.6.5-7.139-s390 #1 SMP Fri Jan 14 15:41:33 UTC 2005 s390 s390 s390 GNU/Linux Ismael -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Michael MacIsaac Sent: Sunday, January 23, 2005 8:01 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: SuSE Installation Server Ismael, > How do I integrate the recently released SLES9 SP1 yast -> software -> Patch CD update It's documented (for SLES8 and SP3 at least) in the zDomino redbook: SG24-7021. "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 -- 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: Having 1 linux kernel
We use a variation of the Using BIND Mounts to Create A Simplified BaseVol/GuestVol Linux Server process outlined at: http://linuxvm.org/present/misc/basevol.html Instead of the REXX scripts, we used standard scripting. We have the / (root) and /opt file systems as R/O z/VM mini disks. The rest of the data is mounted in R/W LVMs. We maintain Linux in a 3-tier approach. A Maintenance Linux in which all updates and installs take place to the R/W / and /opt directories. These directories are then cloned to a Testing Linux where the / and /opt directories are only R/O. This is necessary to insure that no writes are attempted to the R/O directories. After we are happy with testing, we move the / and /opt directories to the ?Golden Linux? from which all Penguins share in a R/O mode. Some advantages are: We maintain one Linux but many virtual Linux guests. We can install products once and make them available to all Linux guests. If a Linux guest does not need them, they just do not use them. The cost is a R/O /opt which is necessary if only one Linux required a product anyway. Prevents accidental and/or unauthorized changes to Linux or its program products. Simplifies security, backup and recovery. Some disadvantages are: We do not run many Linux guests yet and might have no idea what we are getting into. Must have a set of guidelines and procedures that must be adhered to. But then, making people play by the rules is not necessarily a bad thing. Some software might require repackaging or modification to insure R/O data goes to R/O file systems and R/W data goes to R/W file systems. I hope this helps -- 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: Debian Sarge on 7060 H30 LPAR
On Jan 26, 2005, at 3:16 PM, Richard Pinion wrote: Yes, I think it is finding the card because it asks me to verify the CTC devices addresses of B30-B31. I am unable to perform any actions from the console because of the install script. It keeps asking me for the country and mirror site. How can I stop the install script and get back to a command prompt, change the parmfile?? Well, after it's done that--before you tell it country and mirror--can you ping it from your desktop? That will tell you whether the network config succeeded. You may also need to set your MTU to 1492 since the OS/2 LCS emulation eats 8 bytes. I'm not entirely sure I remember this right, but I think if you add debconf/priority=low to the parmfile you boot with, you will get all manner of really obnoxious questions (incl. MTU) that are normally hidden from you and defaults assumed. 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: Debian Sarge on 7060 H30 LPAR
Yes, I think it is finding the card because it asks me to verify the CTC devices addresses of B30-B31. I am unable to perform any actions from the console because of the install script. It keeps asking me for the country and mirror site. How can I stop the install script and get back to a command prompt, change the parmfile?? >>> [EMAIL PROTECTED] 01/26/05 04:06PM >>> On Jan 26, 2005, at 1:38 PM, Richard Pinion wrote: > I am attempting to install Debian Sarge on a LPAR of an IBM 7060 H30 > using emio (IOCP CTC device and defined as LCS when using z/OS TCP/IP) > for the network interface. After selecting LCS and entering the TCP > configuration parms, (IP address, gateway address, name server > address, host name, and domain name) I am unable to establish an SSH > connection. > > Guys from Sinenomine any ideas? > Is the LCS detected OK from the Sarge network parms screen? That is, does it find the device address? Can you ping yourself? Can you ping the gateway? Can you ping the nameserver? Once it claims to be up, can you ping the Sarge host from your desktop? 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 -- 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: Debian Sarge on 7060 H30 LPAR
On Jan 26, 2005, at 1:38 PM, Richard Pinion wrote: I am attempting to install Debian Sarge on a LPAR of an IBM 7060 H30 using emio (IOCP CTC device and defined as LCS when using z/OS TCP/IP) for the network interface. After selecting LCS and entering the TCP configuration parms, (IP address, gateway address, name server address, host name, and domain name) I am unable to establish an SSH connection. Guys from Sinenomine any ideas? Is the LCS detected OK from the Sarge network parms screen? That is, does it find the device address? Can you ping yourself? Can you ping the gateway? Can you ping the nameserver? Once it claims to be up, can you ping the Sarge host from your desktop? 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
LVM Volume Group Descriptor Area (VGDA) Recovery HOWTO
A new HOWTO, "LVM Volume Group Descriptor Area (VGDA) Recovery" has been added to the linuxvm.org web site. Thanks to Peter Abresch for doing this write-up for us. http://linuxvm.org/Info/HOWTOs/ Mark Post -- 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
Debian Sarge on 7060 H30 LPAR
I am attempting to install Debian Sarge on a LPAR of an IBM 7060 H30 using emio (IOCP CTC device and defined as LCS when using z/OS TCP/IP) for the network interface. After selecting LCS and entering the TCP configuration parms, (IP address, gateway address, name server address, host name, and domain name) I am unable to establish an SSH connection. Guys from Sinenomine any ideas? -- 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
VM: What was an input: REXEC or LOGON Userid?
Ref: Your note of Wed, 26 Jan 2005 14:00:42 -0500 Sorry - wrong mailing list! (I get them easily confused..) Bruce -- 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
VM: What was an input: REXEC or LOGON Userid?
Ref: Your note of Wed, 26 Jan 2005 19:58:51 +0100 (attached) Q AUTOUSER is a local exit... (local = "all IBM internal systems" ;-) Very useful, though.. Bruce Hayden IBM Global Services Endicott, NY - Note follows -- > REXECD does not use LOGON BY, it uses XAUTOLOG. So Q AUTOUSER then? ( or have I been listening in the wrong rooms?) -- Rob van der Heij rvdheij @ gmail.com -- 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: Having 1 linux kernel
Kernel sharing would be a nice-to-have feature. There just seem to be a lot of issues surrounding it's implementation. They involve extensive bootup customizations, r/o and r/w switching, and non-standard manipulations of file systems. Ask five people how to do it and you will get five different solutions. Some are really elegant but they look difficult to undo if your needs change, or if part of your penguin farm has to stay back-level for compatibility reasons. But there needs to be a standardized, supportable way to do this to allow everyone to leverage this important advantage. For now, the real beauty of Linux on VM, which I saw from the very beginning, is the ability to quickly restore your production environment at the DR location. Put another way, which would you rather recover: 100 1U servers with their disks/SAN(s) and network infrastructure, or 1 or 2 mainframe partitions? Ray Mrohs Energy Information Administration U.S. Department of Energy -Original Message- From: Noll, Ralph [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 26, 2005 11:00 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Having 1 linux kernel That's ok... Don't mind each linux guest having r/w to /usr/opt Just want 1 place to upgrade the kernel... If not might as well have 1u servers. Ralph -Original Message- From: Adam Thornton [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 26, 2005 9:34 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Having 1 linux kernel On Jan 26, 2005, at 8:39 AM, Noll, Ralph wrote: > > Is there any doc on setting up 1 linux kernel and all linux guests > booting from That 1 kernel... > > Right now I have 8 linux guests all with separate boot disks... > > Be nice to have just one.. > You can put the kernel in NSS and then everyone can IPL that shared segment, but that doesn't really get you around needing some per-machine unique r/w DASD. Although with a shared kernel in NSS and smart use of basevol/guestvol, you could probably get a system with minimal writeable DASD. http://www.vm.ibm.com/linux/linuxnss.html tells you how to do the NSS trick. Ignore the "64M is recommended" bit; I've done it successfully in 12M. Do it in the smallest size you're ever going to want to run with. 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 -- 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: z/Linux SuSE 8.2 and Openssh-3.4p1
Ooof. You just tripped over one of the big reasons why RPM-managed systems need to have all their updates installed via RPM. If you have gcc and glibc-devel installed on your system, what I normally recommend is taking the .src.rpm for the current version of the package, and doing an "rpm -ivh" on it. This will place the source files in /usr/src/packages/SOURCES and the .spec file in /usr/src/packages/SPECS. Look at the openssh.spec file to see how SUSE built it. Download the current source package from openssh.org, and tweak the .spec file to use that, instead of the original version. Do an "rpmbuild -bb openssh.spec" and watch the build crash and burn. Tweak the .spec file to fix whatever problem you encountered, rinse and repeat. Learning how to do this (and in most cases it's not too difficult a process), frees you from depending on anyone, including your Linux distribution provider, to provide you with software versions you require. Quite liberating once you feel confident of your ability to build software. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Lewis, Ted (OFT) Sent: Wednesday, January 26, 2005 11:43 AM To: LINUX-390@VM.MARIST.EDU Subject: z/Linux SuSE 8.2 and Openssh-3.4p1 On SuSE 8.2, openssh-3.4p1 causes an ssh disconnect when updating LDAP expired passwords. Has anyone else experienced this problem and how did they solve it (if it's solved)? According to SuSE, it is a known bug and their recommendation is to upgrade to SLES 9 or download the latest version of openssh (bug fixed in openssh-3.5 and later). We cannot upgrade to SLES 9 due to software certification. Downloading the latest release of openssh (3.9p1 - non RPM) raises maintenance issues - updating the RPM database, patches, etc. - YaST2 still shows 3.4p1 install. I can remove openssh-3.4p1 from the YaST2 RPM database, but that is only a work around. Do you know of an openssh release at 3.5p1 or later that is in SuSE RPM format? Ted Lewis (518-473-1104) VM & z/Linux NYS Office for Technology -- 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
z/Linux SuSE 8.2 and Openssh-3.4p1
On SuSE 8.2, openssh-3.4p1 causes an ssh disconnect when updating LDAP expired passwords. Has anyone else experienced this problem and how did they solve it (if it's solved)? According to SuSE, it is a known bug and their recommendation is to upgrade to SLES 9 or download the latest version of openssh (bug fixed in openssh-3.5 and later). We cannot upgrade to SLES 9 due to software certification. Downloading the latest release of openssh (3.9p1 - non RPM) raises maintenance issues - updating the RPM database, patches, etc. - YaST2 still shows 3.4p1 install. I can remove openssh-3.4p1 from the YaST2 RPM database, but that is only a work around. Do you know of an openssh release at 3.5p1 or later that is in SuSE RPM format? Ted Lewis (518-473-1104) VM & z/Linux NYS Office for Technology -- 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: Awwww...come on, guys...help us out...
On Jan 26, 2005, at 10:38 AM, Miguel Diaz wrote: ...and not the cheap gold you buy in Times Square either; we're talking "dear god the market's crashing and I need a safe investment" gold here :-) I just want to point out that in the event of a REAL catastrophe, lead and gold have very similar ballistic and neutron-stopping properties and it's a whole lot cheaper to buy lead. Just don't lick it. And whatever you do, stay away from fancy bottles of cinnamon schnapps advertising themselves as Leadschlager. 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: Awwww...come on, guys...help us out...
...and not the cheap gold you buy in Times Square either; we're talking "dear god the market's crashing and I need a safe investment" gold here :-) Regards, Miguel Diaz Staff Software Engineer z/VM TCP/IP Development IBM Corporation 607.429.3504 [EMAIL PROTECTED] Linux on 390 Port wrote on 01/26/2005 11:31:26 AM: > I won't be at this SHARE, but I want to add my two cents here. > > If you volunteer as a session chair, you will be treated like GOLD. > > If you're going to attend one of these sessions anyway, do yourself a > BIG FAVOUR and volunteer to chair it. > > TIA > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of > Martha McConaghy > Sent: Wednesday, January 26, 2005 7:42 AM > To: LINUX-390@VM.MARIST.EDU > Subject: A...come on, guys...help us out... > > > OK, I'm not above begging, at least when it is for a good cause. > > Response to my request for session chairs for SHARE has been somewhat less > than overwhelming. I know it is tough to choose when SHARE is still a month > away. However, the Linux and VM Program is putting on a lot of really > terrific sessions. So, whatever you choose, it will be a good one. It's > easy to do and only requires 1 hour of your time...an hour you would be > spending in that session anyway. So, please help us out and sign up to > chair a session or two. The following is a list of the available sessions. > Just send me a note (OFF LIST, PLEASE!) with the session numbers you want. > It's that easy! > > If you have questions, let me know. > > Martha > > Day Time Sess Title > --- -- --- > Mon 09:30a 9100 z/VM Platform Update > Mon 09:30a 9200 Linux and Open Souce: The View from IBM > Mon 11:00a 9102 z/VM: The Very Basics > Mon 11:00a 9202 Linux Platform Options - Selecting Linux on zSeries > Mon 01:30p 9214 Virtualization in the Real World - zSeries Linux Customer Exp > Mon 03:00p 9106 VM Performance Update > Mon 03:00p 9112 z/VM TCP/IP Stack Configuration > Mon 03:00p 9207 Directory Serving Solutions using OpenLDAP > Mon 04:30p 9142 z/VM Device Support Overview > > Tue 08:00a 9113 The z/VM Control Program (CP), Part 1 - Useful Things to Know > Tue 08:00a 9131 VM TCP/IP Routing > Tue 08:00a 9255 Linux Debugging at the System Level > Tue 09:30a 9107 Introduction to VM Hands-On Lab - Part 1 of 2 > Tue 09:30a 9114 The z/VM Control Program (CP), Part 2 - Under the Covers > Tue 09:30a 9115 VM Performance Introduction > Tue 09:30a 9215 Penguins Board the Stagecoach for the Linux > Frontier: A User Exp > Tue 11:00a 9108 Introduction to VM Hands-On Lab - Part 2 of 2 > Tue 11:00a 9128 Hardware Configuration Management for z/VM > Tue 11:00a 9237 VM and Linux Performance Issues > Tue 01:30p 9136 Automated Linux Guest Monitoring on z/VM using PROP > Tue 01:30p 9227 Linux for S/390 Installation Hands-On Lab - Part 1 of 3 > Tue 01:30p 9281 Replacing Windows Servers with Linux > Tue 03:00p 9133 Configuring, Customizing and Modifying Your VM System w/o IPL > Tue 03:00p 9228 Linux for S/390 Installation Hands-On Lab - Part 2 of 3 > Tue 03:00p 9267 Networking with Linux on zSeries - Part 1 of 2 > Tue 04:30p 9134 Dynamically Managing Hardware I/O Configuration Using VM > Tue 04:30p 9229 Linux for S/390 Installation Hands-On Lab - Part 3 of 3 > Tue 04:30p 9268 Networking with Linux on zSeries - Part 2 of 2 > Tue 06:00p 9248 Help! My (Virtual) Penguin is Sick! > > Wed 08:00a 9205 Attack of the Linux Clones at Marist College > Wed 09:30a 9118 Maintaining z/VM by Using and Understanding VMSES/E > Wed 09:30a 9224 Linux for S/390 System Management for the MF SysProg - 1 of 2 > Wed 11:00a 9126 Performance Toolkit for VM > Wed 11:00a 9225 Linux for S/390 System Management for the MF SysProg - 2 of 2 > Wed 01:30p 9129 z/VM Security and Integrity > Wed 01:30p 9238 Linux on z/VM Performance Measurement and Tuning > Wed 01:30p 9242 Linux for Beginners Hands-On Lab - Part 1 of 3 > Wed 03:00p 9148 Disaster Recovery, Backup & Restore for z/VM & Linux > Wed 03:00p 9243 Linux for Beginners Hands-On Lab - Part 2 of 3 > Wed 03:00p 9249 Linux for zSeries in Production : A User's Experience > Wed 04:30p 9212 Managing a Penguin Farm on the VM Prairie > Wed 04:30p 9241 Understanding Linux Memory Management > Wed 04:30p 9244 Linux for Beginners Hands-On Lab - Part 3 of 3 > Wed 06:00p 9269 Scalability of the Linux Kernel 2.6 on zSeries > Wed 06:00p 9271 Lab: How to Make a Webserver Highly Available with Tivoli > > Thu 08:00a 9121 Performance Choices for Linux and Other VM Guests > Thu 08:00a 9123 TRACK for z/VM - What's Happening in Your Virtual Machines? > Thu 08:00a 9265 Enhancing Scalability of Linux on z/VM Using Execute-in-Place > Thu 09:30a 9209 Using Oracle Products on Linux for IBM's zSeries Computing Env > Thu 09:30a 9273 Exploration of Open Source Security Tools for > z/Linux Server Env > Thu 11:00a 9132 MPRoute Configuration for z/VM > Thu 11:00a 9257 Linux on zSeries Journaling File Systems > Thu 11
Re: Having 1 linux kernel
On Wed, 26 Jan 2005 10:00:05 -0600, Noll, Ralph <[EMAIL PROTECTED]> wrote: > That's ok... > Don't mind each linux guest having r/w to /usr/opt > Just want 1 place to upgrade the kernel... > If not might as well have 1u servers. If you don't want to use NSS (for example because it is unsupported) then you could consider to take a small mini disk to mount at /lib/modules and also put the kernel on it so you can IPL that one to get your favorite kernel. The bad news is that you also need to keep the kernel command line the same, so you must standardize on the virtual disk addresses to use. Also, the boot process typically wants to write into that area so you may need to play with --bind mounts to create some write space inside again. It gets hairy. We have gone that way for our servers because I believe in not having serviceable parts inside (I can upgrade the kernel by simple system wide switches). I am considering to use the xip2fs to pack the kernel modules in a DCSS that goes with the NSS. Rob -- Rob van der Heij rvdheij @ gmail.com -- 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: Awwww...come on, guys...help us out...
I won't be at this SHARE, but I want to add my two cents here. If you volunteer as a session chair, you will be treated like GOLD. If you're going to attend one of these sessions anyway, do yourself a BIG FAVOUR and volunteer to chair it. TIA -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of Martha McConaghy Sent: Wednesday, January 26, 2005 7:42 AM To: LINUX-390@VM.MARIST.EDU Subject: A...come on, guys...help us out... OK, I'm not above begging, at least when it is for a good cause. Response to my request for session chairs for SHARE has been somewhat less than overwhelming. I know it is tough to choose when SHARE is still a month away. However, the Linux and VM Program is putting on a lot of really terrific sessions. So, whatever you choose, it will be a good one. It's easy to do and only requires 1 hour of your time...an hour you would be spending in that session anyway. So, please help us out and sign up to chair a session or two. The following is a list of the available sessions. Just send me a note (OFF LIST, PLEASE!) with the session numbers you want. It's that easy! If you have questions, let me know. Martha Day Time Sess Title --- -- --- Mon 09:30a 9100 z/VM Platform Update Mon 09:30a 9200 Linux and Open Souce: The View from IBM Mon 11:00a 9102 z/VM: The Very Basics Mon 11:00a 9202 Linux Platform Options - Selecting Linux on zSeries Mon 01:30p 9214 Virtualization in the Real World - zSeries Linux Customer Exp Mon 03:00p 9106 VM Performance Update Mon 03:00p 9112 z/VM TCP/IP Stack Configuration Mon 03:00p 9207 Directory Serving Solutions using OpenLDAP Mon 04:30p 9142 z/VM Device Support Overview Tue 08:00a 9113 The z/VM Control Program (CP), Part 1 - Useful Things to Know Tue 08:00a 9131 VM TCP/IP Routing Tue 08:00a 9255 Linux Debugging at the System Level Tue 09:30a 9107 Introduction to VM Hands-On Lab - Part 1 of 2 Tue 09:30a 9114 The z/VM Control Program (CP), Part 2 - Under the Covers Tue 09:30a 9115 VM Performance Introduction Tue 09:30a 9215 Penguins Board the Stagecoach for the Linux Frontier: A User Exp Tue 11:00a 9108 Introduction to VM Hands-On Lab - Part 2 of 2 Tue 11:00a 9128 Hardware Configuration Management for z/VM Tue 11:00a 9237 VM and Linux Performance Issues Tue 01:30p 9136 Automated Linux Guest Monitoring on z/VM using PROP Tue 01:30p 9227 Linux for S/390 Installation Hands-On Lab - Part 1 of 3 Tue 01:30p 9281 Replacing Windows Servers with Linux Tue 03:00p 9133 Configuring, Customizing and Modifying Your VM System w/o IPL Tue 03:00p 9228 Linux for S/390 Installation Hands-On Lab - Part 2 of 3 Tue 03:00p 9267 Networking with Linux on zSeries - Part 1 of 2 Tue 04:30p 9134 Dynamically Managing Hardware I/O Configuration Using VM Tue 04:30p 9229 Linux for S/390 Installation Hands-On Lab - Part 3 of 3 Tue 04:30p 9268 Networking with Linux on zSeries - Part 2 of 2 Tue 06:00p 9248 Help! My (Virtual) Penguin is Sick! Wed 08:00a 9205 Attack of the Linux Clones at Marist College Wed 09:30a 9118 Maintaining z/VM by Using and Understanding VMSES/E Wed 09:30a 9224 Linux for S/390 System Management for the MF SysProg - 1 of 2 Wed 11:00a 9126 Performance Toolkit for VM Wed 11:00a 9225 Linux for S/390 System Management for the MF SysProg - 2 of 2 Wed 01:30p 9129 z/VM Security and Integrity Wed 01:30p 9238 Linux on z/VM Performance Measurement and Tuning Wed 01:30p 9242 Linux for Beginners Hands-On Lab - Part 1 of 3 Wed 03:00p 9148 Disaster Recovery, Backup & Restore for z/VM & Linux Wed 03:00p 9243 Linux for Beginners Hands-On Lab - Part 2 of 3 Wed 03:00p 9249 Linux for zSeries in Production : A User's Experience Wed 04:30p 9212 Managing a Penguin Farm on the VM Prairie Wed 04:30p 9241 Understanding Linux Memory Management Wed 04:30p 9244 Linux for Beginners Hands-On Lab - Part 3 of 3 Wed 06:00p 9269 Scalability of the Linux Kernel 2.6 on zSeries Wed 06:00p 9271 Lab: How to Make a Webserver Highly Available with Tivoli Thu 08:00a 9121 Performance Choices for Linux and Other VM Guests Thu 08:00a 9123 TRACK for z/VM - What's Happening in Your Virtual Machines? Thu 08:00a 9265 Enhancing Scalability of Linux on z/VM Using Execute-in-Place Thu 09:30a 9209 Using Oracle Products on Linux for IBM's zSeries Computing Env Thu 09:30a 9273 Exploration of Open Source Security Tools for z/Linux Server Env Thu 11:00a 9132 MPRoute Configuration for z/VM Thu 11:00a 9257 Linux on zSeries Journaling File Systems Thu 11:00a 9283 Red Hat Enterprise Linux for zSeries, S/390 - Extending Linux Thu 01:30p 9127 RACF/VM: Protecting Your z/VM System from Vandals Thu 01:30p 9266 Using Execute-in-Place Technology with SuSE Linux Enterprise Ser Thu 03:00p 9135 VM Performance Internals - Why It Works That Way Thu 03:00p 9259 SCSI IPL for IBM zSeries Servers Thu 04:30p 9143 Using z/VM in a SCSI Environment Thu 04:30p 9256 Linux for zSeries Ease of Use and Information Strategy Roundtbl Thu 06:00p 9103 z/VM TCP/
Re: appropriate value of "LOAD AVERAGE"
On Wed, 26 Jan 2005 09:36:03 -0600, Adam Thornton <[EMAIL PROTECTED]> wrote: > With or without timer ticks? Given the emphasis on "On Demand" it would be silly not to use the "on demand timer" :-) Sure, with the timer ticks disabled and after killing the daemons that request early wakeup constanly. Rob -- Rob van der Heij rvdheij @ gmail.com -- 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: appropriate value of "LOAD AVERAGE"
On Jan 26, 2005, at 6:24 AM, Rob van der Heij wrote: The load average does not help you a lot. What you really want to do is look at the z/VM monitoring and see that the virtual machine is indeed considered idle and drops from queue. When idle, my Linux server tends to use 6 mS of CPU time per minute. With or without timer ticks? 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: Awwww...come on, guys...help us out...
I would like to take this opportunity to ask SHARE attendees to please contribute a small portion of your time to help an organization that represents YOUR interests. I know, you're going "But SHARE is still a month away and I don't have time to worry about it right now!" Well, other people have donated their time and energy to plan the agenda and create the content, but they need your help to actually pull it all off. They cannot plan, present, attend sessions to get their own education, and chair all the sessions themselves. It just isn't possible. Volunteers are appreciated. While the on-site Conscription Service that I provide can be fun, too (for me, heh heh heh), it does have someembarrasingaspects to it. Martha will now count the hands. Chuckie (while ol' what's-his-name attempts to untie the...whoops! gotta run!) [note the correct use of 'postrophes] -- 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: Having 1 linux kernel
That's ok... Don't mind each linux guest having r/w to /usr/opt Just want 1 place to upgrade the kernel... If not might as well have 1u servers. Ralph -Original Message- From: Adam Thornton [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 26, 2005 9:34 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Having 1 linux kernel On Jan 26, 2005, at 8:39 AM, Noll, Ralph wrote: > > Is there any doc on setting up 1 linux kernel and all linux guests > booting from That 1 kernel... > > Right now I have 8 linux guests all with separate boot disks... > > Be nice to have just one.. > You can put the kernel in NSS and then everyone can IPL that shared segment, but that doesn't really get you around needing some per-machine unique r/w DASD. Although with a shared kernel in NSS and smart use of basevol/guestvol, you could probably get a system with minimal writeable DASD. http://www.vm.ibm.com/linux/linuxnss.html tells you how to do the NSS trick. Ignore the "64M is recommended" bit; I've done it successfully in 12M. Do it in the smallest size you're ever going to want to run with. 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 -- 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
Awwww...come on, guys...help us out...
OK, I'm not above begging, at least when it is for a good cause. Response to my request for session chairs for SHARE has been somewhat less than overwhelming. I know it is tough to choose when SHARE is still a month away. However, the Linux and VM Program is putting on a lot of really terrific sessions. So, whatever you choose, it will be a good one. It's easy to do and only requires 1 hour of your time...an hour you would be spending in that session anyway. So, please help us out and sign up to chair a session or two. The following is a list of the available sessions. Just send me a note (OFF LIST, PLEASE!) with the session numbers you want. It's that easy! If you have questions, let me know. Martha Day Time Sess Title --- -- --- Mon 09:30a 9100 z/VM Platform Update Mon 09:30a 9200 Linux and Open Souce: The View from IBM Mon 11:00a 9102 z/VM: The Very Basics Mon 11:00a 9202 Linux Platform Options - Selecting Linux on zSeries Mon 01:30p 9214 Virtualization in the Real World - zSeries Linux Customer Exp Mon 03:00p 9106 VM Performance Update Mon 03:00p 9112 z/VM TCP/IP Stack Configuration Mon 03:00p 9207 Directory Serving Solutions using OpenLDAP Mon 04:30p 9142 z/VM Device Support Overview Tue 08:00a 9113 The z/VM Control Program (CP), Part 1 - Useful Things to Know Tue 08:00a 9131 VM TCP/IP Routing Tue 08:00a 9255 Linux Debugging at the System Level Tue 09:30a 9107 Introduction to VM Hands-On Lab - Part 1 of 2 Tue 09:30a 9114 The z/VM Control Program (CP), Part 2 - Under the Covers Tue 09:30a 9115 VM Performance Introduction Tue 09:30a 9215 Penguins Board the Stagecoach for the Linux Frontier: A User Exp Tue 11:00a 9108 Introduction to VM Hands-On Lab - Part 2 of 2 Tue 11:00a 9128 Hardware Configuration Management for z/VM Tue 11:00a 9237 VM and Linux Performance Issues Tue 01:30p 9136 Automated Linux Guest Monitoring on z/VM using PROP Tue 01:30p 9227 Linux for S/390 Installation Hands-On Lab - Part 1 of 3 Tue 01:30p 9281 Replacing Windows Servers with Linux Tue 03:00p 9133 Configuring, Customizing and Modifying Your VM System w/o IPL Tue 03:00p 9228 Linux for S/390 Installation Hands-On Lab - Part 2 of 3 Tue 03:00p 9267 Networking with Linux on zSeries - Part 1 of 2 Tue 04:30p 9134 Dynamically Managing Hardware I/O Configuration Using VM Tue 04:30p 9229 Linux for S/390 Installation Hands-On Lab - Part 3 of 3 Tue 04:30p 9268 Networking with Linux on zSeries - Part 2 of 2 Tue 06:00p 9248 Help! My (Virtual) Penguin is Sick! Wed 08:00a 9205 Attack of the Linux Clones at Marist College Wed 09:30a 9118 Maintaining z/VM by Using and Understanding VMSES/E Wed 09:30a 9224 Linux for S/390 System Management for the MF SysProg - 1 of 2 Wed 11:00a 9126 Performance Toolkit for VM Wed 11:00a 9225 Linux for S/390 System Management for the MF SysProg - 2 of 2 Wed 01:30p 9129 z/VM Security and Integrity Wed 01:30p 9238 Linux on z/VM Performance Measurement and Tuning Wed 01:30p 9242 Linux for Beginners Hands-On Lab - Part 1 of 3 Wed 03:00p 9148 Disaster Recovery, Backup & Restore for z/VM & Linux Wed 03:00p 9243 Linux for Beginners Hands-On Lab - Part 2 of 3 Wed 03:00p 9249 Linux for zSeries in Production : A User's Experience Wed 04:30p 9212 Managing a Penguin Farm on the VM Prairie Wed 04:30p 9241 Understanding Linux Memory Management Wed 04:30p 9244 Linux for Beginners Hands-On Lab - Part 3 of 3 Wed 06:00p 9269 Scalability of the Linux Kernel 2.6 on zSeries Wed 06:00p 9271 Lab: How to Make a Webserver Highly Available with Tivoli Thu 08:00a 9121 Performance Choices for Linux and Other VM Guests Thu 08:00a 9123 TRACK for z/VM - What's Happening in Your Virtual Machines? Thu 08:00a 9265 Enhancing Scalability of Linux on z/VM Using Execute-in-Place Thu 09:30a 9209 Using Oracle Products on Linux for IBM's zSeries Computing Env Thu 09:30a 9273 Exploration of Open Source Security Tools for z/Linux Server Env Thu 11:00a 9132 MPRoute Configuration for z/VM Thu 11:00a 9257 Linux on zSeries Journaling File Systems Thu 11:00a 9283 Red Hat Enterprise Linux for zSeries, S/390 - Extending Linux Thu 01:30p 9127 RACF/VM: Protecting Your z/VM System from Vandals Thu 01:30p 9266 Using Execute-in-Place Technology with SuSE Linux Enterprise Ser Thu 03:00p 9135 VM Performance Internals - Why It Works That Way Thu 03:00p 9259 SCSI IPL for IBM zSeries Servers Thu 04:30p 9143 Using z/VM in a SCSI Environment Thu 04:30p 9256 Linux for zSeries Ease of Use and Information Strategy Roundtbl Thu 06:00p 9103 z/VM TCP/IP Update Fri 08:00a 9146 Using VM:Operator to Monitor Linux Guests Fri 08:00a 9223 Jump-starting Solution Deployments on Linux for zSeries Fri 08:00a 9245 Linux InstallFest Hands-On Lab - Part 1 of 3 Fri 09:30a 9147 Systems Management Tools Fri 09:30a 9211 Linux Shell Scripting for the z/VM REXX User Fri 09:30a 9246 Linux InstallFest Hands-On Lab - Part 2 of 3 Fri 11:00a 9247 Linux InstallFest Hands-On Lab - Part 3 of 3
Re: Having 1 linux kernel
On Jan 26, 2005, at 8:39 AM, Noll, Ralph wrote: Is there any doc on setting up 1 linux kernel and all linux guests booting from That 1 kernel... Right now I have 8 linux guests all with separate boot disks... Be nice to have just one.. You can put the kernel in NSS and then everyone can IPL that shared segment, but that doesn't really get you around needing some per-machine unique r/w DASD. Although with a shared kernel in NSS and smart use of basevol/guestvol, you could probably get a system with minimal writeable DASD. http://www.vm.ibm.com/linux/linuxnss.html tells you how to do the NSS trick. Ignore the "64M is recommended" bit; I've done it successfully in 12M. Do it in the smallest size you're ever going to want to run with. 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: HTMLDOC install err. /s390-suse-linux/bin/ld: cannot find -lsocket
Hi, I inform you that now HTMLDOC works. The programmer uses only the htmldoc cmd in batch mode but I launchedthe same in VNC and the GUI works. HTMLDOC : htmldoc-1.8.24-source.tar Some prerequisite has been installed on SLES8 platform Linux/zVM : fltk-devel-1.1.0rc5-28 fltk-1.1.0rc5-28 gcc-c++-3.2.2-23 xdevel-4.2.0-119 XFree86-compat-libs-4.2.0-119 gcc33-libs-3.3.1-1 libpng-devel-1.2.4-25 zlib-devel-1.1.4-31 Theconfigure comand used : lxit000:/usr/local/src/htmldoc-1.8.24 #./config --prefix=/usr/local --disable-localpng Thanks toNeal and Rob for your help. Cordiali saluti / Best regards Marco Bosisio > Neal -Original Message- Contrary to what my wife tells me, I have a couple of ideas :-). Two options: 1. Have a look in configure and see if there are any --disable or --without options, you may be able to disable the part that requires png 2. Install the package that include libpng: libpng-devel-1.2.5-182.10 for example Neale > Rob -Original Message- He's also missing libz-devel and a socket library. I think he'd be much better off to pick up a src.rpm that has been made for SuSE systems and build that... at least trying to build will show what prereq it has for building. Rob Rob van der Heij rvdheij @ gmail.com > -Original Message- Hi, I'm installing the HTMLDOC ( http://www.htmldoc.org/index.php ) on Linux/zVM guest with SuSE SLES8 sp3. When I isuue the command ./configure --prefix=/usr/local I receive these errors as reported inconfig.log: ..other msg. configure:3958: checking for socket in -lsocket configure:3989: gcc -o conftestconftest.c -lsocket -lm >&5 /usr/lib/gcc-lib/s390-suse-linux/3.2.2/../../../../s390-suse-linux/bin/ld: cannot find -lsocket collect2: ld returned 1 exit status configure:3992: $? = 1 ..other msg. configure:4902: gcc -o conftestconftest.c -lz -ljpeg -lnsl -lm >&5 /usr/lib/gcc-lib/s390-suse-linux/3.2.2/../../../../s390-suse-linux/bin/ld: cannot find -lz collect2: ld returned 1 exit status configure:4905: $? = 1 ..other msg. configure:4975: gcc -o conftestconftest.c -lpng -ljpeg -lnsl -lm >&5 /usr/lib/gcc-lib/s390-suse-linux/3.2.2/../../../../s390-suse-linux/bin/ld: cannot find -lpng collect2: ld returned 1 exit status configure:4978: $? = 1 ...other msg #endif #ifdef __cplusplus #include configure: exit 0 The configurerc=0butif I continue with make it ends with error : ..other msg. Making all in zlib... Making all in png... Making all in htmldoc... Linking htmldoc... /usr/lib/gcc-lib/s390-suse-linux/3.2.2/../../../../s390-suse-linux/bin/ld: cannot find -lpng collect2: ld returned 1 exit status make[1]: *** [htmldoc] Error 1 Here are the sw levels : libgcc-3.2.2-23 gcc-c++-3.2.2-23 gcc-3.2.2-23 gcc33-libs-3.3.1-1 Linux SUSE SLES8 2.4.21 Do you have any idea ? Marco Bosisio -- 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
Having 1 linux kernel
Is there any doc on setting up 1 linux kernel and all linux guests booting from That 1 kernel... Right now I have 8 linux guests all with separate boot disks... Be nice to have just one.. Thanks Ralph -- 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: appropriate value of "LOAD AVERAGE"
On Wed, 26 Jan 2005 16:26:11 +0900, <[EMAIL PROTECTED]> wrote: > My client asked me what is the appropriate value of "LOAD AVERAGE" value > when the system is IDLE. (well i think he meant idle "NO MIDDLEWARE (and > some DBs) RUNNING") The answer is 0. :-) rmhtest3:~ # ps -ef | grep db2 | wc --lines 14 rmhtest3:~ # uptime 1:20pm up 10 days 17:33, 2 users, load average: 0.00, 0.00, 0.00 It should not make a difference whether the virtual machine has one or two virtual CPU's (only when you have multiple processes running that require in total more than an engine). The load average does not help you a lot. What you really want to do is look at the z/VM monitoring and see that the virtual machine is indeed considered idle and drops from queue. When idle, my Linux server tends to use 6 mS of CPU time per minute. -- Rob van der Heij rvdheij @ gmail.com -- 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
