search for: respun

Using Rusty's suggestion I've respun the patch removing the special copy function. I've tested this patch in a guest kernel with and without qemu supplying serial numbers for the block devices and it's working as expected. When qemu supplies serial numbers, the correct value is supplied to /sys/block/vdX/serial and can be use...

Using Rusty's suggestion I've respun the patch removing the special copy function. I've tested this patch in a guest kernel with and without qemu supplying serial numbers for the block devices and it's working as expected. When qemu supplies serial numbers, the correct value is supplied to /sys/block/vdX/serial and can be use...

Hello, I''m using the latest b75 ISO to try and get a solaris dom0 running on my laptop, a Sony SZ-330P. The Xen LiveCD works just fine, so I know that theoretically it should work. Build 75 also works just fine on my Sony, including sound and video, etc. But when I try and boot the Xen kernel, the system hangs. There''s no panic printed to console. If I pass a -v option at

https://bugzilla.mindrot.org/show_bug.cgi?id=1933 Bug #: 1933 Summary: restorecon typoed as "restorcon" in contrib/redhat/sshd.init Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: All OS/Version: All Status: NEW Severity: normal

.... > > uvesafb will always need X86_IOPORT. It's kind of implicit in the design. > I'm not suggesting that fbdev should select X86_IOPORT but in the uvesafb > case at least it's completely useless to have one and not the other. OK, fair enough. Do you want the patch series respun to add that select in patch 10/10, or would you consider it sufficient to add that in a followup patch, since the kernel will build and boot either way (so it won't break bisection)? Related to that: Is it intentional that FB_UVESA doesn't depend on X86, even though FB_VESA does? Does v86...

Some of the other RHEL rebuilds take one or two days, while CentOS takes 2 weeks. While i can't say if they have more than a hundred users, their speed in releasing quarterly updates is commendable. Technically CentOS is not the slowest, as Whitebox takes the wooden spoon but you get the general idea. :) __________________________________________________ Do You Yahoo!? Tired of spam?

OpenSSH 5.9 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches,

OpenSSH 5.9 has just been released. It will be available from the mirrors listed at http://www.openssh.com/ shortly. OpenSSH is a 100% complete SSH protocol version 1.3, 1.5 and 2.0 implementation and includes sftp client and server support. Once again, we would like to thank the OpenSSH community for their continued support of the project, especially those who contributed code or patches,

> > This isn't unreasonable but there are drivers with userspace helpers that > > use iopl/ioperm type functionality where you should be doing a SELECT of > > X86_IOPORT. The one that comes to mind is the uvesa driver. From a quick > > scan it may these days be the only mainstream one that needs the select > > adding. > > Should kernel drivers really

> > This isn't unreasonable but there are drivers with userspace helpers that > > use iopl/ioperm type functionality where you should be doing a SELECT of > > X86_IOPORT. The one that comes to mind is the uvesa driver. From a quick > > scan it may these days be the only mainstream one that needs the select > > adding. > > Should kernel drivers really

Hi Kaleb, Thanks, this refers to 3.11.x On Mon, Jul 3, 2017 at 4:16 PM, Kaleb S. KEITHLEY <kkeithle at redhat.com> wrote: > On 07/03/2017 06:29 AM, Kaleb S. KEITHLEY wrote: > >> On 07/03/2017 04:34 AM, Atin Mukherjee wrote: >> >>> >>> On Mon, 3 Jul 2017 at 12:28, Pawan Alwandi <pawan at platform.sh> wrote: >>> >>> Hello Atin,

Hello! What is the simplest way to make merb respond to the client sending Accept-Encoding: gzip? Just checking if it exists, otherwise I''ll implement it myself. Regards, Magnus

The formatting of the IO-APIC debug key info has niggled me for a while, and with the latest interrupt bug I am chasing, has finally motivated me to fix it. The attached patch causes all columns to line up, and removes the comma which served no purpose in combination with the spaces already present. -- Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer T: +44 (0)1223 225 900,

Patch 5 has been respun with the recommended change... remove the ex argument in ocfs2_orphan_scan_lock() and ocfs2_orphan_scan_unlock(). Sunil

This series replaces the existing paravirtualized spinlock mechanism with a paravirtualized ticketlock mechanism. The series provides implementation for both Xen and KVM. The current set of patches are for Xen/x86 spinlock/KVM guest side, to be included against -tip. I 'll be sending a separate patchset for KVM host based on kvm tree. Please note I have added the below performance result

This series replaces the existing paravirtualized spinlock mechanism with a paravirtualized ticketlock mechanism. The series provides implementation for both Xen and KVM. The current set of patches are for Xen/x86 spinlock/KVM guest side, to be included against -tip. I 'll be sending a separate patchset for KVM host based on kvm tree. Please note I have added the below performance result

This series replaces the existing paravirtualized spinlock mechanism with a paravirtualized ticketlock mechanism. The series provides implementation for both Xen and KVM. The current set of patches are for Xen/x86 spinlock/KVM guest side, to be included against -tip. I 'll be sending a separate patchset for KVM host based on kvm tree. Please note I have added the below performance result