Search Results

Search found 4 results on 1 pages for 'ivant'.

Page 1/1 | 1 

• If sudo is broken, what should be used instead?

  - by ivant

  I found the following answer to a FAQ question about a security problem in Oprofile: This "problem" only occurs if you actively, and mistakenly, configure access to OProfile via sudo. OProfile uses shell scripts which have not been audited (nor is it likely to happen) for use through the broken sudo facility (anything that lets you alter root's path arbitrarily counts as horribly broken). Do not use sudo! As I see it, the author of the answer suggests that sudo is broken, so that it should not be used not only with oprofile, but for other purposes as well. Are there better alternatives to sudo in Linux?

  Read the article

• ARM assembly puzzle

  - by ivant

  First of all, I'm not sure if solution even exists. I spent more than a couple of hours trying to come up with one, so beware. The problem: r1 contains an arbitrary integer, flags are not set according to its value. Set r0 to 1 if r1 is 0x80000000, to 0 otherwise, using only two instructions. It's easy to do that in 3 instructions (there are many ways), however doing it in 2 seems very hard, and may very well be impossible.

  Read the article

• Best tools / formats for documenting XML API?

  - by ivant

  We are developing XML over HTTP service and we need a way to document the XML interface. Our supported XMLs generally are subsets of some industry standard XML API, which unfortunately lacks any good documentation. It has XSDs though with some annotations, so we use this go generate the initial documentation and then remove the unsupported parts and refine the result. But this process is tedious and the results aren't at all great. Any suggestion about documentation formats and tools? I prefer to have HTML output and possibly more, e.g. PDF. Oh, and we are mixed Linux and Windows shop, so the tools should work well on both.

  Read the article

• "set -e" in shell and command substitution

  - by ivant

  In shell scripts set -e is often used to make them more robust by stopping the script when some of the commands executed from the script exits with non-zero exit code. It's usually easy to specify that you don't care about some of the commands succeeding by adding || true at the end. The problem appears when you actually care about the return value, but don't want the script to stop on non-zero return code, for example: output=$(possibly-failing-command) if [ 0 == $? -a -n "$output" ]; then ... else ... fi Here we want to both check the exit code (thus we can't use || true inside of command substitution expression) and get the output. However, if the command in command substitution fails, the whole script stops due to set -e. Is there a clean way to prevent the script from stopping here without unsetting -e and setting it back afterwards?

  Read the article

1