search for: msg00004

...Is this a known limitation of samba on the Mac, or can it be fixed by upgrading to a newer version of the client? I found a bit of info stating that there _used_ to be a problem (2004), but it would be fixed in the 10.4 series of MacOSX. http://lists.apple.com/archives/Darwin-userlevel/2004/Jul/msg00004.html I couldn't find any other info. Anybody know? ~Sean

...ill not be added to augeas). Can we > somehow handle the error aug_transform? Because if we could know that > augeas already contains the config path, it would simplify the issue. I posted a question related to this on augeas-devel: https://www.redhat.com/archives/augeas-devel/2016-November/msg00004.html Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. h...

The previous commit broke the build during 'make check'; we want to test the in-tree header, not some (potentially stale or missing) installed header. Signed-off-by: Eric Blake <eblake at redhat.com> --- tests/Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/Makefile.am b/tests/Makefile.am index c2d473a..9076d6b 100644 --- a/tests/Makefile.am

Hi List. doing my weekly updates with yum last night installed kernel.x86_64 2.6.18-194.17.4.el5.centos.plus and flash-plugin.i386 10.1.102.64-release now today as I go to watch a movie from hulu.com it crashes the flash-plugin whenever I try to go full screen. Anyone else notice this behaviour? I guess I'll try to downgrade flash and see if that fixes the problem. TIA --------------

Hi, everyone I'm writing a application using libvirt and need to query guest os's virtual network interface usage, like bytes read or written through a given interface. I know int virDomainInterfaceStats(virDomainPtr dom, const char * path, virDomainInterfaceStatsPtr stats, size_t size) is designed for my purpose but I 'm not sure how I determine the second parameter path.

...(switching to less old one didn''t help) qemu VFB due to https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=718620 = the event channel issue where the dom0 and domU are using different vcpus while talking to each other http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00004.html this could possibly be sorted with a nightmarish hack that maps all vcpus onto one cpu on shutdown time by sshing into dom0. One would have to ensure the mapping is OK again after a reboot. err. you can imagine how much I "like" this idea. = domU kernel: yet untested, I hardly have...

...9:30:36AM -0500, Eric Blake wrote: > I've run several tests to demonstrate why this is useful, as well as > prove that because I have multiple interoperable projects, it is worth > including in the NBD standard. The original proposal was here: > https://lists.debian.org/nbd/2019/03/msg00004.html > where I stated: > > > I will not push this without both: > > - a positive review (for example, we may decide that burning another > > NBD_FLAG_* is undesirable, and that we should instead have some sort > > of NBD_OPT_ handshake for determining when the server...

I guess you've all read it already, but here it goes: "All video codecs are covered by patents. A patent pool is being assembled to go after Theora and other ?open source? codecs now. Unfortunately, just because something is open source, it doesn?t mean or guarantee that it doesn?t infringe on others patents. An open standard is different from being royalty free or open source. Sent

v1 was here: https://www.redhat.com/archives/libguestfs/2019-November/msg00003.html This version depends on: https://www.redhat.com/archives/libguestfs/2019-November/msg00004.html and this series: https://www.redhat.com/archives/libguestfs/2019-November/msg00009.html The delta has been reduced slightly because of changes made possible by cleaning up and fixing the quit path in nbdkit. It's still a fairly ugly and invasive patch however, so suggestions sought about...

...reference, > it's a draft. It's also not an OASIS document yet. It may be riddled > with mistakes. As this is a working draft, it is unstable and I do not > guarantee backward compatibility of future versions. > [3] https://lists.gnu.org/archive/html/qemu-arm/2017-08/msg00004.html > [4] git://linux-arm.org/linux-jpb.git virtio-iommu/v0.4 > Warning: UAPI headers have changed! They didn't follow the spec, > please update. (Use branch v0.1, that has the old headers, for the > Qemu prototype [3]) When rebasing the v0.4 driver on master I observe...

...h you to complete the patch. (In the meantime, I'm using openssh patched with libunbound on my macbook since OS/X's libc doesn't support DNSSEC.) Thanks for your consideration, Luca Filipozzi [1] http://www.debian.org/intro/organization [2] http://lists.debian.org/debian-ssh/2012/05/msg00004.html -- Luca Filipozzi Member, Debian System Administration Team -------------- next part -------------- A non-text attachment was scrubbed... Name: openssh.diff Type: text/x-diff Size: 2654 bytes Desc: not available URL: <http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/2012050...

...it's a draft. It's also not an OASIS document yet. It may be riddled > > with mistakes. As this is a working draft, it is unstable and I do not > > guarantee backward compatibility of future versions. > > [3] https://lists.gnu.org/archive/html/qemu-arm/2017-08/msg00004.html > > [4] git://linux-arm.org/linux-jpb.git virtio-iommu/v0.4 > > Warning: UAPI headers have changed! They didn't follow the spec, > > please update. (Use branch v0.1, that has the old headers, for the > > Qemu prototype [3]) > > [5] git://linux-arm....

From: Pavel Butsykin <pbutsykin@virtuozzo.com> This patch improves the search of grub config on EFI partition. This means that the config will be found not only for rhel but also for many other distributions. Tests were performed on the following distributions: centos, fedora, ubuntu, suse. In all cases, the config path was /boot/efi/EFI/*distname*/grub.cfg The main purpose of the patch

...reference, > it's a draft. It's also not an OASIS document yet. It may be riddled > with mistakes. As this is a working draft, it is unstable and I do not > guarantee backward compatibility of future versions. > [3] https://lists.gnu.org/archive/html/qemu-arm/2017-08/msg00004.html > [4] git://linux-arm.org/linux-jpb.git virtio-iommu/v0.4 > Warning: UAPI headers have changed! They didn't follow the spec, > please update. (Use branch v0.1, that has the old headers, for the > Qemu prototype [3]) > [5] git://linux-arm.org/kvmtool-jpb.git virti...

...is always the same. I have a couple of KVM books - consulted them on this topic, consulted Red Hat and SUSE docs but pretty much the configuration instructions are, naturally, the same. I saw that some colleagues posted a few emails (ie https://www.redhat.com/archives/libvirt-users/2015-September/msg00004.html) to the list related to virtlock but it seems that it is not the same issue. I have also, as a last resort, completely disabled SELinux, rebooted both hypervisors, created a new vm, repeated all the steps listed above but with the same results. Now, I am pretty sure that I am missing somethin...

...this document as a reference, it's a draft. It's also not an OASIS document yet. It may be riddled with mistakes. As this is a working draft, it is unstable and I do not guarantee backward compatibility of future versions. [3] https://lists.gnu.org/archive/html/qemu-arm/2017-08/msg00004.html [4] git://linux-arm.org/linux-jpb.git virtio-iommu/v0.4 Warning: UAPI headers have changed! They didn't follow the spec, please update. (Use branch v0.1, that has the old headers, for the Qemu prototype [3]) [5] git://linux-arm.org/kvmtool-jpb.git virtio-iommu/v0.4 Warning:...

...this document as a reference, it's a draft. It's also not an OASIS document yet. It may be riddled with mistakes. As this is a working draft, it is unstable and I do not guarantee backward compatibility of future versions. [3] https://lists.gnu.org/archive/html/qemu-arm/2017-08/msg00004.html [4] git://linux-arm.org/linux-jpb.git virtio-iommu/v0.4 Warning: UAPI headers have changed! They didn't follow the spec, please update. (Use branch v0.1, that has the old headers, for the Qemu prototype [3]) [5] git://linux-arm.org/kvmtool-jpb.git virtio-iommu/v0.4 Warning:...

With GPLPV under 2.6.30, GPLPV gets the following from the ring: ring slot n (first buffer): status (length) = 54 bytes offset = 0 flags = NETRXF_extra_info (possibly csum too but not relevant) ring slot n + 1 (extra info) gso.size (mss) = 1460 Because NETRXF_extra_info is not set, that''s all I get for that packet. In the IP header though, the total length is 1544 (which in itself

With GPLPV under 2.6.30, GPLPV gets the following from the ring: ring slot n (first buffer): status (length) = 54 bytes offset = 0 flags = NETRXF_extra_info (possibly csum too but not relevant) ring slot n + 1 (extra info) gso.size (mss) = 1460 Because NETRXF_extra_info is not set, that''s all I get for that packet. In the IP header though, the total length is 1544 (which in itself

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3 Severity: grave Justification: causes non-serious data loss -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash