search for: unsympathetic

...mp/thursday.snap # zfs create pool/thursday # gzip -d -c /var/tmp/thursday.snap.gz | zfs receive -F pool/thursday === End quote === There have been several threads on this list saying not to do that. It seems that this guide aimed at new users is inviting people to do things that will lead them to unsympathetic ears if things go poorly. -- Mike Gerdts http://mgerdts.blogspot.com/

...on -questions, or it was out of place there, or I'm not providing the right kind of info or... I'm open to suggestions.) At this stage I'd approach bliss if someone could even tell me how to make bind forget that IPv6 exists, and therefore stop hammering these queries at an apparently unsympathetic NT DNS server. Two affected (dns-forwarding-only) machines are: FreeBSD 4.8-PRERELEASE #0: Mon Feb 24 12:43:50 EST 2003 named 8.3.4-REL Mon Feb 24 11:46:20 EST 2003 4.6-RELEASE FreeBSD 4.6-RELEASE #0: Tue Jun 11 06:14:12 GMT 2002 named 8.3.2-T1B Tue Jun 11 03:58:03 GMT 2002 BTW, requiring BIND...

Dear all, I'm trying to construct confidence intervals for a LOWESS estimation (by not using bootstrapping). I have checked previous posts and other material online and I understand that the main procedure is: my.count<- seq(...) fit<- loess (y ~ x, data=z) pred<- pred(fit, my.count, se=TRUE) and then the plotting. However, it's not working; as confidence

Hi, i would like to inspire a discussion on why samba4 has nearly no adaption on home/small business routers firmware. I recently switched from my old Asus-N16 running tomato to a WRT-1200AC and was researching potential firmware's that i could run. We have a new synology disk-station at work that runs Samba 4.x and it works great. So i was surprised to notice that 3 years after the 4.0

Hi Neil, I'm really not sure what you're getting at. Are you objecting to the proposal to update? The LLVM community operates by having request-for-comment (RFC) discussion threads to coalesce around a plan, then just moving forward. There is no formal argument or proposal needed. We also don't really have an official policy regarding updating CMake. In your other emails on the

This came up again recently with an irreproducible paper. Below an attempt to make a case for extending the r-devel/r-release cycle to CRAN packages. These suggestions are not in any way intended as criticism on anyone or the status quo. The proposal described in [1] is to freeze a snapshot of CRAN along with every release of R. In this design, updates for contributed packages treated the same as

(quoting from the web archive, I only just subscribed) Monty wrote: > > > (a bit testy that this flamewar has started again, and no one has learned a > > thing from the previous rounds) > > OK, that wasn't fair... the old timers know what's up, but I do wish some of > the folks who bring things up would browse the archive threads or at least not > jump in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On October 31st, FreeBSD 5.3 and FreeBSD 5.4 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Users of either of those FreeBSD releases are strongly encouraged to upgrade to FreeBSD 5.5 or FreeBSD 6.1 before that date. In addition, the FreeBSD 6.0 End of Life is presently scheduled