Re: What distribution and why?
Kevin, does MQ mean WebSphere MQ? We are working with WebSphere MQ on SUSE for several years and it works fine. Regards Hubert -Ursprüngliche Nachricht- Von: Linux on 390 Port LINUX-390@VM.MARIST.EDU Gesendet: 14.04.08 12:36:08 An: LINUX-390@VM.MARIST.EDU Betreff: Re: What distribution and why? We use RHEL and if I remember correctly (I don't work on the zLinux project directly) it was to do with RHEL compatibility with some other software at the time we started (several years ago). Maybe it was MQ, although not sure. If it is important I can ask the folks that do work on it. K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Thursday, April 10, 2008 10:35 AM To: LINUX-390@VM.MARIST.EDU Subject: What distribution and why? We¹re looking at the costs and effort of converting our installation from SuSE SLES to RedHat RHEL on the zSeries, and I¹m wondering what others are running, and why they chose the particular distribution. All comments are welcome, on or off list; I just want to be sure we¹re not backing ourselves into the room¹s other corner I know this has been discussed before, but times change, and maybe a headcount is in order again. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. -- 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: What distribution and why?
We use RHEL and if I remember correctly (I don't work on the zLinux project directly) it was to do with RHEL compatibility with some other software at the time we started (several years ago). Maybe it was MQ, although not sure. If it is important I can ask the folks that do work on it. K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Thursday, April 10, 2008 10:35 AM To: LINUX-390@VM.MARIST.EDU Subject: What distribution and why? We¹re looking at the costs and effort of converting our installation from SuSE SLES to RedHat RHEL on the zSeries, and I¹m wondering what others are running, and why they chose the particular distribution. All comments are welcome, on or off list; I just want to be sure we¹re not backing ourselves into the room¹s other corner I know this has been discussed before, but times change, and maybe a headcount is in order again. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. -- 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: What distribution and why?
Mark is right in that he is much more active in this forum an RH even though Brad does pop in sometimes. Not sure that this is a deciding factor or not...I'm sure there are more important factors. Having said that, I'm sure Mark has helped MANY people in this list. K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, April 11, 2008 1:22 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: What distribution and why? On Thu, Apr 10, 2008 at 10:35 AM, in message [EMAIL PROTECTED], RPN01 [EMAIL PROTECTED] wrote: -snip- I know this has been discussed before, but times change, and maybe a headcount is in order again. From what I've been told by people who would know, it's about 90-95%/5-10%, depending on whether you count customers or actual systems. Based on the near-deafening silence in this mailing list when RH specific questions are asked that seems likely to be correct. (Along with David Boyes, I also want to acknowledge Brad Hinson for being active in the list. This community and the industry in general needs that kind of participation from all of the distribution providers.) 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: What distribution and why?
Hubert, No, it doesn't. We do use MQ only and have our own CICS adapters to directly manipulate the queues. From talking to one of the zLinux developers this morning, he is not sure he remembers the exact reasons. Message Broker springs to mind because we did play with that for a while before rejecting it for use here. The other thing that he thought may have played into the equation is that the FBI already used RH products on the desktop, so the support issue may have been easier to deal with as there was an existing agreement with RH. The thing that this topic may have raised is that (at least back then) not all products necessarily play with each other. I'm not sure whether that is still true but wouldn't mind betting that it is. Regards, K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hubert Kleinmanns Sent: Monday, April 14, 2008 6:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: What distribution and why? Kevin, does MQ mean WebSphere MQ? We are working with WebSphere MQ on SUSE for several years and it works fine. Regards Hubert -Ursprüngliche Nachricht- Von: Linux on 390 Port LINUX-390@VM.MARIST.EDU Gesendet: 14.04.08 12:36:08 An: LINUX-390@VM.MARIST.EDU Betreff: Re: What distribution and why? We use RHEL and if I remember correctly (I don't work on the zLinux project directly) it was to do with RHEL compatibility with some other software at the time we started (several years ago). Maybe it was MQ, although not sure. If it is important I can ask the folks that do work on it. K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Thursday, April 10, 2008 10:35 AM To: LINUX-390@VM.MARIST.EDU Subject: What distribution and why? We¹re looking at the costs and effort of converting our installation from SuSE SLES to RedHat RHEL on the zSeries, and I¹m wondering what others are running, and why they chose the particular distribution. All comments are welcome, on or off list; I just want to be sure we¹re not backing ourselves into the room¹s other corner I know this has been discussed before, but times change, and maybe a headcount is in order again. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: What distribution and why?
Kevin, what's exactly is your problem? As I told we are working with WebSphere MQ without any problems on SLES10 and it worked before on SLES8 (we did not test it on SLES9). Possibly your own CICS adapters interfere with some other stuff on SUSE, which is not installed on RH. The WebSphere Message Broker comes with its own MQ queue manager, so maybe you did not remove everything properly before installing Websphere MQ (this could be a SUSE specifc issue, but I do not think so). Of course the packages which come with RH or SUSE may affect other applications. We had a problem using OpenREXX and WebSphere Application Server on SLES9 ... Last question: What do you mean with MQ only? Regards Hubert -Ursprüngliche Nachricht- Von: Linux on 390 Port LINUX-390@VM.MARIST.EDU Gesendet: 14.04.08 13:58:03 An: LINUX-390@VM.MARIST.EDU Betreff: Re: What distribution and why? Hubert, No, it doesn't. We do use MQ only and have our own CICS adapters to directly manipulate the queues. From talking to one of the zLinux developers this morning, he is not sure he remembers the exact reasons. Message Broker springs to mind because we did play with that for a while before rejecting it for use here. The other thing that he thought may have played into the equation is that the FBI already used RH products on the desktop, so the support issue may have been easier to deal with as there was an existing agreement with RH. The thing that this topic may have raised is that (at least back then) not all products necessarily play with each other. I'm not sure whether that is still true but wouldn't mind betting that it is. Regards, K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hubert Kleinmanns Sent: Monday, April 14, 2008 6:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: What distribution and why? Kevin, does MQ mean WebSphere MQ? We are working with WebSphere MQ on SUSE for several years and it works fine. Regards Hubert -Ursprüngliche Nachricht- Von: Linux on 390 Port LINUX-390@VM.MARIST.EDU Gesendet: 14.04.08 12:36:08 An: LINUX-390@VM.MARIST.EDU Betreff: Re: What distribution and why? We use RHEL and if I remember correctly (I don't work on the zLinux project directly) it was to do with RHEL compatibility with some other software at the time we started (several years ago). Maybe it was MQ, although not sure. If it is important I can ask the folks that do work on it. K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Thursday, April 10, 2008 10:35 AM To: LINUX-390@VM.MARIST.EDU Subject: What distribution and why? We¹re looking at the costs and effort of converting our installation from SuSE SLES to RedHat RHEL on the zSeries, and I¹m wondering what others are running, and why they chose the particular distribution. All comments are welcome, on or off list; I just want to be sure we¹re not backing ourselves into the room¹s other corner I know this has been discussed before, but times change, and maybe a headcount is in order again. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- Hubert Kleinmanns Beratung / Schulung / Projektleitung Chairman der WG WebSphere MQ and Business Integration in der GSE, deutsche Region. Tel.: +49 (0) 60 78 / 7 12 21 Fax: +49 (0) 60 78 / 7 12 25 Mobil: +49 (0) 178 / 6 97 22 54 Web: www.kleinmanns.eu GSE: www.gsenet.de -- For LINUX-390 subscribe / signoff /
Re: What distribution and why?
Hubert, We don't have a problem...I was only replying to an inquiry from Robert Nix where he asked what distro people used and why. What I was saying was some backup to why we use RHEL. Our CICS adapters are totally separate from the zLinux code (which runs under z/VM), so no interference possible there. The only interface between the CICS adapters and our zLinux code is via MQ Series queues. By MQ only, I mean that we do not have all of Websphere installed. Our adapters do native MQGETs, MQWPUTs etc. Regards, Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hubert Kleinmanns Sent: Monday, April 14, 2008 8:36 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: What distribution and why? Kevin, what's exactly is your problem? As I told we are working with WebSphere MQ without any problems on SLES10 and it worked before on SLES8 (we did not test it on SLES9). Possibly your own CICS adapters interfere with some other stuff on SUSE, which is not installed on RH. The WebSphere Message Broker comes with its own MQ queue manager, so maybe you did not remove everything properly before installing Websphere MQ (this could be a SUSE specifc issue, but I do not think so). Of course the packages which come with RH or SUSE may affect other applications. We had a problem using OpenREXX and WebSphere Application Server on SLES9 ... Last question: What do you mean with MQ only? Regards Hubert -Ursprüngliche Nachricht- Von: Linux on 390 Port LINUX-390@VM.MARIST.EDU Gesendet: 14.04.08 13:58:03 An: LINUX-390@VM.MARIST.EDU Betreff: Re: What distribution and why? Hubert, No, it doesn't. We do use MQ only and have our own CICS adapters to directly manipulate the queues. From talking to one of the zLinux developers this morning, he is not sure he remembers the exact reasons. Message Broker springs to mind because we did play with that for a while before rejecting it for use here. The other thing that he thought may have played into the equation is that the FBI already used RH products on the desktop, so the support issue may have been easier to deal with as there was an existing agreement with RH. The thing that this topic may have raised is that (at least back then) not all products necessarily play with each other. I'm not sure whether that is still true but wouldn't mind betting that it is. Regards, K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hubert Kleinmanns Sent: Monday, April 14, 2008 6:59 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: What distribution and why? Kevin, does MQ mean WebSphere MQ? We are working with WebSphere MQ on SUSE for several years and it works fine. Regards Hubert -Ursprüngliche Nachricht- Von: Linux on 390 Port LINUX-390@VM.MARIST.EDU Gesendet: 14.04.08 12:36:08 An: LINUX-390@VM.MARIST.EDU Betreff: Re: What distribution and why? We use RHEL and if I remember correctly (I don't work on the zLinux project directly) it was to do with RHEL compatibility with some other software at the time we started (several years ago). Maybe it was MQ, although not sure. If it is important I can ask the folks that do work on it. K -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of RPN01 Sent: Thursday, April 10, 2008 10:35 AM To: LINUX-390@VM.MARIST.EDU Subject: What distribution and why? We¹re looking at the costs and effort of converting our installation from SuSE SLES to RedHat RHEL on the zSeries, and I¹m wondering what others are running, and why they chose the particular distribution. All comments are welcome, on or off list; I just want to be sure we¹re not backing ourselves into the room¹s other corner I know this has been discussed before, but times change, and maybe a headcount is in order again. -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. -- 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
Re: What distribution and why?
what's exactly is your problem? Easy, easy... this isn't IBM-MAIN or LKML. Play nice. Last question: What do you mean with MQ only? Probably has to do with the recent (and IMHO not beneficial) renaming of MQ to be part of the Websphere megalith. Not everyone got the memo on the new name, and the phrase Websphere MQ commonly still parsed as Websphere + MQ, not just the pure MQ we used to have to cope with. IBM: is it really beneficial to push things that you've built a name for into association with things that pretty much aren't more than peripherally related, and have some negative connotations as well? *sigh* Some things normal mankind just isn't meant to know, I guess. Another example of marketing wonks doing something to make understanding what we do more difficult. Methinks a good spanking is in order. -- db -- 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: What distribution and why?
David, I didn't think that people weren't playing nice. But, your observation about the megalith is right on. We don't use Websphere, per se, here but we do use MQ Series queues and adapters running under CICS to manipulate the queues. I'm not sure why Hubert thought I had a problem, maybe didn't read the email from the bottom? I agree with the spanking part g. Regards, Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Monday, April 14, 2008 8:48 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: What distribution and why? what's exactly is your problem? Easy, easy... this isn't IBM-MAIN or LKML. Play nice. Last question: What do you mean with MQ only? Probably has to do with the recent (and IMHO not beneficial) renaming of MQ to be part of the Websphere megalith. Not everyone got the memo on the new name, and the phrase Websphere MQ commonly still parsed as Websphere + MQ, not just the pure MQ we used to have to cope with. IBM: is it really beneficial to push things that you've built a name for into association with things that pretty much aren't more than peripherally related, and have some negative connotations as well? *sigh* Some things normal mankind just isn't meant to know, I guess. Another example of marketing wonks doing something to make understanding what we do more difficult. Methinks a good spanking is in order. -- db -- 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: What distribution and why?
Hi, what's exactly is your problem? I just want to understand, what may be going wrong and - possibly - provide a solution. Not everyone got the memo on the new name, and the phrase Websphere MQ commonly still parsed as Websphere + MQ. I know, but there are many other queuing products and I wanted to clarify, that we are talking about the IBM product. When MQ was renamed to WebSphere MQ I found a mail in a mailing list, where somebody made a guess, in the future IBM would have only one product, which is either name WebSphere for Tivoli or Tivoli for WebSphere :-D Back to the subject: I would prefer SUSE, because I am working since several years with it - starting with version 2.0 or so. I do not think, that SUSE is really better or worse than RH or Debian or Marist or whatever - but I like it ;-). Regards Hubert -Ursprüngliche Nachricht- Von: Linux on 390 Port LINUX-390@VM.MARIST.EDU Gesendet: 14.04.08 14:50:53 An: LINUX-390@VM.MARIST.EDU Betreff: Re: What distribution and why? what's exactly is your problem? Easy, easy... this isn't IBM-MAIN or LKML. Play nice. Last question: What do you mean with MQ only? Probably has to do with the recent (and IMHO not beneficial) renaming of MQ to be part of the Websphere megalith. Not everyone got the memo on the new name, and the phrase Websphere MQ commonly still parsed as Websphere + MQ, not just the pure MQ we used to have to cope with. IBM: is it really beneficial to push things that you've built a name for into association with things that pretty much aren't more than peripherally related, and have some negative connotations as well? *sigh* Some things normal mankind just isn't meant to know, I guess. Another example of marketing wonks doing something to make understanding what we do more difficult. Methinks a good spanking is in order. -- db -- 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 -- Hubert Kleinmanns Beratung / Schulung / Projektleitung Chairman der WG WebSphere MQ and Business Integration in der GSE, deutsche Region. Tel.: +49 (0) 60 78 / 7 12 21 Fax: +49 (0) 60 78 / 7 12 25 Mobil: +49 (0) 178 / 6 97 22 54 Web: www.kleinmanns.eu GSE: www.gsenet.de -- 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: What distribution and why?
On Mon, Apr 14, 2008 at 2:43 PM, Evans, Kevin R [EMAIL PROTECTED] wrote: We don't have a problem...I was only replying to an inquiry from Robert Nix where he asked what distro people used and why. What I was saying was some backup to why we use RHEL. We see that Red Hat is more strict than Novell in wanting things to be in the official kernel sources before they include it. There's pros and cons in that approach. If that particular feature is needed for some middleware, it may be for a while it's only running on SUSE. Rob -- 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: What distribution and why?
Kevin, maybe I misunderstood your mail, but you wrote We use RHEL and if I remember correctly (I don't work on the zLinux project directly) it was to do with RHEL compatibility with some other software at the time we started (several years ago). Maybe it was MQ, I am working several years with MQ and I only wanted to understand, what may be different on SUSE and RH running MQ. But now I think, this question will not be answered here. Regards Hubert -Ursprüngliche Nachricht- Von: Linux on 390 Port LINUX-390@VM.MARIST.EDU Gesendet: 14.04.08 15:06:56 An: LINUX-390@VM.MARIST.EDU Betreff: Re: What distribution and why? David, I didn't think that people weren't playing nice. But, your observation about the megalith is right on. We don't use Websphere, per se, here but we do use MQ Series queues and adapters running under CICS to manipulate the queues. I'm not sure why Hubert thought I had a problem, maybe didn't read the email from the bottom? I agree with the spanking part g. Regards, Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Monday, April 14, 2008 8:48 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: What distribution and why? what's exactly is your problem? Easy, easy... this isn't IBM-MAIN or LKML. Play nice. Last question: What do you mean with MQ only? Probably has to do with the recent (and IMHO not beneficial) renaming of MQ to be part of the Websphere megalith. Not everyone got the memo on the new name, and the phrase Websphere MQ commonly still parsed as Websphere + MQ, not just the pure MQ we used to have to cope with. IBM: is it really beneficial to push things that you've built a name for into association with things that pretty much aren't more than peripherally related, and have some negative connotations as well? *sigh* Some things normal mankind just isn't meant to know, I guess. Another example of marketing wonks doing something to make understanding what we do more difficult. Methinks a good spanking is in order. -- db -- 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 -- Hubert Kleinmanns Beratung / Schulung / Projektleitung Chairman der WG WebSphere MQ and Business Integration in der GSE, deutsche Region. Tel.: +49 (0) 60 78 / 7 12 21 Fax: +49 (0) 60 78 / 7 12 25 Mobil: +49 (0) 178 / 6 97 22 54 Web: www.kleinmanns.eu GSE: www.gsenet.de -- 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: What distribution and why?
David Boyes wrote: Probably has to do with the recent (and IMHO not beneficial) renaming of MQ to be part of the Websphere megalith. Not everyone got the memo on the new name, and the phrase Websphere MQ commonly still parsed as Websphere + MQ, not just the pure MQ we used to have to cope with. IBM: is it really beneficial to push things that you've built a name for into It's not just IBM and it's not just USA: Thrive used to be a product: http://yates.com.au/brand/Thrive.asp So did blitzem http://yates.com.au/brand/Blitzem.asp ratsak http://yates.com.au/brand/Ratsak.asp zero http://yates.com.au/brand/Zero.asp dynamic lifter http://yates.com.au/brand/DynamicLifter.asp -- 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: What distribution and why?
As I said, though, I don't have a problem...but thanks for trying to help! Regards, kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hubert Kleinmanns Sent: Monday, April 14, 2008 9:23 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: What distribution and why? Hi, what's exactly is your problem? I just want to understand, what may be going wrong and - possibly - provide a solution. Not everyone got the memo on the new name, and the phrase Websphere MQ commonly still parsed as Websphere + MQ. I know, but there are many other queuing products and I wanted to clarify, that we are talking about the IBM product. When MQ was renamed to WebSphere MQ I found a mail in a mailing list, where somebody made a guess, in the future IBM would have only one product, which is either name WebSphere for Tivoli or Tivoli for WebSphere :-D Back to the subject: I would prefer SUSE, because I am working since several years with it - starting with version 2.0 or so. I do not think, that SUSE is really better or worse than RH or Debian or Marist or whatever - but I like it ;-). Regards Hubert -Ursprüngliche Nachricht- Von: Linux on 390 Port LINUX-390@VM.MARIST.EDU Gesendet: 14.04.08 14:50:53 An: LINUX-390@VM.MARIST.EDU Betreff: Re: What distribution and why? what's exactly is your problem? Easy, easy... this isn't IBM-MAIN or LKML. Play nice. Last question: What do you mean with MQ only? Probably has to do with the recent (and IMHO not beneficial) renaming of MQ to be part of the Websphere megalith. Not everyone got the memo on the new name, and the phrase Websphere MQ commonly still parsed as Websphere + MQ, not just the pure MQ we used to have to cope with. IBM: is it really beneficial to push things that you've built a name for into association with things that pretty much aren't more than peripherally related, and have some negative connotations as well? *sigh* Some things normal mankind just isn't meant to know, I guess. Another example of marketing wonks doing something to make understanding what we do more difficult. Methinks a good spanking is in order. -- db -- 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 -- Hubert Kleinmanns Beratung / Schulung / Projektleitung Chairman der WG WebSphere MQ and Business Integration in der GSE, deutsche Region. Tel.: +49 (0) 60 78 / 7 12 21 Fax: +49 (0) 60 78 / 7 12 25 Mobil: +49 (0) 178 / 6 97 22 54 Web: www.kleinmanns.eu GSE: www.gsenet.de -- 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: What distribution and why?
Hi Hubert, I'm not sure that we even remember the exact issue g. However, once we settled on RHEL (based on those original issues which would have been 2 to 2.5 years ago), we settled on RHEL and are now invested in it. Probably too hard to change now even if we wanted to! Regards, Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Hubert Kleinmanns Sent: Monday, April 14, 2008 9:29 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: What distribution and why? Kevin, maybe I misunderstood your mail, but you wrote We use RHEL and if I remember correctly (I don't work on the zLinux project directly) it was to do with RHEL compatibility with some other software at the time we started (several years ago). Maybe it was MQ, I am working several years with MQ and I only wanted to understand, what may be different on SUSE and RH running MQ. But now I think, this question will not be answered here. Regards Hubert -Ursprüngliche Nachricht- Von: Linux on 390 Port LINUX-390@VM.MARIST.EDU Gesendet: 14.04.08 15:06:56 An: LINUX-390@VM.MARIST.EDU Betreff: Re: What distribution and why? David, I didn't think that people weren't playing nice. But, your observation about the megalith is right on. We don't use Websphere, per se, here but we do use MQ Series queues and adapters running under CICS to manipulate the queues. I'm not sure why Hubert thought I had a problem, maybe didn't read the email from the bottom? I agree with the spanking part g. Regards, Kevin -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Monday, April 14, 2008 8:48 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: What distribution and why? what's exactly is your problem? Easy, easy... this isn't IBM-MAIN or LKML. Play nice. Last question: What do you mean with MQ only? Probably has to do with the recent (and IMHO not beneficial) renaming of MQ to be part of the Websphere megalith. Not everyone got the memo on the new name, and the phrase Websphere MQ commonly still parsed as Websphere + MQ, not just the pure MQ we used to have to cope with. IBM: is it really beneficial to push things that you've built a name for into association with things that pretty much aren't more than peripherally related, and have some negative connotations as well? *sigh* Some things normal mankind just isn't meant to know, I guess. Another example of marketing wonks doing something to make understanding what we do more difficult. Methinks a good spanking is in order. -- db -- 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 -- Hubert Kleinmanns Beratung / Schulung / Projektleitung Chairman der WG WebSphere MQ and Business Integration in der GSE, deutsche Region. Tel.: +49 (0) 60 78 / 7 12 21 Fax: +49 (0) 60 78 / 7 12 25 Mobil: +49 (0) 178 / 6 97 22 54 Web: www.kleinmanns.eu GSE: www.gsenet.de -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Adding LCS Ethernet on a z9 for z/Linux LPAR (NO VM)
Hi, We are trying to add another OSA LCS Ethernet on our z/9 z/Linux LPAR (SLES 10 sp1) CHP F1 is defined in IODF as OSE Looking at some PDFs I see that it say that we only have to do the following: echo 0.0.f100,0.0.f101 /sys/bus/ccwgroup/drivers/lcs/group 1. Without an echo -n we get an echo invalid argument 2. With echo -n we get no message and nothing build in the appropriate /sys/bus/ccwgroup areas. Next we tried YAST, we rebooted and it f100 times out. F200 is already an LCS, but we want to convert it to QETH as soon I we can get this second LCS Ethernet working. There is NO OAT for f100. I have done an zipl -c /etc/zipl.conf Here is my /etc/zipl.conf [defaultboot] defaultmenu = menu [SLES_10_SP1] image = /boot/image-2.6.16.54-0.2.3-default target = /boot/zipl ramdisk = /boot/initrd-2.6.16.54-0.2.3-default,0x100 # parameters = root=/dev/disk/by-id/ccw-IBM.7500029646.3800.2f-part2 TERM=dumb parameters = dasd=382f,392f root=/dev/disk/by-id/ccw-IBM.7500029646.3800.2f-part2 TERM=dumb :menu default = 1 prompt = 1 target = /boot/zipl timeout = 15 1 = ipl ###Don't change this comment - YaST2 identifier: Original name: ipl### [ipl] image = /boot/image target = /boot/zipl ramdisk = /boot/initrd,0x100 #parameters = root=/dev/disk/by-id/ccw-IBM.7500029646.3800.2f-part2 TERM=dumb parameters = dasd=382f,392f root=/dev/disk/by-id/ccw-IBM.7500029646.3800.2f-part2 TERM=dumb cio_ignore=all,!0.0.382F,!0.0.392F,!0.0.F100-0.0.F11E,!0.0.F200-0.0.F202,!0.0.C000-0.0.C01F,!0.0.C100 -0.0.C11F Sam Bass 254-771-7212 Sr z/OS Systems Specialist -- 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: recover root password
One way to to fix it is to use your rescue system to mount the amnesiac system's / fs at /mnt, chroot to /mnt and run passwd to change root's pw. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Miguel Roman Sent: Monday, April 14, 2008 11:03 AM To: LINUX-390@VM.MARIST.EDU Subject: recover root password Hello, We are running Suse Linux 9.3 (64 bit) under z/VM 5.1. One of the administrators changed the root password and forgot the password. Does anyone know how to recover the root password? Thanks. Miguel A Roman. -- 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
recover root password
Hello, We are running Suse Linux 9.3 (64 bit) under z/VM 5.1. One of the administrators changed the root password and forgot the password. Does anyone know how to recover the root password? Thanks. Miguel A Roman. -- 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: recover root password
On Mon, Apr 14, 2008 at 11:03 AM, in message [EMAIL PROTECTED], Miguel Roman [EMAIL PROTECTED] wrote: Hello, We are running Suse Linux 9.3 (64 bit) under z/VM 5.1. One of the administrators changed the root password and forgot the password. Does anyone know how to recover the root password? Thanks. Boot your installation kernel and initrd, and get your network up. Choose the SSH install method. SSH in, activate your root file system disk. Mount your root file system on /mnt chroot /mnt Change the password Exit the chroot environment Unmount your root file system Re-IPL from DASD 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: recover root password
Does anyone have full sudo? Then you could just sudo su - passwd And change it. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Miguel Roman Sent: Monday, April 14, 2008 8:03 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] recover root password Hello, We are running Suse Linux 9.3 (64 bit) under z/VM 5.1. One of the administrators changed the root password and forgot the password. Does anyone know how to recover the root password? Thanks. Miguel A Roman. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Adding LCS Ethernet on a z9 for z/Linux LPAR (NO VM)
On Mon, Apr 14, 2008 at 10:48 AM, in message [EMAIL PROTECTED], Sam Bass [EMAIL PROTECTED] wrote: -snip- Looking at some PDFs I see that it say that we only have to do the following: echo 0.0.f100,0.0.f101 /sys/bus/ccwgroup/drivers/lcs/group 1.Without an echo -n we get an echo invalid argument That shouldn't be the case. I just tested on my system with an echo 0.0.f100,0.0.f101 command, and no redirection, and I got no error message. 2.With echo -n we get no message and nothing build in the appropriate /sys/bus/ccwgroup areas. This may be a result of the -n switch, but I have no idea. Does anything show up if you do a dmesg command? Next we tried YAST, we rebooted and it f100 times out. When you went into YaST, were the f100 and f101 devices listed already with a not configured under the IP Address column? F200 is already an LCS, but we want to convert it to QETH as soon I we can get this second LCS Ethernet working. There is NO OAT for f100. Just out of idle curiosity, why are you using LCS at all? Seems sorta, umm, antique. 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: recover root password
Miguel, For things like this VM is the Bomb! Just make the root drive from the locked server available for a different Lunix guest, (making sure the one with the locked out root account is down) and boot the 2nd guest. Then mount the new disk as /mnt and cd /mnt/etc Then edit the /mnt/etc/shadow file and remove the password from the root account. Then undo all the previous steps and boot. Fixed. (this is kind of a quick and dirty explanation, I can do better if you'd like) David K. Marcy Cortes [EMAIL PROTECTED] ellsfargo.com To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: recover root password 04/14/2008 11:30 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Does anyone have full sudo? Then you could just sudo su - passwd And change it. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Miguel Roman Sent: Monday, April 14, 2008 8:03 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] recover root password Hello, We are running Suse Linux 9.3 (64 bit) under z/VM 5.1. One of the administrators changed the root password and forgot the password. Does anyone know how to recover the root password? Thanks. Miguel A Roman. -- 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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
Hmm, no responses? -- 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: Wednesday, April 09, 2008 9:18 AM To: Kelly F. Hickel; 'Linux on 390 Port' Cc: Ray Mullins Subject: RE: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC? Here's a blast from the past, this has cropped up again. After a recent full shutdown of our z9, the linux lpar (Centos 4.4 s390x) wouldn't boot, seems like the root volume group may be a bit off. So, I decided to try and boot from the installer image to see if I could repair it, but when I use ht e0.0.0E200,0.0.E201,0.0.E202 addr for the qeth device (blank line for the portname, but I've also tried CHIP00), it fails to come up with the messages: Qeth: loading qeth S/390 OSA-Express driver Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device When I was having this problem last April during the initial install, it went away when the folks that set up the hardware suggested using an OSA adapter that wasn't in use by any other LPARs, I've had folks check and e200 still isn't being used by anything else. I have no idea how to even begin tracking down what the problem is, does anyone have any ideas? -- 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: Monday, April 09, 2007 8:54 AM To: Linux on 390 Port Subject: RE: FW: any help installing 4.4 for s390 (or s390x) on Z9- BC? Brad, I looked in there and didn't like what I saw, talked to one orf the guys that configured the hardware, he said to try a different OSA that wasn't shared with Z/os, with addrs E200-E202, and that worked! Thanks everyone!! -- Kelly F. Hickel Senior Software Architect MQSoftware, Inc 952.345.8677 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Saturday, April 07, 2007 12:28 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9- BC? [snip] I've tried what you wrote above with the same results. As far as the addresses, I'm not positive, but that's what I was told. Presumably there's some way, using the HMC to verify the addrs for LP7, but I don't know how, so if you could give me some pointers, that would be great. You'll have to check the device definitions in the IOCDS config (Single Object Operations - CPC Config menu - Input/Output Configuration - Options[Export Source File]). In ours, we have this line: IODEVICE ADDRESS=(800,010),CUNUMBR=(0800),UNIT=OSA Which means there are 10 devices starting at base address 0800 (0800-0809). - -- - -- 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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
We aren't running VM, You really should fix that. But, anyway. 8-) I could repair it, but when I use ht e0.0.0E200,0.0.E201,0.0.E202 addr for the qeth device (blank line for the portname, but I've also tried CHIP00), it fails to come up with the messages: Qeth: loading qeth S/390 OSA-Express driver Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device That version of CentOS is probably old enough that it still requires a portname for the OSA port to initialize correctly. There were later RPM packages for the OSA drivers that removed that feature. If you're using an OSA that is shared with a z/OS system, the portnames have to match for all systems using that OSA. Is this a base Centos 4 install, or did you apply any maintenance to it? -- 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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
-Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Monday, April 14, 2008 11:22 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC? We aren't running VM, You really should fix that. But, anyway. 8-) I could repair it, but when I use ht e0.0.0E200,0.0.E201,0.0.E202 addr for the qeth device (blank line for the portname, but I've also tried CHIP00), it fails to come up with the messages: Qeth: loading qeth S/390 OSA-Express driver Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device That version of CentOS is probably old enough that it still requires a portname for the OSA port to initialize correctly. There were later RPM packages for the OSA drivers that removed that feature. If you're using an OSA that is shared with a z/OS system, the portnames have to match for all systems using that OSA. [Kelly F. Hickel] I was told that it didn't need it (and the prompt itself says that it is optional). That address isn't supposed to be in use by any other LPAR. Is there a newer released version of CentOS for s390x? I went looking for a v5 mirror but didn't find one and stumbled on a message suggesting that there wasn't one. Is this a base Centos 4 install, or did you apply any maintenance to it? [Kelly F. Hickel] Hmm, it's started as base 4.4, but there had been a small amount of maintenance applied, IIRC. -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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
Are you coupling e200 to an osa? What does 'vmcp q nic' show (or #CP Q NIC at the VM console) .. ? Scott On Mon, Apr 14, 2008 at 10:05 AM, Kelly F. Hickel [EMAIL PROTECTED] wrote: Hmm, no responses? -- 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: Wednesday, April 09, 2008 9:18 AM To: Kelly F. Hickel; 'Linux on 390 Port' Cc: Ray Mullins Subject: RE: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC? Here's a blast from the past, this has cropped up again. After a recent full shutdown of our z9, the linux lpar (Centos 4.4 s390x) wouldn't boot, seems like the root volume group may be a bit off. So, I decided to try and boot from the installer image to see if I could repair it, but when I use ht e0.0.0E200,0.0.E201,0.0.E202 addr for the qeth device (blank line for the portname, but I've also tried CHIP00), it fails to come up with the messages: Qeth: loading qeth S/390 OSA-Express driver Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device When I was having this problem last April during the initial install, it went away when the folks that set up the hardware suggested using an OSA adapter that wasn't in use by any other LPARs, I've had folks check and e200 still isn't being used by anything else. I have no idea how to even begin tracking down what the problem is, does anyone have any ideas? -- 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: Monday, April 09, 2007 8:54 AM To: Linux on 390 Port Subject: RE: FW: any help installing 4.4 for s390 (or s390x) on Z9- BC? Brad, I looked in there and didn't like what I saw, talked to one orf the guys that configured the hardware, he said to try a different OSA that wasn't shared with Z/os, with addrs E200-E202, and that worked! Thanks everyone!! -- Kelly F. Hickel Senior Software Architect MQSoftware, Inc 952.345.8677 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Saturday, April 07, 2007 12:28 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9- BC? [snip] I've tried what you wrote above with the same results. As far as the addresses, I'm not positive, but that's what I was told. Presumably there's some way, using the HMC to verify the addrs for LP7, but I don't know how, so if you could give me some pointers, that would be great. You'll have to check the device definitions in the IOCDS config (Single Object Operations - CPC Config menu - Input/Output Configuration - Options[Export Source File]). In ours, we have this line: IODEVICE ADDRESS=(800,010),CUNUMBR=(0800),UNIT=OSA Which means there are 10 devices starting at base address 0800 (0800-0809). - -- - -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX- 390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 --- -- - For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX- 390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
Scott, We aren't running VM, e200 is the addr of an OSA adapter. -- 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 Scott Rohling Sent: Monday, April 14, 2008 11:09 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC? Are you coupling e200 to an osa? What does 'vmcp q nic' show (or #CP Q NIC at the VM console) .. ? Scott On Mon, Apr 14, 2008 at 10:05 AM, Kelly F. Hickel [EMAIL PROTECTED] wrote: Hmm, no responses? -- 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: Wednesday, April 09, 2008 9:18 AM To: Kelly F. Hickel; 'Linux on 390 Port' Cc: Ray Mullins Subject: RE: FW: any help installing 4.4 for s390 (or s390x) on Z9- BC? Here's a blast from the past, this has cropped up again. After a recent full shutdown of our z9, the linux lpar (Centos 4.4 s390x) wouldn't boot, seems like the root volume group may be a bit off. So, I decided to try and boot from the installer image to see if I could repair it, but when I use ht e0.0.0E200,0.0.E201,0.0.E202 addr for the qeth device (blank line for the portname, but I've also tried CHIP00), it fails to come up with the messages: Qeth: loading qeth S/390 OSA-Express driver Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device When I was having this problem last April during the initial install, it went away when the folks that set up the hardware suggested using an OSA adapter that wasn't in use by any other LPARs, I've had folks check and e200 still isn't being used by anything else. I have no idea how to even begin tracking down what the problem is, does anyone have any ideas? -- 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: Monday, April 09, 2007 8:54 AM To: Linux on 390 Port Subject: RE: FW: any help installing 4.4 for s390 (or s390x) on Z9- BC? Brad, I looked in there and didn't like what I saw, talked to one orf the guys that configured the hardware, he said to try a different OSA that wasn't shared with Z/os, with addrs E200-E202, and that worked! Thanks everyone!! -- Kelly F. Hickel Senior Software Architect MQSoftware, Inc 952.345.8677 [EMAIL PROTECTED] -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Saturday, April 07, 2007 12:28 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9- BC? [snip] I've tried what you wrote above with the same results. As far as the addresses, I'm not positive, but that's what I was told. Presumably there's some way, using the HMC to verify the addrs for LP7, but I don't know how, so if you could give me some pointers, that would be great. You'll have to check the device definitions in the IOCDS config (Single Object Operations - CPC Config menu - Input/Output Configuration - Options[Export Source File]). In ours, we have this line: IODEVICE ADDRESS=(800,010),CUNUMBR=(0800),UNIT=OSA Which means there are 10 devices starting at base address 0800 (0800-0809). - -- - -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX- 390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 --- -- - For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX- 390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 - - For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff /
Re: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
[Kelly F. Hickel] I was told that it didn't need it (and the prompt itself says that it is optional). That address isn't supposed to be in use by any other LPAR. You don't need a portname if your OSAs are at a certain microcode level or if none of the OSes sharing the OSA are z/OS (I think that z/OS still cares about the portname parm for some important reason related to sysplexes). I would think that a z9BC should be above that ucode level, but you might check that out. Is there a newer released version of CentOS for s390x? I went looking for a v5 mirror but didn't find one and stumbled on a message suggesting that there wasn't one. I don't know of one, but haven't really looked either. Is this a base Centos 4 install, or did you apply any maintenance to it? [Kelly F. Hickel] Hmm, it's started as base 4.4, but there had been a small amount of maintenance applied, IIRC. Dunno. All our Centos systems run under VM, so we've never had this problem with them. Sounds like your filesystem may also have gotten corrupted along the way -- does a fsck on the root filesystem show anything that might need fixing? -- 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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
[Kelly F. Hickel] I was told that it didn't need it (and the prompt itself says that it is optional). That address isn't supposed to be in use by any other LPAR. You don't need a portname if your OSAs are at a certain microcode level or if none of the OSes sharing the OSA are z/OS (I think that z/OS still cares about the portname parm for some important reason related to sysplexes). I would think that a z9BC should be above that ucode level, but you might check that out. Is there a newer released version of CentOS for s390x? I went looking for a v5 mirror but didn't find one and stumbled on a message suggesting that there wasn't one. I don't know of one, but haven't really looked either. Is this a base Centos 4 install, or did you apply any maintenance to it? [Kelly F. Hickel] Hmm, it's started as base 4.4, but there had been a small amount of maintenance applied, IIRC. Dunno. All our Centos systems run under VM, so we've never had this problem with them. Sounds like your filesystem may also have gotten corrupted along the way -- does a fsck on the root filesystem show anything that might need fixing? [Kelly F. Hickel] Well, that's the problem, right? I mean I can't boot even single user mode to do a fsck, so I was going to try to use the install boot to look around, but I can't get it running far enough to allow me to log in remotely. I can't even reinstall cleanly, since I can't get the network adapter to work. -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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
Kelly, Does Centos support the ASCII emulator on the HMC of the z9BC? If so, then maybe you could use that as your terminal for entry. -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
-Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Monday, April 14, 2008 12:10 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC? Kelly, Does Centos support the ASCII emulator on the HMC of the z9BC? If so, then maybe you could use that as your terminal for entry. [Kelly F. Hickel] John, no, that doesn't seem to work. Only the Operating System Messages screen from the HMC allows me to see what's going on and respond to the boot prompts. -- 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: recover root password
Thank you all for the help. Miguel -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David K. Kelly Sent: Monday, April 14, 2008 11:43 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: recover root password Miguel, For things like this VM is the Bomb! Just make the root drive from the locked server available for a different Lunix guest, (making sure the one with the locked out root account is down) and boot the 2nd guest. Then mount the new disk as /mnt and cd /mnt/etc Then edit the /mnt/etc/shadow file and remove the password from the root account. Then undo all the previous steps and boot. Fixed. (this is kind of a quick and dirty explanation, I can do better if you'd like) David K. Marcy Cortes [EMAIL PROTECTED] ellsfargo.com To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: recover root password 04/14/2008 11:30 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Does anyone have full sudo? Then you could just sudo su - passwd And change it. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Miguel Roman Sent: Monday, April 14, 2008 8:03 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] recover root password Hello, We are running Suse Linux 9.3 (64 bit) under z/VM 5.1. One of the administrators changed the root password and forgot the password. Does anyone know how to recover the root password? Thanks. Miguel A Roman. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
Hi Kelly, Does dmesg show any qeth-related errors during bootup? Also, do you get any errors when you perform the steps manually? i.e: echo 0.0.e200,0.0.e201,0.0.e202 /sys/bus/ccwgroup/drivers/qeth/group echo 1 /sys/bus/ccwgroup/drivers/qeth/0.0.e200/online Lastly, are you using the OSA in layer2 (OPTIONS='layer2=1' in ifcfg-eth0) or layer3 (ARP=no in ifcfg-eth0) mode? -Brad On Mon, 2008-04-14 at 12:29 -0500, Kelly F. Hickel wrote: -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Monday, April 14, 2008 12:10 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC? Kelly, Does Centos support the ASCII emulator on the HMC of the z9BC? If so, then maybe you could use that as your terminal for entry. [Kelly F. Hickel] John, no, that doesn't seem to work. Only the Operating System Messages screen from the HMC allows me to see what's going on and respond to the boot prompts. -- 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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
-Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Monday, April 14, 2008 12:38 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC? Hi Kelly, Does dmesg show any qeth-related errors during bootup? Also, do you get any errors when you perform the steps manually? i.e: echo 0.0.e200,0.0.e201,0.0.e202 /sys/bus/ccwgroup/drivers/qeth/group echo 1 /sys/bus/ccwgroup/drivers/qeth/0.0.e200/online Lastly, are you using the OSA in layer2 (OPTIONS='layer2=1' in ifcfg-eth0) or layer3 (ARP=no in ifcfg-eth0) mode? -Brad Brad, I don't see any qeth related messages at all when trying to boot the installed image, but it may be failing due to volume group errors before it gets that far. It lists all the DASD addresses, then panics after the Activation logical volumes message with: Kernel panic - not syncing: Attempted to kill init! When trying to boot the installer via FTP, I get the messages below: Qeth: loading qeth S/390 OSA-Express driver Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device 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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
While there is no version 5 of Centos, you may or may not have luck trying to boot the Centos 4.6 installer. (along with what Brad Hinson recommended) ~Justin Kelly F. Hickel wrote: -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Monday, April 14, 2008 11:22 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC? We aren't running VM, You really should fix that. But, anyway. 8-) I could repair it, but when I use ht e0.0.0E200,0.0.E201,0.0.E202 addr for the qeth device (blank line for the portname, but I've also tried CHIP00), it fails to come up with the messages: Qeth: loading qeth S/390 OSA-Express driver Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device That version of CentOS is probably old enough that it still requires a portname for the OSA port to initialize correctly. There were later RPM packages for the OSA drivers that removed that feature. If you're using an OSA that is shared with a z/OS system, the portnames have to match for all systems using that OSA. [Kelly F. Hickel] I was told that it didn't need it (and the prompt itself says that it is optional). That address isn't supposed to be in use by any other LPAR. Is there a newer released version of CentOS for s390x? I went looking for a v5 mirror but didn't find one and stumbled on a message suggesting that there wasn't one. Is this a base Centos 4 install, or did you apply any maintenance to it? [Kelly F. Hickel] Hmm, it's started as base 4.4, but there had been a small amount of maintenance applied, IIRC. -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 -- 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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
-Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Monday, April 14, 2008 12:38 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9- BC? Hi Kelly, Does dmesg show any qeth-related errors during bootup? Also, do you get any errors when you perform the steps manually? i.e: echo 0.0.e200,0.0.e201,0.0.e202 /sys/bus/ccwgroup/drivers/qeth/group echo 1 /sys/bus/ccwgroup/drivers/qeth/0.0.e200/online Lastly, are you using the OSA in layer2 (OPTIONS='layer2=1' in ifcfg-eth0) or layer3 (ARP=no in ifcfg-eth0) mode? -Brad Brad, I don't see any qeth related messages at all when trying to boot the installed image, but it may be failing due to volume group errors before it gets that far. It lists all the DASD addresses, then panics after the Activation logical volumes message with: Kernel panic - not syncing: Attempted to kill init! When trying to boot the installer via FTP, I get the messages below: Qeth: loading qeth S/390 OSA-Express driver Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device Thanks, -Kelly Oops, I didn't answer your other questions. Basically, I can't get any version of Centos up far enough to start messing with options like these, at least, not in any way that I know of. -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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
-Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Justin Payne Sent: Monday, April 14, 2008 12:48 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC? While there is no version 5 of Centos, you may or may not have luck trying to boot the Centos 4.6 installer. (along with what Brad Hinson recommended) ~Justin Justin, I was thinking the same thing, I've started downloading it. Is there any better way to get it than just using wget to pull the whole s390x directory from a mirror? 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: recover root password
Would it be the wrong time to suggest that, once you have the system installed, up and running, nobody should ever log in as root, except in dire or unavoidable circumstances. Once you have the system, give your system administration group sudo all privs. Then just don't log into root at all. This gives you accountability for what is being done to your system; You can't tell who logged in as root (ok, you can tell what IP address they were from, but that person can say Hey! Somebody else used my jack...), but you can tell who is using sudo. Dire circumstances? Like when you need to log into a semi-brain dead system from the console. Or your normal authorization system (like LDAP) has given up the ghost. Unavoidable circumstances? Like when you need to install a product and it checks that you logged in as root; not that you are root now, but that you actually logged in to the root account. If you're the vendor, then shame on you! It shouldn't matter how I got to be root, and you shouldn't care either, just to install your program. In any case, don't log into root, and you avoid this type of problem. At best, someone will lock themselves out, which might actually be a good thing, given some people. And if you change root's password and forget, you have several semi-root people to call upon to easily fix your mistake. Of course, that doesn't mean that you don't need to change root's password from time to time; you still need to maintain the security and integrity of your system -- Robert P. Nix Mayo Foundation.~. RO-OE-5-55 200 First Street SW/V\ 507-284-0844 Rochester, MN 55905 /( )\ -^^-^^ In theory, theory and practice are the same, but in practice, theory and practice are different. On 4/14/08 10:42 AM, David K. Kelly [EMAIL PROTECTED] wrote: Miguel, For things like this VM is the Bomb! Just make the root drive from the locked server available for a different Lunix guest, (making sure the one with the locked out root account is down) and boot the 2nd guest. Then mount the new disk as /mnt and cd /mnt/etc Then edit the /mnt/etc/shadow file and remove the password from the root account. Then undo all the previous steps and boot. Fixed. (this is kind of a quick and dirty explanation, I can do better if you'd like) David K. Marcy Cortes [EMAIL PROTECTED] ellsfargo.com To Sent by: Linux on LINUX-390@VM.MARIST.EDU 390 Port cc [EMAIL PROTECTED] IST.EDU Subject Re: recover root password 04/14/2008 11:30 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Does anyone have full sudo? Then you could just sudo su - passwd And change it. Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Miguel Roman Sent: Monday, April 14, 2008 8:03 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] recover root password Hello, We are running Suse Linux 9.3 (64 bit) under z/VM 5.1. One of the administrators changed the root password and forgot the password. Does anyone know how to recover the root password? Thanks. Miguel A Roman. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
Help needed adding LCS Ethernet on a z9 for z/Linux LPAR (NO VM)
I am reposting to make sure this went out. Any help would be greatly appreciated. Sam Hi, We are trying to add another OSA LCS Ethernet on our z/9 z/Linux LPAR (SLES 10 sp1) CHP F1 is defined in IODF as OSE Looking at some PDFs I see that it say that we only have to do the following: echo 0.0.f100,0.0.f101 /sys/bus/ccwgroup/drivers/lcs/group 1. Without an echo -n we get an echo invalid argument 2. With echo -n we get no message and nothing build in the appropriate /sys/bus/ccwgroup areas. Next we tried YAST, we rebooted and it F100 times out. F200 is already an LCS, but we want to convert it to QETH as soon I we can get this second LCS Ethernet working. There is NO OAT for F100 , but F200 (which works, installed via installation process) has an OAT. CHP(F1) is offline to all but this LPAR. I have done an zipl -c /etc/zipl.conf Here is my /etc/zipl.conf [defaultboot] defaultmenu = menu [SLES_10_SP1] image = /boot/image-2.6.16.54-0.2.3-default target = /boot/zipl ramdisk = /boot/initrd-2.6.16.54-0.2.3-default,0x100 # parameters = root=/dev/disk/by-id/ccw-IBM.7500029646.3800.2f-part2 TERM=dumb parameters = dasd=382f,392f root=/dev/disk/by-id/ccw-IBM.7500029646.3800.2f-part2 TERM=dumb :menu default = 1 prompt = 1 target = /boot/zipl timeout = 15 1 = ipl ###Don't change this comment - YaST2 identifier: Original name: ipl### [ipl] image = /boot/image target = /boot/zipl ramdisk = /boot/initrd,0x100 #parameters = root=/dev/disk/by-id/ccw-IBM.7500029646.3800.2f-part2 TERM=dumb parameters = dasd=382f,392f root=/dev/disk/by-id/ccw-IBM.7500029646.3800.2f-part2 TERM=dumb cio_ignore=all,!0.0.382F,!0.0.392F,!0.0.F100-0.0.F11E,!0.0.F200-0.0.F202,!0.0.C000-0.0.C01F,!0.0.C100 -0.0.C11F Sam Bass 254-771-7212 Sr z/OS Systems Specialist -- 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: recover root password
The quickest way is bring down the server that you lost you password using bootable media procedure as if you are running on an local box. The difference is that your going to use another linux guest to do the recovery for you. detach the minidisk where / is resided on #cp link suse93 mr from the recovery id mount the partition mount /dev/?? /mnt chroot /mnt passwd exit Miguel Roman [EMAIL PROTECTED] c.com To Sent by: Linux LINUX-390@VM.MARIST.EDU on 390 Portcc [EMAIL PROTECTED] IST.EDU Subject recover root password 04/14/2008 11:03 AM Please respond to Linux on 390 Port [EMAIL PROTECTED] IST.EDU Hello, We are running Suse Linux 9.3 (64 bit) under z/VM 5.1. One of the administrators changed the root password and forgot the password. Does anyone know how to recover the root password? Thanks. Miguel A Roman. -- 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 Visit our website at http://www.nyse.com Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Euronext, 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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
On Mon, 2008-04-14 at 12:46 -0500, Kelly F. Hickel wrote: -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Brad Hinson Sent: Monday, April 14, 2008 12:38 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC? Hi Kelly, Does dmesg show any qeth-related errors during bootup? Also, do you get any errors when you perform the steps manually? i.e: echo 0.0.e200,0.0.e201,0.0.e202 /sys/bus/ccwgroup/drivers/qeth/group echo 1 /sys/bus/ccwgroup/drivers/qeth/0.0.e200/online Lastly, are you using the OSA in layer2 (OPTIONS='layer2=1' in ifcfg-eth0) or layer3 (ARP=no in ifcfg-eth0) mode? -Brad Brad, I don't see any qeth related messages at all when trying to boot the installed image, but it may be failing due to volume group errors before it gets that far. It lists all the DASD addresses, then panics after the Activation logical volumes message with: Kernel panic - not syncing: Attempted to kill init! When trying to boot the installer via FTP, I get the messages below: Qeth: loading qeth S/390 OSA-Express driver Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device 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 Just had an idea: When prompted for the device numbers, are you entering uppercase 0.0.E200,... or lowercase 0.0.e200,...? I've seen this before when uppercase is used instead of lowercase. -- 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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
On Mon, Apr 14, 2008 at 2:12 PM, in message [EMAIL PROTECTED], Brad Hinson [EMAIL PROTECTED] wrote: On Mon, 2008-04-14 at 12:46 -0500, Kelly F. Hickel wrote: -Original Message- -snip- Qeth: loading qeth S/390 OSA-Express driver Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device -snip- Just had an idea: When prompted for the device numbers, are you entering uppercase 0.0.E200,... or lowercase 0.0.e200,...? I've seen this before when uppercase is used instead of lowercase. Based on the error message he's getting, it looks like it was lowercase. 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: FW: any help installing 4.4 for s390 (or s390x) on Z9-BC?
On Mon, Apr 14, 2008 at 2:12 PM, in message [EMAIL PROTECTED], Brad Hinson [EMAIL PROTECTED] wrote: On Mon, 2008-04-14 at 12:46 -0500, Kelly F. Hickel wrote: -Original Message- -snip- Qeth: loading qeth S/390 OSA-Express driver Cat: /sys/devices/qeth/0.0.e200/if_name: No such file or directory SIOCSIFNETMASK: No such device SIOCSIFBRDADDR: No such device -snip- Just had an idea: When prompted for the device numbers, are you entering uppercase 0.0.E200,... or lowercase 0.0.e200,...? I've seen this before when uppercase is used instead of lowercase. Based on the error message he's getting, it looks like it was lowercase. Mark Post And, I'm absolutely positive that I've tried it over a dozen times each way. Just for kicks, I tried again, ensuring lower case and the damn thing worked this time! Now I just have to figure out if there's any hope for recovering the volume group of the previous install from the ftp boot, or if I just give up and reinstall (making several people unhappier than they already are). Thanks 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
CentOS 4.4 kernel panic on boot s390x
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
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/vg_name/lv_name to /mnt/where_ever. 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/your_vg_name/your_lv_name 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 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
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/vg_name/lv_name to /mnt/where_ever. 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/your_vg_name/your_lv_name 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
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/vg_name/lv_name to /mnt/where_ever. 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/your_vg_name/your_lv_name 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
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/vg_name/lv_name to /mnt/where_ever. 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/your_vg_name/your_lv_name 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
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/vg_name/lv_name to /mnt/where_ever. 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/your_vg_name/your_lv_name 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
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 Enter 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 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/vg_name/lv_name to /mnt/where_ever. 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/your_vg_name/your_lv_name 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:
Re: recover root password
RPN01 wrote: Would it be the wrong time to suggest that, once you have the system installed, up and running, nobody should ever log in as root, except in dire or unavoidable circumstances. Once you have the system, give your system administration group sudo all privs. Then just don't log into root at all. This gives you accountability Red Hat expects administrators to know and use root's password. That's what su does. SUSE expects administrators to know and use root's password. It configures sudo to work that way. Until the vendors change their approach, administrators are going to be working that way. The only Linux distribution that expects administrators to use their own password is Ubuntu, and while it's based off Debian that is available for IBM mainframes, Ubuntu isn't yet. One can also login as root without password if ssh is so configured. -- 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
