search for: _because_

...;@'. I've frequently read that it's always preferable to use accessor functions, so I would think the '@' operator should be avoided. However, ?slot contains the following advise: "Generally, the only reason to use the functional form rather than the simpler operator is _because_ the slot name has to be computed." How do we decide whether to use the function or the operator? Cheers, -- Seb

...void *handle) > +{ > + /* Although we are serializing all requests anyway so this likely > + * doesn't make a difference, return false because the bounce buffer > + * is not consistent for flush. > + */ > + return 0; > +} I think we could get away with returning 1, _because_ we are serializing all requests. Even though we make multiple calls into the plugin (worst-case being read-modify-write-flush on a client write-with-FUA), no other operation can compete with a client flush. But I also agree that if we were to fix the bounce buffer to be thread-safe and change the...

Eric, what do you think of Pavel's analysis and/or suggested fix below? It seems all too plausible to me unfortunately :-( On Fri, May 05, 2017 at 03:46:45PM +0300, Pavel Butsykin wrote: > On 05.05.2017 12:27, Richard W.M. Jones wrote: > > > >Looks good. I'll push this if it passes 'make check && make check-valgrind' > >which I'm currently

I am trying to put some smarts around a call to <%= error_messages_for %> so that when I first come into this page i.e. when my instance variable @target_list has not been defined yet, the page doesn''t break. I''m doing this: <% if @target_list? %> <%= error_messages_for ''target_list'' %> <% end %> I get a syntax error on line 1.

...in >> accordance with c99: C99 permits: #define NULL 0 but POSIX does not. POSIX _requires_ #define NULL ((void*)0) or the equivalent, so that NULL is properly typed as a pointer to void in ALL cases (rather than the weaker C99 solution of letting the integer zero constant leak), in part _because_ of the commonality of passing NULL through varargs functions. >> >> In practice, this means that if NULL is defined as integer and we have >> 64 bit architecture, then here as the last argument - 4 bytes are >> written on the stack: >> dir_contains_files (g, path, &g...

Hi all, I constructed a GAM model with a linear term and two smooth terms, all of them statistically significant but the intercept was not significant. The adjusted r2 of this model is 0.572 and the deviance 65.3. I decided to run the model again without intercept, so I used in R the following instruction: regression= gam(dependent~ +linear_independent +s(smooth_independent_1)

Hi all, Perhaps a stupid question, but I just need pieces of audio from a file. I know I have to use vorbisfile, and the example compiles, but I don't know how to read the buffer. In fact, it's not even documented (or I'm looking at the wrong place). I assumed it was a interleaved buffer containing unsigned shorts, but that didn't work. I also tried the normal decode example,

Hi, I am using a computer to back up files from another computer automatically. I want to exclude large files from backing up. How can I do that? Thank you. Wensheng Jiang

Hi, I have a dovecot 2.0.7 installed on ubuntu 12.10 and often in dmesg I see "init: dovecot main process (7104) killed by KILL signal", I must restarted dovecot, because I can't access to mailbox. Server hardware: 2x1TB disks 4GB memory 1xCPU 2,4GHz HARDWARE RAID 1 Mailbox ~ 1k dovecot.conf # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.5.0-22-generic x86_64 Ubuntu 12.10 xfs

...error, C<.can_extents> should call C<nbdkit_error> with > +an error message and return C<-1>. > + > +This callback is not required. If omitted, then we return true iff a > +C<.extents> callback has been defined. Should we default this to returning true always, _because_ we have the sane fallback of treating the entire image as allocated when .extents is absent? (That is, a plugin has to explicitly opt out of advertising NBD_CMD_BLOCK_STATUS support, because our default works well enough even if the plugin didn't do anything). It would match how filters can ca...

...quot;<even more anal>Except the iommu, those are limitations of chipset, bus and whatever, not EM64T.</even more anal>" It very much has to do with how EM64T differs from AMD64. GARTs and I/O MMUs are even more capable than the Opteron. The issue has not yet been forced on Intel _because_ they still use a "single point of contention" design. All CPUs share one bus, all memory shares another, etc... into a "hub" (with exception of a proprietary NUMA solution, but all I/O still goes through that MCH "hub" on even those designs). http://lists.centos.org/...

Dr. Tweedie, et al.: I recently formatted a partition using EXT3, and after a "df -h" I get 14GB of space. When I reformatted the partition with ReiserFS, and did a "df -h" I got 16GB of space! Now the partition was setup to be 16GB via fdisk, so 16GB is correct. However, why does EXT3 loose 2GB of space? The journals cannot be that big!?! Very Respectfully, Stuart

...should call C<nbdkit_error> with > > +an error message and return C<-1>. > > + > > +This callback is not required. If omitted, then we return true iff a > > +C<.extents> callback has been defined. > > Should we default this to returning true always, _because_ we have the > sane fallback of treating the entire image as allocated when .extents is > absent? (That is, a plugin has to explicitly opt out of advertising > NBD_CMD_BLOCK_STATUS support, because our default works well enough even > if the plugin didn't do anything). It would matc...

...ry first. That's different, although the concepts are similiar. There is no vendor that can provide a solution that doesn't need accommodate at some point in a solution. Fortuntely, we don't have the "on-a-whim" changes in the RHEL space like we do in Windows -- _primarily_ _because_ Red Hat _never_ mixes in "new features" mid-release. But configuration management is _always_ an issue. You are _never_ going to eliminate much of it even in the Linux space. It is a necessary evil that you must do -- and that will vary on the focus of the distro. In fact, not doing co...

On Tue, Jan 31, 2023 at 01:49:53PM +0100, Laszlo Ersek wrote: > On 1/28/23 13:47, Richard W.M. Jones wrote: > > systemd allows sockets passed through socket activation to be named > > with the protocol they require. We only ever pass one socket, name > > it. This environment variable is currently ignored by qemu-nbd and > > nbdkit, but might be used by

After reading through the various SELinux threads, I really became quite perturbed. I mean, really quite perturbed. As an IT Director (and the entire IT department, currently), if I were hiring a sysadmin I know for a fact that someone whose first response to a question on why something doesn't work is 'turn it off' would not get a job here. Neither would a sysadmin with as much

For existing commits, this is almost identical to v1, except that I updated some commit messages and reordered the commits in a somewhat more logical sequence. The main changes are the extra commits: [06/11] plugins: Return NBD_FLAG_CAN_MULTI_CONN from some readonly plugins. - Readonly plugins that can set the flag unconditionally. [09/11] partitioning: Return NBD_FLAG_CAN_MULTI_CONN. [10/11]

Not sure what version we're up to, but this reimplements extents using the new simpler structure described in this thread: https://www.redhat.com/archives/libguestfs/2019-March/msg00077.html I also fixed most of the things that Eric pointed out in the previous review, although I need to go back over his replies and check I've got everything. This needs a bit more testing. However the