Re: dig

2011-01-21 Thread Matthew King
On Tue, 18 Jan 2011 12:48:34 +, Peter Corlett ab...@cabal.org.uk wrote: On Tue, Jan 18, 2011 at 12:26:25PM +, Matthew King wrote: Dig can easily look up any type of DNS record with the simple form: $ dig fqdn rr Moreover, when the fqdn is actually a CNAME, it will helpfully look up

Re: scons

2011-01-21 Thread Matthew King
On Wed, 19 Jan 2011 15:21:01 +, Nicholas Clark n...@ccl4.org wrote: On Wed, Jan 19, 2011 at 03:14:30PM +, Nicholas Clark wrote: I'm not sure whose fault this hateful incompetence is - the authors of scons, or the authors of the package's SConstruct file. But, frankly, I don't care.

Re: scons

2011-01-21 Thread Nicholas Clark
On Fri, Jan 21, 2011 at 03:04:34PM +, Matthew King wrote: make is a steaming heap of festering hate, with putrid, hate-filled maggots writhing out of it. Everything which has tried to replicate or improve upon it makes it look attractive and appealing. Like OS X looks right up until the

Re: scons

2011-01-21 Thread Gert Doering
Hi, On Fri, Jan 21, 2011 at 03:12:23PM +, Nicholas Clark wrote: $ scons -f 'This file does not exist' scons: Reading SConscript files ... scons: warning: Ignoring missing SConscript 'This file does not exist' File /usr/bin/scons, line 161, in module scons: done reading SConscript

bash

2011-01-21 Thread H.Merijn Brand
Why do you think I became root? # id uid=0(root) gid=0(root) groups=33(video),100(users) # yast2 sw_single Absolute path to 'yast2' is '/sbin/yast2', so running it may require superuser privileges (eg. root). If that were in . I'd understand and appreciate, but this is so silly -- H.Merijn

Re: scons

2011-01-21 Thread Walt Mankowski
On Fri, Jan 21, 2011 at 03:12:23PM +, Nicholas Clark wrote: $ make -f 'This file does not exist' make: This file does not exist: No such file or directory make: *** No rule to make target `This file does not exist'. Stop. $ echo $? 2 $ sed -f 'This file does not exist' sed:

Re: scons

2011-01-21 Thread Peter Corlett
On Fri, Jan 21, 2011 at 10:43:58AM -0500, Walt Mankowski wrote: [...] I suppose it's too much to ask for programs to return the *same* error code (ENOENT comes to mind) when a file doesn't exist. Why bother? It's not as if shell scripts ever bother to check for errors anyway.

Re: bash

2011-01-21 Thread Aaron Crane
H.Merijn Brand h.m.br...@xs4all.nl wrote: # yast2 sw_single Absolute path to 'yast2' is '/sbin/yast2', so running it may require superuser privileges (eg. root). I entirely agree that this is utterly hateful. (For one thing, the idea that there's a strong relationship between living in a

Re: scons

2011-01-21 Thread Nicholas Clark
On Fri, Jan 21, 2011 at 03:48:44PM +, Peter Corlett wrote: On Fri, Jan 21, 2011 at 10:43:58AM -0500, Walt Mankowski wrote: [...] I suppose it's too much to ask for programs to return the *same* error code (ENOENT comes to mind) when a file doesn't exist. Why bother? It's not as if

Re: bash

2011-01-21 Thread Aristotle Pagaltzis
* Aaron Crane hate...@aaroncrane.co.uk [2011-01-21 16:50]: But the Bash source doesn't seem to contain relevant chunks of that message, so I fear that, if you want to correctly apportion blame, you should probably look elsewhere. Yes. My first instinct would be to indict SELinux. Regards, --