search for: fanfar

Hi, I didn't notice php7 bindings were included since 1.4.2. That's good. But I have some problems with these, I compiled xapian-bindings 1.4.3 in a debian 9 container, but had no luck with it: php -r 'require "/usr/share/php/xapian.php";var_export(Xapian::version_string());' '1.4.3'Segmentation fault (core dumped) Regards, Pascal Bonne journée Pascal

...39;m experimenting more with Sweave, R, and LyX. There's now an entry in the LyX wiki on using R, so anybody can do it! http://wiki.lyx.org/LyX/LyxWithRThroughSweave Now I notice this frustrating thing. I think I've done everything possible to make the Design library start up without any fanfare: <<echo=F,quiet=T,print=F>>= library(Design, verbose=F) @ But in the output there is still one page of banner information, which starts like this: Loading required package: Hmisc Hmisc library by Frank E Harrell Jr Type library(help= Hmisc ), ?Overview, or ?Hmisc.Overview ) to see...

...r elusive HOWTO for compiling MFC but I haven't found it anywhere and I don't see any pointers or FAQs on the do's and dont's of compiling MFC. We really want this App to run on Linux and although we are not a large company by any stretch, we are Linux advocates, and will give the fanfare and news of porting our App to Linux with the help of Wine if we can get there. Right now, I'm stuck and need some guidance. Thanks

...a RAID 4 or 5 array (desktop IDE) was not clearly identified and required a bit of troubleshooting to pinpoint which drive had failed. Unfortunately, I've never had an experience where a drive just failed cleanly and was marked bad by Linux software RAID and could then be replaced without fanfare. This is in contrast to my HW raid experiences where a single drive failure is almost always handled in a reliable and predictable manner with zero downtime. Your points about having to use a clunky BIOS setup or CLI tools may be true for some controllers, as are your points about needing to m...

...of R with a more privileged inside view than most I'd like to offer my personal congratulations and thanks. This is the first major release, and a triumph for the skill, perseverence and dedication of the core team that works so quietly but so productively. (I see there was just a little more fanfare than usual this time but I suspect few will notice.) The statistical computing community owes you a tremendous debt of gratitude. My hope is that this release will lead to many authors and teachers adopting R as a standard computational vehicle of great elegance and power, free and here to stay....

Hi - I also posted this on r-sig-ecology to little fanfare, so I'm trying here. I've recently hit an apparent R issue that I cannot resolve (or understand, actually). I am using the quantreg package (quantile regression) to fit a vector of quantiles to a dataset, approx 200-400 observations. To accommodate some autocorrelation issues, I h...

I cannot seem to make the directory work properly ( as I see it ). When I call directory with this setup and press the 3 letters, it locates the person and plays their name. When I hit '1' to call it hangs up without any fanfare or message on the console ( verbose 999 ) It doesn't play goodbye or anything, just a drop. What am I missing? TIA, Bill console... -- Accepting call from '4123673031' to '1529' on channel 1, span 4 == Accepting call on 'Zap/73-1' (4123673031) -- Exec...

I have this message coming every 20 seconds in winbind log. [2008/08/16 11:23:18, 0] libsmb/clientgen.c:cli_receive_smb(165) Receiving SMB: Server stopped responding This is a samba/winbind setup with ldapbackend (editposix feature). I have seen error message in a post of last year but no final explanation of the issue: http://lists.samba.org/archive/samba/2007-August/134178.html version

On Mon, Apr 03, 2017 at 11:58:05AM +0200, Pascal MASSCHELIER wrote: > I didn't notice php7 bindings were included since 1.4.2. That's good. Perhaps I should have made more of a fanfare about them getting added. > But I have some problems with these, > > I compiled xapian-bindings 1.4.3 in a debian 9 container, but had no luck > with it: > > php -r 'require > "/usr/share/php/xapian.php";var_export(Xapian::version_string());' > '1....

...ds, Pascal On Mon, Apr 3, 2017 at 12:12 PM, Olly Betts <olly at survex.com> wrote: > On Mon, Apr 03, 2017 at 11:58:05AM +0200, Pascal MASSCHELIER wrote: > > I didn't notice php7 bindings were included since 1.4.2. That's good. > > Perhaps I should have made more of a fanfare about them getting added. > > > But I have some problems with these, > > > > I compiled xapian-bindings 1.4.3 in a debian 9 container, but had no luck > > with it: > > > > php -r 'require > > "/usr/share/php/xapian.php";var_export(Xapian:...

Doing some comparison to older builds of wxRuby2 I see that some things work better now and some worse. I wish I could pin down exactly where things went wrong in one case. I will try doing some comparison to recent changes to see if I can find a solution to those problems. I''d really like to get this alpha release done ASAP. Roy

...'qx2nut' table, the 'accepted'/'rejected' strings, etc. Now, onto communications (entirely in 'nutdrv_qx.c')... For serial devices: - given that, so far, all supported devices shared similar settings and I/O modus operandi, operations are done directly without much fanfare... - setup is done directly in `upsdrv_initups()`, - ditto for subsequent communications, in `qx_command()`. For USB devices: - `qx_usb_id` lists the various VID:PID pairs (with, optionally and only if needed, the iManufacturer and iProduct strings) of each supported device, coupled with a functi...

Dear Daniele, I'm trying to create a subdriver for 'nutdrv_qx' instead of modifying the Blazer as you suggested, but i honestly don't understand how to integrate usb-serial devices (some of our UPSs have USB but serial protocol Q1). i understand the serial version but not the USB one. i also checked the "Claim" function, but i can't see drivers that uses the VID

On Jun 28, 2019, at 8:46 AM, Blake Hudson <blake at ispn.net> wrote: > > Linux software RAID?has only decreased availability for me. This has been due to a combination of hardware and software issues that are are generally handled well by HW RAID controllers, but are often handled poorly or unpredictably by desktop oriented hardware and Linux software. Would you care to be more

I'm interested in these very questions (librsync-rsync relationship, remaining limitations of rsync, active prospects for ground-up rewrites), Google searches for rsync info have proved a little too vague due to the programs ubiquity. Much has certainly changed since this was written, could some people with knowledge in these areas could update martin's response for the state of rsync,

...p IDE) was >not clearly identified and required a bit of troubleshooting to >pinpoint >which drive had failed. > >Unfortunately, I've never had an experience where a drive just failed >cleanly and was marked bad by Linux software RAID and could then be >replaced without fanfare. This is in contrast to my HW raid experiences > >where a single drive failure is almost always handled in a reliable and > >predictable manner with zero downtime. Your points about having to use >a >clunky BIOS setup or CLI tools may be true for some controllers, as are > &g...

This information will be mirrored on the Xen 4.4 Roadmap wiki page: http://wiki.xen.org/wiki/Xen_Roadmap/4.4 Our timeline had us start the code freeze last Friday. However, we have not released an RC0 because we have been waiting for PVH dom0 support. Adding bug fixes during RCs makes sense, but RC0 should contain all of the functionality we expect to be in the final release. PVH dom0 support

...information >> using LLVM IR, rather than having to override internal LLVM classes in >> order to provide this information. >> > > Can you explain what the benefit of doing so is, past some amount of > work ( that was even done recently in a similar contextwithout much fanfare > in a not-horrible amount-of-time)? > I think i've described the downsides adequately: > > It's not an ideal representation depending on the analysis > For producers that *also* want to convey type based alias info in addition > to this type of info, it requires combinin...

...'qx2nut' table, the 'accepted'/'rejected' strings, etc. Now, onto communications (entirely in 'nutdrv_qx.c')... For serial devices: - given that, so far, all supported devices shared similar settings and I/O modus operandi, operations are done directly without much fanfare... - setup is done directly in `upsdrv_initups()`, - ditto for subsequent communications, in `qx_command()`. For USB devices: - `qx_usb_id` lists the various VID:PID pairs (with, optionally and only if needed, the iManufacturer and iProduct strings) of each supported device, coupled with a functi...

...a frontend to convey this information > using LLVM IR, rather than having to override internal LLVM classes in > order to provide this information. > Can you explain what the benefit of doing so is, past some amount of work ( that was even done recently in a similar contextwithout much fanfare in a not-horrible amount-of-time)? I think i've described the downsides adequately: It's not an ideal representation depending on the analysis For producers that *also* want to convey type based alias info in addition to this type of info, it requires combining multiple analysis outputs i...