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:
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:
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
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
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.
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
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
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
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
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
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:
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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,
30 matches
Mail list logo