search for: criminy

Hey folks. I have a rails controller which is filtering search results for access control. The search results are typically URLs into the rest of the rails app. I''m finding it would simplify the grotty code which is accumulating if I could manually invoke the router. That is to say, if I could send something a URI path string and get back the hash of controller, action, and params that

What unmitigated bullshit. Your attempt at logic is laughable. You hold up threadbare stereotypes as the norm, when in reality they are little more than characters straight out of Central Casting. The "genius hermit who can't associate with people" is dumb and false. It's meant to excuse behavior that is unacceptable, when in reality a person who cannot interact with people is

(Here follows the same email but hopefully properly formatted, with each newline doubled to two as the list engine seems to need it, and mangled to 80 characters line width.) Non-meritocratic technology and academic projects will be damned. This is a general response to Renato's response to Rafael's post, and also to the media discussion sparked by this thread at

Hello everyone. Please keep discussion civil and productive. I’d suggest moving general discussions of social behavior and norms off the llvm-dev list. These discussions are generally quite off topic and draw more heat than light. I’d prefer it if we all just move on. I obviously do not know who “unnamed poster” is, but I am also specifically concerned about people who are not LLVM

...Matches IPv4 packets. > > ip6 | ipv6 > Matches IPv6 packets. > > ip | all > Matches any packet. > ============================================================== > >According to this, "ip" and "all" are synonymous. Criminy! >What am I missing here? > > > >> > >"ipfw -a list" may also help (packet counts). >> >>It's only a short ruleset, it may help us if you show the output of > say >>'ipfw -t show' (or ipfw -at list, same thing), if you're stil...

Dear W.D. Do you understand that by adding the rules into kernel space numbered from zero to sixty five thousand five hundred thirty four you may alter the behavior of the rule number sixty five thousand five hundred thirty five can you please define and list the goals you are trying to achieve by altering default rule in the terms you can both explain and understand. ----- Original Message

Hi peeps, After compiling ipfw into the new 6.2 kernel, and typing "ipfw list", all I get is: "65535 deny ip from any to any" From reading the docs, this might indicate that this is the default rule. (I am certainly protected this way--but can't be very productive ;^) ) By the way, when I run "man ipfw" I get nothing. Using this instead: