Re: JBoss, Anyone?
My organization is absolutely not a WebSphere fan. They find it both too heavy (computing resources) and too complex (people resources). JBoss is both simpler and uses fewer resources. For Mark, these observations, while believed to be true for the mainframe, are based upon our experience on Intel and pSeries systems, and while I would like to say that within 12 months we will be having JBoss used on Linux on the mainframe, I can't say that plans are in place to make that happen in this timeframe. Harold Grovesteen Adam Thornton wrote: On Aug 28, 2007, at 2:45 PM, Tom Duerbusch wrote: A second question, other than a cost issue, is there any thing you would use Jboss for that wouldn't work just as well on Websphere? Do you consider resource consumption a cost issue ? Websphere tends to need more resources than JBoss, in my admittedly anecdotal experience. If cost extends to well, we can add some more storage to the box then that isn't a problem. 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
Adding dasd with Red Hat
We got our first Linux system up under a trial Red Hat, LPAR install with an IFL, no Z/VM. Looks good. We let the install autoconfig 4 3390-3's but we want to add more dasd. Make a logical volume group and partition a single 3390. The Red Hat manuals I've looked at don't seem to cover this and the cookbook doesn't either. What should I be reading? Thanks Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -- 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: Migrating Linux Dasd to a larger device
I need to move all of my Linux volumes from an Hitachi box (that will eventually be going out the door) to a new box. Most of the Linux dasd are 3390-3 with a couple of mod 1's used for swap vols. If you have VM, define minidisks on the new box, shut them down and image copy from the old disks to the new minidisks. As long as the virtual addresses remain the same in the virtual machines, Linux won't know or care. DDR will work, as will FDR image restore...8-) Before I forget, I was going to move the model 1's that are used as swap space to VM mini disks, and I was thinking about using a mod 9+ (aka mod 27 or larger) to hold the swap mdisks for several of the Linux systems. Does anyone know if this is a good, bad, or doesn't matter idea? Ditch real disks entirely and switch to VDISK. Get a copy of SWAPGEN from www.sinenomine.net and don't look back. -- 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: Migrating Linux Dasd to a larger device
Not something you can add to the plan now, but if the filesystems are defined using LVM (Logical Volume Manager), then you can add the new disks to the LVM volume group, then use pvmove and pvremove to migrate and remove the older volumes. In this way, you can migrate to the new disks (for the most part) without bring down the Linux image. You'll still have to bring it down and copy the /boot minidisk by hand, then bring the image back up, but it will decrease your downtime dramatically, if the image is large. We used this method to migrate just over half a terabyte from one DASD system to another, making the movement of the image take under a half hour, and used it on smaller images as well. The vageries of hardware being what they are, we're in the process of doing this all again right now, this time within the same box, to get into a single logical controller so that the z/OS folks can move toward GDPS without us. -- .~.Robert P. Nix Mayo Foundation /V\RO-OE-5-55200 First Street SW /( )\ 507-284-0844 Rochester, MN 55905 ^^-^^ - In theory, theory and practice are the same, but in practice, theory and practice are different. On 8/31/07 8:44 AM, David Boyes [EMAIL PROTECTED] wrote: I need to move all of my Linux volumes from an Hitachi box (that will eventually be going out the door) to a new box. Most of the Linux dasd are 3390-3 with a couple of mod 1's used for swap vols. If you have VM, define minidisks on the new box, shut them down and image copy from the old disks to the new minidisks. As long as the virtual addresses remain the same in the virtual machines, Linux won't know or care. DDR will work, as will FDR image restore...8-) Before I forget, I was going to move the model 1's that are used as swap space to VM mini disks, and I was thinking about using a mod 9+ (aka mod 27 or larger) to hold the swap mdisks for several of the Linux systems. Does anyone know if this is a good, bad, or doesn't matter idea? Ditch real disks entirely and switch to VDISK. Get a copy of SWAPGEN from www.sinenomine.net and don't look back. -- 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: SLES 10 cookbook
I have a different question about the cookbook. I installed SLES 10, no not SP1, that's downloading right now. When I got to the section about removing RPMs that were not needed I kept getting errors due to dependencies. Is that because I didn't have SP1 or did I do something else wrong? Thanks... Russ -- 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: SLES 10 cookbook
On Fri, Aug 31, 2007 at 11:22 AM, in message [EMAIL PROTECTED], Russ Burtnett [EMAIL PROTECTED] wrote: I have a different question about the cookbook. I installed SLES 10, no not SP1, that's downloading right now. When I got to the section about removing RPMs that were not needed I kept getting errors due to dependencies. Is that because I didn't have SP1 or did I do something else wrong? No, the book was written for SLES10 GA. Are the dependencies that are preventing removal also in the list of RPMs to be removed? If so, then just list them on the same rpm -e command. If not, then I'm not sure what would be wrong. 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
Re: Adding dasd with Red Hat
On Fri, Aug 31, 2007 at 8:10 AM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: We got our first Linux system up under a trial Red Hat, LPAR install with an IFL, no Z/VM. Looks good. We let the install autoconfig 4 3390-3's but we want to add more dasd. Make a logical volume group and partition a single 3390. The Red Hat manuals I've looked at don't seem to cover this and the cookbook doesn't either. It's been a while since I played with RHEL, so make sure you have good backups of stuff... From what I remember, you need to add the new DASD volume to the dasd= parameter in /etc/zipl.conf, then re-run mkinitrd and zipl, and then reboot. To be safe, you might want to make a copy of your current stanza in /etc/zipl.conf, give it a different name, and update that. You'll also need to update the [menu] section to point to it. When you reboot the system, it should show up in the list of kernels to select from. If you have already configured the DASD online to the LPAR, the system should have detected that, and you should be able to do a chccwdev -e 0.0. command to bring it online without rebooting. You'll still need to make the other changes, though, since that is only temporary until the next time you boot the system. 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
Re: Migrating Linux Dasd to a larger device
On Thu, Aug 30, 2007 at 8:19 PM, in message [EMAIL PROTECTED], Sue Sivets [EMAIL PROTECTED] wrote: I need to move all of my Linux volumes from an Hitachi box (that will eventually be going out the door) to a new box. Hi, Sue, I'll be better able to give you advice if I understand how your file systems are laid out currently. The output from df -h would be a start, as well as knowing if the disks are minidisks, or dedicated volumes. Just using a track-image copy, either via FDR or DDR, is usually a pain, because the partition table gets copied as-is, so the resulting system thinks the disk size is the same. One way around this is to get into fdasd, print out the partition information, and then zero it out, get out of fdasd, get back into fdasd (so that the system will try to re-read the disk information), and then create a new partition table, using the information from before. Kinda scary, at least to me. 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
Re: Adding dasd with Red Hat
It seems funny to me that Mark (who seems to bend over backwards to help everyone) replied to this email. It also seems to me that RH folks don't respond anywhere near as often as Mark does on this listserver. I hope that we here didn't hang our hat on the wrong horse when we chose RHRL. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, August 31, 2007 11:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd with Red Hat On Fri, Aug 31, 2007 at 8:10 AM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: We got our first Linux system up under a trial Red Hat, LPAR install with an IFL, no Z/VM. Looks good. We let the install autoconfig 4 3390-3's but we want to add more dasd. Make a logical volume group and partition a single 3390. The Red Hat manuals I've looked at don't seem to cover this and the cookbook doesn't either. It's been a while since I played with RHEL, so make sure you have good backups of stuff... From what I remember, you need to add the new DASD volume to the dasd= parameter in /etc/zipl.conf, then re-run mkinitrd and zipl, and then reboot. To be safe, you might want to make a copy of your current stanza in /etc/zipl.conf, give it a different name, and update that. You'll also need to update the [menu] section to point to it. When you reboot the system, it should show up in the list of kernels to select from. If you have already configured the DASD online to the LPAR, the system should have detected that, and you should be able to do a chccwdev -e 0.0. command to bring it online without rebooting. You'll still need to make the other changes, though, since that is only temporary until the next time you boot the system. 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 -- 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: Adding dasd with Red Hat
Thanks Mark. I also did find a section in the Red Hat manual on the topic. I missed it the first time. Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 11:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd with Red Hat On Fri, Aug 31, 2007 at 8:10 AM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: We got our first Linux system up under a trial Red Hat, LPAR install with an IFL, no Z/VM. Looks good. We let the install autoconfig 4 3390-3's but we want to add more dasd. Make a logical volume group and partition a single 3390. The Red Hat manuals I've looked at don't seem to cover this and the cookbook doesn't either. It's been a while since I played with RHEL, so make sure you have good backups of stuff... From what I remember, you need to add the new DASD volume to the dasd= parameter in /etc/zipl.conf, then re-run mkinitrd and zipl, and then reboot. To be safe, you might want to make a copy of your current stanza in /etc/zipl.conf, give it a different name, and update that. You'll also need to update the [menu] section to point to it. When you reboot the system, it should show up in the list of kernels to select from. If you have already configured the DASD online to the LPAR, the system should have detected that, and you should be able to do a chccwdev -e 0.0. command to bring it online without rebooting. You'll still need to make the other changes, though, since that is only temporary until the next time you boot the system. 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 -- 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: Missing OSA/2 Interfaces
Hi Mark, I read the man pages for mkinitrd, but I am not really sure what I am looking at, what options I need when, etc. I ran mkinitrd and let it default, and then ran zipl. Shutdown -r, and my network interfaces are gone again. The /sys/bus/ccwgroup/ directory doesn't even exist. So I guess I get to go back through Chapter 10 of the Device Drivers, Features and Commands manual to re-enable my network interfaces again. So, after the fact, I am pondering the -I option for mkinitrd. Should I have specified a -I eth0? And can I specify both eth0 and eth1? The Man page says -I iface. It doesn't appear to allow -I iface1,iface2. Rather confused this Friday morning, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 [EMAIL PROTECTED] Mark Post [EMAIL PROTECTED] 8/30/2007 8:13 PM -snip- You're welcome. If the new initrd doesn't fix things, I'll take a look at that too. :) 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 -- 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: Adding dasd with Red Hat
On Fri, Aug 31, 2007 at 12:23 PM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: Thanks Mark. I also did find a section in the Red Hat manual on the topic. I missed it the first time. So, just for my own info, did it match what I said to do? Or was I off somewhere? 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
Re: Adding dasd with Red Hat
I'm not sure we can criticize Red Hat for not responding on a community mailing list to their customers support issues. There are actual Red Hat lists and official support channels for that purpose. I'm guessing those Red Hatters that do occasionally pipe in here are doing so not because it's their job but rather as members of the community at large. With that said, kudos to Mark for being so attentive to this lists members. Hopefully he is getting paid to do so! ;) -Sam -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Kevin R Sent: Friday, August 31, 2007 12:15 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd with Red Hat It seems funny to me that Mark (who seems to bend over backwards to help everyone) replied to this email. It also seems to me that RH folks don't respond anywhere near as often as Mark does on this listserver. I hope that we here didn't hang our hat on the wrong horse when we chose RHRL. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, August 31, 2007 11:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd with Red Hat On Fri, Aug 31, 2007 at 8:10 AM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: We got our first Linux system up under a trial Red Hat, LPAR install with an IFL, no Z/VM. Looks good. We let the install autoconfig 4 3390-3's but we want to add more dasd. Make a logical volume group and partition a single 3390. The Red Hat manuals I've looked at don't seem to cover this and the cookbook doesn't either. It's been a while since I played with RHEL, so make sure you have good backups of stuff... From what I remember, you need to add the new DASD volume to the dasd= parameter in /etc/zipl.conf, then re-run mkinitrd and zipl, and then reboot. To be safe, you might want to make a copy of your current stanza in /etc/zipl.conf, give it a different name, and update that. You'll also need to update the [menu] section to point to it. When you reboot the system, it should show up in the list of kernels to select from. If you have already configured the DASD online to the LPAR, the system should have detected that, and you should be able to do a chccwdev -e 0.0. command to bring it online without rebooting. You'll still need to make the other changes, though, since that is only temporary until the next time you boot the system. 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 -- 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: Adding dasd with Red Hat
My intent was not to be critical, per se but observational. As well as praising Mark for being as active as he is. I still think that RH could maybe learn from this. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kielek, Samuel Sent: Friday, August 31, 2007 12:35 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd with Red Hat I'm not sure we can criticize Red Hat for not responding on a community mailing list to their customers support issues. There are actual Red Hat lists and official support channels for that purpose. I'm guessing those Red Hatters that do occasionally pipe in here are doing so not because it's their job but rather as members of the community at large. With that said, kudos to Mark for being so attentive to this lists members. Hopefully he is getting paid to do so! ;) -Sam -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Evans, Kevin R Sent: Friday, August 31, 2007 12:15 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd with Red Hat It seems funny to me that Mark (who seems to bend over backwards to help everyone) replied to this email. It also seems to me that RH folks don't respond anywhere near as often as Mark does on this listserver. I hope that we here didn't hang our hat on the wrong horse when we chose RHRL. Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, August 31, 2007 11:37 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd with Red Hat On Fri, Aug 31, 2007 at 8:10 AM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: We got our first Linux system up under a trial Red Hat, LPAR install with an IFL, no Z/VM. Looks good. We let the install autoconfig 4 3390-3's but we want to add more dasd. Make a logical volume group and partition a single 3390. The Red Hat manuals I've looked at don't seem to cover this and the cookbook doesn't either. It's been a while since I played with RHEL, so make sure you have good backups of stuff... From what I remember, you need to add the new DASD volume to the dasd= parameter in /etc/zipl.conf, then re-run mkinitrd and zipl, and then reboot. To be safe, you might want to make a copy of your current stanza in /etc/zipl.conf, give it a different name, and update that. You'll also need to update the [menu] section to point to it. When you reboot the system, it should show up in the list of kernels to select from. If you have already configured the DASD online to the LPAR, the system should have detected that, and you should be able to do a chccwdev -e 0.0. command to bring it online without rebooting. You'll still need to make the other changes, though, since that is only temporary until the next time you boot the system. 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 -- 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: Adding dasd with Red Hat
Very close. The dasd= parm is in /etc/modprobe.conf, not /etc/zipl.conf. Brought the dasd online in /sys/bus/ccw/drivers/dasd-eckd and this gave me the device name to use in the dasdfmt command. New dasd online and I'm reading about LVM. Haven't had this much fun since I learned the IBM firewall technologies a couple of years ago! Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 12:34 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd with Red Hat On Fri, Aug 31, 2007 at 12:23 PM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: Thanks Mark. I also did find a section in the Red Hat manual on the topic. I missed it the first time. So, just for my own info, did it match what I said to do? Or was I off somewhere? 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 -- 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: Adding dasd with Red Hat
I'm serious about this being fun. I enjoy learning/making new things even when they are sometimes frustrating like just finding out that the LVM command line interface isn't working on this new install I just did! Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 1:22 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd with Red Hat On Fri, Aug 31, 2007 at 12:47 PM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: Very close. The dasd= parm is in /etc/modprobe.conf, not /etc/zipl.conf. Rats. Ok, I'll try to remember that. -snip- New dasd online and I'm reading about LVM. Haven't had this much fun since I learned the IBM firewall technologies a couple of years ago! Not sure if you were being sarcastic or serious, but I've had more fun in the last seven years than I had for quite a while before that. :) 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 -- 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: Adding dasd with Red Hat
Haven't had this much fun since I learned the IBM firewall technologies a couple of years ago! Has anyone suggested you might need to get out a bit more...? 8-) (it's Friday. Have a laugh.) -- 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: Adding dasd with Red Hat
LOL Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: David Boyes [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 1:28 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Adding dasd with Red Hat Haven't had this much fun since I learned the IBM firewall technologies a couple of years ago! Has anyone suggested you might need to get out a bit more...? 8-) (it's Friday. Have a laugh.) -- 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: Adding dasd with Red Hat
On Fri, Aug 31, 2007 at 12:47 PM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: Very close. The dasd= parm is in /etc/modprobe.conf, not /etc/zipl.conf. Rats. Ok, I'll try to remember that. -snip- New dasd online and I'm reading about LVM. Haven't had this much fun since I learned the IBM firewall technologies a couple of years ago! Not sure if you were being sarcastic or serious, but I've had more fun in the last seven years than I had for quite a while before that. :) 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
Re: LVM CLI, was: Adding dasd with Red Hat
On Fri, Aug 31, 2007 at 1:25 PM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: I'm serious about this being fun. I enjoy learning/making new things even when they are sometimes frustrating like just finding out that the LVM command line interface isn't working on this new install I just did! Oh? Not working in what way? I don't think I've run into that problem with LVM. 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
Re: LVM CLI, was: Adding dasd with Red Hat
None of the LVM commands are found: lvscan bash: lvscan: command not found pvscan bash: pvscan: command not found Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 1:33 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM CLI, was: Adding dasd with Red Hat On Fri, Aug 31, 2007 at 1:25 PM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: I'm serious about this being fun. I enjoy learning/making new things even when they are sometimes frustrating like just finding out that the LVM command line interface isn't working on this new install I just did! Oh? Not working in what way? I don't think I've run into that problem with LVM. 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 -- 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: LVM CLI, was: Adding dasd with Red Hat
On Fri, Aug 31, 2007 at 1:35 PM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: None of the LVM commands are found: lvscan bash: lvscan: command not found pvscan bash: pvscan: command not found Did you issue those commands as root, or some other user? They should be in /usr/sbin or /sbin, assuming you have the lvm2 RPM installed. # rpm -qlp lvm2-2.02.12-7.el5.s390x.rpm | grep bin/[lp]vscan /sbin/pvscan /usr/sbin/lvscan /usr/sbin/pvscan 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
Re: LVM CLI, was: Adding dasd with Red Hat
That explains it. They are in /usr/sbin but /usr/sbin is not in my $PATH. If I cd to /usr/sbin and type ./lvscan it works as expected. I'm running as root for this stuff. Looks like I need to update profile Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 1:41 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM CLI, was: Adding dasd with Red Hat On Fri, Aug 31, 2007 at 1:35 PM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: None of the LVM commands are found: lvscan bash: lvscan: command not found pvscan bash: pvscan: command not found Did you issue those commands as root, or some other user? They should be in /usr/sbin or /sbin, assuming you have the lvm2 RPM installed. # rpm -qlp lvm2-2.02.12-7.el5.s390x.rpm | grep bin/[lp]vscan /sbin/pvscan /usr/sbin/lvscan /usr/sbin/pvscan 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 -- 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: LVM CLI, was: Adding dasd with Red Hat
I found my problem. I su'ed to root with 'su root' instead of 'su - root' Bobby Bauer Center for Information Technology National Institutes of Health Bethesda, MD 20892-5628 301-594-7474 -Original Message- From: Mark Post [mailto:[EMAIL PROTECTED] Sent: Friday, August 31, 2007 1:41 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: LVM CLI, was: Adding dasd with Red Hat On Fri, Aug 31, 2007 at 1:35 PM, in message [EMAIL PROTECTED], Bauer, Bobby (NIH/CIT) [E] [EMAIL PROTECTED] wrote: None of the LVM commands are found: lvscan bash: lvscan: command not found pvscan bash: pvscan: command not found Did you issue those commands as root, or some other user? They should be in /usr/sbin or /sbin, assuming you have the lvm2 RPM installed. # rpm -qlp lvm2-2.02.12-7.el5.s390x.rpm | grep bin/[lp]vscan /sbin/pvscan /usr/sbin/lvscan /usr/sbin/pvscan 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 -- 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: Missing OSA/2 Interfaces
On Fri, Aug 31, 2007 at 12:25 PM, in message [EMAIL PROTECTED], David Stuart [EMAIL PROTECTED] wrote: Hi Mark, I read the man pages for mkinitrd, but I am not really sure what I am looking at, what options I need when, etc. I ran mkinitrd and let it default, and then ran zipl. Shutdown -r, and my network interfaces are gone again. Dave, Send me your initrd in an off-list email. I'll see if I can figure out what needs to be done. Mark -- 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: SLES 10 cookbook
If you are reading the: z/VM and Linux on IBM System z The Virtualization Cookbook When you install SLES10, at the software point of configuring your system: select patterns and uncheck all boxes except for server base and 32 bit runtime like: Patterns: Select Server Base Select 32 bit runtime Unselect all others (changes 150 from 2,203,096K to 1,007,840K) And then add in anything else you might need. It gives you a good base server system while only using about 1GB of disk space. Tom Duerbusch THD Consulting Mark Post [EMAIL PROTECTED] 8/31/2007 10:27 AM On Fri, Aug 31, 2007 at 11:22 AM, in message [EMAIL PROTECTED], Russ Burtnett [EMAIL PROTECTED] wrote: I have a different question about the cookbook. I installed SLES 10, no not SP1, that's downloading right now. When I got to the section about removing RPMs that were not needed I kept getting errors due to dependencies. Is that because I didn't have SP1 or did I do something else wrong? No, the book was written for SLES10 GA. Are the dependencies that are preventing removal also in the list of RPMs to be removed? If so, then just list them on the same rpm -e command. If not, then I'm not sure what would be wrong. 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 -- 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: Missing OSA/2 Interfaces
Hi Mark, I've got one network interface up and running. The other one gave a Detection of LCS card failed rc = -5 error. But I can live with one right now. Where do I find initrd? A locate shows one in /boot, but it is a link to the executable, and one in /dev. But I am unable to view the contents of /dev/initrd to determine if that's the one I should be sending you. All other occurrences of initrd, as shown by locate, all appear to be source, or man pages, etc. Thanks, Dave Dave Stuart Prin. Info. Systems Support Analyst County of Ventura, CA 805-662-6731 [EMAIL PROTECTED] Mark Post [EMAIL PROTECTED] 8/31/2007 10:57 AM On Fri, Aug 31, 2007 at 12:25 PM, in message [EMAIL PROTECTED], David Stuart [EMAIL PROTECTED] wrote: Hi Mark, I read the man pages for mkinitrd, but I am not really sure what I am looking at, what options I need when, etc. I ran mkinitrd and let it default, and then ran zipl. Shutdown -r, and my network interfaces are gone again. Dave, Send me your initrd in an off-list email. I'll see if I can figure out what needs to be done. Mark -- 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: Missing OSA/2 Interfaces
On Fri, Aug 31, 2007 at 4:32 PM, in message [EMAIL PROTECTED], David Stuart [EMAIL PROTECTED] wrote: -snip- Where do I find initrd? A locate shows one in /boot, but it is a link to the executable, and one in /dev. But I am unable to view the contents of /dev/initrd to determine if that's the one I should be sending you. All other occurrences of initrd, as shown by locate, all appear to be source, or man pages, etc. It would be the one in /boot. It will have a name similar to /boot/initrd-2.6.5-7.286-s390x and should be a little less than 2MB in size. It's not an executable, it's a compressed image of an ext2 file system that gets loaded into real storage during the boot process. Mark -- 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: Adding dasd with Red Hat
Evans, Kevin R wrote: It seems funny to me that Mark (who seems to bend over backwards to help everyone) replied to this email. It also seems to me that RH folks don't respond anywhere near as often as Mark does on this listserver. I hope that we here didn't hang our hat on the wrong horse when we chose RHRL. Mark has been on this list a very long time, long before he joined Novell. He's been helping folk all that time. It might be on his job description, but probably not, he's here because he likes helping. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Please do not reply off-list -- 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
