Re: [CentOS] CentOS 6 as DNS-Server

[Walter H.]

On 10.05.2016 21:36, Александр Кириллов wrote:
I'm also using ddns and have my zone files in 
/var/named/chroot/var/named/dynamic.

are you using DDNS in DualStack (IPv4 and IPv6 together) or do you
have only DHCP or DHCPv6 and not both?


IPv4 only.

if a host has IPv4 only or IPv6 only this works fine, but when a host 
has both - DualStack

somethimes it works sometimes only one - can be IPv4 or can be IPv6 works;
and in /var/log/messages  I get something like

May 10 18:51:30 dnssrvr named[2526]: client 192.168.1.2#38618: view 
wkst: updating zone 'ddns.local/IN': update unsuccessful: 
WIN7HOST.ddns.local: 'name not in use' prerequisite not satisfied (YXDOMAIN)


for several times;

   By default, SELinux prevents any role from modifying named_zone_t
   files; this means that files in the zone database directory 
cannot be

   modified by dynamic DNS (DDNS) updates or zone transfers.

   The Red Hat BIND distribution and SELinux policy creates three
   directories where named is allowed to create and modify files:
   /var/named/slaves, /var/named/dynamic /var/named/data. By 
placing files
   you want named to modify, such as slave or DDNS updateable 
zone files
   and database / statistics dump files in these directories, 
named will
   work normally and no further operator action is required. 
Files in
   these directories are automatically assigned the 
’named_cache_t’ file

   context, which SELinux allows named to write."


That's probably why I have updateable zone files in chrooted 
/var/named/dynamic.

Default targeted policy comes with necessary rules for chrooted bind. See

# semanage fcontext -l | grep named_


I have them in /var/named/dynamic


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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[Valeri Galtsev]

On Tue, May 10, 2016 2:22 pm, Hakan Peker wrote:
> On 05/10/2016 06:44 PM, Valeri Galtsev wrote:
>>
>> "Other systems" you mention I bet are Debian and its clones (Ubuntu
>> being
>> one of them). These systems have different update philosophy than that
>> of
>> RedHat Enterprise Linux (and hence what CentOS is, which is derived from
>> RHEL). Namely, these "other systems" do constant micro-upgrades of
>> components installed on the system to latest release, whenever new
>> release
>> of given piece of software happens. To the contrary, RHEL mostly
>> backports
>> important security fixes to a version that was included in original
>> system
>> release (but occasionally does make upgrades). Hence the differences:
>>
>> 1. Debian (and clones): you keep the components of the system pretty
>> much
>> on the level of latest release of each of components. Therefore
>> "upgrade"
>> to new release of the system is pretty close to just a regular routine
>> update. This apparent advantage comes with a disadvantage, namely: every
>> update has a potential to break something on your machine, as new
>> release
>> may have different internals, then you will need to work on migration to
>> them, and this can come as a surprise with any of routine updates.
>>
>
> This is so flat out wrong that I don't know where to begin, and this is
> not the place to give a lecture about Debian stable or Ubuntu LTS
> release process anyway.
>
> Not knowing something is perfectly normal and it is nothing to be
> ashamed of, spreading misinformation about a topic you have no knowledge
> of and doing it in a public list *and* when nobody asked you about it,
> on the other hand...

Smashing! ;-)

You can begin by describing what the differences are, or by making the
statement that there are no differences whatsoever. Both will be helpful
to everybody. Another option would be e-mail privately to list moderators
and suggest to moderate an idiot (yours truly), - whoever does more damage
than help does deserve to be moderated. Either of the above suggestions
will be more productive than this post IMHO.

Thanks.

Valeri


Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

Re: [CentOS] CentOS 6 as DNS-Server

[Alice Wonder]

On 05/10/2016 12:08 PM, m.r...@5-cent.us wrote:


Which assumes that setting selinux to enforcing doesn't break your
websites, or the locally-created root directories that have been created
before an actual sysadmin came onboard, or



That's my biggest problem with SELinux. I suppose at some point I need 
to invest both time and money and take a class on it, but every time I 
try to use it - it gets in the way and when I try to resolve it, the 
documentation is very confusing and I think the documentation often 
makes assumptions about concepts being known that I don't know.


I know that it can be a significant benefit when you are attacked with 
an exploit that either is either zero-day or hasn't been patched, but so 
far when I have tried enabling SELinux it ends up taking up hours and 
hours and hours of my time.


And sometimes the problems are things like tmpfs - I don't remember 
exactly what it was, but I had an issue where when I finally got help, 
the answer was don't use tmpfs if you have SELinux enabled.


I want to use it, I do, but so far it has only caused me grief.

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

Re: [CentOS] CentOS 6 as DNS-Server

[m . roth]

Walter H. wrote:
> On 10.05.2016 18:57, Александр Кириллов wrote:
>>> this seems to be relevant in chroot environments;
>>>
>>> as I noticed when configuring the DDNS-feature, that this is a little
>>> bit weired, when running in a chroot environment; I saw the
>>> recommendation not
>>> to use a chroot in the man-page and removed bind-chroot and then the
>>> zone updates worked perfekt;
>>>
>>> so this file /etc/named.root.key isn't really used; or am I missing
>>> something?
>>
>> These files are included in both my /etc/named.conf and
>> /usr/share/doc/bind-x.x.x/named.conf.default which I probably used as
>> a template years ago. I'm no dns expert but you'd probably need these
>> files when accessing root servers directly without use of forwarders.
>>
>> I'm also using ddns and have my zone files in
>> /var/named/chroot/var/named/dynamic.
> are you using DDNS in DualStack (IPv4 and IPv6 together) or do you have
> only DHCP or DHCPv6 and not both?
>> Selinux is enabled and I don't see any additional bind-related rules
>> in my local policy or
>> /etc/selinux/targeted/contexts/files/file_contexts.local.
>>
>
> the manpage shows this:
>
> "NOTES
> Red Hat SELinux BIND Security Profile:
>
> By default, Red Hat ships BIND with the most secure SELinux
> policy that  will not prevent normal BIND operation and will prevent
> exploitation of all known BIND security vulnerabilities . See the

Which assumes that setting selinux to enforcing doesn't break your
websites, or the locally-created root directories that have been created
before an actual sysadmin came onboard, or

mark

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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[Alice Wonder]

On 05/10/2016 12:19 AM, Johnny Hughes wrote:

On 05/10/2016 02:08 AM, Venkateswara Rao Dokku wrote:

Hi,

I would like to know whether the valid upgrade path will be present from
CentOS 7 to future versions like we get for Ubuntu or some other operating
systems.

Right now, I am sure that we do not have proper update path in CentOS to
move from one version to another.



If you mean upgrade to all CentOS-7 point releases, yes (from source
code for RHEL-7.0 to RHEL-7.1, to RHEL-7.2).  If you mean from CentOS-7
to CentOS-8, there is no way to know.  There is no RHEL-8 to look at.

Red Hat has source code for preupgrade-assistant and
redhat-upgrade-tool.  That is created for inplace upgrades from one
major version to another.  Currently those tools are community and
maintained and they are several updates behind because currently no one
in the community has stepped up to maintain them.

But, CentOS-7 has an EOL of June 30, 2024 .. so there is security
updates for 8 more years.




I tend to keep all server content in /srv and all user content in /home

Upgrading from one major version to another then is pretty simple - but 
not on the same machine.


I do a fresh install of the new version in a new vm, make sure all the 
services are in place, and all the user and group ids match.


I can then rsync the old /home and /srv to the new system.

Yes there are server migration files that need to be migrated but what I 
like about this approach is I can keep serving from the old server until 
this is done and tested in the new server, and then it is just a simple 
DNS change and the new server is used.


Migrating configuration files to me means starting with the defaults in 
the new version and modifying them to match the needs of the service, 
not replacing them with the old files.


I have tried updating between major versions in Fedora before and there 
were always too many glitches, it really is better to clean install and 
migrate the data. In my opinion. Especially if you skip a release like I 
tend to do.


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

Re: [CentOS] CentOS 6 as DNS-Server

[Walter H.]

On 10.05.2016 18:57, Александр Кириллов wrote:

this seems to be relevant in chroot environments;

as I noticed when configuring the DDNS-feature, that this is a little 
bit
weired, when running in a chroot environment; I saw the 
recommendation not
to use a chroot in the man-page and removed bind-chroot and then the 
zone

updates worked perfekt;

so this file /etc/named.root.key isn't really used; or am I missing
something?


These files are included in both my /etc/named.conf and 
/usr/share/doc/bind-x.x.x/named.conf.default which I probably used as 
a template years ago. I'm no dns expert but you'd probably need these 
files when accessing root servers directly without use of forwarders.


I'm also using ddns and have my zone files in 
/var/named/chroot/var/named/dynamic.
are you using DDNS in DualStack (IPv4 and IPv6 together) or do you have 
only DHCP or DHCPv6 and not both?
Selinux is enabled and I don't see any additional bind-related rules 
in my local policy or 
/etc/selinux/targeted/contexts/files/file_contexts.local.




the manpage shows this:

"NOTES
   Red Hat SELinux BIND Security Profile:

   By default, Red Hat ships BIND with the most secure SELinux 
policy that
   will not prevent normal BIND operation and will prevent 
exploitation of
   all known BIND security vulnerabilities . See the selinux(8) man 
page

   for information about SElinux.

   It is not necessary to run named in a chroot environment if the 
Red Hat
   SELinux policy for named is enabled. When enabled, this policy 
is far
   more secure than a chroot environment. Users are recommended to 
enable

   SELinux and remove the bind-chroot package.

   With this extra security comes some restrictions:

   By default, the SELinux policy does not allow named to write any 
master

   zone database files. Only the root user may create files in the
   $ROOTDIR/var/named zone database file directory (the options {
   "directory" } option), where $ROOTDIR is set in 
/etc/sysconfig/named.


   The "named" group must be granted read privelege to these files in
   order for named to be enabled to read them.

   Any file created in the zone database file directory is 
automatically

   assigned the SELinux file context named_zone_t .

   By default, SELinux prevents any role from modifying named_zone_t
   files; this means that files in the zone database directory 
cannot be

   modified by dynamic DNS (DDNS) updates or zone transfers.

   The Red Hat BIND distribution and SELinux policy creates three
   directories where named is allowed to create and modify files:
   /var/named/slaves, /var/named/dynamic /var/named/data. By 
placing files
   you want named to modify, such as slave or DDNS updateable zone 
files
   and database / statistics dump files in these directories, named 
will

   work normally and no further operator action is required. Files in
   these directories are automatically assigned the ’named_cache_t’ 
file

   context, which SELinux allows named to write."


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

Re: [CentOS] CentOS 6 as DNS-Server

[Александр Кириллов]

I'm also using ddns and have my zone files in 
/var/named/chroot/var/named/dynamic.

are you using DDNS in DualStack (IPv4 and IPv6 together) or do you
have only DHCP or DHCPv6 and not both?


IPv4 only.

   By default, SELinux prevents any role from modifying 
named_zone_t
   files; this means that files in the zone database directory 
cannot be

   modified by dynamic DNS (DDNS) updates or zone transfers.

   The Red Hat BIND distribution and SELinux policy creates three
   directories where named is allowed to create and modify files:
   /var/named/slaves, /var/named/dynamic /var/named/data. By 
placing files
   you want named to modify, such as slave or DDNS updateable zone 
files
   and database / statistics dump files in these directories, named 
will
   work normally and no further operator action is required. Files 
in
   these directories are automatically assigned the ’named_cache_t’ 
file

   context, which SELinux allows named to write."


That's probably why I have updateable zone files in chrooted 
/var/named/dynamic.
Default targeted policy comes with necessary rules for chrooted bind. 
See


# semanage fcontext -l | grep named_

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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[m . roth]

Alice Wonder wrote:
> On 05/10/2016 12:19 AM, Johnny Hughes wrote:
>> On 05/10/2016 02:08 AM, Venkateswara Rao Dokku wrote:
>>>
>>> I would like to know whether the valid upgrade path will be present
>>> from CentOS 7 to future versions like we get for Ubuntu or some other
>>> operating systems.
>>>
>>> Right now, I am sure that we do not have proper update path in CentOS
>>> to move from one version to another.
>>
> I tend to keep all server content in /srv and all user content in /home
>
> Upgrading from one major version to another then is pretty simple - but
> not on the same machine.
>
> I do a fresh install of the new version in a new vm, make sure all the
> services are in place, and all the user and group ids match.

I had an article published in the late, lamented SysAdmin magazine about
10 years ago, where I recommended having a three of spare partitions,
doing an install using those  for /, /usr and /boot - though now you could
get away with / and /boot. Then, if you had show-stopper issues, you could
always boot back via the old partitions.

Where I work, I don't think we have a handful of VMs... because in a lot
of cases, we need every bloody CPU cycle. For example, we have an SGI
UV2000, a small, true supercomputer, 512 cores, 2TB RAM...and I see top
telling me that one of my users's multithreaded parallel job has a load of
it of 467 (and no, I'm not misplacing the decimal point)

 mark


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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[Hakan Peker]

On 05/10/2016 06:44 PM, Valeri Galtsev wrote:


"Other systems" you mention I bet are Debian and its clones (Ubuntu being
one of them). These systems have different update philosophy than that of
RedHat Enterprise Linux (and hence what CentOS is, which is derived from
RHEL). Namely, these "other systems" do constant micro-upgrades of
components installed on the system to latest release, whenever new release
of given piece of software happens. To the contrary, RHEL mostly backports
important security fixes to a version that was included in original system
release (but occasionally does make upgrades). Hence the differences:

1. Debian (and clones): you keep the components of the system pretty much
on the level of latest release of each of components. Therefore "upgrade"
to new release of the system is pretty close to just a regular routine
update. This apparent advantage comes with a disadvantage, namely: every
update has a potential to break something on your machine, as new release
may have different internals, then you will need to work on migration to
them, and this can come as a surprise with any of routine updates.



This is so flat out wrong that I don't know where to begin, and this is 
not the place to give a lecture about Debian stable or Ubuntu LTS 
release process anyway.


Not knowing something is perfectly normal and it is nothing to be 
ashamed of, spreading misinformation about a topic you have no knowledge 
of and doing it in a public list *and* when nobody asked you about it, 
on the other hand...


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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[m . roth]

Alice Wonder wrote:
> On 05/10/2016 01:29 PM, m.r...@5-cent.us wrote:
>> Alice Wonder wrote:
>>> On 05/10/2016 12:19 AM, Johnny Hughes wrote:
 On 05/10/2016 02:08 AM, Venkateswara Rao Dokku wrote:
>
> I would like to know whether the valid upgrade path will be present
> from CentOS 7 to future versions like we get for Ubuntu or some other
> operating systems.
>
> Right now, I am sure that we do not have proper update path in CentOS
> to move from one version to another.

>>> I tend to keep all server content in /srv and all user content in /home
>>>
>>> Upgrading from one major version to another then is pretty simple - but
>>> not on the same machine.
>>>
>>> I do a fresh install of the new version in a new vm, make sure all the
>>> services are in place, and all the user and group ids match.
>> 
>> I had an article published in the late, lamented SysAdmin magazine about
>> 10 years ago, where I recommended having a three of spare partitions,
>> doing an install using those  for /, /usr and /boot - though now you
>> could get away with / and /boot. Then, if you had show-stopper issues, you
>> could always boot back via the old partitions.
>>
>> Where I work, I don't think we have a handful of VMs... because in a lot
>> of cases, we need every bloody CPU cycle. For example, we have an SGI
>> UV2000, a small, true supercomputer, 512 cores, 2TB RAM...and I see top
>> telling me that one of my users's multithreaded parallel job has a load
>> of it of 467 (and no, I'm not misplacing the decimal point)
>>
> Ah - yes, different perspective I suppose. Vast majority of servers I
> manage are VMs purchased for a monthly fee from a service provider like
> linode. If you run the physical hardware yourself that is a completely
> different set of circumstances, point taken.

Yup. I'm 0ne of 3.5 sysadmins, and we run better than 170 servers and
workstations. (.5, because she's at another Institute the other half of
her time.)

   mark

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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[Johnny Hughes]

On 05/10/2016 05:15 PM, phil wrote:



> This would be a good question for the ubuntu users list . . .
> 
> Ubuntu user technical support,
>  not for general discussions 
> 

I agree :)







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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[Alice Wonder]

On 05/10/2016 01:29 PM, m.r...@5-cent.us wrote:

Alice Wonder wrote:

On 05/10/2016 12:19 AM, Johnny Hughes wrote:

On 05/10/2016 02:08 AM, Venkateswara Rao Dokku wrote:


I would like to know whether the valid upgrade path will be present
from CentOS 7 to future versions like we get for Ubuntu or some other
operating systems.

Right now, I am sure that we do not have proper update path in CentOS
to move from one version to another.



I tend to keep all server content in /srv and all user content in /home

Upgrading from one major version to another then is pretty simple - but
not on the same machine.

I do a fresh install of the new version in a new vm, make sure all the
services are in place, and all the user and group ids match.


I had an article published in the late, lamented SysAdmin magazine about
10 years ago, where I recommended having a three of spare partitions,
doing an install using those  for /, /usr and /boot - though now you could
get away with / and /boot. Then, if you had show-stopper issues, you could
always boot back via the old partitions.

Where I work, I don't think we have a handful of VMs... because in a lot
of cases, we need every bloody CPU cycle. For example, we have an SGI
UV2000, a small, true supercomputer, 512 cores, 2TB RAM...and I see top
telling me that one of my users's multithreaded parallel job has a load of
it of 467 (and no, I'm not misplacing the decimal point)



Ah - yes, different perspective I suppose. Vast majority of servers I 
manage are VMs purchased for a monthly fee from a service provider like 
linode. If you run the physical hardware yourself that is a completely 
different set of circumstances, point taken.


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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[Bill Maltby (C4B)]

On Tue, 2016-05-10 at 10:44 -0500, Valeri Galtsev wrote:
> 

> 2. RHEL (and derivatives): you do routine updates, and all is guaranteed
> to keep working as it did when you originally configured your machine.

*Almost*. exception was 6.5->6.6 upgrade.

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

Caveat: my assessment may be wrong in that it all works, but not the way
it used to, meaning things broke when I tried to use it the way I used
to use it, and I spent a great deal of time discovering some of the
underlying causes and my eventual work-around.

There was also a couple "not the way it used to" regarding X start-up
and an extra instance of Firefox being started, which I posted
"corrections" for in the form of patches to the scripts.

Based on my memory, as you may have seen in another thread, this was a
change from the past.

> 

> Valeri
> 

Bill

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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[phil]

On 11/05/2016 8:12 AM, Valeri Galtsev wrote:


On Tue, May 10, 2016 3:57 pm, Liam O'Toole wrote:

On 2016-05-10, Valeri Galtsev
 wrote:


1. Debian (and clones): you keep the components of the system pretty
much on the level of latest release of each of components. Therefore
"upgrade" to new release of the system is pretty close to just a
regular routine update.


You are describing Debian sid/unstable, which is contunuously updated,
and where there are no releases in the usual sense of the word. Debian
stable releases are a different matter, and correspond very closely to
major releases of RHEL/CentOS. There is always an upgrade path between
consecutive releases of Debian stable.



Yes, LTS, thanks Liam. Only LTS has life cycle of mere 2 years, whereas
RHEL (hence CentOS) is what, 10 years? I was pretty sure Debian does not
backport patches (of Linuxes no one except RH, as far as I know). How do
they do it with LTS?


This would be a good question for the ubuntu users list . . .

Ubuntu user technical support,
 not for general discussions 

Do they just freeze major version, no matter what (it

is only 2 years the need)?

Thanks.
Valeri



Liam


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





Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

___
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

[CentOS] test builds on mesa

[Andreas Benzler]

Hello Guys...

I wanne let you know that i recently tested  my 
mesa builds 11.2.2 with libdrm 2.4.8  tested on  intel (mesa) and radeon
(d3dadapter)

http://centos.cms4all.org/centos/7/drivers/
http://centos.cms4all.org/centos/7/mesa/

mesa is build with llvm-3.8.0 (skylake patch)

Fixes all my serious problems by use kernel 4.6.RC7, private only here..

wine - easy build to 1.9.9 all in once 64 + 32
http://centos.cms4all.org/centos/7/wine/

Sincerely

Andy

PS: 
mesa rebuild needs --enblerepo cms4all-drivers,cms4all-llvm (libdrm
2.6.8 /cmake)
http://centos.cms4all.org/centos/7/llvm/

[cms4all-llvm]
name=cms4all-llvm
baseurl=http://centos.cms4all.org/centos/7/llvm/
gpgcheck=0
enabled=0

[cms4all-drivers]
name=cms4all-drivers
baseurl=http://centos.cms4all.org/centos/7/drivers/
gpgcheck=0
enabled=0


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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[Liam O'Toole]

On 2016-05-10, Valeri Galtsev
 wrote:
>
> 1. Debian (and clones): you keep the components of the system pretty
> much on the level of latest release of each of components. Therefore
> "upgrade" to new release of the system is pretty close to just a
> regular routine update.

You are describing Debian sid/unstable, which is contunuously updated,
and where there are no releases in the usual sense of the word. Debian
stable releases are a different matter, and correspond very closely to
major releases of RHEL/CentOS. There is always an upgrade path between
consecutive releases of Debian stable.

-- 

Liam


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

Re: [CentOS] CentOS 6 as DNS-Server

[Александр Кириллов]

if a host has IPv4 only or IPv6 only this works fine, but when a host
has both - DualStack
somethimes it works sometimes only one - can be IPv4 or can be IPv6 
works;

and in /var/log/messages  I get something like

May 10 18:51:30 dnssrvr named[2526]: client 192.168.1.2#38618: view
wkst: updating zone 'ddns.local/IN': update unsuccessful:
WIN7HOST.ddns.local: 'name not in use' prerequisite not satisfied
(YXDOMAIN)

for several times;


Which probably means that the name for the host has already been added 
to dns with an IPv6 address or vice versa. Have a look at 
https://deepthought.isc.org/article/AA-01091/0/ISC-DHCP-support-for-Standard-DDNS.html. 
It might be relevant. I don't know. 'ddns-update-style standard' didn't 
even exist when I fiddled with this.


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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[Valeri Galtsev]

On Tue, May 10, 2016 3:57 pm, Liam O'Toole wrote:
> On 2016-05-10, Valeri Galtsev
>  wrote:
>>
>> 1. Debian (and clones): you keep the components of the system pretty
>> much on the level of latest release of each of components. Therefore
>> "upgrade" to new release of the system is pretty close to just a
>> regular routine update.
>
> You are describing Debian sid/unstable, which is contunuously updated,
> and where there are no releases in the usual sense of the word. Debian
> stable releases are a different matter, and correspond very closely to
> major releases of RHEL/CentOS. There is always an upgrade path between
> consecutive releases of Debian stable.
>

Yes, LTS, thanks Liam. Only LTS has life cycle of mere 2 years, whereas
RHEL (hence CentOS) is what, 10 years? I was pretty sure Debian does not
backport patches (of Linuxes no one except RH, as far as I know). How do
they do it with LTS? Do they just freeze major version, no matter what (it
is only 2 years the need)?

Thanks.
Valeri

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



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

Re: [CentOS] CentOS 6 as DNS-Server

[Walter H.]

On 10.05.2016 21:08, m.r...@5-cent.us wrote:

Walter H. wrote:

On 10.05.2016 18:57, Александр Кириллов wrote:

I'm also using ddns and have my zone files in
/var/named/chroot/var/named/dynamic.

are you using DDNS in DualStack (IPv4 and IPv6 together) or do you have
only DHCP or DHCPv6 and not both?
my box has both DHCP and DHCPv6; but some hosts have already a fix IPv4 
address, so only DHCPv6 is used; or some hosts are IPv4only

but if the host has no IP address at all; then this works only sometimes;
and with both IPv4 and IPv6 the same domain is used  ddns.local

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

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[Valeri Galtsev]

On Tue, May 10, 2016 2:19 am, Johnny Hughes wrote:
> On 05/10/2016 02:08 AM, Venkateswara Rao Dokku wrote:
>> Hi,
>>
>> I would like to know whether the valid upgrade path will be present from
>> CentOS 7 to future versions like we get for Ubuntu or some other
>> operating
>> systems.
>>
>> Right now, I am sure that we do not have proper update path in CentOS to
>> move from one version to another.
>>
>
> If you mean upgrade to all CentOS-7 point releases, yes (from source
> code for RHEL-7.0 to RHEL-7.1, to RHEL-7.2).  If you mean from CentOS-7
> to CentOS-8, there is no way to know.  There is no RHEL-8 to look at.
>
> Red Hat has source code for preupgrade-assistant and
> redhat-upgrade-tool.  That is created for inplace upgrades from one
> major version to another.  Currently those tools are community and
> maintained and they are several updates behind because currently no one
> in the community has stepped up to maintain them.
>
> But, CentOS-7 has an EOL of June 30, 2024 .. so there is security
> updates for 8 more years.

I would add to nice Johnny's explanation one more thing.

"Other systems" you mention I bet are Debian and its clones (Ubuntu being
one of them). These systems have different update philosophy than that of
RedHat Enterprise Linux (and hence what CentOS is, which is derived from
RHEL). Namely, these "other systems" do constant micro-upgrades of
components installed on the system to latest release, whenever new release
of given piece of software happens. To the contrary, RHEL mostly backports
important security fixes to a version that was included in original system
release (but occasionally does make upgrades). Hence the differences:

1. Debian (and clones): you keep the components of the system pretty much
on the level of latest release of each of components. Therefore "upgrade"
to new release of the system is pretty close to just a regular routine
update. This apparent advantage comes with a disadvantage, namely: every
update has a potential to break something on your machine, as new release
may have different internals, then you will need to work on migration to
them, and this can come as a surprise with any of routine updates.

2. RHEL (and derivatives): you do routine updates, and all is guaranteed
to keep working as it did when you originally configured your machine.
This is great advantage for those of us who prefer stability. It comes at
some price, namely: more work of the side of RedHat team (backporting
important patches), and you have to live with slightly outdated
components. The last can be seen differently, as slightly outdated is the
same as being used by many, so all trouble in them are already discovered
and fixed. (Yes, there are upgrades occasionally, still...). Now, when you
upgrade to new system version, very many of the components go versions up,
thus the safe way to deal with them is to have everything freshly
installed, freshly configured, and then migrate your custom configurations
to this new level.

Now to comment of what one can choose, I would say about Debian (and
clones) what I would say about Fedora, which definitely is "bleeding
edge". If you want "bleeding edge", be ready for some bleeding sometimes.

All in all it is your choice. If you are to maintain solid server and can
not tolerate 10 min outage in anything happen out of blue, CentOS is for
you. If you don't care about that, then Debian or one of its clones may be
more convenient for your way of system maintenance.

I hope, this helps.

Valeri


Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

[CentOS] Upgrade path from CentOS 7 to future versions

[Venkateswara Rao Dokku]

Hi,

I would like to know whether the valid upgrade path will be present from
CentOS 7 to future versions like we get for Ubuntu or some other operating
systems.

Right now, I am sure that we do not have proper update path in CentOS to
move from one version to another.

-- 
Thanks & Regards,
Venkateswara Rao Dokku.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Upgrade path from CentOS 7 to future versions

[Johnny Hughes]

On 05/10/2016 02:08 AM, Venkateswara Rao Dokku wrote:
> Hi,
> 
> I would like to know whether the valid upgrade path will be present from
> CentOS 7 to future versions like we get for Ubuntu or some other operating
> systems.
> 
> Right now, I am sure that we do not have proper update path in CentOS to
> move from one version to another.
> 

If you mean upgrade to all CentOS-7 point releases, yes (from source
code for RHEL-7.0 to RHEL-7.1, to RHEL-7.2).  If you mean from CentOS-7
to CentOS-8, there is no way to know.  There is no RHEL-8 to look at.

Red Hat has source code for preupgrade-assistant and
redhat-upgrade-tool.  That is created for inplace upgrades from one
major version to another.  Currently those tools are community and
maintained and they are several updates behind because currently no one
in the community has stepped up to maintain them.

But, CentOS-7 has an EOL of June 30, 2024 .. so there is security
updates for 8 more years.



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

Re: [CentOS] CentOS 6 as DNS-Server

[Александр Кириллов]

this seems to be relevant in chroot environments;

as I noticed when configuring the DDNS-feature, that this is a little 
bit
weired, when running in a chroot environment; I saw the recommendation 
not
to use a chroot in the man-page and removed bind-chroot and then the 
zone

updates worked perfekt;

so this file /etc/named.root.key isn't really used; or am I missing
something?


These files are included in both my /etc/named.conf and 
/usr/share/doc/bind-x.x.x/named.conf.default which I probably used as a 
template years ago. I'm no dns expert but you'd probably need these 
files when accessing root servers directly without use of forwarders.


I'm also using ddns and have my zone files in 
/var/named/chroot/var/named/dynamic.
Selinux is enabled and I don't see any additional bind-related rules in 
my local policy or 
/etc/selinux/targeted/contexts/files/file_contexts.local.


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

Re: [CentOS] weird network error

[m . roth]

John R Pierce wrote:
> a previously rock solid reliable server of mine crashed last night, the
> server was still running but eth0, a Intel 82574L using the e1000e
> driver, went down.   The server has a Supermicro X8DTE-F (dual Xeon
> X5650, yada yada).server is a drbd master, so that was the first
> thing to notice network issues.   Just a couple days ago I ran yum
> update to the latest, I do this about once a month.
>
> /var/log/messages logged...

> (prior to this was nothing but normal smbd complaining about CUPS not
> configured).
> Duplex, Flow Control: Rx/Tx
> May  9 22:52:56 sg1 kernel: e1000e: eth0 NIC Link is Down
> May  9 22:53:01 sg1 kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full
> Duplex, Flow Control: Rx/Tx
> May  9 22:55:30 sg1 kernel: e1000e: eth0 NIC Link is Down
> May  9 22:55:35 sg1 kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full
> Duplex, Flow Control: Rx/Tx

This is going to sound really stupid, but consider replacing the patch
cord. If that doesn't work... should I assume that this m/b has at least
two embedded NIC? If so, try using the other NIC.

mark "I haven't done both of those in the last few months, no"

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

[CentOS] weird network error

[John R Pierce]

a previously rock solid reliable server of mine crashed last night, the 
server was still running but eth0, a Intel 82574L using the e1000e 
driver, went down.   The server has a Supermicro X8DTE-F (dual Xeon 
X5650, yada yada).server is a drbd master, so that was the first 
thing to notice network issues.   Just a couple days ago I ran yum 
update to the latest, I do this about once a month.


/var/log/messages logged...

(prior to this was nothing but normal smbd complaining about CUPS not 
configured).


May  9 22:30:21 sg1 kernel: block drbd0: PingAck did not arrive in time.
May  9 22:30:21 sg1 kernel: block drbd0: peer( Secondary -> Unknown ) 
conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown )

May  9 22:30:21 sg1 kernel: block drbd0: asender terminated
May  9 22:30:21 sg1 kernel: block drbd0: Terminating drbd0_asender
May  9 22:30:22 sg1 kernel: block drbd0: new current UUID 
BC856D7A6F94F041:237F4033E81B62DF:1E248D699B6793A9:1E238D699B6793A9

May  9 22:30:22 sg1 kernel: block drbd0: Connection closed
May  9 22:30:22 sg1 kernel: block drbd0: conn( NetworkFailure -> 
Unconnected )

May  9 22:30:22 sg1 kernel: block drbd0: receiver terminated
May  9 22:30:22 sg1 kernel: block drbd0: Restarting drbd0_receiver
May  9 22:30:22 sg1 kernel: block drbd0: receiver (re)started
May  9 22:30:22 sg1 kernel: block drbd0: conn( Unconnected -> 
WFConnection )

May  9 22:30:34 sg1 kernel: [ cut here ]
May  9 22:30:34 sg1 kernel: WARNING: at net/sched/sch_generic.c:261 
dev_watchdog+0x26b/0x280() (Not tainted)

May  9 22:30:34 sg1 kernel: Hardware name: ISS3500
May  9 22:30:34 sg1 kernel: NETDEV WATCHDOG: eth0 (e1000e): transmit 
queue 0 timed out
May  9 22:30:34 sg1 kernel: Modules linked in: drbd(U) nfsd max6650 
coretemp adm1021 ipmi_devintf ipmi_si ipmi_msghandler nfs lockd fscache 
auth_rpcgss nfs_acl sunrpc cpufreq_ondemand acpi_cpufreq freq_table 
mperf ipv6 xfs exportfs microcode iTCO_wdt iTCO_vendor_support joydev 
serio_raw i2c_i801 i2c_core lpc_ich mfd_core e1000e(U) ptp pps_core 
ioatdma dca i7core_edac edac_core ses enclosure sg ext4 jbd2 mbcache 
sd_mod crc_t10dif ahci megaraid_sas mpt2sas scsi_transport_sas 
raid_class dm_mirror dm_region_hash dm_log dm_mod [last unloaded: 
scsi_wait_scan]
May  9 22:30:34 sg1 kernel: Pid: 0, comm: swapper Not tainted 
2.6.32-573.22.1.el6.x86_64 #1

May  9 22:30:34 sg1 kernel: Call Trace:
May  9 22:30:34 sg1 kernel:  [] ? 
warn_slowpath_common+0x91/0xe0
May  9 22:30:34 sg1 kernel: [] ? 
warn_slowpath_fmt+0x46/0x60

May  9 22:30:34 sg1 kernel: [] ? dev_watchdog+0x26b/0x280
May  9 22:30:34 sg1 kernel: [] ? insert_work+0x6d/0xb0
May  9 22:30:34 sg1 kernel: [] ? 
internal_add_timer+0xb5/0x110

May  9 22:30:34 sg1 kernel: [] ? dev_watchdog+0x0/0x280
May  9 22:30:34 sg1 kernel: [] ? 
run_timer_softirq+0x197/0x340
May  9 22:30:34 sg1 kernel: [] ? 
lapic_next_event+0x1d/0x30

May  9 22:30:34 sg1 kernel: [] ? __do_softirq+0xc1/0x1e0
May  9 22:30:34 sg1 kernel: [] ? 
tick_program_event+0x2f/0x40

May  9 22:30:34 sg1 kernel: [] ? call_softirq+0x1c/0x30
May  9 22:30:34 sg1 kernel: [] ? do_softirq+0x65/0xa0
May  9 22:30:34 sg1 kernel: [] ? irq_exit+0x85/0x90
May  9 22:30:34 sg1 kernel: [] ? 
smp_apic_timer_interrupt+0x4a/0x60
May  9 22:30:34 sg1 kernel: [] ? 
apic_timer_interrupt+0x13/0x20
May  9 22:30:34 sg1 kernel:  [] ? 
intel_idle+0xfe/0x1b0

May  9 22:30:34 sg1 kernel: [] ? intel_idle+0xe1/0x1b0
May  9 22:30:34 sg1 kernel: [] ? 
cpuidle_idle_call+0x7a/0xe0

May  9 22:30:34 sg1 kernel: [] ? cpu_idle+0xb6/0x110
May  9 22:30:34 sg1 kernel: [] ? 
start_secondary+0x2c0/0x316

May  9 22:30:34 sg1 kernel: ---[ end trace 883800817e091e53 ]---
May  9 22:30:34 sg1 kernel: e1000e :03:00.0: eth0: Reset adapter 
unexpectedly

May  9 22:30:35 sg1 abrt-dump-oops: Reported 1 kernel oopses to Abrt
May  9 22:30:35 sg1 abrtd: Directory 'oops-2016-05-09-22:30:35-8763-1' 
creation detected
May  9 22:30:38 sg1 kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: Rx/Tx

May  9 22:30:42 sg1 kernel: Bridge firewalling registered
May  9 22:31:27 sg1 kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
May  9 22:31:32 sg1 abrtd: Can't find a meaningful backtrace for hashing 
in '.'
May  9 22:31:32 sg1 abrtd: Preserving oops '.' because 
DropNotReportableOopses is '(not set)'

May  9 22:31:32 sg1 abrtd: Looking for kernel package
May  9 22:31:32 sg1 abrtd: Kernel package 
kernel-2.6.32-573.22.1.el6.x86_64 found
May  9 22:31:33 sg1 abrtd: New problem directory 
/var/spool/abrt/oops-2016-05-09-22:30:35-8763-1, processing

May  9 22:31:33 sg1 abrtd: Sending an email...
May  9 22:31:34 sg1 abrtd: Email was sent to: root@localhost
May  9 22:32:25 sg1 kernel: e1000e: eth0 NIC Link is Down
May  9 22:32:30 sg1 kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: Rx/Tx
May  9 22:34:55 sg1 kernel: e1000e :03:00.0: eth0: Reset adapter 
unexpectedly
May  9 22:34:59 sg1 kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full 

[CentOS] CentOS 6 as DNS-Server

[Walter H.]

Hello,

it has been a while since I had setup a DNS-Server with CentOS 6;
these days I added a few zones needed for DDNS; this works
but in /etc/ I found quite a strange file, I'm not sure if it was in use
at the beginning I used this system as a DNS-Server, and after several
'yum update'
not any more;

/etc/named.root.key with this content

managed-keys {
# DNSKEY for the root zone.
# Updates are published on root-dnssec-annou...@icann.org
. initial-key 257 3 8
"AwEAAagAIKlVZrpC6Ia7gEzahOR+9W29euxhJhVVLOyQbSEW0O8gcCjF
FVQUTf6v58fLjwBd0YI0EzrAcQqBGCzh/RStIoO8g0NfnfL2MTJRkxoX
bfDaUeVPQuYEhg37NZWAJQ9VnMVDxP/VHL496M/QZxkjf5/Efucp2gaD
X6RS6CXpoY68LsvPVjR0ZSwzz1apAzvN9dlzEheX7ICJBBtuA6G3LQpz
W5hOA2hzCTMjJPJ8LbqF6dsV6DoBQzgul0sGIcGOYl7OyQdXfZ57relS
Qageu+ipAdTTJ25AsRTAoub8ONGcLmqrAmRLKBP1dfwhYB4N7knNnulq
QxA+Uk1ihz0=";
};

and /etc/named.iscdlv.key with a content
identical to this: http://ftp.isc.org/isc/bind9/keys/9.8/bind.keys.v9_8

in no file neither in /etc/named.conf nor in any other file that is
included by the main config I can find a reference to /etc/named.root.key

is this file really needed or did it become obsolete?
(as seen on the URL above, /etc/named.root.key is part of
/etc/named.iscdlv.key)

Thanks,
Walter


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

Re: [CentOS] CentOS 6 as DNS-Server

[Александр Кириллов]

in no file neither in /etc/named.conf nor in any other file that is
included by the main config I can find a reference to 
/etc/named.root.key


is this file really needed or did it become obsolete?
(as seen on the URL above, /etc/named.root.key is part of
/etc/named.iscdlv.key)


# cat /etc/rc.d/init.d/named
...
ROOTDIR_MOUNT='/etc/named /etc/pki/dnssec-keys /var/named 
/etc/named.conf
/etc/named.dnssec.keys /etc/named.rfc1912.zones /etc/rndc.conf 
/etc/rndc.key

/usr/lib64/bind /usr/lib/bind /etc/named.iscdlv.key /etc/named.root.key'

mount_chroot_conf()
...

# rpm -qf /etc/named.root.key /etc/named.iscdlv.key
bind-9.8.2-0.37.rc1.el6_7.7.x86_64
bind-9.8.2-0.37.rc1.el6_7.7.x86_64

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

[CentOS] CentOS-announce Digest, Vol 135, Issue 4

[centos-announce-request]

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CESA-2016:0723 Critical CentOS 6  java-1.6.0-openjdk Security
  Update (Johnny Hughes)
   2. CESA-2016:0723 Critical CentOS 5  java-1.6.0-openjdk Security
  Update (Johnny Hughes)
   3. CESA-2016:0723 Critical CentOS 7  java-1.6.0-openjdk Security
  Update (Johnny Hughes)
   4. CESA-2016:0724 Important CentOS 7 qemu-kvmSecurity Update
  (Johnny Hughes)
   5. CESA-2016:0726 Important CentOS 6 ImageMagick Security Update
  (Johnny Hughes)
   6. CESA-2016:0726 Important CentOS 7 ImageMagick Security Update
  (Johnny Hughes)


--

Message: 1
Date: Mon, 9 May 2016 15:40:26 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2016:0723 Critical CentOS 6
java-1.6.0-openjdk Security Update
Message-ID: <20160509154026.ga17...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2016:0723 Critical

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0723.html

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

i386:
0c6fe06779a1d4d859ebdb30ed512fd057a502fb78449e4955e8e2414868159a  
java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6_7.i686.rpm
0c8ac26c02b3543e4198b1da0879b7102d4f85e4ba8dc075631d056908a7c262  
java-1.6.0-openjdk-demo-1.6.0.39-1.13.11.0.el6_7.i686.rpm
2e4b7a98603e139a0b56013225b59a73c82084648b43e5a46e89eaaa342cb276  
java-1.6.0-openjdk-devel-1.6.0.39-1.13.11.0.el6_7.i686.rpm
dedfe6741e0c5c613de3262d2f0ed8a54ddc9e73ae655a454810a962cf8e4511  
java-1.6.0-openjdk-javadoc-1.6.0.39-1.13.11.0.el6_7.i686.rpm
9d639666508200cecd87544bd5d5423bc2521e9ff5fe9144eaa3a347e08203f9  
java-1.6.0-openjdk-src-1.6.0.39-1.13.11.0.el6_7.i686.rpm

x86_64:
3b44a05ecc8050d3b820ea9b7dd994fe2c4a130566a8fb9899091a62ecac47ee  
java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6_7.x86_64.rpm
93b4ad4e1f2c8ea60df8d051d00e2f8d1ecbf564bd61433461ea951ae4a61ee8  
java-1.6.0-openjdk-demo-1.6.0.39-1.13.11.0.el6_7.x86_64.rpm
c1b3018264498d8473fd72d9ef40508d6a50b028d515cd05a09b1f6b32902e03  
java-1.6.0-openjdk-devel-1.6.0.39-1.13.11.0.el6_7.x86_64.rpm
06fb01d701b208562762f42ed91a377b647f5299b0433d0a9296491e49078959  
java-1.6.0-openjdk-javadoc-1.6.0.39-1.13.11.0.el6_7.x86_64.rpm
e69695441facf02fcc2ed64c7dbc85c0b26dc202b4a63a01905b4ff4d4cd0c1a  
java-1.6.0-openjdk-src-1.6.0.39-1.13.11.0.el6_7.x86_64.rpm

Source:
994496b319bb30306845bcc36c3657c602a01e0dab2cb029dec8b6d6528b3d56  
java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el6_7.src.rpm



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



--

Message: 2
Date: Mon, 9 May 2016 15:12:42 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2016:0723 Critical CentOS 5
java-1.6.0-openjdk Security Update
Message-ID: <20160509151242.ga6...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2016:0723 Critical

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0723.html

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

i386:
36e25b70ced8e7761fb2c8a54780bbe65df642bb06e29ff366e48cfe4e18ecb0  
java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el5_11.i386.rpm
ca430885b7b50d5ee059e078dc87b356b4be076502a5a14a9700c7252ac369df  
java-1.6.0-openjdk-demo-1.6.0.39-1.13.11.0.el5_11.i386.rpm
d0b6acf2e1a3e8e8fa4f304058aeff951ee5012e92c526b0443a3faa256640f1  
java-1.6.0-openjdk-devel-1.6.0.39-1.13.11.0.el5_11.i386.rpm
c0f638d1d21ed240a1db1f3245e98c79d719a6f37be977c72fe6f8f45cec02a0  
java-1.6.0-openjdk-javadoc-1.6.0.39-1.13.11.0.el5_11.i386.rpm
3abc1bf9db9f917ebfff5bcece0794e48eafa977b5ef009a94a34abe646a1e29  
java-1.6.0-openjdk-src-1.6.0.39-1.13.11.0.el5_11.i386.rpm

x86_64:
baad834955029d7ea3829e3ea1f5b3ecf9a2e56b71cbb8d6f972dcbadcf960ee  
java-1.6.0-openjdk-1.6.0.39-1.13.11.0.el5_11.x86_64.rpm
d717997de759ef40154352f200ca1bb593fb031217b326b738f77004b32bf47d  
java-1.6.0-openjdk-demo-1.6.0.39-1.13.11.0.el5_11.x86_64.rpm
0cc759a6a4ca4aad7614b825ffccde9a02784ac7537ad54f7a44490cb44f5382  
java-1.6.0-openjdk-devel-1.6.0.39-1.13.11.0.el5_11.x86_64.rpm
d8c6d345a2c73c7d055f6833244599b48d932407cb748151ac5a9b52f7a071b1  

[CentOS-announce] CEBA-2016:1008 CentOS 5 sos BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2016:1008 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1008.html

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

i386:
a475b5d668e11fdedb198fce3b0c7acb44fc6792cfe2b476582827c10235bfde  
sos-1.7-9.74.el5.centos.noarch.rpm

x86_64:
a475b5d668e11fdedb198fce3b0c7acb44fc6792cfe2b476582827c10235bfde  
sos-1.7-9.74.el5.centos.noarch.rpm

Source:
a241963fe6488483dc6c0f6bd811a1a6e7eb9ab44683430341aa439855fa52be  
sos-1.7-9.74.el5.centos.src.rpm



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

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

[CentOS-announce] CEBA-2016:1009 CentOS 5 firefox BugFix Update

[Johnny Hughes]

CentOS Errata and Bugfix Advisory 2016:1009 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1009.html

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

i386:
8a1b5a12cc396b85b2bb8022acc81358366d4a24b6d819ad887478f4b3aad972  
firefox-45.1.1-1.el5.centos.i386.rpm

x86_64:
8a1b5a12cc396b85b2bb8022acc81358366d4a24b6d819ad887478f4b3aad972  
firefox-45.1.1-1.el5.centos.i386.rpm
7cc5b5f1ba36683f7f8b2c04ffaf7151aec3212356d708a852c531b42b6dcf3a  
firefox-45.1.1-1.el5.centos.x86_64.rpm

Source:
2d374e8d6925993a0c43346ab99b73ab7265e334326237318249adacbdade2c4  
firefox-45.1.1-1.el5.centos.src.rpm



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

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