Re: [CentOS] firewalld management on a headless server

[Ned Slider]

On 27/03/17 22:43, Valeri Galtsev wrote:


On Mon, March 27, 2017 3:58 pm, Mike wrote:

I don't think it's going to give you a web-based firewall configuration
tool.


Firewall/router system I use is pfSense:

https://pfsense.org/

It has nice web interface for configuration of everything, based on
FreeBSD (very slim, lightweight, small footprint). Has a lot what you may
want to have in router box, including VPN,... If OP is not married to what
he currently uses I would recommend to try pfSense.

Good luck!

Valeri



Or just buy a dedicated router/firewall box. The Ubiquiti EdgeRouter 
Lite 3 is a true gigabit router/firewall that runs iptables and has a 
very nice web interface, all for under $100. Also highly recommended.



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

Re: [CentOS] Centos7 USB wifi recommendation

[Ned Slider]

On 21/03/17 05:02, Arun Khan wrote:

On Tue, Mar 21, 2017 at 5:39 AM, Robert Moskowitz  wrote:

I am looking for one of those very small USB wifi adapters for the server I
am working on.  I am tired of dealing with the 4" long TP-LINK I have and
for my purposes, one of those little 1cm ones would do.  But which work with
Linux?  When I was last in the store, only the TP-LINK said it was supported
on Linux...



Most of the 1cm WiFi dongles have a Realtek chip.  The rtl819x
supports quite a few Realtek WiFi chipset
(https://wireless.wiki.kernel.org/en/users/drivers/rtl819x).
I have bought a few on eBay for a couple of bucks each and they worked
out fine.   The device is activated when plugged into an USB port
(ifconfig -a).



Just to add, the RHEL 7.3 kernel backported the wireless stack from 
kernel-4.7, so if a chipset is supported by kernel-4.7 then it should be 
supported in latest CentOS 7.


Hope that helps.


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

Re: [CentOS] New C7 kernel ABI and kmods

[Ned Slider]

On 03/03/17 22:56, Fred Smith wrote:

On Fri, Mar 03, 2017 at 12:03:52PM -0800, Akemi Yagi wrote:

On Fri, Mar 3, 2017 at 9:16 AM, Lamar Owen  wrote:

All,

This is just a heads-up that the new C7 update kernel breaks ABI
compatibility, at least as far as using the ELrepo nVidia drivers is
concerned.  I have posted more details to the ELrepo list; but since many
folks use the Elrepo kmods I thought a heads-up would be appropriate.

If you use the ELrepo nvidia kmod you will either need to hold off on the
kernel update or uninstall the nvidia kmod.


This is being tracked here:

https://elrepo.org/bugs/view.php?id=720


didn't we just go thru this a few months ago? they're breaking it again?




It's not uncommon for bits (non kABI whitelisted bits) of the kernel ABI 
to change at point releases, but in my experience it's very uncommon for 
the ABI to change within a point release series. To the best of my 
knowledge I recall it happening twice before on the EL6 kernel, once 
such example was here:


http://elrepo.org/bugs/view.php?id=406

Of course any kABI changes will only affect 3rd party kernel modules 
using those specific ABIs so the vast majority of users will be 
oblivious to the changes. It just so happens in this case it affected 
the 3rd party nvidia drivers which are widely used.



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

Re: [CentOS] mach64 driver, latest update in CentOS 6.8, symbol lookup error

[Ned Slider]

On 09/02/17 17:44, Styma, Robert (Nokia - US) wrote:



Styma, Robert (Nokia - US) wrote:



looks like, the driver isn't rebuilt, take the centos 6.8 ISO and look
how it goes.



I download the ISO's and started the reinstall.  It went through all
the normal setup up to outputting the message that it was starting
Anaconda.   Then the screen went blank and stayed that way.  This is
the same symptom as when it is trying to start.  While the driver was
not rebuild I suspect something that accesses the driver added a call
to xf86LinearVidMem which is not found in the symbol list for the
driver.

I am not sure where to go from here.


I would recommend doing the reinstall, but choose *text* mode install.
You'd get through the install, and it might detect and build the video
driver correctly.



  mark


I installed with text mode.  It does not give you options and does a very minimal 
install.  X is not included.  Neither is ssh/scp/rsync.  Fortunately yum was included.  I 
did a "yum groupinstall Desktop" which brought in the X server and the other 
necessary bits.  It did behave differently.  It just loaded drivers vesa and modeset.  It 
tried to start and then got a segmentation exception at address 0x0.  Last thing it tried 
to do was disable the keyboard and mouse.

The monitor flags the input as bad with the message "Input Not Supported".   I 
think I am following the wrong rabbit hole as it  never had the chance to do any analysis 
as to what type of card it was.  Looking backward, the mach64 that was identified worked 
correctly at CentOS 6.7.  I suspect that the Xserver changed and the driver was not 
updated to match it.  This conclusion fits with the fact that a previous poster on this 
thread said the driver was not rebuilt and the original messages:


X: symbol lookup error: /usr/lib64/xorg/modules/drivers/mach64_drv.so: 
undefined symbol: xf86LinearVidMem
X: symbol lookup error: /usr/lib/xorg/modules/drivers/mach64_drv.so: undefined 
symbol: xf86LinearVidMem


Indicate a  reference to a symbol that does not exist in the driver.  Note that 
the two messages were from separate loads of the OS.



This is a known issue:

https://www.centos.org/forums/viewtopic.php?f=13=58168

I would recommend filing a bug with Red Hat to have them fix it.


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

Re: [CentOS] downgrading packages

[Ned Slider]

On 02/02/17 06:32, Jon LaBadie wrote:

After the large update from 7.2 -> 7.3 there is
one major problem, the amanda backup packages.

Strange situation, the host is the amanda server
is working fine at backing up all my remote clients.
But it has an error backing up itself.

The amanda packages did not change version (3.3.3)
and I've done no configuration change.



Looking back at the released versions, amanada was updated from 3.3.3-13 
to 3.3.3-17 in the 7.3 release.


You can grab the old version here:

http://vault.centos.org/7.2.1511/os/x86_64/Packages/


I'm not looking for help debugging this at the moment.
Instead I'd like to downgrade the amanda packages
to see if the original function can be restored.  But
when I ask yum to downgrade, there are no packages
available.  Is it still possible to downgrade just
these 4 packages?  How?  What potential problems?

Jon



In this instance yum can not downgrade the package for you as CentOS 
(unlike Red Hat) don't keep all previously released versions available 
in the current repo so in this instance yum can't find any previous 
versions as it was from the 7.2 snapshot in time whereas the current 
CentOS repo only contains packages from the 7.3 snapshot in time forwards.


So you would need to grab the package from the vault (about) and 
manually downgrade.


Hope that helps.




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

Re: [CentOS] nVidia K1200 on Centos

[Ned Slider]

On 28/12/16 01:07, H wrote:

Can anyone confirm that the above 4-port card is supported at its full 
resolution and capabilities under CentOS 6 and/or 7? The card has four 
DisplayPort 1.2 connectors, each capable of driving a 4K monitor.

Thank you.


According to NVIDIA the card is supported by the latest NVIDIA 
proprietary driver:


ftp://download.nvidia.com/XFree86/Linux-x86_64/375.26/README/supportedchips.html

I believe support was added in the 346.xx series driver, so anything 
newer than that should support your card.


Hope that helps.


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

Re: [CentOS] Power Cut

[Ned Slider]

On 30/10/16 07:11, Hadi Motamedi wrote:

But the site is far remote and having alert on battery exhaustion can no
longer help . As I said before , I am suspicious if it comes from frequent
power cuts so seeking some means to distinguish it among the system logs.
Thank you in advance




Your UPS should be capable of logging to /var/log/messages and should 
also be capable of powering down the system cleanly when the battery 
reaches a predetermined critical level (either run time remaining or 
percentage charge), so there shouldn't be any uninitiated shutdowns. The 
UPS logs should tell you exactly how many power outages you are getting 
together with how long each one lasts. It sounds like you haven't 
configured your UPS.







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

Re: [CentOS] Disable hybernate/suspend in CentOS 7

[Ned Slider]

On 13/10/16 16:33, Valeri Galtsev wrote:

Dear Experts,

Could someone point me in the right direction: how can I disable
hybernate/suspend in CentOS 7?

I get workstations for graduate students with decent amount of RAM (32
GB), and for machines with large RAM I either do not have swap at all of
have some small (4 GB) swap. As I remember from older manuals, one has to
have at least twice amount of swap compared to physical RAM for
hybernate/suspend to work. This probably is what bit me: new Dells came
with keyboard that has sleep button, when one hits that button the machine
locks up. (it stays powered on, does not respond mouse, keyboard, does not
respond ping).

I would like to disable that sleep button on keyboard. (I'm kind of trying
to avoid replacing keyboard with the ones that do not have "sleep" key).

Thanks a lot for all your help!

Valeri



You should be able to do this with PolicyKit:

https://access.redhat.com/solutions/33954

This solution is for RHEL6, but the same polkit rule should work on RHEL7.


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

Re: [CentOS] porting spec files

[Ned Slider]

On 07/10/16 10:17, Alice Wonder wrote:



On 10/07/2016 01:44 AM, Ned Slider wrote:

On 06/10/16 22:50, Alice Wonder wrote:

An rpm intended for a bleeding edge Fedora builds perfectly for me when
I comment two macros apparently not in CentOS 7 -

%transfiletriggerin

and

%transfiletriggerun

Looks like they operate similar to %post and %postun but are different.

Is a simple way to do what they do in CentOS 7 or do I have to change
the packaging logic to build in CentOS 7 and have things work properly?



These are file triggers, they trigger scripts to run when specific files
are added or removed from the system when packages are (un)installed.
See here:

http://www.rpm.org/wiki/FileTriggers


Whilst RHEL's version of RPM doesn't support file triggers, it does
support package triggers, so maybe you could devise a workaround with
those:

http://rpm.org/api/4.4.2.2/triggers.html




Okay it looks like what is happening is the triggers are used when
plugins are installed, and the CentOS 7 way is to run those triggers in
the post/pre scriptlets of the packages that have the plugins.



Yes, that is the preferred method and is OK as long as you also have 
packaging control over the packages that provide the plugins. The point 
of the file triggers is for when that is not the case.


Generally, triggers should be used sparingly (as a last resort) as they 
have a tendency to complicate matters rather than simplify, and thus 
make troubleshooting issues much harder.


For example, you package some software that needs to do something every 
time the kernel is updated. You don't have control over the kernel 
package, so you use a trigger in your own package - either a package 
trigger if the action needs to be performed every time the kernel 
package is (un)installed/updated, or a file trigger if it's when a 
specific file is (un)installed/updated.


The reason it makes things hard to troubleshoot is that, using the 
example above, the kernel is updated and that triggers your script in 
package Foo and something goes wrong. You've narrowed it down to 
happening every time you update the kernel package so naturally you now 
spend an age going through the kernel SPEC file trying to find the cause 
but of course you are looking in the wrong place and will never find it.



Probably better to have the file trigger conceptually, less chance for
scriptlet bugs, but CentOS 8 will come soon enough I suppose ;)



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

Re: [CentOS] porting spec files

[Ned Slider]

On 06/10/16 22:50, Alice Wonder wrote:

An rpm intended for a bleeding edge Fedora builds perfectly for me when
I comment two macros apparently not in CentOS 7 -

%transfiletriggerin

and

%transfiletriggerun

Looks like they operate similar to %post and %postun but are different.

Is a simple way to do what they do in CentOS 7 or do I have to change
the packaging logic to build in CentOS 7 and have things work properly?



These are file triggers, they trigger scripts to run when specific files 
are added or removed from the system when packages are (un)installed. 
See here:


http://www.rpm.org/wiki/FileTriggers


Whilst RHEL's version of RPM doesn't support file triggers, it does 
support package triggers, so maybe you could devise a workaround with those:


http://rpm.org/api/4.4.2.2/triggers.html


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

Re: [CentOS] CM8828 sound chip ??

[Ned Slider]

On 20/09/16 18:37, Alice Wonder wrote:

Need a PCI-E sound card with low profile bracket, optical out, and one
of those mini-din connectors that fans out into various analog connectors.

Only card I have been able to find so far uses a CM8828 chipset.

Looks like that chipset is natively supported by the kernel alsa driver
starting in 3.17 kernel but CentOS 7 uses 3.10 kernel.



It may have started out it's life as a 3.10 kernel, but Red Hat 
constantly backports updated drivers to support new hardware.


The only way to tell whether or not it is supported by a given driver is 
to query the PCI vendor:device ID.


Once you know these, you can query your system to see if the device is 
supported by any of your installed kernels:


grep -i VendorID /lib/modules/*/modules.alias | grep -i DeviceID


I did not see a package that was obviously for that chipset in elrepo.

Has that driver been backported into the RHEL/CentOS 7 kernel, and if
not, is it in elrepo?

Worst case scenario I suppose it may be possible to port the driver like
many of the elrepo drivers have been, but not sure I want to buy
hardware based on a "may be possible"

Thanks for any comments.


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

Re: [CentOS] Email pid issue

[Ned Slider]

On 22/08/16 02:10, Jay Hart wrote:

Hello gents,

First time poster here!

Current system running Centos 6.8. Buddy of mine posted a few days back about 
me wanting to move
from Postfix 2.6.x to 2.8 to above, still under centos 6.8.  I might move over 
to 7, but probably
not for a while, don't have the resources presently to make this happen.

Running Centos 6.8, postfix 2.6.6, clamav 0.99.1. Basic Centos 6.8 box fully 
patched using stable
repos.

ISSUE_

Logwatch is reporting this error, which I'm going to assume has been occurring 
for a few years but
doesn't affect sending/receiving emails, so I haven't chased it down, now I'm 
looking to fix that.

1   (06498-19) ClamAV-clamd: All attempts (1) failed connecting to
/var/spool/amavisd/clamd.sock, retrying (1)

Since this is reported by "ClamAV-clamd", I am assuming this is coming from 
amavisd.conf.  My
logic on this is that a grep search for that particular string only shows up in 
the
/etc/amavisd.conf file, when its calling the scanner.  Pasted code from file 
below:

@av_scanners = (
['ClamAV-clamd',
  \_daemon, ["CONTSCAN {}\n", "/var/spool/amavisd/clamd.sock"],
  qr/\bOK$/m, qr/\bFOUND$/m,
  qr/^.*?: (?!Infected Archive)(.*) FOUND$/m ],

Best I can determine /var/spool/amavisd/clamd.sock file exists. So, not sure 
what is causing this
or why, or how to fix.



and what does clamd.conf say:

cat /etc/clamd.conf | grep 'clamd.sock'


Does it match the "/var/spool/amavisd/clamd.sock" entry above?


Here is /var/spool/amavisd contents:

[run]# ls -al /var/spool/amavisd/
total 64
drwxr-x---   7 amavis amavis  4096 Aug 21 19:10 .
drwxr-xr-x. 15 root   root4096 Mar 15  2012 ..
srwxr-x---   1 amavis amavis 0 Aug 21 19:10 amavisd.sock
srw-rw-rw-   1 amavis amavis 0 Aug 21 19:10 clamd.sock
drwxr-x---   2 amavis amavis  4096 Aug 21 19:10 db
drwxr-x---   2 amavis amavis 36864 Aug 21 19:50 quarantine
drwxr-x---   2 amavis amavis  4096 Aug 21 09:23 .razor
drwx--   2 amavis amavis  4096 Aug 21 20:42 .spamassassin
drwxr-x---   4 amavis amavis  4096 Aug 21 20:42 tmp


Seems to be owned by the right group, I rebooted at 19.10 today hence timestamp 
date/time.



Is the clamav user a member of the amavis group? i.e, does the user clam 
runs under have access to the socket?



So, my question is, what do I need to do to eliminate this error?  How can I 
chase it down?



Check the two most common causes above :-)


TIA,

Jay


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

Re: [CentOS] hfsplus on C7

[Ned Slider]

On 16/08/16 20:17, Jerry Geis wrote:

Thanks Ned... here it is.


The following issue has been SUBMITTED.
==
https://elrepo.org/bugs/view.php?id=669
==
Reported By:Jerry Geis
Assigned To:
==
Project:channel: elrepo/el7
Issue ID:   669
Category:   kmod-hfsplus
Reproducibility:always
Severity:   minor
Priority:   normal
Status: new
Reported upstream:
==
Date Submitted: 2016-08-16 13:16 MDT
Last Modified:  2016-08-16 13:16 MDT
==
Summary:hfsplus does notwork with latest kernel
3.10.0-327.28.2.el7.x86_64
Description:

It would appear that the hfsplus kernel module does not weak-link
against the very latest kernel (3.10.0-327.28.2.el7.x86_64).

==

Issue History
Date ModifiedUsername   FieldChange
==
2016-08-16 13:16 Jerry Geis New Issue
==



Thanks!

The latest kernel update (3.10.0-327.28.2.el7.x86_64) broke the ABI of 
the kernel(blkdev_issue_flush) symbol.


It's unusual/rare to get kABI breakage within a kernel series (as 
opposed to at a point release), but it can occasionally happen for 
symbols that are not on the kernel whitelist as is the case here.


I've built you an updated package that should hopefully fix the issue 
and it's currently syncing to the mirrors.


hfsplus-kmod-0.0-3.el7.elrepo.src.rpm
kmod-hfsplus-0.0-3.el7.elrepo.x86_64.rpm

Note: this package will only work with kernel-3.10.0-327.28.2.el7.x86_64 
and above.




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

Re: [CentOS] hfsplus on C7

[Ned Slider]

On 16/08/16 18:24, Jerry Geis wrote:

It would seem kmod-hfsplus does not have a module for my kernel

uname -r
3.10.0-327.28.2.el7.x86_64




As a temporary workaround Jerry, could you try booting from your 
previous kernel-3.10.0-327.22.2.el7.x86_64 and see if hfsplus works for 
you on that kernel.


As I said in my previous post, once you've filed a bug report I'll see 
if I can fix the issue so we can get you a working kernel module that 
supports your latest kernel.


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

Re: [CentOS] hfsplus on C7

[Ned Slider]

On 16/08/16 18:13, Jerry Geis wrote:

Please show:

find /lib/modules -name hfs*.ko

and

rpm -qa kernel | sort


rpm -qa | grep hfsplus
kmod-hfsplus-0.0-2.el7.elrepo.x86_64
hfsplus-tools-540.1.linux3-4.el7.x86_64
[root@nuc5i3 ~]#
[root@nuc5i3 ~]# find /lib/modules -name hfs*.ko
/lib/modules/3.10.0-327.el7.x86_64/weak-updates/hfs/hfs.ko
/lib/modules/3.10.0-327.el7.x86_64/weak-updates/hfsplus/hfsplus.ko
/lib/modules/3.10.0-327.4.4.el7.x86_64/weak-updates/hfs/hfs.ko
/lib/modules/3.10.0-327.4.4.el7.x86_64/weak-updates/hfsplus/hfsplus.ko
/lib/modules/3.10.0-327.22.2.el7.x86_64/weak-updates/hfs/hfs.ko
/lib/modules/3.10.0-327.22.2.el7.x86_64/weak-updates/hfsplus/hfsplus.ko
/lib/modules/3.10.0-327.28.2.el7.x86_64/weak-updates/hfs/hfs.ko
/lib/modules/3.10.0-229.el7.x86_64/extra/hfs/hfs.ko
/lib/modules/3.10.0-229.el7.x86_64/extra/hfsplus/hfsplus.ko
[root@nuc5i3 ~]# uname -r
3.10.0-327.28.2.el7.x86_64
[root@nuc5i3 ~]# rpm -qa  kernel | sort
kernel-3.10.0-327.22.2.el7.x86_64
kernel-3.10.0-327.28.2.el7.x86_64
kernel-3.10.0-327.4.4.el7.x86_64
kernel-3.10.0-327.el7.x86_64

Next step?
Thanks



Thank you Jerry.

It would appear that the hfsplus kernel module does not weak-link 
against the very latest kernel (3.10.0-327.28.2.el7.x86_64).


Please would you file a bug report at elrepo.org/bugs against the 
kmod-hfsplus el7 package and I will do my best to fix it for you.


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

Re: [CentOS] hfsplus on C7

[Ned Slider]

On 16/08/16 16:05, Jerry Geis wrote:

I dont see anything hfsplus in the modules area???




Please show:

find /lib/modules -name hfs*.ko

and

rpm -qa kernel | sort

thanks


uname -r





3.10.0-327.28.2.el7.x86_64





[root@nuc5i3 ~]# find /lib/modules/3.10.0-327.28.2.el7.x86_64/ |grep hfs
/lib/modules/3.10.0-327.28.2.el7.x86_64/kernel/fs/squashfs
/lib/modules/3.10.0-327.28.2.el7.x86_64/kernel/fs/squashfs/squashfs.ko
/lib/modules/3.10.0-327.28.2.el7.x86_64/kernel/net/sched/sch_hfsc.ko
/lib/modules/3.10.0-327.28.2.el7.x86_64/weak-updates/hfs
/lib/modules/3.10.0-327.28.2.el7.x86_64/weak-updates/hfs/hfs.ko

The packages are installed:


rpm -qa | grep hfs
kmod-hfs-0.0-2.el7.elrepo.x86_64
kmod-hfsplus-0.0-2.el7.elrepo.x86_64
hfsplus-tools-540.1.linux3-4.el7.x86_64

modprobe hfsplus gives the error: hfsplus not found

mkfs.hfsplus is present.

but hfsplus is not available? why not.

Thanks,

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


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

Re: [CentOS] Locked out of the CentOS Fora

[Ned Slider]

Hi Dan,

A forum administrator has reset your account so you should receive an 
email shortly.


Thanks.


On 15/08/16 12:54, Dan White wrote:

The username/email combo I give the "forgot password" option does not
work and I cannot re-register as it says my email is in use.

Suggestions ?
Dan White | d_e_wh...@icloud.com

“Sometimes I think the surest sign that intelligent life exists
elsewhere in the universe is that none of it has tried to contact us.”
(Bill Waterson: Calvin & Hobbes)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

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

Re: [CentOS] postscreen and clamav on CentOS 6.8

[Ned Slider]

On 12/08/16 21:38, Jon LaBadie wrote:

A friend runs 6.8 but would like to add postscreen
to his email server.  It is provided with postfix
version 2.8 and up.  The newest postfix for 6.8
is 2.6.x.  Any likelyhood it will be further
updated?  Or is there another source for newer
postfix versions for CentOS 6.8?



It is very unlikely Postfix will ever be updated from the current 
version in CentOS 6. Maybe CentOS 7 has the version you require?



Similar query for the clamav db, now at 0.99.1
with 0.99.2 out for quite some time.



ClamAV is not a part of CentOS so you will need to ask on the mailing 
list for whichever repository you got the package from.


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

Re: [CentOS] installing centos 7 32 bit i386 to laptop

[Ned Slider]

On 28/07/16 07:36, geo.inbox.ignored wrote:



On 07/28/16 01:13, Ned Slider wrote:

On 28/07/16 06:16, John R Pierce wrote:

<<>>


hmmm, that repository has no 32 bit RPMs.

http://mirror.steadfast.net/centos/7/os/

but they do exist here, http://mirror.centos.org/altarch/7/os/ and
http://mirror.centos.org/altarch/7/updates/

so you might need to tweak your /etc/yum.repos.d files a bit.




Additionally, most 3rd party repos (e.g, epel above) do not ship 32-bit
packages for el7 as there is no 32-bit offering of RHEL from Red Hat. So
not much point configuring them in yum.


--->

hi Ned, you up late or early on your side of the pond?

the above altarch 7 repos links do have both 32 and 64 bit directories.



I was referring to the entry you had for the EPEL repository, not the 
distro repos.



after reading John's post, i logged them and bookmarked both.

when i am trying something new, as i am now, i like to pull files so
i have them local. saves going back online if i mess something up and
have need again.



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

Re: [CentOS] installing centos 7 32 bit i386 to laptop

[Ned Slider]

On 28/07/16 06:16, John R Pierce wrote:

On 7/27/2016 9:58 PM, geo.inbox.ignored wrote:

$ sudo yum install NetworkManager-wifi
[sudo] password for geo:
Loaded plugins: aliases, changelog, fastestmirror, ovl, presto, refresh-
   : packagekit, security, tmprepo, verify, versionlock
Setting up Install Process
Loading mirror speeds from cached hostfile
  * base: mirror.steadfast.net
  * epel: mirror.steadfast.net
  * extras: mirror.steadfast.net
  * updates: mirror.steadfast.net
extras   | 3.3 kB
00:00
updates  | 3.4 kB
00:00
updates/primary_db   | 1.3 MB
00:01
No package NetworkManager-wifi available.


hmmm, that repository has no 32 bit RPMs.

http://mirror.steadfast.net/centos/7/os/

but they do exist here, http://mirror.centos.org/altarch/7/os/ and
http://mirror.centos.org/altarch/7/updates/

so you might need to tweak your /etc/yum.repos.d files a bit.




Additionally, most 3rd party repos (e.g, epel above) do not ship 32-bit 
packages for el7 as there is no 32-bit offering of RHEL from Red Hat. So 
not much point configuring them in yum.


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

Re: [CentOS] installing centos 7 32 bit i386 to laptop

[Ned Slider]

On 26/07/16 19:04, geo.inbox.ignored wrote:


greetings one and all.

installing centos 7 32 bit i386 to laptop;

specs:

toshiba satellite l455d-s5976
amd sempron si-42
2 GB ddr2
250 GB hdd

]$ lspci|grep Realtek
0e:00.0 Network controller: Realtek Semiconductor Co., Ltd. \
RTL8187SE Wireless LAN Controller (rev 22)
14:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. \
RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller (rev 02)

]$ lspci|grep VGA
01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] \
RS780MC [Mobility Radeon HD 3100]

centos 6:
network and vga controllers ok.
ethernet controller not recognized.

3 questions:

anyone have problems installing 7 32 bit to a laptop?

any suggestions for getting ethernet controller to work?



I have no experience with the 32-bit builds (but device support should 
be otherwise identical), but that device should be supported by the in 
kernel r8169 driver. Grepping for the Vendor:Device ID pairing in 
modules.alias for your kernel will determine that for sure.




any way to turn off touch pad? using logitech m570 marble.


any/all suggestions/comments greatly appreciated.

tia.



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

Re: [CentOS] [CENTOS ]IPTABLES - How Secure & Best Practice

[Ned Slider]

On 30/06/16 23:19, Mike wrote:

Ned,

Thank you very much for the response.
Great example following through on the premise.
It sounds like I need to have a better understanding of the traffic
patterns on my network to know the optimal order for iptables
filtering rules.



Try running:

iptables -nv -L

which will show you in the left hand column a counter for the number of 
packets that has matched each rule. That will give you an exact 
breakdown of how often your rules are being hit.



My brief example -

Premise:  I want to limit outsiders from interfering with LAN client machines.
So, I have the following rules regarding forwarding traffic:

-A FORWARD -m state --state INVALID -j DROP
-A FORWARD -p tcp --tcp-flags ACK,FIN FIN -j DROP
-A FORWARD -p tcp --tcp-flags ACK,PSH PSH -j DROP
-A FORWARD -p tcp --tcp-flags ACK,URG URG -j DROP
-A FORWARD -p tcp --tcp-flags FIN,RST FIN,RST -j DROP
-A FORWARD -p tcp --tcp-flags SYN,FIN SYN,FIN -j DROP
-A FORWARD -p tcp --tcp-flags SYN,RST SYN,RST -j DROP
-A FORWARD -p tcp --tcp-flags ALL ALL -j DROP
-A FORWARD -p tcp --tcp-flags ALL NONE -j DROP
-A FORWARD -p tcp --tcp-flags ALL FIN,PSH,URG -j DROP
-A FORWARD -p tcp --tcp-flags ALL SYN,FIN,PSH,URG -j DROP
-A FORWARD -p tcp --tcp-flags ALL SYN,RST,ACK,FIN,URG -j DROP
-A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
-A FORWARD -i LAN-NIC -s 10.100.100.0/24 -o INET-NIC -m state --state
NEW -j ACCEPT
-A FORWARD -i INET-NIC -o LAN-NIC -d 10.100.100.0/24 -m state --state
NEW -j ACCEPT



The first thing I would do is move your ESTABLISHED,RELATED rule to the 
top of the chain. Once you've accepted the first packet you may as well 
accept the rest of the stream as quickly and efficiently as possible as 
you've established the connection is not malicious.


What is the default policy for the FORWARD table? Assuming it is accept 
then the last two accept rules can be removed.



But I don't know if this is interfering with, or delaying DNS requests
between LAN clients and the DHCP server.


The FORWARD chain only processes packets being router through the 
machine, so in your case that would be packets from the lan destined for 
the wan, or packets from the wan destined to the lan. All internal lan 
traffic such as dns requests from clients to the dchp server are 
internal and not subject to the FORWARD chain. Of course the dhcp server 
probably forwards those dns requests to a dns server outside of the lan 
so those requests will pass through the FORWARD chain at that point.


Assuming your hardware is not crippled or the cpu constantly overloaded, 
it's not going to have any problems routing traffic through your rule 
set. But if you want to ensure particular traffic is processed quickly 
and bypasses all other rules, place a rule matching it near the top to 
accept that traffic. For example, if you trust all traffic coming from 
inside your network that is destined for the outside and want to pass 
that traffic without testing for all those tcp flags (and any other 
rules), you could do something like:


-A Forward -p all -i LAN-NIC -o INET-NIC -j ACCEPT

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

Re: [CentOS] [CENTOS ]IPTABLES - How Secure & Best Practice

[Ned Slider]

On 30/06/16 18:49, Mike wrote:

On Wed, Jun 29, 2016 at 1:49 PM, Gordon Messmer
 wrote:


By putting these rules first, before the "ESTABLISHED,RELATED" rule, you're
applying additional processing (CPU time) to the vast majority of your
packets for no reason.  The "E,R" rule should be first.  It won't match the
invalid packets you're trying to drop.

You're not specifying the "new" state in any of your input ACCEPT rules,
which means that you're also ACCEPTing invalid packets that don't match the
handful of invalid states you DROPped earlier.


 1. The drop commands at the beginning of each chain is for increase
 performance.



I understand what you're trying to do, but in the real world, this will
decrease performance.



Gordon,

I appreciate your observations.
I've been using iptables for a long time and still don't really know
how to configure the order of rules to optimize performance while
providing thorough filtering as a component of security.
Can you share links and/or other sources and guides on this subject.

Thank you.


Hi Mike,

If I may reply...

The premise is simple, rules are located in chains. Chains of rules are 
evaluated from top to bottom, until the packet being evaluated matches a 
rule. You want to order your rules so that packets pass through as few 
rules as possible, i.e they are matched and either accepted or rejected 
as soon as possible. Each time a packet is evaluated against a rule it 
is using CPU cycles, so the fewer the better.


Of course the number of rules evaluated will depend on the packet. For 
example, if you run a mail server receiving 1,000 emails per day, a web 
server with 10,000 hits per day and a DNS server with 100,000 queries 
per day, it makes sense to order your rules to accept the DNS queries 
first, followed by http traffic, and to accept the smtp traffic last.


This ordering would cause 111,000 packets to be evaluated by the first 
rule, 11,000 by the second rule and 1,000 by the third rule giving a 
total of 123,000 times a packet was inspected by a rule. If we reversed 
the order we would see 111,000 for our first rule, 110,000 for our 
second rule and 100,000 for our third rule, giving a total of 321,000 
examinations which is 2.6 times more than our first example. Don't 
forget it's only the initial (first) packet of each connection that is 
passing down through our chain of rules - all subsequent packets would 
be matched against our Established,Related SPI rule which is typically 
placed at the very top of the chain so our firewall doesn't have to 
examine every packet of that 100MB email you just received in the same 
way as it examines the first packet. This is the rule that will always 
by far match the most packets hence why it's always placed near or at 
the top of the chain.


This is a very simplistic approach but you get the idea.

As things get more complicated, you can create user-defined chains to 
filter off certain traffic for further examination, maybe logging action 
and/or rate-limiting, rather than subjecting all packets to that extra 
scrutiny where it is not applicable thus improving the overall 
efficiency. You want to make the flow of packets through the firewall as 
efficient as possible. This approach is only really needed where you 
want a given packet to be evaluated by two or more rules (e.g, log the 
packet then drop it).


In reality most modern hardware is more than capable of achieving 
throughput that isn't going to be rate limiting even with quite complex 
rule sets, but we all like to optimise stuff anyway don't we :-)



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

Re: [CentOS] yum "Requires" yum-plugin-fastestmirror; why?

[Ned Slider]

On 17/06/16 20:04, Warren Young wrote:

In another recent thread,[1] someone was having trouble with the 
yum-plugin-fastestmirror feature, so I suggested he remove it, since it’s just 
a plugin and should therefore be optional.  He reported that it couldn’t be 
removed due to package dependencies.

I investigated further and found that this also affects CentOS 5.11 and CentOS 
7.2.  (The OP is on CentOS 6.8.)  So, I reported it as a bug upstream, and they 
claim their yum package doesn’t do that, so they’re bouncing the problem back 
downstream.

I checked, and they’re right insofar as CentOS’s current C7 yum.spec file has 
this on line 118:

   Requires: yum-plugin-fastestmirror

I then tried to go get the RHEL SRPM for yum to compare its spec file to C7’s, 
but their download site just refers visitors to git.centos.org, and the yum 
repo there doesn’t seem to have an upstream RHEL7 branch.

So, I started poking around in the yum.spec file history, and indeed, the 
oldest yum.spec file on the c7 branch doesn’t have that Requires line!  It was 
introduced in checkin f1c1b982, which claims all it does is “debrand 
yum-3.4.3-132.el7”.[2]

I realize it is in the CentOS project’s best interest if users always use the 
fastest mirror when downloading, but I claim that it is a bug to mark any 
plugin as Requires, particularly when upstream does not.



Correct, the fastestmirror plugin is a requirement on CentOS (and 
Scientific Linux) but is not on RHEL.


It was originally discussed here:

https://lists.centos.org/pipermail/centos-devel/2008-June/002864.html

Personally, I'm firmly in favour of having fastestmirror plugin as a 
dependency in yum as it will benefit the vast majority of people IMHO. 
Plus it is easily disabled for those who disagree.


The very fact it's taken 8 years for anyone to notice/comment kind of 
supports this point of view.


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

Re: [CentOS] Today's firefox update

[Ned Slider]

On 17/06/16 04:18, Frank Cox wrote:

Johnny's announcement refers to:
firefox-45.2.0-1.el5.centos.src.rpm
firefox-45.2.0-1.el6.centos.src.rpm
firefox-45.2.0-1.el7.centos.src.rpm

The linked rhel webpage refers to:
firefox-45.2.0-1.el5_11.src.rpm
firefox-45.2.0-1.el6_8.src.rpm
firefox-45.2.0-1.el7_2.src.rpm

These do not appear to be the same thing.  Note the numbers just before the 
.src part of the filenames.



CentOS drop the underscore part of the dist tag when they rebuild them. 
Checking the changelog should confirm they are the same.


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

Re: [CentOS] yum timeout ... (CentOS 6.8)

[Ned Slider]

On 16/06/16 19:41, Walter H. wrote:

On 16.06.2016 19:40, Frank Cox wrote:

On Thu, 16 Jun 2016 19:34:09 +0200
Walter H. wrote:


Yes, but doesn't help ...
the same before ...

by the way, I can't image that there is no mirror in Europa,
and that the "timeout"-mirrors from US are the fastest;

yum -disableplugin=fastestmirror nowseewhathappens.



yes this goes fast, no timeout;
can I configure this in /etc/yum.conf?



The correct way to disable a yum plugin is to set enabled to zero in the 
plugin config file:


/etc/yum/pluginconf.d/fastestmirror.conf

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

Re: [CentOS] Getting hibernate to work on a new CentOS 7.2.1115 install

[Ned Slider]

On 12/06/16 16:45, Globe Trotter wrote:

Hi,
I am a new CentOS user (quite familiar with Fedora 1-23+) and I decided to try 
a new install of CentOS on a ASUS R503U.

However, I can not get hibernate to work. I try:
systemctl hibenaate
and I get:
Failed to execute operation: sleep verb not supported
Btw, the problem does not go away with super-user.

I was wondering how to get around this issue. I would like the abililty to 
hibernate and come back in the last state.
Thanks!


This error message is generated when the sleep operation is not 
possible. Do you have sufficient SWAP configured on your system?


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

Re: [CentOS] Realtek 8111GR on C7

[Ned Slider]

It should be supported by the unified R8169 kernel driver, but the only 
way to know for sure is to check the Device ID against the C7 kernel.



On 03/06/16 11:11, Alessandro Baggi wrote:

Hi list,
I'm planning to buy a mobo (z170-K) that has Realtek 8111GR (nic).

I've tried to search on google about support on C7 but can't fine anything.

There is a way to check if supported?
Is the Realtek 8111GR supported or I must change mobo?

Thanks in advance.

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


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

Re: [CentOS] HFSPlus Question

[Ned Slider]

On 03/06/16 04:45, Chris Murphy wrote:

On Tue, May 31, 2016, 7:59 PM Albert McCann 
wrote:


In CentOS 7.2.1511 does the 3.10.0-327.18.2.el7.centos.plus.x86_64 (Plus)
kernel read HFSPlus iMac drives? I don't see any hfsplus modules installed
anywhere, so I suspect not.



It's in mainline so I don't know why it would not be built. It certainly
exists on Fedora. You could get Fedora live image, dd to a USB stick and it
will boot the Mac.



There are a lot of modules in the equivalent mainline kernel that are 
not enabled / built in the RHEL kernel, reason being RH don't want the 
extra workload of maintaining (backporting fixes) those drivers for the 
10 year lifespan of the product, long after upstream support at 
kernel.org has ended.


In this case they probably determined it unlikely that a user would want 
to hook an HFSPlus volume up to a RHEL server. They also disabled a 
whole bunch of 100Mbit ethernet drivers commonly found on older desktop 
motherboards in RHEL7 for the same reason.


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

Re: [CentOS] E-mail advice sought

[Ned Slider]

On 01/05/16 13:23, Alice Wonder wrote:

On 05/01/2016 05:10 AM, Alice Wonder wrote:


I think this is my autism coming in to play, I think what is very clear
to me I just am not able to adequately communicate because clearly
people are not even remotely grasping what I am trying to convey.



Basically whether it is a white list or a black list doesn't matter.

One is just the complement set of the other.

It's the set I'm after. Or its complement. I don't care. Not whether my
code should use set A or its complement.



See Gordon's previous answer above:

That is, [A-Za-z0-9._][A-Za-z0-9._-]

In other words, allowable characters are A-Za-z (upper and lower case), 
0-9 (numerics), . and _ (period and underscore).


Hyphens are allowed, but NOT as the first character, so maybe easier to 
just not allow hyphens in your account usernames.




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

Re: [CentOS] EPEL - Clamav update?

[Ned Slider]

On 03/04/16 22:10, Ireneusz Piasecki wrote:

W dniu 03.04.2016 o 04:39, Rob Kampen pisze:

EPEL maintainers?
I note messages in the log about updated version 0.99.1 of CLAMAV
being available since Mar 5th.
for CentOS 6 no update is available yet.
I used to use rpmforge for this package but that languished for months
before updates became available and eventually stopped altogether.
Is there something I can do to assist in getting this package updated?
I have no idea if this is a difficult package to compile with lots of
dependancies or some otherwise complexities.
In this era of constant SPAM and so many virus / trojan attempts to do
harm to others, it is vital that we run this package to protect our
users.
Please let me know if / how I can assist.
Kind regards
Rob

Hi,

Does clamav detect anything in this floding e-mail viruses ? My clamav
instalation (with amavisd-new) in centos 5 with the current signatures
detect nothing in compare to virustotal.org antivirus - i noticed that
clamav signatures are lag behind form the top antivir in the market.

Viruses in ZIP archives goes via my e-mail gateway (amavisd-new+clamavd)
and are stopped finally by F-Secure Client Security. So, clamav is
defend from anything ?

Sorry for off topic.



That is pretty much my experience too - I've only seen the occasional FP 
hit from ClamAV on a mail server for as long as I can remember.


The latest flavour of the month seems to be .js ransomware which go 
undetected. I have long blocked all executable file types in amavisd as 
a matter of policy.


IMHO the AV vendors lost the battle a long time ago - they simply can't 
compete with the bad guys nor keep up with the volume and this 
particular layer of defence is now less effective/ineffective.


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

Re: [CentOS] rpmbuild annoyance

[Ned Slider]

On 22/03/16 20:20, m.r...@5-cent.us wrote:

I'm building a package (rasmol, if you must know) from an srpm. It's an
FC20 pkg, nothing older, but the software itself hasn't changed. So... I
try the build, and it fails, telling me:
gcc: %__global_ldflags: No such file or directory
make: *** [rasmol] Error 1

Now, this isn't a brand-new package, so I'm puzzled by the error. Is there
supposed to be something I need to add to the rpmbuild command line,
or...?

Clues for the poor.



You didn't mention which version of CentOS you are trying to build on.

The %__global_ldflags macro was introduced in RHEL7. It's provided by 
redhat-rpm-config. If you're attempting to build on an older version 
then you'll need to fix that.




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

Re: [CentOS] [OT] security bug with firefox and add-on

[Ned Slider]

On 09/03/16 19:11, g wrote:



On 03/09/16 12:46, Mike - st257 wrote:

On Wed, Mar 9, 2016 at 1:38 PM, g  wrote:

<<>>


What version of CentOS and Firefox?


--

centos 6.7, firefox 38.6.1.


Does it affect the latest version of Firefox just released:

firefox-38.7.0-1.el6_7

Is the bug in Firefox or the add-on.

If the bug is in Firefox, then I would report it to Red Hat. CentOS will 
not fix bugs, security or otherwise, as the policy is to rebuild RHEL, 
bugs and all.




<<>>


so my question is just who should i inform of problem?

mozilla.org? author of add-on? cve.mitre.org? all 3?


Author of the add-on would be my first stop.

If it turns out to be a larger bug affecting more than just that add-on,
hopefully the add-on author will run it up the chain to Mozilla.


--

reason in bring this up is if a hacker hacks someone's system and has
knowledge of bug, he most likely will have disassembled add-on and knows
what he needs to know to cause serious problems.

at first, i thought author. after posting and more thought time, authors
tend to be too lax in testing and slow in fixing.

as for mozilla.org, their attitude has become 'not fixable, upgrade to
later version', which in many cases is not doable.

with cve.mitre.org, they just might issue a 'CESA' to remove add-on and
reinstall firefox, do not use add-on until bug is fixed.



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

Re: [CentOS] Intel Xorg driver for Intel HD graphics

[Ned Slider]

You haven't explained the problem you are trying to solve. I assume your
hardware is not supported?

Which version of which package does not support your hardware? At what
version was support added?

On 24/01/16 18:42, Jerry Geis wrote:
> I found this page:
>  https://01.org/linuxgraphics/downloads/2015q4-intel-graphics-stack-release
> 
> I have an Intel NUC5C with "Intel HD" graphics and I'm trying to use CentOS
> 7.2
> 
> I downloaded the files suggested:
> cairo-1.14.4.tar.xz   libva-1.6.2.tar.bz2
> mesa-11.0.4.tar.xz
> intel-gpu-tools-1.13.tar.bz2  libva-intel-driver-1.6.2.tar.bz2
>  xf86-video-intel-2.99.917.tar.gz

No point updating that, it's already at that version in the distro:

$ rpm -q xorg-x11-drv-intel
xorg-x11-drv-intel-2.99.917-8.20150615.el7.x86_64

> libdrm-2.4.65.tar.gz   xorg-server-1.18.0.tar.bz2
> 
> and compiled, then installed them. All are working except the final one
> xorg-server-1.18
> 
> On the configure I get these errors:
> configure: error: Package requirements (fixesproto >= 5.0 damageproto >=
> 1.1 xcmiscproto >= 1.2.0 xtrans >= 1.3.5 bigreqsproto >= 1.1.0 xproto >=
> 7.0.28 randrproto >= 1.5.0 renderproto >= 0.11 xextproto >= 7.2.99.901
> inputproto >= 2.3 kbproto >= 1.0.3 fontsproto >= 2.1.3 pixman-1 >= 0.27.2
> videoproto compositeproto >= 0.4 recordproto >= 1.13.99.1 scrnsaverproto >=
> 1.1 resourceproto >= 1.2.0 xf86driproto >= 2.1.0 glproto >= 1.4.17 dri >=
> 7.8.0 presentproto >= 1.0 xineramaproto xkbfile  pixman-1 >= 0.27.2 xfont
>> = 1.4.2 xau libsystemd-daemon xshmfence >= 1.1) were not met:
> 
> Requested 'xproto >= 7.0.28' but version of Xproto is 7.0.26
> Requested 'randrproto >= 1.5.0' but version of RandrProto is 1.4.0
> 
> 
> I'm not sure what to do with these errors.
> The "proto" packags are nothing that I can install -devel packages for
> as these packages are not even present on the Packages directory that I see.
> 
> 
> Any thoughts how I might get the Xorg server running on the "Intel HD"
> graphics of the NUC5C?
> 
> Thanks,
> 
> Jerry
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
> 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] yum/RPM and Trust on First Use

[Ned Slider]

On 20/12/15 10:28, Gordon Messmer wrote:
> On 12/19/2015 09:49 AM, Alice Wonder wrote:
>>
>> With third party repositories the key and configuration file is often
>> distributed separately. That's the potential attack vector for trojan
>> keys.
> 
> Examples?
> 
> All of the notable repositories that I'm aware of publish an
> x-release.rpm that installs their key and yum repo file.  But if your
> concern is that users might manually install a repo file and public key,
> then I don't see how modifying yum would change that. The attacker would
> probably include a key that contains an address they control and
> validates properly against it.
> 
> In other words, I think the solution to the problem is simply to make
> sure that the repositories publish their "release" rpm over https and
> that documentation reflects the secure URL.  I notice now that EPEL
> links directly to the https URL for their release rpm, but their FAQ
> still provides a command-line example for installation using an http URL.
> 
> The FAQ should be updated.  That method is a potential security problem
> because it doesn't use https and doesn't check the package signature. 
> But the solution is simply to replace http with https in the FAQ.  yum
> isn't used to install the release package, and I think the solution is
> to make sure that malicious release packages don't get installed, not to
> try to behave well on a system where an attacker already installed
> malicious data.
> 

Unless I'm mistaken RPM in el5 does not support the https protocol.


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

Re: [CentOS] Detecting empty office doc containing virus macro

[Ned Slider]

On 29/10/15 10:51, Gary Stainburn wrote:
> On Wednesday 28 October 2015 21:12:19 Ned Slider wrote:
>> On 28/10/15 11:55, Gary Stainburn wrote:
>>> We are receiving LOTS of emails that contain empty XLS or DOC documents
>>> with embedded virus macros.  These are getting past SPAMASSASSIN, Clamav
>>> and Kaspersky.
>>>
>>> I'm trying to write a filter for EXIM to block these emails but I need to
>>> know a good, quick, command-line to detect an empty doc with a macro.
>>>
>>> Is there anything available that I can use??
>>>
>>> I have managed to write a PERL script to detect empty xls xlsx, doc and
>>> docx files but I cannot detect whether they have any macros embedded
>>>
>>> Gary
>>
>> If you've got a script to detect empty docs then it should be relatively
>> easy to detect these. I assume empty attachments are not normal in your
>> mail flows?
>>
> 
> I have come to the conculsiion that I am just going to have to stick with 
> detecting empty documents and forget the macro checks.
> 
>> I would look to write some custom SpamAssassin rules, maybe
>> incorporating your script, to detect these and filter them out.
> 
> I would love to be able to write custom Spamassassin rules but do not know 
> how 
> to do this. All I have done in the past is add small pattern matching rules 
> to local.cf
> 

That's a great place to start. Combining multiple simple rules in a meta
rule is also a great way to detect many spams. If you can find 3 or 4
factors specific to these spam (the more unique the better), combining
them usually gives excellent results. For example, they all contain a
doc,docx,xls,xlsx attachment, they all contain a specific phrase or
something unique in the Subject, maybe they all contain a URL or email
address in the body etc. Individually the rules might not be
particularly good indicators of spam, but when combined together they
may become highly effective.

This might not be the best forum to discuss in detail; the SpamAssassin
mailing list is a great place to get help with writing rules.

> Another rule I would like to add to Spamassassin is to catch emails where the 
> subject starts with the email local part in brackets as we get a LOT of those 
> too.
> 
>>
>> Are you able to post some examples to pastebin?
> 
> http://www.stainburn.com/virus_files/I040777.doc
> http://www.stainburn.com/virus_files/FAX_20151028_1445421437_89.doc

Sorry, I meant examples of the emails (including the full headers,
redacted where necessary), not the attachments. We might be able to
point you in the right direction or offer a few thoughts on how to
detect them in SpamAssassin.

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

Re: [CentOS] Detecting empty office doc containing virus macro

[Ned Slider]

On 28/10/15 11:55, Gary Stainburn wrote:
> We are receiving LOTS of emails that contain empty XLS or DOC documents with 
> embedded virus macros.  These are getting past SPAMASSASSIN, Clamav and 
> Kaspersky.
> 
> I'm trying to write a filter for EXIM to block these emails but I need to 
> know 
> a good, quick, command-line to detect an empty doc with a macro.
> 
> Is there anything available that I can use??
> 
> I have managed to write a PERL script to detect empty xls xlsx, doc and docx 
> files but I cannot detect whether they have any macros embedded
> 
> Gary

If you've got a script to detect empty docs then it should be relatively
easy to detect these. I assume empty attachments are not normal in your
mail flows?

I would look to write some custom SpamAssassin rules, maybe
incorporating your script, to detect these and filter them out.

Are you able to post some examples to pastebin?

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

Re: [CentOS] Updating intel graphics driver on CentOS7

[Ned Slider]

On 23/09/15 07:00, C. L. Martinez wrote:
> Hi all,
> 
>  Is it possible to upgrade intel X11 org driver on CentOS7?? Maybe
> with elrepo's packages:
> http://elrepo.org/linux/extras/el7/x86_64/RPMS/xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm??
> 

Yes.

>  It seems it doesn't exists driver in the upstream: 
> https://01.org/linuxgraphics
> 

The upstream is actually at http://xorg.freedesktop.org

If you read the notes, and look at the stack that driver bundle is based
upon, you will see it uses the same (latest) X11 driver as the elrepo
package above:

https://01.org/linuxgraphics/downloads/2015q2-intel-graphics-stack-release

Hope that helps.

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

Re: [CentOS] Updating intel graphics driver on CentOS7

[Ned Slider]

On 23/09/15 08:39, Fabian Arrotin wrote:
> On 23/09/15 08:00, C. L. Martinez wrote:
>> Hi all,
> 
>> Is it possible to upgrade intel X11 org driver on CentOS7?? Maybe 
>> with elrepo's packages: 
>> http://elrepo.org/linux/extras/el7/x86_64/RPMS/xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm??
> 
>>  It seems it doesn't exists driver in the upstream:
>> https://01.org/linuxgraphics
> 
>> Thanks,
> 
> Well, that package is older as the one in the current CentOs 7 distro :
> xorg-x11-drv-intel-2.99.916-1.el7.elrepo.x86_64.rpm
> vs
> xorg-x11-drv-intel-2.99.916-5.el7.x86_64
> 

Yes, looks like the distro caught up with the release of 7.1 :-)

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

Re: [CentOS] rpmbuild dwz error

[Ned Slider]

On 21/08/15 22:46, Andrew Neuschwander wrote:
 On 08/21/2015 02:04 PM, Leon Fauster wrote:
 Am 21.08.2015 um 21:08 schrieb Александр Кириллов nevis...@infoline.su:
 On CentOS 7, I'm building a large C++ package with rpmbuild. Arachne
 (https://www.broadinstitute.org/crd/wiki/index.php/Arachne_Main_Page).
 During the debuginfo extraction stage, I get the following error:
 + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz
 --dwz-low-mem-die-limit 1000 --dwz-max-die-limit 11000
 /home/andrew/rpmbuild/BUILD/arachne-46233
 dwz: Multifile temporary files too large
 cpio: /builddir/build/BUILD/glibc-2.17-c758a686/math: Cannot stat: No
 such file or directory
 cpio: arachne-46233/src/Calculator.cc: Cannot stat: No such file or
 directory
 cpio: arachne-46233/src/Calculator.y: Cannot stat: No such file or
 directory
 36150 blocks
 rpmbuild/dwz appear to be using /var/tmp for large temporary debug
 info files. This package generates over 30GB of debug data and I think
 it is filling up /var/tmp leading to the error. How can I tell
 rpmbuild to use an alternative temporary file location?

 Try to change %_tmppath in /usr/lib/rpm/macros or build in mock and
 place the whole chroot on a larger drive (/etc/mock/site-defaults.cfg).
 
 I set %_tmppath (in ~/.rpmmacros) and $TMPPATH (xz called by
 find-debuginfo.sh uses it) and more parts of the build process used my
 custom tmppath. But dwz still uses large temporary files in /tmp.
 


 and if you do not need the debug packages, add

 %_enable_debug_packages  0

 into your .rpmmacros file

 -- 
 LF

 
 I tried disabling the debug packages but then rpmbuild just leaves the
 debuginfo in the binaries and I ended up with a 30GB binary rpm.
 
 -A

That sounds like the package hasn't been stripped. You can manually
strip the debug information (see man strip), but rpmbuild should do this
as part of the build process.

Rather than disabling debuginfo packages system wide as suggested above,
try disabling in package SPEC file:

%define  debug_package  %{nil}

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

Re: [CentOS] TLS for all CentOS websites but not for smtp?

[Ned Slider]

On 19/08/15 17:50, Alice Wonder wrote:
 
 
 On 08/19/2015 09:24 AM, Kai Bojens wrote:
 On 19-08-15 08:30:27, Alice Wonder wrote:

 e-mail by its very design is not secure, SMTP creates Man In The
 Middle at every server along the way.

 DANE exists and mail servers like postfix support this. My logfiles
 show me that mail.centos.org delivers straight to me without any
 servers along the way.
 
 DANE just pins the certificate.
 

 I'm not saying they shouldn't implement TLS on the list server, just
 not sure what the privacy or security benefit really would be.

 Encryption ensures that third parties simply cannot follow their collect
 all strategy.
 
 That's a fair point.

But it's a public mailing list??

I can understand why you may want to send some mail encrypted point to
point, but not when you then publish said mail on a publicly accessible
archived list. It's just adding unnecessary overhead.

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

Re: [CentOS] RHEL 6.7 is released

[Ned Slider]

On 24/07/15 07:40, Akemi Yagi wrote:
 On Thu, Jul 23, 2015 at 8:02 PM, Devin Reade g...@gno.org wrote:
 
 In upgrading from RHEL 6.6 to 6.7, I did find that I had to disable
 my 3rd party repos (elrepo and epel) in order to avoid yum erroring
 out.
 
 Can you elaborate on this? What yum error(s) did you see? I updated a
 RHEL 6.6 system with ELRepo enabled (but no EPEL packages) to RHEL 6.7
 using 'yum update' without any issue.
 
 Akemi

Same here - I updated RHEL 6.6 systems yesterday with elrepo enabled
with no issues whatsoever. I don't have EPEL installed so perhaps that
was the issue rather than elrepo?

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

Re: [CentOS] install nvidia driver on centos 7.1

[Ned Slider]

On 20/07/15 21:47, Wes James wrote:
 
 On Jul 20, 2015, at 2:41 PM, Akemi Yagi amy...@gmail.com wrote:
 
 snip
 

 You may want to start from this page:

 http://elrepo.org/tiki/nvidia-detect http://elrepo.org/tiki/nvidia-detect

 Akemi
 
 OK.  Thanks :)
 
 -wes
 

Yes, once you have the elrepo repository configured, the general
procedure is:

yum install nvidia-detect

then:

yum install $(nvidia-detect)

then reboot and you should be good to go :-)

The second command will automatically install the correct nvidia driver
packages for your device.


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

Re: [CentOS] ntpd new version

[Ned Slider]

On 06/07/15 12:04, Vijendra Agarwal (vijagarw) wrote:
 Hi All,
 Currently CentOS site contains the below version of ntpd.
 ntp-4.2.6p5-3.el6.centos.x86_64.rpmhttp://mirror.centos.org/centos/6.6/updates/x86_64/Packages/ntp-4.2.6p5-3.el6.centos.x86_64.rpm
  :- 16 mar 2015.
 
 Does anybody have any information about when the new version of ntpd is 
 expected to release containing new vulnerabilities fixes?
 
 Thanks
 Vijendra.


That is the current version for el6.

What new vulnerabilities?

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

Re: [CentOS] C7: EPEL conflicts with Base and ElRepo?

[Ned Slider]

On 18/06/15 22:04, Marko Vojinovic wrote:
 
 Hi everyone,
 
 This just came to my attention --- I have CentOS 7 installed on one
 machine, and have configured elrepo and epel as additional
 repositories. When I turned on the yum-priorities package (and set up
 priorities in the order baseupdates  elrepo  epel), it turns out
 that there are 65 conflicting packages between base and epel, and
 additional 5 between elrepo and epel (there are no conflicts between
 base and elrepo, as expected).
 

The overlap between elrepo and EPEL is due to the 5 VirtualGL packages
in elrepo.

VirtualGL packages, albeit 64-bit only, are also available in EPEL. They
don't appear to be shipping the 32-bit VirtualGL libs.

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

Re: [CentOS] video problem since 2015-04-01 update

[Ned Slider]

On 03/04/15 20:41, Francis Gerund wrote:
 Well, it could be the same, but the bug report does seem to refer to the
 bug being in kernel series 3.18.  I am just using whatever 3.10 series
 kernel comes standard with Centos 7.x.
 

Well, the CentOS kernel is a 3.10 kernel in name (or number) only. Red
Hat backport much stuff from later kernels, and in this case that
includes much broken code for the Intel i915 driver. The code is broken
from around 3.15 and still not completely fixed in the current 4.0-rc6
code base. Updating to a newer kernel, and hence a newer i915 driver,
may or may not help, but it doesn't hurt to try.

 I don't know anything about bug reports, and I an not familiar with
 swapping out kernels in Centos.
 
 BTW, is El Repo another name for the EPEL repository?
 

No, they are two completely separate repositories:

http://wiki.centos.org/AdditionalResources/Repositories

 
 
 On Fri, Apr 3, 2015 at 1:07 PM, Akemi Yagi amy...@gmail.com wrote:
 
 On Fri, Apr 3, 2015 at 10:30 AM, Francis Gerund ranr...@gmail.com wrote:
 Hello!

 No updates for days until 2015-04-01.  Then presented with huge steaming
 pile of updates all at once, apparently related to Centos 7.1 release.

 After reboot, there is a problem with the video.  It seems to flicker
 when
 the mouse pointer touches the screen edges.  Also, sometimes when viewing
 pages in Firefox, the window becomes partially covered with horizontal
 black lines.

 During reboots, before the login screen appears, there are quickly
 disappearing messages seeming to include references to drm:9 and some
 sort of underrun.

 In the terminal window, I get a message:

 ABRT has detected 3 problem(s). For more info run: abrt-cli list --since
 1428078184

 When I do that, I get:

 id (blah, blah)
 reason: WARNING: at drivers/gpu/drm/i915/intel_display.c:869
 intel_wait_for_vblank+0x211/0x220 [i915]()
 time: Fri 03 Apr 2015 11:41:49 AM CDT
 cmdline:BOOT_IMAGE=/vmlinuz-3.10.0-229.1.2.el7.x86_64
 root=UUID=(blah, blah) ro vconsole.keymap=us
 vconsole.font=latarcyrheb-sun16 rhgb quiet LANG=en_US.UTF-8
 count:  1
 Directory:  /var/tmp/abrt/oops-2015-04-03-11:41:49-590-0

 Does this kernel.org bug look similar to yours?

 https://bugzilla.kernel.org/show_bug.cgi?id=86771

 I suggest you try kernel-ml from ELRepo and see if that fixes the issue.

 Akemi

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

[Ned Slider]

On 02/04/15 20:47, Jim Perrin wrote:
 
 
 On 04/02/2015 02:29 PM, Phelps, Matthew wrote:
 On Thu, Apr 2, 2015 at 3:25 PM, Jim Perrin jper...@centos.org wrote:



 On 04/02/2015 01:28 PM, Phelps, Matthew wrote:


 Soliciting our feedback *before* changing everything regarding release
 names would
 have been nice.


 We did.

 http://lists.centos.org/pipermail/centos-devel/2015-February/012873.html



 WE'RE NOT ON THE DEVEL LIST!
 
 WHY NOT?
 

Would it have made a difference? Yes, you asked on that list. And yes,
nearly everyone who responded said no to the change, yet you did it anyway.

If Matthew had been on the list, and had also responded against the
change, would his voice have made the difference?

Seriously, show me a post in that thread from someone not on the CentOS
board speaking strongly in favour of the change. It's a big thread.

The point is, you asked and the community said no (at least those who
were subscribed to the -devel list and took the time to respond). Yet
you did it anyway.

The damage is done now, you can't take it back.



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

Re: [CentOS] 7-Zip for CentOS X86-64

[Ned Slider]

On 11/03/15 23:24, Mark LaPierre wrote:
 Hey Y'all,
 
 I'm looking at ZCad:
 http://sourceforge.net/projects/zcad/?source=directory
 
 It looks like the kind of 3D CAD package that I've been looking for.  It
 says that it works on Linux but it's zipped with 7-Zip which doesn't
 seem to be available for CentOS.
 
 Does anyone know if ZCAD or 7-Zip is packaged for CentOS X86-64
 somewhere out there?
 

On EL5 I have p7zip installed from rpmforge which handles 7-Zip files.

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

Re: [CentOS] How to install tp_smapi and acpi_call kernel modules

[Ned Slider]

On 07/03/15 15:29, Tim wrote:
 Thanks for your answer.
 
 tlp and tlp-rdw are already installed from epel.
 But these packages miss that kernel modules.
 So when I want these I have to add the repo and replace $release in the 
 mirror url with 21 of fedora, right?
 

No, the kernel modules must be compiled for the CentOS kernel.
Installing from a Fedora repository will not work.

I would suggest you talk to the folks at EPEL on their mailing list.

 Am 7. März 2015 15:39:14 MEZ, schrieb Bob Marcan bob.mar...@gmail.com:
 On Sat, 07 Mar 2015 12:52:27 +0100
 Tim li...@kiuni.de wrote:

 Hello,

 I've got a Thinkpad T420 and would like to use full tlp
 functionality.
 Therefore I need the kernel module tp_smapi and acpi_call.

 Have a look right here:

 http://linrunner.de/en/tlp/docs/tlp-linux-advanced-power-management.html#installation
 There are only fedora related packages but none for RHEL/CentOS.

 Should I install that repo and hardcode the mirror to the fc21 repo?

 Regards
 Tim
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos
 ...
 Fedora 20 and 21

 TLP packages are available from the official Fedora repositories:

tlp (Updates) – Power saving
tlp-rdw (Updates) – optional, Radio Device Wizard

 Install the above packages with the command (in a root shell):
 yum install tlp tlp-rdw

 Note: packages for RHEL/CentOS are available from EPEL6/7 repositories.
 
 BR, Bob

 ___
 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
 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Running the Wine emulator on CentOS 7

[Ned Slider]

On 07/03/15 16:40, Niki Kovacs wrote:
 Hi,
 
 Up until recently, I've been running Wine 1.6.2 on my workstation under
 Slackware64 14.1. I used it to emulate a handful of legacy apps that ran
 under Windows XP. They worked perfectly with that setup.
 
 After migrating the workstation from Slackware to CentOS 7, I installed
 the Wine packages, but none of my applications run. I only get an error
 message about wrong EXE format. And that's it.
 
 Any idea what's going on?
 
 Cheers,
 
 Niki


Only a guess as I don't run wine and don't have any Windows
applications, but...

CentOS 7 is 64-bit. Therefore I'm guessing you've installed a 64-bit
version of wine on CentOS? Further guessing your Windows apps are
32-bit? Can you see where I'm going here?

I'm guessing you are either going to need to build/install a 32-bit
version of wine or will need to find 64-bit versions of your Windows
applications.

Like I said, just a guess :-)

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

Re: [CentOS] Running the Wine emulator on CentOS 7

[Ned Slider]

On 07/03/15 22:01, Niki Kovacs wrote:
 Le 07/03/2015 18:24, Ned Slider a écrit :
 I'm guessing you are either going to need to build/install a 32-bit
 version of wine or will need to find 64-bit versions of your Windows
 applications.
 
 Is it possible to build a 32-bit version of Wine on 64-bit CentOS 7 ? A
 curt yes or no will do. Eventually I'll RTFM for the details.
 

Only if 32-bit versions of all the BRs are available. You can't build in
mock as there is no 32-bit tree to build against.

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

Re: [CentOS] Strange crash after NVidia driver installation from ELRepo

[Ned Slider]

On 03/03/15 18:47, Niki Kovacs wrote:
 
 
 Le 03/03/2015 19:25, Jonathan Billings a écrit :
 One of the things that the nvidia driver adds is nouveau.modeset=0
 rdblacklist=nouveau to the kernel arguments.  Do you see them?  I
 know that we saw the kernel panic when the nouveau driver was loaded
 on a el6.6 system with an NVidia K620, so perhaps when you brought in
 X11 you also installed the nouveau drivers?
 
 One thing I did this time was to make sure there weren't any
 incompatible drivers (like 'nouveau') installed *before* actually
 installing and configuring kmod-nvidia. Now everything works as expected.
 

The elrepo nvidia drivers will disable the nouveau driver automatically
so you don't need to worry about things like that.

Don't over-think it. I would recommend you just set up your system the
way you want it with at least a minimal working Xorg installation, and
fully updated. Then just:

yum install nvidia-detect
yum install $(nvidia-detect)

and reboot, and you should be good to go.


 I can't be sure 100 %, but I think this was the culprit.
 
 Cheers,
 
 Niki
 
 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Package group X Window System has disappeared

[Ned Slider]

On 27/02/15 13:27, Greg Bailey wrote:
 On 02/27/2015 02:54 AM, Niki Kovacs wrote:
 Hi,

 Until last week, I could install a CentOS 7 based desktop using the
 following approach:

 1. Install minimal system.

 2. yum groupinstall X Window System

 3. yum install gdm gnome-classic-session gnome-terminal liberation-fonts

 4. Install applications as needed.

 This morning, the package group X Window System seems to have
 disappeared. This is embarrassing.

 What happened?

 Niki
 
 Works for me, although I have to do yum group list hidden to see the
 X Window System group (both as available for installation, and as
 installed once I've done the group install invocation).  yum group list
 hidden and yum group list hidden ids are 2 variations I only learned
 about recently...
 

Nice tip! I've added it to the Yum tips and tricks section on the wiki
as there wasn't anything there on working with yum groups:

http://wiki.centos.org/TipsAndTricks/YumAndRPM#head-b3159dc0594ab59a5ae0c27d86c3815085064419

Note 'yum group list' only works on el7 whereas 'yum grouplist' works
across el5/6/7 so I've gone with that syntax on the wiki.

 Nice recipe, BTW, for a simple GUI install.  The spacing of the font
 doesn't look very good in Gnome terminal though; I must be missing
 whatever the default font is configured to be.
 
 -Greg
 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] repositories

[Ned Slider]

On 27/02/15 12:30, Pol Hallen wrote:
 Hi all :-)
 This is my first post: I'm coming from debian/bsd world.
 
 A question about repositories:
 
 minimal installation (version 7) provides:
 
 CentOS-Base.repo
 CentOS-CR.repo
 CentOS-Debuginfo.repo
 CentOS-fasttrack.repo
 CentOS-Sources.repo
 CentOS-Vault.repo
 
 I known there are others repositories as:
 
 RPMForge, EPEL, REMI, ATrpms, Webtatic (and maybe also others)
 
 so, what kind of these repositories are?
 
 Does they repositories substitute packages from main? Or only adding new
 packages?
 
 thanks for advices and help!
 
 Pol


Hi Pol,

Welcome to CentOS and the mailing lsit.

Start here for more information on 3rd party repositories:

http://wiki.centos.org/AdditionalResources/Repositories

Some may replace distro packages whereas others may have a policy not to
replace distro packages (so only contain packages not in the distro).
Some repositories split into channels where the main repo doesn't
contain distro packages but may have an extras channel that contains
any packages that replace distro packages.

Ultimately CentOS has little influence over what 3rd party repos do so
the ecision / policies are down to each individual repo.

The yum priorities plugin can be used to prevent 3rd party repositories
from replacing distro packages:

http://wiki.centos.org/PackageManagement/Yum/Priorities

Hope that at least gets you started.

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

Re: [CentOS] Package group X Window System has disappeared

[Ned Slider]

On 27/02/15 09:54, Niki Kovacs wrote:
 Hi,
 
 Until last week, I could install a CentOS 7 based desktop using the
 following approach:
 
 1. Install minimal system.
 
 2. yum groupinstall X Window System
 
 3. yum install gdm gnome-classic-session gnome-terminal liberation-fonts
 
 4. Install applications as needed.
 
 This morning, the package group X Window System seems to have
 disappeared. This is embarrassing.
 
 What happened?
 
 Niki

Not sure as I don't have a CentOS 7 install to hand, only RHEL7 on which
the X Window System group does not exist.

It does exist on RHEL 5/6 - perhaps you are getting confused between
versions?

You can see the list of valid groups with:

yum grouplist

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

Re: [CentOS-docs] [CentOS] Securing SSH wiki article outdated

[Ned Slider]

On 12/02/15 20:03, Warren Young wrote:
 Hi, just a quick note to whoever is maintaining this page:
 
   http://wiki.centos.org/HowTos/Network/SecuringSSH
 
 The procedure is missing the firewall-cmd calls necessary in EL7:
 
   firewall-cmd --add-port 2345/tcp
   firewall-cmd --add-port 2345/tcp --permanent
 
 Also, it may be worth mentioning that semanage is in the 
 policycoreutils-python package, which isn’t installed by default in all stock 
 configurations.


Thank you, and copying to the centos-docs list for reference.

___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS] Securing SSH wiki article outdated

[Ned Slider]

On 12/02/15 20:03, Warren Young wrote:
 Hi, just a quick note to whoever is maintaining this page:
 
   http://wiki.centos.org/HowTos/Network/SecuringSSH
 
 The procedure is missing the firewall-cmd calls necessary in EL7:
 
   firewall-cmd --add-port 2345/tcp
   firewall-cmd --add-port 2345/tcp --permanent
 
 Also, it may be worth mentioning that semanage is in the 
 policycoreutils-python package, which isn’t installed by default in all stock 
 configurations.


Thank you, and copying to the centos-docs list for reference.

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

Re: [CentOS] Nvidia Mod Update

[Ned Slider]

On 08/02/15 05:09, S.Tindall wrote:
 On Sat, 2015-02-07 at 23:06 -0500, Mark LaPierre wrote:
 Hey all,

 On my X86-64 CentOS 6.6 machine I just ran yum update.  In the update
 was an upgrade from the 340.XX Nvidia package to the 346.XX package.
 Hrmmm?  I'm thinking this is not a good idea but, since this is just a
 test system any way, I let it run.  Sure enough I was right.  Dmesg says
 that my video is supported by the 340.XX driver, not the 346.XX driver.
  It's not happy cause it can't find a supported GPU.

 1. So, having only a command line interface, how do I tell yum to rip
 out the 346.XX package and reinstall the 340.XX package?

 2. How do I tell yum not to do such stupid stuff again?
 
 Assuming you mean that you just updated the kmod-nvidia package, then
 follow the instructions at the top of this page.
 
 http://elrepo.org/tiki/kmod-nvidia
 
 It happened to me, too. Easy fix. :-)
 
 Steve
 

Yes, just to reiterate:

yum erase kmod-nvidia
yum install kmod-nvidia-340xx
reboot

You will then be on the correct driver branch and will get the
appropriate driver updates going forwards, no changes to yum necessary.

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

Re: [CentOS] Nvidia Mod Update

[Ned Slider]

On 08/02/15 12:33, Pete Geenhuizen wrote:
 
 On 02/08/15 06:12, Ned Slider wrote:

 On 08/02/15 05:09, S.Tindall wrote:
 Yes, just to reiterate:

 yum erase kmod-nvidia
 yum install kmod-nvidia-340xx
 reboot

 You will then be on the correct driver branch and will get the
 appropriate driver updates going forwards, no changes to yum necessary.

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

 I went through all this, and now that I have kmod-nvidia-340xx
 installed, but have you executed yum update or yum list updates?
 If you do then yum  will want up upgrade you to the latest and greatest
 kmod-nvidia-346xx.
 So other than modifying yum to exclude the nvidia driver how do you
 prevent the update in the future?
 
 rpm -qa | grep nvidia
 nvidia-detect-346.35-1.el6.elrepo.x86_64
 kmod-nvidia-340.65-1.el6.elrepo.x86_64
 nvidia-x11-drv-340.65-1.el6.elrepo.x86_64
 
 Output from yum list updates
 Updated Packages
 kmod-nvidia.x86_64   
 346.35-1.el6.elrepo elrepo
 nvidia-x11-drv.x86_64
 346.35-1.el6.elrepo elrepo
 
 

No, you don't have the package kmod-nvidia-340xx installed. You have
kmod-nvidia VERSION 340.65. In the first example, the package NAME is
kmod-nvidia-340xx (the -340xx is part of the package name, NOT the version).

Please do as I advised:

yum erase kmod-nvidia
yum install kmod-nvidia-340xx
reboot

Because you now no longer have package kmod-nvidia installed, yum will
not try to update you to the latest version. You will stay forever on
the 340.xx branch which is the last version to support your hardware.

Hope that helps
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Nvidia Mod Update

[Ned Slider]

On 08/02/15 14:24, Pete Geenhuizen wrote:
 
 On 02/08/15 07:45, Ned Slider wrote:

 On 08/02/15 12:33, Pete Geenhuizen wrote:
 No, you don't have the package kmod-nvidia-340xx installed. You have
 kmod-nvidia VERSION 340.65. In the first example, the package NAME is
 kmod-nvidia-340xx (the -340xx is part of the package name, NOT the
 version).

 Please do as I advised:

 yum erase kmod-nvidia
 yum install kmod-nvidia-340xx
 reboot

 Because you now no longer have package kmod-nvidia installed, yum will
 not try to update you to the latest version. You will stay forever on
 the 340.xx branch which is the last version to support your hardware.

 Hope that helps

 Oops, yup right you are, kinda missed that small but important detail.
 
 Thx.
 Pete
 

No problem Pete.

Now you are on the correct branch you will continue to get updates to
that 340.xx driver as and when nvidia release them. IIRC, nvidia said
they would continue to support the 340.xx legacy branch until the end of
2019, so for the best part of another 5 years :-)

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

Re: [CentOS] Probing EDD (edd=off to disable)

[Ned Slider]

On 08/01/15 18:51, Fred Smith wrote:
 Hi all!
 
 Running Centos-6.latest on an AMD six-core Vishera processor. It's
 been running for a year on that hardware.
 
 today I swapped out the video card (from Nvidia 9800GT to Nvidia 460 GTX)
 hoping to get a little more horsepower, and the ability to run the
 Folding At Home GPUclient.
 
 I know that's an old card, it's a hand-me-down from my son who just
 replaced it with a new 970 GTX card.
 
 So, I got the hardware installed, close up the case, connect all the
 cables, boot it up and booting stops with this message on the screen
 in plain text mode:
 
   Probing EDD (edd=off to disable)
 
 I can reboot and edit the kernel commandline to add edd=off at the
 end then it comes up all the way.
 
 I haven't made any changes in the Nvidia drivers, because nvidia's
 web site tells me it uses the same driver as the 9800GT card did.
 
 I'm using the RPMs from elrepo, so it uses akmod to do a rebuild when
 a new kernel is installed. But I didn't install a new kernel, so it
 didn't get rebuilt, and I'm wondering if that's the cause of the
 problem... different card works with the same driver version but may
 need recompiling due to the different hardware ?
 
 If so, I don't think I know how to force akmod to do the rebuild.
 Thoughts/or actual knowledge on this would be appreciated.

No, the elrepo packages are kABI-tracking kmod packages that are
compatible with the RHEL kernels stable ABI. These drivers work across
all RHEL kernel releases, no rebuilding takes place. This is unique to
Enterprise Linux (RHEL and it's clones) and different to how things may
happen on other distros or when using the NVIDIA installer.

Your card is supported by the latest elrepo driver release, so just make
sure you are yum updated to the latest release (currently
kmod-nvidia-340-65):

yum --enablerepo=elrepo update kmod-nvidia

Reboot if the driver gets updated and you should be good to go.

 
 Also, among the googling I did, I found one posting that said that message
 means an unexpected (DOS??) interrupt occurred, but it did't  help me
 any with how to resolve it.
 
 Your suggestions will be welcomed, thanks in advance!
 
 Fred
 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Sun Microsystems Quad gigabit ethernet nic compatibility

[Ned Slider]

On 02/01/15 06:01, John R Pierce wrote:
 On 1/1/2015 9:41 PM, mechy2k2000 wrote:
 Hello I am thinking of buying this card to and wanted  to know if this
 NIC
 is supported. The card is a Sun Microsystems PCI-X Quad-Port Gigabit
 Ethernet Adapter QGEXPCI 501-6738-10. Can't find any info on how well the
 card plays with centos and also proxmox ve (if any of you use that
 distro )
 
 I've not tried that card on anything other than Sun UltraSparc running
 Solaris 9 and 10, but rumor has it Linux has a 'cassini' driver that
 supports the Sun GigaSwift NIC on those.
 
 
 
 
 

The cassini.ko driver is present in el5 and el6, but Red Hat dropped
support from RHEL7. If you want to use it on el7 then elrepo.org has
packaged the driver for el7, backported from kernel-3.10.63:

kmod-cassini-1.6-1.el7.elrepo.x86_64.rpm

At present it's in the testing repo so do let us know if you try it and
it works for you.

Regards,

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

Re: [CentOS] can't enable selinux CentOS 6.5

[Ned Slider]

On 30/12/14 22:07, Valeri Galtsev wrote:


I have that vague feeling that what I'm about to say will probably be
declared wrong... Still. From the very beginning I do not consider SELinux
adding to the security of the system. How can it if it can be turned off
on the fly? On the other hand, it adds hundreds of thousands of lines to
kernel code which does exactly opposite: deteriorates security by
potentially introducing bugs. I discovered at some point that there are
other people out there who share this opinion ;-)

So, my question is: can someone design attack scenario which would be
successful if it were not for SELinux, and which is thwarted by SELinux.
Note that the fact that script kiddie just forgot to put as a first line

/usr/sbin/setenforce 0

doesn't make such example a solid case pro SELinux for me.

Thanks a lot for your insight! (Always hoping to learn ;-)



Disabling SELinux requires root privileges at which point most all 
security implimentations are pretty useless.


Firewalls add much code to the kernel and can also be turned off on the 
fly by any script kiddie with root privileges. Should we discount 
them too?


IMHO your arguments are weak with bad examples. The questions you should 
be asking is how effective would SELinux be in preventing an initial 
remote exploit, or preventing an attacker gaining further escalation of 
privileges once they have gained access to the system.


In answer to your question, you will find lots of good real life 
examples in Dans' blog here:


http://danwalsh.livejournal.com/



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

Re: [CentOS] Design changes are done in Fedora

[Ned Slider]

On 29/12/14 01:52, Always Learning wrote:


On Thu, 2014-12-18 at 10:30 -0600, Les Mikesell wrote:


..  The design changes are done in Fedora, by
people who apparently never liked unix or consistency, not the people
using Red Hat or CentOS that already have things working that they
would like to keep working the same way across upgrades.


What type of large commercial organisation lets undisciplined people
make adverse changes detrimental to the reputation and ultimate success
of its 'stable' commercial product. Since Enterprise Linux is supposed
NOT to be Windoze, consistency is very important especially for the
paying (R.H.) customers. It is also much appreciated by its devout fans
and the hardworking guardians of the Centos cloned version.

* The dramatic upheaval in C7;
* The claimed life-span of C5 truncated by no more normal upgrades;
* The changes introduced in C6.6, during the lifetime of an allegedly
stable C6 product;

all seem to suggest Upstream lacks a clear, reliable and dependable
strategic policy (or what some call a 'sense of direction').

Happy New Year to all to everyone.



The stability comes _within_ a product release. I don't think it's 
realistic to expect el7 to be the same as el6 or el5, otherwsie what's 
the point of the newer releases. You have 7 years of support / 
consistency (now 10 years). What business model do you have that you 
can't build around a product guaranteed to be consistent/supported for 
the next 10 years?



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

Re: [CentOS] yum upgrade not working

[Ned Slider]

On 21/12/14 02:25, Tim Dunphy wrote:
 Hey all,
 
 I'm attempting to upgrade a Centos 5.9 machine to CentOS 5.10.
 
 But when I try the yum update command I get this response:
 
 -- Finished Dependency Resolution
 python26-PyYAML-3.08-5.el5.x86_64 from installed has depsolving problems
   -- Missing Dependency: libyaml-0.so.1()(64bit) is needed by package
 python26-PyYAML-3.08-5.el5.x86_64 (installed)
 -- Running transaction check
 --- Package kernel.x86_64 0:2.6.18-164.15.1.el5.centos.plus set to be
 erased
 --- Package kernel.x86_64 0:2.6.18-194.11.4.el5 set to be erased
 --- Package kernel.x86_64 0:2.6.18-238.9.1.el5 set to be erased
 --- Package kernel-devel.x86_64 0:2.6.18-308.4.1.el5 set to be erased
 -- Processing Dependency: libyaml-0.so.1()(64bit) for package:
 python26-PyYAML
 -- Finished Dependency Resolution
 python26-PyYAML-3.08-5.el5.x86_64 from installed has depsolving problems
   -- Missing Dependency: libyaml-0.so.1()(64bit) is needed by package
 python26-PyYAML-3.08-5.el5.x86_64 (installed)
 Error: Missing Dependency: libyaml-0.so.1()(64bit) is needed by package
 python26-PyYAML-3.08-5.el5.x86_64 (installed)
  You could try using --skip-broken to work around the problem
  You could try running: package-cleanup --problems
 package-cleanup --dupes
 rpm -Va --nofiles --nodigest
 
 
 The system claims that it can't find libyaml-0.so.1, however I can easily
 locate it:
 
 [root@ops:~] #locate libyaml-0.so.1
 /usr/lib64/libyaml-0.so.1
 /usr/lib64/libyaml-0.so.1.1.0
 

What does rpm say? 'rpm -q --whatprovides /usr/lib64/libyaml-0.so.1'

 Can someone please point me in the right direction for solving these
 problems?
 

These are not CentOS packages (python26-PyYAML and libyaml). I would
suggest you ask on the appropriate list for whichever repository these
packages were installed from (rpm -qi should tell you).

 Thanks
 Tim
 
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] NVIDIA dropping support for older hardware (G8xxx, G9xxx and GT2xx chipsets)

[Ned Slider]

Hi all,

I just wanted to give a heads up to any NVIDIA users that NVIDIA are
dropping support for older hardware based on G8xxx, G9xxx and GT2xx
chipsets in their latest display drivers. The last version to support
these older chipsets will be the current Long Lived 340.xx branch.

If anyone is using NVIDIA driver packages from elrepo, legacy 340.xx
driver packages are now available for those affected. There is a thread
on the elrepo mailing list here:

http://lists.elrepo.org/pipermail/elrepo/2014-September/002362.html
http://lists.elrepo.org/pipermail/elrepo/2014-December/002447.html

There is also an updated version of nvidia-detect (v343.36) available
which will tell users if they are affected and need to switch to the new
340.xx legacy driver packages or whether their hardware will continue to
be supported by future NVIDIA driver releases.

Obviously we would like to avoid a situation where folks 'yum update'
their drivers to a release that doesn't support their hardware and
breaks their system. Thus we would like to help users who will be
affected transition to the correct legacy driver now and so avoid future
issues.

If anyone needs any advice / help, please just ask.

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

Re: [CentOS] CentOS 7 grub.cfg missing on new install

[Ned Slider]

On 10/12/14 18:13, Jeff Boyce wrote:
 Greetings -
 
 The short story is that got my new install completed with the
 partitioning I wanted and using software raid, but after a reboot I
 ended up with a grub prompt, and do not appear to have a grub.cfg file. 
 So here is a little history of how I got here, because I know in order
 for anyone to help me they would subsequently ask for this information. 
 So this post is a little long, but consider it complete.
 
 Brand new Dell system with two 3GB drives in this system with RAID1 LVM
 taking all the space outside the boot partitions.  I initially created
 the sda[1,2] and sdb[1,2] partitions via GParted leaving the remaining
 space unpartitioned.  A gpt partition table was put on both drives. 
 During installation Anaconda recognized everything properly which
 resulted in the following partition summary:
 
 sda1 /boot/efi 500 MB EFI System Partition
 sda2 /boot 500 MB xfs
 vg_jab-hostroot / 8 GB LVM xfs RAID1
 vg_jab-hostvar /var 4 GB LVM xfs RAID1
 vg_jab-hostswap /swap 2 GB LVM swap RAID1
 
 The installer also recognized and listed these unknown partitions that
 were untouched during installation.
 sdb1 vfat 500 MB standard partition
 sdb2 vfat 500 MB standard partition
 
 Installation proceeded successfully, and after the initial reboot of the
 system I used mdadm commands to watch the raid complete building before
 doing anything else (I know, not necessary but I am doing other things
 and had the time to let it complete).  I rebooted the system and got a
 terminal prompt as expected (no GUI installed).  At this point I needed
 to copy my /boot/efi and /boot partitions from sda[1,2] to sdb[1,2] so
 that the system would boot from either drive, so I issued the following
 sgdisk commands:
 
 root#  sgdisk -R /dev/sdb1 /dev/sda1
 root#  sgdisk -R /dev/sdb2 /dev/sda2
 root#  sgdisk -G /dev/sdb1
 root#  sgdisk -G /dev/sdb2
 
 Results of the first command above:
   Found invalid GPT and valid MBR; converting MBR to GPT format.
   Warning the kernel is still using the old partition table.  The new
 table will be used at the next reboot.  The operation has completed
 successfully.
   The same note (from the Warning on) was repeated for the other three
 commands.
 
 I then installed GRUB2 on /dev/sdb1 using the following command:
 root#  grub2-install /dev/sdb1
Results:  Installing for x86_64-efi platform.  Installation finished.
 No error reported.
 

The upstream docs (see below) seem to suggest 'grub2-install /dev/sdb'
rather than /dev/sdb1 (i.e, installing to the device rather than a
partition on the device). I don't know if this is the cause of your issue.

 I rebooted the system now, only to be confronted with a GRUB prompt.
 Thinking that this is a good opportunity to for me to learn to rescue a
 system since I am going to need to understand how to recover from a disk
 or raid failure, I started researching and reading.  It takes a little
 bit of work to understand what information is valuable when a lot of it
 refers to GRUB (not GRUB2) and doesn't make reference to UEFI booting
 and partitions. I found this Ubuntu wiki as a pretty good source
 https://help.ubuntu.com/community/Grub2/Troubleshooting#Search_.26_Set
 

I found the upstream documentation for grub2 to be useful:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Working_with_the_GRUB_2_Boot_Loader.html

Included is a procedure for completely reinstalling grub2 which might
help you recover.

 Below is the current information of my system as seen by grub;
 
 grub#  set(the important grub2 variables are:)
prefix = (hd1, gpt2)/grub2
root = hd1, gpt2
 
 grub#  ls -lha
Device proc:  filesystem type procfs
Device hd0:  no known filesystem detected
Device hd1:  no known filesystem detected
Partition hd1, gpt3:  no known filesystem detected
Partition hd1, gpt2:  filesystem xfs
Partition hd1, gpt1:  filesystem fat
Device hd2:  no known filesystem detected
Partition hd2, gpt3:  no known filesystem detected
Partition hd2, gpt2:  no known filesystem detected
Partition hd2, gpt1:  no known filesystem detected
 
 grub#  ls (hd1, gpt2) -l /
/efi
/grub
/grub2
vmlinuz -3.10.0-123.el7.x86_64
initramfs-3.10.0-123.el7.x86_64.img
... plus some other files
 
 Looking through the directories, I see that there is no grub.cfg file.
 Other than grub not recognizing the filesystem on hd2, the directories
 on hd2, gpt[1,2] seem to be identical to hd1, gpt[1,2] as I would assume
 based on the sgdisk commands I gave to copy them.  My initial thinking
 is that I need to re-run grub2-install on hd1 (sda), but I need a
 running system to do that.  So 

Re: [CentOS] ELRepo still active?

[Ned Slider]

On 04/12/14 13:10, Niki Kovacs wrote:
 Hi,
 
 I'm currently installing CentOS 5.11 i386 on an old PC.
 
 Is the ELRepo third-party repository still active and maintained?
 
 Cheers,
 
 Niki Kovacs

Sure is. Although you would probably be better off asking on the elrepo
mailing list rather than the CentOS list.

Anything you are particularly interest in?


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

Re: [CentOS] CentOS 7 - not using latest installed kernel

[Ned Slider]

On 03/12/14 17:10, John Horne wrote:
 Hello,
 
 I have just installed CentOS 7 onto two servers and applied all the
 current patches. There are currently two kernels installed:
 
 # rpm -q kernel
 kernel-3.10.0-123.el7.x86_64
 kernel-3.10.0-123.9.3.el7.x86_64
 
 
 However, if I reboot the servers they both start up on the older kernel:
 
 # uname -r
 3.10.0-123.el7.x86_64
 
 I would have expected them to restart using kernel 3.10.0-123.9.3.
 I know I can manually select the kernel to use at boot time (from the
 grub2 menu), but, as with CentOS 6, I would have expected the servers to
 reboot using the latest kernel automatically.
 
 Has anyone else noticed this? Any ideas as to why it might be happening?
 
 
 
 
 Thanks,
 
 John.
 

Someone already pointed you to the upstream bug for this.

Uninstalling the original release kernel (3.10.0-123.el7.x86_64) should
provide a workaround as the rest of the kernels should then be sorted in
the correct order.



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

Re: [CentOS] CentOs 7.0 and reboot failure

[Ned Slider]

On 02/12/14 18:34, Gregory P. Ennis wrote:
 On Mon, 2014-12-01 at 18:50 +, Ned Slider wrote:
 On 01/12/14 18:36, Gregory P. Ennis wrote:
 On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote:
 On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote:
 Date: Sun, 23 Nov 2014 13:50:17 -0600

 On Sun, 23 Nov 2014 13:07:47 -0600
 Gregory P. Ennis wrote:

 I also changed the boot level to 5.

 Do you mean the runlevel?  If so, are you sure that you changed it 
 correctly?

 Centos 7 doesn't use runlevels set in inittab like previous versions did. 
  I see that fact is actually noted in /etc/inittab, along with the 
 expected way to do it.
 -

 Frank,

 Yes, you are correct, I changed the run level and not boot level to 5
 and did so by using the command :

 ln -sf /lib/systemd/system/graphical.target 
 /etc/systemd/system/default.target

 Also, I appreciate everybody's input on this, but I am still at a loss
 as to how to fix this.  Without being able to reboot, it sure makes the
 set up difficult.

 Does anyone else have any ideas??

 Greg


 I have tried some additional changes that have not made a difference.

 I disabled selinux - that made no difference
 I stopped and disabled firewalld  - that made no difference.

 I can boot this machine after I turn it off and then back on, but when I
 try to do a shutdown now -r, the system hangs right after picking the OS
 that is desired CentOS Linux...

 After the machine is turned off the boot process occurs normally after
 this choice and I get two penguins in the upper left hand corner, and
 the boot proceeds.  When I do a shutdown now -r, I do not get to the
 penguins and the machine hangs forever until I either unplug it or press
 the power button for 5 seconds.

 Any help would be appreciated!!!

 Greg 

 ---

 Everyone, 

 I did not get much of a response on the list so I filed a bug report.  I
 wanted to document the bug report for anyone else that is having a
 reboot problem. 

 https://bugs.centos.org/view.php?id=7949


 Greg Ennis


 Seems little point in filing a bug report when you have no idea what the
 issue is. Bugs are not a means of troubleshooting nor a support forum.
 However, you did get my attention so lets see if we can stimulate some
 further interest in troubleshooting this.

 So the system will perform a cold reboot, but not a warm reboot. Sounds
 like a hardware issue to me.

 Any clues in /var/log/messages ?

 Tried updating the BIOS?

 Any hardware firmwares being loaded?


 ___
 
 Ned,
 
 Thanks for your response!!!
 
 Sorry, if posting a bug report was the wrong venue !!!
 
 There are no messages in the message logs that I could identify as
 problems, but the system fails before the OS is active.
 
 I have not updated the BIOS, and do not know how to do this... but this
 is my testing machine so I am more than open to doing this.  I am using
 a Gateway SX2855-UB12P.  I will take a look at the Gateway site; if
 there are tutorials you could point me to I would appreciate it.

You'd have to check the Gateway website to see if a bios update is
available to download for your model. Instructions are normally included
/ available.

 
 The only hardware that has been added has been a usb ethernet connection
 so that I have the motherboard nic card and the usb nic connection.


Just to eliminate the easy option first, does unplugging the USB
ethernet adapter (before rebooting) solve the problem?


 wanted to use this setup to test the firewalld capabilities for a
 network gateway.  The machine does not have a monitor, and is without a
 mouse or keyboard.  
 
 It should be noted that this machine previously had CentOS 6 with a 3T
 Seagate drive that worked without a problem, but recently developed a
 disc failure.  I replaced the drive with a 4T WesternDigital drive and
 installed CentOs 7.0 from a DVD.  
  

I wouldn't think the drive swap would make a difference.

 Thanks again for your help!!!
 
 Greg
 

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

Re: [CentOS] CentOs 7.0 and reboot failure

[Ned Slider]

On 01/12/14 18:36, Gregory P. Ennis wrote:
 On Thu, 2014-11-27 at 22:04 -0600, Gregory P. Ennis wrote:
 On Thu, 2014-11-27 at 18:50 -0600, Gregory P. Ennis wrote:
 Date: Sun, 23 Nov 2014 13:50:17 -0600

 On Sun, 23 Nov 2014 13:07:47 -0600
 Gregory P. Ennis wrote:

 I also changed the boot level to 5.

 Do you mean the runlevel?  If so, are you sure that you changed it 
 correctly?

 Centos 7 doesn't use runlevels set in inittab like previous versions did.  
 I see that fact is actually noted in /etc/inittab, along with the expected 
 way to do it.
 -

 Frank,

 Yes, you are correct, I changed the run level and not boot level to 5
 and did so by using the command :

 ln -sf /lib/systemd/system/graphical.target 
 /etc/systemd/system/default.target

 Also, I appreciate everybody's input on this, but I am still at a loss
 as to how to fix this.  Without being able to reboot, it sure makes the
 set up difficult.

 Does anyone else have any ideas??

 Greg


 I have tried some additional changes that have not made a difference.

 I disabled selinux - that made no difference
 I stopped and disabled firewalld  - that made no difference.

 I can boot this machine after I turn it off and then back on, but when I
 try to do a shutdown now -r, the system hangs right after picking the OS
 that is desired CentOS Linux...

 After the machine is turned off the boot process occurs normally after
 this choice and I get two penguins in the upper left hand corner, and
 the boot proceeds.  When I do a shutdown now -r, I do not get to the
 penguins and the machine hangs forever until I either unplug it or press
 the power button for 5 seconds.

 Any help would be appreciated!!!

 Greg 

 ---
 
 Everyone, 
 
 I did not get much of a response on the list so I filed a bug report.  I
 wanted to document the bug report for anyone else that is having a
 reboot problem. 
 
 https://bugs.centos.org/view.php?id=7949
 
 
 Greg Ennis
 

Seems little point in filing a bug report when you have no idea what the
issue is. Bugs are not a means of troubleshooting nor a support forum.
However, you did get my attention so lets see if we can stimulate some
further interest in troubleshooting this.

So the system will perform a cold reboot, but not a warm reboot. Sounds
like a hardware issue to me.

Any clues in /var/log/messages ?

Tried updating the BIOS?

Any hardware firmwares being loaded?


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

Re: [CentOS] Fix for RHEL BZ#771868 in CentOS?

[Ned Slider]

On 01/12/14 20:33, Jeff Hammerbacher wrote:
 Hey,
 
 We are blocked on a bug fixed by RHEL in
 https://rhn.redhat.com/errata/RHBA-2012-0362.html. Specifically, the splice
 code in sendfile() incorrectly updating the offset position on the write
 side, Red Hat BZ#771868.
 
 I have not been able to figure out if this bugfix is included in any CentOS
 releases. If you are better at reading release notes than me, could you
 please help me out and let me know if there's a CentOS release that
 includes this bugfix?
 
 Thanks,
 Jeff

Hi Jeff,

It looks like it's fixed in the current kernel.

Hint: try grepping the package changelog:

$ rpm -q --changelog kernel-2.6.32-504.el6.x86_64 | grep sendfile
- [fs] Fix sendfile write-side file position (Steven Whitehouse) [770023]
- [fs] sendfile(): check f_op.splice_write() rather than f_op.sendpage()
(Lukas Czerner) [689426]

Those entries seem to match the bug description in the errata you list
so I'd guess it's fixed.


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

Re: [CentOS] Fix for RHEL BZ#771868 in CentOS?

[Ned Slider]

On 01/12/14 20:48, Ned Slider wrote:
 On 01/12/14 20:33, Jeff Hammerbacher wrote:
 Hey,

 We are blocked on a bug fixed by RHEL in
 https://rhn.redhat.com/errata/RHBA-2012-0362.html. Specifically, the splice
 code in sendfile() incorrectly updating the offset position on the write
 side, Red Hat BZ#771868.

 I have not been able to figure out if this bugfix is included in any CentOS
 releases. If you are better at reading release notes than me, could you
 please help me out and let me know if there's a CentOS release that
 includes this bugfix?

 Thanks,
 Jeff
 
 Hi Jeff,
 
 It looks like it's fixed in the current kernel.
 
 Hint: try grepping the package changelog:
 
 $ rpm -q --changelog kernel-2.6.32-504.el6.x86_64 | grep sendfile
 - [fs] Fix sendfile write-side file position (Steven Whitehouse) [770023]
 - [fs] sendfile(): check f_op.splice_write() rather than f_op.sendpage()
 (Lukas Czerner) [689426]
 
 Those entries seem to match the bug description in the errata you list
 so I'd guess it's fixed.
 

Further googling finds that it was fixed in the 6.2 kernel release, as
documented in the Technical Notes for 6.2:

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.2_Technical_Notes/kernel.html

^^ Search for sendfile and you will find it.


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

Re: [CentOS-docs] [CentOS] Broadcom WiFi Wiki Updated

[Ned Slider]

On 19/11/14 11:17, Milos Blazevic wrote:
 Hi all,
 
 
 Long time, no speak. Shifting from private sector job to full-time
 freelance work took its toll.
 As a result, among other things, the Broadcom Wiki page
 http://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom I maintain was
 neglected, and over the past couple of years I've been receiving e-mail
 inquiries about the Wiki and its applicability.
 
 I'm happy to say and let you all know that the Wiki page has been
 updated with instructions for compiling the latest Broadcom driver
 with the latest kernel release, and the driver was tested. The current
 instructions are applicable to CentOS 6 x86_64, but I'm hoping to expand
 that to CentOS 7 as well.
 CentOS 5 instructions were removed. Of course, I can post compilation
 instructions for 5 also, but it'd be tested on a VM and the driver
 module wouldn't actually go through proper testing. Your thoughts on
 this matter are certainly welcome.
 
 The page is still being reviewed/edited by myself and could use
 'polishing', but again, your feedback is always more than welcome and
 even desired!
 
 

Hi Milos,

Always great to see folks contributing, so thanks for your efforts!

Regarding Step 4a: Loading the driver module into kernel:

modprobe understands module dependencies and will automatically resolve
them whereas insmod does not. Therefore one should probably use modprobe
to load the module.

You mix the usage of insmod and modprobe in section 4a - for consistency
I would stick to modprobe at which point the discussion about manually
loading module dependencies becomes irrelevant and could be removed to
simplify the section.

I've also copied my reply to the centos-docs list.





___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS] Broadcom WiFi Wiki Updated

[Ned Slider]

On 19/11/14 11:17, Milos Blazevic wrote:
 Hi all,
 
 
 Long time, no speak. Shifting from private sector job to full-time
 freelance work took its toll.
 As a result, among other things, the Broadcom Wiki page
 http://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom I maintain was
 neglected, and over the past couple of years I've been receiving e-mail
 inquiries about the Wiki and its applicability.
 
 I'm happy to say and let you all know that the Wiki page has been
 updated with instructions for compiling the latest Broadcom driver
 with the latest kernel release, and the driver was tested. The current
 instructions are applicable to CentOS 6 x86_64, but I'm hoping to expand
 that to CentOS 7 as well.
 CentOS 5 instructions were removed. Of course, I can post compilation
 instructions for 5 also, but it'd be tested on a VM and the driver
 module wouldn't actually go through proper testing. Your thoughts on
 this matter are certainly welcome.
 
 The page is still being reviewed/edited by myself and could use
 'polishing', but again, your feedback is always more than welcome and
 even desired!
 
 

Hi Milos,

Always great to see folks contributing, so thanks for your efforts!

Regarding Step 4a: Loading the driver module into kernel:

modprobe understands module dependencies and will automatically resolve
them whereas insmod does not. Therefore one should probably use modprobe
to load the module.

You mix the usage of insmod and modprobe in section 4a - for consistency
I would stick to modprobe at which point the discussion about manually
loading module dependencies becomes irrelevant and could be removed to
simplify the section.

I've also copied my reply to the centos-docs list.





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

Re: [CentOS] Can't build RPM for i686 target (i386 works)

[Ned Slider]

On 19/11/14 20:40, Ian Pilcher wrote:
 I'm creating a simple RPM for my 32-bit CentOS 6 server.  When I build
 the RPM without specifying a target architecture (rpmbuild foo.spec), it
 successfully builds an i386 RPM.
 
 If I try to build an i686 RPM, I get nothing:
 
   $ rpmbuild --target i686 foo.spec
   Building target platforms: i686
   Building for target i686
 
 And I'm returned to command prompt with no error message.  The SPEC file
 doesn't contain any architecture-related tags.
 
 I feel like I must be missing something really, really basic, but I'll
 be darned if I can figure out what it might be.
 
 Any ideas?
 

Try running rpmbuild verbosely with -vv and see if that gives you any clues.

Can you rebuild other i686 packages? That should tell you if the issue
is with your build system or the package in question.

Have you ever edited any arch related parameters in ~/.rpmrc?


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

Re: [CentOS] Centos 7 Nvidia openGL breaks vncserver

[Ned Slider]

On 18/11/14 18:32, Stan Cruise wrote:
 Bare metal Centos 6.5, vncserver running, client able to connect with
 perfect resolution. Nvidia GT240, driver 331.49.
 
 Upgrade to Centos 7 with nouveau basic driver, all still works fine.
 Resolution poor on wire connected monitor, but perfect on vnc client
 session (1920x1080).
 
 Upgrade Nvidia driver via elrepo. 340.58; removed nouveau via 'Software'
 manager. Excellent wired monitor resolution.
 
 But  Client vnc connect receives the dreaded 'oh no, something has .'
 
 Backed out Nvidia  340.58, back to nouveau, client vnc works again. Also
 tried 304 driver (only other one in elrepo for el7) - same problem.
 

If it's of any help to you I have just restored the last 331.xx series
driver (331.89) to the elrepo repository. It's currently syncing and
should show up on the mirrors shortly. At least now you should be able
to make a like for like driver comparison with your el6 install.

http://elrepo.org/linux/elrepo/el7/x86_64/RPMS/

kmod-nvidia-331.89-1.el7.elrepo.x86_64.rpm
nvidia-x11-drv-32bit-331.89-1.el7.elrepo.x86_64.rpm
nvidia-x11-drv-331.89-1.el7.elrepo.x86_64.rpm


 Research seems to indicate that openGL does not play well with vnc. I
 cannot see any solutions posted as yet.
 
 So, what are my options?
 
 Maybe change out the video card for AMD? I cannot know if the Catalyst
 driver will work, but there is a much more active and extensive open
 driver community, which could work better than nouveau?
 
 And I noted the Linus 'salute' to Nvidia... Good timing.
 
 
 Stan
 

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

Re: [CentOS] Centos7 Net install on HP A1710N fails

[Ned Slider]

On 11/11/14 01:37, david wrote:
 At 03:23 PM 11/8/2014, you wrote:
 On Sat, Nov 8, 2014 at 3:21 PM, Akemi Yagi amy...@gmail.com wrote:

  The command to display the vendor:device PCI ID is:
 
  lspci -nn | grep -i net

 That was just for the ethernet device. Remove the grep part and you'll
 get the IDs for other hardware.

 Akemi
 
 
 Using the LiveCD for Centos 7, the network was Unknown.  The results
 of the lscpi command gave
 
 00:14.0 Bridge [0680]: Nvidia Corporation MCP51 Ethernet Controller
 [10DE:0269] (Revision A3)
 
 However, we could not define the ethernet controller and make it usable.
 
 David


Thank you for the information.

You need the kmod-forcedeth driver from elrepo.org for that device:

http://elrepo.org/linux/elrepo/el7/x86_64/RPMS/kmod-forcedeth-0.64-1.el7.elrepo.x86_64.rpm

Download and install the driver after installing CentOS 7.

Hope that helps.


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

Re: [CentOS] Centos7 Net install on HP A1710N fails

[Ned Slider]

On 08/11/14 22:32, david wrote:
 At 02:26 PM 11/7/2014, you wrote:
 On 11/7/2014 2:02 PM, david wrote:
 I took an older 64-bit machine, HP Pavillion A1710N

 ok, googled, and found...

 Athlon 64 X2 4200+ 2.2Ghz
 Geforce 6150LE chipset
 Asus A8M2N-LA motherboard
 1-4GB DDR2 ram
 SATA
 Ethernet: 100baseT - Marvell 88EC031
 
 Good spotting...
 
 Is this device known to be not supported in C7?  Recall that it worked
 just fine in a C6 Net-Install.  If not supported, is there any option
 but to get an add-on card with a modern NIC.
 
 David

We would need more information to answer that. The vendor:device PCI ID
pairing would be a good place to start. If you happen to know which
kernel module (driver) the device used under CentOS 6, that would be
helpful too.


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

Re: [CentOS] No X with new 6.6 kernel(SOLVED)

[Ned Slider]

On 30/10/14 01:43, Mark LaPierre wrote:
 On 10/29/14 07:03, Ned Slider wrote:
 On 29/10/14 03:09, Akemi Yagi wrote:
 On Tue, Oct 28, 2014 at 7:33 PM, Johnny Hughes joh...@centos.org wrote:
 On 10/28/2014 09:06 PM, Mark LaPierre wrote:
 On 10/28/14 21:13, Mark LaPierre wrote:
 Hey Y'all,

 After upgrade to 6.6 my gui will not start.  The problem is probably
 related to the dusty old video card I've got in this crusty old machine.

 01:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7600
 GS] (rev a2)

 I've got the proprietary drivers installed.  Normally when I update my
 kernel the video module is rebuilt automagically.  That probably doesn't
 work with the new kernel.

 I can get the GUI running by booting into the previous kernel version.

 Does anyone know what repository and package name I need to update the
 driver for 6.6?


 Okay, I erased kmod-nvidia-304xx and nvidia-x11-drv-304xx

 I booted into the new kernel and reinstalled kmod-nvidia-304xx and
 nvidia-x11-drv-304xx.

 After a reboot still no joy.

 The Xorg.0.log says:

 [57.575] (EE) NVIDIA: Failed to load the NVIDIA kernel module.
 Please check your
 [57.575] (EE) NVIDIA: system's kernel log for additional error
 messages.

 Where do I find said kernel log?



 Do you also have kernel-devel for the new kernel installed?

 I don't know how that package works (it is not in one of the CentOS
 repo's) but it might need to be updated by the provider to work with the
 new kernel as well.

 Akemi, is that an elrepo package .. and does it work with 6.6?

 Someone called my name ... :)

 Mark, first make sure you need the -304xx driver by running nvidia-detect:

 http://elrepo.org/tiki/nvidia-detect

 Once confirmed, you need to install the latest version of
 kmod-nvidia-304xx from the elrepo-testing repository on your 6.6 OS.
 Please see:

 http://elrepo.org/bugs/view.php?id=517

 They will eventually be moved to the elrepo main repository.

 Akemi

 Akemi is correct. Users of kmod-nvidia-304xx will need to update to the
 latest release (currently kmod-nvidia-304xx-304.123-3.el6.elrepo) at the
 same time as updating to 6.6.

 Please note, due to changes in the 6.6 kernel ABI, the original release
 (304.123-1) is compatible with 6.5 but NOT 6.6, and latest release
 (304.123-3) is compatible with 6.6 but NOT backwards compatible with
 6.5. This means you MUST update  kmod-nvidia-304xx at the same time as
 performing the 6.5 to 6.6 update / reboot if you want X to continue
 working seamlessly.

 The newer kmod-nvidia-304xx release(s) are in the elrepo-testing
 repository, and are now also syncing to the main elrepo repository.

 The current 340.xx driver is unaffected. The older 173.xx driver may
 also be similarly affected but I have not tested it and have yet to
 receive a bug report on it. If it is similarly broken I will fix it as
 and when someone reports it and is able to test the fix.

 Thanks.

 
 Hey Ned,
 
 The new driver package appeared on my update list this evening.  I
 installed it and rebooted into the new kernel.  All is well.
 
 

Hi Mark,

Thanks for the confirmation. Glad we got it fixed and apologies for the
slight delay / mishap you experienced.


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

Re: [CentOS] No X with new 6.6 kernel

[Ned Slider]

On 29/10/14 03:09, Akemi Yagi wrote:
 On Tue, Oct 28, 2014 at 7:33 PM, Johnny Hughes joh...@centos.org wrote:
 On 10/28/2014 09:06 PM, Mark LaPierre wrote:
 On 10/28/14 21:13, Mark LaPierre wrote:
 Hey Y'all,

 After upgrade to 6.6 my gui will not start.  The problem is probably
 related to the dusty old video card I've got in this crusty old machine.

 01:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7600
 GS] (rev a2)

 I've got the proprietary drivers installed.  Normally when I update my
 kernel the video module is rebuilt automagically.  That probably doesn't
 work with the new kernel.

 I can get the GUI running by booting into the previous kernel version.

 Does anyone know what repository and package name I need to update the
 driver for 6.6?


 Okay, I erased kmod-nvidia-304xx and nvidia-x11-drv-304xx

 I booted into the new kernel and reinstalled kmod-nvidia-304xx and
 nvidia-x11-drv-304xx.

 After a reboot still no joy.

 The Xorg.0.log says:

 [57.575] (EE) NVIDIA: Failed to load the NVIDIA kernel module.
 Please check your
 [57.575] (EE) NVIDIA: system's kernel log for additional error
 messages.

 Where do I find said kernel log?



 Do you also have kernel-devel for the new kernel installed?

 I don't know how that package works (it is not in one of the CentOS
 repo's) but it might need to be updated by the provider to work with the
 new kernel as well.

 Akemi, is that an elrepo package .. and does it work with 6.6?
 
 Someone called my name ... :)
 
 Mark, first make sure you need the -304xx driver by running nvidia-detect:
 
 http://elrepo.org/tiki/nvidia-detect
 
 Once confirmed, you need to install the latest version of
 kmod-nvidia-304xx from the elrepo-testing repository on your 6.6 OS.
 Please see:
 
 http://elrepo.org/bugs/view.php?id=517
 
 They will eventually be moved to the elrepo main repository.
 
 Akemi

Akemi is correct. Users of kmod-nvidia-304xx will need to update to the
latest release (currently kmod-nvidia-304xx-304.123-3.el6.elrepo) at the
same time as updating to 6.6.

Please note, due to changes in the 6.6 kernel ABI, the original release
(304.123-1) is compatible with 6.5 but NOT 6.6, and latest release
(304.123-3) is compatible with 6.6 but NOT backwards compatible with
6.5. This means you MUST update  kmod-nvidia-304xx at the same time as
performing the 6.5 to 6.6 update / reboot if you want X to continue
working seamlessly.

The newer kmod-nvidia-304xx release(s) are in the elrepo-testing
repository, and are now also syncing to the main elrepo repository.

The current 340.xx driver is unaffected. The older 173.xx driver may
also be similarly affected but I have not tested it and have yet to
receive a bug report on it. If it is similarly broken I will fix it as
and when someone reports it and is able to test the fix.

Thanks.


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

Re: [CentOS] Need to Understand booting process of CENTOS-7

[Ned Slider]

On 30/09/14 18:24, keshab mahapatra wrote:
 Team,
 
 could some help me understand the booting process of CENTOS-7
 
 I need to have constructive material where i could able present a
 presentation on booting process of CENTOS-7
 
 
 
 
 With Thanks  Regards,
 
 Keshaba Mahapatra
 Sr.Technical Consultant

How about I do your presentation for you and you pay me your salary!

I mean, seriously - according to your signature you are a Senior
Technical Consultant. Surely you can read the technical notes / product
manual provided by upstream, or if that does not contain enough in depth
material then man pages and google should be able to fill in the blanks
for you. At the very least I would expect a Senior Technical Consultant
to be able to research such things by himself and not post nonsense
questions to a public mailing list.

Jeez, and it's only Tuesday :-D




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

Re: [CentOS] Need to Understand booting process of CENTOS-7

[Ned Slider]

On 30/09/14 20:39, Digimer wrote:
 On 30/09/14 03:33 PM, Ned Slider wrote:
 On 30/09/14 18:24, keshab mahapatra wrote:
 Team,

 could some help me understand the booting process of CENTOS-7

 I need to have constructive material where i could able present a
 presentation on booting process of CENTOS-7




 With Thanks  Regards,

 Keshaba Mahapatra
 Sr.Technical Consultant

 How about I do your presentation for you and you pay me your salary!

 I mean, seriously - according to your signature you are a Senior
 Technical Consultant. Surely you can read the technical notes / product
 manual provided by upstream, or if that does not contain enough in depth
 material then man pages and google should be able to fill in the blanks
 for you. At the very least I would expect a Senior Technical Consultant
 to be able to research such things by himself and not post nonsense
 questions to a public mailing list.

 Jeez, and it's only Tuesday :-D
 
 That was a little rude, don't you think?
 

A little harsh maybe, but not rude. I didn't swear and I didn't
personally insult. I simply called it as I saw it. But I take your point.

It was the Senior part of the job title that set me off. IMHO the
level of questioning didn't in any way match up with the level of
professionalism inferred by the job title. To me it read more like a
grad student asking the list to do their latest assignment for them.


 I agree with your general premises; Keshaba could have started with
 google and then, perhaps, asked here if s/he got stuck on a particular
 part. That said though, there was no need for you to come down so hard,
 either.
 



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

Re: [CentOS] elrepo problem?

[Ned Slider]

On 09/09/14 17:02, Les Mikesell wrote:
 On Tue, Sep 9, 2014 at 10:54 AM, Jim Perrin jper...@centos.org wrote:


 On 09/09/2014 10:49 AM, Les Mikesell wrote:
 So much for elrepo being a painless way to get working Nvidia drivers...

 This isn't elrepo's fault.

 The glibc update changes the location of the ldconfig binary. It's still
 in root's path, but anything that had a hardcoded path as a requirement
 will break.
 
 Ummm, great...  I thought that was just the sort of breakage that
 'Enterprise' OS versions were supposed to avoid.  (I realize it's not
 CentOS's fault either).
 
 The original glibc package provides both /usr/sbin/ldconfig and
 /sbin/ldconfig, while the updated package only provides /sbin/ldconfig.
 
 The whole 's' concept was a bad idea to begin with.  Why did they have
 to make it worse?
 
 Yum update (or just update glibc) says:

 -- Processing Dependency: /usr/sbin/ldconfig for package:
 nvidia-x11-drv-304xx-304.123-1.el7.elrepo.x86_64
 -- Finished Dependency Resolution
 Error: Package: nvidia-x11-drv-304xx-304.123-1.el7.elrepo.x86_64 (@elrepo)
Requires: /usr/sbin/ldconfig
Removing: glibc-2.17-55.el7.x86_64 (@anaconda)
Not found
Updated By: glibc-2.17-55.el7_0.1.x86_64 (updates)
Not found
  You could try using --skip-broken to work around the problem

 What do those 'not found's mean?


 It means there's no more /usr/sbin/ldconfig provided in the newer packages.
 
 Seems odd to say it twice.   But what's the right fix here?
 

Hi Les,

Actually I think Jim is being generous and I do take at least some
responsibility for the breakage.

I've already committed a fix (below) but it won't show up until the next
nvidia legacy driver release:

https://github.com/elrepo/packages/commit/760a09a8147c4bc676dfa05c03d682255dbb52d6

For now, one workaround is to install the glibc update with --nodeps
(using rpm).


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

Re: [CentOS] Use postfix and spamd on CentOS 6 - looking for a shortest guide

[Ned Slider]

On 13/08/14 17:32, Timothy Murphy wrote:
 BC wrote:
 
 I've never seen a 1-page document that said,
 These are the changes I made after downloading packages X, Y and Z.
 
 There is a large chasm between configuring a mail server and understanding
 the configuration of a mail server. Due to the many pitfalls and custom
 environments, it is very difficult to have a 1-page document that does
 much more than be an outbound MTA.
 
 Note what I asked for.
 If you have installed postfix + spamassassin or whatever under CentOS
 then presumably you downloaded certain packages
 and then made certain changes in config files and perhaps elsewhere.
 Therefore it is possible to write a short document just listing
 the changes you have made.
 It may be a waste of time in your view;
 but in my experience this is exactly what I want to read
 for my very basic home server needs.
 

Yes, I did exactly that for CentOS 5, and you can find it on the Wiki here:

http://wiki.centos.org/HowTos#head-0facb50d5796bee0bd394636c32ffa9a997a6ab5

There's a basic Postfix/Dovecot guide:

http://wiki.centos.org/HowTos/postfix

It lists all the config changes required in Postfix and Dovecot for a
basic Postfix server (assumes networking knowledge).

Then you can add in some simple spam filtering with Postfix restrictions:

http://wiki.centos.org/HowTos/postfix_restrictions

or greylisting:

http://wiki.centos.org/HowTos/postgrey

or bolt on Amavisd/SpamAssassin:

http://wiki.centos.org/HowTos/Amavisd

or bolt on some encryption with SASL and SSL/TLS

http://wiki.centos.org/HowTos/postfix_sasl

These guides were all designed to be fully functional and modular so you
could pick just the bits you wanted to extend your basic Postfix
installation.

There will be some config differences between el5 and el6 due to the
different versions of the packages used. If you can't figure out the
differences just go with the docs provided on el5 - it's supported for
another 3 years or so.

If you get it working on el6/el7 please feel free to fork the docs for
those dists. I know of at least one person running this setup on el6
with the extra packages from EPEL.

This really isn't that difficult. The Postfix docs are excellent. You
just need to spend a day reading (and understanding) the docs. The main
confusion seems to stem from the fact that there are so many different
ways to implement a solution and there is no right or wrong way to do
it. But this just illustrates the ultimate flexibility of the software
you are using.

The methods documented above illustrate one such approach. I (and
another contributor to this list) documented it for the wider community
as it's the method we use. If you don't like it feel free to use another
approach, but please don't complain that there isn't any documentation
when we worked really hard to develop those docs for the community.





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

Re: [CentOS] Automating the preparation of kernel sources

[Ned Slider]

On 05/08/14 02:24, BC wrote:
 I have a driver that requires installing the kernel sources (into my own
 rpmbuild tree, not the system) prior to compiling. 

Are you absolutely sure?

What driver is it? With some specifics we might be able to help.

 I followed the info for
 centos6 here:
 
 http://wiki.centos.org/HowTos/I_need_the_Kernel_Source#head-a8dae925eec15786df9f6f8c918eff16bf67be0d
 
 I can successfully compile and install the module from tarball after
 manually prepping the kernel sources, but I need to turn this into a proper
 RPM and am wondering if there are macros I'm not seeing for how to prep the
 kernel sources as part of a %prep or %build phase. I have looked at many
 real-world spec files and googled all afternoon and cannot find any info on
 this. As this will ultimately be a mock build, having to go into the mock
 shell and manually prep the sources would be a PITA. Am I looking for
 something that doesn't exist?
 
 Thanks for any suggestions you might have!


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

Re: [CentOS] dlink ethernet pci card not detected

[Ned Slider]

On 31/07/14 18:21, Sathish Kumar wrote:
 my d-link ethernet pci card not detected in centos 7 even after i have
 installed kmod forcedth driver..
 
 
 output of lscpi -nn
 
 01:07.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6105/VT6106S
 [Rhine-III] [1106:3106] (rev 8b)
 
 pl help
 

Why would you install kmod-forcedeth? That is the driver for the NVIDIA
NIC. Please uninstall that package as it is not the correct driver for
your device.

The correct driver for your device is via-rhine.

If you give me a couple hours, I will make you a driver package and
upload it to the elrepo repository for el7.


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

Re: [CentOS] dlink ethernet pci card not detected

[Ned Slider]

On 31/07/14 18:57, Ned Slider wrote:
 On 31/07/14 18:21, Sathish Kumar wrote:
 my d-link ethernet pci card not detected in centos 7 even after i have
 installed kmod forcedth driver..


 output of lscpi -nn

 01:07.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6105/VT6106S
 [Rhine-III] [1106:3106] (rev 8b)

 pl help

 
 Why would you install kmod-forcedeth? That is the driver for the NVIDIA
 NIC. Please uninstall that package as it is not the correct driver for
 your device.
 
 The correct driver for your device is via-rhine.
 
 If you give me a couple hours, I will make you a driver package and
 upload it to the elrepo repository for el7.
 
 

Package built and uploaded to elrepo.org:

kmod-via-rhine-1.5.1-1.el7.elrepo.x86_64.rpm

It is currently syncing to the mirrors and should show up here shortly:

http://elrepo.org/linux/elrepo/el7/x86_64/RPMS/

Please let me know if it works as expected.

Thanks.


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

Re: [CentOS] /usr/bin/ld: cannot find -lncurses

[Ned Slider]

On 24/07/14 15:43, Samson wrote:
 Hi all,
 I am having this error when i tried to compile a program
 
 /usr/bin/ld: cannot find -lncurses
 collect2: ld returned 1 exit status
 /usr/bin/ld: cannot find -lncurses
 collect2: ld returned 1 exit status
 
 Kindly help me out.
 
 Regard.


Something simple maybe. Do you have ncurses-devel installed?


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

Re: [CentOS] Trying to install amavisd-new in CentOS-7

[Ned Slider]

On 21/07/14 11:37, Timothy Murphy wrote:
 When I try
   sudo yum install amavisd-new
 I get the message
 -
 Error: Package: amavisd-new-2.9.1-1.el7.noarch (epel)
Requires: perl(Unix::Syslog)
 Error: Package: amavisd-new-2.9.1-1.el7.noarch (epel)
Requires: clamav-server
 Error: Package: amavisd-new-2.9.1-1.el7.noarch (epel)
Requires: clamav-server-systemd
 Error: Package: amavisd-new-2.9.1-1.el7.noarch (epel)
Requires: cabextract
 Error: Package: amavisd-new-2.9.1-1.el7.noarch (epel)
Requires: perl(Convert::TNEF)
 -
 
 As this says, there is no clamav-server rpm
 (or clamav or clamd) in epel's CentOS-7 repository.
 
 I mentioned this before, and was advised to write to
 the epel mailing list.
 However, there doesn't appear to be any relevant epel list;
 there is an epel-developers list, but I am far from a developer.
 
 There is also a redhat bugzilla list,
 but will redhat be interested in a CentOS user?
 

Yes, that bugzilla is the correct place to file bugs for EPEL packages.

Here's the link:

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL

Or you can get to the right place by clicking to file a New bug on the
top menu bar, selecting Fedora and then Fedora EPEL.

Then file your bug report against amavisd-new in the Component box.

They will be interested to receive bug reports from ALL users,
regardless if genuine or clone (RHEL, CentOS, Scientific Linux etc).

Hope that helps.


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

Re: [CentOS] el7: Thunderbird?

[Ned Slider]

On 19/07/14 13:25, Chris Pemberton wrote:
 
 On 07/18/2014 02:19 PM, Ned Slider wrote:
 I note EPEL has a thunderbird package but it seems very out of date at
 version 24.5.0. Version 24.6.0 was released 10 June, nearly 6 weeks ago,
 and fixed 3 critical security issues. Is this normal for EPEL to be so
 far behind on security updates?

 So what is everyone else using?
 
 I'm using the EPEL package for my personal laptop.  The odds of me 
 getting bit by a 6 week old exploit are probably almost non-existent.  
 The odds of me forgetting to keep a custom install of thunderbird 
 updated outside of yum is very high.
 

Yes, the power of a centralized packaging system where everything can be
updated in one hit can not be understated.

Firefox and Thunderbird do have a built in updating mechanism and are
supposed to update themselves (this is disabled in packaged versions).
I've no idea how well it currently works - I'll let you know when the
next update comes out.

 I'm far from any kind of security expert, but here are two things I do 
 to keep my browser/email client safe:
 
 1.  I only use gmail - as Google likes to scrub all of my data clean 
 before they steal it
 
 2.  I install a custom hosts file ( http://someonewhocares.org/hosts/ 
 ).  This protects all applications in one swoop, not just the browser.
 

Yes, great advice. There's another popular variant here:

http://winhelp2002.mvps.org/hosts.htm

 I don't use any adblock browser/email plugins because I've never 
 investigated where the list of re-directs are stored on the machine.  
 Perhaps they are harmless... but it would be easy to place a few 
 re-directs in there and get millions of machines to do bad things real fast.
 
 ~ Chris

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

[CentOS] el7: Thunderbird?

[Ned Slider]

Hi Folks,

Just wondering what Thunderbird users are doing on el7 now it's been
removed from the distro?

I note EPEL has a thunderbird package but it seems very out of date at
version 24.5.0. Version 24.6.0 was released 10 June, nearly 6 weeks ago,
and fixed 3 critical security issues. Is this normal for EPEL to be so
far behind on security updates?

The other alternative seems to be running the tarball from Mozilla, but
that is only available in 32-bit and I don't really want to install a
whole bunch of 32-bit libs just to run one program.

So what is everyone else using?

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

Re: [CentOS] el7: Thunderbird?

[Ned Slider]

On 18/07/14 21:22, James Pearson wrote:
 Ned Slider wrote:

 The other alternative seems to be running the tarball from Mozilla, but
 that is only available in 32-bit and I don't really want to install a
 whole bunch of 32-bit libs just to run one program.
 
 Mozilla do have 64 bit builds:
 
 http://ftp.mozilla.org/pub/mozilla.org/thunderbird/releases/24.6.0/linux-x86_64/
 
 James Pearson

Many thanks James, I didn't know they existed!

I'll give that a try.


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

Re: [CentOS] ngrep missing in epel el7

[Ned Slider]

On 12/07/14 15:32, 彭勇 wrote:
 ngrep is a great network packet capture.
 
 will it be included in epel?
 
 

Wrong list. This is the CentOS mailing list.

You will need to ask on the EPEL mailing list :-)

HTH


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

Re: [CentOS] nvidia ethernet port not detected centos 7

[Ned Slider]

On 13/07/14 04:44, sathish wrote:
 hi
 
 When i tried to install centos 7, my nvidia ethernet port not detected 
 during installation whereas all of other distros working perfectly 
 without any problem... Pl help..
 
 my rig is AMD Athlon x2 64 processor and Nvidia chipset..
 
 output of lspci -nn | grep -i net
 
 00:0a.0 Ethernet controller [0200]: NVIDIA Corporation MCP77 Ethernet 
 [10de:0760] (rev a2)
 
 with regards
 sathish.
 


This device uses the forcedeth driver which is disabled in the CentOS 7
kernel.

You can use the kmod-forcedeth driver from elrepo.org:

http://elrepo.org/linux/elrepo/el7/x86_64/RPMS/kmod-forcedeth-0.64-1.el7.elrepo.x86_64.rpm


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

Re: [CentOS] Moving sshd listen port

[Ned Slider]

On 09/07/14 16:45, Robert Moskowitz wrote:
 
 On 07/09/2014 10:50 AM, Mike McCarthy, W1NR wrote: This was a
 minimal install for a virtual server and semanage is not 
 available so the command doesn't work...
 
 What package is semanage in?
 
 Had to dig back in my notes:
 
 policycoreutils-python
 

Yum will tell you:

yum provides */semanage

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

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Ned Slider]

On 08/07/14 02:22, Always Learning wrote:
 
 On Mon, 2014-07-07 at 20:46 -0400, Robert Moskowitz wrote:
 
 On 07/07/2014 07:47 PM, Always Learning wrote:
 Reading about systemd, it seems it is not well liked and reminiscent of
 Microsoft's put everything into the Windows Registry (Win 95 onwards).

 Is there a practical alternative to omnipresent, or invasive, systemd ?
 
 So you are following the thread on the Fedora list?  I have been 
 ignoring it.
 
 No. I read some of
 http://www.phoronix.com/scan.php?page=news_topicq=systemd
 
 The systemd proponent, advocate and chief developer? wants to
 abolish /etc and /var in favour of having the /etc and /var data
 in /usr.
 
 Seems a big revolution is being forced on Linux users when stability and
 the same old familiar Linux is desired by many, including me.
 

It's already started. Some configs have already moved from /etc to /usr
under el7.

Whilst I'm as resistant to change as the next man, I've learned you
can't fight it so best start getting used to it ;-)

 Best I can tell is learn it and use it.  And if you have any services, 
 fix them so that they work with systemd.  I work with one that does not 
 and it is very slow to complete its startup.
 
 I was keenly waiting to upgrade to C7. Perhaps I'll upgrade to C6 and
 retain familiar Linux.
 
 

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

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Ned Slider]

On 08/07/14 14:14, Dennis Jacobfeuerborn wrote:
 On 08.07.2014 14:58, Adrian Sevcenco wrote:
 On 07/08/2014 04:22 AM, Always Learning wrote:

 On Mon, 2014-07-07 at 20:46 -0400, Robert Moskowitz wrote:

 On 07/07/2014 07:47 PM, Always Learning wrote:
 Reading about systemd, it seems it is not well liked and reminiscent of
 Microsoft's put everything into the Windows Registry (Win 95 onwards).

 Is there a practical alternative to omnipresent, or invasive, systemd ?

 So you are following the thread on the Fedora list?  I have been 
 ignoring it.

 No. I read some of
 http://www.phoronix.com/scan.php?page=news_topicq=systemd

 The systemd proponent, advocate and chief developer? wants to
 abolish /etc and /var in favour of having the /etc and /var data
 in /usr.
 err.. what? even on that wild fedora thread this did not come up!!!

 i will presume that you understood well your information source and you
 are actually know what you are referring to ... so, could you elaborate
 more about this?(with some references)
 i use systemd for some time (and i keep myslef informed about it) and i
 would need to know in time about this kind of change..
 
 There are no plans to abolish /etc and /var.
 
 The idea is that rather than say proftpd shipping a default config file
 /etc/proftpd.conf that you then have to edit for you needs instead it
 will ship the default config somewhere in /usr and let the config in
 /etc override the one in /usr. That way if you want to factory reset
 the system you can basically clear out /etc and you are back do the
 defaults. The same applies to /var.
 The idea is that /etc and /var become site-local directories that only
 contain the config you actually changed from the defaults for this system.
 
 Since you already have experience with systemd you are already familiar
 with this system where it stores its unit files in /usr/lib/systemd and
 if you want to change some of them you copy them to /etc/systemd and
 change them there. Same principle.
 
 /etc and /var will stay as valid as ever though and are not being
 abolished.
 

That's not always true.

Some configs that were under /etc on el6 must now reside under /usr on el7.

Take modprobe blacklists for example.

On el5 and el6 they are in /etc/modprobe.d/

On el7 they need to be in /usr/lib/modprobe.d/

If you install modprobe blacklists to the old location under el7 they
will not work.

I'm sure there are other examples, this is just one example I've
happened to run into.


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

Re: [CentOS] Cemtos 7 : Systemd alternatives ?

[Ned Slider]

On 08/07/14 18:36, Dennis Jacobfeuerborn wrote:
 On 08.07.2014 15:53, Ned Slider wrote:
 On 08/07/14 14:14, Dennis Jacobfeuerborn wrote:
 On 08.07.2014 14:58, Adrian Sevcenco wrote:
 On 07/08/2014 04:22 AM, Always Learning wrote:

 On Mon, 2014-07-07 at 20:46 -0400, Robert Moskowitz wrote:

 On 07/07/2014 07:47 PM, Always Learning wrote:
 Reading about systemd, it seems it is not well liked and reminiscent of
 Microsoft's put everything into the Windows Registry (Win 95 onwards).

 Is there a practical alternative to omnipresent, or invasive, systemd ?

 So you are following the thread on the Fedora list?  I have been 
 ignoring it.

 No. I read some of
 http://www.phoronix.com/scan.php?page=news_topicq=systemd

 The systemd proponent, advocate and chief developer? wants to
 abolish /etc and /var in favour of having the /etc and /var data
 in /usr.
 err.. what? even on that wild fedora thread this did not come up!!!

 i will presume that you understood well your information source and you
 are actually know what you are referring to ... so, could you elaborate
 more about this?(with some references)
 i use systemd for some time (and i keep myslef informed about it) and i
 would need to know in time about this kind of change..

 There are no plans to abolish /etc and /var.

 The idea is that rather than say proftpd shipping a default config file
 /etc/proftpd.conf that you then have to edit for you needs instead it
 will ship the default config somewhere in /usr and let the config in
 /etc override the one in /usr. That way if you want to factory reset
 the system you can basically clear out /etc and you are back do the
 defaults. The same applies to /var.
 The idea is that /etc and /var become site-local directories that only
 contain the config you actually changed from the defaults for this system.

 Since you already have experience with systemd you are already familiar
 with this system where it stores its unit files in /usr/lib/systemd and
 if you want to change some of them you copy them to /etc/systemd and
 change them there. Same principle.

 /etc and /var will stay as valid as ever though and are not being
 abolished.


 That's not always true.

 Some configs that were under /etc on el6 must now reside under /usr on el7.

 Take modprobe blacklists for example.

 On el5 and el6 they are in /etc/modprobe.d/

 On el7 they need to be in /usr/lib/modprobe.d/

 If you install modprobe blacklists to the old location under el7 they
 will not work.

 I'm sure there are other examples, this is just one example I've
 happened to run into.
 
 You might want to report this as a bug. The modprobe and modprobe.d man
 pages explicitly reference /etc/modprobe.d/*.conf for the configuration.
 
 Regards,
   Dennis

Well, I stand corrected!

I was just running though the issue for a reply here, and what was
broken in the rhel7rc is now fixed and indeed working as documented.

My issue looked like a regression of this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=873220


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

Re: [CentOS] compiling centos 6.5 linux-2.6.32-431.el6-kernel

[Ned Slider]

On 19/06/14 05:57, Dilip Basavaraju wrote:
 Dear all,

  I have compiled the  linux-2.6.32-431.el6-kernel with the 
 following steps

 1.Make mproper

 2.Make menuconfig

 3.Make

 4.Make modules

 5.Make modules_install
 The compilation is successful but there is a huge change in the size of the 
 .ko generated compared to original .ko from the rpm.

 Please suggest the steps to compile the centos  linux-2.6.32-431.el6-kernel 
 and use the modules and to build the kernel.rpm


It's extremely well documented in the 3 kernel articles on the Wiki:

http://wiki.centos.org/HowTos#head-c4dbf9ecb355694c78175c7eaad46a2472a3849b



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