Re: CentOS on z/VM
I have an older 4.3 version of Centos running here on z/VM 6.1. I don't think Centos has been very good about keeping the s390x architecture up with their latest releases, probably due to low demand. DJ On 11/30/2011 08:43 AM, Cameron Seay wrote: > Is anyone using CentOS on z/VM, and if so what version works? > > -- > Cameron Seay, Ph.D. > Electronics, Computer and Information Technology > School of Technology > NC A & T State University > Greensboro, NC > 336 334 7717 x2251 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: CentOS on z/VM
We use 4.7 and it works quite well. On 11/30/11 10:19 AM, "Dave Jones" wrote: > I have an older 4.3 version of Centos running here on z/VM 6.1. I don't > think Centos has been very good about keeping the s390x architecture up > with their latest releases, probably due to low demand. > > DJ > > On 11/30/2011 08:43 AM, Cameron Seay wrote: >> Is anyone using CentOS on z/VM, and if so what version works? >> >> -- >> Cameron Seay, Ph.D. >> Electronics, Computer and Information Technology >> School of Technology >> NC A & T State University >> Greensboro, NC >> 336 334 7717 x2251 >> >> -- >> For LINUX-390 subscribe / signoff / archive access instructions, >> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or >> visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> -- >> For more information on Linux on System z, visit >> http://wiki.linuxvm.org/ >> > > -- > Dave Jones > V/Soft Software > www.vsoft-software.com > Houston, TX > 281.578.7544 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: CentOS 4.7 on zSeries
Yes, that was the trick. THANKS! Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Brad Hinson Sent: Friday, December 18, 2009 3:04 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS 4.7 on zSeries Frank M. Ramaekers wrote: > No, I want two: eth0 - Real OSA-X (out to the real world) > eth1 - VSWITCH (internal to the zSeries) > > I went ahead and added my own ifcfg-eth1 (hoping that would help). > > # IBM QETH > DEVICE=eth1 > ARP=no > BOOTPROTO=static > BROADCAST=192.168.199.255 > IPADDR=192.168.199.40 > MTU=4096 > NETMASK=255.255.255.0 > NETTYPE=qeth > NETWORK=192.168.199.0 > ONBOOT=yes > PORTNAME=FOOBAR > SUBCHANNELS=0.0.0700,0.0.0701,0.0.0702 > TYPE=Ethernet > Is eth1 not coming up automatically? If not, make sure you have this line in /etc/modprobe.conf: alias eth1 qeth > Frank M. Ramaekers Jr. > Systems Programmer MCP, MCP+I, MCSE & RHCE > American Income Life Insurance Co. Phone: (254)761-6649 > 1200 Wooded Acres Dr.Fax: (254)741-5777 > Waco, Texas 76710 > > > > > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > Brad Hinson > Sent: Friday, December 18, 2009 2:28 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: CentOS 4.7 on zSeries > > Frank M. Ramaekers wrote: >> 1) see below... >> CP Q NIC DET >> Adapter 0700.P00 Type: QDIO Name: UNASSIGNED Devices: 3 >> MAC: 02-00-00-00-00-06 VSWITCH: SYSTEM VSWTMK00 >> RX Packets: 0 Discarded: 0 Errors: 0 >> TX Packets: 0 Discarded: 0 Errors: 0 >> RX Bytes: 0TX Bytes: 0 >> Unassigned Devices: >> Device: 0700 Unit: 000 Role: Unassigned >> Device: 0701 Unit: 001 Role: Unassigned >> Device: 0702 Unit: 002 Role: Unassigned >> Currently, I IPL CMS in order to perform the 'COUPLE' command (which >> doesn't fail). I have performed the SET GRANT. I see nothing in > the >> dmesg (except for the eth0): >> qeth: Device 0.0.0600/0.0.0601/0.0.0602 is a OSD Express card (level: >> 0892) >> with link type OSD_1000 (portname: FOOBAR) >> divert: allocating divert_blk for eth0 >> qeth: Hardware IP fragmentation not supported on eth0 >> qeth: VLAN enabled >> qeth: Multicast enabled >> qeth: IPV6 enabled >> qeth: Broadcast enabled >> qeth: Using SW checksumming on eth0. >> qeth: Outbound TSO enabled >> ip_tables: (C) 2000-2002 Netfilter core team >> eth0: no IPv6 routers present >> (The real OSA-X is at 0600-0602 and the VSWITCH is 0700-0702) > > This indicates eth0 is 600-602, the real OSA. If you want eth0 to be > the NIC, set SUBCHANNES=0.0.0700,0.0.0701,0.0.0702 in > /etc/sysconfig/network-scripts/ifcfg-eth0. If that doesn't help, the > output of 'q vswitch VSWTMK00' and > /etc/sysconfig/network-scripts/ifcfg-eth0 may help. > > -Brad > >> # vmcp q v osa >> OSA 0600 ON OSA 0F90 SUBCHANNEL = >> 0600 DEVTYPE OSA CHPID 01 OSD >> 0600 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE >> OSA 0601 ON OSA 0F91 SUBCHANNEL = 0001 >> 0601 DEVTYPE OSA CHPID 01 OSD >> 0601 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE >> OSA 0602 ON OSA 0F92 SUBCHANNEL = 0002 >> 0602 DEVTYPE OSA CHPID 01 OSD >> 0602 QDIO ACTIVE QIOASSIST ACTIVE >> 0602 >> 0602 INP + 01 IOCNT = 00136721 ADP = 014 PROG = 000 UNAVAIL = > 114 >> 0602 BYTES = 01359600 >> 0602 OUT + 01 IOCNT = ADP = 000 PROG = 000 UNAVAIL = > 128 >> 0602 BYTES = >> 0602 OUT + 02 IOCNT = ADP = 000 PROG = 000 UNAVAIL = > 128 >> 0602 BYTES = >> 0602 OUT - 03 IOCNT = 1377 ADP = 001 PROG = 127 UNAVAIL = > 000 >> 0602 BYTES = 0004ADC0 >> 0602 OUT + 04 IOCNT = ADP = 000 PROG = 000 UNAVAIL = > 128 >> 0602 BYTES = >> OSA 0700 ON NIC 0700 UNIT 000 SUBCHANNEL = 0003 >> 0700 DEVTYPE OSA CHPID 02 OSD >> 0700 MAC 02-00-00-00-00-06 CURRENT >> 0700 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE >> OSA 0701 ON NIC 0700 UNIT 001 SUBCHANNEL = 0004 >&
Re: CentOS 4.7 on zSeries
Frank M. Ramaekers wrote: No, I want two: eth0 - Real OSA-X (out to the real world) eth1 - VSWITCH (internal to the zSeries) I went ahead and added my own ifcfg-eth1 (hoping that would help). # IBM QETH DEVICE=eth1 ARP=no BOOTPROTO=static BROADCAST=192.168.199.255 IPADDR=192.168.199.40 MTU=4096 NETMASK=255.255.255.0 NETTYPE=qeth NETWORK=192.168.199.0 ONBOOT=yes PORTNAME=FOOBAR SUBCHANNELS=0.0.0700,0.0.0701,0.0.0702 TYPE=Ethernet Is eth1 not coming up automatically? If not, make sure you have this line in /etc/modprobe.conf: alias eth1 qeth Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Brad Hinson Sent: Friday, December 18, 2009 2:28 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS 4.7 on zSeries Frank M. Ramaekers wrote: 1) see below... CP Q NIC DET Adapter 0700.P00 Type: QDIO Name: UNASSIGNED Devices: 3 MAC: 02-00-00-00-00-06 VSWITCH: SYSTEM VSWTMK00 RX Packets: 0 Discarded: 0 Errors: 0 TX Packets: 0 Discarded: 0 Errors: 0 RX Bytes: 0TX Bytes: 0 Unassigned Devices: Device: 0700 Unit: 000 Role: Unassigned Device: 0701 Unit: 001 Role: Unassigned Device: 0702 Unit: 002 Role: Unassigned Currently, I IPL CMS in order to perform the 'COUPLE' command (which doesn't fail). I have performed the SET GRANT. I see nothing in the dmesg (except for the eth0): qeth: Device 0.0.0600/0.0.0601/0.0.0602 is a OSD Express card (level: 0892) with link type OSD_1000 (portname: FOOBAR) divert: allocating divert_blk for eth0 qeth: Hardware IP fragmentation not supported on eth0 qeth: VLAN enabled qeth: Multicast enabled qeth: IPV6 enabled qeth: Broadcast enabled qeth: Using SW checksumming on eth0. qeth: Outbound TSO enabled ip_tables: (C) 2000-2002 Netfilter core team eth0: no IPv6 routers present (The real OSA-X is at 0600-0602 and the VSWITCH is 0700-0702) This indicates eth0 is 600-602, the real OSA. If you want eth0 to be the NIC, set SUBCHANNES=0.0.0700,0.0.0701,0.0.0702 in /etc/sysconfig/network-scripts/ifcfg-eth0. If that doesn't help, the output of 'q vswitch VSWTMK00' and /etc/sysconfig/network-scripts/ifcfg-eth0 may help. -Brad # vmcp q v osa OSA 0600 ON OSA 0F90 SUBCHANNEL = 0600 DEVTYPE OSA CHPID 01 OSD 0600 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0601 ON OSA 0F91 SUBCHANNEL = 0001 0601 DEVTYPE OSA CHPID 01 OSD 0601 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0602 ON OSA 0F92 SUBCHANNEL = 0002 0602 DEVTYPE OSA CHPID 01 OSD 0602 QDIO ACTIVE QIOASSIST ACTIVE 0602 0602 INP + 01 IOCNT = 00136721 ADP = 014 PROG = 000 UNAVAIL = 114 0602 BYTES = 01359600 0602 OUT + 01 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 0602 BYTES = 0602 OUT + 02 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 0602 BYTES = 0602 OUT - 03 IOCNT = 1377 ADP = 001 PROG = 127 UNAVAIL = 000 0602 BYTES = 0004ADC0 0602 OUT + 04 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 0602 BYTES = OSA 0700 ON NIC 0700 UNIT 000 SUBCHANNEL = 0003 0700 DEVTYPE OSA CHPID 02 OSD 0700 MAC 02-00-00-00-00-06 CURRENT 0700 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0701 ON NIC 0700 UNIT 001 SUBCHANNEL = 0004 0701 DEVTYPE OSA CHPID 02 OSD 0701 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0702 ON NIC 0700 UNIT 002 SUBCHANNEL = 0005 0702 DEVTYPE OSA CHPID 02 OSD 0702 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE 2) Okay: modprobe vmcp [r...@vmlnx000 ~]# vmcp q t TIME IS 10:28:38 CST FRIDAY 12/18/09 CONNECT= 27:04:50 VIRTCPU= 014:03.64 TOTCPU= 014:28.42 Does the monprobe have to run each time the Linux system is booted? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mauro Souza Sent: Friday, December 18, 2009 9:50 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS 4.7 on zSeries 1 - When you IPL your Linux, there could be some message indicating why your vswitch isn't working. The most common mistake is forgetting to give the guest authorization to couple to the vswitch. 2 - To use vmcp, the module vmcp must be loaded. Issue a "modprobe vmcp" before.
Re: CentOS 4.7 on zSeries
No, I want two: eth0 - Real OSA-X (out to the real world) eth1 - VSWITCH (internal to the zSeries) I went ahead and added my own ifcfg-eth1 (hoping that would help). # IBM QETH DEVICE=eth1 ARP=no BOOTPROTO=static BROADCAST=192.168.199.255 IPADDR=192.168.199.40 MTU=4096 NETMASK=255.255.255.0 NETTYPE=qeth NETWORK=192.168.199.0 ONBOOT=yes PORTNAME=FOOBAR SUBCHANNELS=0.0.0700,0.0.0701,0.0.0702 TYPE=Ethernet Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Brad Hinson Sent: Friday, December 18, 2009 2:28 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS 4.7 on zSeries Frank M. Ramaekers wrote: > 1) see below... > CP Q NIC DET > Adapter 0700.P00 Type: QDIO Name: UNASSIGNED Devices: 3 > MAC: 02-00-00-00-00-06 VSWITCH: SYSTEM VSWTMK00 > RX Packets: 0 Discarded: 0 Errors: 0 > TX Packets: 0 Discarded: 0 Errors: 0 > RX Bytes: 0TX Bytes: 0 > Unassigned Devices: > Device: 0700 Unit: 000 Role: Unassigned > Device: 0701 Unit: 001 Role: Unassigned > Device: 0702 Unit: 002 Role: Unassigned > Currently, I IPL CMS in order to perform the 'COUPLE' command (which > doesn't fail). I have performed the SET GRANT. I see nothing in the > dmesg (except for the eth0): > qeth: Device 0.0.0600/0.0.0601/0.0.0602 is a OSD Express card (level: > 0892) > with link type OSD_1000 (portname: FOOBAR) > divert: allocating divert_blk for eth0 > qeth: Hardware IP fragmentation not supported on eth0 > qeth: VLAN enabled > qeth: Multicast enabled > qeth: IPV6 enabled > qeth: Broadcast enabled > qeth: Using SW checksumming on eth0. > qeth: Outbound TSO enabled > ip_tables: (C) 2000-2002 Netfilter core team > eth0: no IPv6 routers present > (The real OSA-X is at 0600-0602 and the VSWITCH is 0700-0702) This indicates eth0 is 600-602, the real OSA. If you want eth0 to be the NIC, set SUBCHANNES=0.0.0700,0.0.0701,0.0.0702 in /etc/sysconfig/network-scripts/ifcfg-eth0. If that doesn't help, the output of 'q vswitch VSWTMK00' and /etc/sysconfig/network-scripts/ifcfg-eth0 may help. -Brad > # vmcp q v osa > OSA 0600 ON OSA 0F90 SUBCHANNEL = > 0600 DEVTYPE OSA CHPID 01 OSD > 0600 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE > OSA 0601 ON OSA 0F91 SUBCHANNEL = 0001 > 0601 DEVTYPE OSA CHPID 01 OSD > 0601 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE > OSA 0602 ON OSA 0F92 SUBCHANNEL = 0002 > 0602 DEVTYPE OSA CHPID 01 OSD > 0602 QDIO ACTIVE QIOASSIST ACTIVE > 0602 > 0602 INP + 01 IOCNT = 00136721 ADP = 014 PROG = 000 UNAVAIL = 114 > 0602 BYTES = 01359600 > 0602 OUT + 01 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 > 0602 BYTES = > 0602 OUT + 02 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 > 0602 BYTES = > 0602 OUT - 03 IOCNT = 1377 ADP = 001 PROG = 127 UNAVAIL = 000 > 0602 BYTES = 0004ADC0 > 0602 OUT + 04 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 > 0602 BYTES = > OSA 0700 ON NIC 0700 UNIT 000 SUBCHANNEL = 0003 > 0700 DEVTYPE OSA CHPID 02 OSD > 0700 MAC 02-00-00-00-00-06 CURRENT > 0700 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE > OSA 0701 ON NIC 0700 UNIT 001 SUBCHANNEL = 0004 > 0701 DEVTYPE OSA CHPID 02 OSD > 0701 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE > OSA 0702 ON NIC 0700 UNIT 002 SUBCHANNEL = 0005 > 0702 DEVTYPE OSA CHPID 02 OSD > 0702 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE > > 2)Okay: > modprobe vmcp > [r...@vmlnx000 ~]# vmcp q t > TIME IS 10:28:38 CST FRIDAY 12/18/09 > CONNECT= 27:04:50 VIRTCPU= 014:03.64 TOTCPU= 014:28.42 > > Does the monprobe have to run each time the Linux system is booted? > > Frank M. Ramaekers Jr. > Systems Programmer MCP, MCP+I, MCSE & RHCE > American Income Life Insurance Co. Phone: (254)761-6649 > 1200 Wooded Acres Dr.Fax: (254)741-5777 > Waco, Texas 76710 > > > > > > -Original Message- > From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of > Mauro Souza > Sent: Friday, December 18, 2009 9:50 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: CentOS 4.7 on zSeries > > 1 - When you IPL your Linux, t
Re: CentOS 4.7 on zSeries
Frank M. Ramaekers wrote: 1) see below... CP Q NIC DET Adapter 0700.P00 Type: QDIO Name: UNASSIGNED Devices: 3 MAC: 02-00-00-00-00-06 VSWITCH: SYSTEM VSWTMK00 RX Packets: 0 Discarded: 0 Errors: 0 TX Packets: 0 Discarded: 0 Errors: 0 RX Bytes: 0TX Bytes: 0 Unassigned Devices: Device: 0700 Unit: 000 Role: Unassigned Device: 0701 Unit: 001 Role: Unassigned Device: 0702 Unit: 002 Role: Unassigned Currently, I IPL CMS in order to perform the 'COUPLE' command (which doesn't fail). I have performed the SET GRANT. I see nothing in the dmesg (except for the eth0): qeth: Device 0.0.0600/0.0.0601/0.0.0602 is a OSD Express card (level: 0892) with link type OSD_1000 (portname: FOOBAR) divert: allocating divert_blk for eth0 qeth: Hardware IP fragmentation not supported on eth0 qeth: VLAN enabled qeth: Multicast enabled qeth: IPV6 enabled qeth: Broadcast enabled qeth: Using SW checksumming on eth0. qeth: Outbound TSO enabled ip_tables: (C) 2000-2002 Netfilter core team eth0: no IPv6 routers present (The real OSA-X is at 0600-0602 and the VSWITCH is 0700-0702) This indicates eth0 is 600-602, the real OSA. If you want eth0 to be the NIC, set SUBCHANNES=0.0.0700,0.0.0701,0.0.0702 in /etc/sysconfig/network-scripts/ifcfg-eth0. If that doesn't help, the output of 'q vswitch VSWTMK00' and /etc/sysconfig/network-scripts/ifcfg-eth0 may help. -Brad # vmcp q v osa OSA 0600 ON OSA 0F90 SUBCHANNEL = 0600 DEVTYPE OSA CHPID 01 OSD 0600 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0601 ON OSA 0F91 SUBCHANNEL = 0001 0601 DEVTYPE OSA CHPID 01 OSD 0601 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0602 ON OSA 0F92 SUBCHANNEL = 0002 0602 DEVTYPE OSA CHPID 01 OSD 0602 QDIO ACTIVE QIOASSIST ACTIVE 0602 0602 INP + 01 IOCNT = 00136721 ADP = 014 PROG = 000 UNAVAIL = 114 0602 BYTES = 01359600 0602 OUT + 01 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 0602 BYTES = 0602 OUT + 02 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 0602 BYTES = 0602 OUT - 03 IOCNT = 1377 ADP = 001 PROG = 127 UNAVAIL = 000 0602 BYTES = 0004ADC0 0602 OUT + 04 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 0602 BYTES = OSA 0700 ON NIC 0700 UNIT 000 SUBCHANNEL = 0003 0700 DEVTYPE OSA CHPID 02 OSD 0700 MAC 02-00-00-00-00-06 CURRENT 0700 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0701 ON NIC 0700 UNIT 001 SUBCHANNEL = 0004 0701 DEVTYPE OSA CHPID 02 OSD 0701 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0702 ON NIC 0700 UNIT 002 SUBCHANNEL = 0005 0702 DEVTYPE OSA CHPID 02 OSD 0702 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE 2) Okay: modprobe vmcp [r...@vmlnx000 ~]# vmcp q t TIME IS 10:28:38 CST FRIDAY 12/18/09 CONNECT= 27:04:50 VIRTCPU= 014:03.64 TOTCPU= 014:28.42 Does the monprobe have to run each time the Linux system is booted? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mauro Souza Sent: Friday, December 18, 2009 9:50 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS 4.7 on zSeries 1 - When you IPL your Linux, there could be some message indicating why your vswitch isn't working. The most common mistake is forgetting to give the guest authorization to couple to the vswitch. 2 - To use vmcp, the module vmcp must be loaded. Issue a "modprobe vmcp" before. Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Fri, Dec 18, 2009 at 1:42 PM, Frank M. Ramaekers wrote: I've just loaded CentOS 4.7 in a VM (z/VM 5.4) and am experiencing some problems: 1) I have a VSWITCH that I can't seem to get working (already have a eth0 with a real OSA-X) 2) The vmcp device seems to be missing: # vmcp q t Error: Could not open device /dev/vmcp: No such file or directory Thanks, Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this
Re: CentOS 4.7 on zSeries
>>> On 12/18/2009 at 2:15 PM, Richard Gasiorowski wrote: > Frank > > Does not sound like you have it http://linuxvm.org/Patches/index.html will > get it for you cpint which contains vmcp. No. That package contains the hcp command (and device driver). The vmcp module and command are included in the s390-tools package, which is installed by default. As was mentioned, he simply needed to do a modprobe for the module. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: CentOS 4.7 on zSeries
Frank Does not sound like you have it http://linuxvm.org/Patches/index.html will get it for you cpint which contains vmcp. also http://publib.boulder.ibm.com/infocenter/eserver/v1r2/index.jsp?topic=/diricinfo/vsd0_r_tbs_zvmctr_guest_assc.html explains what to do - good luck Richard (Gaz) Gasiorowski Global System z Linux /AO Mainframe Services Product Manager Americas RPE Portfolio Platform Services CSC 3170 Fairview Park Dr., Falls Church, VA 22042 845-889-8533|Work|845-392-7889 Cell|rgasi...@csc.com|www.csc.com This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. From: "Frank M. Ramaekers" To: LINUX-390@VM.MARIST.EDU Date: 12/18/2009 01:56 PM Subject: Re: CentOS 4.7 on zSeries Also: Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs -- 0.0.0600 0.0. 1732/01 1731/01 yes 80 80 FF 0100 0.0.0601 0.0.0001 1732/01 1731/01 yes 80 80 FF 0100 0.0.0602 0.0.0002 1732/01 1731/01 yes 80 80 FF 0100 0.0.0700 0.0.0003 1732/01 1731/01 80 80 FF 0200 0.0.0701 0.0.0004 1732/01 1731/01 80 80 FF 0200 0.0.0702 0.0.0005 1732/01 1731/01 80 80 FF 0200 0.0.0191 0.0.0006 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.0200 0.0.0007 3390/0A 3990/E9 yes F0 F0 FF A1B1C1D1 0.0.0201 0.0.0008 3390/0A 3990/E9 yes F0 F0 FF A1B1C1D1 0.0.0202 0.0.0009 3390/0A 3990/E9 yes F0 F0 FF A1B1C1D1 0.0.0203 0.0.000A 3390/0A 3990/E9 yes F0 F0 FF A1B1C1D1 0.0.0009 0.0.000B /00 3215/00 yes 80 80 FF 0.0.000C 0.0.000C /00 2540/00 80 80 FF 0.0.000D 0.0.000D /00 2540/00 80 80 FF 0.0.000E 0.0.000E /00 1403/00 80 80 FF 0.0.0190 0.0.000F 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.019E 0.0.0010 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.019D 0.0.0011 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.0402 0.0.0012 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.0401 0.0.0013 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.0405 0.0.0014 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.0120 0.0.0015 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Andrew Avramenko Sent: Friday, December 18, 2009 9:52 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS 4.7 on zSeries 1) check with q v nic if it is attached to vswitch if no, chech if you gave permissions (set vswitch NAME grant GUEST) 2) modprobe vmcp 2009/12/18 Frank M. Ramaekers : > I've just loaded CentOS 4.7 in a VM (z/VM 5.4) and am experiencing some > problems: > > 1) I have a VSWITCH that I can't seem to get working (already have > a eth0 with a real OSA-X) > > 2) The vmcp device seems to be missing: > # vmcp q t > Error: Could not open device /dev/vmcp: No such file or directory > > Thanks, > > > Frank M. Ramaekers Jr. > Systems Programmer MCP, MCP+I, MCSE & RHCE > American Income Life Insurance Co. Phone: (254)761-6649 > 1200 Wooded Acres Dr.Fax: (254)741-5777 > Waco, Texas 76710 > > > _ > This message contains information which is privileged and confidential and is solely for the use of the > intended recipient. If you are not the intended recipient, be aware that any review, disclosure, > copying, distribution, or use of the contents of this message is strictly prohibited. If you have > received this in error, please destroy it immediately and notify us at privacy...@ailife.com. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- With best regards, Andrew -- For LINUX-390 subscribe / signoff / archive access instructions, send
Re: CentOS 4.7 on zSeries
Also: Device Subchan. DevType CU Type Use PIM PAM POM CHPIDs -- 0.0.0600 0.0. 1732/01 1731/01 yes 80 80 FF 0100 0.0.0601 0.0.0001 1732/01 1731/01 yes 80 80 FF 0100 0.0.0602 0.0.0002 1732/01 1731/01 yes 80 80 FF 0100 0.0.0700 0.0.0003 1732/01 1731/01 80 80 FF 0200 0.0.0701 0.0.0004 1732/01 1731/01 80 80 FF 0200 0.0.0702 0.0.0005 1732/01 1731/01 80 80 FF 0200 0.0.0191 0.0.0006 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.0200 0.0.0007 3390/0A 3990/E9 yes F0 F0 FF A1B1C1D1 0.0.0201 0.0.0008 3390/0A 3990/E9 yes F0 F0 FF A1B1C1D1 0.0.0202 0.0.0009 3390/0A 3990/E9 yes F0 F0 FF A1B1C1D1 0.0.0203 0.0.000A 3390/0A 3990/E9 yes F0 F0 FF A1B1C1D1 0.0.0009 0.0.000B /00 3215/00 yes 80 80 FF 0.0.000C 0.0.000C /00 2540/00 80 80 FF 0.0.000D 0.0.000D /00 2540/00 80 80 FF 0.0.000E 0.0.000E /00 1403/00 80 80 FF 0.0.0190 0.0.000F 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.019E 0.0.0010 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.019D 0.0.0011 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.0402 0.0.0012 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.0401 0.0.0013 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.0405 0.0.0014 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 0.0.0120 0.0.0015 3390/0A 3990/E9 FF FF FF 2050A0B0 C0D02151 Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Andrew Avramenko Sent: Friday, December 18, 2009 9:52 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS 4.7 on zSeries 1) check with q v nic if it is attached to vswitch if no, chech if you gave permissions (set vswitch NAME grant GUEST) 2) modprobe vmcp 2009/12/18 Frank M. Ramaekers : > I've just loaded CentOS 4.7 in a VM (z/VM 5.4) and am experiencing some > problems: > > 1) I have a VSWITCH that I can't seem to get working (already have > a eth0 with a real OSA-X) > > 2) The vmcp device seems to be missing: > # vmcp q t > Error: Could not open device /dev/vmcp: No such file or directory > > Thanks, > > > Frank M. Ramaekers Jr. > Systems Programmer MCP, MCP+I, MCSE & RHCE > American Income Life Insurance Co. Phone: (254)761-6649 > 1200 Wooded Acres Dr. Fax: (254)741-5777 > Waco, Texas 76710 > > > _ > This message contains information which is privileged and confidential and is > solely for the use of the > intended recipient. If you are not the intended recipient, be aware that any > review, disclosure, > copying, distribution, or use of the contents of this message is strictly > prohibited. If you have > received this in error, please destroy it immediately and notify us at > privacy...@ailife.com. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- With best regards, Andrew -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: CentOS 4.7 on zSeries
1) ]# vmcp q v nic Adapter 0700.P00 Type: QDIO Name: UNASSIGNED Devices: 3 MAC: 02-00-00-00-00-06 VSWITCH: SYSTEM VSWTMK00 2) monprobe worked (does this have to be done after every boot?) Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Andrew Avramenko Sent: Friday, December 18, 2009 9:52 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS 4.7 on zSeries 1) check with q v nic if it is attached to vswitch if no, chech if you gave permissions (set vswitch NAME grant GUEST) 2) modprobe vmcp 2009/12/18 Frank M. Ramaekers : > I've just loaded CentOS 4.7 in a VM (z/VM 5.4) and am experiencing some > problems: > > 1) I have a VSWITCH that I can't seem to get working (already have > a eth0 with a real OSA-X) > > 2) The vmcp device seems to be missing: > # vmcp q t > Error: Could not open device /dev/vmcp: No such file or directory > > Thanks, > > > Frank M. Ramaekers Jr. > Systems Programmer MCP, MCP+I, MCSE & RHCE > American Income Life Insurance Co. Phone: (254)761-6649 > 1200 Wooded Acres Dr. Fax: (254)741-5777 > Waco, Texas 76710 > > > _ > This message contains information which is privileged and confidential and is > solely for the use of the > intended recipient. If you are not the intended recipient, be aware that any > review, disclosure, > copying, distribution, or use of the contents of this message is strictly > prohibited. If you have > received this in error, please destroy it immediately and notify us at > privacy...@ailife.com. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- With best regards, Andrew -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: CentOS 4.7 on zSeries
1) see below... CP Q NIC DET Adapter 0700.P00 Type: QDIO Name: UNASSIGNED Devices: 3 MAC: 02-00-00-00-00-06 VSWITCH: SYSTEM VSWTMK00 RX Packets: 0 Discarded: 0 Errors: 0 TX Packets: 0 Discarded: 0 Errors: 0 RX Bytes: 0TX Bytes: 0 Unassigned Devices: Device: 0700 Unit: 000 Role: Unassigned Device: 0701 Unit: 001 Role: Unassigned Device: 0702 Unit: 002 Role: Unassigned Currently, I IPL CMS in order to perform the 'COUPLE' command (which doesn't fail). I have performed the SET GRANT. I see nothing in the dmesg (except for the eth0): qeth: Device 0.0.0600/0.0.0601/0.0.0602 is a OSD Express card (level: 0892) with link type OSD_1000 (portname: FOOBAR) divert: allocating divert_blk for eth0 qeth: Hardware IP fragmentation not supported on eth0 qeth: VLAN enabled qeth: Multicast enabled qeth: IPV6 enabled qeth: Broadcast enabled qeth: Using SW checksumming on eth0. qeth: Outbound TSO enabled ip_tables: (C) 2000-2002 Netfilter core team eth0: no IPv6 routers present (The real OSA-X is at 0600-0602 and the VSWITCH is 0700-0702) # vmcp q v osa OSA 0600 ON OSA 0F90 SUBCHANNEL = 0600 DEVTYPE OSA CHPID 01 OSD 0600 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0601 ON OSA 0F91 SUBCHANNEL = 0001 0601 DEVTYPE OSA CHPID 01 OSD 0601 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0602 ON OSA 0F92 SUBCHANNEL = 0002 0602 DEVTYPE OSA CHPID 01 OSD 0602 QDIO ACTIVE QIOASSIST ACTIVE 0602 0602 INP + 01 IOCNT = 00136721 ADP = 014 PROG = 000 UNAVAIL = 114 0602 BYTES = 01359600 0602 OUT + 01 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 0602 BYTES = 0602 OUT + 02 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 0602 BYTES = 0602 OUT - 03 IOCNT = 1377 ADP = 001 PROG = 127 UNAVAIL = 000 0602 BYTES = 0004ADC0 0602 OUT + 04 IOCNT = ADP = 000 PROG = 000 UNAVAIL = 128 0602 BYTES = OSA 0700 ON NIC 0700 UNIT 000 SUBCHANNEL = 0003 0700 DEVTYPE OSA CHPID 02 OSD 0700 MAC 02-00-00-00-00-06 CURRENT 0700 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0701 ON NIC 0700 UNIT 001 SUBCHANNEL = 0004 0701 DEVTYPE OSA CHPID 02 OSD 0701 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE OSA 0702 ON NIC 0700 UNIT 002 SUBCHANNEL = 0005 0702 DEVTYPE OSA CHPID 02 OSD 0702 QDIO-ELIGIBLE QIOASSIST-ELIGIBLE 2) Okay: modprobe vmcp [r...@vmlnx000 ~]# vmcp q t TIME IS 10:28:38 CST FRIDAY 12/18/09 CONNECT= 27:04:50 VIRTCPU= 014:03.64 TOTCPU= 014:28.42 Does the monprobe have to run each time the Linux system is booted? Frank M. Ramaekers Jr. Systems Programmer MCP, MCP+I, MCSE & RHCE American Income Life Insurance Co. Phone: (254)761-6649 1200 Wooded Acres Dr.Fax: (254)741-5777 Waco, Texas 76710 -Original Message- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Mauro Souza Sent: Friday, December 18, 2009 9:50 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS 4.7 on zSeries 1 - When you IPL your Linux, there could be some message indicating why your vswitch isn't working. The most common mistake is forgetting to give the guest authorization to couple to the vswitch. 2 - To use vmcp, the module vmcp must be loaded. Issue a "modprobe vmcp" before. Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Fri, Dec 18, 2009 at 1:42 PM, Frank M. Ramaekers wrote: > I've just loaded CentOS 4.7 in a VM (z/VM 5.4) and am experiencing some > problems: > > 1) I have a VSWITCH that I can't seem to get working (already have > a eth0 with a real OSA-X) > > 2) The vmcp device seems to be missing: > # vmcp q t > Error: Could not open device /dev/vmcp: No such file or directory > > Thanks, > > > Frank M. Ramaekers Jr. > Systems Programmer MCP, MCP+I, MCSE & RHCE > American Income Life Insurance Co. Phone: (254)761-6649 > 1200 Wooded Acres Dr.Fax: (254)741-5777 > Waco, Texas 76710 > > > _ > This message contains information which is privileged and confidential and > is solely for the use of the > intended recipient. If you are not the intended recipient, be aware that > any review, disclosure, > copying, distribution, or use of the contents of this message is stric
Re: CentOS 4.7 on zSeries
1) check with q v nic if it is attached to vswitch if no, chech if you gave permissions (set vswitch NAME grant GUEST) 2) modprobe vmcp 2009/12/18 Frank M. Ramaekers : > I've just loaded CentOS 4.7 in a VM (z/VM 5.4) and am experiencing some > problems: > > 1) I have a VSWITCH that I can't seem to get working (already have > a eth0 with a real OSA-X) > > 2) The vmcp device seems to be missing: > # vmcp q t > Error: Could not open device /dev/vmcp: No such file or directory > > Thanks, > > > Frank M. Ramaekers Jr. > Systems Programmer MCP, MCP+I, MCSE & RHCE > American Income Life Insurance Co. Phone: (254)761-6649 > 1200 Wooded Acres Dr. Fax: (254)741-5777 > Waco, Texas 76710 > > > _ > This message contains information which is privileged and confidential and is > solely for the use of the > intended recipient. If you are not the intended recipient, be aware that any > review, disclosure, > copying, distribution, or use of the contents of this message is strictly > prohibited. If you have > received this in error, please destroy it immediately and notify us at > privacy...@ailife.com. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- With best regards, Andrew -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: CentOS 4.7 on zSeries
1 - When you IPL your Linux, there could be some message indicating why your vswitch isn't working. The most common mistake is forgetting to give the guest authorization to couple to the vswitch. 2 - To use vmcp, the module vmcp must be loaded. Issue a "modprobe vmcp" before. Mauro http://mauro.limeiratem.com - registered Linux User: 294521 Scripture is both history, and a love letter from God. On Fri, Dec 18, 2009 at 1:42 PM, Frank M. Ramaekers wrote: > I've just loaded CentOS 4.7 in a VM (z/VM 5.4) and am experiencing some > problems: > > 1) I have a VSWITCH that I can't seem to get working (already have > a eth0 with a real OSA-X) > > 2) The vmcp device seems to be missing: > # vmcp q t > Error: Could not open device /dev/vmcp: No such file or directory > > Thanks, > > > Frank M. Ramaekers Jr. > Systems Programmer MCP, MCP+I, MCSE & RHCE > American Income Life Insurance Co. Phone: (254)761-6649 > 1200 Wooded Acres Dr.Fax: (254)741-5777 > Waco, Texas 76710 > > > _ > This message contains information which is privileged and confidential and > is solely for the use of the > intended recipient. If you are not the intended recipient, be aware that > any review, disclosure, > copying, distribution, or use of the contents of this message is strictly > prohibited. If you have > received this in error, please destroy it immediately and notify us at > privacy...@ailife.com. > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: [CentOS-devel] slow Perl on CentOS 5
Notes to RHEL5 users. I'm sending this to the RHEL5 list because it affects RHEL5 users. The full discussion can be read from the archive for centos-devel at centos.org. RH has promised its fix in RHEL5U3. CentOS has it now, the remaining discussion is how it's distributed. If you need it now, use the CentOS5 rpm and/or lean on RH. Note to RHEL5 on Linux-390. The CentOS fixed rpm needs to be built for Zeds, but (probably) the CentOS src.rpm will build fine. Note to SLES10 users on linux-390 I don't have a clue whether this applies to you, it could. Code to test it can be found in the archive I mentioned above. Marcus Moeller wrote: Dear John. _I_ would prefer to pick it up automatically, without having to make special configuration changes or use unusual commandline arguments. I'm looking for someone to explain why it should not be so, and "binary compatibility" isn't it. Nor does the overview at www.centos.org explain why not. It's not only about binary compatibility (of course this patch might not break with it). It's more about dividing from upstream. That's not, afaics, a stated objective. There is a downside (prospective problems for users) in not fixing the problem for all C5 users. What disadvantage is there to CentOS supplying its fix through the regular updates repo? MM, like me, doesn't see a problem with binary compatibility. The fix is available and implemented and (to some extent) tested. Apparently, RH has promised to fix it properly at some point in the future and the RH fix will automatically supersede the C fix. As mentioned before RH will push out a fix sooner or later. Those systems that are affected (which is non of mine, at least) may be patched using testing or even fasttrack repo. As I've said before, I don't think most people would know, unless they run over the problem in their own code, and if they do encounter it and use Google as I did, the fix they are more likely to find is "build your own perl." I value compatibility with RH even though, in practice, it's probably not going to affect me directly - I'm unlikely to use commercial certified software - but I don't see a reason for retaining RH bugs just for compatibility. Note, my C5 system doesn't even have a definition of a testing or fasttrack repo. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot 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
Re: CentOS 4.4 kernel panic on boot s390x
> -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Mark Post > Sent: Tuesday, April 15, 2008 10:18 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: CentOS 4.4 kernel panic on boot s390x > > >>> On Tue, Apr 15, 2008 at 11:03 AM, in message > <[EMAIL PROTECTED]>, > "Kelly F. > Hickel" <[EMAIL PROTECTED]> wrote: > -snip- > > That explains something, although fdasd doesn't think there are > > partition tables either, I just tried again though, and I can still > do a > > "normal" load from DASD address D04D and it works right up to the > point > > where it panics after trying to activate the volume groups... > > Right. The script on the ram disk is trying to get the real root file > system ready, and when it can't the system dies. > > -snip- > > Vgscan fails: > > -/bin/sh-3.00# lvm > > lvm> vgscan > > Reading all physical volumes. This may take a while... > > No volume groups found > > lvm> > > I would say at this point that you are indeed out of luck. If pvscan > and vgscan aren't finding any traces of the metadata that should be > there, it's game over. Are these DASD volumes accessible from other > LPARs? If so, it's entirely possible that some overzealous storage > administrator reformatted them for you. > > > Mark Post OK Mark, thanks for the help. I was suspicious of this very thing, especially since we had recently brought up a new z/OS 1.8 LPAR and I suspected that they might have reused one of these "idle" addresses. I had people check and they told me that didn't happen. I'm having them check again, and if they say they aren't in use, I'm going to reload zlinux. I guess we'll find out pretty fast if they really are using them (when their data disappears)! Thanks again all, -Kelly -- 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: CentOS 4.4 kernel panic on boot s390x
>>> On Tue, Apr 15, 2008 at 11:03 AM, in message <[EMAIL PROTECTED]>, "Kelly F. Hickel" <[EMAIL PROTECTED]> wrote: -snip- > That explains something, although fdasd doesn't think there are > partition tables either, I just tried again though, and I can still do a > "normal" load from DASD address D04D and it works right up to the point > where it panics after trying to activate the volume groups... Right. The script on the ram disk is trying to get the real root file system ready, and when it can't the system dies. -snip- > Vgscan fails: > -/bin/sh-3.00# lvm > lvm> vgscan > Reading all physical volumes. This may take a while... > No volume groups found > lvm> I would say at this point that you are indeed out of luck. If pvscan and vgscan aren't finding any traces of the metadata that should be there, it's game over. Are these DASD volumes accessible from other LPARs? If so, it's entirely possible that some overzealous storage administrator reformatted them for you. 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: CentOS 4.4 kernel panic on boot s390x
> >>> On Tue, Apr 15, 2008 at 7:55 AM, in message > <[EMAIL PROTECTED]>, > "Kelly F. > Hickel" <[EMAIL PROTECTED]> wrote: > > Well, I guess that I'm out of luck. It says that there are no valid > > partition tables on any of my devices, I have no idea how that could > > have possibly happened, but I seem to have no choices left except to > > reinstall. > > If you used the fdisk command instead of the fdasd command, fdisk will > report that, since DASD volumes aren't set up in such a way that fdisk > will work on them. SCSI over FCP will, but not DASD. I suspect your > partition definitions are still there. That explains something, although fdasd doesn't think there are partition tables either, I just tried again though, and I can still do a "normal" load from DASD address D04D and it works right up to the point where it panics after trying to activate the volume groups... -/bin/sh-3.00# fdasd -p /dev/dasda reading volume label: Could not find VOL1 volume label. exiting... -/bin/sh-3.00# fdasd -p /dev/dasdb reading volume label: Could not find VOL1 volume label. exiting... -/bin/sh-3.00# fdasd -p /dev/dasdc reading volume label: Could not find VOL1 volume label. exiting... -/bin/sh-3.00# fdasd -p /dev/dasdd reading volume label: Could not find VOL1 volume label. exiting... > > > I guess that I also don't really understand how it could be getting > far > > enough along in a normal boot to get the kernel loaded to the point > of > > activating the volume groups, if there aren't any partition tables. > > Because the system is still running off a ram disk at that point. > > > Am I missing something about lvm? Do I have to do some mdadm commands > to > > reassemble these devices into a working filesystem before I can do > > anything? I thought that they would have had to have valid partition > > tables before I could do that.. > > No, vgscan should do it for you, followed by vgchange -a y if things > are in working order. Vgscan fails: -/bin/sh-3.00# lvm lvm> vgscan Reading all physical volumes. This may take a while... No volume groups found lvm> > > > Mark Post Thanks, Kelly -- 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: CentOS 4.4 kernel panic on boot s390x
> -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Brad Hinson > Sent: Tuesday, April 15, 2008 8:52 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: CentOS 4.4 kernel panic on boot s390x > > I think that message may be misleading. If you're getting that far > into > the boot process, the partition tables may be there. Did you get to > the > point of entering the NFS/HTTP/FTP server and path and selecting > "Next"? > That's really as far as you need to go in the installer. The rest > should be done in a separate SSH session. > > >From that separate SSH session, do you see /usr/sbin/lvm? I've rebooted and gotten to the point of telling it to start VNC, then I ssh in again. /usr/sbin/lvm exists. Lvm lvscan/pvscan don't seem to find any volumes. -/bin/sh-3.00# lvm lvm> lvscan No volume groups found lvm> pvscan No matching physical volumes found lvm> fdisk seems to think that none of the devices have partition tables on them (I'd expect /dev/dasda or /dev/dasda1 to have one, since I can get through a normal boot up to the point of activating volume groups): Warning: invalid flag 0x of partition table 4 will be corrected by w(rite) Command (m for help): p Disk /dev/dasda: 2461 MB, 2461777920 bytes 15 heads, 12 sectors/track, 3339 cylinders Units = cylinders of 180 * 4096 = 737280 bytes Device Boot Start End Blocks Id System Command (m for help): Thanks, Kelly > > -Brad > > On Tue, 2008-04-15 at 06:55 -0500, Kelly F. Hickel wrote: > > Well, I guess that I'm out of luck. It says that there are no valid > > partition tables on any of my devices, I have no idea how that could > > have possibly happened, but I seem to have no choices left except to > > reinstall. > > > > I guess that I also don't really understand how it could be getting > far > > enough along in a normal boot to get the kernel loaded to the point > of > > activating the volume groups, if there aren't any partition tables. > > > > Am I missing something about lvm? Do I have to do some mdadm commands > to > > reassemble these devices into a working filesystem before I can do > > anything? I thought that they would have had to have valid partition > > tables before I could do that.. > > > > -- 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: CentOS 4.4 kernel panic on boot s390x
>>> On Tue, Apr 15, 2008 at 7:55 AM, in message <[EMAIL PROTECTED]>, "Kelly F. Hickel" <[EMAIL PROTECTED]> wrote: > Well, I guess that I'm out of luck. It says that there are no valid > partition tables on any of my devices, I have no idea how that could > have possibly happened, but I seem to have no choices left except to > reinstall. If you used the fdisk command instead of the fdasd command, fdisk will report that, since DASD volumes aren't set up in such a way that fdisk will work on them. SCSI over FCP will, but not DASD. I suspect your partition definitions are still there. > I guess that I also don't really understand how it could be getting far > enough along in a normal boot to get the kernel loaded to the point of > activating the volume groups, if there aren't any partition tables. Because the system is still running off a ram disk at that point. > Am I missing something about lvm? Do I have to do some mdadm commands to > reassemble these devices into a working filesystem before I can do > anything? I thought that they would have had to have valid partition > tables before I could do that.. No, vgscan should do it for you, followed by vgchange -a y if things are in working order. 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: CentOS 4.4 kernel panic on boot s390x
I think that message may be misleading. If you're getting that far into the boot process, the partition tables may be there. Did you get to the point of entering the NFS/HTTP/FTP server and path and selecting "Next"? That's really as far as you need to go in the installer. The rest should be done in a separate SSH session. >From that separate SSH session, do you see /usr/sbin/lvm? -Brad On Tue, 2008-04-15 at 06:55 -0500, Kelly F. Hickel wrote: > Well, I guess that I'm out of luck. It says that there are no valid > partition tables on any of my devices, I have no idea how that could > have possibly happened, but I seem to have no choices left except to > reinstall. > > I guess that I also don't really understand how it could be getting far > enough along in a normal boot to get the kernel loaded to the point of > activating the volume groups, if there aren't any partition tables. > > Am I missing something about lvm? Do I have to do some mdadm commands to > reassemble these devices into a working filesystem before I can do > anything? I thought that they would have had to have valid partition > tables before I could do that.. > > > -- > > Kelly F. Hickel > Senior Product Architect > MQSoftware, Inc. > 952-345-8677 Office > 952-345-8721 Fax > [EMAIL PROTECTED] > www.mqsoftware.com > SEE BUSINESS WORK > > > > -Original Message- > > From: Kelly F. Hickel > > Sent: Tuesday, April 15, 2008 6:14 AM > > To: LINUX-390@VM.MARIST.EDU > > Subject: RE: CentOS 4.4 kernel panic on boot s390x > > > > Brad, > > That sounds like a great tip, I'll give it a try. I hadn't gone > > past the initial "choose a language" screen, both because some of the > > google hits said that was as far as you needed to go, and because I > was > > afraid that if I gave it the location, it might destroy some of the > > data. I know it prompts before writing anything, but there are too > many > > things I don't know about Linux on s390x, so I'm more than a bit > > paranoid. > > > > Thanks, > > > > > > -- > > > > Kelly F. Hickel > > Senior Product Architect > > MQSoftware, Inc. > > 952-345-8677 Office > > 952-345-8721 Fax > > [EMAIL PROTECTED] > > www.mqsoftware.com > > SEE BUSINESS WORK > > > > > -Original Message- > > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf > Of > > > Brad Hinson > > > Sent: Monday, April 14, 2008 5:10 PM > > > To: LINUX-390@VM.MARIST.EDU > > > Subject: Re: CentOS 4.4 kernel panic on boot s390x > > > > > > Hi Kelly, > > > > > > You mentioned earlier that you're using the installer image. How > far > > > into the install are you going before SSH'ing in to troubleshoot? > If > > > you go past the point of entering the location of the stage 2 > > > environment (i.e. on the installation method screen, select > > > FTP/HTTP/NFS, enter the server and path, then select Next), the > > > installer will download or mount (depending on method) the stage 2 > > > image > > > containing the LVM tools. > > > > > > I'd recommend going through the install until the point where the > VNC > > > server is started and it asks you to connect. At that point, SSH in > > a > > > second time (or press to get a shell prompt). You should > see > > > that "/" is mounted from the stage 2 image (shown below as > > /dev/root), > > > and /usr/sbin/lvm will exist: > > > > > > -/bin/sh-3.00# mount | grep root > > > /dev/root on / type ext2 (rw) > > > > > > -/bin/sh-3.00# which lvm > > > /usr/sbin/lvm > > > > > > > > > -Brad > > > > > > On Mon, 2008-04-14 at 15:34 -0500, Kelly F. Hickel wrote: > > > > /usr only contains the lib64 directory. > > > > > > > > > > > > -- > > > > > > > > Kelly F. Hickel > > > > Senior Product Architect > > > > MQSoftware, Inc. > > > > 952-345-8677 Office > > > > 952-345-8721 Fax > > > > [EMAIL PROTECTED] > > > > www.mqsoftware.com > > > > SEE BUSINESS WORK > > > > > > > > > > > > > -Original Message- > > > > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > > Behalf > > > Of > > > > > Justin Payne > > > > > Sent: Monday, April 14, 200
Re: CentOS 4.4 kernel panic on boot s390x
Well, I guess that I'm out of luck. It says that there are no valid partition tables on any of my devices, I have no idea how that could have possibly happened, but I seem to have no choices left except to reinstall. I guess that I also don't really understand how it could be getting far enough along in a normal boot to get the kernel loaded to the point of activating the volume groups, if there aren't any partition tables. Am I missing something about lvm? Do I have to do some mdadm commands to reassemble these devices into a working filesystem before I can do anything? I thought that they would have had to have valid partition tables before I could do that.. -- Kelly F. Hickel Senior Product Architect MQSoftware, Inc. 952-345-8677 Office 952-345-8721 Fax [EMAIL PROTECTED] www.mqsoftware.com SEE BUSINESS WORK > -Original Message- > From: Kelly F. Hickel > Sent: Tuesday, April 15, 2008 6:14 AM > To: LINUX-390@VM.MARIST.EDU > Subject: RE: CentOS 4.4 kernel panic on boot s390x > > Brad, > That sounds like a great tip, I'll give it a try. I hadn't gone > past the initial "choose a language" screen, both because some of the > google hits said that was as far as you needed to go, and because I was > afraid that if I gave it the location, it might destroy some of the > data. I know it prompts before writing anything, but there are too many > things I don't know about Linux on s390x, so I'm more than a bit > paranoid. > > Thanks, > > > -- > > Kelly F. Hickel > Senior Product Architect > MQSoftware, Inc. > 952-345-8677 Office > 952-345-8721 Fax > [EMAIL PROTECTED] > www.mqsoftware.com > SEE BUSINESS WORK > > > -Original Message- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > > Brad Hinson > > Sent: Monday, April 14, 2008 5:10 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: CentOS 4.4 kernel panic on boot s390x > > > > Hi Kelly, > > > > You mentioned earlier that you're using the installer image. How far > > into the install are you going before SSH'ing in to troubleshoot? If > > you go past the point of entering the location of the stage 2 > > environment (i.e. on the installation method screen, select > > FTP/HTTP/NFS, enter the server and path, then select Next), the > > installer will download or mount (depending on method) the stage 2 > > image > > containing the LVM tools. > > > > I'd recommend going through the install until the point where the VNC > > server is started and it asks you to connect. At that point, SSH in > a > > second time (or press to get a shell prompt). You should see > > that "/" is mounted from the stage 2 image (shown below as > /dev/root), > > and /usr/sbin/lvm will exist: > > > > -/bin/sh-3.00# mount | grep root > > /dev/root on / type ext2 (rw) > > > > -/bin/sh-3.00# which lvm > > /usr/sbin/lvm > > > > > > -Brad > > > > On Mon, 2008-04-14 at 15:34 -0500, Kelly F. Hickel wrote: > > > /usr only contains the lib64 directory. > > > > > > > > > -- > > > > > > Kelly F. Hickel > > > Senior Product Architect > > > MQSoftware, Inc. > > > 952-345-8677 Office > > > 952-345-8721 Fax > > > [EMAIL PROTECTED] > > > www.mqsoftware.com > > > SEE BUSINESS WORK > > > > > > > > > > -Original Message- > > > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf > > Of > > > > Justin Payne > > > > Sent: Monday, April 14, 2008 3:28 PM > > > > To: LINUX-390@VM.MARIST.EDU > > > > Subject: Re: CentOS 4.4 kernel panic on boot s390x > > > > > > > > Do you see lvm in /usr/sbin? > > > > > > > > ~Justin > > > > > > > > Kelly F. Hickel wrote: > > > > > Brad, > > > > > I don't have any of those commands. What I've done is to to > > a > > > > > load from CDRom on the HMC and point it at a downloaded mirror > of > > > the > > > > > s390x centos repo. Is there some other rescue mode that is > more > > > > useful > > > > > than what I have > > > > > > > > > > The contents of /sbin on this ramdisk are: > > > > > -/bin/sh-3.00# ls /sbin > > > > > [dasdfmt hexdump mktemp rmmod > > > > touch > > > > > ash date hostname modprob
Re: CentOS 4.4 kernel panic on boot s390x
Brad, That sounds like a great tip, I'll give it a try. I hadn't gone past the initial "choose a language" screen, both because some of the google hits said that was as far as you needed to go, and because I was afraid that if I gave it the location, it might destroy some of the data. I know it prompts before writing anything, but there are too many things I don't know about Linux on s390x, so I'm more than a bit paranoid. Thanks, -- Kelly F. Hickel Senior Product Architect MQSoftware, Inc. 952-345-8677 Office 952-345-8721 Fax [EMAIL PROTECTED] www.mqsoftware.com SEE BUSINESS WORK > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Brad Hinson > Sent: Monday, April 14, 2008 5:10 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: CentOS 4.4 kernel panic on boot s390x > > Hi Kelly, > > You mentioned earlier that you're using the installer image. How far > into the install are you going before SSH'ing in to troubleshoot? If > you go past the point of entering the location of the stage 2 > environment (i.e. on the installation method screen, select > FTP/HTTP/NFS, enter the server and path, then select Next), the > installer will download or mount (depending on method) the stage 2 > image > containing the LVM tools. > > I'd recommend going through the install until the point where the VNC > server is started and it asks you to connect. At that point, SSH in a > second time (or press to get a shell prompt). You should see > that "/" is mounted from the stage 2 image (shown below as /dev/root), > and /usr/sbin/lvm will exist: > > -/bin/sh-3.00# mount | grep root > /dev/root on / type ext2 (rw) > > -/bin/sh-3.00# which lvm > /usr/sbin/lvm > > > -Brad > > On Mon, 2008-04-14 at 15:34 -0500, Kelly F. Hickel wrote: > > /usr only contains the lib64 directory. > > > > > > -- > > > > Kelly F. Hickel > > Senior Product Architect > > MQSoftware, Inc. > > 952-345-8677 Office > > 952-345-8721 Fax > > [EMAIL PROTECTED] > > www.mqsoftware.com > > SEE BUSINESS WORK > > > > > > > -Original Message- > > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf > Of > > > Justin Payne > > > Sent: Monday, April 14, 2008 3:28 PM > > > To: LINUX-390@VM.MARIST.EDU > > > Subject: Re: CentOS 4.4 kernel panic on boot s390x > > > > > > Do you see lvm in /usr/sbin? > > > > > > ~Justin > > > > > > Kelly F. Hickel wrote: > > > > Brad, > > > > I don't have any of those commands. What I've done is to to > a > > > > load from CDRom on the HMC and point it at a downloaded mirror of > > the > > > > s390x centos repo. Is there some other rescue mode that is more > > > useful > > > > than what I have > > > > > > > > The contents of /sbin on this ramdisk are: > > > > -/bin/sh-3.00# ls /sbin > > > > [dasdfmt hexdump mktemp rmmod > > > touch > > > > ash date hostname modprobe route > tr > > > > awk dd id more rpm2cpio > > > > traceroute > > > > basename deallocvtifconfig mountsed > > true > > > > bash df in.telnetd msh sh > tty > > > > bunzip2 dirname init mv shutdown > > > umount > > > > busybox dmesginsmod nc sleep > > > uname > > > > bzcatdu install openvt sort > > uniq > > > > cat echo ip passwd sshd > > > unzip > > > > chgrpegrepkill pidofstrings > > > uptime > > > > chmodenv killall ping stty > > > usleep > > > > chownexpr ln pivot_root swapoff > vi > > > > chroot falseload_policy poweroff swapon > wc > > > > chvt fgreploader ps sync > > wget > > > > clearfind loginpwd tail > > > which > > > > cmp free ls rdatetar > > > whoami > > > > cmsfscat grep lsmodreadlink tee > > > xargs > > > > cmsfslst gunzip makedevs reboot telnet > > > x
Re: CentOS 4.4 kernel panic on boot s390x
Hi Kelly, You mentioned earlier that you're using the installer image. How far into the install are you going before SSH'ing in to troubleshoot? If you go past the point of entering the location of the stage 2 environment (i.e. on the installation method screen, select FTP/HTTP/NFS, enter the server and path, then select Next), the installer will download or mount (depending on method) the stage 2 image containing the LVM tools. I'd recommend going through the install until the point where the VNC server is started and it asks you to connect. At that point, SSH in a second time (or press to get a shell prompt). You should see that "/" is mounted from the stage 2 image (shown below as /dev/root), and /usr/sbin/lvm will exist: -/bin/sh-3.00# mount | grep root /dev/root on / type ext2 (rw) -/bin/sh-3.00# which lvm /usr/sbin/lvm -Brad On Mon, 2008-04-14 at 15:34 -0500, Kelly F. Hickel wrote: > /usr only contains the lib64 directory. > > > -- > > Kelly F. Hickel > Senior Product Architect > MQSoftware, Inc. > 952-345-8677 Office > 952-345-8721 Fax > [EMAIL PROTECTED] > www.mqsoftware.com > SEE BUSINESS WORK > > > > -Original Message- > > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > > Justin Payne > > Sent: Monday, April 14, 2008 3:28 PM > > To: LINUX-390@VM.MARIST.EDU > > Subject: Re: CentOS 4.4 kernel panic on boot s390x > > > > Do you see lvm in /usr/sbin? > > > > ~Justin > > > > Kelly F. Hickel wrote: > > > Brad, > > > I don't have any of those commands. What I've done is to to a > > > load from CDRom on the HMC and point it at a downloaded mirror of > the > > > s390x centos repo. Is there some other rescue mode that is more > > useful > > > than what I have > > > > > > The contents of /sbin on this ramdisk are: > > > -/bin/sh-3.00# ls /sbin > > > [dasdfmt hexdump mktemp rmmod > > touch > > > ash date hostname modprobe routetr > > > awk dd id more rpm2cpio > > > traceroute > > > basename deallocvtifconfig mountsed > true > > > bash df in.telnetd msh sh tty > > > bunzip2 dirname init mv shutdown > > umount > > > busybox dmesginsmod nc sleep > > uname > > > bzcatdu install openvt sort > uniq > > > cat echo ip passwd sshd > > unzip > > > chgrpegrepkill pidofstrings > > uptime > > > chmodenv killall ping stty > > usleep > > > chownexpr ln pivot_root swapoff vi > > > chroot falseload_policy poweroff swapon wc > > > chvt fgreploader ps sync > wget > > > clearfind loginpwd tail > > which > > > cmp free ls rdatetar > > whoami > > > cmsfscat grep lsmodreadlink tee > > xargs > > > cmsfslst gunzip makedevs reboot telnet > > xauth > > > cp gzip md5sum resettest > > xinetd > > > cpio halt mkdirrm time yes > > > cut head mknodrmdirtop > zcat > > > > > > And that's all that I have to work with... > > > > > > -- > > > > > > Kelly F. Hickel > > > Senior Product Architect > > > MQSoftware, Inc. > > > 952-345-8677 Office > > > 952-345-8721 Fax > > > [EMAIL PROTECTED] > > > www.mqsoftware.com > > > SEE BUSINESS WORK > > > > > > > > > > > >> -Original Message- > > >> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf > > Of > > >> Brad Hinson > > >> Sent: Monday, April 14, 2008 3:05 PM > > >> To: LINUX-390@VM.MARIST.EDU > > >> Subject: Re: CentOS 4.4 kernel panic on boot s390x > > >> > > >> When inside the rescue environment, run 'lvm'. This is an LVM > > "shell" > > >> with all the commands you need (pvcreate, vgscan, etc). At the > very > > >> least, you can run: > > >> > > >> lvm > > >> vgsca
Re: CentOS 4.4 kernel panic on boot s390x
/usr only contains the lib64 directory. -- Kelly F. Hickel Senior Product Architect MQSoftware, Inc. 952-345-8677 Office 952-345-8721 Fax [EMAIL PROTECTED] www.mqsoftware.com SEE BUSINESS WORK > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Justin Payne > Sent: Monday, April 14, 2008 3:28 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: CentOS 4.4 kernel panic on boot s390x > > Do you see lvm in /usr/sbin? > > ~Justin > > Kelly F. Hickel wrote: > > Brad, > > I don't have any of those commands. What I've done is to to a > > load from CDRom on the HMC and point it at a downloaded mirror of the > > s390x centos repo. Is there some other rescue mode that is more > useful > > than what I have > > > > The contents of /sbin on this ramdisk are: > > -/bin/sh-3.00# ls /sbin > > [dasdfmt hexdump mktemp rmmod > touch > > ash date hostname modprobe routetr > > awk dd id more rpm2cpio > > traceroute > > basename deallocvtifconfig mountsed true > > bash df in.telnetd msh sh tty > > bunzip2 dirname init mv shutdown > umount > > busybox dmesginsmod nc sleep > uname > > bzcatdu install openvt sort uniq > > cat echo ip passwd sshd > unzip > > chgrpegrepkill pidofstrings > uptime > > chmodenv killall ping stty > usleep > > chownexpr ln pivot_root swapoff vi > > chroot falseload_policy poweroff swapon wc > > chvt fgreploader ps sync wget > > clearfind loginpwd tail > which > > cmp free ls rdatetar > whoami > > cmsfscat grep lsmodreadlink tee > xargs > > cmsfslst gunzip makedevs reboot telnet > xauth > > cp gzip md5sum resettest > xinetd > > cpio halt mkdirrm time yes > > cut head mknodrmdirtop zcat > > > > And that's all that I have to work with... > > > > -- > > > > Kelly F. Hickel > > Senior Product Architect > > MQSoftware, Inc. > > 952-345-8677 Office > > 952-345-8721 Fax > > [EMAIL PROTECTED] > > www.mqsoftware.com > > SEE BUSINESS WORK > > > > > > > >> -Original Message- > >> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf > Of > >> Brad Hinson > >> Sent: Monday, April 14, 2008 3:05 PM > >> To: LINUX-390@VM.MARIST.EDU > >> Subject: Re: CentOS 4.4 kernel panic on boot s390x > >> > >> When inside the rescue environment, run 'lvm'. This is an LVM > "shell" > >> with all the commands you need (pvcreate, vgscan, etc). At the very > >> least, you can run: > >> > >> lvm > >> vgscan > >> vgchange -a y > >> > >> to activate the LVM. The vgscan creates the /dev nodes, so you > don't > >> need to do that manually. After you exit the LVM shell, you can > >> manually mount /dev// to /mnt/. > >> > >> The kernel panic is most likely because your root file system can't > be > >> found. This could be due to the logical volume for "/" having > >> problems, > >> or zipl not finding it correctly. Double check that /etc/zipl.conf > >> > > has > > > >> the correct root= entry, i.e. > >> > >> "root=/dev//" > >> > >> for the root file system. And for good measure, you may want to run > >> 'zipl' again from the rescue environment after 'chroot'ing to the > >> mounted root fs, just to make sure the MBR is in sync with > zipl.conf. > >> > >> -Brad > >> > >> On Mon, 2008-04-14 at 14:36 -0500, Kelly F. Hickel wrote: > >> > >>> So, I've got this zlinux LPAR on a z9BC, and it's been running > >>> > > CentOS > > > >>> 4.4 for a year or so, and recently it failed to reboot after an > IPL. > >>> > >>> It lists all the dasd, then says "Activating logical volumes"
Re: CentOS 4.4 kernel panic on boot s390x
Do you see lvm in /usr/sbin? ~Justin Kelly F. Hickel wrote: Brad, I don't have any of those commands. What I've done is to to a load from CDRom on the HMC and point it at a downloaded mirror of the s390x centos repo. Is there some other rescue mode that is more useful than what I have The contents of /sbin on this ramdisk are: -/bin/sh-3.00# ls /sbin [dasdfmt hexdump mktemp rmmodtouch ash date hostname modprobe routetr awk dd id more rpm2cpio traceroute basename deallocvtifconfig mountsed true bash df in.telnetd msh sh tty bunzip2 dirname init mv shutdown umount busybox dmesginsmod nc sleepuname bzcatdu install openvt sort uniq cat echo ip passwd sshd unzip chgrpegrepkill pidofstrings uptime chmodenv killall ping stty usleep chownexpr ln pivot_root swapoff vi chroot falseload_policy poweroff swapon wc chvt fgreploader ps sync wget clearfind loginpwd tail which cmp free ls rdatetar whoami cmsfscat grep lsmodreadlink tee xargs cmsfslst gunzip makedevs reboot telnet xauth cp gzip md5sum resettest xinetd cpio halt mkdirrm time yes cut head mknodrmdirtop zcat And that's all that I have to work with... -- Kelly F. Hickel Senior Product Architect MQSoftware, Inc. 952-345-8677 Office 952-345-8721 Fax [EMAIL PROTECTED] www.mqsoftware.com SEE BUSINESS WORK -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Monday, April 14, 2008 3:05 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS 4.4 kernel panic on boot s390x When inside the rescue environment, run 'lvm'. This is an LVM "shell" with all the commands you need (pvcreate, vgscan, etc). At the very least, you can run: lvm vgscan vgchange -a y to activate the LVM. The vgscan creates the /dev nodes, so you don't need to do that manually. After you exit the LVM shell, you can manually mount /dev// to /mnt/. The kernel panic is most likely because your root file system can't be found. This could be due to the logical volume for "/" having problems, or zipl not finding it correctly. Double check that /etc/zipl.conf has the correct root= entry, i.e. "root=/dev//" for the root file system. And for good measure, you may want to run 'zipl' again from the rescue environment after 'chroot'ing to the mounted root fs, just to make sure the MBR is in sync with zipl.conf. -Brad On Mon, 2008-04-14 at 14:36 -0500, Kelly F. Hickel wrote: So, I've got this zlinux LPAR on a z9BC, and it's been running CentOS 4.4 for a year or so, and recently it failed to reboot after an IPL. It lists all the dasd, then says "Activating logical volumes" then panics with "Kernel panic - not syncing: Attempted to kill init!". I've been able to boot from the initrd 4.4 images (thanks all!) but the tools that I'd expect to see (pvscan, fdisk) aren't there. Looking in /proc/dasd/devices shows that the devices are all there and online. I'm even tried created the /dev nodes and mounting /dev/dasda1 (that should be where /boot is, right?) with no luck. I've googled and found a few cookbooks on getting back up after a device or kernel change, but I can't get to the point where I can mount the volume. Any ideas what to try next? -- Kelly F. Hickel Senior Product Architect MQSoftware, Inc. 952-345-8677 Office 952-345-8721 Fax [EMAIL PROTECTED] www.mqsoftware.com SEE BUSINESS WORK - - 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 -- Brad Hinson <[EMAIL PROTECTED]> Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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
Re: CentOS 4.4 kernel panic on boot s390x
Looks like I was slow on the draw. Brad++ Brad Hinson wrote: When inside the rescue environment, run 'lvm'. This is an LVM "shell" with all the commands you need (pvcreate, vgscan, etc). At the very least, you can run: lvm vgscan vgchange -a y to activate the LVM. The vgscan creates the /dev nodes, so you don't need to do that manually. After you exit the LVM shell, you can manually mount /dev// to /mnt/. The kernel panic is most likely because your root file system can't be found. This could be due to the logical volume for "/" having problems, or zipl not finding it correctly. Double check that /etc/zipl.conf has the correct root= entry, i.e. "root=/dev//" for the root file system. And for good measure, you may want to run 'zipl' again from the rescue environment after 'chroot'ing to the mounted root fs, just to make sure the MBR is in sync with zipl.conf. -Brad On Mon, 2008-04-14 at 14:36 -0500, Kelly F. Hickel wrote: So, I've got this zlinux LPAR on a z9BC, and it's been running CentOS 4.4 for a year or so, and recently it failed to reboot after an IPL. It lists all the dasd, then says "Activating logical volumes" then panics with "Kernel panic - not syncing: Attempted to kill init!". I've been able to boot from the initrd 4.4 images (thanks all!) but the tools that I'd expect to see (pvscan, fdisk) aren't there. Looking in /proc/dasd/devices shows that the devices are all there and online. I'm even tried created the /dev nodes and mounting /dev/dasda1 (that should be where /boot is, right?) with no luck. I've googled and found a few cookbooks on getting back up after a device or kernel change, but I can't get to the point where I can mount the volume. Any ideas what to try next? -- Kelly F. Hickel Senior Product Architect MQSoftware, Inc. 952-345-8677 Office 952-345-8721 Fax [EMAIL PROTECTED] www.mqsoftware.com SEE BUSINESS WORK -- 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 -- Brad Hinson <[EMAIL PROTECTED]> Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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: CentOS 4.4 kernel panic on boot s390x
Brad, I don't have any of those commands. What I've done is to to a load from CDRom on the HMC and point it at a downloaded mirror of the s390x centos repo. Is there some other rescue mode that is more useful than what I have The contents of /sbin on this ramdisk are: -/bin/sh-3.00# ls /sbin [dasdfmt hexdump mktemp rmmodtouch ash date hostname modprobe routetr awk dd id more rpm2cpio traceroute basename deallocvtifconfig mountsed true bash df in.telnetd msh sh tty bunzip2 dirname init mv shutdown umount busybox dmesginsmod nc sleepuname bzcatdu install openvt sort uniq cat echo ip passwd sshd unzip chgrpegrepkill pidofstrings uptime chmodenv killall ping stty usleep chownexpr ln pivot_root swapoff vi chroot falseload_policy poweroff swapon wc chvt fgreploader ps sync wget clearfind loginpwd tail which cmp free ls rdatetar whoami cmsfscat grep lsmodreadlink tee xargs cmsfslst gunzip makedevs reboot telnet xauth cp gzip md5sum resettest xinetd cpio halt mkdirrm time yes cut head mknodrmdirtop zcat And that's all that I have to work with... -- Kelly F. Hickel Senior Product Architect MQSoftware, Inc. 952-345-8677 Office 952-345-8721 Fax [EMAIL PROTECTED] www.mqsoftware.com SEE BUSINESS WORK > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Brad Hinson > Sent: Monday, April 14, 2008 3:05 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: CentOS 4.4 kernel panic on boot s390x > > When inside the rescue environment, run 'lvm'. This is an LVM "shell" > with all the commands you need (pvcreate, vgscan, etc). At the very > least, you can run: > > lvm > vgscan > vgchange -a y > > to activate the LVM. The vgscan creates the /dev nodes, so you don't > need to do that manually. After you exit the LVM shell, you can > manually mount /dev// to /mnt/. > > The kernel panic is most likely because your root file system can't be > found. This could be due to the logical volume for "/" having > problems, > or zipl not finding it correctly. Double check that /etc/zipl.conf has > the correct root= entry, i.e. > > "root=/dev//" > > for the root file system. And for good measure, you may want to run > 'zipl' again from the rescue environment after 'chroot'ing to the > mounted root fs, just to make sure the MBR is in sync with zipl.conf. > > -Brad > > On Mon, 2008-04-14 at 14:36 -0500, Kelly F. Hickel wrote: > > So, I've got this zlinux LPAR on a z9BC, and it's been running CentOS > > 4.4 for a year or so, and recently it failed to reboot after an IPL. > > > > It lists all the dasd, then says "Activating logical volumes" then > > panics with "Kernel panic - not syncing: Attempted to kill init!". > > > > I've been able to boot from the initrd 4.4 images (thanks all!) but > the > > tools that I'd expect to see (pvscan, fdisk) aren't there. Looking > in > > /proc/dasd/devices shows that the devices are all there and online. > I'm > > even tried created the /dev nodes and mounting /dev/dasda1 (that > should > > be where /boot is, right?) with no luck. > > > > I've googled and found a few cookbooks on getting back up after a > device > > or kernel change, but I can't get to the point where I can mount the > > volume. > > > > Any ideas what to try next? > > > > > > -- > > > > Kelly F. Hickel > > Senior Product Architect > > MQSoftware, Inc. > > 952-345-8677 Office > > 952-345-8721 Fax > > [EMAIL PROTECTED] > > www.mqsoftware.com > > SEE BUSINESS WORK > > > > - > - > > 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: CentOS 4.4 kernel panic on boot s390x
Kelly F. Hickel wrote: So, I've got this zlinux LPAR on a z9BC, and it's been running CentOS 4.4 for a year or so, and recently it failed to reboot after an IPL. It lists all the dasd, then says "Activating logical volumes" then panics with "Kernel panic - not syncing: Attempted to kill init!". I've been able to boot from the initrd 4.4 images (thanks all!) but the tools that I'd expect to see (pvscan, fdisk) aren't there. Not sure if you're in rescue mode or not, but if you are, commands like pvscan have to be run as: $ lvm pvscan It would be interesting to see what the following shows: $ lvm vgdisplay -v ~Justin Looking in /proc/dasd/devices shows that the devices are all there and online. I'm even tried created the /dev nodes and mounting /dev/dasda1 (that should be where /boot is, right?) with no luck. I've googled and found a few cookbooks on getting back up after a device or kernel change, but I can't get to the point where I can mount the volume. Any ideas what to try next? -- Kelly F. Hickel Senior Product Architect MQSoftware, Inc. 952-345-8677 Office 952-345-8721 Fax [EMAIL PROTECTED] www.mqsoftware.com SEE BUSINESS WORK -- 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: CentOS 4.4 kernel panic on boot s390x
When inside the rescue environment, run 'lvm'. This is an LVM "shell" with all the commands you need (pvcreate, vgscan, etc). At the very least, you can run: lvm vgscan vgchange -a y to activate the LVM. The vgscan creates the /dev nodes, so you don't need to do that manually. After you exit the LVM shell, you can manually mount /dev// to /mnt/. The kernel panic is most likely because your root file system can't be found. This could be due to the logical volume for "/" having problems, or zipl not finding it correctly. Double check that /etc/zipl.conf has the correct root= entry, i.e. "root=/dev//" for the root file system. And for good measure, you may want to run 'zipl' again from the rescue environment after 'chroot'ing to the mounted root fs, just to make sure the MBR is in sync with zipl.conf. -Brad On Mon, 2008-04-14 at 14:36 -0500, Kelly F. Hickel wrote: > So, I've got this zlinux LPAR on a z9BC, and it's been running CentOS > 4.4 for a year or so, and recently it failed to reboot after an IPL. > > It lists all the dasd, then says "Activating logical volumes" then > panics with "Kernel panic - not syncing: Attempted to kill init!". > > I've been able to boot from the initrd 4.4 images (thanks all!) but the > tools that I'd expect to see (pvscan, fdisk) aren't there. Looking in > /proc/dasd/devices shows that the devices are all there and online. I'm > even tried created the /dev nodes and mounting /dev/dasda1 (that should > be where /boot is, right?) with no luck. > > I've googled and found a few cookbooks on getting back up after a device > or kernel change, but I can't get to the point where I can mount the > volume. > > Any ideas what to try next? > > > -- > > Kelly F. Hickel > Senior Product Architect > MQSoftware, Inc. > 952-345-8677 Office > 952-345-8721 Fax > [EMAIL PROTECTED] > www.mqsoftware.com > SEE BUSINESS WORK > > -- > 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 -- Brad Hinson <[EMAIL PROTECTED]> Sr. Support Engineer Lead, System z Red Hat, Inc. (919) 754-4198 -- 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: Centos 4.4 S390x - what's the proper way to install the 32 bit libstdc++ rpm?
> -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Mark Post > Sent: Monday, April 16, 2007 1:17 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Centos 4.4 S390x - what's the proper way to install the > 32 bit libstdc++ rpm? > > >>> On Mon, Apr 16, 2007 at 12:38 PM, in message > <[EMAIL PROTECTED]>, > "Kelly F. > Hickel" <[EMAIL PROTECTED]> wrote: > >> -Original Message- > -snip- > > I already had the 390 RPMs locally, so I tried that and got this: > > [EMAIL PROTECTED] RPMS]# rpm -i libgcc-3.4.6-3.s390.rpm > > package libgcc-3.4.6-3.1 (which is newer than libgcc-3.4.6- > 3) is > > already installed > > > > What am I missing? > > It looks like you've put on some updates. Try the s390 RPM from the > update tree: > http://mirrors.kernel.org/centos/4.4/updates/s390/RPMS/libgcc-3.4.6- > 3.1.s390.rpm > > > Mark Post > DING, DING! We have a winner! Thanks Mark! -Kelly -- 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: Centos 4.4 S390x - what's the proper way to install the 32 bit libstdc++ rpm?
>>> On Mon, Apr 16, 2007 at 12:38 PM, in message <[EMAIL PROTECTED]>, "Kelly F. Hickel" <[EMAIL PROTECTED]> wrote: >> -Original Message- -snip- > I already had the 390 RPMs locally, so I tried that and got this: > [EMAIL PROTECTED] RPMS]# rpm -i libgcc-3.4.6-3.s390.rpm > package libgcc-3.4.6-3.1 (which is newer than libgcc-3.4.6-3) is > already installed > > What am I missing? It looks like you've put on some updates. Try the s390 RPM from the update tree: http://mirrors.kernel.org/centos/4.4/updates/s390/RPMS/libgcc-3.4.6-3.1.s390.rpm 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: Centos 4.4 S390x - what's the proper way to install the 32 bit libstdc++ rpm?
> -Original Message-
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
> Kyle Smith
> Sent: Monday, April 16, 2007 2:03 PM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: Centos 4.4 S390x - what's the proper way to install the
> 32 bit libstdc++ rpm?
>
> First off, are you sure you wanted to install libgcc and not
> libstdc++? Your most recent message mentioned the former, your
> original the latter.
That was my mistake, if you try libstdc++ it wants libgcc, so I tried
that and got the reported error. Trying both together gives:
[EMAIL PROTECTED] RPMS]# rpm -i libstdc++-3.4.6-3.s390.rpm
libgcc-3.4.6-3.s390.rpmpackage libgcc-3.4.6-3.1 (which is newer
than libgcc-3.4.6-3) is already installed
package libstdc++-3.4.6-3.1 (which is newer than
libstdc++-3.4.6-3) is already installed
>
> If so... Sounds to me like the 31-bit version of libgcc is already
> installed.
>
> Try running this:
>
> rpm -qa --queryformat "%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n" | grep
> libgcc
>
> And see what you get for results (try repeating for libstdc++ and
> compat-libstdc++ to see what you're missing).
[EMAIL PROTECTED] RPMS]# rpm -qa --queryformat "%{NAME}
%{VERSION}-%{RELEASE} %{ARCH}\n" | egrep -e "libgcc|libstdc"
libgcc 3.4.6-3.1 s390x
libstdc++ 3.4.6-3.1 s390x
compat-libstdc++-295 2.95.3-81 s390x
libstdc++-devel 3.4.6-3.1 s390x
compat-libgcc-295 2.95.3-81 s390x
compat-libstdc++-33 3.2.3-47.3 s390x
>
> Typically the easiest way to tell if a package is installed is by
> doing an `rpm -qa | grep ` and seeing if you get two
> identical lines of output (31 and 64-bit). Of course if you only get
> one line of output it means you have only the s390 or s390x version
> installed (but not both), hence the longer command above.
That's where I started, I only have the s390x rpms installed, as that's
all that's available in the repo. The guides that I've found on 32 bit
compatibility (mostly for intel) all say that by default I should have
both 32 and 64 bit versions.
-Kelly
>
> ks
>
>
> On 4/16/07, Kelly F. Hickel <[EMAIL PROTECTED]> wrote:
>
> >
> > I already had the 390 RPMs locally, so I tried that and got this:
> > [EMAIL PROTECTED] RPMS]# rpm -i libgcc-3.4.6-3.s390.rpm
> > package libgcc-3.4.6-3.1 (which is newer than libgcc-3.4.6-
> 3) is
> > already installed
> >
> > What am I missing?
> > -Kelly
>
> --
> 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: Centos 4.4 S390x - what's the proper way to install the 32 bit libstdc++ rpm?
First off, are you sure you wanted to install libgcc and not
libstdc++? Your most recent message mentioned the former, your
original the latter.
If so... Sounds to me like the 31-bit version of libgcc is already installed.
Try running this:
rpm -qa --queryformat "%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n" | grep libgcc
And see what you get for results (try repeating for libstdc++ and
compat-libstdc++ to see what you're missing).
Typically the easiest way to tell if a package is installed is by
doing an `rpm -qa | grep ` and seeing if you get two
identical lines of output (31 and 64-bit). Of course if you only get
one line of output it means you have only the s390 or s390x version
installed (but not both), hence the longer command above.
ks
On 4/16/07, Kelly F. Hickel <[EMAIL PROTECTED]> wrote:
I already had the 390 RPMs locally, so I tried that and got this:
[EMAIL PROTECTED] RPMS]# rpm -i libgcc-3.4.6-3.s390.rpm
package libgcc-3.4.6-3.1 (which is newer than libgcc-3.4.6-3) is
already installed
What am I missing?
-Kelly
--
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: Centos 4.4 S390x - what's the proper way to install the 32 bit libstdc++ rpm?
> -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Michael MacIsaac > Sent: Monday, April 16, 2007 1:34 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Centos 4.4 S390x - what's the proper way to install the > 32 bit libstdc++ rpm? > > > [EMAIL PROTECTED] RPMS]# rpm -i libgcc-3.4.6-3.s390.rpm > >package libgcc-3.4.6-3.1 (which is newer than libgcc-3.4.6-3) > is > > already installed > I got an error similar to this recently and the problem turned out to > be > that I was pointing to a different install tree than the one that I > installed from. So be sure what you are pointing to is the same set > of > RPMs from which Linux was installed. Mike, Well, that's sort of the problem. I've installed from the s390x iso, but need the 32 bit libstdc++ rpm from the s390 iso. It seems that I should have been able to do "yum install libstdc++.s390", but the yum repo for s390x doesn't contain an rpm for that. So, I took the s390 rpm from an iso image and tried to install that via yum and rpm, but they both think it conflicts with the s390x rpm. -Kelly > > Hope this helps. > > "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: Centos 4.4 S390x - what's the proper way to install the 32 bit libstdc++ rpm?
> [EMAIL PROTECTED] RPMS]# rpm -i libgcc-3.4.6-3.s390.rpm >package libgcc-3.4.6-3.1 (which is newer than libgcc-3.4.6-3) is > already installed I got an error similar to this recently and the problem turned out to be that I was pointing to a different install tree than the one that I installed from. So be sure what you are pointing to is the same set of RPMs from which Linux was installed. Hope this helps. "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
Re: Centos 4.4 S390x - what's the proper way to install the 32 bit libstdc++ rpm?
> -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Mark Post > Sent: Monday, April 16, 2007 11:26 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Centos 4.4 S390x - what's the proper way to install the > 32 bit libstdc++ rpm? > > >>> On Mon, Apr 16, 2007 at 11:55 AM, in message > <[EMAIL PROTECTED]>, > "Kelly F. > Hickel" <[EMAIL PROTECTED]> wrote: > > I've got an LPAR running Centos 4.4 s390x and I'm trying to install > a > > product that needs the 31 bit versions of libstdc++ and so on. It > > *seems * that I should be able to issue "yum install libstdc++.s390" > and > > that should be that. However, yum indicates that the s390 package > does > > exist in the repository (I'm using the default yum configuration). > > > > What's the "proper" way to deal with this? I could grab the rpms I > need > > from an S390 ISO image, but I'm not sure that's the right thing to > do. > > I don't see a 31-bit version on the CentOS mirrors for s390x. In that > case, you would probably want to download > http://mirrors.kernel.org/centos/4.4/os/s390/CentOS/RPMS/libstdc++- > 3.4.6-3.s390.rpm and install it. > I already had the 390 RPMs locally, so I tried that and got this: [EMAIL PROTECTED] RPMS]# rpm -i libgcc-3.4.6-3.s390.rpm package libgcc-3.4.6-3.1 (which is newer than libgcc-3.4.6-3) is already installed What am I missing? -Kelly > > 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: Centos 4.4 S390x - what's the proper way to install the 32 bit libstdc++ rpm?
Hi, On Mon, Apr 16, 2007 at 10:55:13AM -0500, Kelly F. Hickel wrote: > I've got an LPAR running Centos 4.4 s390x and I'm trying to install a > product that needs the 31 bit versions of libstdc++ and so on. It > *seems * that I should be able to issue "yum install libstdc++.s390" and > that should be that. However, yum indicates that the s390 package does > exist in the repository (I'm using the default yum configuration). > > > > What's the "proper" way to deal with this? I could grab the rpms I need > from an S390 ISO image, but I'm not sure that's the right thing to do. > As it was already stated, you can fetch anything you want from the s390 repo(s). It's intentional that the s390x os clearly 64bit pure and clean version with only glibc and glibc-devel from s390 (needed for build). It's not even trying to mimic the mixed mode version from upstream source provider, so if you need to get mixed mode installation, you need to fetch the needed parts from s390 version of CentOS-4 manually (or what ever way one seems to be suitable). It's possible to make s390 repos available for yum simply by editing right paths in /etc/yum.repos.d/ files, but one should be extra carefull with full s390 repo available to s390x installation. Sometimes yum just 'gets greedy' and fetches unneeded packages in. That is not so problematic, when 'the overriding arch' is the host main arch (s390x overrides s390). -- Pasi Pirhonen - [EMAIL PROTECTED] - http://pasi.pirhonen.eu/ Top-postings silently ignored -- 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: Centos 4.4 S390x - what's the proper way to install the 32 bit libstdc++ rpm?
>>> On Mon, Apr 16, 2007 at 11:55 AM, in message <[EMAIL PROTECTED]>, "Kelly F. Hickel" <[EMAIL PROTECTED]> wrote: > I've got an LPAR running Centos 4.4 s390x and I'm trying to install a > product that needs the 31 bit versions of libstdc++ and so on. It > *seems * that I should be able to issue "yum install libstdc++.s390" and > that should be that. However, yum indicates that the s390 package does > exist in the repository (I'm using the default yum configuration). > > What's the "proper" way to deal with this? I could grab the rpms I need > from an S390 ISO image, but I'm not sure that's the right thing to do. I don't see a 31-bit version on the CentOS mirrors for s390x. In that case, you would probably want to download http://mirrors.kernel.org/centos/4.4/os/s390/CentOS/RPMS/libstdc++-3.4.6-3.s390.rpm and install it. 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: CentOS DASD format
Melancon, Ruddy wrote: > Is there a way to restart the loader? Not easily that I know of. Re-IPL of your media will probably be the easiest/quickest way. I find that it can take me several IPLs to get used to the installation process of an unfamiliar distro. Time is well spent getting familiar with the parmfile syntax, so that you can get to the point of SSH/Telnet into the installer with few or no console commands having to be entered. In your "Load from CD-ROM" case you could experiment with writing your own CD containing the installation files (kernel, parmfile, initrd) -- use a CD-RW while getting the parmfile right, unless you need a new set of coasters! :D Cheers, Vic Cross PS: Hoping this is helpful... It's *real* late (early?) over here and I might be starting to ramble :) -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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: CentOS DASD format
> Is there a way to restart the loader? #cp ipl 00c Assuming the three punch files are still in your reader, that will just start the install process again. "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
Re: CentOS DASD format
Is there a way to restart the loader? When I first connected to the IPLed image I was disconnected before I could do any setup. Now when I login I get a message... Loader has already been run. Starting shell. If I try to rerun the loader I get the same message. Ruddy A. Melancon IT System Specialist - ISD State of Alabama 64 North Union Street Montgomery, AL 36130 334.353.7275 When the only tool you have is a hammer, every problem begins to resemble a nail. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Vic Cross Sent: Friday, July 21, 2006 9:56 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS DASD format Richard Pinion wrote: > Have done the fdasd command? fdasd comes *after* dasdfmt... >>>> [EMAIL PROTECTED] 7/21/2006 10:20:13 AM >>> > I am attempting to install CentOS (Red Hat) v4.2 in a zSeries LPAR > (standalone). I IPLed the CD-ROM and I am at the point of havint to > format the DASD. I entered: > > Dasdfmt -b 4096 -d cdl -f /dev/dasda Ummm.. I've done several CentOS installations, and I don't recall having to manually format the DASD on any of them... When you SSH/Telnet into the installation system, you end up in the system installer (Anaconda), which is pretty much a bouncing-ball thing, including the setup of the DASD. > It comes back with a message that the file is not available. When I > look in the /dev directory there is no dasda, although in looking in > /sys I can find the file that describes the disk drive as well as the > file that shows it online. It's likely that the installer hasn't set up the device nodes for your DASDs yet -- too early in the piece. > Where does CentOS put the device descriptor and how do I address it in > the 'dasdfmt' command? If you *really* need to format the DASDs manually, you will need to create the device nodes yourself. Check to see that the proc filesystem is mounted, then issue "cat /proc/dasd/devices" to see what device major/minors have been allocated to the DASDs. Then, "mknod /dev/dasd b " with appropriate substitutions for and , for each of the nodes you want, will get you started. But you really should not need to do any of this. Just follow the installer's prompts and it should get you there. Rob's comments are gold as well: ensure that the DASDs are online (cat the appropriate "online" pseudofile in the sys filesystem directory you found; a result of "1" is good) and that the DASD modules are loaded. Cheers, Vic Cross -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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: CentOS DASD format
On 7/21/06, Melancon, Ruddy <[EMAIL PROTECTED]> wrote: When I look in the /dev directory there is no dasda, although in looking in /sys I can find the file that describes the disk drive as well as the file that shows it online. If the device (/dev/dasda) is not in /dev, maybe you need to create it manually ? Check if it is present in /proc/dasd/devices. You will fin the major and minor in that file. As an example : [EMAIL PROTECTED]:~> cat /proc/dasd/devices 0.0.0150(ECKD) at ( 94: 0) is dasda : active at blocksize: 4096, 105840 blocks, 413 MB 0.0.0151(ECKD) at ( 94: 4) is dasdb : active at blocksize: 4096, 211860 blocks, 827 MB You can create the dasda device in that example by entering these commands : mknod /dev/dasda b 94 0 mknod /dev/dasda1 b 94 1 mknod /dev/dasda2 b 94 2 mknod /dev/dasda3 b 94 3 Then you will be able to dasdfmt and fdasd. Regards. -- 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: CentOS DASD format
Richard Pinion wrote: > Have done the fdasd command? fdasd comes *after* dasdfmt... [EMAIL PROTECTED] 7/21/2006 10:20:13 AM >>> > I am attempting to install CentOS (Red Hat) v4.2 in a zSeries LPAR > (standalone). I IPLed the CD-ROM and I am at the point of havint to > format the DASD. I entered: > > Dasdfmt -b 4096 -d cdl -f /dev/dasda Ummm.. I've done several CentOS installations, and I don't recall having to manually format the DASD on any of them... When you SSH/Telnet into the installation system, you end up in the system installer (Anaconda), which is pretty much a bouncing-ball thing, including the setup of the DASD. > It comes back with a message that the file is not available. When I > look in the /dev directory there is no dasda, although in looking in > /sys I can find the file that describes the disk drive as well as the > file that shows it online. It's likely that the installer hasn't set up the device nodes for your DASDs yet -- too early in the piece. > Where does CentOS put the device descriptor and how do I address it in > the 'dasdfmt' command? If you *really* need to format the DASDs manually, you will need to create the device nodes yourself. Check to see that the proc filesystem is mounted, then issue "cat /proc/dasd/devices" to see what device major/minors have been allocated to the DASDs. Then, "mknod /dev/dasd b " with appropriate substitutions for and , for each of the nodes you want, will get you started. But you really should not need to do any of this. Just follow the installer's prompts and it should get you there. Rob's comments are gold as well: ensure that the DASDs are online (cat the appropriate "online" pseudofile in the sys filesystem directory you found; a result of "1" is good) and that the DASD modules are loaded. Cheers, Vic Cross -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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: CentOS DASD format
On 7/21/06, Melancon, Ruddy <[EMAIL PROTECTED]> wrote: It comes back with a message that the file is not available. When I look in the /dev directory there is no dasda, although in looking in /sys I can find the file that describes the disk drive as well as the file that shows it online. But is dasda indeed online? Is the device driver module loaded? -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.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: CentOS DASD format
Have done the fdasd command? >>> [EMAIL PROTECTED] 7/21/2006 10:20:13 AM >>> I am attempting to install CentOS (Red Hat) v4.2 in a zSeries LPAR (standalone). I IPLed the CD-ROM and I am at the point of havint to format the DASD. I entered: Dasdfmt -b 4096 -d cdl -f /dev/dasda It comes back with a message that the file is not available. When I look in the /dev directory there is no dasda, although in looking in /sys I can find the file that describes the disk drive as well as the file that shows it online. Where does CentOS put the device descriptor and how do I address it in the 'dasdfmt' command? Ruddy A. Melancon IT System Specialist - ISD State of Alabama 64 North Union Street Montgomery, AL 36130 334.353.7275 When the only tool you have is a hammer, every problem begins to resemble a nail. -- 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
WWTFDOT: RE: CentOS vs. Tuttle, OK
> Presumably you would have been a little quicker to spot that you were > being a dill, or maybe even a little cautions about collecting the facts > so as to begin to understand the problem before casting nasturtiums all > over the place. Oh, my. The flowering of Western Civilization. Positively spicy. -- db PS - it's too hot for this. -- 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: CentOS vs. Tuttle, OK
McKown, John wrote: -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Gregg C Levine Sent: Tuesday, March 28, 2006 3:31 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS vs. Tuttle, OK Hello! If he's got that much experience then why'd he sound like an idiot to begin with? Perhaps because what he has is 22 times 1 year of experience instead of 22 years of experience? It happens that I do have that much experience and happen to recognize the classic Apache webpage that indicates it was indeed installed successfully. But this person, despite his qualifications, most likely had never even heard of Linux or Apache. If this had happened to me, say 4 years ago, I would have been in the same boat. John, Presumably you would have been a little quicker to spot that you were being a dill, or maybe even a little cautions about collecting the facts so as to begin to understand the problem before casting nasturtiums all over the place. -- 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: CentOS vs. Tuttle, OK
> -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On > Behalf Of Gregg C Levine > Sent: Tuesday, March 28, 2006 3:31 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: CentOS vs. Tuttle, OK > > > Hello! > If he's got that much experience then why'd he sound like an idiot to > begin with? Perhaps because what he has is 22 times 1 year of experience instead of 22 years of experience? > It happens that I do have that much experience and happen > to recognize the classic Apache webpage that indicates it was indeed > installed successfully. But this person, despite his qualifications, most likely had never even heard of Linux or Apache. If this had happened to me, say 4 years ago, I would have been in the same boat. > > Quite obviously it was the fault of the people of that town to elect > someone who had no clear idea of what he was doing in either local City Managers are usually hired, not elected. This person may lose his job. Not for being ignorant, but for bringing down "bad publicity" on the community. Had he just been courteous instead of a , then this would likely never have been reported upon. > technology or government. And to select a cable TV company to deliver > their Internet access as well. Besides I am convinced that our friend Cable companies are aggressively going after "small businesses". This town is in that category. It is a small burg, from what I can tell. The local cable company, Comcast, is really pushing their small business internet connectivity. > at CentOS went out of his way to be polite to this individual. The > kind of thing that's called far beyond the call of duty. Very true. That's why I posted this story originally. -- 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. -- 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: CentOS vs. Tuttle, OK
Hello! If he's got that much experience then why'd he sound like an idiot to begin with? It happens that I do have that much experience and happen to recognize the classic Apache webpage that indicates it was indeed installed successfully. Quite obviously it was the fault of the people of that town to elect someone who had no clear idea of what he was doing in either local technology or government. And to select a cable TV company to deliver their Internet access as well. Besides I am convinced that our friend at CentOS went out of his way to be polite to this individual. The kind of thing that's called far beyond the call of duty. -- Gregg C Levine [EMAIL PROTECTED] --- "Remember the Force will be with you. Always." Obi-Wan Kenobi > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Jon Brock > Sent: Tuesday, March 28, 2006 11:07 AM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: [LINUX-390] CentOS vs. Tuttle, OK > > I was thinking the same thing. > > I loved this part: > "I am computer literate! I have 22 > years in computer systems engineering and operation." > > Jon > > > > > Johnny Hughes certainly has far more patience than I do. After the > second threat to contact the FBI, my reply would have been along the > lines of: > > Mr. Taylor, > You are an idiot. Please contact the FBI, and let them explain to you > why you are an idiot. > > > -- > 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: CentOS vs. Tuttle, OK
Hey, the city manager and co-star of this *cough* humorous tidbit is obviously fearless... Check out the photo at: http://www.tuttletimes.com/viewarticle.php?id=949 -dan. Little, Chris wrote: Why Oklahoma?? But I always knew there was something wrong with Tuttle. We have a commercial running on some local radio stations right now . . . . one of the lines goes: Speaker 1: Why is it so different in Tuttle? Speaker 2: Have you ever been to Tuttle? Speaker 3: Oh. -Original Message- From: McKown, John [mailto:[EMAIL PROTECTED] Sent: Monday, March 27, 2006 3:00 PM To: LINUX-390@VM.MARIST.EDU Subject: CentOS vs. Tuttle, OK Kudos to Johnny Hughes of CentOS. How to handle an idiot! Not mainframe related, but both amusing and saddening. http://wwwf.centos.org/127_story.html?storyid=127 -- 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. -- 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: CentOS vs. Tuttle, OK
Why Oklahoma?? But I always knew there was something wrong with Tuttle. We have a commercial running on some local radio stations right now . . . . one of the lines goes: Speaker 1: Why is it so different in Tuttle? Speaker 2: Have you ever been to Tuttle? Speaker 3: Oh. > -Original Message- > From: McKown, John [mailto:[EMAIL PROTECTED] > Sent: Monday, March 27, 2006 3:00 PM > To: LINUX-390@VM.MARIST.EDU > Subject: CentOS vs. Tuttle, OK > > Kudos to Johnny Hughes of CentOS. How to handle an idiot! Not > mainframe related, but both amusing and saddening. > > http://wwwf.centos.org/127_story.html?storyid=127 > > -- > 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. > > -- > 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: CentOS vs. Tuttle, OK
I can empathize with Mr. Taylor. Years ago I was taken in by the 'Budweiser Frog' hoax (I shouldn't feel bad about it, so was our help desk), and passed it on to the VMESA-L list. I received nice, but firm instructions to check my facts before sending out anything similar. It made me a better, wiser person, but it was really embarrassing at the time. Peter -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: March 28, 2006 11:14 To: LINUX-390@VM.MARIST.EDU Subject: Re: CentOS vs. Tuttle, OK As a follow up to this. "The Register", the web site that apparently had the original story, has now received an email from Mr. Taylor asking them to stop all the emails that he has been getting from people about this story. http://www.theregister.co.uk/2006/03/27/tuttle_email/ I do not follow instructions that show up when a website that I am not familiar with appears on my computer and I do not think anyone with experience would do so either. Once the Centos site appeared on four computers at one site I contacted our web service provider. The web service provider did not know what could cause the problem and had never heard of "CentOS". I then contacted the internet provider's local office and was told that they did nothing to cause the problem. I checked the building's server and found nothing relating to CentOS on the server. I was then left with only the web page email address to contact. I asked for the strange website to be removed because it blocked my City web site and I could not post public information. I only got help after threatening to contact the FBI. Now I am being flooded with emails from CentOS users that after knowing the answer say the problem was simple. I think this is unjustified and would like for this to stop. Your website should provide useful information and be a credit to the IT world. I do not believe it should be used to incite the users. Your attention to this matter is greatly appreciated. -- 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. -- 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 The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error, please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail, or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner. -- 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: CentOS vs. Tuttle, OK
As a follow up to this. "The Register", the web site that apparently had the original story, has now received an email from Mr. Taylor asking them to stop all the emails that he has been getting from people about this story. http://www.theregister.co.uk/2006/03/27/tuttle_email/ I do not follow instructions that show up when a website that I am not familiar with appears on my computer and I do not think anyone with experience would do so either. Once the Centos site appeared on four computers at one site I contacted our web service provider. The web service provider did not know what could cause the problem and had never heard of "CentOS". I then contacted the internet provider's local office and was told that they did nothing to cause the problem. I checked the building's server and found nothing relating to CentOS on the server. I was then left with only the web page email address to contact. I asked for the strange website to be removed because it blocked my City web site and I could not post public information. I only got help after threatening to contact the FBI. Now I am being flooded with emails from CentOS users that after knowing the answer say the problem was simple. I think this is unjustified and would like for this to stop. Your website should provide useful information and be a credit to the IT world. I do not believe it should be used to incite the users. Your attention to this matter is greatly appreciated. -- 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. -- 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: CentOS vs. Tuttle, OK
I was thinking the same thing. I loved this part: "I am computer literate! I have 22 years in computer systems engineering and operation." Jon Johnny Hughes certainly has far more patience than I do. After the second threat to contact the FBI, my reply would have been along the lines of: Mr. Taylor, You are an idiot. Please contact the FBI, and let them explain to you why you are an idiot. -- 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: CentOS vs. Tuttle, OK
Johnny Hughes certainly has far more patience than I do. After the second threat to contact the FBI, my reply would have been along the lines of: Mr. Taylor, You are an idiot. Please contact the FBI, and let them explain to you why you are an idiot. Dennis "Do you think it's a good idea, letting an Arab country take over our ports? This is like letting Bill Clinton be the manager of a Hooters." -- Jay Leno -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Monday, March 27, 2006 13:00 To: LINUX-390@VM.MARIST.EDU Subject: CentOS vs. Tuttle, OK Kudos to Johnny Hughes of CentOS. How to handle an idiot! Not mainframe related, but both amusing and saddening. http://wwwf.centos.org/127_story.html?storyid=127 -- 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. -- 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: CentOS ISO needed.
Ruddy, I was in the same position. Our security people would freak if I tried to install BitTorrent. Go to ftp://centos.upi.iki.fi/pub/centos/. Thanks to Pasi Pirhonen for making this option available. Peter -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Melancon, Ruddy Sent: March 13, 2006 18:00 To: LINUX-390@VM.MARIST.EDU Subject: CentOS ISO needed. I would like to obtain an ISO copy of CentOS 4.2 to test on a 390 LPAR. I notice that all download sites want to use BitTorrent. This is a peer to peer file sharing program that as a state agency we are not allowed to use. Is there a source for download that allows direct transfer of ISO files? Is there another source that I may use for free? Ruddy A. Melancon IT System Specialist - ISD State of Alabama 64 North Union Street Montgomery, AL 36130 334.353.7275 One seventh of your life is spent on Monday. -- 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 The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error, please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail, or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner. -- 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: CentOS ISO needed.
John Summerfied wrote: > I believe bittorrent doesn't force you to share, but then I've not used it. Bittorrent does always "share" in a sense that it uploads parts of the file it is currently dowloading. Bittorrent is a popular download method for oss, because it saves server bandwidth (cost). As opposed to trading files that are protected by copyright, there is no legal reason not to use bt for oss/copyleft data. Carsten -- Carsten Otte IBM Linux technology center ARCH=s390 -- 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: CentOS ISO needed.
On 3/14/06, John Summerfied <[EMAIL PROTECTED]> wrote: > I believe bittorrent doesn't force you to share, but then I've not used it. The clients I have seen do share the portion of the file you already downloaded while you are downloading the last bits and pieces. When I downloaded the CentOS DVD it turned out I was the only one doing so at that time so there was nobody to upload to (and the 3 mirrors had the full file and did not need my contribution). We've been there. FTP used to be a popular way to download illegal content, so we could not use FTP in the company (other than through a authenticated proxy that logged all traffic). When I did the statistics of the e-mail backbone I found that a lot of mails were 1.44MB in size originating from various bitftp servers (youngsters: that's the size of what we called HD floppy). I expect that some day we will go and educate users about illegal activities rather than block ports for everyone. Given the audience, I think it would make sense to host the CentOS download on an FTP or HTTP server as well but that's not up to me. If you're not able to get yourself an ADSL connection and a spare PC for this, you can buy from someone who did. I see that http://www.cheeplinux.com/ explictly lists the s390 and s390x CD's (you want to make sure not to get the obvious default) at GBP 10 per set, but there may be places that are wiser w.r.t. shipping cost. Rob -- Rob van der Heij Velocity Software, Inc -- 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: CentOS ISO needed.
Melancon, Ruddy wrote: I would like to obtain an ISO copy of CentOS 4.2 to test on a 390 LPAR. I notice that all download sites want to use BitTorrent. This is a peer to peer file sharing program that as a state agency we are not allowed to use. I believe bittorrent doesn't force you to share, but then I've not used it. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Tourist pics http://portgeographe.environmentaldisasters.cds.merseine.nu/ 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
Re: CentOS ISO needed.
You might take a look at this thread in the archives: http://www2.marist.edu/htbin/wlvtype?LINUX-VM.58494 Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Melancon, Ruddy Sent: Monday, March 13, 2006 6:00 PM To: LINUX-390@VM.MARIST.EDU Subject: CentOS ISO needed. I would like to obtain an ISO copy of CentOS 4.2 to test on a 390 LPAR. I notice that all download sites want to use BitTorrent. This is a peer to peer file sharing program that as a state agency we are not allowed to use. Is there a source for download that allows direct transfer of ISO files? Is there another source that I may use for free? -- 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: Centos ISOs
This is going way back to reply, I know (been waaay to busy lately), but about 18 months ago, I took an installation kernel and initrd, put it in /boot on a running Linux/390 system, and ran zipl against them. When I rebooted the system, I was put right into the installer. Got me thinking that trying to boot from tape, or the VM reader might be unnecessarily cumbersome. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Rick Troth Sent: Thursday, January 19, 2006 8:55 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Centos ISOs No one is doing it (I say, without proof, but with confidence) but it IS possible to create IPLable .iso images, either FBA IPLable or presumably also SCSI IPLable. (I've personally done the former.) Can TRACKWRITE handle FBA? If so, then we might could crank out a tool that would stamp VDISK with bootable stuff from .iso files. -- R; -- 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: Centos ISOs
The desire to download .iso images is because that is what the installation instructions are written for. It's been quite a while since I last did a Linux install, and I like having the crutch of written instructions. You did, however, tweak my memory, and I think that I used wget for my last install. Thanks for the pointer, I will look into it. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Post, Mark K Sent: January 19, 2006 15:55 To: LINUX-390@VM.MARIST.EDU Subject: Re: Centos ISOs I would imagine that it isn't the mirrors making a decision to only offer bittorrents, but the CentOS project itself. I doubt anyone has .iso files for the mainframe. Personally, I still don't understand the desire to download .iso images. You still have turn play games to make an installable directory structure. Just use wget to download the individual files to start with. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter Webb, Toronto Transit Commission Sent: Thursday, January 19, 2006 3:42 PM To: LINUX-390@VM.MARIST.EDU Subject: Centos ISOs Hi, Does anybody know a site that has the Centos ISO images for S390 available? All the mirrors appear to have bittorrent files, and installing bittorrent at work could get me into some trouble. Home is on a 56K dial-up, so that's not really an option either. And no, I don't have a budget to buy anything. -- 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 The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error, please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail, or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner. -- 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: Centos ISOs
On Jan 19, 2006, at 7:55 PM, Rick Troth wrote: No one is doing it (I say, without proof, but with confidence) but it IS possible to create IPLable .iso images, either FBA IPLable or presumably also SCSI IPLable. (I've personally done the former.) Can TRACKWRITE handle FBA? If so, then we might could crank out a tool that would stamp VDISK with bootable stuff from .iso files. Ahem. RXDASD certainly can. It's what we did with SWAPGEN. 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: Centos ISOs
No one is doing it (I say, without proof, but with confidence) but it IS possible to create IPLable .iso images, either FBA IPLable or presumably also SCSI IPLable. (I've personally done the former.) Can TRACKWRITE handle FBA? If so, then we might could crank out a tool that would stamp VDISK with bootable stuff from .iso files. -- R; On Thu, 19 Jan 2006, Post, Mark K wrote: > I would imagine that it isn't the mirrors making a decision to only > offer bittorrents, but the CentOS project itself. I doubt anyone has > .iso files for the mainframe. > > Personally, I still don't understand the desire to download .iso images. > You still have turn play games to make an installable directory > structure. Just use wget to download the individual files to start > with. > > > Mark Post > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of > Peter Webb, Toronto Transit Commission > Sent: Thursday, January 19, 2006 3:42 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Centos ISOs > > > Hi, > > Does anybody know a site that has the Centos ISO images for S390 > available? All the mirrors appear to have bittorrent files, and > installing bittorrent at work could get me into some trouble. Home is on > a 56K dial-up, so that's not really an option either. And no, I don't > have a budget to buy anything. > > -- > 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: Centos ISOs
Hi, On Thu, Jan 19, 2006 at 03:42:22PM -0500, Peter Webb, Toronto Transit Commission wrote: > Hi, > > Does anybody know a site that has the Centos ISO images for S390 > available? All the mirrors appear to have bittorrent files, and > installing bittorrent at work could get me into some trouble. Home is on > a 56K dial-up, so that's not really an option either. And no, I don't > have a budget to buy anything. > > Although i am making those ISO-images, i am not resposnsible about the policy that those images arean't available from out RRDNS http://mirror.centos.org/ . Then again, i do have box i am fully controlling, so i keep my work available thru it, so ftp://centos.upi.iki.fi/pub/centos/ should always have anything recent availlable. The box is somewhat bandwith limited as i am not allowed to use more than 10Mbit/s, so that's where it's limited. There is list of mirrors at http://www.centos.org/modules/tinycontent/index.php?id=13 which are rsynching from our machines, but i don't know which ones of those are carrying the s390/s390x images :/ HTH, -- Pasi Pirhonen - [EMAIL PROTECTED] - http://iki.fi/upi/ -- 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: Centos ISOs
I would imagine that it isn't the mirrors making a decision to only offer bittorrents, but the CentOS project itself. I doubt anyone has .iso files for the mainframe. Personally, I still don't understand the desire to download .iso images. You still have turn play games to make an installable directory structure. Just use wget to download the individual files to start with. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Peter Webb, Toronto Transit Commission Sent: Thursday, January 19, 2006 3:42 PM To: LINUX-390@VM.MARIST.EDU Subject: Centos ISOs Hi, Does anybody know a site that has the Centos ISO images for S390 available? All the mirrors appear to have bittorrent files, and installing bittorrent at work could get me into some trouble. Home is on a 56K dial-up, so that's not really an option either. And no, I don't have a budget to buy anything. -- 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: CentOS 4.2 on Hercules: install networking problem
On Tue, Oct 18, 2005 at 07:10:51PM +0300, Pasi Pirhonen wrote: > That's weird as the primary development platform for it is hercules. > I have not been able to get LCS working under hercules (haven't even > tried long time tho), but i use CTC myself and have even done test > installation with these 4.2-level (update2) image for both - s390 and > s390x under hercules. Of course, when I tried to recreate the problem, it started working. Bleh. -- Jay Maynard, K5ZC http://www.conmicro.cx http://www.tronguy.net (Yes, that's me!) http://jmaynard.livejournal.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: CentOS 4.2 on Hercules: install networking problem
Hi, On Tue, Oct 18, 2005 at 09:25:49AM -0500, Jay Maynard wrote: > I'm trying to install CentOS 4.2 on Hercules. (About time, eh?) I got the > DVD image downloaded, mounted, and IPLed, but when I try to tell the > installer about the network, it either doesn't find the interface (if I use > CTC) or panics (while loading the LCS module). Is this a known problem? > FWIW, I was able to get SLES 9 RC5 installed via a CTC connection (after > working around an installer bug that treats FTP paths as relative, even if a > leading / is specified). That's weird as the primary development platform for it is hercules. I have not been able to get LCS working under hercules (haven't even tried long time tho), but i use CTC myself and have even done test installation with these 4.2-level (update2) image for both - s390 and s390x under hercules. One thing coming in my mind that one should select '0' as compatibility module at least. I do believe that chose that 'linux mode' once and found that isn't something that is not working under hercules. Known issue (actually it's more like feature on hercules most likely) is that graphical installation crashes on time zone selection map draving, so graphical install under hercules isn't working. It might (just a hunch) be relatedto the fact hercules does pass some of the floating point ops to the hosts FPU directly and due to fact of different accuracy, we sometimes se different results there. At least something like that does pop up sometimes with other stuff. It's just that it's _feature_ as making it not to pass those, would make all floating point crawl (at least i've told so). for example i do have 0400.2 3088CTCI 192.168.4.2 192.168.4.1 defined for one host as CTC. Then i tell it to use 0.0.0400,0.0.0401 for CTC address and select the '0' for compat more. Works for me at least. Then again. I do use CVS snapshots of hercules, but that should not really matter. HTH, -- Pasi Pirhonen - [EMAIL PROTECTED] - http://iki.fi/upi/ -- 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: CentOS
Jim, That's not really sufficient. The "name" of the kernel (and that is compiled into the kernel) has to match the name of the kernel for which the driver was compiled. That's why I asked Istvan if he knew what a "uname -a" command reported. If it doesn't match exactly what the Red Hat kernel reports, it will be necessary to force the loading of the driver, which most people really, really try to avoid. Part of this involves the issue that the kernel developers don't guarantee the correct functioning of kernel modules that were compiled with a different compiler than the kernel itself. It usually works, but there are always exceptions. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Jim Elliott Sent: Thursday, July 28, 2005 12:15 PM To: LINUX-390@VM.MARIST.EDU Subject: CentOS > Is CentOS kernel compatible with IBM's 3590 tape driver? Istvan: CentOS is just a recompiled RHEL. You should be able to download the relevant binary for the IBM 3590 for the equivalent RHEL level. Jim -- 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: CentOS
I'm just thinking about downloading and installing it.. :) Anobody tried it? Linux on 390 Port írta 2005.07.28 07:46:07 időpontban: > When you do a "uname -a" command, what does it report? > > > Mark Post > > -Original Message- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf > Of Istvan Nemeth > Sent: Thursday, July 28, 2005 1:40 AM > To: LINUX-390@VM.MARIST.EDU > Subject: CentOS > > > Hello! > > Is CentOS kernel compatible with IBM's 3590 tape driver? > > István > > -- > 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: CentOS
When you do a "uname -a" command, what does it report? Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Istvan Nemeth Sent: Thursday, July 28, 2005 1:40 AM To: LINUX-390@VM.MARIST.EDU Subject: CentOS Hello! Is CentOS kernel compatible with IBM's 3590 tape driver? István -- 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
