search for: mantra

How do i upgrade my Xen guest (domu1) ? On a stand alone hardware one would insert DVD/CD/Network and perform the upgrade, What is the equivalent in Xen World ? Tahnks !!! -- Regards, mantra - Instrument of Thought _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hey all, Figured this might be a decent place to ask, I am looking for design firms, but very much would like to look into firms like 37signals that understand how important usability is to a site''s success. I''ve already got a call into 37signals so don''t think I''m going to leave them out, but the more I have the better chance I have of convincing the PHB that

Hello Everyone, We are currently having talks with various service providers, and trying to determine what the best way is to interconnect in order to have access to the PSTN network. As you know there are two ways of doing this: Traditional PRI: Have trunks grouped into a transport layer such as OC3/12. With DIDs attached to the group. As you many know, this approach would also require a POP

Hi, I have searched the documentations of eval, substitute, expression, and I cannot make work something like the values of a list of variable names: lis <- ls(pattern="pr") # all variables with names containing 'pr' What is the mantra giving me the _values_ of the variables whose names are contained in 'lis'. eval(parse(ls(pattern="pr"))) will not do but returning TRUE. TIA C. -- Christian Hoffmann Rigiblickstrasse 15b CH-8915 Hausen am Albis Switzerland Telefon +41-(0)44-7640853

...an't help but recall that I brought up this exact issue probably 15 years ago and was told (by Brian, I believe) "don't do that" (pass a null pointer), which was perfectly fine. The real issue was not the behavior but that it was not documented or consistent. I've lived by the mantra since that you can never trust a pointer in R code. User must always check for NULL. I just wrote my own functions mkXXX_safe that wrap the internals and check the pointer. THK http://www.keittlab.org/ [[alternative HTML version deleted]]

...hown itself by now surely. > > gcc is however notorious for exposing bad memory problems. The build also stops at exactly the same point in several different *virtual* machines. (the assert() in utils/TableGen/CodeGenDAGPatterns.cpp line 932) Please stop repeating the "bad memory" mantra, that hasn't been true for years; it is much more likely to be a bug in gcc. > >> As a test I got another developer to try on a different machine and he >> has the same problem. In another test he also tried a more aggressive >> malloc.conf (a mechanism which causes mallo...

On Wed, December 31, 2014 12:03, Warren Young wrote: > > So, cope with change. > Is one to infer from your mantra 'cope with change' that one is not supposed to express any opinion whatsoever, ever, on any forum; on the externalised cost of changes made to software with no evident technical justification? And that to do so is evidence of some moral or intellectual defect in oneself? We all cope with c...

Sorry, I couldn't resist, there are so many recipients... FROM THE DALAI LAMA: Do not keep this message. The mantra must leave your hands within 96 hours. You will get a very pleasant surprise. This is true, even if you are not superstitious. I N S T R U C T I O N S F O R L I F E 1. Take into account that great love and great achievements involve great risk. 2. When you lose, don't lose the lesson. 3...

...nyone > who breaks the MSVC build will get a nastygram from buildbot. This is new news for me. If the developer who broke the msvc build receives a nastygram, would he urged to fix it when he has no msvc compiler and probably no Windows machine either? The "don't break the build" mantra applies to *nix only. No LLVM developer will be bashed for breaking the msvc build. Which is understandable: the pain of multiple compiler C++ support is too much for mere mortals. Anyways, that buildbot only checks one msvc compiler (right?). It is not infrequent a broken build on some compiler v...

"Google: Evil or Not?" is my first Rails webapp and I''ve just made it public at http://evilornot.info Do you still believe the ?Do no evil? Google mantra? Do you think Google Book Search, the AOL deal, and Larry and Sergey?s 767 point to Google losing it?s pristine morality and turning over to the dark side? Now you can discover what the world thinks and contribute your own opinion. Head over to Google: Evil or Not? and vote with your mouse....

...hadow? User input is not an option, meaning I do not want to locate these 100+ users and have them type in their passwd to smbpasswd. Assigning passwords to these 100+ users is not an options as well. I would like their smbpasswd and shadow passwd to be identical. One network, one password is the mantra here. I do have read about smbpasswd and /etc/passwd synchronization and changing passwds from Windows boxes. I do not need synchronization of smbpasswd and passwd, I just need to build this smbpasswd file once. Users will not need to change passwds from their Windows boxes. Does a solution to my...

...is move the retrieval code into the model then have something along the lines of <% Event.upcoming do |event| %> //html code <%= event.name %> //html code <% end %> In the layout view. This seems to fly in the face of the "Put as little code in the views as possible" mantra I see all over the ruby community so I am not quite sure how to handle this. Does anyone have any insightful way of doing this? Many thanks Jeff -- Posted via http://www.ruby-forum.com/.

...VC build will get a nastygram from buildbot. > > This is new news for me. > > If the developer who broke the msvc build receives a nastygram, would he > urged to fix it when he has no msvc compiler and probably no Windows > machine either? The "don't break the build" mantra applies to *nix > only. No LLVM developer will be bashed for breaking the msvc build. > Which is understandable: the pain of multiple compiler C++ support is > too much for mere mortals. It is frequently possible to unbreak the build just from reading the log. In practice this isn't t...

...st check out http://svn.xiph.org/oggdsf/trunk (it will take a while!), cd into the unix/ directory, type 'autoreconf' there to invoke the GNU autotools chain (autoreconf should come as part of your OS distribution), and do the standard ./configure && make && make install mantra. Anyway, if you have more of a C++ bent or just want an alternative to libogg on UNIX, have a look at the oggdsf-derived libraries. Happy hacking! -- : Andr? Pang (x4180) : Software Engineer, Networked Media : CeNTIE

...st check out http://svn.xiph.org/oggdsf/trunk (it will take a while!), cd into the unix/ directory, type 'autoreconf' there to invoke the GNU autotools chain (autoreconf should come as part of your OS distribution), and do the standard ./configure && make && make install mantra. Anyway, if you have more of a C++ bent or just want an alternative to libogg on UNIX, have a look at the oggdsf-derived libraries. Happy hacking! -- : Andr? Pang (x4180) : Software Engineer, Networked Media : CeNTIE

> AFAIU, it's not OK for -g to affect code generation. I agree with the > rest of your plan. That's correct, -g must not affect code generation. This is a fundamental mantra among debug-info people. > > > On Wed, Nov 27, 2013 at 2:16 PM, Renato Golin <renato.golin at linaro.org> > wrote: > > On 27 November 2013 08:43, Evgeniy Stepanov > <eugeni.stepanov at gmail.com> > > wrote: > >> > >> Also note that tail me...

Hi all, I hope you don't mind the slightly off topic email, but I'm going to be teaching an R development master class in New York City on Dec 12-13. The basic idea of the class is to help you write better code, focused on the mantra of "do not repeat yourself". In day one you will learn powerful new tools of abstraction, allowing you to solve a wider range of problems with fewer lines of code. Day two will teach you how to make packages, the fundamental unit of code distribution in R, allowing others to save time by...

On Sun, Aug 9, 2009 at 1:04 PM, Óscar Fuentes<ofv at wanadoo.es> wrote: > Eli Friedman <eli.friedman at gmail.com> writes: > >> On Sun, Aug 9, 2009 at 10:03 AM, Óscar Fuentes<ofv at wanadoo.es> wrote: >>> I think most LLVM users on Windows are interested on X86 only. This >>> saves a lot of time on the build process and creates smaller >>>

...3.3 No privileged access is possible for OpenSSH with UsePrivsep enabled. 3. Solution: Apply the following patch and replace radix.c with http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/radix.c?rev=1.18 4. Credits: kurt at seifried.org for notifying the OpenSSH team. http://mantra.freeweb.hu/ Appendix: Index: bufaux.c =================================================================== RCS file: /cvs/src/usr.bin/ssh/bufaux.c,v retrieving revision 1.24 diff -u -r1.24 bufaux.c --- bufaux.c 26 Mar 2002 15:23:40 -0000 1.24 +++ bufaux.c 19 Apr 2002 12:55:29 -0000 @@ -137,10 +137...

...3.3 No privileged access is possible for OpenSSH with UsePrivsep enabled. 3. Solution: Apply the following patch and replace radix.c with http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/radix.c?rev=1.18 4. Credits: kurt at seifried.org for notifying the OpenSSH team. http://mantra.freeweb.hu/ Appendix: Index: bufaux.c =================================================================== RCS file: /cvs/src/usr.bin/ssh/bufaux.c,v retrieving revision 1.24 diff -u -r1.24 bufaux.c --- bufaux.c 26 Mar 2002 15:23:40 -0000 1.24 +++ bufaux.c 19 Apr 2002 12:55:29 -0000 @@ -137,10 +137...