Re: Google Chrome on Red Hat?
I just tried Firefox 67 and still get the Segmentation Fault. If someone managed to get Firefox to work please let me know which Linux. I have tried it on various Linux flavors on ZBC12 and LinuxOne Rockhopper II Adolph Kahan | Senior Consultant GlassHouse Systems | Tel: +1 (416) 229-2950 x304 www.glasshousesystems.com From: Linux on 390 Port on behalf of Dan Horák Sent: May 31, 2019 5:36 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Google Chrome on Red Hat? On Fri, 31 May 2019 20:59:59 + Adolph Kahan wrote: > Mark, it does not run anymore on any of the new mainframes. It will > install and start to come up and then crash with a segmentation > fault. Mozilla has been aware of the problem. > > Here is a link to the Bugzilla > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/173 I believe newer Firefox versions (64+ or 65+) shouldn't crash, should generally work, although they might present incorrect colors due endian issues. Work has been done for FF to run on ppc64, so s390x should work fine too. Dan > > Adolph Kahan | Senior Consultant > Tel: +1 (416) 229-2950 x304 | Mobile: +1 (416) 822-3329 > > > -Original Message- > From: Linux on 390 Port On Behalf Of Mark > Post Sent: Friday, May 31, 2019 4:51 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Google Chrome on Red Hat? > > On 5/31/19 4:16 PM, Adolph Kahan wrote: > > Hi David, I was also looking for either Firefox or Chrome to run on > > z/Linux. At present none of these work on z/Linux. > > > > The only browser that will run on z/Linux is MIDORI - > > https://www.midori-browser.org/ > > That is incorrect. Mozilla Firefox has been available on mainframe > Linux for rather a long time. I've built it numerous times for > Slack/390. > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit http://www2.marist.edu/htbin/wlvindex?LINUX-390 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: dasd_configure in SLES 12 SP4
Thanks for the explanation, Mark. Easy enough for me to change the dasd_configure command in my scripts to chzdev so I will do that and not bother reporting that difference from SP3. The problem with by-path not working is a little more problematic, so I've opened a SUSE ticket for that. -Original Message- From: Linux on 390 Port On Behalf Of Mark Post Sent: Friday, May 31, 2019 10:42 AM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] dasd_configure in SLES 12 SP4 On 5/31/19 6:47 AM, Michael MacIsaac wrote: > Why? Doing so will break scripts we have ... Because they require maintenance, cause bug reports (such as Marcy's), etc., etc. They're not going away tomorrow, but please plan ahead. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Google Chrome on Red Hat?
On Fri, 31 May 2019 16:40:50 -0400 Alan Altmark wrote: > On Friday, 05/31/2019 at 08:19 GMT, "Dan Horák" > wrote: > > there are many places in Chromium source code base that need > > architecture specific code, you can look at [1] for the current > > effort of bringing ppc64le support. Having the new code accepted > > upstream is another story. I haven't even dared to think about > > Chromium on s390x ;-) > > Dan, why would a web browser require arch-specific code in it? I'm > missing the obvious, I know... a modern web browser is more like an operating system than a simple application, combine it with the not-invented-here syndrome, then you really don't want to know the details :-) Dan > Alan Altmark > > Senior Managing z/VM and Linux Consultant > IBM Systems Lab Services > IBM Z Delivery Practice > ibm.com/systems/services/labservices > office: 607.429.3323 > mobile; 607.321.7556 > alan_altm...@us.ibm.com > IBM Endicott > > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Google Chrome on Red Hat?
On Fri, 31 May 2019 20:59:59 + Adolph Kahan wrote: > Mark, it does not run anymore on any of the new mainframes. It will > install and start to come up and then crash with a segmentation > fault. Mozilla has been aware of the problem. > > Here is a link to the Bugzilla > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/173 I believe newer Firefox versions (64+ or 65+) shouldn't crash, should generally work, although they might present incorrect colors due endian issues. Work has been done for FF to run on ppc64, so s390x should work fine too. Dan > > Adolph Kahan | Senior Consultant > Tel: +1 (416) 229-2950 x304 | Mobile: +1 (416) 822-3329 > > > -Original Message- > From: Linux on 390 Port On Behalf Of Mark > Post Sent: Friday, May 31, 2019 4:51 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: Google Chrome on Red Hat? > > On 5/31/19 4:16 PM, Adolph Kahan wrote: > > Hi David, I was also looking for either Firefox or Chrome to run on > > z/Linux. At present none of these work on z/Linux. > > > > The only browser that will run on z/Linux is MIDORI - > > https://www.midori-browser.org/ > > That is incorrect. Mozilla Firefox has been available on mainframe > Linux for rather a long time. I've built it numerous times for > Slack/390. > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit http://www2.marist.edu/htbin/wlvindex?LINUX-390 > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 > or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Google Chrome on Red Hat?
Mark, it does not run anymore on any of the new mainframes. It will install and start to come up and then crash with a segmentation fault. Mozilla has been aware of the problem. Here is a link to the Bugzilla https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/173 Adolph Kahan | Senior Consultant Tel: +1 (416) 229-2950 x304 | Mobile: +1 (416) 822-3329 -Original Message- From: Linux on 390 Port On Behalf Of Mark Post Sent: Friday, May 31, 2019 4:51 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Google Chrome on Red Hat? On 5/31/19 4:16 PM, Adolph Kahan wrote: > Hi David, I was also looking for either Firefox or Chrome to run on z/Linux. > At present none of these work on z/Linux. > > The only browser that will run on z/Linux is MIDORI - > https://www.midori-browser.org/ That is incorrect. Mozilla Firefox has been available on mainframe Linux for rather a long time. I've built it numerous times for Slack/390. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Google Chrome on Red Hat?
On 5/31/19 4:16 PM, Adolph Kahan wrote: > Hi David, I was also looking for either Firefox or Chrome to run on z/Linux. > At present none of these work on z/Linux. > > The only browser that will run on z/Linux is MIDORI - > https://www.midori-browser.org/ That is incorrect. Mozilla Firefox has been available on mainframe Linux for rather a long time. I've built it numerous times for Slack/390. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Google Chrome on Red Hat?
On Friday, 05/31/2019 at 08:19 GMT, "Dan Horák" wrote: > there are many places in Chromium source code base that need > architecture specific code, you can look at [1] for the current effort > of bringing ppc64le support. Having the new code accepted upstream is > another story. I haven't even dared to think about Chromium on s390x ;-) Dan, why would a web browser require arch-specific code in it? I'm missing the obvious, I know... Alan Altmark Senior Managing z/VM and Linux Consultant IBM Systems Lab Services IBM Z Delivery Practice ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Google Chrome on Red Hat?
Hi David, I was also looking for either Firefox or Chrome to run on z/Linux. At present none of these work on z/Linux. The only browser that will run on z/Linux is MIDORI - https://www.midori-browser.org/ Adolph Kahan | Senior Consultant Tel: +1 (416) 229-2950 x304 | Mobile: +1 (416) 822-3329 -Original Message- From: Linux on 390 Port On Behalf Of Dave Jones Sent: Tuesday, May 28, 2019 1:22 PM To: LINUX-390@VM.MARIST.EDU Subject: Google Chrome on Red Hat? Hello, all. I'd like to run Google Chrome on Red Hat z/Liunx...does anyone know where a pre-build binary might be found? Thanks in advance. DJ -- DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and Cloud 703.237.7370 (Office) | 281.578.7544 (CELL) INFORMATION TECHNOLOGY COMPANY -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: Google Chrome on Red Hat?
On 5/28/19 1:21 PM, Dave Jones wrote: > I'd like to run Google Chrome on Red Hat z/Liunx...does anyone know > where a pre-build binary might be found? I just tried to build Chromium on the openSUSE Build Service. It failed due to what seems like in-line assembler code in the source. I suspect that there's not a pre-built binary out there, unless someone has gone to a fair amount of trouble to get it to build. That no one has spoken up in this mailing list would indicate that none of the usual suspects have made that effort. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: dasd_configure in SLES 12 SP4
Mark, Thanks for a thorough reply. We have been warned :)) -Mike M On Fri, May 31, 2019 at 1:43 PM Mark Post wrote: > On 5/31/19 6:47 AM, Michael MacIsaac wrote: > > Why? Doing so will break scripts we have ... > > Because they require maintenance, cause bug reports (such as Marcy's), > etc., etc. They're not going away tomorrow, but please plan ahead. > > One of the complaints we hear is that "doing X on SLES for the mainframe > is different from how it's done on RHEL." Red Hat hears the same, in > reverse. SUSE and Red Hat both approached IBM to ask them to write and > maintain a replacement set of tools for these sorts of scripts. That > way, the tools to perform persistent and transient configuration will be > the same across distributions. I haven't looked, but I'm guessing Ubuntu > for the mainframe is using them as well. > > So, IBM came up the lszdev and chzdev utilities. To provide > compatibility, I modified the existing *_configure scripts to use them > instead of the previous logic. Moving forward, SUSE will be using the > lszdev and chzdev commands in our own tools where the *_configure > scripts have been used in the past. The linuxrc program to set up the > installation environment is already doing that. > > The wrapper scripts were written solely as a means of translating the > old semantics into the ones required by IBM's commands. The lszdev and > chzdev commands provide a lot more functionality than the old > *_configure scripts did. There will be no changes to the *_configure > scripts unless there's a bug, or for some reason IBM changes the > parameters their commands accept or require. > > If you set an environment variable of DEBUG to "yes", the *_configure > scripts will display the chzdev command that gets executed, as well as > actually executing it. Besides helping in debugging, this will allow > anyone wishing to get ahead of the curve to see exactly what command > needs to be executed to accomplish the same task as before. > > The old scripts will not be removed from the SLES12 product. At this > point, we're not sure if they will be removed from future service pack > levels of SLES15 or not. They almost certainly will not be part of the > follow-on version after SLES15. (After what happened between SLES12 and > SLES15, I'm not going to even try and outguess Product Management as to > what name that's going to be.) > > Finally, this is Open Source Software. If you decide you're simply not > going to move to the new commands from IBM, you're welcome to make and > keep copies of the *_configure scripts for your own use, for ever and ever. > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > -- -Mike MacIsaac -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: dasd_configure in SLES 12 SP4
On 5/31/19 6:47 AM, Michael MacIsaac wrote: > Why? Doing so will break scripts we have ... Because they require maintenance, cause bug reports (such as Marcy's), etc., etc. They're not going away tomorrow, but please plan ahead. One of the complaints we hear is that "doing X on SLES for the mainframe is different from how it's done on RHEL." Red Hat hears the same, in reverse. SUSE and Red Hat both approached IBM to ask them to write and maintain a replacement set of tools for these sorts of scripts. That way, the tools to perform persistent and transient configuration will be the same across distributions. I haven't looked, but I'm guessing Ubuntu for the mainframe is using them as well. So, IBM came up the lszdev and chzdev utilities. To provide compatibility, I modified the existing *_configure scripts to use them instead of the previous logic. Moving forward, SUSE will be using the lszdev and chzdev commands in our own tools where the *_configure scripts have been used in the past. The linuxrc program to set up the installation environment is already doing that. The wrapper scripts were written solely as a means of translating the old semantics into the ones required by IBM's commands. The lszdev and chzdev commands provide a lot more functionality than the old *_configure scripts did. There will be no changes to the *_configure scripts unless there's a bug, or for some reason IBM changes the parameters their commands accept or require. If you set an environment variable of DEBUG to "yes", the *_configure scripts will display the chzdev command that gets executed, as well as actually executing it. Besides helping in debugging, this will allow anyone wishing to get ahead of the curve to see exactly what command needs to be executed to accomplish the same task as before. The old scripts will not be removed from the SLES12 product. At this point, we're not sure if they will be removed from future service pack levels of SLES15 or not. They almost certainly will not be part of the follow-on version after SLES15. (After what happened between SLES12 and SLES15, I'm not going to even try and outguess Product Management as to what name that's going to be.) Finally, this is Open Source Software. If you decide you're simply not going to move to the new commands from IBM, you're welcome to make and keep copies of the *_configure scripts for your own use, for ever and ever. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: dasd_configure in SLES 12 SP4
On Fri, May 31, 2019 at 12:48 PM Michael MacIsaac wrote: > Mark, > > > The wrappers will be removed at some point in the future. > Why? Doing so will break scripts we have ... > > Same here. I would urge SuSE to keep them. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
Re: dasd_configure in SLES 12 SP4
Mark, > The wrappers will be removed at some point in the future. Why? Doing so will break scripts we have ... -Mike On Thu, May 30, 2019 at 5:06 PM Mark Post wrote: > On 5/30/19 4:54 PM, Marcy Cortes wrote: > > Should I just be using that chzdev command now? > > Yes. Starting with SLES12 SP4, the following SUSE-provided scripts: > ctc_configure > dasd_configure > qeth_configure > zfcp_disk_configure > zfcp_host_configure > > are simply wrappers for the chzdev command. The wrappers will be removed > at some point in the future. > > > Mark Post > > -- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www2.marist.edu/htbin/wlvindex?LINUX-390 > -- -Mike MacIsaac -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
