Re: [CentOS] getting rid of hp c3180

[Michael Hennebry]

On Thu, 20 Jul 2017, Michael Hennebry wrote:


On Thu, 20 Jul 2017, Fred Smith wrote:


On Thu, Jul 20, 2017 at 03:27:14PM -0500, Michael Hennebry wrote:



Next on the list is a Brother HL-L2360DW.
It appears to work with linux.
I got as far as this page:
http://support.brother.com/g/b/downloadlist.aspx?c=us=en=hll2360dw_us=127



If  I use the install tool,
does it matter whether I have the printer connected during the install?


It does.
The directions that came in the box say to do so, but I forgot.
The result was that the test page went to my old printer.

Telling CUPS about it wasn't too bad.
Just went through the "add Printer" menus.

BTW one has to read the box fairly carefully
to realize that the printer comes with toner.
One has to make an inference from the term "replacement cartridge".

--
Michael   henne...@web.cs.ndsu.nodak.edu
"Sorry but your password must contain an uppercase letter, a number,
a haiku, a gang sign, a heiroglyph, and the blood of a virgin."
 --  someeecards
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] TeX Live on CentOS 7

[Nicolas Kovacs]

Le 21/07/2017 à 23:14, Alice Wonder a écrit :
> I always install official TeXLive in /usr/local/texlive - yum update
> thanks me. Every few months I update it, but keeping it outside of RPM
> means I don't get tons of individual packages, many that I never use,
> constantly updating in yum.

And how do you manage conflicts with packages? Do you blacklist them in
Yum's repo configuration? And how about the stuff dependending on them?
Install it manually using --nodeps?

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] TeX Live on CentOS 7

[Nicolas Kovacs]

Le 21/07/2017 à 20:46, Denniston, Todd A CIV NAVSURFWARCENDIV Crane,
JXVS a écrit :
> Going from my experiences on CentOS 6, I find it surprising that
> LaTeX is not working. Does even the trivial.tex from [0] compile? Can
> you get the LaTeX file that OpenVAS is generating, and on the command
> line run pdflatex (or other latex compile command) on it and capture
> the error messages? This might point to missing packages/fonts.

Thanks very much for your detailed answer. I'll look into it tomorrow
and see if this solves the problem.

Cheers from France,

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] TeX Live on CentOS 7

[Alice Wonder]

I always install official TeXLive in /usr/local/texlive - yum update 
thanks me. Every few months I update it, but keeping it outside of RPM 
means I don't get tons of individual packages, many that I never use, 
constantly updating in yum.


On 07/21/2017 11:46 AM, Denniston, Todd A CIV NAVSURFWARCENDIV Crane, 
JXVS wrote:

-Original Message-
From: Nicolas Kovacs [mailto:i...@microlinux.fr]
Sent: Friday, July 21, 2017 2:29 AM
To: CentOS
Subject: [CentOS] TeX Live on CentOS 7

Hi,

I just installed the OpenVAS vulnerability scanner on my CentOS 7
workstation. Everything seems to work fine, except PDF generation. The
'openvas-check-setup' script tells me that PDF generation works fine,
but whenever I want to generate a report, the result is unusable and
can't open in Evince or Okular.

After googling a bit, I found out that several users complained that Tex
Live is broken under RHEL/CentOS 7.

While I did use LaTeX a long time ago to write documents, I don't use it
anymore nowadays (just Markdown or LibreOffice). But I do need a working
installation of TeX Live for OpenVAS PDF reports.

What can I do now? Perform a manual installation of TeX Live with their
provided installer (to /opt) and then blacklist all texlive* packages? I
admit I'm a bit surprised that a distribution like RHEL/CentOS that
prises quality wouldn't provide a working TeX Live in their package
repositories.

Any suggestions?


The users that were complaining, were they all OpenVAS user?

Going from my experiences on CentOS 6, I find it surprising that LaTeX is not 
working.
Does even the trivial.tex from [0] compile?
Can you get the LaTeX file that OpenVAS is generating, and on the command line 
run pdflatex (or other latex compile command) on it and capture the error 
messages?
This might point to missing packages/fonts.

It may be possible that not enough of texlive has been installed.   I tend to 
do a `yum install \*latex\*` (and answer no) to see what is available and then 
install every latex thing that is not a -devel package. That way I never have 
to think about getting packages again, or if I do I will pretty much know I'll 
have to get it from CTAN myself.
seeing [1] from the opanvas wiki makes me think you should try `yum install 
\*latex\*extra\*` and see if it is now available.  And as seen elsewhere [2] 
sometimes rpm packager's don't name them the same as LaTeX packagers.   And it 
looks like[3] a lot of folks take the same 'trash the distro' perspective as 
openvas[1] which is unfortunate.  Perhaps we could ask the CentOS-extras (and a 
RHEL or EPEL ticket) folks if they would be willing to rebuild the needed 
packages from an old Fedora RPM if they are not yet available in a EL 
repository.  Have you checked EPEL?


[0] https://www.centos.org/forums/viewtopic.php?t=48421
[1] https://wiki.openvas.org/index.php/Generate_a_PDF_report#CentOS_7
[2] https://tex.stackexchange.com/a/166140
[3] https://www.centos.org/forums/viewtopic.php?t=54410

--
Even when this disclaimer is not here:
I am not a contracting officer. I do not have authority to make or modify the 
terms of any contract.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



--
-=-
Sent my from my laptop, may not be able to respond timely
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] MATROX GPU - xorg-x11-drv-mga-1.6.3 on supermicro server

[Andreas Benzler]

Hello Guys,

our cluster runs till 2014 on supermicro board. 

It is not unusual that still mainboards with mga graphics cards are delivered.

So I have then adjusted the mga driver from centos 6 - the specification file - 
,
to be build on CentOS 7. Since then this runs on the headnode without failures.

Maybe you should provide this via epel. The source can be found here:

http://centos.cms4all.org/repo/7/drivers/SRPM/xorg-x11-drv-mga-1.6.3-11.el7.centos.src.rpm

This is the latest from Centos 6.9.

Sincerely

Andy


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] TeX Live on CentOS 7

[Denniston, Todd A CIV NAVSURFWARCENDIV Crane, JXVS]

> -Original Message-
> From: Nicolas Kovacs [mailto:i...@microlinux.fr]
> Sent: Friday, July 21, 2017 2:29 AM
> To: CentOS
> Subject: [CentOS] TeX Live on CentOS 7
> 
> Hi,
> 
> I just installed the OpenVAS vulnerability scanner on my CentOS 7
> workstation. Everything seems to work fine, except PDF generation. The
> 'openvas-check-setup' script tells me that PDF generation works fine,
> but whenever I want to generate a report, the result is unusable and
> can't open in Evince or Okular.
> 
> After googling a bit, I found out that several users complained that Tex
> Live is broken under RHEL/CentOS 7.
> 
> While I did use LaTeX a long time ago to write documents, I don't use it
> anymore nowadays (just Markdown or LibreOffice). But I do need a working
> installation of TeX Live for OpenVAS PDF reports.
> 
> What can I do now? Perform a manual installation of TeX Live with their
> provided installer (to /opt) and then blacklist all texlive* packages? I
> admit I'm a bit surprised that a distribution like RHEL/CentOS that
> prises quality wouldn't provide a working TeX Live in their package
> repositories.
> 
> Any suggestions?

The users that were complaining, were they all OpenVAS user?

Going from my experiences on CentOS 6, I find it surprising that LaTeX is not 
working.
Does even the trivial.tex from [0] compile?
Can you get the LaTeX file that OpenVAS is generating, and on the command line 
run pdflatex (or other latex compile command) on it and capture the error 
messages?
This might point to missing packages/fonts.

It may be possible that not enough of texlive has been installed.   I tend to 
do a `yum install \*latex\*` (and answer no) to see what is available and then 
install every latex thing that is not a -devel package. That way I never have 
to think about getting packages again, or if I do I will pretty much know I'll 
have to get it from CTAN myself.
seeing [1] from the opanvas wiki makes me think you should try `yum install 
\*latex\*extra\*` and see if it is now available.  And as seen elsewhere [2] 
sometimes rpm packager's don't name them the same as LaTeX packagers.   And it 
looks like[3] a lot of folks take the same 'trash the distro' perspective as 
openvas[1] which is unfortunate.  Perhaps we could ask the CentOS-extras (and a 
RHEL or EPEL ticket) folks if they would be willing to rebuild the needed 
packages from an old Fedora RPM if they are not yet available in a EL 
repository.  Have you checked EPEL?


[0] https://www.centos.org/forums/viewtopic.php?t=48421
[1] https://wiki.openvas.org/index.php/Generate_a_PDF_report#CentOS_7
[2] https://tex.stackexchange.com/a/166140
[3] https://www.centos.org/forums/viewtopic.php?t=54410

--
Even when this disclaimer is not here:
I am not a contracting officer. I do not have authority to make or modify the 
terms of any contract.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS-virt] kernel-4.9.37-29.el7 (and el6)

[Johnny Hughes]

On 07/21/2017 06:06 AM, Piotr Gackiewicz wrote:
> On Fri, 21 Jul 2017, Johnny Hughes wrote:
> 
>>>
>>
>> I will happily create a test kernel with SLAB .. what is your config
>> file diff?
> 
> I have just choosed SLAB allocator in menuconfig.
> It has implied several other internal configurations changes.
> 
> Overall differencess (config file patch) is in attachment.
> 
> But my considerations about compiled in PATA etc., instead of modules,
> remain actual ;-).
> 


OK .. I have built:

kernel-4.9.39-29.el6 and kernel-4.9.39-29.el7

They have been tagged to the testing repository

They should show up in a couple of hours into the testing repo.

Everyone who was having memory issues, give those a try.

Also, please test the iscsi configs as well.




signature.asc
Description: OpenPGP digital signature
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS] How does yum decide when 2 packages meet a dependency?

[Phil Perry]

On 21/07/17 17:10, Matthew Miller wrote:

On Fri, Jul 21, 2017 at 05:00:35PM +0100, John Hodrien wrote:

Say a package has a dependency for libfoo.so.1, and 2 (or more)
packages provide libfoo.so.1, how does yum decide which package to
install to meet the dependency?

It has a series of heuristics:
http://yum.baseurl.org/wiki/CompareProviders


Many thanks Matthew, that's a great overview.


That's fabulous.  You mean Phil could have fixed my issue by renaming the
package priimus so that the name was longer than mesa-libGL ;)


Tragically possible. :)




In this case, working through the logic, it would appear that primus 
probably won the battle on the basis of pulling in fewer deps than 
mesa-libGL, but what else is already installed on the system would 
clearly have an effect here.


Still, nice to know the logic involved.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How does yum decide when 2 packages meet a dependency?

[Matthew Miller]

On Fri, Jul 21, 2017 at 05:00:35PM +0100, John Hodrien wrote:
> >>Say a package has a dependency for libfoo.so.1, and 2 (or more)
> >>packages provide libfoo.so.1, how does yum decide which package to
> >>install to meet the dependency?
> >It has a series of heuristics:
> >http://yum.baseurl.org/wiki/CompareProviders
> That's fabulous.  You mean Phil could have fixed my issue by renaming the
> package priimus so that the name was longer than mesa-libGL ;)

Tragically possible. :)


-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How does yum decide when 2 packages meet a dependency?

[John Hodrien]

On Fri, 21 Jul 2017, Matthew Miller wrote:


On Fri, Jul 21, 2017 at 04:19:20PM +0100, Phil Perry wrote:

Say a package has a dependency for libfoo.so.1, and 2 (or more)
packages provide libfoo.so.1, how does yum decide which package to
install to meet the dependency?


It has a series of heuristics:

http://yum.baseurl.org/wiki/CompareProviders


That's fabulous.  You mean Phil could have fixed my issue by renaming the
package priimus so that the name was longer than mesa-libGL ;)

jh
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] How does yum decide when 2 packages meet a dependency?

[Matthew Miller]

On Fri, Jul 21, 2017 at 04:19:20PM +0100, Phil Perry wrote:
> Say a package has a dependency for libfoo.so.1, and 2 (or more)
> packages provide libfoo.so.1, how does yum decide which package to
> install to meet the dependency?

It has a series of heuristics:

http://yum.baseurl.org/wiki/CompareProviders



-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] How does yum decide when 2 packages meet a dependency?

[Phil Perry]

Hi list,

Say a package has a dependency for libfoo.so.1, and 2 (or more) packages 
provide libfoo.so.1, how does yum decide which package to install to 
meet the dependency?


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-announce] CESA-2017:1793 Important CentOS 7 graphite2 Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2017:1793 Important

Upstream details at : https://access.redhat.com/errata/RHSA-2017:1793

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
c3e6a22ff94cc8f2dff08a00f4fb2bdf24dad7c113f2e92e57ab2d58f2395b0c  
graphite2-1.3.10-1.el7_3.i686.rpm
06cc9092a8016778f4708c4d6443e76e4bc628b047dc83af8155ee694e6035df  
graphite2-1.3.10-1.el7_3.x86_64.rpm
9b929a1b6f97f17de020928bc2d58db1d98a975bcbd49eccbc9e14ac240c061e  
graphite2-devel-1.3.10-1.el7_3.i686.rpm
0f0ffdc164dc72b02f7de2147b50b1db15f3c5597d6cd34de7788a4804c8da30  
graphite2-devel-1.3.10-1.el7_3.x86_64.rpm

Source:
346757f69f162461ef4a26d2e08994c53837f4858c5a64fc46d0e483f522f2b5  
graphite2-1.3.10-1.el7_3.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CESA-2017:1789 Critical CentOS 7 java-1.8.0-openjdk Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2017:1789 Critical

Upstream details at : https://access.redhat.com/errata/RHSA-2017:1789

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
edb8077e58e41caaa199362bc57724007cc15952b2dea1bb35f120aa61400698  
java-1.8.0-openjdk-1.8.0.141-1.b16.el7_3.i686.rpm
6717ac7dc584e61c8bf68171b322331d6eac8c8a7d9a4a5fd662a4bf4efa794f  
java-1.8.0-openjdk-1.8.0.141-1.b16.el7_3.x86_64.rpm
ad904ba554b4ebaf47a8c9e1087513cadba468e1c225cc1bb02990e5643208b1  
java-1.8.0-openjdk-accessibility-1.8.0.141-1.b16.el7_3.x86_64.rpm
d7eb40e252335322f7678b561e6e11d41c85a9e469d42801007f9b4e617a4d34  
java-1.8.0-openjdk-accessibility-debug-1.8.0.141-1.b16.el7_3.x86_64.rpm
716ef81de6147878ea1ff9c8dd9ea324f2de4b65216df9c95db9319cf51c230c  
java-1.8.0-openjdk-debug-1.8.0.141-1.b16.el7_3.i686.rpm
b5d1c62ed70d1c1cb960e9896e876a6a27e5429cf2f8c41f603e7d57f8a9f42f  
java-1.8.0-openjdk-debug-1.8.0.141-1.b16.el7_3.x86_64.rpm
6c6722f43edf530ad67c0778c866491c0aef703e26dbefc9ddc1f6857ecb1600  
java-1.8.0-openjdk-demo-1.8.0.141-1.b16.el7_3.x86_64.rpm
00eaae7219cab8370c36f50b799786ca01cfbf299a34ce7d307ef1ee120768ab  
java-1.8.0-openjdk-demo-debug-1.8.0.141-1.b16.el7_3.x86_64.rpm
ca56200f35f8228bbfb29a0d9c89ad9e580e275b30c3b228e512d703b6a272dd  
java-1.8.0-openjdk-devel-1.8.0.141-1.b16.el7_3.i686.rpm
995f62425703a173bea32d04971507b042d0d36eeb6fdb032c695f8a471d5c4a  
java-1.8.0-openjdk-devel-1.8.0.141-1.b16.el7_3.x86_64.rpm
eca771e28f8e82bbffe0c740fd6be956be157380643d0959fc2dfd44f858b794  
java-1.8.0-openjdk-devel-debug-1.8.0.141-1.b16.el7_3.i686.rpm
eb8c47a56da6401ccaac6096dee2748f37fe74f3b7ae39bac69de3495aa5c56a  
java-1.8.0-openjdk-devel-debug-1.8.0.141-1.b16.el7_3.x86_64.rpm
360abe6e43018ff4964fb71cb9b1fbf4dd9b9944ea9d2bfbd4ecbe9bdc00608a  
java-1.8.0-openjdk-headless-1.8.0.141-1.b16.el7_3.i686.rpm
53e7df3b218f9522fb054774b66a44b050fee2389249c1c9c03004fa7b02a173  
java-1.8.0-openjdk-headless-1.8.0.141-1.b16.el7_3.x86_64.rpm
c2299a3f9ad8bfe12774793563da01e076e5c98a74de81b49cbe8a55f80aa413  
java-1.8.0-openjdk-headless-debug-1.8.0.141-1.b16.el7_3.i686.rpm
10cebec92938e045f77848abd64225cddab79966794dc026a3d58d5e373deafa  
java-1.8.0-openjdk-headless-debug-1.8.0.141-1.b16.el7_3.x86_64.rpm
473b0bdcdbaf70deb36b34808a6eb81968c3997d60d78d6f761acfa0deb4d719  
java-1.8.0-openjdk-javadoc-1.8.0.141-1.b16.el7_3.noarch.rpm
8df058a609ea6e8a7d660c0c9dce9f260e0fa5040de9f375081e1116e8963843  
java-1.8.0-openjdk-javadoc-debug-1.8.0.141-1.b16.el7_3.noarch.rpm
c6170ee7c3056c116eb1ac878f989455b087edfdf1f00afa150bbd1dd80c142d  
java-1.8.0-openjdk-javadoc-zip-1.8.0.141-1.b16.el7_3.noarch.rpm
3a6f2679d7b1c51c8a5f8d497ada36914fab880311eef66ed384b0947ee1146d  
java-1.8.0-openjdk-javadoc-zip-debug-1.8.0.141-1.b16.el7_3.noarch.rpm
cc08abb15e61118c147cf42febd1d7b759680b6a3726fc4e1017a8d4fa106176  
java-1.8.0-openjdk-src-1.8.0.141-1.b16.el7_3.x86_64.rpm
4244b40b9d9d104764454e1f9f1346528e8a6c1b64734e97513c1f88b3d50b2b  
java-1.8.0-openjdk-src-debug-1.8.0.141-1.b16.el7_3.x86_64.rpm

Source:
3648961c8cb07f0426f5cb9b688737664afd5188095ee5630008c207a7f23274  
java-1.8.0-openjdk-1.8.0.141-1.b16.el7_3.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

[CentOS-announce] CESA-2017:1789 Critical CentOS 6 java-1.8.0-openjdk Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2017:1789 Critical

Upstream details at : https://access.redhat.com/errata/RHSA-2017:1789

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
f52e4ad097d13678088a4e75b78f77b16ca66c046c5783abcba212654dc36970  
java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.i686.rpm
3a6e22d84f5abeec393247fc3cb1530ab93da5f068a002ba92ee861ae258d0e0  
java-1.8.0-openjdk-debug-1.8.0.141-2.b16.el6_9.i686.rpm
bffa9cb71ea43f4753a846b9450da2e8b7b81bd94e4484d809934cd17268e375  
java-1.8.0-openjdk-demo-1.8.0.141-2.b16.el6_9.i686.rpm
4cce6815f6360c532d491d52e4b142a3309e8b57468609d597102b6d9e5cc7a6  
java-1.8.0-openjdk-demo-debug-1.8.0.141-2.b16.el6_9.i686.rpm
54f92980aefab61f850923cf91d3f17fdc69e987d4ad84b3c490e2cd83ea31a6  
java-1.8.0-openjdk-devel-1.8.0.141-2.b16.el6_9.i686.rpm
fa7bb77a495ee1401e9951cb704a8660e86a374e67547173e4a07f16260a1285  
java-1.8.0-openjdk-devel-debug-1.8.0.141-2.b16.el6_9.i686.rpm
a4d3a7d676b3a1150eccb624eaf132094109ae644645b5e9fadf08a948f9dc97  
java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.i686.rpm
9ec95b88d7c6964e769e666451636934daa62a06a4de02dd979601f41d90bd0d  
java-1.8.0-openjdk-headless-debug-1.8.0.141-2.b16.el6_9.i686.rpm
4dba092ad163f12f2baa26b8df729a0ef48042290a0c4bb0820d0705a64615c7  
java-1.8.0-openjdk-javadoc-1.8.0.141-2.b16.el6_9.noarch.rpm
b2f21bbd6e97ad285088cdf254ae3bd3e80bc1fef92f53622852a35aaee625e3  
java-1.8.0-openjdk-javadoc-debug-1.8.0.141-2.b16.el6_9.noarch.rpm
9ad05542df8705ca50458b913f87bf00d0e614e7fa4f61cafd2ef926b024bbe2  
java-1.8.0-openjdk-src-1.8.0.141-2.b16.el6_9.i686.rpm
0a46d8e8f5f6ccd3423d6a88b806dbd9bba65cc8dae4afa0734a74e90c56fce8  
java-1.8.0-openjdk-src-debug-1.8.0.141-2.b16.el6_9.i686.rpm

x86_64:
d6f873e3cf402ec86b6787e47d048f16ee0e46c479183c4a3ed91686e8dd3283  
java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.x86_64.rpm
5cd11249fdfd267fe826a81e2f72db50f773874408a265654d24442f3567e5da  
java-1.8.0-openjdk-debug-1.8.0.141-2.b16.el6_9.x86_64.rpm
c007905d767920d1cd312a08b034abf1aae58e33a2ccb87f880e73ddb35f0a5e  
java-1.8.0-openjdk-demo-1.8.0.141-2.b16.el6_9.x86_64.rpm
0930f7131581917e8d038db37fa4f567ee2054729a201da3793c543efa9d5440  
java-1.8.0-openjdk-demo-debug-1.8.0.141-2.b16.el6_9.x86_64.rpm
8d86dc26bc1dbccc86f68facefac5a528c4471d69ab984f696f40e08a03e4f97  
java-1.8.0-openjdk-devel-1.8.0.141-2.b16.el6_9.x86_64.rpm
aaa7c5cc5b260277e471b65f26b5dfba40dc408091d5b35c8e1961907bc05da0  
java-1.8.0-openjdk-devel-debug-1.8.0.141-2.b16.el6_9.x86_64.rpm
fb8f39171b2825b3c02ca0b3dd1933c20044fe43192db05125de3d487176ad4d  
java-1.8.0-openjdk-headless-1.8.0.141-2.b16.el6_9.x86_64.rpm
fb65ce188c11cb677cab4c268511a648a065ea0aa74c319c519229a1ef8496c0  
java-1.8.0-openjdk-headless-debug-1.8.0.141-2.b16.el6_9.x86_64.rpm
4dba092ad163f12f2baa26b8df729a0ef48042290a0c4bb0820d0705a64615c7  
java-1.8.0-openjdk-javadoc-1.8.0.141-2.b16.el6_9.noarch.rpm
b2f21bbd6e97ad285088cdf254ae3bd3e80bc1fef92f53622852a35aaee625e3  
java-1.8.0-openjdk-javadoc-debug-1.8.0.141-2.b16.el6_9.noarch.rpm
9168f6aa93be930be869f7f1eabb39fb5ff26768c4e70a6b7be73d2e43a4f1bb  
java-1.8.0-openjdk-src-1.8.0.141-2.b16.el6_9.x86_64.rpm
b226fb799e77db44bcd875043d385a0863f027e98036bf05318ba68567a54a48  
java-1.8.0-openjdk-src-debug-1.8.0.141-2.b16.el6_9.x86_64.rpm

Source:
8661435a6023919fb61977e19566d75143a782482866ab55114873a83a1982dc  
java-1.8.0-openjdk-1.8.0.141-2.b16.el6_9.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

Re: [CentOS-virt] kernel-4.9.37-29.el7 (and el6)

[Johnny Hughes]

On 07/21/2017 06:06 AM, Piotr Gackiewicz wrote:
> On Fri, 21 Jul 2017, Johnny Hughes wrote:
> 
>>>
>>
>> I will happily create a test kernel with SLAB .. what is your config
>> file diff?
> 
> I have just choosed SLAB allocator in menuconfig.
> It has implied several other internal configurations changes.
> 
> Overall differencess (config file patch) is in attachment.
> 
> But my considerations about compiled in PATA etc., instead of modules,
> remain actual ;-).
> 

OK .. I will create a 4.9.39 kernel with slub off and slab on later
today.  The only change I will make is to also turn slab_debug on (it
will add things to the debuginfo file that Sarah created for the kernels).

WRT the other items in the kernel (modules or compiled directly), I
would rather leave everything else alone as it is how the Red Hat
kernels seem to be done .. unless someone has them actually causing a
problem.



signature.asc
Description: OpenPGP digital signature
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] kernel-4.9.37-29.el7 (and el6)

[Piotr Gackiewicz]

On Fri, 21 Jul 2017, Johnny Hughes wrote:





I will happily create a test kernel with SLAB .. what is your config
file diff?


I have just choosed SLAB allocator in menuconfig.
It has implied several other internal configurations changes.

Overall differencess (config file patch) is in attachment.

But my considerations about compiled in PATA etc., instead of modules,
remain actual ;-).

Regards,

--
Piotr Gackiewicz
Intertele S.A. - operator systemów ITL.PL i DOMENY.ITL.PL
al. T. Rejtana 10, 35-310 Rzeszów
TEL: +48 17 8507580, FAX: +48 17 8520275

http://www.itl.pl   - niezawodne usługi hostingowe
http://domeny.itl.pl- tanie domeny internetowe
http://www.intertele.pl--- SOURCES/config-x86_64   2017-07-21 12:54:16.550735676 +0200
+++ /home/gacek/rpm/SOURCES/config-x86_64   2017-07-19 23:50:35.0 
+0200
@@ -1,6 +1,6 @@
 #
 # Automatically generated file; DO NOT EDIT.
-# Linux/x86 4.9.20 Kernel Configuration
+# Linux/x86 4.9.38 Kernel Configuration
 #
 CONFIG_64BIT=y
 CONFIG_X86_64=y
@@ -243,13 +243,11 @@
 CONFIG_PERF_EVENTS=y
 # CONFIG_DEBUG_PERF_USE_VMALLOC is not set
 CONFIG_VM_EVENT_COUNTERS=y
-CONFIG_SLUB_DEBUG=y
 # CONFIG_COMPAT_BRK is not set
-# CONFIG_SLAB is not set
-CONFIG_SLUB=y
+CONFIG_SLAB=y
+# CONFIG_SLUB is not set
 # CONFIG_SLOB is not set
 CONFIG_SLAB_FREELIST_RANDOM=y
-CONFIG_SLUB_CPU_PARTIAL=y
 # CONFIG_SYSTEM_DATA_VERIFICATION is not set
 CONFIG_PROFILING=y
 CONFIG_TRACEPOINTS=y
@@ -290,7 +288,6 @@
 CONFIG_HAVE_PERF_USER_STACK_DUMP=y
 CONFIG_HAVE_ARCH_JUMP_LABEL=y
 CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG=y
-CONFIG_HAVE_ALIGNED_STRUCT_PAGE=y
 CONFIG_HAVE_CMPXCHG_LOCAL=y
 CONFIG_HAVE_CMPXCHG_DOUBLE=y
 CONFIG_ARCH_WANT_COMPAT_IPC_PARSE_VERSION=y
@@ -7330,8 +7327,7 @@
 # CONFIG_PAGE_POISONING is not set
 # CONFIG_DEBUG_PAGE_REF is not set
 # CONFIG_DEBUG_OBJECTS is not set
-# CONFIG_SLUB_DEBUG_ON is not set
-# CONFIG_SLUB_STATS is not set
+# CONFIG_DEBUG_SLAB is not set
 CONFIG_HAVE_DEBUG_KMEMLEAK=y
 # CONFIG_DEBUG_KMEMLEAK is not set
 # CONFIG_DEBUG_STACK_USAGE is not set
___
CentOS-virt mailing list
CentOS-virt@centos.org
https://lists.centos.org/mailman/listinfo/centos-virt

Re: [CentOS-virt] kernel-4.9.37-29.el7 (and el6)

[Johnny Hughes]

On 07/20/2017 03:14 PM, Piotr Gackiewicz wrote:
> On Thu, 20 Jul 2017, Kevin Stange wrote:
> 
>> On 07/20/2017 05:31 AM, Piotr Gackiewicz wrote:
>>> On Wed, 19 Jul 2017, Johnny Hughes wrote:
>>>
 On 07/19/2017 09:23 AM, Johnny Hughes wrote:
> On 07/19/2017 04:27 AM, Piotr Gackiewicz wrote:
>> On Mon, 17 Jul 2017, Johnny Hughes wrote:
>>
>>> Are the testing kernels (kernel-4.9.37-29.el7 and
>>> kernel-4.9.37-29.el6,
>>> with the one config file change) working for everyone:
>>>
>>> (turn off: CONFIG_IO_STRICT_DEVMEM)
>>
>> Hello.
>> Maybe it's not the most appropriate thread or time, but I have been
>> signalling it before:
>>
>> 4.9.* kernels do not work well for me any more (and for other people
>> neither, as I know). Last stable kernel was 4.9.13-22.
>>>
>>> I think I have nailed down the faulty combo.
>>> My tests showed, that SLUB allocator does not work well in Xen Dom0, on
>>> top of Xen Hypervisor.
>>> Id does not work at least on one of my testing servers (old AMD K8 (1
>>> proc,
>>> 1 core), only 1 paravirt guest).
>>> If kernel with SLUB booted as main (w/o Xen hypervisor), it works well.
>>> If booted as Xen hypervisor module - it almost instantly gets page
>>> allocation failure.
>>>
>>>
>>> SLAB=>SLUB was changed in kernel config, starting from 4.9.25. Then
>>> problems
>>> started to explode in my production environment, and on testing server
>>> mentioned
>>> above.
>>>
>>> After recompiling recent 4.9.34 with SLAB - everything works well on
>>> that testing machine.
>>> A will try to test 4.9.38 with the same config on my production servers.
>>
>> I was having page allocation failures on 4.9.25 with SLUB, but these
>> problems seem to be gone with 4.9.34 (still with SLUB).   Have you
>> checked this build?  It was moved to the stable repo on July 4th.
> 
> Yes, 4.9.34 was failing too. And this was actually the worst case, with
> I/O error on guest:
> 
> Jul 16 06:01:03 dom0 kernel: [452360.743312] CPU: 0 PID: 28450 Comm:
> 12.xvda3-0 Tainted: G   O4.9.34-29.el6.x86_64 #1
> Jul 16 06:01:03 guest kernel: end_request: I/O error, dev xvda3, sector
> 9200640
> Jul 16 06:01:03 dom0 kernel: [452360.758931] SLUB: Unable to allocate
> memory on node -1, gfp=0x200(GFP_NOWAIT)
> Jul 16 06:01:03 guest kernel: Buffer I/O error on device xvda3, logical
> block 1150080
> Jul 16 06:01:03 guest kernel: lost page write due to I/O error on xvda3
> Jul 16 06:01:03 guest kernel: Buffer I/O error on device xvda3, logical
> block 1150081
> Jul 16 06:01:03 guest kernel: lost page write due to I/O error on xvda3
> Jul 16 06:01:03 guest kernel: Buffer I/O error on device xvda3, logical
> block 1150082
> Jul 16 06:01:03 guest kernel: lost page write due to I/O error on xvda3
> Jul 16 06:01:03 guest kernel: Buffer I/O error on device xvda3, logical
> block 1150083
> Jul 16 06:01:03 guest kernel: lost page write due to I/O error on xvda3
> Jul 16 06:01:03 guest kernel: Buffer I/O error on device xvda3, logical
> block 1150084
> Jul 16 06:01:03 guest kernel: lost page write due to I/O error on xvda3
> Jul 16 06:01:03 dom0 kernel: [452361.449389] 12.xvda3-0: page allocation
> failure: order:0, mode:0x220(GFP_NOWAIT|__GFP_NOTRACK)
> Jul 16 06:01:03 dom0 kernel: [452361.449685] CPU: 1 PID: 28450 Comm:
> 12.xvda3-0 Tainted: G   O4.9.34-29.el6.x86_64 #1
> Jul 16 06:01:03 dom0 kernel: [452361.449934] Hardware name: Supermicro
> X8SIL/X8SIL, BIOS 1.0c 02/25/2010
> Jul 16 06:01:03 guest kernel: end_request: I/O error, dev xvda3, sector
> 6102784
> Jul 16 06:01:03 dom0 kernel: [452361.462103] SLUB: Unable to allocate
> memory on node -1, gfp=0x200(GFP_NOWAIT)
> Jul 16 06:01:03 dom0 kernel: [452361.676257] 12.xvda3-0: page allocation
> failure: order:0, mode:0x220(GFP_NOWAIT|__GFP_NOTRACK)
> Jul 16 06:01:03 dom0 kernel: [452361.676531] CPU: 0 PID: 28450 Comm:
> 12.xvda3-0 Tainted: G   O4.9.34-29.el6.x86_64 #1
> Jul 16 06:01:03 guest kernel: end_request: I/O error, dev xvda3, sector
> 6127872
> Jul 16 06:01:03 dom0 kernel: [452361.692171] SLUB: Unable to allocate
> memory on node -1, gfp=0x200(GFP_NOWAIT)
> Jul 16 06:01:07 dom0 kernel: [452365.438565] 12.xvda3-0: page allocation
> failure: order:0, mode:0x220(GFP_NOWAIT|__GFP_NOTRACK)
> Jul 16 06:01:07 dom0 kernel: [452365.438870] CPU: 0 PID: 28450 Comm:
> 12.xvda3-0 Tainted: G   O4.9.34-29.el6.x86_64 #1
> Jul 16 06:01:07 dom0 kernel: [452365.454213] SLUB: Unable to allocate
> memory on node -1, gfp=0x200(GFP_NOWAIT)
> Jul 16 06:01:07 guest kernel: end_request: I/O error, dev xvda3, sector
> 6477112
> Jul 16 06:01:09 dom0 kernel: [452366.732994] 12.xvda3-0: page allocation
> failure: order:0, mode:0x220(GFP_NOWAIT|__GFP_NOTRACK)
> Jul 16 06:01:09 dom0 kernel: [452366.733306] CPU: 0 PID: 28450 Comm:
> 12.xvda3-0 Tainted: G   O4.9.34-29.el6.x86_64 #1
> Jul 16 06:01:09 dom0 kernel: [452366.746362] SLUB: Unable to allocate
> 

Re: [CentOS] getting rid of hp c3180

[Fred Smith]

On Thu, Jul 20, 2017 at 07:41:32PM -0500, Michael Hennebry wrote:
> On Thu, 20 Jul 2017, Fred Smith wrote:
> 
> >On Thu, Jul 20, 2017 at 03:27:14PM -0500, Michael Hennebry wrote:
> 
> >>Next on the list is a Brother HL-L2360DW.
> >>It appears to work with linux.
> >>I got as far as this page:
> >>http://support.brother.com/g/b/downloadlist.aspx?c=us=en=hll2360dw_us=127
> >>I infer that the "Driver Install Tool" will install the four listed rpms,
> >>probably from a script.
> >>Is that the way to go?
> >>Printer installs have given me so much joy in the past,
> >>that I approach them with fear and trepidation.
> >
> >I've installed brother drivers by hand, and it involves working
> >through a somewhat cryptic list of modifications you need to do to
> >your Linux system.
> >
> >other times I use their driver install tool and let it do what is needed.
> 
> Thanks.
> 
> If  I use the install tool,
> does it matter whether I have the printer connected during the install?
> I'll be using USB 2.

sorry, I don't know the answer to that question.

-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
 God made him who had no sin
  to be sin for us, so that in him
 we might become the righteousness of God."
--- Corinthians 5:21 -
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] TeX Live on CentOS 7

[Nicolas Kovacs]

Hi,

I just installed the OpenVAS vulnerability scanner on my CentOS 7
workstation. Everything seems to work fine, except PDF generation. The
'openvas-check-setup' script tells me that PDF generation works fine,
but whenever I want to generate a report, the result is unusable and
can't open in Evince or Okular.

After googling a bit, I found out that several users complained that Tex
Live is broken under RHEL/CentOS 7.

While I did use LaTeX a long time ago to write documents, I don't use it
anymore nowadays (just Markdown or LibreOffice). But I do need a working
installation of TeX Live for OpenVAS PDF reports.

What can I do now? Perform a manual installation of TeX Live with their
provided installer (to /opt) and then blacklist all texlive* packages? I
admit I'm a bit surprised that a distribution like RHEL/CentOS that
prises quality wouldn't provide a working TeX Live in their package
repositories.

Any suggestions?

Niki
-- 
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Web  : http://www.microlinux.fr
Mail : i...@microlinux.fr
Tél. : 04 66 63 10 32
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos