search for: foothold

Hi there I''m planning to build "The Perfect Rails/Debian/Lighttpd Stack", published by Ezra Zygmuntowicz and Sean Schertell at http://brainspl.at/rails_stack.html I''m wondering what sort of constant maintanance that setup would incur. What actions have be regularly performed to keep this setup healthy and secure under normal conditions? Alder

...for the use of classes or methods which seem to no longer exist. The SOAP4R rdocs as well as the docs for the SOAP stuff built into Ruby are almost completely empty. They list methods that the classes define, but remain frustratingly silent on what they''re for or how to use them. I need a foothold here. Does anyone have any pointers to decent, not- outdated documents on getting started with SOAP as a client? Also, does anyone know if the SOAP stuff in Ruby does document/literal, or is it RPC only? I''ve read that SOAP4R can do it, but of course it''s not documented, so I have...

...been really "meaty" patches; by that I mean that they affect core functionality and need a careful review by one of a small number of people who really understand that part of the code; understandably, these patches are more likely to go unanswered, especially if you haven't gotten a foothold in that part of the tree. You might try sending in some smaller, trivial patches, like documenting a function which is missing documentation (your patches show that you apparently know the code quite well, an advantage I didn't have), or even just spelling fixes (don't go overboard though)...

...#39;d just do something like my_day_input(@date1), my_hour_input(@date1), my_minute_input(@date1) and then just access @date1 in the receiving controller method and have it be a valid Date. So if you had to implement the above, how would you go about doing it? I''m having trouble getting a foothold in this seemingly complex problem. -- -Matt Torok

...es and putting the things on their own switch and LAN segment blocked from the rest of your networks then do it. If it means shutting down the affected hosts then do it. If if means disconnecting from the network at your gateway then do it. They are in and they are looking for ways to expand their foothold. Delaying containment is pointless. The third thing to do is to involve the authorities. Unauthorised computer access is an indictable offence in Canada and the UK. It is a federal felony in the U.S.A. If you have an incident then report it. That means you should have computer emergency respon...

I think the main benefit of a scheme like this would be that a pull request tells a code owner which patches require their attention. As a contributor it would be nice to see your patch in a queue somewhere rather than just be buried down the mailing list. When patches are sent to llvm-commits it can be hard to tell if a code owner has noticed the patch because it is a very high-volume list.

...eaty" patches; by that I mean that they > affect core functionality and need a careful review by one of a small > number of people who really understand that part of the code; > understandably, these patches are more likely to go unanswered, > especially if you haven't gotten a foothold in that part of the tree. Why is that at alkl understandable? It's understandable that it might take a while top review them but to not get an acknowledgement at all? That is never understandable. > It *would* be nice for a code-owner to have some way to see what needs > to be reviewed...

Just brainstorming here, but what if each CODE_OWNER maintained a spork on Github and accepted Pull Requests? What's a spork, you ask? Well it's fork with no intent to diverge - it spoons some centralized repo (be it via git or git-svn). If you haven't heard the term 'spork' in this context before, it's either because I just made it up or that we share the same

In the spirit of improving communication of Fedora Xen plans to the world, below is a mail I recently circulated in the Fedora community about the direction for Xen-ified kernels from Fedora 9 and onwards. The short story, is that we intend to ship hypervisor & userspace based on Xen 3.2.0 tree, and a kernel based on latest LKML pv_ops tree and patches ontop of that to support Dom0 and

Hey Everyone, We are in the works of planning a new * installation for our company. We have 20 users in our main office and 5 users in a remote office a couple of states away. Our call volume for the main office will be anywhere from 5-10 concurrent calls. The remote office will have about 3 heavy users with two users making calls occasionally. Right now we have an existing PBX. We have a