CentOS Errata and Security Advisory 2015:1980 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1980.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
On 11/4/2015 11:36 AM, Boris Epstein wrote:
Absolutely, I see your point. This was the starting point - you add the
device on the ESXi server, you reboot the VM, the VM sees the device, no
problem. Now, I ask - do I have to reboot the VM? Logically I hope there
ought to be a way for me not to
CentOS Errata and Security Advisory 2015:1980 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1980.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
> -Original Message-
> From: m.r...@5-cent.us [mailto:m.r...@5-cent.us]
> Sent: Tuesday, November 03, 2015 11:58 AM
> To: CentOS mailing list
> Subject: Re: [CentOS] Centos 7, ATI card, 30" monitor
>
> John R Pierce wrote:
> > On 11/3/2015 8:11 AM, John R Pierce wrote:
> >> On 11/3/2015
Denniston, Todd A CIV NAVSURFWARCENDIV Crane wrote:
>> From: m.r...@5-cent.us [mailto:m.r...@5-cent.us]
>>
>> John R Pierce wrote:
>> > On 11/3/2015 8:11 AM, John R Pierce wrote:
>> >> On 11/3/2015 7:33 AM, m.r...@5-cent.us wrote:
>> >>> Well, I got my user back to being able to use his system,
CentOS Errata and Security Advisory 2015:1982 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1982.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
On 11/4/2015 12:52 PM, Boris Epstein wrote:
I don't get this for some reason... not even sure why. ESXi's default
behaviour seems to be to allow hotplug, that does not seem to be
deactivated. I am just not sure. Wonder if this could be the Centos 7 vs 6
- perhaps that is what I ought to test
>>
> vmware esxi 5.5.0 (free, using vsphere client to manage), vm is minimal
> centos 7 64bit. I added a 16gb vdisk and immediately see this in dmesg...
>
> [155484.386792] vmw_pvscsi: msg type: 0x0 - MSG RING: 1/0 (5)
> [155484.386796] vmw_pvscsi: msg: device added at scsi0:1:0
>
Aun no consigo conectar mis equipos :(
Estoy terminando, reiniciando y finalmente corriendo ipsec verify y me
muestra lo siguiente.
*shell# /etc/init.d/openvpn restart*
Apagando openvpn: [ OK ]
Iniciando openvpn: [ OK ]
*shell#
Hey Billings,
Thanks for the response.
Just a quick question, you are talking about initramfs or initrd ?? My
/boot dosent seem to have a initrd.img rather does seem to have a
initramfs..
On Wed, Nov 4, 2015 at 9:22 PM, Jonathan Billings
wrote:
> On Tue, Nov 03, 2015 at
Hi Billing and others,
Thanks to your help, learnt a lot about plymouth and yay, it actually works
:-)
Thanks to all the help and the fast response :-)
On Thu, Nov 5, 2015 at 10:23 AM, Ramaseshan S
wrote:
> Hey Billings,
> Thanks for the response.
> Just a quick
On Wed, Nov 4, 2015 at 1:57 PM, wrote:
> Boris Epstein wrote:
> >>
> >> My turn for a dumb question: from not paying a lot of attention to this
> >> thread, the answer isn't clear to me: has the *host* recognized the
> >> disk? If not, the guest's not going to see it.
> >
> >
Am 04.11.2015 um 11:22 schrieb Andrew Holway:
The server in question is a Centos 7 based FreeIPA server, OpenVPN
concentrator and DNS server.
Can have been a DNS amplification attack.
https://www.us-cert.gov/ncas/alerts/TA13-088A
On 11/04/2015 09:10 AM, Bowie Bailey wrote:
If all of the routers are providing access to the same network, you
can set up the same SSID, wifi password, and security type for all the
routers and the clients should seamlessly switch between them as they
move around.
As a point of
Jonathan Billings wrote:
> On Wed, Nov 04, 2015 at 12:59:14PM -0500, m.r...@5-cent.us wrote:
>> The answer is that the large exported filesystem is a very large XFS...
>> and at least through CentOS 6, upstream has *never* fixed an NFS bug
>> that I find, googling, being complained about in '09:
Boris Epstein wrote:
>>
>> My turn for a dumb question: from not paying a lot of attention to this
>> thread, the answer isn't clear to me: has the *host* recognized the
>> disk? If not, the guest's not going to see it.
>
> IMO your question is not dumb at all. Unfortunately, I don't have an
>
Valeri Galtsev wrote:
> On Wed, November 4, 2015 11:59 am, m.r...@5-cent.us wrote:
>>
>> The answer is that the large exported filesystem is a very large XFS...
>> and at least through CentOS 6, upstream has *never* fixed an NFS bug
>> that I find, googling, being complained about in '09: it gags
On 11/4/2015 9:59 AM, m.r...@5-cent.us wrote:
*sigh*
The answer is that the large exported filesystem is a very large XFS...
and at least through CentOS 6, upstream has*never* fixed an NFS bug that
I find, googling, being complained about in '09: it gags on inodes > 32bit
(not sure if that's
Can I have two WiFi routers on the same LAN
on my CentOS server?
--
Timothy Murphy
gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Thoughts please?
Thanks,
- Mike
On Mon, Nov 2, 2015 at 2:40 PM, Mike - st257 wrote:
> Hello List,
>
> After demystifying the cause for my /sbin/ifup-local not being executed by
> network scripts for an Ethernet interface (don't let NetworkManager control
> it or
Richard Zimmerman wrote:
> I've got a 3 building network...
>
> Buildings 1/2 between then have 3 wireless routers all pointed to one
> CentOS server.
>
> The 3rd building across the WAN has 3 wireless routers all into one
> server...
>
> In my case They are for local LAN access so they are
Hi Boris,
Just rescan the scsi host.
#scsi-rescan #if you have sg3_utils package
#lsscsi
Or
#echo "- - -" > /sys/class/scsi_host/host[n]/scan
Julius
> On Nov 4, 2015, at 15:31, Boris Epstein wrote:
>
> Hello all,
>
> Is there a way to recognize a hot-plugged disk (i.e.,
Hello Julius,
Thanks - but it doesn't seem to work.
I installed sg3_utils and ran
#scsi-rescan
but that seemed to have done nothing for some reason.
Cheers,
Boris.
On Wed, Nov 4, 2015 at 10:12 AM, Tnjulius wrote:
> Hi Boris,
> Just rescan the scsi host.
> #scsi-rescan
Hello all,
Is there a way to recognize a hot-plugged disk (i.e., to get the system to
recognize it and build the appropriate /dev/sd* device for the new device)
without a reboot?
Thanks.
Boris.
___
CentOS mailing list
CentOS@centos.org
On Wed, Nov 4, 2015 at 1:18 PM, Jens Larsson wrote:
> Hi,
>
> There was new packages (4.4.3-3) released on Oct 29, but they don't
> address the CVE-2015-7835 problems. Does anyone have news about a
> rebuild with this fix applied? Or should we make our own build?
Actually they
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf Of
Timothy Murphy
Sent: Wednesday, November 04, 2015 9:07 AM
To: centos@centos.org
Subject: Re: [CentOS] Two WiFi routers
Timothy Murphy wrote:
> Thanks for your response.
> Do you have them
Have you a public IP on the server? Take a loot at your DNS
configuration it could be an open resolver
http://openresolver.com/
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
The question is quite vague but the answer is yes.
I've got a 3 building network...
Buildings 1/2 between then have 3 wireless routers all pointed to one CentOS
server.
The 3rd building across the WAN has 3 wireless routers all into one server...
In my case They are for local LAN access so
Did you run basic checks like rkhunter and so on?
Is there password login enabled or only public key on ssh service.
Weak passwords on ssh is usually primary reason on system compromise.
Eero
4.11.2015 12.23 ip. "Andrew Holway" kirjoitti:
> Hi,
>
> One of our AWS
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
Hi,
There was new packages (4.4.3-3) released on Oct 29, but they don't
address the CVE-2015-7835 problems. Does anyone have news about a
rebuild with this fix applied? Or should we make our own build?
/jens
___
CentOS-virt mailing list
On 11/04/2015 10:27 AM, Mauricio Tavares wrote:
> On Wed, Nov 4, 2015 at 10:22 AM, Boris Epstein wrote:
>> Hello Julius,
>>
>> Thanks - but it doesn't seem to work.
>>
>> I installed sg3_utils and ran
>> #scsi-rescan
>>
>> but that seemed to have done nothing for some
On Wed, Nov 4, 2015 at 11:03 AM, Jonathan Billings
wrote:
> On Wed, Nov 04, 2015 at 05:39:59PM +0200, Eero Volotinen wrote:
> > I think, this is possible with scsi disks
> >
> >
> http://www.cyberciti.biz/tips/vmware-add-a-new-hard-disk-without-rebooting-guest.html
>
> While
>> There was new packages (4.4.3-3) released on Oct 29, but they don't
>> address the CVE-2015-7835 problems. Does anyone have news about a
>> rebuild with this fix applied? Or should we make our own build?
>
> Actually they do includu CVE-2015-7835 (aka XSA-148) -- I just made a
> mistake when I
On Wed, Nov 4, 2015 at 10:22 AM, Boris Epstein wrote:
> Hello Julius,
>
> Thanks - but it doesn't seem to work.
>
> I installed sg3_utils and ran
> #scsi-rescan
>
> but that seemed to have done nothing for some reason.
>
Dumb question: did dmesg even bother to notice
Hi,
I think, this is possible with scsi disks
http://www.cyberciti.biz/tips/vmware-add-a-new-hard-disk-without-rebooting-guest.html
Eero
4.11.2015 4.32 ip. "Boris Epstein" kirjoitti:
> Hello all,
>
> Is there a way to recognize a hot-plugged disk (i.e., to get the system
CentOS Errata and Security Advisory 2015:1981 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1981.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
On Tue, Nov 03, 2015 at 10:36:50AM +0530, Ramaseshan S wrote:
> Sorry didnt know that
> Here is an attached online link.
>
> http://tinypic.com/r/33pdcw6/9
Thats 'plymouth', specifically the text theme. Looking at the
plymouth source, it uses /etc/system-release by default (and it looks
for
>
>
>
> was the controller you added the virtual disk to an IDE or scsi controller?
>
> --
> public gpg key id: 1362BA1A
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
It was a SCSI controller.
On 11/04/2015 11:05 AM, Boris Epstein wrote:
> On Wed, Nov 4, 2015 at 11:03 AM, Jonathan Billings
> wrote:
>
>> On Wed, Nov 04, 2015 at 05:39:59PM +0200, Eero Volotinen wrote:
>>> I think, this is possible with scsi disks
>>>
>>>
>>
On Wed, Nov 4, 2015 at 11:29 AM, Eero Volotinen
wrote:
> It should work fine. What esxi version you are using?
>
> Eero
> 4.11.2015 6.27 ip. "Boris Epstein" kirjoitti:
>
>
Eero,
I know. It is EXSi 5.5
Thanks.
Boris.
Zep,
Thanks - nothing insulting about asking questions.
I did run this command as root as I would never run stuff like this as any
other user (or, perhaps, I'd use sudo if so forced).
dmesg did not seem to detect the device addition, no.
Cheers,
Boris.
On Wed, Nov 4, 2015 at 10:32 AM, zep
On Wed, Nov 04, 2015 at 05:39:59PM +0200, Eero Volotinen wrote:
> I think, this is possible with scsi disks
>
> http://www.cyberciti.biz/tips/vmware-add-a-new-hard-disk-without-rebooting-guest.html
While I believe that this URL has technically correct advice, it's
basically doing a subset of the
It should work fine. What esxi version you are using?
Eero
4.11.2015 6.27 ip. "Boris Epstein" kirjoitti:
> >
> >
> >
> > was the controller you added the virtual disk to an IDE or scsi
> controller?
> >
> > --
> > public gpg key id: 1362BA1A
> >
> >
CentOS Errata and Security Advisory 2015:1981 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1981.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
@Boris:
If you have CentOS 6 + ESXi5.5, it should normally work fine.
Have you retry the operation by adding another vDisk? monitor
/var/log/messages
Julius
2015-11-04 17:34 GMT+01:00 Boris Epstein :
> On Wed, Nov 4, 2015 at 11:29 AM, Eero Volotinen
On 11/04/2015 05:16 AM, Mike - st257 wrote:
But when I try to remove it, I'm either trying to do something_actually_
>not supported or I don't have the proper syntax to accomplish what I want.
>~]# ip link delete dev eno1 alias "hit"
>RTNETLINK answers: Operation not supported
The man page for
CentOS Errata and Security Advisory 2015:1981 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1981.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
Am 04.11.2015 um 17:26 schrieb Boris Epstein:
It was a SCSI controller.
It usually works very nice here,
Have you added only the disk or by accident another scsi controller?
This happens (you probably know) if you select another bus while
creating the disc.
VG Rainer
CentOS Errata and Security Advisory 2015:1982 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1982.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
Richard Zimmerman wrote:
>> Do you have them on different channels?
>
> YES, definitely If you have the room in the spectrum, ch1, skip2, ch3,
> skip 4, ch5, etc... I've actually have mine set with two empty channels
> between them as the 3rd building is a machine / fabrication shop with
On 11/4/2015 11:45 AM, Timothy Murphy wrote:
Richard Zimmerman wrote:
Do you have them on different channels?
YES, definitely If you have the room in the spectrum, ch1, skip2, ch3,
skip 4, ch5, etc... I've actually have mine set with two empty channels
between them as the 3rd building is
On Wed, November 4, 2015 4:22 am, Andrew Holway wrote:
> Hi,
>
> One of our AWS machines was used in an DOS attack last night and I am
> looking for possible attack vectors.
Is it AWS as in Amazon Web Services?
> AWS tells me it was sending UDP port
> 0
> traffic to a cloudflare address.
CentOS Errata and Security Advisory 2015:1981 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1981.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
CentOS Errata and Security Advisory 2015:1981 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1981.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
CentOS Errata and Security Advisory 2015:1982 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1982.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
On 11/4/2015 6:07 AM, Timothy Murphy wrote:
Thanks for your response.
Do you have them on different channels?
If you have an android device with wifi (tablet, phone), install the
freeware app "WiFi Analyzer", and put it in the display mode where it
shows channels across the bottom and signal
*sigh*
The answer is that the large exported filesystem is a very large XFS...
and at least through CentOS 6, upstream has *never* fixed an NFS bug that
I find, googling, being complained about in '09: it gags on inodes > 32bit
(not sure if that's signed, or unsigned, but).
The answer was to
>
>
> It usually works very nice here,
> Have you added only the disk or by accident another scsi controller?
> This happens (you probably know) if you select another bus while creating
> the disc.
>
> VG Rainer
>
> ___
> CentOS mailing list
>
Boris Epstein wrote:
> Hello Julius,
>
> Thanks - but it doesn't seem to work.
>
> I installed sg3_utils and ran
> #scsi-rescan
>
> but that seemed to have done nothing for some reason.
>
My turn for a dumb question: from not paying a lot of attention to this
thread, the answer isn't clear to me:
On Wed, November 4, 2015 11:59 am, m.r...@5-cent.us wrote:
> *sigh*
>
> The answer is that the large exported filesystem is a very large XFS...
> and at least through CentOS 6, upstream has *never* fixed an NFS bug that
> I find, googling, being complained about in '09: it gags on inodes > 32bit
>
>
> My turn for a dumb question: from not paying a lot of attention to this
> thread, the answer isn't clear to me: has the *host* recognized the disk?
> If not, the guest's not going to see it.
>
> mark
>
>
>
> ___
> CentOS mailing list
>
CentOS Errata and Security Advisory 2015:1981 Critical
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1981.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
On 11/04/2015 06:21 AM, Richard Zimmerman wrote:
If you have the room in the spectrum, ch1, skip2, ch3, skip 4, ch5, etc
Those channels are too close. They still overlap and cause
interference. Effectively, the only useful channels for 2.4Ghz WiFi are
1, 6, and 11.
On Wed, Nov 04, 2015 at 12:59:14PM -0500, m.r...@5-cent.us wrote:
> The answer is that the large exported filesystem is a very large XFS...
> and at least through CentOS 6, upstream has *never* fixed an NFS bug that
> I find, googling, being complained about in '09: it gags on inodes > 32bit
>
Le 03/11/2015 00:49, Jean-Marc LIGER a écrit :
Le 02/11/2015 18:28, Johnny Hughes a écrit :
On 10/31/2015 04:34 PM, Jean-Marc LIGER wrote:
Hi Lucian,
It seems to be upstream libvirt-1.2.15-2 with options with_xen and
with_libxl enabled.
http://cbs.centos.org/koji/buildinfo?buildID=1348
Hi,
One of our AWS machines was used in an DOS attack last night and I am
looking for possible attack vectors. AWS tells me it was sending UDP port 0
traffic to a cloudflare address.
This instance had an incorrectly configured AWS security group exposing all
ports.
The server in question is a
CentOS Errata and Security Advisory 2015:1978 Moderate
Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1978.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
On Tue, Nov 03, 2015 at 02:06:18PM -0600, Johnny Hughes wrote:
> On 11/03/2015 08:53 AM, Lars Kurth wrote:
> > Hi all,
> >
> > I wanted to let you know that I feel I need to step down as leader of the
> > Virtualisation SIG. When I originally was approached by KB to do this, it
> > was always
On 11/04/2015 04:31 AM, Jean-Marc LIGER wrote:
>
>
> Le 03/11/2015 00:49, Jean-Marc LIGER a écrit :
>>
>> Le 02/11/2015 18:28, Johnny Hughes a écrit :
>>> On 10/31/2015 04:34 PM, Jean-Marc LIGER wrote:
Hi Lucian,
It seems to be upstream libvirt-1.2.15-2 with options with_xen and
70 matches
Mail list logo