similar to: CESA-2016:2047 Important CentOS 7 kernel Security Update

Displaying 13 results from an estimated 13 matches similar to: "CESA-2016:2047 Important CentOS 7 kernel Security Update"

2016 Oct 12
0
CentOS-announce Digest, Vol 140, Issue 5
Send CentOS-announce mailing list submissions to centos-announce at 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-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2016 Oct 30
3
Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel
I have something very strange that occurred. After updating the kernel on my host CentOS 7 Dell 2950iii I have found that one of my CentOS 7 guest VMs will no longer boot... it just stops at the grub prompt (a second VM functions just fine). I have no idea why this problem occurred and have been unable to fix it. On google I have found several suggestions as to how to repair grub but so far
2016 Oct 30
0
Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel
A bit hard to say. Try chrooting into environment and rebuilding initrd? -- Eero 2016-10-30 22:53 GMT+02:00 Paul R. Ganci <ganci at nurdog.com>: > On 10/30/2016 12:26 PM, Paul R. Ganci wrote: > >> <snip>I am thinking of putting the CentOS iso out and then booting the VM >> into it just to poke around the file system. Otherwise my other option is >> to just
2016 Oct 30
2
Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel
On 10/30/2016 12:26 PM, Paul R. Ganci wrote: > <snip>I am thinking of putting the CentOS iso out and then booting the > VM into it just to poke around the file system. Otherwise my other > option is to just clone a twin VM on another server and then just > change the networking IPs/hostname. Anybody have any other ideas as to > how to debug this problem? So I booted off
2016 Oct 30
2
Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel
so, Just chroot to mountpoint: http://www.cyberciti.biz/faq/unix-linux-chroot-command-examples-usage-syntax/ chroot /mounted/path /bin/bash and then .. mkinitrd (see man page for documentation) 2016-10-30 22:57 GMT+02:00 Eero Volotinen <eero.volotinen at iki.fi>: > A bit hard to say. Try chrooting into environment and rebuilding initrd? > > -- > Eero > > 2016-10-30
2016 Dec 10
3
kmod-nvidia problems
Hi List, I use the kmod-nvidia package on my CentOS workstations. Always this has "just worked". Doing a yum update this morning I now get this: 09:15:28 : ERROR: Package: kmod-nvidia-367.57-2.el7.elrepo.x86_64 (elrepo) Requires: kernel(drm_atomic_helper_plane_reset) = 0xabd4c98d Installed: kernel-3.10.0-327.28.2.el7.x86_64 (@updates)
2016 Oct 30
3
Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel
Any error in your host logs? On Sunday, 30 October 2016, Steven Tardy <sjt5atra at gmail.com> wrote: > > > On Oct 30, 2016, at 3:27 AM, Paul R. Ganci <ganci at nurdog.com > <javascript:;>> wrote: > > > > grub> set root=(hd0,msdos2) > > grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 > root=(hd0,msdos2)/ > > grub> initrd
2016 Oct 24
0
Disk near failure
Il 21/10/2016 17:20, m.roth at 5-cent.us ha scritto: > John R Pierce wrote: >> On 10/21/2016 2:03 AM, Alessandro Baggi wrote: >>> >>> My ssds are failing? >> >> SSD's wear out based on writes per block. they distribute those >> writes, but once each block has been written X number of times, they are >> no longer reliable. >> >>
2016 Oct 30
0
Cannot boot CentOS 7 VM after updating Host CentOS 7 Kernel
> On Oct 30, 2016, at 3:27 AM, Paul R. Ganci <ganci at nurdog.com> wrote: > > grub> set root=(hd0,msdos2) > grub> linux (hd0,1)/vmlinuz-3.10.0-327.36.2.el7.x86_64 root=(hd0,msdos2)/ > grub> initrd initrd-plymouth.img > grub> boot Try the initrd matching the kernel?
2012 Nov 05
2
[Bug 2047] New: Definition of Sophie Germain primes is wrong in manual moduli.5
https://bugzilla.mindrot.org/show_bug.cgi?id=2047 Priority: P5 Bug ID: 2047 Assignee: unassigned-bugs at mindrot.org Summary: Definition of Sophie Germain primes is wrong in manual moduli.5 Severity: normal Classification: Unclassified OS: Linux Reporter: plautrba at redhat.com
2002 Mar 13
1
"max disk size = 2047" by share
We regularly boot ghost from a special DOS floppy to upload/backup a disk image to a samba server from our important servers. Currently, in our smb.conf we have to specify "max disk size = 2047", because if we don't, ghost complains that there is not enough room to store the backup image. Not enough room, that is, with over 40GB free. Anyway, it's an old DOS FAT 16 limitation I
1999 Apr 06
1
SAMBA digest 2047
Thanks Andy ! Unfortunately the situation is unchanged. Interesting is that sometime Win98 can see the correct shares but only the first time when is accessing Samba and then... lost. I'm still trying . Can someone tell me how to find what values those %.. parameters take when Samba is acessed ? Alex > > Go to http://www.reac.com/samba/ and check out the stuff with
2016 Oct 21
2
Disk near failure
John R Pierce wrote: > On 10/21/2016 2:03 AM, Alessandro Baggi wrote: >> >> My ssds are failing? > > SSD's wear out based on writes per block. they distribute those > writes, but once each block has been written X number of times, they are > no longer reliable. > > they appear to still be working perfectly, but they are beyond their > design life. soon