search for: oooohhh

Dear All, Here the version 2.2 a new version of your dear CallingCard Software !!! http://www.areski.net/areskicc-doc-v2/ Many new features have been added and several enhancements made! Newest features : - A new re-build rate-engine - LCR & LCD management (OOOOHHH YESSSSS) - Billing Increment - Progressive Rate - Scheduled Rates (days of the weeks) - Expiration rates - Buy rates configuration - importation ratecard from csv file - Simultaneous access for same card - SIP/IAX Friends Management - Generate conf file for SIP/IAX Friends - Reload Asteri...

On 9/13/11 9:22 AM, Michael Clagett wrote: > Oooohhh! That's interesting. Does the optimizer just work around > these inline fragments? Is there documentation for this facility? CC'ing the mailing list. The inline assembly feature is described in the LLVM Language Reference Manual (http://llvm.org/docs/LangRef.html). I'm not r...

Hello all. Is there a way to stop users from being able to access a controllers methods without affecting the ability of other controllers to use them? i.e FooController def secret #Stuff end end BarController def index redirect_to :controller => ''foo'', action => ''secret'', :id => ''007'' end end But directly

Hi -- I'm still very much a newbie with llvm, but am looking (hopefully) to use it to compile into native intel code a set of source that is a combination of byte codes for my own custom vm and intel code that has been coded in assembly language directly. In an earlier exchange, I already discovered that llvm does not do any optimizations on intel assembly language code. This would be an

...nd "zpool add" a new log device. Next: 1. Created a pool, with unmirrored log device. 2. Started benchmark of sync writes, verified the log device getting heavily used. 3. Yank out both power cords. 4. While the system is down, also remove the log device. (OOoohhh, that''s harsh.) I created a situation where an unmirrored log device is known to have unplayed records, there is an ungraceful shutdown, *and* the device disappears. That''s the absolute worst case scenario possible, other than the whole building burning down. Anyway, the system...

Hey all, Let's make an assumption: 1) I am a root user on a system. 2) I don't want said system being used as a jumping-off point if either a user account or the root account is compromised. Given an unencrypted private key, plus a known_hosts file, plus bash_history, it's a pretty easy avenue of attack once you're in the front door. And it's happened before*. Thus,