search for: _ever_

...#39;t really seem necessary because usually > hardware enablement is additive. Either CentOS is up to the version you > need, or it isn't yet. > > > If you really _need_ a specific minor release and want to _stay_ on it, > to my knowledge, that's not something CentOS has _ever_ done anyway. > You can pay for Red Hat's "EUS", or, I think Scientific Linux actually > does keep the ".y" releases separate (but I'm not sure of the details > as to how that's implemented). > That last paragraph is EXACTLY the message we are trying to...

...ic entries. It has always been mode 0600. And it is quite usual for our configs to have root filesystem read-only. So I don't really know when popped up just today. Samba version is 4.17, but the same code exists in 4.19 too. What's the deal, why samba tries to chmod this file at open, _ever_? This should not be done.. Unfortunately, this incident demonstrated that the legacy logging system is incapable, - in order to stop the filesystem from filling up like this, I removed the old syslog daemon entirely, leaving only systemd journal files - this one keeps the logs under control. Than...

On Thu, Apr 2, 2015 at 11:51 AM, John R Pierce <pierce at hogranch.com> wrote: > On 4/2/2015 9:49 AM, Les Mikesell wrote: >> >> How, without a cross reference of some sort, do you know if a given >> CentOS iso will install on hardware where you know that the needed >> driver was added in an RH minor rev? > > > always use the latest one. Which, combined

...ic to them. There is no saying your random 2k relax loop will be enough to propagate the change. Equally, another arch (this is generic code) might have starvation issues on its inter-cpu fabric and delay the store just long enough. The thing is, one should _never_ rely on timing for correctness, _ever_. > So I am going to > withdraw this particular patch as it has no functional impact to the overall > patch series. Please let me know if you have any other comments on other > parts of the series and I will send send out a new series without this > particular patch. Please wait a l...

...ic to them. There is no saying your random 2k relax loop will be enough to propagate the change. Equally, another arch (this is generic code) might have starvation issues on its inter-cpu fabric and delay the store just long enough. The thing is, one should _never_ rely on timing for correctness, _ever_. > So I am going to > withdraw this particular patch as it has no functional impact to the overall > patch series. Please let me know if you have any other comments on other > parts of the series and I will send send out a new series without this > particular patch. Please wait a l...

...f you have allocated the memory and if it is initialised. This could be done for threads as-well. (ie. how many different threads access this memory, where was this memory is allocated, is there an associated lock?) If people can associate memory regions with locks, we can make sure that no thread _ever_ access synchronised memory without a lock. Although now that I think of it, you could do this with valgrind too. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20070809/595465e5/attachment.html>

Is there a definitive guide on how to create a controller that understands and responds to GET/POST methods ? This does not necessarily mean I''m trying RESTful Web services. Google returned lot of material but most of them is pre-Rails 2.0 or not well explained. Did I miss any obvious document ? -Arun --~--~---------~--~----~------------~-------~--~----~ You received this message

Roger Marquis wrote: > [snip] > >It takes all of 2 seconds to generate a ssh 2 new session on a >500Mhz cpu (causing less than 20% utilization). Considering that >99% of even the most heavily loaded servers have more than enough >cpu for this task I don't really see it as an issue. > >Also, by generating a different key for each session you get better >entropy,

..., but 'u' is the READ_ONCE, and 'v' is the write. Any data, address or conditional dependency between the two implies an ordering. So no, "smp_read_barrier_depends()" is *ONLY* about two reads, where the second read is data-dependent on the first. Nothing else. So if you _ever_ see a "smp_read_barrier_depends()" that isn't about a barrier between two reads, then that is a bug. The above code is crap. It's exactly as much crap as a = READ_ONCE(x); smp_rmb(); WRITE_ONCE(b, y); because a "rmb()" simply doesn't have anything to do...

..., but 'u' is the READ_ONCE, and 'v' is the write. Any data, address or conditional dependency between the two implies an ordering. So no, "smp_read_barrier_depends()" is *ONLY* about two reads, where the second read is data-dependent on the first. Nothing else. So if you _ever_ see a "smp_read_barrier_depends()" that isn't about a barrier between two reads, then that is a bug. The above code is crap. It's exactly as much crap as a = READ_ONCE(x); smp_rmb(); WRITE_ONCE(b, y); because a "rmb()" simply doesn't have anything to do...

To continue here with problems on this compaq v2000 laptop, I put kernel source on a USB disk and plugged it into the v2000. NOTHING IS recognized. I tried to manually mount the disk and nothing either... I thought USB was well established.... I thought trying to recompile the kernel for realtek support might get my networking going... I am stuck??? Jerry -------------- next part

...y different threads access this > memory, where was this memory is allocated, is there an associated > lock?) Yes, that would be extremely handy for debugging synchronization issues (e.g deadlock). > If people can associate memory regions with locks, we can make sure > that no thread _ever_ access synchronised memory without a lock. > Although now that I think of it, you could do this with valgrind too. Okay. Reid. > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.c...

...html A cross-reference doesn't really seem necessary because usually hardware enablement is additive. Either CentOS is up to the version you need, or it isn't yet. If you really _need_ a specific minor release and want to _stay_ on it, to my knowledge, that's not something CentOS has _ever_ done anyway. You can pay for Red Hat's "EUS", or, I think Scientific Linux actually does keep the ".y" releases separate (but I'm not sure of the details as to how that's implemented). -- Matthew Miller <mattdm at fedoraproject.org> Fedora Project Leader

...because usually > > hardware enablement is additive. Either CentOS is up to the version you > > need, or it isn't yet. > > > > > > If you really _need_ a specific minor release and want to _stay_ on it, > > to my knowledge, that's not something CentOS has _ever_ done anyway. > > You can pay for Red Hat's "EUS", or, I think Scientific Linux actually > > does keep the ".y" releases separate (but I'm not sure of the details > > as to how that's implemented). > > > > That last paragraph is EXACTLY t...

On Thu, Apr 2, 2015 at 1:08 PM, Johnny Hughes <johnny at centos.org> wrote: >> >> If you really _need_ a specific minor release and want to _stay_ on it, >> to my knowledge, that's not something CentOS has _ever_ done anyway. >> You can pay for Red Hat's "EUS", or, I think Scientific Linux actually >> does keep the ".y" releases separate (but I'm not sure of the details >> as to how that's implemented). >> > > That last paragraph is EXACTLY the m...

Just the sort of newbie question we all hate ;-) I'm a bit stuck with MOH. I think all is done right and I've read everyhing I can find, but whenever * tries to do MOH, all that happens is '-z: No such file or directory' Yes, I am on redHat. Yes I have installed real mpg123. Yes, it does seem to work from the command line. Any suggestions would be greta, I'm sire

Hi, I get an error using RcppGSL: fatal error: gsl/gsl_vector.h:No such file or directory. What is the best way to install these files as they seem to be missing? Thanks, Oyvind -- View this message in context: http://r.789695.n4.nabble.com/Error-using-RcppGSL-tp3613535p3613535.html Sent from the R devel mailing list archive at Nabble.com.

I'm still relatively new to R but was wondering if anyone could help me force R to compute the f-statistic etc using the the nested term rather than the residual. In my particular case we were nesting a treatment effect by a replicated tank which was not non-significant enough (p>0.25)to be dropped from the statistical model. Here's my code:

Hi, I'm a little confused as to how Debian deals with texinfo files. The R docs are a good example of my problems, so maybe you folks can explain how this works. What I've noticed is that the texinfo files for R get appended/indexed in /usr/share/info/dir as well as /usr/local/info. This results in duplicated entries when I browse the info tree from Emacs. The only solutions I can come

...ONCE, and 'v' is the write. Any data, address or > conditional dependency between the two implies an ordering. > > So no, "smp_read_barrier_depends()" is *ONLY* about two reads, where > the second read is data-dependent on the first. Nothing else. > > So if you _ever_ see a "smp_read_barrier_depends()" that isn't about a > barrier between two reads, then that is a bug. And the smp_read_barrier_depends() in both rcu_dereference() and in lockless_dereference() is ordering the read-to-read case and the underlying hardware is ordering the read-to-w...