Re: [CentOS] And then there was one (browser)
>> Well, turns out it was more than a rumour. Here it is, some test >> version: >> >> http://people.redhat.com/tpopela/rpms/ >> > > I would recommend trying those RPMs .. I will see if I can get it to > build and get it into my chromium soon. FYI chromium-31.0.1650.63-1.el6_5.src.rpm builds (in mock) and installs just fine in C6.5 64-bit. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 106, Issue 13
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org
You can reach the person managing the list at
centos-announce-ow...@centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."
Today's Topics:
1. CEEA-2013:1867 CentOS 6 tzdata Update (Johnny Hughes)
2. CESA-2013:1869 Important CentOS 6 pixman Update (Johnny Hughes)
3. CESA-2013:1868 Important CentOS 6 xorg-x11-server Update
(Johnny Hughes)
4. CESA-2013:1869 Important CentOS 5 pixman Update (Johnny Hughes)
5. CEEA-2013:1867 CentOS 5 tzdata Update (Johnny Hughes)
6. CESA-2013:1868 Important CentOS 5 xorg-x11-server Update
(Johnny Hughes)
--
Message: 1
Date: Fri, 20 Dec 2013 12:22:00 +
From: Johnny Hughes
Subject: [CentOS-announce] CEEA-2013:1867 CentOS 6 tzdata Update
To: centos-annou...@centos.org
Message-ID: <20131220122200.ga21...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Enhancement Advisory 2013:1867
Upstream details at : https://rhn.redhat.com/errata/RHEA-2013-1867.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
c1260a53a38479ec7a17f2340c494b511e45c8b45b52d5fac94180d74f94adb3
tzdata-2013i-1.el6.noarch.rpm
c5597cc069dd09ce597aed44f6f9ca5a378bd6599319dda9139f3a60426e1a61
tzdata-java-2013i-1.el6.noarch.rpm
x86_64:
c1260a53a38479ec7a17f2340c494b511e45c8b45b52d5fac94180d74f94adb3
tzdata-2013i-1.el6.noarch.rpm
c5597cc069dd09ce597aed44f6f9ca5a378bd6599319dda9139f3a60426e1a61
tzdata-java-2013i-1.el6.noarch.rpm
Source:
65aa2cea8bb55dc6b39c15370f7a2ee749a0d87cc4d87efb9ed9d396475cdcc5
tzdata-2013i-1.el6.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
--
Message: 2
Date: Fri, 20 Dec 2013 12:22:40 +
From: Johnny Hughes
Subject: [CentOS-announce] CESA-2013:1869 Important CentOS 6 pixman
Update
To: centos-annou...@centos.org
Message-ID: <20131220122240.ga21...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2013:1869 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-1869.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
2ac990d608f38d038d458c02bae6dcb2a2505cc62e7cb249d9a9a90c0e56678c
pixman-0.26.2-5.1.el6_5.i686.rpm
5746b9d5183181ac7ecd01c1d19bbb9486aee35cc3c2dc208e18fb3e3396a966
pixman-devel-0.26.2-5.1.el6_5.i686.rpm
x86_64:
2ac990d608f38d038d458c02bae6dcb2a2505cc62e7cb249d9a9a90c0e56678c
pixman-0.26.2-5.1.el6_5.i686.rpm
09c9a292fb752a9bd3f86476877c0d4a13d8a51d6d6397c879774abca76c5403
pixman-0.26.2-5.1.el6_5.x86_64.rpm
5746b9d5183181ac7ecd01c1d19bbb9486aee35cc3c2dc208e18fb3e3396a966
pixman-devel-0.26.2-5.1.el6_5.i686.rpm
8c8b3da0c1f696c1ab5f6ea1ab3609e5d73c943a69f58e6da112521f83fcc00c
pixman-devel-0.26.2-5.1.el6_5.x86_64.rpm
Source:
ecc7276eb4b9dfc5db0ab4ea2fc67bbd796dca56f249dae9398ebeec27d0dda1
pixman-0.26.2-5.1.el6_5.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
--
Message: 3
Date: Fri, 20 Dec 2013 12:23:37 +
From: Johnny Hughes
Subject: [CentOS-announce] CESA-2013:1868 Important CentOS 6
xorg-x11-server Update
To: centos-annou...@centos.org
Message-ID: <20131220122337.ga21...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2013:1868 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2013-1868.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
070409ae9e7d2ae07a223b9694efc08e8a7537876816fea9a622be26a23a01e5
xorg-x11-server-common-1.13.0-23.1.el6.centos.i686.rpm
bbddf2917d1bcfda2ad76726680654887705638500643b27fe5e26392d01a784
xorg-x11-server-devel-1.13.0-23.1.el6.centos.i686.rpm
6dc6cd1c7733f36e90f82a9b244828b67b403a7930025cf72de47eb0be709564
xorg-x11-server-source-1.13.0-23.1.el6.centos.noarch.rpm
6827b62a8589321efe9e7cbe93e12cd6ed4e34f70819c7c5109109dcf3e42062
xorg-x11-server-Xdmx-1.13.0-23.1.el6.centos.i686.rpm
e5fbe493562e486ed6854efdbcab0458b7de4cc499f0b7ad0820e1271207c316
xorg-x11-server-Xephyr-1.13.0-23.1.el6.centos.i686.rpm
8ae2ad12275d71e2b51d9c4ab107988021ed113a2849f02f80da40fafafc33ce
xorg-x11-server-Xnest-1.13.0-23.1.el6.centos.i686.rpm
02492ec230cd3690017225b6526df22a760e3069714e420a62eb5ca9139b2086
xorg-x11-server-Xorg-1.13.0-23.1.el6.cen
Re: [CentOS] And then there was one (browser)
On 20.12.2013 21:14, Akemi Yagi wrote: > On Fri, Dec 20, 2013 at 5:33 AM, Akemi Yagi wrote: >> On Thu, Dec 19, 2013 at 5:48 PM, Robert Arkiletian >> wrote: >> >>> Does anyone know of secret plans to eventually support >>> Chrome/Chromium >>> on C6? (crossing fingers) >> >> I heard a rumour about such a "secret" plan (RH talking with Google) >> but cannot confirm ... > > Well, turns out it was more than a rumour. Here it is, some test > version: > > http://people.redhat.com/tpopela/rpms/ Thanks! However even this version has serious problems - like the old versions, on multiple monitor setups it will refuse to leave full screen. Stay away from F11! :-) -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] And then there was one (browser)
On 12/21/2013 04:14 AM, Александр Кириллов wrote: >>> Well, turns out it was more than a rumour. Here it is, some test >>> version: >>> >>> http://people.redhat.com/tpopela/rpms/ >>> >> I would recommend trying those RPMs .. I will see if I can get it to >> build and get it into my chromium soon. > FYI > chromium-31.0.1650.63-1.el6_5.src.rpm builds (in mock) and installs just > fine in C6.5 64-bit. Indeed it does and I have put a version of it built for centos-6 i386 an x86_64 in my testing repo: http://people.centos.org/hughesjr/chromium/6/ I will try to keep this updated (as I did before) when new versions of chromium become available. I was able to rebuild other versions of the 31.x tree for testing a process to keep chromium updated ... however, the current chromium beta tree (32.0.1700.68 right now) fails to build. As always with things in my personal repo ... use at your own risk :) Thanks, Johnny Hughes signature.asc Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] And then there was one (browser)
Scot P. Floess writes: > > > All, > > I don't know if this will help y'all, but I have gotten Chrome working > with CentOS 6.x: > > http://www.tecmint.com/install-google-chrome-on-redhat-centos-fedora-linux/ > > On Fri, 20 Dec 2013, Kwan Lowe wrote: > > > No consolation for CentOS 6, but Chrome does appear to work on the upstream > > 7 beta. > > ___ > > CentOS mailing list > > CentOS@... > > http://lists.centos.org/mailman/listinfo/centos > > > > Scot P. Floess RHCT (Certificate Number 605010084735240) > Chief Architect FlossWare http://sourceforge.net/projects/flossware > http://flossware.sourceforge.net > https://github.com/organizations/FlossWare > Were you able to get mono/moonlight to work? I'm happy with FF but the local water district re-did their web site to require silverlight. I was able to get Chrome installed and added the moonlight/mono pieces but I end up with a blank page after I login to their web site (couldn't even get the login screen with FF so I guess that's progress). Cheers, Dave ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] And then there was one (browser)
Dave, To be honest, I never tried - as much as I hate to admit it, I'm not sure what mono/moonlight are... But I've had Chrome working for me for at least 6 months if not a year and it works fine (I'm not on CentOS 6.5)... Thanks, Flossy On Sat, 21 Dec 2013, David G. Miller wrote: > Scot P. Floess writes: > >> >> >> All, >> >> I don't know if this will help y'all, but I have gotten Chrome working >> with CentOS 6.x: >> >> http://www.tecmint.com/install-google-chrome-on-redhat-centos-fedora-linux/ >> >> On Fri, 20 Dec 2013, Kwan Lowe wrote: >> >>> No consolation for CentOS 6, but Chrome does appear to work on the upstream >>> 7 beta. >>> ___ >>> CentOS mailing list >>> CentOS@... >>> http://lists.centos.org/mailman/listinfo/centos >>> >> >> Scot P. Floess RHCT (Certificate Number 605010084735240) >> Chief Architect FlossWare http://sourceforge.net/projects/flossware >> http://flossware.sourceforge.net >> https://github.com/organizations/FlossWare >> > Were you able to get mono/moonlight to work? I'm happy with FF but the > local water district re-did their web site to require silverlight. I was > able to get Chrome installed and added the moonlight/mono pieces but I end > up with a blank page after I login to their web site (couldn't even get the > login screen with FF so I guess that's progress). > > Cheers, > Dave > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > Scot P. Floess RHCT (Certificate Number 605010084735240) Chief Architect FlossWare http://sourceforge.net/projects/flossware http://flossware.sourceforge.net https://github.com/organizations/FlossWare ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] And then there was one (browser)
I'm using too in these hours, 4-5 hours, no crash, and finally also the site of MVA works with Chrome :) Fabrizio On Sat, Dec 21, 2013 at 9:00 PM, Scot P. Floess wrote: > > Dave, > > To be honest, I never tried - as much as I hate to admit it, I'm not sure > what mono/moonlight are... > > But I've had Chrome working for me for at least 6 months if not a year and > it works fine (I'm not on CentOS 6.5)... > > Thanks, > > Flossy > > > On Sat, 21 Dec 2013, David G. Miller wrote: > > > Scot P. Floess writes: > > > >> > >> > >> All, > >> > >> I don't know if this will help y'all, but I have gotten Chrome working > >> with CentOS 6.x: > >> > >> > http://www.tecmint.com/install-google-chrome-on-redhat-centos-fedora-linux/ > >> > >> On Fri, 20 Dec 2013, Kwan Lowe wrote: > >> > >>> No consolation for CentOS 6, but Chrome does appear to work on the > upstream > >>> 7 beta. > >>> ___ > >>> CentOS mailing list > >>> CentOS@... > >>> http://lists.centos.org/mailman/listinfo/centos > >>> > >> > >> Scot P. Floess RHCT (Certificate Number 605010084735240) > >> Chief Architect FlossWare http://sourceforge.net/projects/flossware > >> http://flossware.sourceforge.net > >> https://github.com/organizations/FlossWare > >> > > Were you able to get mono/moonlight to work? I'm happy with FF but the > > local water district re-did their web site to require silverlight. I was > > able to get Chrome installed and added the moonlight/mono pieces but I > end > > up with a blank page after I login to their web site (couldn't even get > the > > login screen with FF so I guess that's progress). > > > > Cheers, > > Dave > > > > ___ > > CentOS mailing list > > CentOS@centos.org > > http://lists.centos.org/mailman/listinfo/centos > > > > Scot P. Floess RHCT (Certificate Number 605010084735240) > Chief Architect FlossWare http://sourceforge.net/projects/flossware > http://flossware.sourceforge.net > https://github.com/organizations/FlossWare > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > -- "The intuitive mind is a sacred gift and the rational mind is a faithful servant. We have created a society that honors the servant and has forgotten the gift." (A. Einstein) "La mente intuitiva è un dono sacro e la mente razionale è un fedele servo. Noi abbiamo creato una società che onora il servo e ha dimenticato il dono." (A. Einstein) Fabrizio Di Carlo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Serial Console Config in 6.5
Alle, After upgrading from 6.4 to 6.5, our serial console configuration non longer work. We have the following upstart file: [cwfox@hilo ~]$ cat /etc/init/ttyS0.conf # ttyS0 - agetty # # This service maintains a agetty on ttyS0. stop on runlevel [S016] start on runlevel [23] respawn exec agetty -h -L -w /dev/ttyS0 115200 vt100 [cwfox@hilo ~]$ And the following in /etc/securetty: [cwfox@hilo ~]$ sudo tail -2 /etc/securetty ttyS0 ttyS1 [cwfox@hilo ~]$ And finally this is appended to what used to be the kernel (now the module) line in /boot/grub/grub.conf: module /vmlinuz-2.6.32-431.1.2.0.1.el6.x86_64 ro root=/dev/mapper/vg_hilo-lv_root intel_iommu=on rd_NO_LUKS LANG=en_US.UTF-8 rd_LVM_LV=vg_hilo/lv_swap rd_NO_MD SYSFONT=latarcyrheb-sun16 rd_LVM_LV=vg_hilo/lv_root KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet crashkernel=auto console=tty0 console=ttyS0,115200 We've tried putting console=tty0 console=ttyS0,115200 in the kernel line, but no joy. We couldn't find anything in the Release Notes about a change in the serial console config. Can anyone point us in the right direction please? Best Regards, Camron -- Camron W. Fox Hilo Office High Performance Computing Group Fujitsu Management Services of America, Inc. E-mail: cw...@us.fujitsu.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] And then there was one (browser)
On 12/22/2013 09:00 AM, Scot P. Floess wrote: > > as much as I hate to admit it, I'm not sure what mono/moonlight are... Linux implementation of Microsoft .net and Silverlight respectively. Silverlight was supposed to be Microsoft's answer to flash which never really took off except in some high corporate and government situations where some PHB was tricked into it by a Microsoft salesman. Both mono (and as an extension moonlight) are spearheaded by Novel with "support" from Microsoft, which means it will almost work but not quite. To the GP, I would try rebuilding moonlight with the latest version and see if it helps, and if it doesn't then you may be stuck with either dual-booting or running a VM with windoze in order to access that government website. You may also want to look into laws regarding equal access to government resources in your area. Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Log rolling with a daemon
I'm looking for advice or suggestions for rolling log files with a daemon. I have a python script that I daemonized with http://www.jejik.com/articles/2007/02/a_simple_unix_linux_daemon_in_python/. Before I daemonized it it was run from a bash script that invoked the underlying python script. It ran the python script, waited for it to complete and then it slept for 5 seconds and ran it again. This was in a infinite loop. In between each invocation it checked the log file and if it was over 10MB it renamed it and then the next invocation started with a new empty log. Since each invocation was a separate run this worked fine. But now the daemonized python script doesn't exit - the same log file is attached to it forever. So my renaming of the file does nothing - the i node doesn't change and it's still logging to the same large file. Anyone have any ideas how I can achieve this sort of log rolling in this situation? TIA! -lrry ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Log rolling with a daemon
On 12/21/2013 4:56 PM, Larry Martell wrote: > I'm looking for advice or suggestions for rolling log files with a > daemon. I have a python script that I daemonized with > http://www.jejik.com/articles/2007/02/a_simple_unix_linux_daemon_in_python/. > Before I daemonized it it was run from a bash script that invoked the > underlying python script. It ran the python script, waited for it to > complete and then it slept for 5 seconds and ran it again. This was in > a infinite loop. In between each invocation it checked the log file > and if it was over 10MB it renamed it and then the next invocation > started with a new empty log. Since each invocation was a separate run > this worked fine. But now the daemonized python script doesn't exit - > the same log file is attached to it forever. So my renaming of the > file does nothing - the i node doesn't change and it's still logging > to the same large file. Anyone have any ideas how I can achieve this > sort of log rolling in this situation? > send a SIGHUP to syslog and it shoudl re-opent he log files. silly question, but whats wrong with the logrotate daemon thats built into centos? -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Log rolling with a daemon
On Sat, Dec 21, 2013 at 8:52 PM, John R Pierce wrote: > On 12/21/2013 4:56 PM, Larry Martell wrote: >> I'm looking for advice or suggestions for rolling log files with a >> daemon. I have a python script that I daemonized with >> http://www.jejik.com/articles/2007/02/a_simple_unix_linux_daemon_in_python/. >> Before I daemonized it it was run from a bash script that invoked the >> underlying python script. It ran the python script, waited for it to >> complete and then it slept for 5 seconds and ran it again. This was in >> a infinite loop. In between each invocation it checked the log file >> and if it was over 10MB it renamed it and then the next invocation >> started with a new empty log. Since each invocation was a separate run >> this worked fine. But now the daemonized python script doesn't exit - >> the same log file is attached to it forever. So my renaming of the >> file does nothing - the i node doesn't change and it's still logging >> to the same large file. Anyone have any ideas how I can achieve this >> sort of log rolling in this situation? >> > > send a SIGHUP to syslog and it shoudl re-opent he log files. > > silly question, but whats wrong with the logrotate daemon thats built > into centos? This is not using syslog. If you look at the daemonizing script I gave the link to, you pass in the log files for stdout and stderr, and it does some double fork magic and then associates the given files with them. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Log rolling with a daemon
On 12/21/2013 6:15 PM, Larry Martell wrote: > This is not using syslog. If you look at the daemonizing script I gave > the link to, you pass in the log files for stdout and stderr, and it > does some double fork magic and then associates the given files with > them i rarely read links on emails, and am even less likely to do a code analysis for an offhand question unless I'm being paid. -- john r pierce 37N 122W somewhere on the middle of the left coast ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Log rolling with a daemon
John's suggestion is still pertinent. You'll need a SIGHUP handler in your script. Logrotate could send the SIGHUP in a postrotate 'script'. Cheers, Cliff On Sun, Dec 22, 2013 at 3:15 PM, Larry Martell wrote: > On Sat, Dec 21, 2013 at 8:52 PM, John R Pierce > wrote: > > On 12/21/2013 4:56 PM, Larry Martell wrote: > >> I'm looking for advice or suggestions for rolling log files with a > >> daemon. I have a python script that I daemonized with > >> > http://www.jejik.com/articles/2007/02/a_simple_unix_linux_daemon_in_python/ > . > >> Before I daemonized it it was run from a bash script that invoked the > >> underlying python script. It ran the python script, waited for it to > >> complete and then it slept for 5 seconds and ran it again. This was in > >> a infinite loop. In between each invocation it checked the log file > >> and if it was over 10MB it renamed it and then the next invocation > >> started with a new empty log. Since each invocation was a separate run > >> this worked fine. But now the daemonized python script doesn't exit - > >> the same log file is attached to it forever. So my renaming of the > >> file does nothing - the i node doesn't change and it's still logging > >> to the same large file. Anyone have any ideas how I can achieve this > >> sort of log rolling in this situation? > >> > > > > send a SIGHUP to syslog and it shoudl re-opent he log files. > > > > silly question, but whats wrong with the logrotate daemon thats built > > into centos? > > This is not using syslog. If you look at the daemonizing script I gave > the link to, you pass in the log files for stdout and stderr, and it > does some double fork magic and then associates the given files with > them. > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
