similar to: zpool fails with panic in zio_ddt_free()

Hi! I have been plaing arround with libvirt and I've ran into a problem that I don't seem to able to fix, sharing the clipboard. Both my host and my guest are running Arch Linux. I have properly installed, enabled and started spice-vdagent on both machines and I don't see any error in the logs. Am I doing anything wrong? Do I need to have anything else in consideration? Any help is

Sun, 26 Jul 2020 19:03:04 +0100 Rowland penny via samba <samba at lists.samba.org>: > On 26/07/2020 18:45, RhineDevil wrote: > > > > Done, I still get the same errors when adding mod.ldif > > > > (I used ldbadd instead of ldbmodify, is that a problem?) > > No, that isn't the problem, the problem is that I forgot to remove a > comment :-( > >

Mon, 27 Jul 2020 09:09:04 +0100 Rowland penny via samba <samba at lists.samba.org>: > On 27/07/2020 01:12, RhineDevil wrote: > > Sun, 26 Jul 2020 19:03:04 +0100 Rowland penny via samba <samba at lists.samba.org>: > >> On 26/07/2020 18:45, RhineDevil wrote: > >>> Done, I still get the same errors when adding mod.ldif > >>> > >>> (I

Sun, 26 Jul 2020 12:06:03 +0100 Rowland penny via samba <samba at lists.samba.org>: > On 26/07/2020 10:58, RhineDevil wrote: > > You said you didn't want to help me about this but if you'd do at least I'd learn something useful for custom schemas, since this type of error isn't referenced anywhere > > No, I said I wouldn't help you shoot yourself in the

Dear all, I have build a Domain with to samba4 DC's. Everything works fine DNS Replication, User Replication, etc. Now I started to create a Logonscript. I doesn't reach to get the Logonscript automatcally loaded. The client doesn't load the DDP, doesn't load the GPO and doesn't load the logonscript individually in the user-setup by Remote Server Tools. When I start

I am new on R, so I have a maybe naive question: if I have many large data.frames and I use only one or two per session, what's the best way? If all are stored in the actual .Rdata, the system gets slow. On the other hand, I wouldn't like to make a separate package for the data. Should I save it with save() and then remove it with rm() ? Could I reload it then? Thanks for suggestions

A new package "g.data" is available on CRAN, to create and maintain databases that work more like the S-Plus model. Here's the official Description for g.data (v1.2): Create and maintain delayed-data packages (DDP's). Data stored in a DDP are available on demand, but do not take up memory until requested. You attach a DDP with g.data.attach(), then read from it and assign

A new package "g.data" is available on CRAN, to create and maintain databases that work more like the S-Plus model. Here's the official Description for g.data (v1.2): Create and maintain delayed-data packages (DDP's). Data stored in a DDP are available on demand, but do not take up memory until requested. You attach a DDP with g.data.attach(), then read from it and assign

Hi everyone, I have a very annoying character encoding problem. Have a look to this: # ls -l M*mo-1.* -rw-rw-rw- 1 root root 8417218 6 sept. 2013 Mémo-1.aif -rwxr--r-- 1 hope hope 8417218 6 sept. 2013 Mémo-1.aif -rw-rw-rw- 1 root root 363175 6 sept. 2013 Mémo-1.m4a -rwxr--r-- 1 hope hope 363175 6 sept. 2013 Mémo-1.m4a Yes, it looks like two files have exactly the same name, but

Hello! [Cc to stable@, for wider audience] The plan is two axe two old networking protocols from FreeBSD head/, meaning that FreeBSD 11.0-RELEASE, available in couple of years would be shipped without them. 1) AppleTalk Last time claimed to be supported by vendor in 2007[1]. In practice had very little use since 90th. Discontinued by major routing equipment vendors since 2009[2].

I've been doing this on CentOS 4 and CentOS 5 but after installing 2.6.18-53.1.4el kernel, I'm having a bit of a struggle... # make -C /lib/modules/2.6.18-53.1.4.el5/build \ SUBDIRS=/usr/src/appletalk modules make: Entering directory `/usr/src/kernels/2.6.18-53.1.4.el5-i686' CC [M] /usr/src/appletalk/aarp.o CC [M] /usr/src/appletalk/ddp.o CC [M] /usr/src/appletalk/dev.o

as the next klibc release 1.5.16 looks like shaping up, I have a trouble to build that for Debian. currently I build depent on linux-libc-dev, I don't know what against I can build latest klibc, see klibc fails to build due too: make -C linux/ ARCH=x86_64 INSTALL_HDR_PATH=debian/tmp/usr/lib/klibc/ headers_install make[3]: *** No rule to make target `headers_install'. Stop. make[2]: ***

On Wed, Oct 10, 2018 at 01:54:33PM -0500, Segher Boessenkool wrote: > It would be great to hear from kernel people if it works adequately for > what you guys want it for :-) Sure, ping me when you have the final version and I'll try to build gcc with it and do some size comparisons. Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the

On Wed, Oct 10, 2018 at 01:54:33PM -0500, Segher Boessenkool wrote: > It would be great to hear from kernel people if it works adequately for > what you guys want it for :-) Sure, ping me when you have the final version and I'll try to build gcc with it and do some size comparisons. Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the

I have a daily job that attaches hundreds of pseudo-packages containing data as promise objects (DDP's, ref: g.data package), and plots the results to a multi-page pdf device. Sometimes it fails. Under R-2.2.1 it just gave segfaults. Under R-2.3.1 it gave this error message: *** caught segfault *** address (nil), cause 'memory not mapped' Traceback: 1:

My "g.data" contributed package fails under R-devel. g.data creates minimal packages which consist only of a "DESCRIPTION" file and the "R" and "data" subdirectories, but .find.package() now rejects them because the DESCRIPTION file lacks a "Version" field. I will fix g.data to add a "Version" field. My question is, what else is

The following patchset implements 3 seperate series of changes. External Building ================= Patches 1 through 8 enable to use of klibc's build system while leaving the src tree pristine (and potentially read only). Specifically: - srctree=<Sources for klibc> - objtree=<Ouput directory for klibc> - KLIBCKERNELSRC=<Kernel sources> - KLIBCKERNELOBJ=<Kernel