similar to: CESA-2014:2008 Important CentOS 5 kernel Security Update

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Quoting Ulf Volmer <u.volmer at u-v.de>: > On 12/18/2014 08:11 PM, Dave Stevens wrote: >> ran routine updates on the lernel this morning and got this: >> >> WARNING: No module xenblk found for kernel 2.6.18-400.1.1.el5, >> continuing anyway > > i'm not sure that i can help you, i have currently no centos5 vm on xen. > > But i guess the warning is

On 12/20/2014 07:02 AM, Dave Stevens wrote: > $ rpm -q kernel kernel-xen > kernel-2.6.18-371.11.1.el5 > kernel-2.6.18-371.12.1.el5 > kernel-2.6.18-398.el5 > kernel-2.6.18-400.el5 > kernel-2.6.18-400.1.1.el5 > kernel-xen-2.6.18-371.11.1.el5 > kernel-xen-2.6.18-371.12.1.el5 > kernel-xen-2.6.18-398.el5 > kernel-xen-2.6.18-400.el5 > kernel-xen-2.6.18-400.1.1.el5 It is

On 12/18/2014 08:11 PM, Dave Stevens wrote: > ran routine updates on the lernel this morning and got this: > > WARNING: No module xenblk found for kernel 2.6.18-400.1.1.el5, > continuing anyway i'm not sure that i can help you, i have currently no centos5 vm on xen. But i guess the warning is from the normal, not xen enabled kernel. Does /boot/vmlinuz-2.6.18-400.1.1.el5xen

On 12/23/2014 11:11 PM, Dave Stevens wrote: > Quoting Ulf Volmer <u.volmer at u-v.de>: > >> On 12/18/2014 08:11 PM, Dave Stevens wrote: >>> ran routine updates on the lernel this morning and got this: >>> >>> WARNING: No module xenblk found for kernel 2.6.18-400.1.1.el5, >>> continuing anyway >> >> i'm not sure that i can help

ran routine updates on the lernel this morning and got this: WARNING: No module xenblk found for kernel 2.6.18-400.1.1.el5, continuing anyway The only references I can find are a year or so old. Anyone able to comment? or refer me? Have not rebooted. uname -a Linux bulkley.bvserver.ca 2.6.18-400.el5xen #1 SMP Thu Dec 4 13:29:23 EST 2014 x86_64 x86_64 x86_64 GNU/Linux Thanks, Dave --

On 03/16/2015 08:58 AM, Pasi K?rkk?inen wrote: > On Sun, Mar 15, 2015 at 07:52:42PM -0700, Sarah Newman wrote: >>> I'd really prefer to work from 'virsh' than from hand-writing xl >>> configuration files.When I last did this sort of thing, I worked from >>> a PXE environment that I controlled and could reserve DHCP settings >>> based on MAC

On Mon, Mar 16, 2015 at 10:32 PM, Nico Kadel-Garcia <nkadel at gmail.com> wrote: > On Mon, Mar 16, 2015 at 4:02 AM, Manuel Wolfshant > <wolfy at nobugconsulting.ro> wrote: > > > Quote from an actual installation: > > > > [root at xenh4 ~]# history| grep virt > > virt-install -n dhcpdns -p -r 1024 --os-type=linux --vnc -f > >

On Mon, Mar 16, 2015 at 4:02 AM, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > Quote from an actual installation: > > [root at xenh4 ~]# history| grep virt > virt-install -n dhcpdns -p -r 1024 --os-type=linux --vnc -f > /var/lib/xen/images/dhcpdns -s 2 -l > http://192.168.50.40/mrepo/centos6-i386/disc1 -x >

Hi at all, there is a bug in in acl_defaults_from_inbox option: if you define it with ANY value ('yes', 'no', 'whatyouwant', 'xxx') it acts like the value is ALWAYS 'yes', and Dovecot enable it; the only way to disable it, is comment it or delete from configuration file. With 'acl_defaults_from_inbox = no', or 'acl_defaults_from_inbox =

Hi at all, I have a problem with ACL; I want to share INBOX and Sent folder to an other user, but when I configure ACL on INBOX, all folders are shared (Sent, Junk, Draft, Trash, etc) # doveadm acl get -u janedoe INBOX ID Global Rights user=johndoe expunge insert lookup post read write write-deleted write-seen # doveadm acl get -u janedoe Sent ID Global Rights

On Sun, Mar 15, 2015 at 07:52:42PM -0700, Sarah Newman wrote: > > > > I'd really prefer to work from 'virsh' than from hand-writing xl > > configuration files.When I last did this sort of thing, I worked from > > a PXE environment that I controlled and could reserve DHCP settings > > based on MAC addresses, and tune PXE to boot from disk by default but